Zolana
ExplorerDocsGitHubOpen wallet

Docs · Project

What’s new

Additions to the repository that these docs now describe, each with the pull request that merged it. No dates.

Status

None of this changes the status of the project. Zolana’s blockchain is in devnet, devnet test coins are valueless and distinct from the ZOL token issued on Solana, and the blockchain code has not yet been independently audited.

Every item below is in the main branch of the public repository. The number after an item links to the pull request that merged it.

Protocol

  • Protocol specification with test vectors (#26). A statement of the formats and rules the code implements, vectors written by the code, and a second reader written from the text alone. See Protocol specification; the file is docs/protocol-spec.md.
  • Fuzz targets and property tests (#24). One fuzz target for each decoder, property tests for the pool state transition, and two pool-state rules that followed from their first runs. See Testing and verification; the file is docs/protocol-fuzzing.md.
  • Protocol copy guard (#23). A check that compares the workspace’s protocol library and native program, as text, with the copies inside the candidate patch series. See Protocol copy guard.
  • One slot-anchor rule and one runtime binding in the workspace program (#25). The workspace’s native program now has the candidate’s slot-anchor rule and reaches its runtime through one file. The registered workspace program still accepts no NPOOL004 payment. The record is decision 0043.

Tools

  • Supply and pool-backing monitor (#22). A read-only tool that checks the public boundary of the shielded pool and the total supply at one RPC endpoint. It is a tool in the repository; these docs do not present it as running against the devnet. See Supply and pool-backing monitor; the runbook is docs/supply-monitor-runbook.md.
  • Deployment description (#21). The names, directories, service accounts, loopback ports and unit names of one installed network are now held in one place, tools/deployment.py, where the tools used to carry them as typed constants. The document says what its tests do not cover: no second deployment has been started on a host from these tools. The file is docs/deployment-description.md.

Wallet

  • Browser wallet network pin (#20). A browser wallet bundle is built for exactly one network and refuses a gateway that reports another. That identifies the network and proves nothing about its history: the wallet still trusts its endpoint for consensus. The pin is a build input, written into the bundle by tools/browser_wallet_pin.py from the public wallet profile of a network. No network’s genesis hash is written in the repository. The record is decision 0040.

SDK

All in one pull request (#27):

  • Offline JavaScript readers. sdk/js/formats.mjs and sdk/js/explorer.mjs read a payment, the pool account, a shielded address and the explorer feed, with four runnable examples. See JavaScript readers.
  • inspect-payment. A command that decodes a payment and checks its signatures and its proof offline. See Verify a payment offline.
  • Fixtures. Real payments with real proofs, and the pool account after them, in sdk/fixtures.
  • Cookbook. Five recipes, each checked by a test. See Cookbook.

The Developer SDK page lists the parts.

Decision records

Five records were added under docs/decisions. The middle column is each record’s own description of its status.

Decision records added
RecordStatus, in its own wordsPull request
0038: Bridge between the ZOL token on Solana and native ZOL: options“options record, not a decision. Nothing is chosen here.”#18
0039: Key custody on a public network, and a genesis ceremony: requirements and options“design record, not a description of anything that exists”#19
0040: Wallet trust in chain reads: network pin, endpoint agreement, certificate verification“section 1 is a decision and is implemented for the browser wallet. Sections 2 and 3 are design records”#20
0041: What a validator does when a slot cannot be completed“draft for review. Nothing described here is implemented.”#24
0043: One copy of the payment protocol and the native program“draft for review”; two of its three steps are implemented and tested in the workspace#25

In these docs

Releases and the state of the devnet are on Network, releases and roadmap.

Your privacy
has a boundary.

Zolana is an independent blockchain for native shielded deposits, private transfers and withdrawals. The browser wallet creates proofs and decrypts its own notes locally.

Shielded details

Payment amounts and receiving addresses are protected by proofs. Your spending and viewing keys stay on your device.

Public evidence

Blocks, timing, fees, nullifiers and public deposit or withdrawal accounts and amounts remain visible.

The invited gateway knows your membership and receiving address. It sees your IP address and request timing and can link your submissions. This is not a claim of complete anonymity.

Valueless test coins. No Solana bridge, SOL/USDC deposits, post-quantum protection or audited-security claim.