Six functional layers with shared chain rules.
PBE's reference implementation separates consensus primitives, node orchestration, network behavior, persistence, merchant services and browser-facing integration while preserving a single chain identity.
Functional layers
| Layer | Responsibility |
|---|---|
| Core | Transactions, blocks, state transitions, emission, participation and validation primitives. |
| Node | Synchronization, block production, mempool selection and local orchestration. |
| Network | Signed peer hello, endpoint safety, peer exchange and block/transaction relay. |
| Storage | Common persistence abstraction over MySQL/MariaDB and SQLite. |
| Commerce | PBE-PAY payment requests/status plus optional signed webhook watches. |
| Web / Wallet | Explorer/RPC presentation and non-custodial browser signing. |
Deployment models
Web/server deployment selects MySQL/MariaDB and can expose explorer, wallet, developer documentation, Commerce APIs and P2P routes. Standalone deployment selects SQLite, keeps UI/RPC on localhost by default, and exposes a separate P2P listener.
State and persistence
Account state tracks balance and nonce. Canonical blocks and transactions are stored with indexed fields plus raw representations for reconstruction/debugging. Reorganization support uses per-block undo state and transactional database updates.
Merchant separation
Commerce webhook tables are optional. This keeps merchant automation from becoming a hidden prerequisite for validation, synchronization, transaction relay or block production.