A sealed deployment runs on Tinfoil Containers with the deploy kit in the repository. Each property below comes from a mechanism you can read and check. Each card says what stays visible.
You can check the build
At boot Bellows makes a key pair in memory and serves a hardware attestation that binds the key to the build it runs.
Before it sends anything, a client checks that attestation and finds the build in the public builds.json. If the check fails, it sends nothing.
Limit. Whoever controls builds.json decides which builds clients trust. The operator approves releases in their own keyserver, the known weak point of version 1.
How attestation works
The operator cannot read the words
Requests, answers, balances, the wallet seed and the supplier keys exist in plaintext only inside the confidential VM.
Clients encrypt each call to the attested key. The database sits on an encrypted volume whose key a keyserver releases only to an approved build.
Limit. The operator still sees aggregate totals, logs that hold no client data, and traffic timing and volume. A model's supplier sees the prompts of plaintext models.
What each party can see
Pay with eCash, no account
Pay each request with a Cashu token in a header and get the unused value back as change. Or top up a balance and use its key like an API key.
Prices are set per million tokens. Balances stay in usd or sat, and you can withdraw what is left as eCash at any time.
Limit. Every request on one balance key is linkable to the others. The mint sees its own swaps.
How payments work
A relay hides who is asking
Send each call through an Oblivious HTTP relay. The relay sees your address and ciphertext. Bellows sees the request and the relay's address.
Who is asking is hidden from the operator when you use a relay run by someone else, or Tor. Answers still stream.
Limit. A relay and a Bellows run by the same party hide nothing from that party. Without a relay or Tor, the operator's network sees client addresses.
How Oblivious HTTP works
Releases 0.1.0 to 0.1.2 were built and measured by the public release workflows, and the reference instance runs 0.1.2 sealed on Tinfoil Containers. A paid request, an Oblivious HTTP round trip and reading a balance back after a restart are covered by the test suite and local runs, and have not yet been run on sealed hardware. Run your own lists every step not yet checked there. A Bellows run outside the deploy kit, on your own server, does not seal anything: its operator can read requests in memory and its database.