Interconnected nodes
Participants connect to one another and exchange messages. The network does not require a central server to operate.
This page explains the role of nodes and the status of public BI3LYX network information. No chain height, peers, or statistics are simulated.
PUBLIC NETWORK STATUS
No sample values are shown. These indicators will remain empty until a reliable public API is connected.
General principles
These concepts are general. BI3LYX-specific topology and parameters will be published separately.
Participants connect to one another and exchange messages. The network does not require a central server to operate.
Transactions and blocks travel from peer to peer. Each node applies its known rules before relaying data.
A node does not trust its neighbor: it checks received data against protocol rules.
Run a node
A public node serves the network, but must never expose wallet secrets. The final procedure will be published with the official release.
Read the installation frameworkA 64-bit Linux server, a non-privileged account, backups, and controlled administrator access.
Compare the SHA-256 hash and signature with those published on the Downloads page.
Final configuration files, ports, and options will be provided with the official release.
Monitor logs and disk space. The node's RPC must never be exposed publicly.
Public information
Every item has an explicit status. Missing data is never replaced with an estimate.
| Information | Status | Publication condition |
|---|---|---|
| Chain height | Unavailable | Requires the public API |
| Peer count | Unavailable | No fabricated data |
| Protocol version | To be published | With the technical documentation |
| Default ports | To be published | With the installation guide |
| Hardware requirements | To be published | With the official node release |
| Public explorer | In preparation | Interface ready, API not connected |
Access to this website does not depend on BI3LYX nodes. If the network is unavailable, the overview pages, documentation, and announcements remain accessible.
Public statistics must never reveal an operator's IP address, private key, recovery phrase, or wallet identity.