Security and limits

This page lists what an organism does not do and what can go wrong. It is written before anyone asks.

What it does not do

What can go wrong

RiskWhat happensWhat limits it
RPC outageclaims and burns fail and are retried the next beatthe journal shows claim failed / burn failed; nothing is spent on the books
Key lost or leakedthe wallet's funds are lostnothing: this is custody. Keep the key off shared machines
Price moves while a burn is builtthe buy fills at a different priceeach buy carries a minimum-out guard (3% on the curve, 2% plus the coin's tax in a pool) and reverts beyond it
A wrong model answeran order is trimmed or held backit cannot raise an order or fire a hook; caps do not depend on it
A bugan unexpected orderthe caps are checked before building; the daily ceiling and the gas reserve bound the damage
The coin graduatesit leaves the curve for a Uniswap v4 poolthe organism follows it there: price and buys come from the pool, with a price-impact limit. Between graduation and the pool's creation it waits, see Graduation
A thin poola drip would move the priceevery pool buy is cut down to the size whose estimated price move stays within 4%
A lost receipt on a dev payoutthe transfer is mined but the answer is lost, and the balance cannot be readthe amount stays owed and is retried: in that rare case one payout can be sent twice, to the same address and never past the gas reserve
A lost receipta burn is mined but the caller is told it failedthe wallet balance is compared before and after; if it dropped, the burn is counted. If the balance cannot be read either, the order is counted against the day's ceiling
Fake coin with the same namea holder buys the wrong onethe address is published in two places; paste any address into Verify

Graduation

A Pons coin starts on a bonding curve and later moves to a Uniswap v4 pool. The organism handles both: it reads where the coin trades and buys there. The details, and what is still not covered, are in Graduation.

The key

The organism needs the private key of the wallet that receives the fees, in .env on the machine that runs it. With your own wallet that is the key of a wallet that holds your funds: the code limits what the program does with it, but anyone who reads .env can do anything. Keep it on a machine you trust, never in a repository, never in a chat.

Model keys

ANTHROPIC_API_KEY is read from .env by the runner and sent only to the model provider's API. Use a key with a spending limit. The battery limits what the organism may spend on thinking in accounting terms; the provider's limit is the real wall.

Reporting a problem

Open an issue on the repository once it is public, or message the official X account. Never send a private key to anyone, including us.