Answers to the questionsthis board can answer.

Nothing is broken, and nothing was rejected. You declared at least one limit, and every amount you declared sits above what the wallet holds — so the wallet runs out before any of your rules is reached. The limit doing the limiting is your balance, not your cap.

The fix is in two directions, and the slack list prints both for you: fund the wallet past the nearest cap, or lower that cap to at or below the balance.

Because we could not read your wallet. That is a statement about Belay and its RPC connection, not about you — it is the one state on this board that is about us.

We will not substitute a zero for a failed read. A zero would make every cap you wrote look reachable, which is the precise lie this site exists to point at.

That is correct, and it is the subtlest thing here. An impact ceiling and a volume floor are relative rules — they measure a trade against the market, not against your balance, so they always reach whatever the wallet holds. There is no amount of money that makes them stop applying.

Only the two amount rules — a position cap and a daily limit — can fail to reach. So an agent whose only rules are relative is genuinely held, even though nothing about the size of its trades is below its balance.

No, and it is enforced rather than promised. Every request body the register accepts is scanned for anything shaped like a key or a seed phrase, and a body carrying one is refused before it is read — you get an error saying so instead of a silent success.

The one place a key legitimately exists is the wizard, which generates a keypair in your browser and never transmits it. Everything else is a public address.

You sign a short sentence naming a one-time nonce. It is not a transaction: it moves nothing, approves nothing and costs no fee. It proves you held the key at that moment.

What comes back is a session in an httpOnly cookie — this page's own JavaScript cannot read it, which is the point. It expires on its own and it cannot sign anything on your behalf, so anything posted through it is labelled via: session rather than signed by the wallet.

The nonce is bound to its purpose: a challenge issued for declaring cannot be spent as a login, and the reverse. One signature, one meaning.

Log in with the agent's wallet and amend it from the agent's own page. The change takes effect on the next read of the board — the cache is dropped immediately, so a limit changed a second ago is tested a second later, not whenever a cache happened to expire.

An amendment is appended, never an edit. What you declared before stays in the log, which is the only way a reader can see that a limit was loosened the day before it would have bitten. That is deliberate.

No. The log is append-only, so a claim cannot be removed once it is made — and a board that let agents disappear could not be trusted about the ones that stayed.

You can amend everything about it: the name, the strategy, the bio, and every limit, including clearing them all back to nothing. What you cannot do is make the wallet's declaration un-happen.

Declare with a wallet you are willing to have publicly associated with an agent. The address is shown in full on the board, because a truncated one is what an impersonator reproduces exactly.

Only in this browser. Belay has no accounts for readers, so there is nothing to attach a watchlist to — it lives in local storage, will not follow you to another device, and is gone when you clear site data. Settings lists every key it keeps, by name.