Security
Annon is in public alpha. Here is what that means, what we know can go wrong, and how to tell us.
Status
Alpha
- Contract
v1.annon.defdone.near on NEAR mainnet, upgradeable by defdone- Packages
@defdone/annon and @defdone/annon-mcp, release series 0.1.0-alpha.N on the npm alpha tag- Audits
- Internal reviews and mutation testing only. No independent audit yet.
defdone can change the contract
During the alpha defdone keeps a full-access key to the contract account so that a bug can be fixed in place. That key can change the contract's code, and therefore its rules. It is the largest trust Annon asks for. After an independent audit we will remove the key and lock the contract; a later fix then ships as a new contract that sellers move to. We do not give a date for the audit yet.
ed25519:7HhkRnyjJkMzkZfKqg1wLbwfKYgadxuHpNyxKgnQZG4GCheck the deployed contract
Compare the code hash on chain with the one in contracts/annon/mainnet.json.
- contract
- v1.annon.defdone.near
- codeHash
- FFuE8TCvuVTtLK7vVAsmBoj4BSHq1X64fzpuiF2MrKNU
- deployedAt
- 2026-11-12
- source
- hackathon-submission, 951dc72
- audit
- none yet
curl -fsS https://rpc.mainnet.fastnear.com -H 'Content-Type: application/json' \
-d '{"jsonrpc":"2.0","id":1,"method":"query","params":{"request_type":"view_account","finality":"final","account_id":"v1.annon.defdone.near"}}' \
| jq -er .result.code_hash
With "request_type":"view_access_key_list" the same request lists the account's keys. The account is also on NearBlocks.
An open protocol
The contract will still change during the alpha, and we take responsibility for those changes. Annon is an open protocol: start a discussion with any proposal for the specifications or the contract. We review every proposal and either adopt it or work it out there in the open.
Start a discussion
Known limits
These are known and accepted for the alpha. Please do not report them as new findings, but do tell us if you can make one worse than described. The four with the widest effect come first; open any of the rest. Every detail is in the security policy.
Takedown after a key request
A moderator's takedown refuses new key requests. A request already sent to the MPC network can still complete, because the network publishes its answer on chain.
Refund proof window
When the contract rejects a payment and its storage reserve is too low to record the refund, it adds a refund leaf to an on-chain accumulator instead, and the refund is claimed later with a proof. Proofs against the current root and the previous 31 roots are accepted: a proof goes stale once 32 more leaves are added, and the claim then needs a proof against a newer root.
A failed payout callback
A failed payout callback leaves that step marked in flight. It is never reset automatically: a timeout cannot tell a completed transfer from a delayed one, and a reset could pay twice. During the alpha a reviewed upgrade can repair a provable accounting error.
USDC issuer controls
Circle can freeze a recipient address or a Base split. A frozen push split pays nobody until it is unfrozen; the contract's own records stay correct.
Browser storage
In the browser, encrypted purchase records and the secret that protects them live in the same IndexedDB origin. They protect against accidental disclosure, not against code running on the same page. Export receipts with a separate secret for anything you want to keep.
Local agents
The MCP server enforces the owner's price limits, daily budget and working directory against tool calls. It does not contain a shell agent running as the same operating system user, which can edit the configuration directly. Use separate OS users when that matters.
Real browsers
Browser code is tested against stubbed wallets and IndexedDB, and its bundles are checked for CSP compatibility. Behaviour in specific browsers and wallet extensions is tested by hand, not in CI.
Previews
A PAY2 file can carry a preview, but clients do not verify previews for buyers in this release. A page must not present a preview as checked.
Not DRM
The seller knows the content and a buyer can share what they decrypted. Listing terms, titles, descriptions and file sizes are public.
Hosting
Key release does not keep a file online. A shop's host can refuse, expire or lose a file; the purchase stays on chain and opens from any host that serves the same checked file.
If a payment goes wrong
Your money is never lost to a pending state. Here is what happens in each case.
Pending means wait
A purchase that shows as pending or not yet accepted is still being confirmed. Check it again later with the same purchase; never pay a second time.
Underpayment never opens a file
A valid NEAR or 1Click payment below the price is refunded in full to the NEAR Intents account of the wallet that paid. Withdraw it with that wallet, to any chain.
1Click refunds
If NEAR Intents delivers a payment the contract refuses (for example after the purchase expired), the refund stays in the NEAR Intents account named in the quote, not on the source chain.
Report a vulnerability
Please report privately before you write about it, through GitHub's private reporting on the SDK repository. We reply within 72 hours and keep you informed until the fix ships. If the issue can lose funds or leak keys on mainnet, say so in the title. If you cannot use GitHub, write to hello@annon.dev without exploit details, and we will set up a private channel.
Only the latest alpha release on npm and the contract listed above receive fixes.
Report on GitHub/.well-known/security.txt