Issue Details

Number

31348

Title

Add support for creating v3 raw transactions in `createrawtransaction` RPC

Description

### Please describe the feature you'd like to see added. Currently, `createrawtransaction` RPC creates only v2 raw transaction, i.e. the first byte of the serialised transaction hex is `02`. It'd be helpful for the RPC to conditionally create V3 raw transactions if such intent is passed in the arguments of the RPC call. ### Is your feature related to a problem, if so please describe it. _No response_ ### Describe the solution you'd like - A new argument to the RPC call can be passed that allows the user to create v3 raw transactions conditionally. It can be either a `bool isV3` or `int version` (with sanity checks) whichever is most compatible with the current RPC nomenclature. - Default transaction version need not change as part of this solution. ### Describe any alternatives you've considered _No response_ ### Please leave any additional context Need to double check for conformity of v3 raw transactions with other RPCs. Though I didn't notice any issue with signing and broadcasting v3 transactions after manually updating the hex during testing TRUC transactions while coming up with [V28 Testing Guide](https://github.com/bitcoin-core/bitcoin-devwiki/wiki/28.0-Release-Candidate-Testing-Guide#2-v3-transactions-truc).

URL

https://github.com/bitcoin/bitcoin/issue/31348

Closed by

Notes

Attention of

Kill Factor (1-10)

Save

Back to List