Skip to content
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

rpcclient: no way to set 'verbosity' parameter on GetBlock rpc call #2092

Open
Avionic23 opened this issue Jan 4, 2024 · 5 comments
Open

Comments

@Avionic23
Copy link

No description provided.

@Avionic23 Avionic23 changed the title rpcclient: no way to set parameter 'verbosity' parameter on GetBlock rpc call rpcclient: no way to set 'verbosity' parameter on GetBlock rpc call Jan 4, 2024
@joseguru
Copy link

joseguru commented Mar 5, 2024

Hey @Avionic23 , I would like to pick up on this issue. Any progress on your end?

@joseguru
Copy link

joseguru commented Mar 6, 2024

@Avionic23 Just went through the docs and I found GetBlockVerbose function which returns a data structure from the server with information about a block given its hash. I think this should help

@Avionic23
Copy link
Author

Hey @joseguru. Sorry, I was busy, couldn't respond you. There is a possibility to set verbose parameter '3' for block rpc and the response data structure is different from '2' (the input of the transaction includes previous PK script with all related info). I didn't find any related function with '3' verbosity in btcd package, so I implemented it on my own

@Avionic23
Copy link
Author

Screenshot 2024-03-06 at 17 11 19

@Avionic23
Copy link
Author

@joseguru As you can see the '2' parameter is hard-coded in RPC request for GetBlockVerboseTx function. For GetBlockVerbose function the '1' parameter is passed. Also, there is a possibility to pass '3' parameter, but I assume you cannot find that in the documentation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants