A Bitcoin Core node on our infrastructure, deployed the house way (generic.md §3, §6–§10): systemd unit with hardening, sysusers drop-in, firewalld service for P2P, RPC on loopback only, txindex=0 (the judge watches addresses, it does not look up arbitrary txids), ZMQ or polling for new blocks, and the same for signet so rehearsals run against a chain with no value. Pruning is acceptable if the judge only needs the recent window, and the choice is recorded here with the reason.
Operator decision to record here before starting
The host, and pruned or full.
Acceptance
bitcoin-cli getblockchaininfo shows a synced mainnet node and a synced signet node; the judge can answer "address A received ≥ X with N confirmations by height H" from RPC alone, and the deploy is reproducible from the workflow.
Depends on
Nothing.
Parent: #54
## Scope
A Bitcoin Core node on our infrastructure, deployed the house way (generic.md §3, §6–§10): systemd unit with hardening, sysusers drop-in, firewalld service for P2P, RPC on loopback only, `txindex=0` (the judge watches addresses, it does not look up arbitrary txids), ZMQ or polling for new blocks, and the same for signet so rehearsals run against a chain with no value. Pruning is acceptable if the judge only needs the recent window, and the choice is recorded here with the reason.
## Operator decision to record here before starting
The host, and pruned or full.
## Acceptance
`bitcoin-cli getblockchaininfo` shows a synced mainnet node and a synced signet node; the judge can answer "address A received ≥ X with N confirmations by height H" from RPC alone, and the deploy is reproducible from the workflow.
## Depends on
Nothing.
grenade
added the child label 2026-09-15 14:42:16 +00:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Parent: #54
Scope
A Bitcoin Core node on our infrastructure, deployed the house way (generic.md §3, §6–§10): systemd unit with hardening, sysusers drop-in, firewalld service for P2P, RPC on loopback only,
txindex=0(the judge watches addresses, it does not look up arbitrary txids), ZMQ or polling for new blocks, and the same for signet so rehearsals run against a chain with no value. Pruning is acceptable if the judge only needs the recent window, and the choice is recorded here with the reason.Operator decision to record here before starting
The host, and pruned or full.
Acceptance
bitcoin-cli getblockchaininfoshows a synced mainnet node and a synced signet node; the judge can answer "address A received ≥ X with N confirmations by height H" from RPC alone, and the deploy is reproducible from the workflow.Depends on
Nothing.