NODE OPERATION

Run a PBE node or produce blocks.

A PBE node can validate, relay and synchronize without producing blocks. Block production is an explicit local opt-in authorized by the operator wallet.

Public node status

HTTP

GET /rpc/status

Public status identifies the node software/protocol, PBE-MAINNET, network ID 1, the frozen genesis hash, canonical tip and synchronization state. It deliberately excludes the operator wallet address, its balance and local producer details.

Mainnet identityA compatible 0.0.1 wallet expects genesis <code>75d92b8389173d388e9989b208b8f623e0e88f9059f02e66b73cfbf4c412e5eb</code>. Do not trust a node merely because it claims network ID 1; verify chain ID, protocol and genesis identity as well.

Operator binding

On first launch, bin/pbe-node creates a one-time setup code. The browser wallet signs a binding proof and sends only its public address/public key and proof to the node. The wallet private key never enters the server filesystem.

Windows CMD

cd /d D:\xampp\htdocs\paybyte.org
D:\xampp\php\php.exe bin\pbe-node --config config\config.php

The daemon will print setup instructions until an operator wallet is bound through /wallet/.

On hosted nodes, operator identity is not published through status RPC. After unlock, the bound browser wallet signs an OPERATOR_STATUS challenge to retrieve its private management state. Public callers receive only generic configured/node/network information.

Block production

Enabling block production is a two-step authorization: the node creates/loads a machine producer key, and the bound wallet signs authorization for that exact producer key. The wallet remains the reward identity and receives block rewards and fees.

GET/rpc/mining/status/{address}

Mining status for wallet

Public read

Returns chain-derived participation balance, holding multiplier and reward history. Hosted deployments redact whether the address is the local operator, local producer identity, ticket timing and mining state; standalone localhost can receive those local details.

Parameters

Name	Location / Type	Required	Description
address	path PBE address	yes	Wallet address.

Participation mechanics

Each authorized wallet gets at most one deterministic Argon2id participation ticket per slot. Wallets with zero PBE remain eligible. Confirmed holdings improve the ticket's eligibility timing according to a bounded multiplier schedule. Funds are never locked by consensus.

No manual stakingPBE 0.0.1 has no registry-based producer lifecycle, no registration/exit/withdrawal transaction types, no minimum stake, and no locked-balance account field.