Build on YAZIMAO
Everything you need to start building — documentation, SDKs, APIs, and an open-source protocol you can audit and contribute to.
One place to start building
The developer surface of YAZIMAO: documentation, SDKs, APIs, node onboarding, architecture and the open-source repository. Every entry states honestly what is available today.
Developer Docs
Protocol guides, architecture decisions, and API references — kept in sync with the code.
ExploreNode Guide
What running a node involves — hardware, onboarding steps, and how validator participation will work.
ExploreArchitecture
The layer stack behind the network — consensus, P2P, execution and storage, from top to bottom.
ExploreArchitecture overview
How the layers fit together, from the application layer down to storage. This is the intended architecture — components ship progressively, and nothing here runs on a public network yet.
- 01Application layerWallets · Explorer · dApps
- 02API / SDKRPC · SDKs · developer tools
- 03WASM executionSandboxed contracts · metered gas
- 04State transitionDeterministic · auditable
- 05ConsensusPoS · DAG · BFT finality
- 06P2P networkGossip · discovery · encrypted transport
- 07StorageVerifiable state · content-addressed data
Launch Testnet
A public testnet is the milestone between protocol development and mainnet. When it launches, you'll get test tokens, faucets, and a full suite of explorer and wallet tooling.
- 01Public RPC endpoints
- 02Faucet for test tokens
- 03Explorer for blocks & transactions
- 04Wallet support (mobile & desktop)
- 05Validator onboarding guide
import { YazimaoClient } from '@yazimao/sdk'
const client = new YazimaoClient{
rpcUrl: process.env.NEXT_PUBLIC_RPC_URL,
network: "testnet",
});
// Amounts are integers — never floats
const tx = await client.transfer{
to: "yazimao1",
amount: "1000000",
});
const status = await tx.wait();
// pending → accepted → confirmed → finalizedCode that just works
SDKs give you typed, safe interfaces to the protocol. No floats, no magic — amounts are integers, statuses are explicit, and finality is never overstated.
- TypeScript & Rust SDKs
- Typed transaction & event models
- Explicit status: pending / accepted / confirmed / finalized
- Proof & state verification built in
Public RPC & data APIs
Read the chain, submit transactions, and query indexed data through versioned APIs. Public RPC is separated from validator management endpoints.
Public RPC
Submit transactions and query chain state. Versioned, rate-limited, size-bounded.
Indexer API
Blocks, transactions, accounts, and validators — built for explorers and dashboards.
Versioning
/api/v1 → /api/v2. Breaking changes never silently ship.
Developer Docs
Documentation is a first-class deliverable — written alongside the protocol, recorded as architectural decisions, and kept in sync with the code.
Open Source
The YAZIMAO protocol is developed in the open. Read the code, audit the decisions, and contribute. Transparency is part of the security model.
What ships next
The developer surface follows the protocol. No dates are promised — only sequencing, published honestly as work lands.
Protocol & consensus design
- Architecture & protocol design
- Canonical encoding & test vectors
Core implementation
- Transaction & state-transition execution
- Node coordination, P2P & sync primitives
Genesis · Devnet · Testnet
- Public RPC, faucet, explorer, wallets
- Validator & node onboarding guides
Mainnet & developer ecosystem
- SDKs & versioned APIs
- Builder & creator programs
Full milestone detail lives on the roadmap. Testnet participation is not open yet — nothing here can be joined today.
Build the next generation of open apps
Wallets, games, storage apps, compute markets, and AI creator tools — YAZIMAO is infrastructure for builders and creators. Start with the docs, and join the developer community.