LibraryConfidential compute2020Design paperCorpus record
Secret Network: contracts with encrypted state on a known validator set
Secret Network. Secret Labs.
Secret Network publishes contracts whose state is encrypted, with a validator set that can compute on that state inside a trusted execution environment.
A reading of the project's public design document. Not a copy, not a benchmark, and not an offer.
Secret Network publishes contracts whose state is encrypted, with a validator set that can compute on that state inside a trusted execution environment.
- Evidence
- Primary paper
- Re-measured
- No
- Assumptions
- 3
- Records linked
- 4
01 Claim ledger
What the paper is allowed to say
Each row is a sentence already in the study. The status is the same on every row: a model claim, not a live measurement.
Claim 01 · Paper model
The defect
Encrypted state on a public chain usually means the validators can see more than the public can. The threat model has to say so.
Claim 02 · Paper model
The proposal
Secret Network publishes contracts whose state is encrypted, with a validator set that can compute on that state inside a trusted execution environment.
Claim 03 · Paper model
The mechanism
The enclave, if that is the mechanism the docs still specify, is the trust root for confidentiality. A broken enclave breaks the privacy claim even if consensus is honest.
Claim 04 · Paper model
The bound
This note does not rate the hardware.
02 Three cuts
Observation, model, falsifier
A desk does not stop at the summary. Each claim is cut three ways, using only this study's own assumptions and checks. Nothing here is a new figure.
01 The defect
Observation
What the study says
Encrypted state on a public chain usually means the validators can see more than the public can. The threat model has to say so.
Model
What has to hold
You are reading Secret Network's documentation. Ekiden is the academic relative, not this deployment.
Falsifier
What would retire it
Who can decrypt contract state?
02 The proposal
Observation
What the study says
Secret Network publishes contracts whose state is encrypted, with a validator set that can compute on that state inside a trusted execution environment.
Model
What has to hold
You are reading Secret Network's documentation. Ekiden is the academic relative, not this deployment.
Falsifier
What would retire it
Who can decrypt contract state?
03 The mechanism
Observation
What the study says
The enclave, if that is the mechanism the docs still specify, is the trust root for confidentiality. A broken enclave breaks the privacy claim even if consensus is honest.
Model
What has to hold
No price, supply, yield, or adoption figure is added by this desk.
Falsifier
What would retire it
What remains public: the call, the sender, the code?
04 The bound
Observation
What the study says
This note does not rate the hardware.
Model
What has to hold
You are reading Secret Network's documentation. Ekiden is the academic relative, not this deployment.
Falsifier
What would retire it
What hardware assumption does the page you opened actually name?
03 Sequence
One action, as an operating tape
- 01The enclave, if that is the mechanism the docs still specify, is the trust root for confidentiality. A broken enclave breaks the privacy claim even if consensus is honest.
- 02Consensus among validators orders transactions. The enclave is a different assumption, closer to Ekiden than to a zkVM.
- 03A query that decrypts state for a user is a disclosure. The docs define who may query.
04 Load-bearing
The argument, and where a pitch drops it
What the name has to mean
The cut
Secret Network publishes contracts whose state is encrypted, with a validator set that can compute on that state inside a trusted execution environment.
Why it carries weight
If this cut is skipped, the paper's name is being used without the mechanism that makes the name mean anything.
Where it is dropped
It does not say contract state is hidden from validators if the docs say the enclave sees it.
What actually moves
The cut
Consensus among validators orders transactions. The enclave is a different assumption, closer to Ekiden than to a zkVM.
Why it carries weight
If this cut is skipped, the paper's name is being used without the mechanism that makes the name mean anything.
Where it is dropped
It does not say contract state is hidden from validators if the docs say the enclave sees it.
What a later deployment may change
The cut
A query that decrypts state for a user is a disclosure. The docs define who may query.
Why it carries weight
If this cut is skipped, the paper's name is being used without the mechanism that makes the name mean anything.
Where it is dropped
It does not say contract state is hidden from validators if the docs say the enclave sees it.
05 Register
What has to be true
Network · Not re-measured
You are reading Secret Network's documentation. Ekiden is the academic relative, not this deployment.
Model · Not re-measured
The document is the one at the source URL. A marketing page with the same brand is not this text.
Model · Not re-measured
No price, supply, yield, or adoption figure is added by this desk.
06 Divergence
What happened after the paper
This is not Aztec. There is no proof that hides the state from the operator. There is hardware.
A later client, parameter set, or reward formula is a different object. Cite this paper for the mechanism. Cite a primary release for the network. This desk has not re-run the proof.
07 Pre-mortem
What to check before you use the idea
- 0 of 3 marked on this browser. A mark is a reading note, not a pass, a rating, or a recommendation.
08 Anatomy
The paper, in the order a builder needs
The problem it names
Encrypted state on a public chain usually means the validators can see more than the public can. The threat model has to say so.
What the design proposes
- The enclave, if that is the mechanism the docs still specify, is the trust root for confidentiality. A broken enclave breaks the privacy claim even if consensus is honest.
- Consensus among validators orders transactions. The enclave is a different assumption, closer to Ekiden than to a zkVM.
- A query that decrypts state for a user is a disclosure. The docs define who may query.
How the mechanism is specified
- The enclave, if that is the mechanism the docs still specify, is the trust root for confidentiality. A broken enclave breaks the privacy claim even if consensus is honest.
- Consensus among validators orders transactions. The enclave is a different assumption, closer to Ekiden than to a zkVM.
- A query that decrypts state for a user is a disclosure. The docs define who may query.
What this page does not treat as proven
- This note does not rate the hardware.
- It does not say contract state is hidden from validators if the docs say the enclave sees it.
- This is not Aztec. There is no proof that hides the state from the operator. There is hardware.
Why the desk still reads it
Secret Network publishes contracts whose state is encrypted, with a validator set that can compute on that state inside a trusted execution environment.
09 Lexicon
Terms, opened into the record
- Trusted execution environment
- Hardware that is supposed to hide computation from the operator. It is a trust assumption.
- Encrypted contract state
- State that is ciphertext on the public ledger. Ciphertext is not the same as hidden from validators.
10 Repository
Every linked record on this page
Underlined words open a page that already exists: a concept, a protocol profile, a failure record, or another paper. If a word is not underlined, this desk does not have a record for it.
This is Blockchain Lab's reading of a public design paper. It is not the paper, not a copy of it, and not an offer of tokens, equity, custody or a partnership. Later network behaviour can diverge from the text. Nothing here is investment, legal or technical advice.
Research status: Design paper. Last reviewed: 1 October 2026. This is a reading of a public paper, not investment, legal or security advice.