-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
fix verbocity in getblock command #1232
fix verbocity in getblock command #1232
Conversation
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.
Looks good. I can confirm it works with new bitcoind, and new codes are covered in test cases. Maybe we need some feedback from core teams, to decide whether we should share common fields between the types or just make a copy like I did.
Cool. How can I contact or cast core team members? It looks like there are a lot of open pr here. I don't mind a copy. It will also remove extra logic from "btcjson/help.go". But "verbose == 1" and "verbose == 2" responses are similiar except the one field (tx). So I thought that the "rpcserver.go/getblock" would be repetitive. |
Totally agree. I have no idea how to contact core devs, and I believe they have some conventions about merging similar types. So maybe our best bet is waiting (?) |
Yep. I am going to wait and the then cast sombody from people. I am afraid that the project is stagnating a little. |
@jrick, hello. Sorry for being annoying, but it's hard to wait without any knowledge about the current situation. |
@reinerRubin Works a treat, tested with bitcoind. |
@reinerRubin |
a174975
to
ee9c8d0
Compare
@galileo-pkm, I have done a rebase and "Bech32HRPSegwit" is correct now. The rebase could break your lock version (dep, glide, etc.), so be careful. But I think it is acceptable for pr branches. |
Looks good, Thanks |
Would love to see this get merged as well! |
@Roasbeef can we merge this? |
@jcvernaleo (as per #1530)
Linked Issues: Not having this prevents #1529 from being merged |
yeah - your correct here. I misread the test output- #1529 is a newer version of this which adds more params |
Closing since #1529 supersedes this. |
"getblock" command new verbosity levels were implemented in the BTC-core 0.15.0 [1 (see "The verbose argument of getblock")]. So you can easily get a block within all txs. It is a very useful feature.
But unfortunately rpcclient does not support a new format, when lot of people use "rpcclient" with standart bitcoin-core.
It's yet another pr. But I tried to add some tests, keep rpcserverhelp.go and rpcserver in an working state.
1 - https://github.com/bitcoin/bitcoin/blob/3c6286873e50248717afd7c56c664cee069c76fa/doc/release-notes/release-notes-0.15.0.md
issue: #1230
new pr: #1231
old pr: #1112