The fee grows with the message size. It's filled in automatically from the network; you can raise it.
Encryption is available only for ZBC → ZBC transfers.
The recipient can claim the amount proportionally as it vests over this period.
Expecting to be paid instead? Request a payment — the receiver-side escrow: you set the amount and approver, the payer funds it.
Amount0 ZBC
Approver commission0 ZBC
Network fee0 ZBC
Total0 ZBC
Share this address to receive funds — or send a payment request: an escrow in the other direction that the payer just approves.
Activity
Contacts
Save people and their addresses across blockchains. Their name shows in place of the address when you send or review activity — the address is always one tap away to copy.
Stored on-chain as an account dataset. A network fee applies, like any transaction.
Datasets — your on-chain entries
Every chat message, poll, invoice, form and profile field is a dataset entry on an account. Read yours here, add new ones, remove ones you created. Rent, access policy & ownership live under the Objects tab.
My entries
Unlock a wallet to list its dataset entries.
Add an entry
Writes a property → value pair on an account (a SetupAccountDataset transaction). Stored on-chain; storage rent applies. Max 4,096 bytes per entry.
0 / 4096 bytes
Remove an entry manually
Removal must match the entry exactly — the account it was set on, the property and the value. Entries listed above have a one-tap Remove instead.
Fund storage (prepay dataset rent)
Top up prepaid storage so your dataset entries live longer before rent expires.
Per-dataset targeting (one account can hold several datasets) is being added on the node; for now this funds your account's storage. Activates on the next blockchain (new transaction type).
Fund any object by creating-tx hash — longevity deposit
Datasets & stored files pay storage rent from a ZBS_ deposit derived from their creating transaction. Top it up so the object isn't pruned. Funding can itself be escrowed (so a sponsor approves it).
Node
Everything for running a validator node — kept separate, since most wallet users won't need it.
My nodes
Every node owned by one of your wallets — across all accounts or one you pick. Name them locally to tell them apart, and copy the keys the actions on the other tabs ask for.
Register a node
Registers a node owned by this wallet. Paste the node's secret key — the wallet builds a proof of ownership from a recent block and signs it. (ZooBC accounts only.)
Staked by the node; the minimum is a blockchain parameter, currently 1 ZBC on this blockchain. The stake is refundable in full, always, even if the node is expelled at zero participation score.
Running a registered testnet node by 14 December 2026 (2 months minimum, 3 or more recommended) is a foundation requirement to join the mainnet registry at genesis. Project roadmap
Remove a node
Deregister a validator node you own; its locked balance is released.
Update node stake
Change the locked stake on a node you own. The new amount can only stay the same or increase. Paste the node's secret key — the wallet builds a fresh proof of ownership.
Claim a node
Re-assign a node's ownership to this wallet, proving control with the node's secret key.
Blockchain economics
What the blockchain charges — storage rent, account rent, gateway stake — is set by the node operators themselves. A vote is signed with your node key; a value takes effect only when 2/3 of all registered nodes have voted for exactly that value. There is no proposer and no admin — a node either agrees with a specific number or it doesn't.
Loading the values in force…
The blockchain doesn't yet publish how many nodes back each value, so no live tally is shown here — your node's vote is recorded on-chain and stands until the parameter changes.
What I transact with
Refuse whole categories of transactions for this account — recorded on-chain and enforced by every node. Turning a category off removes it in both directions: you won’t send or receive it. Anyone who tries is bounced — no funds move; they pay only the network fee.
Loading current policy…
Saving broadcasts a SetTransactPolicy transaction signed by this account — it costs a normal network fee (~0.05 ZBC) and applies once the block settles.
Network
Everything registered on this blockchain, read straight from the node: the gateways wallets connect through, the relays that carry calls & presence, and the archival nodes that serve full history. To register your own, use My infrastructure.
Gateways
The web front wallets talk to. Tap one to connect this wallet to it.
Loading…
Relays
Call signaling and presence. Each relay belongs to a gateway.
Loading…
Archival nodes
Full blockchain history behind “All TX” in Activity.
Loading…
My infrastructure
Everything you run, in one place — register, keep alive and withdraw your gateways, relays and archival nodes. What you already have registered is listed first. To browse the whole network, use Network.
Loading registries…
Register a gateway
Registering it on-chain lets wallets discover it. Locks a 10 ZBC stake (refunded when you unregister) plus the fee. The gateway key is the gateway's 32-byte identity public key (can be the node's key). Heartbeats are emitted automatically by the running gateway — there's no button for them here.
ZBG_XXXXXXXX_XXXXXXXX_XXXXXXXX_XXXXXXXX_XXXXXXXX_XXXXXXXX_XXXXXXXX
The ZBG_ address of the key below — it updates live as you type or generate.
Generate one above, or — if the gateway server is already running — copy the key the gateway installer printed at setup (it's in the server's env/config). The gateway's public endpoint never exposes it.
Unregister a gateway
Withdraw a gateway you registered; its 10 ZBC stake is refunded.
Register / update a relay
Publish a relay for discovery: which gateway it serves, and where to reach it. (The off-chain relay-bind certificate below still authenticates it — this record only makes it findable.)
Copy it from the relay server — the relay installer prints it at setup (also in the relay's env file), or from Relay key & certificate below if this wallet generated it. It isn't exposed on any public endpoint.
Relay key & certificate
A relay is the call/presence server your gateway runs. The wallet generates its ZBR_ key and a certificate signed by your gateway's ZBG_ key — no transaction, no fee. Paste the output into the relay server's /etc/zoobc/relay.env and restart it; its log then shows [fed] ON and it links to peer gateways. Re-run any time to rotate the relay key.
Register / update an archival node
An archival node is one of your registered nodes that also serves full history + the explorer API. This record puts the Archival badge on it in the explorer.
Copy it from the node server — the node installer prints it at setup (also in the node's startup log). The node's public API doesn't expose it.
Governance
Decide together — community polls and network fee votes, all on-chain.
Polls
A poll is an on-chain record, like a form: a question with options, a description, a voting window, and eligibility rules. Each vote is a signed transaction from the voter's account; tallies read straight from the blockchain.
Loading…
Fee voting
Vote the network fee scale up or down — 1.0× = normal. The median of all node votes moves it, clamped to 0.5×–2.0× per period. Voting is two steps: commit your vote (hidden as a hash), then reveal it in the reveal window. This device remembers your committed vote so you can reveal it.
Keys & seeds
One seed phrase can hold accounts on several blockchains. Name your seeds, then add ZooBC, Ethereum, Bitcoin or Solana accounts from each — no need to re-enter the phrase.
Imported keys & watched addresses
Active transactions
Transactions that are live right now and may need an action from you.
Act on a transaction by ID
Not listed above? Paste any transaction ID — the wallet detects whether it's an escrow, a liquid payment or a vesting/recurring schedule and opens the matching action.
Approve or reject an escrow
As the named approver, release the held funds to the recipient or send them back.
Stop a liquid payment
Halt a liquid payment you started; the unvested remainder returns to you.
Stop a vested / recurring schedule
Schedules you created that are still running. Revoking returns the unfired remainder to you; tranches already delivered stay with the recipient.
Stop a schedule by ID
Works even when it isn't listed: enter the ID of the transaction that created the schedule. The unfired remainder returns to the sender; tranches already delivered stay put.
Multi-sig
An account that needs several people to approve each transaction.
Registering records the participant set on-chain. "Add to my wallet" lets you select it as an account (marked with a multisig badge) to receive and propose spends.
Spend from a multisig account: this builds the transfer, adds your signature (the wallet selected in the top bar must be a participant), and broadcasts it as a proposal. Co-signers find it under “Sign multisig transaction” and the spend executes automatically the moment enough have signed.
A co-signer sent you a multisig transaction to approve? Paste it below and sign with the wallet selected in the top bar; then pass the result to the next signer, or broadcast once enough signatures are collected.
Signing never broadcasts anything by itself — the signed payload is copied so you can send it to the next participant. “Broadcast” opens Submit a signed transaction with it prefilled.
Tokens
Create a token backed by ZBC, or send one you hold. Backed tokens keep a constant ZBC value (burning redeems your share).
Issue a token
Send a token
Mint or burn
Mint (issuer only, mintable tokens) adds supply and locks more backing so unit value stays constant. Burn (redeemable tokens) destroys your tokens and returns your share of the backing. For Finance, the amount above is ZBC: it is spent as the transaction fee, which is what buys the token's storage persistence.
Submit a signed transaction
Broadcast a transaction that was signed elsewhere (e.g. on an offline / air-gapped wallet). Paste its data below, or scan its QR code. No key is needed here.