obenblock
The full node: validates SHA-256d blocks and PoWit finality, relays on port 18110 and serves RPC on 18210 (bound to localhost by default).
DOWNLOADS
ObenBlock's release binaries are published at launch, together with their checksums, the genesis block hash and the DNS seed. Nothing is published yet: there is no ObenBlock network to join before then. The code base is open and builds from source today.
01 / RELEASE
64-bit Linux and macOS. Each release lists its files with SHA-256 checksums.
obenblockThe full node: validates SHA-256d blocks and PoWit finality, relays on port 18110 and serves RPC on 18210 (bound to localhost by default).
obenblock-cliThe RPC client and keystore tool: create a wallet of either signature suite, send, and read the node's finality with getfinalityinfo.
obenblock-walletThe keystore wallet: addresses, public keys, signing and payments against a node's RPC.
| Release files and SHA-256 checksums | At launch |
|---|---|
| Genesis block hash | At launch |
| DNS seed | seed.obenblock.xyz At launch |
| Chain id | 0x4F420001 mainnet · 0x4F420002 regtest |
| Default ports | 18110 P2P · 18210 RPC |
| Peer protocol | /obenblock/pq/1.0.0 |
| Minimum chain work | 0 at launchLater releases set it, and a release finality checkpoint, from independent nodes |
02 / FROM SOURCE
The Rust toolchain is pinned by rust-toolchain.toml; cargo installs it on first use.
git clone https://github.com/gnb-smh/ObenBlock.git cd ObenBlock cargo build --release
Before the relaunch packages land, this build produces the GnB tools (gnb, gnb-cli, gnb-wallet in target/release) and runs the GnB chain. The ObenBlock names, chain ids and genesis come with the packages listed in the relaunch plan.
Regtest (chain id 0x4F420002, obb1t… addresses) is the network for local development and tests. How to start it is documented with the release.
Running a node: requirements, ports and operation are described in docs/RUNNING.md, which is updated for ObenBlock with the release.
03 / YOUR KEYS
The browser wallet and explorer run on this site, against this site's node API.
A GnB keystore (v2 or v3) or the Bloch JSON keystore opens unchanged. Its gnb1… or bloch1… address is shown as the obb1… address of the same script.
Keys are decrypted and used only in your browser tab, inside WebAssembly. Nothing secret is sent anywhere.
Blocks, the GhostDAG, transactions, addresses and holders, read from a node through a read-only API.