Adytum
Launch app

The auditor key

Selective disclosure is a feature for institutions. A fund, a desk or a regulator can be named as a domain's auditor and read the domain's transcripts, while the public chain only records who holds that role.

Naming an auditor

init_domain stores an auditor public key in the domain account when the domain opens. set_auditor (tag 4) replaces it; only the sequencer can sign it. Both are public transactions, so anyone can see which key holds the role and when it changed.

Reading

From the moment an auditor key is named on Solana, the sequencer seals every inside transfer and every exit request to that key: who, to whom, how much, the member's signature and the batch. Each record gets a fresh one-time key, combined with the auditor's key by X25519, stretched with HKDF-SHA256 and used for AES-256-GCM. The sealed records are served at /api/domain/audit, and only the auditor's private key opens them.

In the local test the auditor opened a sealed 0.2 SOL transfer and read both addresses, the amount and the payer's signature. A second key opened nothing, and the published log showed neither address in the clear.

The tools

product/sequencer/auditor.mjs has three commands: keygen makes the auditor's key on their own machine and prints its public half, grant (signed by the sequencer) names it on Solana, and read fetches the sealed records and opens the ones for that key.

How the key works in this build

The auditor key is an X25519 key. The sequencer writes the records, so it can read the inside ledger too; the auditor's key is what lets a party outside the sequencer read it, and the chain shows who holds that key.

What the auditor cannot do

The auditor key is not a signer on the vault. Exits still need each owner's ed25519 signature and a settle signed by the sequencer.