Skip to content
Open app

ProtocolMeasured figures

Measured figures

Every figure measured from a real proof and real transactions, what each means, and how it was taken.

Every figure on this page was measured on a running build, never estimated. They were taken on localnet against Agave 4.3.2, with program 5hJVoxABR1b9QqnQ7FfZDtY2fgNGkUsQtPBqjyBLPTU3, on 2026-11-15 at 17:39 UTC.

How they were measured#

The figures come from the transactions of the end-to-end message flow on the validator, one more real proof simulated at the capacity boundary, and the validator's own rent. The backend records them in docs/measured.json, with a summary in docs/measured.md. These pages read measured.json directly.

  • Compute units are read from the program's own consumed log line for the instruction, the last matching line of the transaction. For buy_pass it is the parent instruction's line, not the smaller line of its event CPI.
  • Sizes are the serialized bytes of the confirmed transaction as the validator returns it.
  • Node proof time comes from the circuit check, which runs groth16.fullProve single-threaded in Node.
  • Browser proof time was measured in Chrome on /proof, which runs the SDK's demonstration proof and verifies it.

Proof#

FigureValueWhat it means
Proof generation, Node1,882 msOne measured run of a full proof: witness and Groth16 proof, single-threaded.
Proof generation, browser1,400 msA proof made in the browser. /proof measures it live in your own browser.
Proof verification, browser317 msChecking that proof against the verification key in the same browser, as /proof does after proving.
Proof size256 bytesThe packed Groth16 proof a post carries.
Circuit constraints7,941Non-linear constraints of the post circuit. Circuit.
Public inputs6Field elements the verifier sees: root, day, nullifier, payload hash and the relay as two limbs.

Post#

One real post from the message flow, and the buy_pass that bought its pass.

FigureValueWhat it means
post compute120,879 CUThe whole instruction: proof verification, the Nullifier account and the relay fee.
post transaction1,540 bytesThe serialized Transaction V1 of this message.
Its payload852 bytesVersion byte, two key slots and ciphertext.
Its ciphertext641 bytesThe encrypted message after the key slots.
buy_pass compute45,919 CUThe parent instruction: pricing, the leaf, 26 Poseidon hashes up the tree and the payment split. Its event CPI's own line is smaller and is not this figure.

The measured transactions:

postsignature
27qt7MXJL62zFfqteY8N6g5jTaDohGCdiNcnqGUX9QKLSK1b5Dr1yZf3c3UxQrUH2YEcfAkvuqHjqVkscSt1fRTv
buy_passsignature
3aN3oCA2UPa3muHoyuVdhua4S6FKo364mn12HK4g4sXAUf2APnnMGLUfpmr9gPSLUp4X1hppfJRbM5h6EYZPfA6K

Capacity#

How much one message can carry in one Transaction V1 with the current six-account post, one signature and the SDK's version 1 envelope.

FigureValueWhat it means
Transaction4,096 bytesThe Transaction V1 limit.
Payload3,408 bytesThe largest payload a post fits. Relays refuse anything larger.
Ciphertext3,197 bytesThe payload less its version byte and two key slots.
Plaintext3,157 bytesThe ciphertext less its nonce and tag: the envelope's whole budget.
ASCII text2,614 charactersText that fits in one part inside the envelope with its two authentication tags. Characters outside ASCII and characters JSON escapes take more bytes.
SDK part size700 UTF-8 bytesThe text the SDK puts in each part. Longer text is sent as numbered parts, one post each.
Boundary simulated4,096 bytesA real proof with the largest payload was simulated at exactly this size and accepted.
One byte morerejectedThe same transaction with one byte added.

Log entry format gives the bytes behind each of these sizes.

Rent#

The rent-exempt balance of the two accounts a person's actions create.

AccountBytesOn the validatorAt the mainnet rate
Nullifier811,454,640 lamports1,061,720 lamports
Inbox1011,593,840 lamports1,163,320 lamports

The validator column is the validator's own rent-exempt minimum. The mainnet column is computed as (account bytes + 128) × 5,080 lamports, with no call to mainnet. A relay fronts the Nullifier rent for each post and receives it back when the day is closed (Relays); a wallet pays the Inbox rent once when it opens its inbox.

Checks#

What the measured flow asserted on the chain, beyond the figures.

CheckResultWhat was asserted
Poseidon matches the chainpassedThe pool root the SDK rebuilt from every leaf equals the root the program computed.
Reader authenticatedpassedThe reader's scan found the message, decrypted it and confirmed its writer.
Writer's slot restoredpassedA fresh device of the writer found its own sent message and the day's used count through the writer's key slot.
One relay signerpassedThe landed post is a Transaction V1 with one signature, the relay's.
Writer and reader absentpassedNeither wallet is among the transaction's accounts.
Relay rent refundedpassedClosing the day returned the Nullifier's whole balance to the relay that fronted it.
Public inputs bound6 rejectedEach of the six public signals, changed by one, made the proof fail.