protocol 1.7 (WIP)#2
Draft
SomberNight wants to merge 9 commits intospesmilo:masterfrom
Draft
Conversation
This comment was marked as spam.
This comment was marked as spam.
Sorry, something went wrong.
SomberNight
commented
Feb 12, 2025
SomberNight
force-pushed
the
202502_protocol_next
branch
2 times, most recently
from
d32a69e to
c10f63f
Compare
This was referenced Feb 18, 2025
SomberNight
force-pushed
the
202502_protocol_next
branch
2 times, most recently
from
e74e0f1 to
9e02865
Compare
SomberNight
force-pushed
the
202502_protocol_next
branch
from
ff53c91 to
1c30e19
Compare
SomberNight
force-pushed
the
202502_protocol_next
branch
from
1c30e19 to
337b006
Compare
SomberNight
force-pushed
the
202502_protocol_next
branch
from
f17061d to
7911396
Compare
SomberNight
added a commit
to SomberNight/electrum-protocol
that referenced
this pull request
Oct 22, 2025
This is a minimal changeset for a new protocol version. The ideas for the less trivial changes are deferred a bit, just so we get something out. ref spesmilo#2 ref spesmilo/electrumx#90
SomberNight
commented
Feb 26, 2026
|
|
||
| **Signature** | ||
|
|
||
| .. function:: blockchain.outpoint.subscribe(tx_hash, txout_idx, spk_hint=None) |
Member
Author
There was a problem hiding this comment.
note: bitcoin core added a txospenderindex, to be used with the gettxspendingprevout RPC.
ref bitcoin/bitcoin#24539
- see what their API looks like and maybe adapt what we add to that
- in particular we could put
spender_blockhashin the response - they also have an option to put the full tx in the response
- in particular we could put
- This is mostly split off from the protocol 1.5/2.0 specs and ideas in spesmilo/electrumx#90 - notably it does not include the history pagination, and the recursive scripthash status, which are deferred for now
This construction makes it more homogeneous with existing notifications. ref spesmilo/electrumx#303 (comment)
SomberNight
force-pushed
the
202502_protocol_next
branch
from
7911396 to
7efc355
Compare
SomberNight
force-pushed
the
202502_protocol_next
branch
from
7efc355 to
7eb1d59
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
wip