-
Notifications
You must be signed in to change notification settings - Fork 381
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
rpc: change getnewblockhex to take multiple commitments #1155
rpc: change getnewblockhex to take multiple commitments #1155
Conversation
e034aeb
to
dd51fcd
Compare
Concept ACK -- heads up you can make this a non-breaking change by explicitly accepting a string and just converting it to an array internally. |
@apoelstra thanks, yeah good point is that preferable? |
Yes, it's much preferable to keep existing RPC scripts working. |
Okay sure will do |
dd51fcd
to
aedacbf
Compare
a2f6bd4
to
ef125af
Compare
ef125af
to
1100877
Compare
utACK 1100877 |
./test/functional/rpc_help.py fails now |
1100877
to
0fe2264
Compare
sorry will take a look |
0fe2264
to
6300b4b
Compare
|
cb20237
to
220de00
Compare
@apoelstra all fixed now |
Modifies the getnewblockhex json rpc call to accept an array of commitments instead of a single commitment. Backwards compatibility is maintained by first attempting to parse as a string for a singular commitment.
220de00
to
5d10ff9
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ACK 5d10ff9
Modifies the
getnewblockhex
json rpc call to accept an array of commitments instead of a single commitment. Backwards compatibility is maintained by first parsing as a string for a single commitment.Adds a new functional test for this rpc call.