Skip to content

03 · Protocol

Creator fees become dollars for a person, and less ASH for everyone.

HandlePay is a fee router. It claims token creator fees on chain, pays 80% to a named handle and spends 20% buying ASH and burning it. This terminal is the public record of all of it.

AMechanics

  1. 01

    A token routes its fees

    The deployer points 100% of creator fees at the protocol treasury, permanently. A partial or revocable share is not accepted.

  2. 02

    A handle is named

    One line in the token description names the recipient. They do not sign up, connect a wallet or agree to anything first.

  3. 03

    Fees are claimed on chain

    Accrued fees are claimed on a schedule. Each claim is keyed on its own transaction signature, so it can never be recorded twice.

  4. 04

    Split 80% / 20%

    Applied per claim, at claim time, never recalculated. There is no discretion and no tier.

  5. 05

    The recipient is paid

    Balances are paid when they cross a milestone: $5, $10, $20, $50, $100, $250, $500, $1,000, then every $1,000.

  6. 06

    The cut buys and burns ASH

    The protocol share buys ASH on the open market through an aggregator, then sends it to a burn instruction. Both are on chain.

BBuyback status system

  • Pending

    The protocol cut is queued. It keeps collecting claims until the next execution window.

  • Executing

    The swap has been submitted to the aggregator and is waiting for confirmation.

  • Bought

    The asset was bought on the open market. The burn instruction is being submitted.

  • Burned

    Bought and burned. Supply is permanently reduced; both transactions are on chain.

  • Failed

    Execution did not complete. No funds were lost; the amount rolls into the next attempt.

CPayouts & expiry

  • Paid

    Delivered to the recipient.

  • Claimable

    Sent. The recipient has not opened a payout account yet and has 14 days to claim.

  • Expired

    Not claimed in time. Returned and split 50/50 between treasury and buyback.

Expired payouts return and are split 50% to the treasury and 50% to a separate buyback. Those burns are tagged Recycled expired payout in the ledger, never blended with protocol-cut burns.

DData provenance in this build

LIVE

Read from a real source today

  • ETH/USD spot price (public price API, 30s cache)
  • Explorer links for every mint and signature
  • Buyback & burn ledger read from Robinhood Chain (hybrid mode)

MOCK

Seeded history standing in for the indexer

  • Claims, buybacks, burns, payouts
  • Registered tokens and recipients (fictional)
  • Daily volume audit and hourly snapshots

SIMULATED

Runtime stream on top of the mock

  • New claims every few seconds
  • Buybacks moving through the pipeline (~40s instead of hourly)
  • Occasional failures with retry

Set NEXT_PUBLIC_DATA_MODE=live and INDEXER_URL to replace mock and simulated records with the indexer. Components do not change: they only consume the typed snapshot. How each figure is computed →