FAQ
RBC (Royal Bullion Coin) is a gold-backed token concept — digital ownership designed around physical bullion on our trading platform — with a fixed 100M supply, deployed on five test networks (Tron, Ethereum, Base, Optimism, Arbitrum) as a demonstration. It shows the full token lifecycle — creation, presale, staking, treasury, and DEX listing — with every rule enforced by smart contracts. In the demo phase no physical gold is held; the mainnet design pairs each token with audited bullion reserves.
No. This deployment runs on a test network with valueless test TRX. It is an educational demonstration, not an offer or solicitation to invest. A real launch would only happen after audits, legal review, and regulatory compliance — see the roadmap.
Near-zero transaction fees, 3-second blocks, and the most battle-tested token standard in the industry — TRC-20 carries more USDT volume than any other chain. For a token whose users will make many small transactions (buys, stakes, claims), fees matter.
They're the same idea on different chains: a standard interface for tokens. ERC-20 lives on Ethereum, TRC-20 on Tron. RBC's contracts are written in Solidity either way — Tron's virtual machine is Ethereum-compatible — so an Ethereum deployment remains possible later.
Today, the deployer wallet (this is a demo). Before mainnet, ownership moves to a multisig, and the roadmap adds governance voting over the parameters that remain adjustable (like staking APR). Most rules — supply, sale caps, rates — are immutable and controlled by nobody.
A smart contract — no person handles orders. It enforces the price, per-wallet limits, and caps, and issues automatic refunds if the soft cap fails. You can read its code on Tronscan.
Refunds open automatically for every buyer — one click returns 100% of your TRX. The team cannot prevent or delay this; it's in the contract.
No. TRX stays locked in the sale contract until the sale window ends and finalize() is called — and only if the soft cap was met. On mainnet, the destination would be a multisig, and most of it goes straight into locked DEX liquidity.
By the market. At listing, a SunSwap pool (Uniswap-style AMM) is seeded at ~25% above the final presale rate; from then on every trade moves the price. See the DEX page for exactly how that works.
From the community allocation (15M RBC), deposited into an on-chain reward reserve. The contract can only pay out what the reserve actually holds — it cannot print new tokens, because no mint function exists.
No. Stake and unstake at any time, no cooldown, no exit fee. Rewards accrue per second and can be claimed separately.
Your staked principal is always withdrawable — it's held 1:1 by the contract. Only new reward claims would pause until the reserve is topped up from the community bucket.
Yes, within a hard ceiling of 50% coded into the contract. Today the owner sets it (12% at launch); post-mainnet this becomes a governance vote.
Primary venue: SunSwap, Tron's Uniswap-style DEX, where the locked liquidity pool lives. DEX aggregators pick the pool up automatically. Bridged listings on Uniswap (Ethereum) or PancakeSwap (BNB Chain) and centralized exchanges come later as volume justifies — see the roadmap.
Three contract-level facts: the liquidity pool's LP tokens are time-locked for 12 months; team tokens sit behind a 12-month cliff; and the token has no mint function. Each is publicly verifiable on-chain — you don't have to trust anyone's word.
Possibly, for distribution and third-party badges — but every safety feature a launchpad enforces (escrowed funds, caps, liquidity lock, vesting) is already implemented in RBC's own contracts. See the comparison on the DEX page.
After Phase 2: a third-party audit, legal review with KYC/AML for the sale, and a funded treasury. The demo phase exists precisely so everything is proven before real money is involved.
Three layers: (1) the complete contract registry lists every address on every network with explorer links — balances, locks, sale totals are live on-chain data; (2) the full Solidity source is published on this site (EVM / Tron) and submitted to Sourcify for independent source-to-bytecode verification; (3) the mint itself is public — the single Transfer-from-zero event in each token's deployment transaction is the entire supply history, and no mint function exists afterwards.