annon

Trust model

What each party can do, what it cannot, and what you rely on when you buy or sell with Annon.

Who can do what

The buyer's one-time key and the decrypted file stay on the buyer's device. Buyer records never keep a released file key or decrypted content: the browser decrypts in memory, and the CLI writes plaintext only to the output path you name. A seller's pending listing keeps its file key, encrypted with the backup secret, until registration and publication finish, then clears it. Copies of a backup you made elsewhere need your own cleanup.

Seller

Can

List a file, stop its sales for good

Cannot

Take back a key already released, change the split or price of a listed file

Moderatoroptional, named by the seller

Can

Refuse new key releases for that file

Cannot

Move money, read files

Host

Can

Refuse to serve a file

Cannot

Read it, see keys, redirect payouts

Relayer

Can

Refuse to sponsor a transaction

Cannot

Sign as the buyer or seller, redirect payouts, see keys

NEAR MPC network

Can

Derive keys when the contract asks

Cannot

Release a key the contract did not request

defdone

Can

Upgrade the contract during the alpha, which can change any rule, including who may receive a file key

A file key depends on the contract account and the file, not on the buyer. An upgrade could therefore release the same file key to a recipient chosen by the upgrade-key holder, including a key already released to a buyer. Check the deployed contract

Cannot

Decrypt a buyer's existing key answer from public chain data alone

What else you rely on

Besides defdone's upgrade key, four services outside the rules the contract checks.

NEAR MPC network

Derives a key only when the contract asks.

NEAR Intents

Delivers payments from other chains and holds payouts and refunds for their owners.

0xSplits on Base

Pays the shares of a Base payment.