Topic index

Development status: Overview — This page is a navigation aid that lists public pages by topic. It makes no capability claims; status is stated on each page, not in the index. Nothing is publicly available for live use.

Before you read: nothing — this page is a starting point.

Where is a topic covered if you do not know which section it is in? This alphabetical list of topics links each one to the page or pages that cover it. It is offered in addition to the site navigation, Choose your path and search, and it is built only from public page titles and their reader keywords.

How the index works

• Alphabetical. Topics are listed alphabetically under letter headings, with letter navigation at the top of the list.
• Main page first. Each topic links to the page that covers it; where several pages do, the main page comes first and the others follow.
• Reader words. Topic phrases come from public page titles and the plain words readers tend to search for, so one page can appear under several topics.
• Named links. Link text always names the destination page.

What an entry looks like

These five entries show the format; each also appears in the list below.

• Audit trails — Audit trails and tamper-evident logging
• Errors and failures — What can go wrong: failure and error concepts
• Finality — Agreement and finality status; Lifecycle stages used in this documentation
• Getting started — Getting started once a release exists
• SDK availability — Tools, SDKs and wallet availability; Submitting work and retrieving results

What the index does not include

• No status. Status labels and availability statements are not shown here; each page states its own status.
• No uncovered topics. Topics this documentation does not cover are not listed.
• No internal names. Internal names, page identifiers and anything not shown on a public page are not listed.
• No definitions. Terms are defined in the Glossary, not here.

Accessibility

The index is text only, and nothing in it is conveyed by colour alone. Link text is meaningful and the letter structure is predictable, following accessibility guidance without claiming conformance with any standard. The index gives a second route to every page, alongside navigation and search.

Topics from A to Z

Jump to a letter: A · B · C · D · E · F · G · H · I · J · K · L · M · N · O · P · Q · R · S · T · U · V · W

A

• About this documentation — About the Cubane developer documentation
• Abuse prevention — Request abuse and replay protection
• Access control — Privacy-protection building blocks in the experimental prototype
• Account recovery — Participant identity
• Accountability — Design note: accountability for misbehaviour
• Admission control — Service levels and admission control
• Agreement — Agreement and finality status
• API — Interfaces and their status
• API reference — Conceptual reference
• Appeals — Disputes and appeals
• Application logic — Application logic, execution and storage
• Application patterns — What you could build: intended application patterns
• Approvals — Approving actions: authority and multi-party approval; Organisation workflows with shared approval and custody choices
• Archival — Keeping encrypted data available
• Assumptions — Assumptions and open questions
• Assurance — Security assurance status and reporting problems; Governance, compliance and assurance
• Asynchronous interfaces — Submitting work and retrieving results
• Asynchronous jobs — Confidential jobs: tracking, cancelling and retrieving results
• Attestation — Cryptographic foundations and trust roots
• Audit records — Audit trails and tamper-evident logging; Design note: selective disclosure and audit records
• Audit trails — Audit trails and tamper-evident logging
• Auditor access — Visibility controls and selective disclosure; Sharing selected results with auditors and partners
• Auditors — Participants and roles
• Authentication — Request abuse and replay protection; Approving actions: authority and multi-party approval
• Authorisation — Approving actions: authority and multi-party approval
• Availability — Development status: what exists today and what does not; Availability and changes

B

• Backpressure — Service levels and admission control
• Backup — Deployment, backup and recovery: what operators would plan for
• Benchmarks — Evaluation methodology and published results
• Building on Cubane — Integrating an application end to end
• Busy network — Service levels and admission control

C

• Cancelling and refunds — Confidential jobs: tracking, cancelling and retrieving results
• Capability map — Capability map
• Change log — Documentation change log
• Choose your path — Choose your path
• Collusion — Threat model and misbehaviour defences
• Command-line tools — Tools, SDKs and wallet availability
• Committed state — Committed state and inclusion proofs
• Compatibility — Versioning, compatibility and deprecation
• Compliance — Compliance position and data-protection intent; Governance, compliance and assurance
• Compliance position — Compliance position and data-protection intent
• Conceptual reference — Conceptual reference
• Confidential applications — What you could build: intended application patterns; Using outside data in confidential applications
• Confidential computation — Confidential computation; Confidential jobs: tracking, cancelling and retrieving results
• Confidential computation research — Design note: confidential computation with verifiable results
• Confidential jobs — Confidential jobs: tracking, cancelling and retrieving results
• Confidentiality — Privacy and confidentiality: intent and current limits
• Confirmation — Agreement and finality status
• Contracts — Application logic, execution and storage
• Cost estimates — Fees and cost estimates
• Cryptography — Cryptographic foundations and trust roots
• Custody — Custody options for organisations; Organisation workflows with shared approval and custody choices

D

• Data and state — Data and state: how information is recorded and retrieved
• Data availability — Keeping encrypted data available
• Data feeds — Using outside data in confidential applications
• Data protection — Compliance position and data-protection intent; Privacy and confidentiality: intent and current limits
• Data residency — What remains observable
• Data sharing — Visibility controls and selective disclosure; Sharing selected results with auditors and partners
• Data storage — Data and state: how information is recorded and retrieved
• Debugging — Local development environment
• Deployment — Deployment, backup and recovery: what operators would plan for
• Deprecation — Versioning, compatibility and deprecation
• Design notes — Research: problems, properties and open questions
• Deterministic execution — Application logic, execution and storage
• Developer tools — Tools, SDKs and wallet availability
• Development status — Development status: what exists today and what does not; About the Cubane developer documentation
• Devnet — Local development environment
• Disaster recovery — Deployment, backup and recovery: what operators would plan for
• Disputes — Disputes and appeals
• Documentation conventions — Documentation conventions: status labels, dates and reviews

E

• Economic parameters — Treasury and governed economic settings
• Emergency controls — Emergency controls and protocol safeguards
• Encrypted computation — Confidential computation; Processing sensitive data with verifiable results
• Encrypted data storage — Keeping encrypted data available
• Encryption status — Privacy and confidentiality: intent and current limits
• End-to-end integration — Integrating an application end to end
• Enterprise onboarding — Onboarding an organisation
• Errors and failures — What can go wrong: failure and error concepts
• Evaluation methodology — Evaluation methodology and published results
• Evidence — Audit trails and tamper-evident logging; Disputes and appeals
• Examples — How illustrative examples work in this documentation
• Experimental prototype — Development status: what exists today and what does not
• Explorers — Querying network data and browsing activity
• External data — Using outside data in confidential applications

F

• Faucet — Networks and environments
• Features overview — Capability map
• Feedback — Feedback on this documentation
• Fees — Fees and cost estimates
• Finality — Agreement and finality status; Lifecycle stages used in this documentation
• Future developer experience — Future developer experience: what a supported release would add

G

• Getting started — Getting started once a release exists
• Glossary — Glossary
• Governance — Governance, compliance and assurance; Governance proposals and decisions; Treasury and governed economic settings
• Governance proposals — Governance proposals and decisions
• Governed parameters — Governed parameters and policies
• Graceful degradation — Design note: operating under partial failure and evolving participation

H

• Hardware-backed keys — Key lifecycle: creation, rotation and revocation
• Hashing — Cryptographic foundations and trust roots
• How Cubane is intended to work — System model: how Cubane is intended to work for its users

I

• Identity — Identity, keys and access: concepts
• Identity, keys and access — Identity, keys and access: concepts
• Incident response — Emergency controls and protocol safeguards
• Inclusion proofs — Committed state and inclusion proofs
• Installation — Getting started once a release exists; Tools, SDKs and wallet availability
• Integration — Integrating an application end to end
• Intended properties — Problem statement and intended properties
• Interfaces — Interfaces and their status

J

• Job status — Lifecycle stages used in this documentation; Confidential jobs: tracking, cancelling and retrieving results

K

• Key custody — Custody options for organisations; Wallets and the experimental wallet prototype; Cryptographic foundations and trust roots
• Key lifecycle — Key lifecycle: creation, rotation and revocation
• Key management — Key lifecycle: creation, rotation and revocation
• Key revocation — Key lifecycle: creation, rotation and revocation
• Key rotation — Key lifecycle: creation, rotation and revocation; Participant identity
• Known limitations — Known limitations of the experimental prototype

L

• Lifecycle stages — Lifecycle stages used in this documentation
• Limitations — Known limitations of the experimental prototype; Security model, trust and limitations; What remains observable; Assumptions and open questions
• Local development environment — Local development environment

M

• Message propagation — Peer-to-peer networking
• Metadata — What remains observable
• Metering — Fees and cost estimates
• Metrics — Node monitoring and observability
• Migration — Versioning, compatibility and deprecation
• Misbehaviour — Threat model and misbehaviour defences; Penalties for misbehaviour; Design note: accountability for misbehaviour
• Monitoring — Node monitoring and observability
• Multi-party approval — Approving actions: authority and multi-party approval

N

• Networking — Peer-to-peer networking
• Networks and environments — Networks and environments
• Node health — Node monitoring and observability
• Node interface — Interfaces and their status
• Node operators — Operating a node: intended roles and what exists today; Participants and roles

O

• Observability — Node monitoring and observability
• On-chain governance — Governance proposals and decisions
• Open questions — Assumptions and open questions
• Operating a node — Operating a node: intended roles and what exists today
• Oracles — Using outside data in confidential applications
• Organisation onboarding — Onboarding an organisation
• Organisation workflows — Organisation workflows with shared approval and custody choices
• Organisations — Organisation workflows with shared approval and custody choices
• Outside data in confidential applications — Using outside data in confidential applications

P

• Papers — Public references
• Partial failure — Design note: operating under partial failure and evolving participation
• Participant identity — Participant identity
• Participants and roles — Participants and roles
• Peer-to-peer networking — Peer-to-peer networking
• Penalties — Penalties for misbehaviour
• Performance — Evaluation methodology and published results
• Permissions — Approving actions: authority and multi-party approval; Identity, keys and access: concepts
• Persistence — State persistence, snapshots and recovery
• Pricing — Fees and cost estimates
• Privacy — Privacy and confidentiality: intent and current limits
• Privacy accounting — Privacy-protection building blocks in the experimental prototype
• Privacy-protection building blocks — Privacy-protection building blocks in the experimental prototype
• Problem statement — Problem statement and intended properties
• Programming model — Application logic, execution and storage
• Protocol parameters — Governed parameters and policies
• Protocol safeguards — Emergency controls and protocol safeguards
• Public network — Networks and environments
• Public references — Public references

Q

• Querying confidential data — Querying confidential data
• Querying network data — Querying network data and browsing activity
• Quick start — Getting started once a release exists

R

• Rate limiting — Request abuse and replay protection
• Readable names — Participant identity
• Reading paths — Choose your path
• Recorded and final — Lifecycle stages used in this documentation; Agreement and finality status
• Regulation — Compliance position and data-protection intent
• Release notes — Versioning, compatibility and deprecation; Availability and changes
• Release plans — Development status: what exists today and what does not; Future developer experience: what a supported release would add
• Replay protection — Request abuse and replay protection
• Reporting a documentation problem — Feedback on this documentation
• Research — Research: problems, properties and open questions
• Resilience — Design note: operating under partial failure and evolving participation
• Resilience testing — Security assurance status and reporting problems
• Responsibilities — Trust assumptions and responsibilities by participant
• Restart recovery — State persistence, snapshots and recovery
• Retention — Keeping encrypted data available
• Retries — What can go wrong: failure and error concepts
• Retrieving results — Submitting work and retrieving results
• Roles — Participants and roles
• Rollback — Time-delayed execution and staged upgrades
• Running a node — Operating a node: intended roles and what exists today

S

• Sample code — How illustrative examples work in this documentation
• SDK — Tools, SDKs and wallet availability; Submitting work and retrieving results
• SDK availability — Tools, SDKs and wallet availability; Submitting work and retrieving results
• Security assurance — Security assurance status and reporting problems
• Security audit — Security assurance status and reporting problems
• Security model — Security model, trust and limitations
• Selective disclosure — Visibility controls and selective disclosure; Sharing selected results with auditors and partners
• Selective disclosure research — Design note: selective disclosure and audit records
• Sensitive data — Processing sensitive data with verifiable results; What Cubane is designed to do
• Service levels — Service levels and admission control
• Shared control — Custody options for organisations
• Sharing selected results — Sharing selected results with auditors and partners
• Signatures — Cryptographic foundations and trust roots
• Simulated features — Known limitations of the experimental prototype
• Simulation — Confidential computation
• Site map — Topic index
• Slashing — Penalties for misbehaviour
• Snapshots — State persistence, snapshots and recovery
• SQL-style queries — Querying confidential data
• Staged upgrades — Time-delayed execution and staged upgrades
• Staking — Staking and validator participation
• State — Data and state: how information is recorded and retrieved
• State database — State persistence, snapshots and recovery
• State root — Committed state and inclusion proofs
• Status labels — Documentation conventions: status labels, dates and reviews
• Storage for application logic — Application logic, execution and storage
• Submitting jobs — Submitting work and retrieving results
• Submitting transactions — Transaction lifecycle: from submission to result
• Submitting work and retrieving results — Submitting work and retrieving results
• System model — System model: how Cubane is intended to work for its users

T

• Tamper-evident logging — Audit trails and tamper-evident logging
• Templates for use cases — Use-case profiles
• Terminology — Glossary
• Test tokens — Networks and environments
• Testnet — Networks and environments
• Testnet status — Development status: what exists today and what does not
• Threat model — Threat model and misbehaviour defences
• Time-delayed execution — Time-delayed execution and staged upgrades
• Topic index — Topic index
• Trade-offs — Assumptions and open questions
• Transaction lifecycle — Transaction lifecycle: from submission to result
• Transaction lookup — Querying network data and browsing activity
• Transaction status — Transaction lifecycle: from submission to result; Lifecycle stages used in this documentation
• Treasury — Treasury and governed economic settings
• Troubleshooting — What can go wrong: failure and error concepts
• Trust assumptions — Trust assumptions and responsibilities by participant; Security model, trust and limitations
• Trust roots — Cryptographic foundations and trust roots

U

• Upgrades — Time-delayed execution and staged upgrades
• Use cases — What you could build: intended application patterns
• Use-case profiles — Use-case profiles

V

• Validators — Staking and validator participation; Participants and roles
• Verifiable results — Processing sensitive data with verifiable results; What Cubane is designed to do
• Versioning — Versioning, compatibility and deprecation
• Visibility — Visibility controls and selective disclosure; Sharing selected results with auditors and partners
• Voting — Governance proposals and decisions
• Vulnerability reporting — Security assurance status and reporting problems

W

• Wallet availability — Tools, SDKs and wallet availability
• Wallet prototype — Wallets and the experimental wallet prototype
• Wallets — Wallets and the experimental wallet prototype; Identity, keys and access: concepts
• What Cubane is designed to do — What Cubane is designed to do
• What is available today — Development status: what exists today and what does not
• What is Cubane — What Cubane is designed to do
• What is new — Documentation change log
• What remains observable — What remains observable
• What you could build — What you could build: intended application patterns
• Where to start — Choose your path

Assumptions, trust and limitations

An entry is a pointer to a page, not a claim that a capability exists. Being listed in the index says nothing about availability; read the status on the destination page.

Not yet available, and how this page will grow

The index is regenerated whenever pages are added, renamed or withdrawn, and a withdrawn page is removed without description. Entries are added as new topics are documented.

Related pages

• Glossary — definitions of terms, as opposed to routes to pages.
• Capability map — capabilities and their status.
• Choose your path — reading routes by role.

Glossary

Glossary entries are not linked from the index; terms are looked up on the Glossary page.

References

No approved public references yet.