Onchain ledger205.98 GLD delivered21,620 payouts1,559 wallets reachedRobinhood Chain · 4663Block 51,313,638

Golden Goose · Robinhood Chain

A memecoin
that lays GLD.

Every trade can feed the nest. This is the independent receipt book for every GLD allocation, every payout, and every wallet reached by $GG.

Did your wallet get the golden egg?

Direct RPC logsNo wallet connectionRead-only
GLD delivered205.98and counting
01226allocation epochs
021,559wallets reached

Indexed block
51,313,638

Hold $GGTrades pay feesFees settle in GLDEligible wallets receive GLD

The receipt book

The goose has been busy.

From epoch #0 to #225, these figures come from successful onchain payout events—not estimates, screenshots, or token balance guesses.

GLD delivered

205.98 GLDSuccessfully transferred to holder wallets

Reward rounds

226214 fully settled allocation rounds

Wallets reached

1,559Distinct addresses with at least one successful payout

Onchain payouts

21,6205m 55s median gap between epochs

Cumulative rewards

The growing
GLD stack.

Lifetime delivered205.984GLD
Launch · 28 AugEvery point is a completed payout epochLatest · 31 Aug, 23:54

Under the feathers

How a trade becomes
a golden egg.

Golden Goose uses a Pons V2 fee recipient that publishes holder allocations as Merkle epochs. The observed keeper then pushes GLD directly to recipient wallets in batches.

01

Trading

$GG trades against GLD on its Pons market. Quote-denominated fees accrue through the configured fee route.

02

Harvest

The Golden Goose distributor harvests GLD from the fee system. We have indexed every Harvested event.

03

Weight

Pons generates an epoch file. Its published policy says eligible balances are weighted by both size and holding time.

04

Delivery

A keeper submits batches. Successful claims transfer GLD straight to each listed wallet—sometimes immediately, sometimes in a later backfill run.

Not quite “everyone.” Pons publishes a 0.1%–4% holding band and holding-time weighting. The exact Merkle allocation is computed offchain, so this site shows published policy beside observed results.

Read the evidence and caveats
Observed backfill13 older rounds

On 30 August at 15:21 UTC, Pons returned to skipped epochs and delivered 2,767 payouts totalling 48.148552 GLD. The longest waited 32h 31m.

See the round-by-round proof →

Published eligibility

There is a
reward lane.

Ponsi says wallets holding between 0.1% and 4% of “supply” share dividends, with longer holds earning more. A literal fixed-supply translation is 1M–40M GG—but observed payouts prove the backend is not using that as a simple closing-balance cutoff.

Explore the holder board
Current literal fixed-supply band184 wallets
0Below floor1M GG0.1%40M GG4%100M+Above cap
5

Below 1MBelow the literal 0.1% line

1M–40MInside the literal headline band

Above 40MAbove the literal 4% line

Current balances are a diagnostic signal, not proof of a past epoch’s time-weighted eligibility. Epoch #0 alone paid 300 wallets whose replayed balance never reached 1M GG.

Fresh from the nest

Latest allocation epochs.

Allocated is the amount committed to an epoch. Paid is the sum of successful GLD transfers. ‘Not submitted’ and ‘partial delivery’ expose where Pons’ keeper still has work to do.

EpochCreated · UTCStatusGLD allocatedGLD paidGLD outstandingWallets paid / listedProof
#22531 Aug, 23:54settled0.358416 GLD0.358416 GLD0 GLD112 / 112View tx ↗
#22431 Aug, 23:52settled0.207808 GLD0.207808 GLD0 GLD75 / 75View tx ↗
#22331 Aug, 22:55not submitted2.145838 GLD0 GLD2.145838 GLD0 / 383View tx ↗
#22231 Aug, 21:55settled0.466717 GLD0.466717 GLD0 GLD141 / 141View tx ↗
#22131 Aug, 21:46settled0.40201 GLD0.40201 GLD0 GLD126 / 126View tx ↗
#22031 Aug, 21:36settled0.477851 GLD0.477851 GLD0 GLD140 / 140View tx ↗
#21931 Aug, 21:21not submitted0.570999 GLD0 GLD0.570999 GLD0 / 161View tx ↗
#21831 Aug, 21:16settled0.936725 GLD0.936725 GLD0 GLD222 / 222View tx ↗

Your turn

Where are
your eggs?

Paste any address for its complete GLD payout history, round-by-round GG balance signals, streaks, and a plain-English explanation of likely misses.

No connection. No signature. Just public chain data.