Capability map

Development status: Overview — This page lists the capabilities described in this documentation, grouped by topic, each with its own status label and a link to the page that explains it. Labels differ from row to row: some capabilities have an experimental implementation used internally, often with simulated parts, while others are planned, being explored or recorded as research. None is publicly available for live use.

Before you read: About the Cubane developer documentation.

Use this map to find a documented capability by topic, see its own status label and scope limit at a glance, and go to the one page that explains it. The map is a navigation and status aid. It lists only capabilities that are documented at summary level, it is not an inventory of the platform’s design, and none of its rows is available for use.

How to read the map

• Each row gives a plain-language capability name, a one-line intended purpose, its own status label — with a scope limit wherever an experimental implementation exists, such as internal use only or simulated parts — and a link to the page that explains it.
• Rows follow the documentation’s section order.
• Labels belong to rows, not to topics, and can differ within one topic. What each label means is set out on Documentation conventions: status labels, dates and reviews.
• The map lists only capabilities documented at summary level on their own pages. It has no placeholder or “coming soon” rows, and it is not an inventory of the design.
• No row is available for live use. “Experimental implementation exists” means internal prototype work only.

Capabilities by section

Start here

Capability	Intended purpose	Status and scope	Explained on
Platform aim	Let organisations process sensitive data while producing results others can verify	Being explored	What Cubane is designed to do
Experimental implementation for protocol development	An early prototype used inside the project for protocol development and integration work	Experimental implementation exists — internal only; confidentiality, proving and several features of how the network agrees on results are simulated or inactive	Development status: what exists today and what does not

What you could build

Capability	Intended purpose	Status and scope	Explained on
Use-case profiles	Starting profiles that help choose confidentiality and performance settings	Being explored	Use-case profiles
Outside data in confidential applications	Use outside data feeds	Being explored	Using outside data in confidential applications

System model

Capability	Intended purpose	Status and scope	Explained on
Transaction submission and validation	Accept transactions and check them before they are executed	Experimental implementation exists — internal prototype only	Transaction lifecycle: from submission to result
Long-running confidential jobs	Confidential jobs that could be tracked, cancelled and refunded, using specialised hardware workers	Being explored	Confidential jobs: tracking, cancelling and retrieving results
Finality status query	Report whether recorded results are final	Experimental implementation exists — reports nothing as final, because finality is not connected	Agreement and finality status
Service levels and admission control	Differentiated service levels, admission control and backpressure	Experimental implementation exists — internal prototype components only; no service is offered	Service levels and admission control
Demand-based fees	Fees that adjust with network demand	Experimental implementation exists — an experimental calculator that charges nothing	Fees and cost estimates
Metering of confidential computation	Measure confidential computation by the cryptographic work performed	Being explored	Fees and cost estimates

Data and state

Capability	Intended purpose	Status and scope	Explained on
Committed state and inclusion proofs	Commit state under a cryptographic root, with proofs that a value is part of that state	Experimental implementation exists — internal prototype only	Committed state and inclusion proofs
State database and persistence	A state database, and saving and restoring node state across restarts	Experimental implementation exists — internal prototype only; crash safety is not established	State persistence, snapshots and recovery
Deterministic execution	Run application logic deterministically	Experimental implementation exists — internal prototype only	Application logic, execution and storage
Storage for application logic	Storage primitives usable directly from application logic	Being explored — none exists	Application logic, execution and storage
Browsing network activity	Browse blocks and transactions	Experimental implementation exists — internal testing only; richer explorers are being explored	Querying network data and browsing activity
Querying confidential data	A SQL-style way to declare and query confidential data	Being explored	Querying confidential data
Encrypted data availability	Keep encrypted data available and retrievable	Being explored — not available	Keeping encrypted data available

Identity, keys and access

Capability	Intended purpose	Status and scope	Explained on
Participant identity	Keep a participant’s identity separate from the keys, wallets and names that act for it	Being explored	Participant identity
Wallet prototype	A wallet used for internal testing	Experimental implementation exists — internal testing only; not released or supported	Wallets and the experimental wallet prototype
Custody choice	Choose how the signing keys behind funds are held	Being explored	Custody options for organisations
Key lifecycle	Create, rotate and revoke keys under policy, with hardware-backed custody	Planned — not implemented; key handling for encrypted computation is only simulated	Key lifecycle: creation, rotation and revocation
Multi-party approval	Require several approvers for sensitive actions	Being explored	Approving actions: authority and multi-party approval

Privacy and confidentiality

Capability	Intended purpose	Status and scope	Explained on
Confidential computation interfaces	Encrypted-computation interfaces that simulate the intended behaviour	Experimental implementation exists — internal prototype only; simulated, with no real encrypted computation performed	Confidential computation
Visibility controls and selective disclosure	Owner-controlled visibility, time-limited access for auditors, seeing controlled separately from acting, and disclosure of selected results to authorised parties	Being explored — no access-controlled data in the prototype; the reveal step is simulated	Visibility controls and selective disclosure
What remains observable	Set out what remains observable even with confidential processing	Being explored	What remains observable
Privacy-protection building blocks	Building blocks for protecting privacy	Experimental implementation exists — internal prototype only; several protections are simulated	Privacy-protection building blocks in the experimental prototype

Security, trust and limitations

Capability	Intended purpose	Status and scope	Explained on
Defences against misbehaviour	Layered defences against misbehaviour	Being explored — none implemented	Threat model and misbehaviour defences
Signature and hashing algorithms	Use established signature and hashing algorithms	Experimental implementation exists — internal prototype only	Cryptographic foundations and trust roots
Trust roots	Certificate-based trust and optional hardware attestation	Being explored — not implemented	Cryptographic foundations and trust roots
Rate limiting and replay checks	Per-caller rate limiting and basic replay checks	Experimental implementation exists — internal prototype only	Request abuse and replay protection
Context scoping	Scope messages to their intended context	Being explored	Request abuse and replay protection
Security assurance	Security review, resilience and recovery testing	Planned — no audits or measurements are published	Security assurance status and reporting problems

Operations and participation

Capability	Intended purpose	Status and scope	Explained on
Peer-to-peer networking	Peer-to-peer networking and message propagation	Experimental implementation exists — internal prototype only; no public network	Peer-to-peer networking
Node monitoring	Basic node status and metrics	Experimental implementation exists — internal prototype only	Node monitoring and observability
Local multi-node test setup	Run a local multi-node test setup for internal testing	Experimental implementation exists — internal only; production deployment, backup and recovery procedures are not specified	Deployment, backup and recovery: what operators would plan for
Emergency controls	Scoped, time-limited emergency controls requiring several approvers	Experimental implementation exists — an experimental library, not connected to any network	Emergency controls and protocol safeguards
Staking	Staking for validators	Planned — not available on any network	Staking and validator participation
Penalties for misbehaviour	Penalties for misbehaviour	Experimental implementation exists — an experimental library; nothing is enforced	Penalties for misbehaviour
Treasury and governed economic settings	A treasury and economic settings adjusted through governance	Being explored	Treasury and governed economic settings

Governance, compliance and assurance

Capability	Intended purpose	Status and scope	Explained on
Governance proposals and decisions	Propose and decide changes	Being explored	Governance proposals and decisions
Governed parameters and policies	Parameters and policies set through governance	Being explored	Governed parameters and policies
Time-delayed execution and staged upgrades	Let approved changes take effect after a delay, and introduce upgrades in stages	Being explored	Time-delayed execution and staged upgrades
Disputes and appeals	Raise and resolve disputes and appeals	Being explored	Disputes and appeals
Tamper-evident audit logging	Audit logs in which later alteration would be detectable	Experimental implementation exists — an experimental library, internal only	Audit trails and tamper-evident logging

Future developer experience

Capability	Intended purpose	Status and scope	Explained on
Local development environment	A local development environment with debugging aids for confidential workloads	Planned	Local development environment
Submitting work through language SDKs	Submit confidential jobs and retrieve results through language SDKs	Planned — no SDK is available	Submitting work and retrieving results

Conceptual reference

Capability	Intended purpose	Status and scope	Explained on
Developer-facing node interface	Submit transactions and query node state	Experimental implementation exists — internal testing only; the broader interface design is being explored	Interfaces and their status

Research

Capability	Intended purpose	Status and scope	Explained on
Operating under partial failure and evolving participation	Study how the network would keep operating when some participants are unavailable, and as participation evolves	Research	Design note: operating under partial failure and evolving participation

Availability and changes

Capability	Intended purpose	Status and scope	Explained on
Internal tooling	Onboarding, operations and simulation tooling	Experimental implementation exists — internal testing only; not released	Tools, SDKs and wallet availability
Test-funds library	A library for issuing test funds	Experimental implementation exists — internal code only; no public network or faucet	Networks and environments

Assumptions, trust and limitations

• Labels reflect the documented status as of this page’s date. Maturity is assessed per capability and may change, and every change is recorded in the Documentation change log.
• “Experimental implementation exists” means internal prototype work only — not availability, completeness, security or performance.
• One-line descriptions summarise intent. The page each row links to holds the explanation, the limits and the open questions.
• The map does not rank, compare or prioritise capabilities, and its order implies no delivery order.

Not yet available, and how this page will grow

Once releases exist, each row would show the release in which the capability became available and link to its versioned reference. Rows are added only when a capability is documented at summary level on its own page; rows may also be reworded or removed, and each such change is recorded in the change log. Further technical reference is not yet available.

Related pages

• Development status: what exists today and what does not — the status hub that explains the labels in context.
• About the Cubane developer documentation — how status is signalled throughout the documentation.
• Glossary — definitions of the terms used in row descriptions.
• Topic index — lookup by reader vocabulary rather than by capability.
• System model: how Cubane is intended to work for its users — how the system-model capabilities fit together for users.

Glossary

• Status label
• Experimental implementation
• Confidential computation
• Inclusion proof
• Finality
• Selective disclosure
• Backpressure

References

No approved public references yet.