MAINNET Home node
Get started
Run additiond --mainnet on your machine — the same model as Bitcoin.
The public site explorer and /api/rpc follow ADDITION_MAINNET_V1
(seed 34.27.30.115:38546). Research testnet remains available as a separate chain.
Public mainnet
Public product: network_id=ADDITION_MAINNET_V1.
Anyone can run a home node, sync from the public seed, and mine —
the same model as bitcoind against a known bootstrap peer.
Public seed: 34.27.30.115:28546 (P2P) and
34.27.30.115:38546 (HTTP).
Site /api/rpc proxies that read path.
Separate chain from research testnet (28545 / 38545).
Full runbook: docs/MAINNET_RUNBOOK.md.
Mainnet ports
| Port | Role |
|---|---|
| 38546 | Public HTTP on the seed (/rpc?cmd=getinfo). Site /api/rpc points here. |
| 28546 | Public P2P bootstrap on the seed |
| 8546 | Write RPC on 127.0.0.1 only — never publish. Site wallet send uses this via /local-rpc. |
Start a mainnet node
Set ADDITION_PRIVACY_MASTER_KEY (32+ characters), build additiond from main, then:
export ADDITION_PRIVACY_MASTER_KEY='replace-with-32-or-more-chars____' export ADDITION_ENABLE_P2P_RPC=1 additiond --mainnet --data-dir $HOME/addition-mainnet --local-rpc-port 8546 --p2p-port 28547 --bootstrap 34.27.30.115:28546
Type sync on the daemon stdin (or send it to write RPC on 127.0.0.1:8546), then getinfo. Mine on that same loopback write RPC when you want to produce blocks (memory_hard).
Never --bootstrap 34.27.30.115:28545 for mainnet (that is the research testnet seed). Never publish port 8546. Auto-mine is refused on mainnet.
Mainnet public read
curl -s 'http://34.27.30.115:38546/rpc?cmd=getinfo' curl -s 'https://additionblockchain.com/api/rpc?cmd=getinfo'
Expect network=mainnet and network_id=ADDITION_MAINNET_V1. Height may still be 0; copy only fields the node prints. Do not invent peer counts or TPS.
On the seed, createwallet / mine may answer on 38546. wallet_send / keys stay disabled on that public port. The site wallet never opens public send — it spends only through /local-rpc → loopback.
Seed operator: ADDITION_ADVERTISED_P2P=34.27.30.115:28546 so public getinfo / peers list that IPv4 endpoint and do not list self.
Research testnet
Separate research chain (ADDITION_TESTNET_V1). Not the public product on this site.
| Port | Role |
|---|---|
| 38545 | Public read RPC for the research chain |
| 28545 | P2P bootstrap for the research chain |
| 8545 | Write RPC on 127.0.0.1 only. Never publish. |
Start a testnet node
Build additiond from main, then:
additiond --network testnet --data-dir $HOME/addition-testnet --local-rpc-port 8545 --p2p-port 28547 --bootstrap 34.27.30.115:28545
Type sync on the daemon stdin (or send it to write RPC on 127.0.0.1). Height should move.
addpeer after --bootstrap is invalid/duplicate (the seed is already listed).
Public read (testnet)
curl 'http://34.27.30.115:38545/rpc?cmd=getinfo'
Those curls succeed only when the operator seed answers. If they timeout, run your own --network testnet node.
Seed operator: ADDITION_ADVERTISED_P2P=34.27.30.115:28545.
Local wallet after your node is up
The Wallet page talks only to /local-rpc →
127.0.0.1:8546 (mainnet) or 127.0.0.1:8545 (testnet)
when you run python3 web/serve.py next to the node
(ADDITION_NETWORK=mainnet selects 8546).
On additionblockchain.com, local write is unavailable and the wallet explains how to connect a home node.
Public wallet_send stays disabled on 38546.
Privacy is ML-DSA / SHA3 opening (opening_not_zk), not a ZK circuit. Coinbase is 50 ADD, 100% to the finding miner. Contact: contact@additionblockchain.com