Development status: what exists today and what does not
Development status: Status and changes — An experimental implementation exists for internal protocol development and integration work; it is an early prototype in which confidentiality and proving features are simulated or switched off and finality is not connected, so it provides no confidentiality protection, and its tooling is for internal testing only. There is no public network, no publicly released tool, SDK or wallet, no faucet and no published release plan or date. Nothing is publicly available for live use.
Before you read: About the Cubane developer documentation.
This is the single status hub for the documentation. It answers the question most readers arrive with — what can I actually use today? — and then summarises what the internal experimental implementation covers, what it does not, how status is labelled on every other page and where the detailed availability pages are.
The short answer
Nothing described in this documentation can be used publicly today. There is no public network or test environment, no publicly released tool, SDK or wallet, no faucet and no public interface endpoint. For your own planning, that means there is nothing to connect to, install or build against yet.
An experimental implementation exists for protocol development and integration work inside the project. It is an early prototype and should not be relied on for security or production use.
No release dates, release plans or phasing are published, and this page does not predict when anything will become available.
The table below summarises status by area. The second column says whether internal experimental work exists; the third says whether anything is publicly available, and today the answer in every row is no.
Status at a glance, by area:
| Area | Internal experimental work | Publicly available | Read more |
|---|---|---|---|
| Networks and environments | Internal development and test setups only; none is a public or test network | No | Networks and environments |
| Tools, SDKs and wallets | Experimental onboarding, operations and simulation tooling, for internal testing only; language SDKs are planned | No | Tools, SDKs and wallet availability |
| Test funds | An experimental library for issuing test funds; no faucet service | No | Networks and environments |
| Transactions and execution | Submission, validation, deterministic execution and recorded state in an internal prototype | No | Transaction lifecycle: from submission to result |
| Finality | An experimental status query that reports nothing as final | No | Agreement and finality status |
| Confidentiality and proving | Simulated or switched off; no confidentiality protection | No | Privacy and confidentiality: intent and current limits |
| Fees | An experimental calculator that charges nothing | No | Fees and cost estimates |
| Operator deployment and recovery procedures | A local multi-node test setup for internal use; no procedures specified or published | No | Deployment, backup and recovery: what operators would plan for |
What the experimental implementation covers, in outline
Status of this section: Experimental implementation exists — internal prototype work only; not released, with several parts simulated.
- In outline, the internal prototype exercises submitting and validating transactions, executing them deterministically and recording the resulting state on a node. Transaction lifecycle: from submission to result gives the detail and its limits.
- An experimental finality status query exists, but it reports nothing as final because the finality component is not connected.
- An experimental fee calculator exists, but it charges nothing.
- Experimental onboarding, operations and simulation tooling and a local multi-node test setup exist for internal development and testing only. Neither is a public product or a test network, and activity in them is not evidence of how a public network would behave.
- An experimental library for issuing test funds exists, but no public faucet service is available.
- The Capability map gives every documented capability its own label; rows labelled “Experimental implementation exists” mark the areas where internal prototype work exists.
What is simulated, inactive or absent
- Confidentiality: encrypted computation is simulated. No real encrypted computation is performed, so the prototype provides no confidentiality protection.
- Proving: proving features are simulated or switched off.
- Agreement: several features of how the network agrees on results are simulated or not connected, and no result is reported as final.
- Economics: no fees are charged, and no staking or penalties operate on any network.
- Operations: production deployment, backup and recovery procedures are not specified or published.
The complete list lives on Known limitations of the experimental prototype; this page summarises it and links there.
How status is labelled across the documentation
- Experimental implementation exists — internal prototype work exists. The page says “An experimental implementation exists; this page describes the intended public developer capability.” and always states its scope limit, such as internal use only, simulated parts or not released.
- Planned — the design is specified, and the developer experience is described conditionally: “The planned developer experience would allow…” or “Once this capability is implemented, enabled and publicly released, developers are expected to…”. Planned material is not a commitment.
- Being explored — the design is unsettled: “The design is being explored; its public interface and support are not settled.”
- Research — goals, assumptions and open questions: “This note records goals, assumptions and open questions; nothing here is an assurance or a released feature.”
- Status and changes — dated availability statements only.
- Overview — orientation pages that carry the site-wide notice and block labels.
Labels describe maturity, not availability, quality or assurance. “Experimental implementation exists” never means usable, released, reviewed or secure, and nothing is publicly available whatever the label.
Each page carries the label of its primary capability, and any block whose maturity differs carries its own label. Label changes are dated in the Documentation change log, and the full conventions are on Documentation conventions: status labels, dates and reviews.
Where to find details
- Networks and environments — which environments exist (none publicly) and what would be announced when one does.
- Tools, SDKs and wallet availability — the status of developer and operator tooling.
- Known limitations of the experimental prototype — the full limitations list.
- Security assurance status and reporting problems — no independent audit results or resilience measurements are published.
- Versioning, compatibility and deprecation — no versions or compatibility promises exist yet.
- Documentation change log — dated changes, including status-label changes.
Release plans and dates
No dates, release plans or phasing are published. If a reviewed statement about release phasing is approved, it would appear here with its date and be recorded in the change log. Until a release exists, no environment name, version identity or support period is given anywhere in the documentation.
Assumptions, trust and limitations
- Status statements describe the state of development as of this page’s date; they are not commitments.
- Behaviour of the internal prototype is not evidence of future performance, security, confidentiality or availability, and this page reports no test results.
- Experimental work on one part is not evidence that related planned parts exist.
- Anything not stated here as available should be treated as unavailable.
Not yet available, and how this page will grow
When a supported environment or release exists, this page would list it with its date, version identity, what it includes and excludes, and the support offered. Capability labels across the documentation would be updated at the same time, and each change would be recorded in the change log. Exact environment names, endpoints and installation commands are not yet available.
Related pages
- About the Cubane developer documentation — scope of the documentation and the site-wide notice.
- Networks and environments — environment availability in detail.
- Tools, SDKs and wallet availability — tooling availability in detail.
- Known limitations of the experimental prototype — the full limitations list.
- Documentation conventions: status labels, dates and reviews — complete label definitions and review dates.
- Capability map — each documented capability with its own label.
- Documentation change log — dated record of status changes.
Glossary
References
No approved public references yet.
