Documentation

Reserve Holdings (RHOLD) is a fixed-supply token sitting on a growing reserve of tokenized real stocks — Circle, NVIDIA, SanDisk, Micron and AMD today, with more added as holders vote them in. Every trade against its PancakeSwap pool leaves behind a small fee, and that fee is what's meant to fund buying more stock into the reserve. Nothing is paid out to holders along the way — value sits in the reserve itself, and any holder can claim their pro-rata share of it at any time, simply by burning their tokens.

The one idea behind all of it: a token's price can fall to zero. A redeemable claim on a reserve of real, checkable stock can't — for as long as that reserve holds something and redemption stays open to everyone. That's what RHOLD is built to be.

One thing worth reading before anything else on this page: the token is currently upgradeable, and that control hasn't been given up yet. See Trust model near the bottom for what that means in plain terms — everything else here describes what the contract does today, not a permanent guarantee.

RHOLD is a plain BEP-20 with its supply fixed at 1,000,000,000, set once, at launch, and never since. There's no way to mint more — the only thing that can happen to supply from here is it shrinking, when someone redeems and their tokens get burned. Fewer tokens against the same or a bigger reserve means everyone left is holding a bigger slice of it.

RHOLD trades on a single PancakeSwap V3 pool, and that pool was funded entirely by the token contract itself at launch — not a deployer wallet, not a locker service, and not through a transferable NFT position someone could later pull. Liquidity, and attention, stay in one place.

RHOLD doesn't charge a tax on transfers. That's not actually possible on the kind of pool it trades on — the pool demands the full amount on every swap, no exceptions. What funds the reserve instead is simpler: the ordinary swap fee every trade already pays into the pool. RHOLD's own contract is built to collect that fee itself, automatically, in BNB, on every trade, with no manual step in between.

A second fee is planned on top of that: a small protocol fee, taken in BNB by a swap hook and routed straight to the reserve. It hasn't shipped yet. This page will say so the moment it does — the same way it's saying plainly now that it hasn't.

bStocks the reserve acquires are held directly at RHOLD's own contract address — there's no separate vault contract standing in between holding them on the token's behalf. That means anyone can check exactly what's held, and how much, on BscScan's Tokens tab for that address, any time, instead of trusting a number someone quotes them.

Fee in, bStocks out — the same one address the whole way through.

The BNB collected from swap fees is what's meant to fund buying bStocks into the reserve — that's the design. This exact pipeline was directly observed running on the project's prior deployment, with bStocks and the WBNB that funded them arriving at the treasury from the same address. We'll confirm the same thing here, cited against this contract's own transfer history, as soon as it's observable.

Anyone holding RHOLD can call burn() on their own balance, any time — no approval needed, no permission to ask for, no waiting period. In the same transaction, the contract sends back a pro-rata share of everything the treasury holds: every bStock it's sitting on, split by exactly your share of total supply at that moment.

This isn't a hypothetical: the same burn-to-redeem mechanism was directly observed working on the project's prior deployment — a holder redeemed RHOLD and received bStocks back, pro-rata, in the same transaction. This site's Redeem button calls that same function on the current contract; we'll cite a fresh redeem transaction for this address as soon as one's observable, same as everywhere else on this page.

This site's Redeem button is one way to call it, connecting your wallet here — but it's not the only way. Because burn() is a plain public function on the token contract, it can be called directly from BscScan's own "Write Contract" tab for the token, connecting a wallet there instead, with no dependency on this website at all.

One thing that transaction doesn't settle: the precise rounding behavior of the contract's own math. The site's "you will receive" preview is a simple client-side estimate — your balance's share of supply, times current holdings — not a call into the contract itself, so treat it as an estimate, not a guaranteed quote.

A price can fall to zero. A redeemable claim on a reserve of real stock can't — as long as that reserve holds something, and redemption stays open to everyone. If RHOLD ever traded below the value of what it can actually be redeemed for, buying it and redeeming immediately would be risk-free profit — exactly the kind of gap markets tend to close on their own.

That's arbitrage doing its job: anyone who spots RHOLD trading under the treasury's per-token backing has an incentive to buy and redeem until the price is pushed back up to that level. The floor isn't enforced by a promise — it's enforced by whoever notices the gap first and profits from closing it, which tends to keep the market price sitting at or above what the treasury actually backs each token with.

Two things keep that logic honest, worth saying plainly rather than skipping past. Redemption only ever pays out whatever the treasury actually holds at that moment — thin on a given bStock means your share of that one is thin too, and you can check current holdings before you redeem (see The treasury above). And the whole argument assumes the contract keeps working the way it works today — see Trust model below for why that's a real qualifier here, not boilerplate.

Any wallet holding at least 100,000 RHOLD can cast a non-binding, on-chain vote for which blue-chip stock the reserve should prioritize once Binance issues a bStock for it. Voting reads your balance at the moment you vote — nothing gets staked or locked, and you keep full control of your tokens the whole time.

It's a signal, not an instruction: the voting contract can't touch RHOLD, the pool, or the treasury. All it does is read a balance to decide who's eligible, and record what they voted for.

• Liquidity is designed to live at the token contract's own address, not a wallet or a transferable NFT — that was directly confirmed on the project's prior deployment; pending the same confirmation for this contract's own launch.
• Fee collection into the treasury is designed to be automatic and on-chain, with no manual step and no separate wallet handling it — confirmed working this way on the prior deployment; pending the same confirmation here.
• Redemption is open to anyone, any time, by design — already proven working on the prior deployment; pending a fresh redeem transaction cited against this contract.
• Whether this contract is upgradeable — like the project's prior deployment was, with upgrade control not yet renounced there — hasn't been confirmed here yet. This is the single most important open question on this page right now, and it'll be answered plainly the moment it's checked.
• Not yet independently confirmed: whether an owner has any path to withdraw the pool's underlying liquidity (as opposed to just the fees it earns), and whether a mint function exists anywhere in the contract. The source hasn't been reviewed line-by-line here, so no stronger claim than that is made.
• No third-party security audit yet, and no legal review of securities classification. Every claim on this page is checked against a cited on-chain transaction where one is cited — not a completed audit.
• One layer of custodial trust further out: bStocks are ultimately backed by Binance/BTech Holdings' Abu Dhabi SPV custody, tracked via Binance's Proof of Collateral. That's verifiable, not trustless.

For anyone who wants to check any of this directly rather than take the page's word for it:

• RHOLD token: 0x9b0c5e8C457D2420899712FD698fc333E08D4B7D
• Governance vote contract: 0x3daa17ceFB41F76aabD2F45034433A8996147506

Prices shown on this site come from DexScreener, with the PancakeSwap pool itself as a fallback.

Do I earn dividends? No — value sits in the reserve instead of getting paid out. You realize it by redeeming or selling.

Are these real shares? They're Binance-issued tokenized stocks (bStocks) — real underlying exposure via custody, not brokerage shares, and they carry no voting rights or dividends of their own.

What if everyone redeems at once? The reserve unwinds pro-rata, in whatever order people redeem in — whatever's left keeps backing whoever hasn't redeemed yet. That's an orderly exit, not a failure mode, assuming the contract keeps working as described (see Trust model above).

Can the team run off with the reserve? Not through any path confirmed so far — bStocks sit at the token's own contract address, not a separate wallet the team controls, and redemption requires nobody's permission. Whether this contract is upgradeable, and if so whether that control has been given up, is the open question tracked in Trust model above — check there for the current answer rather than assuming either way.

Is this audited? Not yet, by a third party — see Trust model above.

What changes once the protocol fee ships? More BNB flows into the treasury per trade, on top of what the pool fee already collects on its own — see The fee above.

• Whether this contract is upgradeable, and the status of upgrade control if so, hasn't been independently confirmed yet for this deployment — see Trust model above.
• Custodial trust one layer up: bStocks are backed by Binance/BTech Holdings' custody, verifiable via Proof of Collateral, not trustless.
• Individual bStock liquidity on PancakeSwap can be thin, especially for newly issued ones — large trades can move price regardless of what's described above.
• Not community-governed beyond the non-binding vote described above.
• This page is informational only, not financial or legal advice, and nothing here is an offer to sell securities.