BitcoBoostBCBO — Exchange Integration Guide

1. Blockchain specification

BitcoBoost Core is a full node derived from Bitcoin Core. Integration uses the standard Bitcoin-style JSON-RPC interface, so existing Bitcoin integration code works with minimal changes (network parameters and binary names differ).

2. Build the node from source

The recommended exchange release (v1.0.0) is published under /downloads/releases/ with SHA256SUMS, a GPG detached signature (SHA256SUMS.asc) and the public signing key (bitcoboost-release-pubkey.asc). Linux (x86_64) and Windows (x64) binaries are provided; the full source tree is public. See RELEASE.md for verification steps. Building from source remains the canonical, verifiable path.

# Ubuntu 22.04 example
sudo apt update && sudo apt install -y build-essential libtool autotools-dev automake \
  pkg-config bsdmainutils python3 libevent-dev libboost-dev libsqlite3-dev git

git clone https://github.com/Bitcoboost/bitcoboost-core.git
cd bitcoboost-core
./autogen.sh
./configure --disable-tests --disable-bench --with-gui=no
make -j$(nproc)
# binaries: src/bitcoboostd  src/bitcoboost-cli

3. Config file (bitcoboost.conf)

server=1
daemon=1
txindex=1
listen=1
rpcuser=CHANGE_ME
rpcpassword=CHANGE_ME_TO_A_LONG_RANDOM_STRING
rpcallowip=127.0.0.1
rpcport=18332
# addnode=seed1.bitcoboost.com
# addnode=seed2.bitcoboost.com
# addnode=seed3.bitcoboost.com

Place it in the data directory (~/.bitcoboost/bitcoboost.conf). Never expose the RPC port to the public internet; keep rpcallowip restricted to localhost or your backend hosts.

4. Run the daemon

bitcoboostd -daemon
bitcoboost-cli getblockchaininfo      # wait until "blocks" == "headers" (fully synced)
bitcoboost-cli getnetworkinfo

A minimal systemd unit:

[Unit]
Description=BitcoBoost node
After=network-online.target

[Service]
User=bitcoboost
ExecStart=/usr/local/bin/bitcoboostd -conf=/home/bitcoboost/.bitcoboost/bitcoboost.conf
Restart=on-failure
TimeoutStopSec=120

[Install]
WantedBy=multi-user.target

5. Wallet RPC

6. Deposit detection

1. Assign each user a unique address with getnewaddress "user_id".
2. Poll for new blocks (or use -blocknotify). On each new block, call listsinceblock "<last_processed_blockhash>" 1 true to get incoming transactions and the new lastblock to store.
3. Credit a deposit only after it reaches the recommended number of confirmations (see §7). Read confirmations from gettransaction.
4. Ignore category: "immature" / coinbase outputs until they reach 100 confirmations (coinbase maturity).
5. Handle reorgs: a transaction can show confirmations: -1 if its block was orphaned (see §9).

7. Recommended confirmations

These are conservative defaults for a 10-minute Proof-of-Work chain. The network also ships hard-coded checkpoints, distributed through verified releases, in the node to protect chain history; exchanges may tune the numbers to their own risk policy.

8. Withdrawals

# single withdrawal
bitcoboost-cli sendtoaddress "bb1…" 12.5 "" "" false

# fee control (recommended: set a fee rate)
bitcoboost-cli -named sendtoaddress address="bb1…" amount=12.5 fee_rate=10

# batch multiple withdrawals in one transaction
bitcoboost-cli sendmany "" '{"bb1aaa…":1.0,"bb1bbb…":2.5}'

Use a hot wallet with a limited balance for automated withdrawals and keep the bulk of funds in an offline (cold) wallet. Always validateaddress before sending. Confirm withdrawals to users after the transaction is included in a block.

9. Reorg handling

• Track the block hash you last processed. On each poll, if getblockchaininfo's best chain no longer contains it, walk back to the common ancestor and re-scan.
• A deposit whose transaction returns confirmations: -1 was orphaned — reverse any provisional credit and wait for it to re-confirm.
• Requiring 20+ confirmations (§7) makes practical reorg impact negligible for standard deposits.

10. Node updates

1. Watch GitHub Releases for new versions and the minimum supported version.
2. bitcoboost-cli stop, replace the binaries, restart the daemon. The data directory is compatible across minor versions.
3. Verify the release checksum (SHA256SUMS) before deploying.

11. Testing your integration (regtest)

The fastest way to test a BitcoBoost integration end-to-end — deposits, confirmations, withdrawals and reorg handling — is a local regtest network, where you mine blocks on demand with no faucet and no waiting.

Verified: the full deposit → 20-confirmation crediting → withdrawal → node-restart persistence flow was tested end-to-end against BitcoBoost Core v1.0.0 on 2026-08-21 (12/12 checks passed).

bitcoboostd -regtest -daemon
bitcoboost-cli -regtest createwallet "test"
ADDR=$(bitcoboost-cli -regtest getnewaddress)

# mine 101 blocks so the first coinbase matures (coinbase maturity = 100)
bitcoboost-cli -regtest generatetoaddress 101 "$ADDR"
bitcoboost-cli -regtest getbalance          # ~50 BCBO spendable

# simulate a user deposit, then confirm it
DEP=$(bitcoboost-cli -regtest getnewaddress "user_1")
bitcoboost-cli -regtest sendtoaddress "$DEP" 5
bitcoboost-cli -regtest generatetoaddress 1 "$ADDR"   # 1 confirmation
bitcoboost-cli -regtest listsinceblock

# test a withdrawal
DEST=$(bitcoboost-cli -regtest getnewaddress "withdrawal_test")
bitcoboost-cli -regtest sendtoaddress "$DEST" 2

Regtest uses the same code paths and RPC as mainnet, so behaviour you validate here matches production. A public testnet (P2P/faucet) can be provided on request for exchanges that require shared-network testing.

12. Support

Technical and listing contact: support@bitcoboost.com. Operated by Primaris Group S.r.l.s. (Torino, Italy). See also the exchange listing page, block explorer, and the live coin / network APIs.

This document is provided for exchange integration purposes. BitcoBoost is open-source software provided without warranty; mining and holding BCBO involve risk. Nothing here is a promise of listing, value or return.