Clients "inspecting and modifying the transactions" is explicitly *not*
supported. There should be more than enough features for clients to get
bitcoind to generate the exact block they want already available via
Bitcoin Core. The only reason transactions are exposed over the work
protocol at all,
Really like that you're moving forward with this. A few months ago I was
working on something similar as it seemed like nobody else was interested.
In regards to the specific proposal, would it make sense to offer a tx
subscription endpoint in addition to TRANSACTION_DATA_REQUEST? Such an
Been working on this one for a while, so its already been through a few
rounds of feeback (thanks to all those who already have provided feedback)!
At a high level, this meets a few goals:
1) Replace getblocktemplate with something that is both more performant
(no JSON encoding, no full
