Scan from GG’s launch block
The historical ledger starts at block 48,709,296. A persistent worker then checks only new GG and distributor logs every 10 minutes through a 20-block confirmation buffer.
Show your work
Receipts,
not vibes.
What the dashboard knows, how it knows it, and where certainty ends. Every headline number can be traced back to public Robinhood Chain data.
Decode protocol events
Epoch events supply root, GLD total, deadline and URI. Claimed events supply epoch, recipient and exact amount. Harvested events expose fee collection.
Reconcile epoch totals
“Allocated” is the onchain epoch total. “Paid” is the sum of successful claims for that epoch. Their difference remains pending or requires investigation.
Replay GG transfers
Token Transfer logs reconstruct present balances and per-wallet balance paths. We compare closing and block-weighted balances with each root-verified allocation; known protocol addresses are separated from ordinary holders.
Validate Merkle metadata
Where available, the URI document is accepted only when its root matches the root committed onchain. Proof arrays are discarded from the analytics snapshot.
Test the payout-cutoff hypothesis
For every verified file we measure its smallest account amount. Across recent adjacent epochs we also test whether the smaller recipient set is an exact subset of the larger one, then correlate list size with both GLD pot size and block-window length.
Who controls delivery?
Configured by the dev. Operated by Pons.
Golden Goose’s developer chose this system, but pons operates it. The current authority graph is more nuanced than either ‘the dev controls it’ or ‘it can never change’.
Cannot currently redirect the fees.
The launcher created the GG distributor, then voluntarily transferred GG’s creator-fee recipient to it on 29 August. The original developer is no longer the current recipient, so the creator-only transfer path now rejects that wallet.
Verify the transfer transaction ↗Controls publication and routine delivery.
Only the configured pons publisher can commit a new Merkle epoch. Its offchain allocator chooses the account list and has used three distinct effective payout-floor regimes. The same pons address is the observed keeper submitting batches of up to 100 recipients. If that service pauses or skips a batch, routine holder delivery pauses too.
That operational dependency—not an empty allocation—is what the current backlog exposes.Not immutable, but not an instant dev switch.
Chain simulations show that any sender can call the distributor with a valid, public proof. The implementation can also be upgraded through a two-day timelock, and the pons V2 owner can override GG’s fee recipient through a separate three-day timelock and three-day execution window.
A user would still need the proof, correctly encoded calldata, gas and an unexpired epoch. Holders cannot publish epochs or recover proofs pons keeps private. Epoch #48 showed that distinction when the keeper cleared it while its public URI remained unavailable.Contract registry
The live address book.
Every address is lowercase-normalized in the index. Follow the explorer link to inspect code, storage and transaction history.
| Role | Address | Why it matters |
|---|---|---|
| Golden Goose token | 0xcacb0e9c…cb68 | Fixed-supply PonsV2LauncherToken |
| GLD reward token | 0xc9a981fe…fc4e | SPDR Gold Trust Stock Token |
| GG distributor | 0x44db4ecd…5ed7 | Harvests, commits epochs and pays claims |
| Pons V2 factory | 0x7ed598bc…ec7e | Stores GG’s live launch configuration and fee recipient |
| GG bonding curve | 0x52956293…0079 | Launch-phase GG / GLD market |
| Fee escrow | 0xd3afeb2a…ac9e | Pons quote-fee escrow |
| V4 hook | 0xe5e70264…e044 | Post-graduation Pons hook |
| V4 pool manager | 0x8366a39c…0951 | Graduated pool infrastructure |
| Pons factory owner | 0x263ed295…19Dd | Recipient-override authority at the indexed block |
| Distributor factory | 0x70e95cc5…1507 | Controls publisher and creates beacon-proxy distributors |
| Distributor factory owner | 0xFdDE5a1E…CC36 | Current operational admin; ownership transfer is pending |
| Pending factory owner | 0x0f963968…6514 | Two-day TimelockController; already owns the beacon |
| Epoch publisher / keeper | 0xe1F7f5A4…EcE7 | Only observed publisher and sender of keeper batches |
| Distributor beacon | 0xa125492a…fa09 | Selects the distributor implementation |
| Distributor implementation | 0xf70c5b3a…8a8a | Implementation selected at the indexed block |
Epistemic status
Known, stated, inferred.
Exact payout history
Recipient, GLD amount, epoch, time, block and transaction are decoded directly from successful contract events.
GG’s launch settings
GLD pair token, distributor recipient, 1% creator tax, disabled buyback vault, fixed supply and graduated phase are readable from deployed contracts.
Fees route to GG holders
The official Golden Goose page makes that general statement. Chain history shows keeper-submitted batches. The correct pons sources publish no numerical threshold or complete selection formula; the earlier 0.1%–4% citation came from an unrelated domain.
Effective payout floor
Verified rewards since epoch #106 bottom out near 0.00105 GLD. Pot size has a 94.2% correlation with recent list counts, and 97.7% of adjacent list pairs are exact nested sets. The root has no reason code, so wallet diagnoses remain labelled likely.
Important nuance
The current route is not immutable.
At the indexed block, GG’s recorded recipient still points to the same distributor and there is no pending recipient change. However, the live pons V2 factory exposes an owner-controlled recipient override with a three-day timelock and three-day execution window.
Separately, the distributor is an EIP-1967 beacon proxy. Its beacon is already owned by a two-day TimelockController, while the distributor factory’s ownership transfer to that same timelock remains pending. The offchain account-selection settings are not fixed by the distributor at all: Golden Goose has already moved through effective floors near 0.005, 0.00035 and 0.00105 GLD. Published roots are fixed; future recipient lists remain an operational pons choice.
Primary reading
Sources.
- 01Robinhood Chain · ConnectingChain ID, official RPC and infrastructure providers ↗
- 02Robinhood · Stock token APIsCanonical asset model and token disclosures ↗
- 03pons launchpad contractsV2 curve, token, factory and graduation source ↗
- 04Official Golden Goose pagePublisher’s current holder-routing statement ↗
- 05pons V2 docsCurrent launch and fee-system documentation ↗
- 06GLD asset registryCanonical Robinhood Chain GLD address ↗
GLD is not a bar of gold.
Robinhood’s stock tokens provide tokenized economic exposure through a debt instrument; they do not confer direct ownership, shareholder or beneficial-owner rights in the underlying ETF. This site reports token units, not fiat value, yield, or investment performance. Nothing here is financial advice.