Wallets and the experimental wallet prototype
Development status: Experimental implementation exists — An experimental implementation exists; this page describes the intended public developer capability. An experimental wallet prototype exists for local and internal testing; it is not released, it is not a supported product, and no production wallet is available. It has not been reviewed for security, must not be relied on to protect anything of value, and nothing is publicly available for live use.
Before you read: Identity, keys and access: concepts.
Is there a wallet I can use, and what would a Cubane wallet be for? Not yet. No wallet is released or supported, and no production wallet is available. An experimental wallet prototype exists for local and internal testing only. The rest of this page explains what a wallet is intended to do, how it relates to identity, custody, keys and approvals, and what the prototype is and is not.
Is there a wallet I can use? Not yet
- No wallet is released or supported, and no production wallet is available.
- An experimental wallet prototype exists for local and internal testing only.
- The availability of any supported wallet would be announced on Tools, SDKs and wallet availability.
What a wallet is intended to do
A wallet is software that holds the keys that act for an identity and uses them to sign on that identity’s behalf. That role is deliberately narrow, and the intended design keeps a wallet apart from several neighbouring concepts:
- It is not the identity. The identity is intended to stay the same if the wallet or its keys change; see Participant identity.
- It is not the only way to hold keys. An organisation might hold the keys behind its funds in arrangements other than one person’s wallet; see Custody options for organisations.
- Signing is not approving. Signing with a wallet’s key is not the same as having authority to approve sensitive actions; see Approving actions: authority and multi-party approval.
- Keys change over time. How keys would be created, rotated and revoked is described on Key lifecycle: creation, rotation and revocation.
The experimental wallet prototype
Status of this section: Experimental implementation exists — local and internal testing only; not released or supported.
- An experimental wallet prototype exists for local and internal testing.
- It is not released and is not a supported product. No download is offered.
- There is no public network for it to connect to.
- It has not been reviewed for security. It is not described as secure, audited or production-ready.
- Its key formats, key handling, interfaces and internal design are not documented.
The prototype exists to support protocol development. Its existence does not mean that a supported wallet is planned for any particular release.
What a wallet does not do
- It does not define who someone is. It holds keys; the identity is a separate concept.
- It is not a custody service. This documentation does not describe Cubane holding users’ or organisations’ keys, or offering custody services.
- It does not confer approval authority. Holding a wallet does not by itself give authority to approve actions.
- It is not a recovery mechanism. In the intended design, losing a wallet need not mean losing the identity — but only if a recovery path was arranged in advance; see Participant identity.
For developers building wallets or tools
If you are planning a wallet or a tool that would work with Cubane, these are the facts to plan around today:
- Account and address conventions are still being settled and are not yet documented.
- The interface families that exist experimentally are summarised on Interfaces and their status; no released interface exists.
- No compatibility with existing wallets, key formats or other platforms’ account conventions is claimed.
- Versioning and compatibility promises would accompany a release; see Versioning, compatibility and deprecation.
Because none of these is settled, keep the parts of your design that would depend on account formats, key formats or interfaces separate from the rest, so that they can be adapted when reference is released.
Assumptions, trust and limitations
- The prototype must not be relied on to protect anything of value, and no key-protection property is claimed for it.
- Nothing described here about future wallets is a commitment to release one.
- The experimental implementation is an early prototype and must not be relied on for security or production use.
Not yet available, and how this page will grow
Supported wallets, downloads, formats and interfaces are not available. Exact installation commands and released tooling are not yet available. If a supported wallet is released, this page would describe what it does and link to its versioned reference and availability notice. The status label would change only with release evidence.
What this page does not claim
This page does not name any wallet product or offer any download, and it describes no key format or recovery method. It claims no security property for the prototype and no compatibility with existing wallets, key formats or other platforms’ accounts. Anything not stated here as available should be treated as unavailable.
Related pages
- Participant identity — the identity that a wallet’s keys act for, and why it is not the wallet.
- Custody options for organisations — other ways an organisation could hold the keys behind its funds.
- Key lifecycle: creation, rotation and revocation — how keys would be created, rotated and revoked.
- Tools, SDKs and wallet availability — where the availability of any supported wallet would be announced.
- Interfaces and their status — the experimental interface families and where reference would appear.
Glossary
References
No approved public references yet.
