Tools, SDKs and wallet availability
Development status: Status and changes — As of this page’s date, no SDK, command-line tool or wallet is publicly available and nothing can be installed; exact installation commands and released tooling are not yet available. Experimental onboarding, operations and simulation tooling and an experimental wallet prototype exist for internal testing only, and language SDKs are planned. Nothing is publicly available for live use.
Before you read: Development status: what exists today and what does not.
Which SDKs, command-line tools or wallets can you install today? None. This dated status page gives the status of each kind of tool, explains what internal experimental tooling is and why it is not a starting point, explains why no tool, package or product names are given, and lists what a release would publish for each tool. It contains no installation commands.
The short answer
No SDK, command-line tool or wallet is publicly available, and nothing can be installed today. Exact installation commands and released tooling are not yet available. Experimental onboarding, operations and simulation tooling exists for internal testing only.
Status by kind of tool
- Language SDKs for applications (Planned). The planned developer experience would allow applications to submit confidential jobs and retrieve results through language SDKs. No SDK is publicly available, and supported languages are not listed. See Submitting work and retrieving results.
- Wallets (Experimental implementation exists — internal testing only). An experimental wallet prototype exists for internal testing; no production wallet is available. See Wallets and the experimental wallet prototype.
- Command-line, node and operator tooling. None is released. Experimental onboarding, operations and simulation tooling exists for internal testing only and is not a getting-started path. See Operating a node: intended roles and what exists today.
- Interfaces and local environment. An experimental node interface exists for internal testing, and the broader developer interface is being explored; see Interfaces and their status. A local development environment is planned; see Local development environment.
- Test funds. An internal library only, with no public faucet; see Networks and environments.
The same status in table form; nothing in it is publicly available:
| Kind of tool | What exists internally | Publicly available | Read more |
|---|---|---|---|
| Language SDKs | Planned; none released | No | Submitting work and retrieving results |
| Wallets | An experimental wallet prototype, for internal testing | No | Wallets and the experimental wallet prototype |
| Command-line, node and operator tooling | Experimental onboarding, operations and simulation tooling, for internal testing | No | Operating a node: intended roles and what exists today |
| Interfaces | An experimental node interface, for internal testing; the broader developer interface is being explored | No | Interfaces and their status |
| Local development environment | Planned; none released | No | Local development environment |
| Test funds | An experimental library for issuing test funds | No | Networks and environments |
What internal experimental tooling is
Internal experimental tooling is tooling used within the project for development and testing. It is not released, not supported and not documented for outside use. Output from internal simulation or demonstration tooling is not test evidence and not a network result. Its names, packages and repositories are not published. Do not build against it or treat it as a preview of released tools.
Names and products
This documentation names no tools, packages, products or repositories; planned tools are described by what they would do. A tool is available only if this page says so. No tool is described as production-ready, and no compatibility with other platforms’ tools or wallets is claimed.
What a release would publish for each tool
Status of this section: Planned — this describes what release documentation would contain; no tool has been released.
Once a tool is released, its release documentation would be expected to give:
- the tool’s name and purpose, its version identity and the network and interface versions it supports;
- an official source from which to obtain it, and a way to confirm that a copy is genuine;
- installation instructions and exact commands, with supported platforms and prerequisites;
- release notes, known limitations and support status;
- compatibility and deprecation information, following Versioning, compatibility and deprecation.
What you can do now
- Learn the concepts that the planned tools would rely on; see Future developer experience: what a supported release would add.
- Keep the part of an application that talks to the network separate, so that it can adopt released tooling later.
- Use only synthetic data and test keys with any software, and follow this page and the Documentation change log for changes.
Assumptions, trust and limitations
Statements on this page are dated. A planned tool is not a commitment to release it in the form described.
Not yet available, and how this page will grow
When a tool is released, it would be listed here with its version, date, official source and support status, and the change would be recorded in the change log. If further reviewed information about developer tooling is approved, it would be added here. Exact installation commands and released tooling are not yet available.
What this page does not claim
This page does not claim any tool, package, product or repository name; any command, version, download or supported platform; that any tool is production-ready or compatible with other platforms’ tools or wallets; or any release date. Anything not stated here as available should be treated as unavailable.
Related pages
- Getting started once a release exists — the planned first-run sequence once tooling exists.
- Wallets and the experimental wallet prototype — what the wallet prototype is and is not.
- Networks and environments — network and test-funds availability.
- Future developer experience: what a supported release would add — the planned developer journey.
Glossary
References
No approved public references yet.
