PBE CORE 0.0.1
Run, secure and maintain a Paybyte node.
A PBE node can validate, relay and synchronize without producing blocks. Block production is a separate operator-authorized function, and merchant webhooks are an optional feature rather than a consensus requirement.
Two supported storage profilesWeb/server deployments use MySQL or MariaDB. Standalone deployments ship with SQLite for a self-contained local node.
Node responsibilities
| Role | Behavior |
|---|---|
| Validation | Checks transaction, block, state and consensus rules before canonical storage. |
| Synchronization | Discovers compatible peers and follows the canonical branch using common-ancestor reorganization support. |
| Relay | Exchanges signed transactions, blocks, hello messages and bounded peer hints. |
| Block production | Optional. Requires an operator wallet binding and authorization of the machine producer key. |
| Commerce | Payment verification is available without custody; signed webhook management is opt-in. |
Operator paths
Install and startUnderstand web/server and standalone deployment modes.StorageSee what ships with each deployment and how chain data is stored.Authorize the nodeBind the non-custodial operator wallet without putting its private key on the server.Connect peersExpose only the required listener and verify chain identity.
Protocol details
Node operators configure and maintain the software here. Developers implementing the peer wire protocol should use the separate P2P protocol reference.