Solo Mining Calculator: Estimate Odds and Timeframes
Use a solo mining calculator correctly: enter productive hashrate, network conditions, uptime and time horizon, then read expected time and probability without.
Read article
ASIC mining knowledge centre
Bitcoin Core generateblock RPC: Custom Regtest Block Guide
Bitcoin Core 0.21 generateblock guide covering custom ordered transactions, address or descriptor rewards, mempool txids, raw transactions, validation and isolation.
This guide explains Bitcoin Core generateblock RPC in plain English. It shows what the command does, what its result means and what it cannot prove.
TL;DR
- What it is: Bitcoin Core 0.21.0 introduced generateblock for regtest scenarios that need a block containing a specified ordered transaction set. The required output could be an address or descriptor, and each transaction entry could be raw hexadecimal or a txid already in the mempool.
- Why it matters: generateblock gives regtest users exact block composition control. Its usefulness depends on strict network isolation, deterministic synthetic fixtures and independent verification of the returned block and transaction order.
- Current position: The entire set had to be valid and correctly ordered or the block was rejected.
What this means in simple English
An RPC is a command sent to one Bitcoin Core node. It can ask that node for information or request a local action. A successful reply describes that node; it does not automatically prove what happened across the Bitcoin network.
Beginners can focus on the input, the result and the limit of that result. Operators should test the command on the exact Bitcoin Core version they run before relying on it.
Simple example
Think of a mempool as one node’s waiting room for valid transactions that have not yet entered a block. Different nodes can have different waiting rooms, and the contents can change from one second to the next.
Key terms in plain English
- Bitcoin Core:
- Widely used software that validates Bitcoin and can provide wallet, network and operator tools.
- RPC:
- A command that software sends to a node to request information or a local action.
- Mempool:
- A node’s changing local collection of valid, unconfirmed transactions.
- Node:
- A computer running Bitcoin software that checks data and communicates with other peers.
How specialists test it
Operators test the command on a non-production node first. They check a normal reply, an invalid request, a timeout and a restart. This shows what the response means and prevents one local result from being mistaken for a network-wide outcome.
Reward output
Validate the address network or checksum the output descriptor and retain it as a public fixture. Mining to it does not import the script or prove a signer can spend rewards.
Transaction array
The second argument is required and ordered. Entries can be raw transactions or mempool txids; a txid must already identify a transaction in the node’s current mempool.
Dependency order
Place parents before children and verify inputs, fees, finality, scripts and conflicts. The RPC rejects the whole block when a transaction or ordering rule is invalid.
Immediate state change
A successful call mines before returning and yields one block hash. Record the previous tip, verify new ancestry and contents and account for coinbase maturity in later fixtures.
Privacy and determinism
Raw transactions expose complete test intent to the node and logs. Use synthetic keys and values, fixed fixture hashes and controlled mock time where required.
How specialists test it
Operators test the command on a non-production node first. They check a normal reply, an invalid request, a timeout and a restart. This shows what the response means and prevents one local result from being mistaken for a network-wide outcome.
Frequently asked questions
What is Bitcoin Core generateblock RPC?
Bitcoin Core 0.21.0 introduced generateblock for regtest scenarios that need a block containing a specified ordered transaction set. The required output could be an address or descriptor, and each transaction entry could be raw hexadecimal or a txid already in the mempool.
Is Bitcoin Core generateblock RPC active or supported today?
The entire set had to be valid and correctly ordered or the block was rejected.
Why does Bitcoin Core generateblock RPC matter?
generateblock gives regtest users exact block composition control. Its usefulness depends on strict network isolation, deterministic synthetic fixtures and independent verification of the returned block and transaction order.
Do beginners need to use the technical details?
No. The command is mainly for people who operate Bitcoin Core or software connected to it. Other readers can use the article to understand what an operator or service is measuring.
Conclusion
generateblock gives regtest users exact block composition control. Its usefulness depends on strict network isolation, deterministic synthetic fixtures and independent verification of the returned block and transaction order.
Primary sources
Check the current specification status and the documentation for the exact implementation you operate before moving production funds or changing a mining node.
On this page
Search More Guides
BIP-110 Explained: Rules, Signalling and Why It Closed
BIP-110 explained in detail: its seven consensus restrictions, 55% signalling threshold, chain-split risk and August 2026 closure.
Read article
Bitcoin Core 29.4 Release: Chainstate Disk I/O Guide
Bitcoin Core 29.4 guide covering repeated chainstate rewrites, regular compaction, LevelDB seek compaction, transaction-data lifetime and wallet sizing fixes.
Read article
Need Advice for Your Mining Setup?
Use our guidance to build your shortlist, then speak to our team when you want help comparing hardware, power, hosting or repairs.