-
Notifications
You must be signed in to change notification settings - Fork 414
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
Feature: add blockchain.outpoint Electrum 1.5 methods in p2p branch #444
Comments
Sounds good, but I prefer adding it when spesmilo/electrumx#90 is officially merged. |
Ok, I understand. I never coded in rust but is it possible to simply cherry pick the content of the last commit in outpoint-rpc branch and apply it to current p2p one to make it work ? The files are not the same but taking the diff of last commit of outpoint branch of rpc.rs and apply it on electrum.rs could make it works, didn't it ? I am just searching a quick way for me to try ^^' (if I have something working I will submit a PR you can merge once Electrum 1.5 is merged too) |
Please note that the |
Ok, so if I understand well, it will just return the "current" status of the outpoint, that's why you don't need to unsubscribe to notifications. |
Could you take a look at what I tried in #446 ? I couldn't test it properly for now because I can't increase verbosity with config file and I don't know how to make a request locally to test the method. Thanks for your help ! |
Many thanks for the contribution! |
The p2p branch uses a db compatible with version 1.5 of Electrum protocol, one of the new features of 1.5 is the outpoint subscription methods to get the spending transaction of an tx output.
I forked btc-rpc-explorer to add a link to spending transaction of an output to the explorer display using this method, like what blockstream.info explorer does. I would like to test it.
It seems that blockchain.outpoint.subscribe was already implemented in outpoint-RPC branch back in nov 2020 but didn't made it to p2p. Could you "merge" it with p2p ? (I guess that some glue code may be needed)
Do we need the unsubscribe method in current electrs implementation to properly avoid flood of subscriptions/notifications ?
Thanks !
The text was updated successfully, but these errors were encountered: