B3 Hive

B3 Hive is the desktop wallet and full-node software for the B3 FlowMesh network. It downloads and validates the B3 chain locally, manages user-controlled keys, and provides the foundation for B3's modern protocol components.

Further information is available in the doc folder.

Programs

• b3coin-qt — B3 Hive desktop wallet
• b3coind — headless full node
• b3coin-cli — RPC command-line client
• b3coin-wallet — offline wallet utility
• b3-bridge-ethcheck — optional bridge proof verifier and canonical payload emitter (-DB3_BRIDGE_TOOLS=ON)
• b3-bridge-bootstrap-proof — optional offline 3-of-4 bootstrap proof and Ethereum initialization-calldata builder (-DB3_BRIDGE_TOOLS=ON)

Linux operator archives also include the automatic Ethereum-to-B3 relayer and its fail-closed operating guide under contrib/b3bridge/. Bridge tools being present in an archive does not activate an unconfigured mainnet bridge.

License

B3 Hive is released under the terms of the MIT license. See COPYING for more information. The source retains the copyright and attribution notices of Bitcoin Core and other upstream projects from which it derives.

Development process

Development branches are built and tested regularly, but are not guaranteed to be stable. Release branches and version tags identify reviewed releases. Check each release's notes for its exact signature and checksum guarantees.

The contribution workflow is described in CONTRIBUTING.md, and useful guidance is available in doc/developer-notes.md.

Testing

Testing and code review are essential for security-sensitive software. Developers are strongly encouraged to add unit tests for new behavior and regressions. Unit tests can be compiled and run with ctest.

Regression and integration tests live under test and can be run with build/test/functional/test_runner.py when their dependencies are installed. Release changes must be tested on all supported platforms.

Manual quality assurance

Changes should be tested by somebody other than the developer who wrote the code, especially when they affect wallet storage, transaction encoding, consensus boundaries, or release packaging. A clear test plan should accompany changes that are not straightforward to verify.

Translations

Translation sources and inherited locale files live under src/qt/locale. See the translation process and translation strings policy before making translation changes.