Most people who stake GGBR for the first time ask the same question within a week. Why hasn't my balance gone up?
Most people who stake GGBR for the first time ask the same question within a week.
Why hasn't my balance gone up?
It is the right question, and the answer is the whole design.
Your stGGBR balance is supposed to stay the same. The yield does not arrive as new tokens appearing in your wallet. It arrives as each token you already hold becoming redeemable for more GGBR than it was yesterday.
This guide explains that mechanic in full: what stGGBR is, why a fixed balance is a feature rather than a bug, what the ERC-4626 vault standard actually does, and most importantly how to check every claim on this page yourself, on-chain, without taking our word for any of it.
If you only read that, you have the shape of it. The rest is detail.
There are two ways to pay someone a return on a token, and the blockchain industry uses both.
The first is to send them more tokens. Your balance grows. It is immediately legible: you open your wallet, the number is bigger, you understand that you earned something.
This is called a rebasing design.
The second is to leave the balance alone and change what it is worth.
You hold the same number of shares in a pool, and the pool gets bigger.
This is non-rebasing, and it is what stGGBR does.
Here is the mechanic, and it is genuinely one line of arithmetic:
Exchange rate = total GGBR in the vault ÷ total stGGBR in existence
Think of stGGBR as a cloakroom ticket that says:
"You own this fraction of everything in the room."
The number of tickets you hold never changes on its own. What changes is how much is in the room.
Crucially, deposits and withdrawals do not move the rate. When someone deposits GGBR they receive newly issued stGGBR in proportion, so both sides of that division grow together and the ratio holds.
The rate only moves when GGBR is added to the vault without any new stGGBR being issued against it.
That is the injection, and it is the entire yield mechanism.
This is the part you can check.
The vault publishes its own exchange-rate history, and across 91 daily observations from 20 May to 21 August 2026 there are 34 consecutive day-pairs where the total stGGBR supply is byte-for-byte identical and the exchange rate is higher.
For example:
| Date | Total stGGBR supply | Exchange rate |
|---|---|---|
| 6 June 2026 | 13,097.9286 | 1.004943008 |
| 7 June 2026 | 13,097.9286 (unchanged) |
Nobody received a single new token on that day. Everybody's position gained value.
That is non-rebasing accrual, demonstrated rather than asserted.
Over the full window the rate moved from 1.000274 to 1.025817, a rise of about 2.55% in 93 days, and it never once went backwards.
It is tempting to multiply 2.55% over 93 days out to a yearly figure, and you will see that done.
Treat any such number as a projection rather than a measurement.
It assumes the same daily pace continues for a full year, which is an assumption about the future rather than an observation about the past.
The realised figure and its window are the honest statement.
Current target rates for each pool are published on the staking page.
This matters more than almost anything else on this page, and it is where the most expensive misunderstandings happen.
What accrues is a claim on more gold.
Not dollars.
If the vault's rate rises 2.55%, you can redeem for 2.55% more GGBR than you could before, and GGBR tracks the gold price.
Your ounce count goes up.
What the gold is worth in dollars is a separate question entirely, and the vault has no opinion on it.
If gold falls 10% while your rate rises 2.55%, the dollar value of your position falls. The yield cushions that move. It does not cancel it, and it does not protect you from it.
You are still holding a long gold position, with all the price exposure that implies.
This is the same trade-off anyone holding physical gold accepts, with one difference: your ounce count is growing rather than shrinking from storage costs.
A gold-denominated return and a dollar-denominated return are not the same product, and any comparison that treats them as interchangeable is comparing the wrong things.
ERC-4626 is a shared vocabulary for vaults.
Before it existed, every yield vault invented its own function names, so every integration was bespoke work.
The standard fixed that by agreeing on a common set of calls:
The practical consequence is that any wallet, dashboard, lending market or aggregator that understands ERC-4626 can read the vault without custom code.
That is the entire pitch, and it is a real one.
stGGBR has 24 decimals against an 18-decimal asset.
That looks like a typo and is not.
It is a mitigation for a known attack on vault share pricing, where someone deposits a tiny amount into a nearly empty vault, then donates assets directly to inflate the share price so the next depositor's shares round down to nothing.
The standard defence is to add virtual shares to the arithmetic.
The widely used default offset is zero, which gives only minimal protection.
stGGBR uses an offset of six, which is where the extra decimals come from, and which makes that attack orders of magnitude more expensive to attempt.
Most vaults inherit the default and never revisit it.
This one did.
Withdrawals are asynchronous.
Deposits happen immediately. Exits do not.
You call a request function, the amount is fixed at that moment, and after a notice period you claim.
The vault currently sets that period at seven days, with a contract-level maximum of thirty.
While your withdrawal is queued it is no longer earning, because the vault's asset total explicitly excludes assets earmarked for pending withdrawals.
Exiting holders stop accruing rather than diluting the people still in.
That asynchronous design is common for vaults whose underlying assets are deployed off-chain, and there is a newer standard, ERC-7540, written specifically to describe it.
It names real-world-asset protocols and liquid staking tokens as its intended cases.
The honest description of stGGBR is therefore an ERC-4626 vault interface with an asynchronous withdrawal path, not a fully synchronous ERC-4626 vault.
The difference matters for integrations.
New to liquid staking tokens?
Nothing in this section changes anything above, so skip to the section on where the yield comes from, further down.
The mental model transfers almost exactly, with one common trip-up.
stETH rebases.
wstETH, sDAI and sUSDe do not.
If your reference point is stETH, you are thinking of the wrong half of Lido's product.
stGGBR belongs with the wstETH, sDAI and sUSDe family:
fixed balance, rising exchange rate, value read from a conversion function rather than balanceOf.
Worth knowing that stETH is internally a share token too.
Its balance is computed as your shares multiplied by a pooled total.
Rebasing is not a different accounting model, it is the same share model with the display inverted.
stETH shows you shares times rate.
A vault shows you shares, and makes you look up the rate.
Where stGGBR genuinely differs from an ETH liquid staking token, and these are the questions worth asking:
None of those is hidden, and a reader who has been through 2022 will want them stated plainly rather than discovered later.
The last two rows in particular are the ones to size a position against.
Gold generates no income on its own.
A bar in a vault pays no interest, no dividend and no rent, and it costs money to store.
So any return on gold is being paid by somebody, for a reason, and the useful question is never:
"What is the APR?"
It is:
"Who pays this, and what would make it stop?"
For StakeMyGold, the reserves are deployed through over-collateralised institutional lending and repo financing, arranged via a named counterparty, I-ON Digital Corp.
It is a credit-based model: a named party pays for the use of capital.
The yield reaching the vault is paid in GGBR, drawn from a pre-funded reserve, which is what allows a defined rate to be offered against a variable source.
The rate does not have to be earned in real time in order to be paid.
We are not going to re-argue that here, because we have already written it out properly, including the parts that are not flattering.
The full breakdown of every legitimate source of gold yield, who pays it and what breaks it, is in Gold Staking Explained: How to Actually Earn Yield on Tokenized Gold, and the mechanism itself is set out on our yield strategy page.
Here is the thesis behind issuing a receipt token at all, rather than simply locking deposits for a term.
A locked position is inert.
It earns its rate and does nothing else.
A transferable receipt token that appreciates against its underlying can, in principle, do several jobs at once:
The economic argument for a liquid staking token is that liquidity and yield stop being a trade-off.
That is the design goal.
It is not a description of what you can do with stGGBR today, and we are going to be precise about the difference.
Pendle and Morpho are soon to be on our roadmap.
Not imminent, not live, not available.
It is worth understanding what integration on venues like those actually requires, because it is more demanding than a listing request.
Any venue that may need to unwind a position, such as a lending market liquidating collateral or a yield tokenisation protocol wrapping the asset, has to be able to exit it programmatically.
An asynchronous request-and-claim queue does not satisfy that, which is why the ERC-7540 work described earlier is a prerequisite rather than an optimisation.
An appreciating share token has to be priced off its conversion rate rather than a market quote, and that feed has to be manipulation-resistant and monotonic.
Risk reviewers on major venues test for exactly this.
Liquidation only works if someone can actually sell the collateral.
Supply caps on serious venues are sized off measured market depth rather than market capitalisation, so a large token with thin liquidity gets a small cap or none at all.
Multi-signature control, and no unresolved critical or high audit findings.
When those integrations are live, they will be announced as live.
Until then they are plans, and you should size your expectations accordingly.
This is the section that matters most, because the alternative to trusting a dashboard is not trusting a nicer dashboard.
It is reading the contract.
Get the stGGBR contract address from the stGGBR product page or the footer of this site, and always copy it from an official source rather than from search results or a message.
Then, in any block explorer's read-contract view:
One thing that will confuse you if nobody warns you.
Dividing totalAssets() by totalSupply() will not exactly match exchangeRate().
That is not an error and nothing is missing.
totalSupply() still includes shares that holders have queued for withdrawal, while totalAssets() already excludes the GGBR earmarked to pay them.
The two reconcile precisely once you account for the pending queue.
Use exchangeRate() or convertToAssets() for the redemption rate, because those are the values the vault actually settles on.
While you are there, the fee arithmetic is checkable too.
The performance fee is taken from each injection before it reaches the vault, and the difference between gross and net yield reconciles to the fee recipient's balance exactly.
No hedging, and no words we cannot support.
There is no guarantee, no insurance and no protection on principal here.
There are specific, checkable mitigations, and specific, real risks.
This is the main one.
The yield comes from lending against reserves, so the primary risk is a counterparty failing to perform, independently of the gold price.
The yield side is pre-funded from a reserve wallet.
The principal remains exposed to counterparty performance, as it is in any credit-based product.
In-situ reserves are not vaulted bullion.
That is a different risk profile, not a marketing distinction, and it belongs in your assessment.
The vault contract is immutable and its source is verified and public.
It has been audited by CertiK, and there is an ongoing bug bounty programme run through CertiK's platform, with details on the security page.
An audit is a point-in-time review of the code it was given.
It reduces risk.
It does not remove it, and it says nothing about whether reserves exist.
The operator can adjust:
Our product page states this directly, and you should read it as a real feature of the product rather than boilerplate.
A target rate set by an operator is a policy, not a contractual obligation enforceable by you.
There is no secondary market for stGGBR.
The withdrawal queue is the exit, and the underlying GGBR's on-chain market is thin.
Check depth before sizing a position.
Depositing, requesting and claiming are all Ethereum transactions, and fees spike when the network is busy.
This does not touch your principal but it can make small positions uneconomic.
Rules for yield-bearing tokenized assets are still developing in several major jurisdictions and could change while you hold.
Connect a wallet on the staking page and choose the liquid pool.
There is no account to create.
If your GGBR balance does not show in your wallet, you may need to add the token manually, and the steps are on getting started.
If you hold PAXG or XAUT rather than GGBR, note that neither is a staking asset on StakeMyGold today.
Direct PAXG and XAUT staking is on the roadmap.
The path today is to convert to GGBR first, then stake.
Three steps, and the middle one is the one people forget:
If you need same-day access to the underlying, this is the wrong product, and you should know that before you deposit rather than after.
It is the receipt token you get when you stake GGBR in the liquid vault.
It represents your share of the vault's total GGBR, and it becomes redeemable for more GGBR over time.
Because it is not meant to.
Yield accrues through the vault's exchange rate, not by new tokens being sent to you.
Call convertToAssets() on your balance to see what your position is currently worth in GGBR.
No.
Rebasing tokens grow your balance.
stGGBR keeps the balance fixed and increases what each unit is worth.
In that respect it behaves like wstETH, sDAI or sUSDe rather than like stETH.
No.
GGBR is the gold-backed asset.
stGGBR is a claim on a pool of GGBR that grows.
One stGGBR is worth more than one GGBR, and the gap widens as yield accrues.
GGBR is injected into the vault without new stGGBR being issued against it, so the same number of shares divides a larger pool.
There is no fixed term, but exits are not instant.
You request a withdrawal on-chain and claim it after a notice period, currently seven days.
You do not earn during that window.
A shared set of function names for yield vaults, so that any wallet or protocol can read and use one without custom code.
It is a compatibility standard.
It is not a safety rating, and it says nothing about whether a vault's assets are sound.
You hold a claim on a pool of GGBR, which is itself a claim on gold reserves.
Once assets are deposited, you hold a claim on the platform rather than segregated metal.
That is true of any staking product, and it is why the counterparty question matters more than the headline rate.
The exchange rate keeps accruing on its own schedule regardless of price.
But your position is denominated in gold, so if gold falls the dollar value of your holding falls too.
The accrued gold cushions the move, it does not offset it.
Not yet.
That is the design goal of issuing a transferable receipt token, and lending market integrations are on the roadmap, but there is no live integration today and the prerequisites are described above.
Term staking locks your GGBR for a set period at a rate written into your position when you deposit.
Liquid staking issues you a transferable receipt with no fixed end date, at a floating target rate, with a withdrawal notice period instead of a lock.
Current terms for both are on the staking page.
Not yet on StakeMyGold.
GGBR is live today, and PAXG and XAUT staking is on the roadmap.
The route today is to convert to GGBR and stake that.
No.
There is a pre-funded yield reserve, which covers the yield rather than the principal, along with audited contracts and a bug bounty.
We would rather say that plainly than imply cover that does not exist.
A liquid staking token for gold is a simple idea with a fiddly surface.
The idea: hold a transferable receipt, let the yield accrue into its redemption value, keep the position usable elsewhere.
The fiddly surface: a balance that never moves, an exchange rate you have to look up, an exit that runs through a queue, and a yield that comes from a credit arrangement rather than from the metal.
The one thing we would ask you to take from this page is the habit rather than the number.
Do not take an exchange rate from a dashboard, including ours.
Call exchangeRate() yourself.
Check withdrawalDelay() before you deposit rather than after.
Compare totalAssets() against totalSupply() and understand why they do not divide cleanly.
A product whose mechanics survive that kind of inspection is worth more of your attention than one with a larger headline rate.
This article is for informational purposes only and is not financial advice.
asset(), totalAssets(), totalSupply(), exchangeRate(), convertToAssets(), withdrawalDelay(), performanceFeeBps(), totalYieldDeposited()| 1.005218335 (higher) |
| Category | ETH liquid staking (e.g. wstETH) | stGGBR |
|---|
| Where the yield originates | Protocol issuance for securing the network | An off-chain credit arrangement |
| What sets the rate | Emergent from validator rewards | A target rate, funded by injection, adjustable by the operator |
| What backs the asset | ETH | GGBR, backed by in-situ gold reserves |
| Principal risk | Validator slashing | Counterparty and credit risk |
| Exit path | Redemption plus deep secondary markets | On-chain request, then claim after a notice period |
| Secondary market | Deep and long-established | None for stGGBR today |
| Status | Current situation |
|---|
| Vault | Working, verifiable, immutable vault |
| Deposits | Open |
| Withdrawals | Processing |
| Accrual history | Documented |
| Secondary market | Does not exist today |
| Lending market integration | Not live |
| DEX integration | Not live |
| Aggregator integration | Not live |
| Pendle | Roadmap |
| Morpho | Roadmap |
| What You Want to Know | Call This |
|---|
| What asset is in the vault | asset() |
| How much GGBR the vault holds | totalAssets() |
| How much stGGBR exists | totalSupply() |
| The current redemption rate | exchangeRate() or convertToAssets() |
| What your own holding is worth | convertToAssets(your balance) |
| The withdrawal notice period | withdrawalDelay(), in seconds |
| The performance fee | performanceFeeBps(), in basis points |
| Cumulative yield paid into the vault | totalYieldDeposited() |