# ZooBC Builders

Canonical page: https://zoobc.com/roles/builders/
Audience: Developers, application teams, protocol engineers, testers, and technical contributors
Symbol: The Beaver, turning raw protocols into working environments
Last reviewed: 2026-08-18

Builders integrate with the protocol's actual wire behavior. Chain GET requests may be served from archival history, while transaction POSTs require a full node with a mempool. Some application-state routes are node endpoints rather than archival endpoints.

## Technical contracts

- Every transaction wraps a typed body in a common signed envelope.
- Recipient and memo may live in the envelope rather than the typed body.
- Amounts are integer atomic units: 1 ZBC equals 100,000,000 atomic units.
- Fees should come from live fee parameters or the exact transaction estimator, not a hard-coded interface value.
- Private keys must remain outside servers, URLs, logs, analytics, process listings, screenshots, and support messages.
- Node acceptance is not the same as confirmed chain state.

## First vertical slice

1. Query blockchain status and confirm the target network.
2. Choose one exact transaction type and read its envelope, body, fee, and modifier rules.
3. Build and sign locally using integer atomic amounts.
4. Submit to a full node, retain the identifier, find inclusion, and reconcile resulting movements or state.

Do not progress beyond testnet while the integration can leak keys, confuse display units with atomic units, hard-code stale fees, or report submission as confirmation.

Primary action: Open the developer guide: https://zoobc.com/developer/
Related: https://zoobc.com/api-docs/ | https://zoobc.com/manuals/transactions/ | https://zoobc.com/manuals/cli/ | https://zoobc.com/manuals/apps-manual/ | https://zoobc.com/faucet