Stratum v2 Template Provider via IPC interface (multiprocess) #48
Conversation
|
@ryanofsky I slightly mangled e373642 because of bitcoin@4e1a434#r1681193702. I'll clean that up later. |
|
Incorporated the changes from bitcoin#30437 (comment) and cleaned up commit history. |
|
@ryanofsky do you have a commit somewhere that adds libmultiprocess to the guix build? |
Sjors
force-pushed
the
sv2-ipc
branch
2 times, most recently
from
c75792b
to
91720b7
Compare
|
Getting a cryptic Somehow related to the Template Provider depending on I can't make sense of the |
Sjors
force-pushed
the
2024/07/sv2-tp-common
branch
2 times, most recently
from
db58076
to
1ff4660
Compare
Sjors
force-pushed
the
sv2-ipc
branch
3 times, most recently
from
4354e96
to
3aa6f0a
Compare
Sjors
force-pushed
the
2024/07/sv2-tp-common
branch
from
1ff4660
to
ee010f5
Compare
|
re: #48 (comment)
I don't, since I haven't really experimented with the guix build. Maybe simplest approach to start with would enable the multiprocess build option and build and package all the multiprocess executables including bitcoin-tp and bitcoin-node. I know in the longer run you want to have separate releases as described in bitcoin#30437 (comment). re: #48 (comment)
This is a -bitcoin_mine_CPPFLAGS = $(bitcoin_bin_cppflags)
+bitcoin_mine_CPPFLAGS = $(bitcoin_bin_cppflags) $(BOOST_CPPFLAGS)to add the right -isystem option.
Not sure about this error. Link seems to be https://cirrus-ci.com/task/4759864851824640?logs=ci#L2486 |
Sjors
force-pushed
the
2024/07/sv2-tp-common
branch
2 times, most recently
from
19cc9f1
to
dabc32c
Compare
Sjors
force-pushed
the
sv2-ipc
branch
3 times, most recently
from
6c24b45
to
a8bb152
Compare
|
I'm getting the MSAN / TSAN error inconsistently on my self-hosted CI. Does not seem related to this PR. Trying to reproduce in isolation in #51. |
|
Rebased. The guix build for Some CI failures are expected due to #49 (comment) (update: temporary disabled these tests for this PR) |
Sjors
force-pushed
the
sv2-ipc
branch
2 times, most recently
from
b93bc8a
to
b2ad32f
Compare
|
Here's a release binary to try it: https://github.com/Sjors/bitcoin/releases/tag/sv2-tp-0.1.10-ipc |
Sjors
force-pushed
the
2024/07/sv2-tp-common
branch
from
735e934
to
c413ad7
Compare
|
New release tag, binaries underway: https://github.com/Sjors/bitcoin/releases/tag/sv2-tp-0.1.12-ipc |
Sjors
force-pushed
the
2024/07/sv2-tp-common
branch
from
c413ad7
to
9cac0b8
Compare
Except for Windows. Co-Authored-By: fanquake <[email protected]>
It's left disabled for the test each commit job. The bitcoin-node binary is built on all platforms which have multiprocess enabled, but for functional tests it's only used in the macOS native job. TODO: * ASAN * valgrind
Allows InitError and InitWarning to be used by other executables beside bitcoind and bitcoin-node.
See src/bitcoin-mine.cpp for usage information. Co-authored-by: Sjors Provoost <[email protected]>
The Template Provider binary: * won't have a wallet * probably won't have a gui (maybe after the QT revamp) * doesn't use the functional test framework Disable some CI stuff to speed it up. This is not a complete list, because: 1. That would be too hard to rebase 2. Some things might be added later, e.g. tracepoints
For now also build bitcoin-node.
This is a very sloppy merge conflict resultation between bitcoin#31283 and bitcoin#31318. A temporary overload is added so that the test can be modified in the next commit.
This is an alternative approach to #68. Rather than integrating the Template Provider directly into Bitcoin Core, we make it an entirely separate application that communicates via IPC, see design/multiprocess.md.
Usage
Compile as usual, multiprocess is enabled by default.
Alternatively get a recent binary, see (unofficial, by me) releases ending in "ICP".
Start node:
Start the Template Provider:
See general Stratum v2 usage instructions in bitcoin#29432.
Rationale, PRs this builds on
There are multiple ways to create such an application. It could be built from scratch in Rust, using bits and pieces of the Stratum Reference Implementation SRI. It could be a c++ application built from scratch, perhaps using some libraries from Bitcoin Core.
But this PR goes about in a slightly different way. Similar to Elements or Knots it's a set of patches on top of the full Bitcoin Core codebase. This allows me to leverage the build system, subclass
Transportand use various other useful bits.This lets me reuse almost all code from the integrated Template Provider bitcoin#29432. Both build direct on:
This PR relies on the interface and build changes listed in bitcoin#31098. These interface changes are also used by bitcoin#29432, but there they run in the same process.
I modified the guix script to only produce
bitcoin-node(for now) andbitcoin-minebinaries.Goal
The goal is to drop
bitcoin-nodefrom the release here. Ideally users would install Bitcoin Core in the manner they're familiar with. They would then installbitcoin-mineseparately and it should just work(tm), at most having to add a line tobitcoin.confto turn IPC on.This won't work until we ship a release with multiprocess and the mining interface enabled, ideally in
bitcoindandbitcoin-qtrather than in seperatebitcoin-nodeandbitcoin-guibinaries. See bitcoin#30437 for progress towards that.It might eventually be feasible to complete separate the codebase. A first step towards that would be to turn
libbitcoin_netinto a library (see #47). However for the time being I'd rather rebase on Bitcoin Core, which I'm familiar with anyway, than maintain an entire (guix) build system myself.