Onchain ledger209.06 GLD delivered22,419 payouts1,577 wallets reachedAuto-indexed every 10 minRobinhood Chain · 4663Block 51,358,097

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.

01

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.

02

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.

03

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.

04

Replay GG transfers

Token Transfer logs reconstruct present balances and per-wallet balance paths. Protocol addresses are excluded from holder rankings.

05

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.

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’.

Golden Goose developer

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 ↗
Pons operations

Controls publication and routine delivery.

Only the configured Pons publisher can commit a new Merkle epoch. The same Pons address is the observed keeper submitting 100-recipient claim pages. If that offchain service pauses or skips a page, automatic holder delivery pauses too.

That operational dependency—not an empty allocation—is what the current backlog exposes.
Contracts and timelocks

Not immutable, but not an instant dev switch.

Anyone can harvest and submit a valid claim once its proof is available. However, the distributor implementation can 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.

So holders can independently finish proof-backed claims; they cannot publish missing epochs or restore epoch #48’s absent proof file.

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.

RoleAddressWhy it matters
Golden Goose token0xcacb0e9c…cb68 Fixed-supply PonsV2LauncherToken
GLD reward token0xc9a981fe…fc4e SPDR Gold Trust Stock Token
GG distributor0x44db4ecd…5ed7 Harvests, commits epochs and pays claims
Pons V2 factory0x7ed598bc…ec7e Stores GG’s live launch configuration and fee recipient
GG bonding curve0x52956293…0079 Launch-phase GG / GLD market
Fee escrow0xd3afeb2a…ac9e Pons quote-fee escrow
V4 hook0xe5e70264…e044 Post-graduation Pons hook
V4 pool manager0x8366a39c…0951 Graduated pool infrastructure
Pons factory owner0x263ed295…19Dd Recipient-override authority at the indexed block
Distributor factory0x70e95cc5…1507 Controls publisher and creates beacon-proxy distributors
Distributor factory owner0xFdDE5a1E…CC36 Current operational admin; ownership transfer is pending
Pending factory owner0x0f963968…6514 Two-day TimelockController; already owns the beacon
Epoch publisher / keeper0xe1F7f5A4…EcE7 Only observed publisher and source of keeper batches
Distributor beacon0xa125492a…fa09 Selects the distributor implementation
Distributor implementation0xf70c5b3a…8a8a Implementation selected at the indexed block

Epistemic status

Known, stated, inferred.

Onchain fact

Exact payout history

Recipient, GLD amount, epoch, time, block and transaction are decoded directly from successful contract events.

Onchain fact

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.

Publisher statement

0.1%–4% eligibility

Ponsi states this band and balance × holding-time weighting, but does not define “supply” there. Epoch #0 paid 300 wallets that never reached 0.1% of fixed total supply.

Analytical signal

Why a wallet missed

Balance paths can show likely causes, but the Merkle root has no reason code. “Likely” diagnoses are intentionally labelled as such.

Important nuance

“Locked routing” needs a narrower reading.

Ponsi says a launch’s custom route configuration is fixed. 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. Neither fact proves misuse; both mean “the percentages are configured” should not be expanded into “no relevant code, publisher or recipient can ever change.”