LibraryConfidential compute2020Design paperCorpus record
Oasis: confidential ParaTimes beside a consensus layer
Oasis protocol. Oasis Protocol.
Oasis publishes a consensus layer and separate ParaTimes, some of which claim confidential execution. The confidential claim lives in the ParaTime, not in every transaction on the consensus layer.
A reading of the project's public design document. Not a copy, not a benchmark, and not an offer.
Oasis publishes a consensus layer and separate ParaTimes, some of which claim confidential execution. The confidential claim lives in the ParaTime, not in every transaction on the consensus layer.
- Evidence
- Primary paper
- Re-measured
- No
- Assumptions
- 3
- Records linked
- 3
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
A chain with a confidential mode is not a confidential chain. The mode has to be the one you are actually calling.
Claim 02 · Paper model
The proposal
Oasis publishes a consensus layer and separate ParaTimes, some of which claim confidential execution. The confidential claim lives in the ParaTime, not in every transaction on the consensus layer.
Claim 03 · Paper model
The mechanism
Consensus orders ParaTime commitments. A ParaTime executes. Mixing those layers is how the design gets misquoted.
Claim 04 · Paper model
The bound
No validator count is stated here.
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
A chain with a confidential mode is not a confidential chain. The mode has to be the one you are actually calling.
Model
What has to hold
You are reading Oasis documentation. A particular ParaTime's status page can be narrower than the architecture.
02 The proposal
Observation
What the study says
Oasis publishes a consensus layer and separate ParaTimes, some of which claim confidential execution. The confidential claim lives in the ParaTime, not in every transaction on the consensus layer.
Model
What has to hold
You are reading Oasis documentation. A particular ParaTime's status page can be narrower than the architecture.
Falsifier
What would retire it
Which ParaTime does the application run in?
03 The mechanism
Observation
What the study says
Consensus orders ParaTime commitments. A ParaTime executes. Mixing those layers is how the design gets misquoted.
Model
What has to hold
You are reading Oasis documentation. A particular ParaTime's status page can be narrower than the architecture.
Falsifier
What would retire it
Which ParaTime does the application run in?
04 The bound
03 Sequence
One action, as an operating tape
- 01Consensus orders ParaTime commitments. A ParaTime executes. Mixing those layers is how the design gets misquoted.
- 02Confidential execution, where the docs claim it, rests on the hardware or cryptographic assumption that page names.
- 03A discrepancy or fraud proof between ParaTime and consensus is a different mechanism from confidentiality.
04 Load-bearing
The argument, and where a pitch drops it
What the name has to mean
The cut
Oasis publishes a consensus layer and separate ParaTimes, some of which claim confidential execution. The confidential claim lives in the ParaTime, not in every transaction on the consensus layer.
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
A ParaTime that is not the confidential one does not inherit the confidential threat model.
What actually moves
The cut
Confidential execution, where the docs claim it, rests on the hardware or cryptographic assumption that page names.
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
A ParaTime that is not the confidential one does not inherit the confidential threat model.
What a later deployment may change
The cut
A discrepancy or fraud proof between ParaTime and consensus is a different mechanism from confidentiality.
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
A ParaTime that is not the confidential one does not inherit the confidential threat model.
05 Register
What has to be true
Model · Not re-measured
You are reading Oasis documentation. A particular ParaTime's status page can be narrower than the architecture.
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
A ParaTime that is not the confidential one does not inherit the confidential threat model.
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
A chain with a confidential mode is not a confidential chain. The mode has to be the one you are actually calling.
What the design proposes
- Consensus orders ParaTime commitments. A ParaTime executes. Mixing those layers is how the design gets misquoted.
- Confidential execution, where the docs claim it, rests on the hardware or cryptographic assumption that page names.
- A discrepancy or fraud proof between ParaTime and consensus is a different mechanism from confidentiality.
How the mechanism is specified
- Consensus orders ParaTime commitments. A ParaTime executes. Mixing those layers is how the design gets misquoted.
- Confidential execution, where the docs claim it, rests on the hardware or cryptographic assumption that page names.
- A discrepancy or fraud proof between ParaTime and consensus is a different mechanism from confidentiality.
What this page does not treat as proven
- No validator count is stated here.
- The Ekiden paper is an ancestor, not this network's current parameter set.
- A ParaTime that is not the confidential one does not inherit the confidential threat model.
09 Lexicon
Terms, opened into the record
- Confidential execution
- A claim about one ParaTime's state, not about the consensus layer as a whole.
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.
Papers
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.