A Bitcoin full node written from scratch in Odin — consensus validation, P2P networking, mempool, storage, RPC, and dashboards, with only C dependencies Bitcoin Core itself uses (libsecp256k1, LevelDB).

Fully synced and verified on mainnet — tip hash and UTXO totals cross-checked against the public network — plus signet, testnet4, and testnet3. 378 tests across 13 packages.

• Full consensus validation — script interpreter (P2PKH through Taproot), all deployed soft forks, parallel script verification, parallel prevout prefetch (warms the UTXO cache from LevelDB across worker threads for faster cold-cache IBD), assumevalid
• Headers-first IBD with multi-peer download, compact blocks (BIP152), and encrypted v2 transport (BIP324) with automatic v1 fallback both ways
• Bitcoin Core-compatible surface — 87 of Core v30's 94 non-wallet RPCs (incl. the BIP174 PSBT family), cookie auth, bitcoin.conf-style config, Core CLI flag names, electrs runs against it unmodified
• ZMQ notifications — Core's zmqpub* interface via a native ZMTP 3.0 implementation (no libzmq), LND-ready
• Crash-safe by construction — chunked atomic flushes, undo-based recovery with live progress, bounded rollback depth, single-instance lock
• Pruning (--prune), background UTXO flushes, sync ETA
• Tor-ready — --proxy routes all outbound P2P through SOCKS5 with proxy-side name resolution (no DNS leaks); .onion peers via --connect
• Drivechain (BIP300/301) — opt-in --drivechain=track|enforce: sidechain proposal/withdrawal tracking, escrow (CTIP) validation, blind merged mining. Full ecash/drivechain node support (running forseti on the drivechain hardfork chain) is in the works
• Dashboards — instant-start GUI window (raylib), SSH-friendly TUI (ncurses), and a standalone remote client (forseti-gui)
• First-run setup wizard (--wizard) — a menuconfig-style ncurses flow that writes your forseti.conf and prints the exact command to start
• Runs headless or as a daemon (--daemon) — forks, detaches, and logs to <datadir>/debug.log, like bitcoind -daemon

Prebuilt binaries (macOS arm64, Linux x64/arm64) are on the releases page. Or build from source:

git clone --recursive https://github.com/Galaxoid-Labs/forseti.git
cd forseti && make

./forseti --network=signet --datadir=~/forseti-signet --gui   # small network, syncs fast
./forseti --network=mainnet --datadir=~/forseti --dbcache=4096 --prune=2000 --gui

Requires the Odin compiler, LLVM 15+, and make — full details in docs/build.md.

Not sure what to configure? Run the wizard — a menuconfig-style ncurses flow that asks the handful of decisions that actually vary per user (network, data directory, full vs pruned, cache size, RPC auth, dashboard, plus an Advanced toggles screen), then creates the data directory, writes a forseti.conf, and prints the exact command to start:

./forseti --wizard

It writes the config and exits without touching the network — everything it doesn't ask keeps its default and can be edited in the conf afterward.

Instead of passing everything on the command line, drop a forseti.conf in your data directory — the node reads <datadir>/forseti.conf at startup. The format is INI-style, mirroring Bitcoin Core's bitcoin.conf (# comments, key=value, optional [network] sections). CLI flags override the file.

# ~/forseti/forseti.conf
network=mainnet
dbcache=1024
prune=2000
rpcuser=alice
rpcpassword=hunter2

./forseti --datadir=~/forseti --gui        # everything else comes from the conf

A fully-commented contrib/forseti.conf.sample lists every supported key with its default. Copy it and uncomment what you need:

cp contrib/forseti.conf.sample ~/forseti/forseti.conf

Full mainnet initial block download (genesis → chain tip), measured:

On a fast CPU with hardware SHA-256, IBD is I/O-bound — UTXO reads dominate over script verification — so a fast NVMe and a large --dbcache help most. See docs/hardware.md for backend details and recommendations.

MIT