How it works,drawn out.

Six diagrams, from who holds what to how you switch it off. Most of what they show is still a design, so each one ends with a line that says how much of it exists today.

Who holds what,in four zones.

Secrets exist only inside the sealed vault. You hold the keys that sign for you, your apps stay where they are, and Concordium is the public notary under all of it.

You

Your browser and your wallet

  • DashboardChat, approvals and the activity feed.
  • Vault checkerChecks the vault’s proof before you connect anything.
  • Concordium walletHolds your verified ID and your keys. You sign with it.

Developers and the cloud hostThey run the machine. They cannot look inside it.

no access

The sealed vault

A confidential machine on Phala Cloud, sealed by the chip (Intel TDX)

  • Front doorLogin and API. HTTPS ends inside the vault, so nobody in between can read it.
  • PersonaThe agent and its tools: mail, calendar and calls to other agents.
  • Rule engineYour rules decide every action: do alone, ask you first, or never.
  • Token vaultApp tokens, encrypted with a key that never leaves the chip. The disk holds ciphertext only.
  • Chain watcherWatches Concordium. If you revoke the persona, it wipes the tokens and stops.
  • Private AI modelRuns in its own sealed machine, so no model provider reads your mail.
  • Receipt writerSigns a tamper-evident log entry for every decision and action.
  • Keys born insideThe persona’s signing keys are created in the vault. Nobody ever sees them.

Your apps and the outside

Everything the persona reaches

  • GmailRead, search, send.
  • Google CalendarRead events, add and remove them.
  • Google DriveRead the files you point to.
  • Other agents and paid servicesOn any chain. They check your badge, you check theirs. Paid through x402.
You sign: register the persona, consent, revoke
The vault anchors its proofs and watches for a revoke
Pays and is paid

Concordium

The public notary. Anyone can read it and nobody can edit it

  • Identity layerA real, ID-checked person stands behind each account. Zero-knowledge proofs keep the details private.
  • Agent RegistryCIS-8004Your persona is owned by your account. It carries the Verified by Concordium badge and the fingerprint of the vault’s code.
  • Key RegistryCIS-8Binds the vault’s key on Base to your verified account.
  • ReceiptsHashes of your consents and of the action log. Never the content.
  • PaymentsStablecoin transfers through x402. Fees are sponsored, so the persona needs no gas.
  • LiveThe Agent Registry and Key Registry on Concordium testnet, with two personas registered.
  • BuiltRegistering a persona from the app, signed calls to other agents, and paying and being paid in test CCD.
  • BuiltThe vault itself: it has run sealed on Phala Cloud, and its hardware proof checked out.
  • DesignedYour app keys inside the vault, the app connections through it, and stablecoin payments from it.

Getting started,in seven steps.

Read each step across: what you do, what the sealed vault does with it, and what is written on Concordium.

  1. Sign in with your wallet

    Connect your Concordium wallet. There is no password that we could reset.

    wallet sign-in
    The sealed vault

    Checks your wallet’s signature itself, so we cannot log in as you.

    On Concordium

    Nothing is written.

  2. Prove you are a real person

    Your wallet shows a zero-knowledge proof: verified ID, adult. No name, no passport.

    Verify and Access
    The sealed vault

    Verifies the proof. Keeps no personal data.

    On Concordium

    Nothing new. Your ID was issued earlier, by a Concordium identity provider.

  3. Check the vault

    One click: is this real sealed hardware, running exactly the public code?

    remote attestation
    The sealed vault

    Hands over its hardware proof.

    On Concordium

    Nothing is written.

  4. Create your persona

    Give it a name, then sign once in your wallet.

    CIS-8004 and CIS-8
    The sealed vault

    Creates the persona’s keys inside. They never leave.

    On Concordium

    The persona is registered to your account, with the Verified badge and the vault’s key.

  5. Connect your apps

    Pick Gmail, Calendar and so on. Approve on Google’s own page.

    OAuth inside the vault
    The sealed vault

    Gets the token directly and seals it.

    On Concordium

    A consent receipt: which app, which permissions, when.

  6. Set your rules

    For each ability: do alone, ask me first, or never. Add a daily spend limit.

    rule engine
    The sealed vault

    Stores the rules. The AI cannot change them.

    On Concordium

    A fingerprint of your rules.

  7. The persona goes live

    It reads, drafts, books and pays within your rules. You see every step.

    receipts and off switch
    The sealed vault

    Runs the agent and logs every action.

    On Concordium

    A proof of the action log.

  • BuiltStep 4 without the vault: a persona is registered on Concordium from inside the app.
  • LiveStep 1, wallet sign-in.
  • BuiltThe vault itself, run on Phala Cloud with a proof that checks out.
  • DesignedThe vault’s part in each step, and steps 2, 3, 5, 6 and 7.

Connecting an app,with Gmail as the example.

Read from top to bottom. The token goes from Google straight into the vault. Our ordinary servers and your browser never hold it.

  1. You

    Click Connect Gmail. Choose what to allow: read, send.

  2. The sealed vault

    The vault sends you to Google with exactly those permissions.

  3. Google

    You approve, on Google’s own page.

  4. Google

    Google sends a one-time code to the vault’s address.

  5. The sealed vault

    The vault swaps the code for your tokens, server to server.

  6. The sealed vault

    It saves the tokens encrypted. The key stays in the chip.

  7. You

    You sign the consent in your wallet: app, permissions, rules.

  8. Concordium

    The consent receipt, a hash, goes on chain.

  9. You

    Connected. You get a link to the receipt.

  • What a developer finds in the database9f3a c1e0 77b2 04dd 5a19 …Only ciphertext. No key, no shell on the machine, no secrets in the logs.
  • Why the code goes to the vaultGoogle returns the code to an address that ends inside the vault, where HTTPS is terminated. Nothing in between can read it.
  • Permissions stay smallRead and send only. No delete, no settings. Add or remove a permission later and a new receipt is written.
  • DesignedEvery step. No app connects through the vault yet.

When the persona wants to act,your rules decide.

The AI only proposes. Rules written in plain code decide, and every outcome leaves a receipt, a blocked attempt included.

Something happensA new email, your chat message, a schedule or another agent.
The persona reads what it needsWith your sealed token, inside the vault.
The private AI proposes a planThe model runs in its own sealed machine.
Your rules: is it allowed?Each step of the plan is checked on its own.
  • Do aloneLow risk: read, draft.
    The persona does itThrough the app’s own API, with your sealed token.
  • Ask me firstSensitive: send, pay.
    You approve or declineIn the app. Approve, and the persona does it. Decline, and nothing is sent.
  • NeverForbidden: delete, forward everything.
    Nothing is sentYou get an alert. Blocked attempts are logged too.
every outcome
A receipt is writtenWhat, when, which rule. Signed inside the vault and chained to the one before.
Proof goes on ConcordiumA hash of the latest receipts.
You see it in your feedEvery entry has a link to verify it.
An example: “Can we meet on Tuesday?”
  1. Read your calendaralone
  2. Draft a replyalone
  3. Send the replyasks you
  4. Create the eventalone
  • Why the rules sit outside the AIAn email can hide instructions for the AI. This is called prompt injection, and the AI can be fooled by it. The rule engine is plain code, so text inside an email can never change your rules.
  • BuiltAsking you before something that commits you, and a receipt for each answer you give, anchored on Concordium testnet. What the persona does alone leaves no receipt yet.
  • DesignedThe rest of this flow.

How a caller is checked,at the gate.

The gate is a few lines in front of an HTTP endpoint. Today it runs in a gateway in front of a persona, and the same check fits any service an agent can call.

An agent sends a requestSigned by its own key, in the ERC-8128 format for Ethereum keys or with ed25519 for Solana keys, and carrying its badge.
The gate checks, in order
  1. The signature is fresh and was made by the caller’s key.
  2. The badge belongs to an Active agent in a trusted registry.
  3. That agent’s bound key is the key that signed.
  4. The key binding is still Active, with the same owner.
  5. Owner facts, if you ask for them: over 18, country.Designed
  6. Your own rules: a deny list, a limit per owner.
  • all pass
    Your handler runsIt is given the badge, the owner’s account and the chain the key lives on.
  • one fails
    401 or 403With the reason, and what a caller must bring to pass. 429 when an owner is over the limit, 503 when the registry cannot be read.
every decision
ReceiptEach decision becomes one entry in a log, and each entry carries the hash of the one before.
AnchorThe newest hash of the log goes on Concordium.
  • Why a signatureA badge alone is a claim. The signature proves the caller holds the key right now.
  • A live lookupThe agent and its key binding are read from Concordium’s registries and cached for 60 seconds, which is also how long a revoke takes to bite.
  • A limit per human, not per keyLimits and deny lists are keyed by the owner’s account, not by the key. Making a thousand new keys does not help a spammer.
  • BuiltChecks 1 to 4 and 6, the hash-chained log, and an hourly anchor of that log on Concordium testnet, in a gateway on our own machine.
  • DesignedCheck 5. Until it exists, a gate that asks for an owner fact refuses everyone.

The off switch,three ways out.

You are never locked in. Two of the three ways do not depend on us at all.

  • In the appPress Stop persona, or Disconnect on one app.
    The vault deletes the tokens and asks Google to cancel them.
  • In your walletRevoke the persona on Concordium.
    The vault sees the revoke on chain, wipes the tokens and stops.Works even if our website is down.
  • At GoogleIn your Google Account, remove the persona from the apps that have access.
    Google cancels the token at the source.Works even if we disappear.
Access is goneThe tokens are wiped or cancelled and the persona stops. The first two ways also leave a revoke receipt on Concordium. You can start again at any time.
  • BuiltRevoking the persona from the owner’s own account. From then on every gate turns it away and it takes no calls. Run on testnet.
  • BuiltThe vault wiping what it holds when the server sees the revoke. It runs when the vault is up.
  • DesignedThe Stop button in the app that wipes the tokens. The third way is Google’s own control and needs nothing from us.

One part of this is live.Read a real agent from the chain.

Check an agent