Security

What you have to trust, stated plainly.

“Trustless” is the wrong word for anything we build. The trust is specific and small, and this page says what it is.

What you trust, and what you don’t

TRUST

You trust

  • The chip maker’s attestation of each enclave: the same trust you place in your own processor.
  • A build that can be reproduced and checked.
  • The operator group, which must agree on every update and every payout.

You don’t have to trust

  • The developers. We can’t ship code the group didn’t admit.
  • Any single operator or machine. None can move funds or change code alone.
  • Bridges, wrapped tokens or off-chain custody. There are none.

Technical overview

Agent keys

You trust

  • The security chip in the agent’s computer, and its maker.
  • The blockchain that enforces the owner’s limits.
  • Where the chip is a virtual one, the cloud platform underneath it.

You don’t have to trust

  • The agent, its model or its tools.
  • Anything that can read the agent’s disk. There is no key file to find.

How it works

Merchant signer

You trust

  • The processor’s enclave and its maker’s attestation, which you check on your own machine.
  • Your own two keys, the owner key and the recovery key, kept off the server.

You don’t have to trust

  • The payment server, its plugins or its admin logins.
  • The server’s operating system, for the seed.
  • The server’s clock. Budgets are counted in blocks.

How it works

How code changes in TRUST

Most systems spread out custody and keep one upgrade path: an admin key, or a push that silently changes what every machine runs. That path is the one TRUST closes first.

Builds are reproducible and independently verified. There is no admin key and no out-of-band push, for test versions too.

The update ceremony

A change
Any new build has a new fingerprint.
The ceremony
Each machine reproduces the build, measures it, and co-signs its admission. The old version hands its sealed state only to a build the group approved.
Then it runs
The group runs exactly that build, and nothing else.

Where things stand

Everything runs on test networks.

The three machines of the testnet engine are physically separate and run by us. Operator independence is what a customer deploys: separate machines, separate administrators, separate clouds or sites, so that capturing one of them does not reach a quorum.

Audits.

Internal review rounds, including independent in-house security review. A third-party audit is planned before any mainnet funds.

What software can’t close.

Physical attacks on a processor, and flaws in its design, are outside what we can fix in software. In TRUST no single machine holds a whole key, so one broken enclave signs nothing. The Merchant signer runs on one machine, and its page says what that means.

More detail.

Threat models and design documents are available on request: info@postcryptum.io.

Report a vulnerability

Tell us what you found and how to reproduce it. We answer every report, and we agree a disclosure date with you before anything is published.

Please test only against test networks and your own accounts. There is no paid bounty program today.