Skip to content

feat: add regtest support with cpunet - #7

Merged
Sansh2356 merged 1 commit into
cpunet-v31.1from
regtest-support
Oct 18, 2026
Merged

Sansh2356 merged 1 commit into
cpunet-v31.1from
regtest-support

Conversation

@zaidmstrr

Copy link
Copy Markdown

Currently, to write and work with the functional test in Braidpool, a regtest node is used to communicate and test. And we can't use any upstream Bitcoin version to do this work because the IPC schema defined should be the same on both sides. The current Braidpool node is configured with the cpunet branch schema, and this can be used for this purpose. Since regtest is a private network, this build will not need to enable any kind of public interactions to work. This commit also disables the use of any other network types (mainnet, signet, testnet, testnet4), and only cpunet and regtest are allowed to run. This also fixes some build warnings.

@zaidmstrr
zaidmstrr force-pushed the regtest-support branch 2 times, most recently from 6358438 to 6a5c581 Compare October 15, 2026 13:22
@zaidmstrr
zaidmstrr changed the base branch from cpunet to cpunet-v31.1 October 17, 2026 17:02
@zaidmstrr
zaidmstrr force-pushed the regtest-support branch 3 times, most recently from 5601881 to bab5cef Compare October 17, 2026 19:45

@Sansh2356 Sansh2356 left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

t-ACK 1668234 now works properly along with cpunet tested locally with long session of mining over both cpunet and regtest respectively over the new built binary and CI is also fixed .

@Sansh2356
Sansh2356 merged commit d6d6467 into cpunet-v31.1 Oct 18, 2026
100 of 104 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants