Execution credits
Every compile, dry run, and live run burns credits. Paying in $CLAUSE settles at the protocol rate instead of the card rate.
$CLAUSE launches on ponsfamily.com and lives on Robinhood Chain. The token pays for compute, sets how high your caps can go, and decides which venues get wired in next. Nothing about it gates custody: your keys stay yours at every tier.
A token with one job gets ignored and a token with ten is a pitch deck. These four are the ones the product actually needs.
Every compile, dry run, and live run burns credits. Paying in $CLAUSE settles at the protocol rate instead of the card rate.
Your staked balance sets the ceiling a single clause may spend. The rail never switches off, it only moves.
Stakers choose the next venue, the next asset class, and which community clauses get promoted into the public feed.
Publish a clause and a slice of every fork's execution fee routes back to you. Attribution is recorded on-chain.
Caps are enforced when the enclave signs, so a tier change cannot be faked from the client. Every tier keeps the same kill switch and the same one-wallet-per-clause rule.
Exact stake sizes and cap numbers are set at launch on ponsfamily.com, published on Robinhood Chain before the sale opens. They are not listed here because quoting numbers that can still move is how people get misled.
Execution is not free: routers quote, enclaves sign, data feeds bill. Credits pay those costs and the surplus is split on a fixed rule.
Drop an address or a handle and you go in the first execution cohort: capped wallets, full ladder, gateway keys, no queue.
Not investment advice. You own the keys, you own the risk.
CLAUSE launches on ponsfamily.com. Drop an address or a handle and you go in the first execution cohort - capped wallets, full ladder, no queue.
No email required. Nothing custodial. You can walk away with your keys at any point.
Read-only. CLAUSE asks for your address to show balances and quote against live pool state. No signature, no approval, nothing to sign.