16 Trust

Fees and token

The 0.3% fee, where it accrues, how it is swept, how the buyback and burn of $OOPS works, and what the token is and is not.

#The fee

  • 0.3% of the amount, taken only when a link is claimed.
  • 0% on undo and on expiry refunds. You never pay for changing your mind. You only pay the network gas.
  • Charged in the asset being sent: an ETH link pays an ETH fee, a token link pays a fee in that token.
  • Hard ceiling of 1% in the contract. The admin can set the fee for new links anywhere from 0 to 1%.
  • Locked per link. The fee is copied into the link at creation, so a later change never touches an open link, and the recipient sees the exact fee before signing.
  • It rounds down. At 0.3%, any amount under 334 base units carries no fee.

Example for 1.5 ETH: if claimed, the recipient receives 1.4955 ETH and 0.0045 ETH accrues as fee. If undone or expired, the sender gets 1.5 ETH back and nothing accrues. The Examples page shows this run.

#Where the fee goes

claim ──► 0.3% ──► feesAccrued[token]          (inside the contract, per asset)
                      │  anyone calls sweepFees(token)
                      ▼
                  fee wallet                    (immutable, fixed at deployment, public)
                      │  V1: run from this wallet, every transaction posted
                      ├─ token fees ──► swapped to ETH
                      └─ ETH ──► buys $OOPS ──► sent to 0x…dEaD (burn)
  • Accrual is automatic and on chain. feesAccrued(token) always shows what has not been swept.
  • Sweeping is permissionless. sweepFees(token) moves the whole accrued balance of that asset to the fee wallet. It reverts with ZeroAmount when nothing has accrued.
  • The fee wallet is immutable. It is set in the constructor and cannot be changed. Its address is published at deployment.
  • Buyback and burn happen from the fee wallet. In V1 a person runs them, and each transaction is posted publicly. A burn is a transfer of $OOPS to the dead address 0x000000000000000000000000000000000000dEaD.
  • The burn counter on the home and token pages reads the dead address's token balance straight from the chain once the token's contract address is set. It is not typed in by hand.

#$OOPS

Launchon Pons, the launchpad of Robinhood Chain, started by the team itself
Supply1,000,000,000 at launch (the Pons standard), reduced by burns
Presalenone
Team or VC allocationnone beyond any dev buy made on the public curve, which is disclosed with its wallet when the token launches
Contract address0x85E6F47B74189Ba0f49472E0069957E14EFA95d0
Utilitythe fee sink: claim fees buy and burn it

#What the token is not

  • It is not required to use Oopsend. You can send, claim and undo without ever holding it.
  • It gives no rights. No dividends, no governance, no claim on the fees or on any escrow. It is a memecoin with a burn mechanism tied to usage.
  • It does not change how the contract treats funds. The contract knows nothing about $OOPS. The fee wallet decides what to buy.
  • The burn depends on usage. If few links are claimed, little is burned. A fee on a claimed send is the only source.

#Be careful of fakes

  • The real contract address will be published once, in the site config, and shown on the home page and the token page.
  • Nobody from the project will DM you, ask for a seed phrase, or ask you to "connect to claim" something unexpected.
  • A link that asks you to approve a token spend when you are only receiving is not an Oopsend claim: claiming needs a signature, not an approval.

Not financial advice. Read Risks.