Networks and environments
Development status: Status and changes — As of this page’s date there is no public network of any kind, neither a main network nor a public test network, and no public endpoint, network identifier, faucet or distribution of test funds; no connection between Cubane and any other network is available. An experimental implementation, experimental onboarding, operations and simulation tooling, and an experimental library for issuing test funds exist for internal development and testing only. Nothing is publicly available for live use.
Before you read: Development status: what exists today and what does not.
Is there a public network, test network, endpoint or faucet you can use? No. This dated status page states what does not exist, what exists only internally, what an announcement of an environment would contain once one exists, and what developers and prospective operators can do in the meantime. It gives no internal environment names, endpoints or identifiers.
The short answer
- There is no public network: neither a main network nor a public test network.
- No public endpoint, network identifier or connection detail is published.
- There is no public faucet, and no test funds — sometimes called test tokens — are distributed.
- No connection between Cubane and any other network is available.
- Nothing on this page can be used to connect to anything.
What exists internally
Status of this section: Experimental implementation exists — internal only.
An experimental implementation exists for protocol development and integration work. It is an early prototype, not a public network. Experimental onboarding, operations and simulation tooling exists for internal testing, and an experimental library for issuing test funds exists in internal code; no public faucet service is available.
Internal development and test setups are not test networks: they are not public, not reachable and not announced. Their names, addresses and identifiers are not published, and activity in them is not evidence of how a public network would behave.
Faucets and test funds
A faucet is a service that gives out test funds so that developers can try out a test network.
- No public faucet service is available, and no test funds are distributed.
- The experimental faucet library exists in internal code only. Its limits and protections are not described here and should not be assumed to work.
- If test funds were offered with a future test network, how to obtain them and any limits would be announced with that network.
- Treat with caution any offer of Cubane test funds, network access or endpoints that does not come from this documentation; none are published here.
What an environment announcement would include
Status of this section: Planned — this describes what an announcement would contain once an environment exists; no environment or launch is announced.
Once an environment exists, its announcement would be expected to cover:
- the environment’s name and purpose, such as development or testing, with its status and level of support;
- the software version it runs, and how upgrades and resets would be announced;
- how to connect, including endpoints and network identifiers;
- whether test funds are available, and how to obtain them;
- known limitations, including whether the environment is suitable for any real data.
Exact environment names, endpoints and identifiers are not yet available, and this documentation does not announce any network or launch.
What you can do now
- Learn the concepts that do not depend on a network, starting with System model: how Cubane is intended to work for its users and Lifecycle stages used in this documentation.
- Keep network details out of application code, so that they can be supplied once an environment exists; Interfaces and their status describes the current status of each kind of interface.
- Do not use real funds, real keys or real data with any experimental software; Known limitations of the experimental prototype explains why.
- Follow this page, the status hub and the Documentation change log for changes.
Assumptions, trust and limitations
Statements on this page are dated; anything not stated here as available should be treated as unavailable. Internal environments are not evidence of a future public network’s behaviour, performance or availability.
Not yet available, and how this page will grow
When an environment exists, this page would list it with the announcement details above, its as-of date and its version identity, and the status hub and change log would be updated. Exact environment names, endpoints and identifiers are not yet available.
What this page does not claim
This page does not claim that any of the following exists or is available: a public network or public test network; a public endpoint or network identifier; a faucet or distributed test funds; a connection to any other network; or launch plans or dates. Anything not stated here as available should be treated as unavailable.
Related pages
- Development status: what exists today and what does not — the status hub for the whole documentation.
- Tools, SDKs and wallet availability — the status of developer and operator tooling.
- Operating a node: intended roles and what exists today — what prospective operators can and cannot prepare.
- Getting started once a release exists — the planned first-run sequence, including configuring an environment.
Glossary
References
No approved public references yet.
