You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Recently bitcoin core added an optional parameter to the sendrawtransaction call to limit intentional burns. It was implmented in this commit. This was released in Bitcoin Core 25.0.
Whereas there was no default limit prior to 25.0, the default is now set to 0, meaning sending non-zero values to OP_RETURN via sendrawtransaction will fail by default.
To keep pre-25.0 functionality intact, users of that RPC call (electrum servers, among others) will need to send the new maxburnamount parameter in the RPC call, which will also require sending the previously unset maxfeerate.
The text was updated successfully, but these errors were encountered:
BamaHodl
pushed a commit
to BamaHodl/Fulcrum
that referenced
this issue
Jun 30, 2023
#182)
* issue #181 preserve pre-25.0 functionality for sendrawtransaction and fix one small typo (Vulberable)
* make BTC version check specific to BTC
---------
Co-authored-by: BamaHodl <BamaHodl@github.com>
Recently bitcoin core added an optional parameter to the sendrawtransaction call to limit intentional burns. It was implmented in this commit. This was released in Bitcoin Core 25.0.
Whereas there was no default limit prior to 25.0, the default is now set to 0, meaning sending non-zero values to OP_RETURN via sendrawtransaction will fail by default.
To keep pre-25.0 functionality intact, users of that RPC call (electrum servers, among others) will need to send the new maxburnamount parameter in the RPC call, which will also require sending the previously unset maxfeerate.
The text was updated successfully, but these errors were encountered: