No published packages
The Developer SDK is version 0.1 and source only: a directory in the repository with examples, a build script, types and an RPC client. It is not a package, and these gaps remain:
| Missing | What the repository shows |
|---|---|
| Published Rust crates | Nothing is on crates.io. All crates are version 0.1.0. native-wallet-core and zolana-browser-core are marked publish = false, and no crate carries registry metadata such as a description or repository field. |
| An npm package | There is no package.json in the first-party tree. |
| A prebuilt Wasm module | None. sdk/build-browser-core.sh builds the single-threaded package from source, with tools you install yourself. The compiler flags for the threaded package are not recorded in the repository. |
| A JavaScript wallet library | None. The SDK has TypeScript types for the browser core and a JSON-RPC client. The sync, storage and recovery logic exists only in the browser wallet’s worker, which is plain JavaScript written for the wallet page. |
| A way to send payments from your own Rust program | None outside the workspace. The instruction builders and everything that signs and sends transactions are in crates that depend on node/agave. |
| Stable formats | The wire format is “not a released protocol”, and identifiers are development values. |
| A separate examples repository | None. The examples are the six programs in sdk/rust-examples, the runbooks, the harness scripts and the tests. |
| Continuous integration | One workflow, .github/workflows/checks.yml, runs on pull requests: the format check, Clippy and the tests of the six packages that build without the validator, and the JavaScript suites. The validator, the native program, the command-line wallet and the Python suites are not covered; for those tools/check.sh is run by hand. |
What to do instead
Build from source. Start with the Developer SDK: its quick start runs an example in four commands.
git clone https://github.com/zolanacom/zolana.git
cd zolana
sh tools/dev.sh fetch --locked
Inside the workspace the crates refer to each other by relative path. These lines are from the repository’s own manifests and show the form:
# clients/wallet-core/Cargo.toml
native-payments = { path = "../../protocol/payments", default-features = false }
# clients/cli/Cargo.toml
native-payments = { path = "../../protocol/payments" }
Which crate to start from:
native-paymentsfor encoding, decoding and verifying payments. It depends onorchardand a few small crates, not on the vendored validator.native-wallet-corefor proof construction and history replay. It also has no dependency on the vendored validator.native-wallet-seedfor the encrypted seed file.native-walletandnative-payment-programdepend on crates insidenode/agaveby path and build only within the workspace.
From outside the workspace, depend on the first three as Git dependencies pinned to a commit. The Developer SDK page has the manifest lines and says how they were checked. There is no compatibility promise between commits; follow changes by reading the history.
For a browser integration, build the Wasm core with sdk/build-browser-core.sh, use the SDK’s types, and read product-worker.js as the reference for everything the SDK does not package.
No open developer network
What the gateway and admission code in the repository enforces:
- Only admitted wallets get through. Every gateway method except the
getGenesisHashhandshake requires a signed access proof from an active member. A test asserts that an unauthenticatedsendTransactionis not forwarded. - Admission needs an invitation, and a cohort is finite. The cohort tooling pins 10 invitations and 10 grants.
- The browser wallet’s path relays shielded payments only. Its gateway has no
sendTransaction. Its one write method accepts a single shape: a 9,230-byte shielded-fee payment for this network, paying this relay. - The invited RPC gateway used by the command-line wallet does list
sendTransactionfor admitted members and forwards it without inspecting the transaction. - Validator RPC is not exposed. It is an operator interface.
What that means for a third party today: without a place in a cohort you cannot send transactions to, or read wallet history from, the public devnet. The explorer page is the only public read, and it shows a recent window.
The repository does not describe deploying programs on the devnet, and nothing in these docs should be read as support for it. The design records list general private smart contracts as deferred. Which gateway and settings the hosted devnet actually runs is not part of the repository.
Develop against a local network instead.
Also not there
- No public RPC endpoint and no public faucet. Test coins come only as a cohort grant.
- No way to run a validator on the devnet. There is no procedure for an outside operator to join.
- No explorer API. The explorer reads a same-origin file in a format versioned
v0. - No light client. Wallets trust their RPC endpoint for consensus.
- No viewing-key export and no watch-only mode in the wallets.
- No second asset. The shielded pool holds only the native coin.
- No bridge. Nothing in the repository implements one.
- No signed wallet packages, and no testing on physical phones or Safari.
- No independent audit.
This page describes the present state. It is not a list of commitments.