EPOCH Robinhood Chain Chain ID 4663 Epoch - next settlement --:--:--
Mechanism // full specification

How settlement actually works.

This page is the complete rule set: what an epoch is, where revenue comes from, how each wallet's settlement is computed, what disqualifies a wallet, and how to verify every step yourself on-chain. If the site and the chain ever disagree, the chain is right.

The clock

An epoch is one hour. The clock is public.

Epochs close at the top of every UTC hour: 24 settlements per day, every day. The epoch number is not something we assign: it is floor(unix time / 3,600), the number of hours since 1970. Anyone with a clock can compute the current epoch and the next settlement time without trusting this site.

00:0006:0012:0018:0024:00 UTC

One day, 24 epochs. The blue line is now (--:-- UTC). Every boundary is a settlement.

01 / Collect

Where the revenue comes from.

EPOCH launches through Pons with a fixed supply. Trading begins on a bonding curve; at graduation, liquidity is deployed into a Uniswap v4 pool and permanently locked. Nobody - including the team and including Pons - can withdraw it.

Settlement begins at migration. During the bonding-curve phase there is no pool and no swap-fee revenue, so pre-migration epochs are simply not settled. The first settled epoch is the first full epoch after liquidity locks.

From graduation onward, every swap in that pool pays a trading fee. A creator share of those fees is claimable by the treasury wallet, denominated in WETH and in EPOCH. That claimable share is the protocol's entire revenue. There is no other source: no emissions, no inflation, no staking pool, no external yield.

At each epoch close, the treasury claims accrued fees. The claim is an ordinary transaction, visible on Blockscout like everything else here.

The creator fee share is a Pons parameter, not ours. The current figure is published in the Pons documentation; if Pons changes it, protocol revenue changes with it, and this page will be updated to match.

02 / Settle

How each wallet's settlement is computed.

At the closing block of each epoch, the distributor takes a snapshot of every EPOCH balance, reconstructed from the token's full Transfer history. Three filters apply, in order.

First, structural addresses are removed: the liquidity pool, the treasury, the distributor, and the dead address. These hold tokens but are not holders, and paying them would recycle revenue into infrastructure.

Second, wallets below the minimum position of 50,000 EPOCH are removed. The floor exists because pushing ETH to a wallet costs gas, and below a certain position the gas exceeds the settlement.

Third, what remains is the eligible supply. Each eligible wallet's settlement is:

settlementpool × ( wallet balance ÷ eligible supply )
poolepoch revenue × 50%
weightingbalance at the closing block

Payment is pushed as ETH in batches directly to each wallet. No claim transaction exists, no gas is spent by the recipient, and no interaction with any contract is ever required to be paid. A wallet that cannot receive ETH (a contract without a receive function) is skipped, and skipped amounts roll into the next epoch, as does sub-wei rounding dust.

Because sub-minimum wallets are excluded from the denominator, actual settlements run above the simple estimate on the front page, which divides by total supply. The worked example below shows the difference.

Worked exampleIllustrative figures
Daily volume (assumed)$500,000
Daily fee revenue at 5% effective capture$25,000
Revenue per epoch (1/24 day)$1,041.67
Holder pool per epoch (50%)$520.83
Your position1,000,000 EPOCH
Eligible supply (after exclusions and floor)620,000,000 EPOCH
Your share of eligible supply0.1613%
Your settlement, per epoch$0.84
Your settlement, per day (24 epochs)$20.16

The front-page estimator, dividing by total supply, would show $12.50 per day for the same position and volume. The difference is the excluded supply. Both numbers move constantly with volume and with the holder set; neither is a promise.

03 / Retire

Supply only moves down.

A tenth of each epoch's revenue is used to retire supply: EPOCH is acquired and sent to the dead address, 0x...dEaD, where no key exists and no transaction can ever move it again. Because fee revenue arrives partly denominated in EPOCH, the token-denominated portion can be retired directly, without a market purchase.

Supply is fixed at launch. There is no mint function, no emissions schedule, and no mechanism by which supply can increase. Retirement is cumulative and one-directional, and the dead address balance is publicly readable at any time.

Eligibility & edge cases

The rules, including the awkward ones.

Self-custody is required.

If EPOCH is held on an exchange, the exchange's wallet holds the balance - and exchange wallets are on the structural exclusion list, so nobody is settled for those tokens. Settlement reaches wallets whose keys you hold. There are no exceptions to this, because at the token level there is no way to see through a custodian.

Splitting wallets changes nothing.

Settlement is linear in balance. Ten wallets of 100,000 EPOCH are settled exactly the same total as one wallet of 1,000,000 - unless a split drops any wallet below the 50,000 minimum, in which case that wallet's share is forfeited to everyone else.

Timing matters, and the rule is stated, not hidden.

Weighting uses the balance at the closing block. A position opened late in an epoch is settled in full for that epoch; a position closed before the boundary is settled nothing. If the weighting rule ever changes - for example to average balance across the epoch - the change will be announced ahead of a stated epoch number and reflected on this page before it takes effect.

Contracts that can't receive ETH are skipped.

A contract wallet without a payable receive function will reject the transfer. The batch does not fail; that recipient is skipped, the event is logged, and the amount rolls into the next epoch's pool.

The minimum is a gas floor, not a gate.

50,000 EPOCH exists so that no settlement costs more to deliver than it is worth. It is not a tier system; above the floor, every wallet is treated identically and weighted only by balance.

Verification

Audit a settlement in four steps.

Every settlement row on the front page carries transaction hashes. Here is how to check one against the chain - trusting Blockscout and your own eyes, not us.

  1. Confirm you're on the real explorer.robinhoodchain.blockscout.com, and the network's chain ID is 4663. Lookalike explorers exist for this chain; verifying a contract on a promoter-controlled explorer proves nothing.
  2. Open the claim transaction.Each epoch begins with the treasury claiming accrued fees. The claim shows revenue arriving in WETH and EPOCH - this is the epoch's income, on the record.
  3. Open the settlement batches.The distribution transactions emit one payout event per wallet. Sum the values: they should equal 50% of the claimed revenue for that epoch, minus dust carried forward.
  4. Check the dead address.The balance of 0x...dEaD only grows. Compare its increase for the epoch against 10% of claimed revenue.

If any of these checks fails for a published epoch and no explanation is posted, treat that as disqualifying. That standard applies to us as much as to anyone.

Risk

What this is, stated plainly.

Settlements are funded entirely by trading volume. Nothing here generates yield: traders pay fees, holders receive a share of them. When volume falls, settlements fall with it, and when volume stops, settlements stop. Projections on this site are arithmetic on an assumed volume, not forecasts.

Protocol revenue depends on the Pons creator fee share, a parameter set by Pons and changeable by Pons. The revenue split - 50% settled, 40% operations, 10% retired - is enforced by published practice and a verifiable transaction history, not by a smart contract.

EPOCH is a speculative token on a two-month-old network. It can lose all of its value. Nothing on this site is financial advice, and no return of any kind is promised.