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

Bitcoin Core GUI getrawtransaction implementation #645

Closed
fanquake opened this issue Aug 8, 2022 · 3 comments
Closed

Bitcoin Core GUI getrawtransaction implementation #645

fanquake opened this issue Aug 8, 2022 · 3 comments
Labels

Comments

@fanquake
Copy link
Member

fanquake commented Aug 8, 2022

Bitcoin Core offers sovereignty by people controlling their keys and validating those keys. But many users today hold their keys on hardware wallets or mobile wallets and it's a bit difficult to connect those wallets to a full node and validate them.

The cli users have the option to "getrawtransaction txid true" in order to find valuable information about a transaction that could be theirs. This is a very powerful api call that effectively eliminates the need of an Electrum server.

I think many users would find a lot of value in easily verifying their personal transaction directly from Bitcoin Core GUI!

Something like Help -> Verify external txid. There would need to be an option to enable txindex also. This would greatly increase the use of Bitcoin Core for the ease of validating a transaction. Sure users could create a watch only wallet but these are extra steps that maybe many of the non technical users would get discouraged from doing.

Moved from: bitcoin/bitcoin#19161.

@maflcko
Copy link
Contributor

maflcko commented Feb 13, 2024

Not sure. Seems easier to just use the RPC window, with the benefit that it has more docs and doesn't need an update if the RPC changes.

@hebasto
Copy link
Member

hebasto commented Feb 15, 2024

@zndtoshi @BrandonOdiwuor

Are there any compelling reasons not using RPC in the "Console" window?

@maflcko
Copy link
Contributor

maflcko commented Feb 22, 2025

The feature request didn't seem to attract much attention in the past. Thus, closing due to lack of interest, progress and direction.

Pull requests with improvements are always welcome. Moreover, it is possible to re-open this issue or create a new issue referencing it, if there is fresh interest.

@maflcko maflcko closed this as completed Feb 22, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants