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

mempool, netsync, electrum, main, peer: Use utreexotx #214

Merged

Conversation

kcalvinalvin
Copy link
Contributor

We favor utreexotx instead of having a separate utreexo encoding for a transaction message.
The code here changes the code so that CSNs ask for utreexotxs and the CSNs and bridges
send over utreexotxs.

@kcalvinalvin kcalvinalvin force-pushed the 2024-11-05-add-leaves-in-addtransaction branch from 8c486c8 to f49a19f Compare November 8, 2024 10:00
addUtreexoData saves the proof and the leaves in memory, allowing us to
propagate proofs for transactions as a utreexo csn node.
Instead of using the UData that's currently part of the MsgTx, we take
in utreexo data and use that to verify txs for utreexo nodes. This is
done to support MsgUtreexoTx while reusing the same code as we currently
do.
We're favoring a new message over a utreexo encoding for propagating txs
for utreexo nodes. So when we're pushing out txs for utreexo tx invs,
send out utreexotxs.
We add support for handling utreexotx messages that we receive from
peers.
@kcalvinalvin kcalvinalvin force-pushed the 2024-11-05-add-leaves-in-addtransaction branch from f49a19f to f1236df Compare November 8, 2024 10:16
Since txs don't serialize udata anymore, this code doesn't change
anything about the behavior of the code but makes it much more explicit
that udata will not be serialized for txs.
@kcalvinalvin kcalvinalvin merged commit 6368725 into utreexo:main Nov 11, 2024
2 checks passed
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

Successfully merging this pull request may close these issues.

1 participant