I saw the bitcoin-mining frontend thing from nostr:npub1s6z7hmmx2vud66f3utxd70qem8cwtggx0jgc7gh8pqwz2k8cltuqrdwk4c (and others?) but i didn’t really look into what it does
Just a reacement for GBT but uses capnproto types via IPC. Sv2 spec defines a Template Provider which was implemented by Sjors within bitcoind but also ad a sidecar using IPC. Now that Core is shipping multiprocess, there will be a Sv2 crate developed for Template Provider stuffs.
Lots of fun coming to mining! I want to splice from a coinbase TX.
Very cool, i am so out of touch with latest mining tech
Happy to elucidate whenever.
finally, someone uses capnproto
Its basically flatbuffers + rpc right ?
more
it supports full promise pipelining
it also supports 3-party handoff though only the C++ implementation supports this
everything is capability based
promise pipelining? Fancy. I dunno what 3 party handoff means
You have 3 parties, A, B, C
When A calls B, and it returns a capability X on C, handoff can be done
So B tells C to expect A, and tells A to go to C and pick up the reference.
This way all further calls on X doesn’t go through B but directly from A to C
must be for distributed systems
yes, that was the idea. the RPC protocol was a bit too complicated for some use cases though, and so at least in the capnp-go community at least there is work on a more lightweight protocol that can be stateless depending on the use case + simpler to port while preserving a majority of the features and use cases
