PBE Core 0.0.1

Build on Paybyte.

PBE is an account-based blockchain with non-custodial browser signing, public blockchain RPC, peer-to-peer node operation, and PBE-PAY merchant payments. Paybyte.org exposes a public primary node, explorer, wallet and these developer docs; compatible self-hosted nodes use the same protocol.

Mainnet releasePBE 0.0.1 uses chain PBE-MAINNET, network ID 1, protocol 1.0, block format v4 and transaction format v2. Mainnet addresses begin with pbe.

Architecture

Layer	Release behavior
Accounts	Account-based state with balance and nonce. 1 PBE = 100,000,000 base units.
Transactions	Ed25519-signed transfer-only transaction v2. Optional signed paymentReference is part of the transaction payload.
Blocks	Block v4 with producer key, reward wallet, transaction root, state root, consensus root and hybrid participation proof.
Consensus	15-second slots. One Argon2id participation ticket per authorized wallet per slot. 0 PBE is eligible; confirmed holdings provide a bounded timing multiplier.
Wallet	Non-custodial browser wallet. Password and private key stay in the browser; signed transactions are sent to the node.
Commerce	PBE-PAY v1: exact recipient + exact amount + signed payment reference, with optional merchant-owned signed webhooks.
Settlement	Canonical-chain confirmation depth. hardFinality=false in 0.0.1.

Where to start

Accept a paymentCreate a PBE-PAY request, open the wallet, and verify it server-side.Fulfil automaticallyReceive HMAC-authenticated payment events from a merchant-controlled node.Sign transactionsImplement transaction v2 serialization and Ed25519 signing.Run a nodeOperate a full node or authorize local block production.

Trust model

Paybyte does not need custody of merchant funds. The recipient is a merchant-controlled PBE address, the customer signs locally, and payment proof is stored on the blockchain. A merchant may query Paybyte.org or any compatible node it controls. Webhooks are an optional convenience layer built from blockchain state; they are not the source of truth.

No hard finalityOne confirmation means inclusion in the current canonical chain. Applications handling meaningful value should use an appropriate confirmation target and handle chain reorganizations.

Base URL

HTTPS

https://paybyte.org

Replace this with your own compatible node URL when self-hosting. Public RPC routes are under /rpc/. P2P routes are under /p2p/.