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

Improve MWEB documentation #881

Open
uwuforever opened this issue Feb 27, 2023 · 0 comments
Open

Improve MWEB documentation #881

uwuforever opened this issue Feb 27, 2023 · 0 comments

Comments

@uwuforever
Copy link

uwuforever commented Feb 27, 2023

I'd like to build in MWEB support on some of my tools, but I'm noticing that a lot of the docs seem outdated. For example, the link for LIP-0005, which other pages mention as describing data serialization, is entirely dead. Is there anywhere I can get reliable documentation/test vectors? If not available at the moment, could I get clarification on how a peg-in transaction works?

I'm trying to set it up so that users without a full node can be given a kernel commitment script to pay to instead, like [ltc1ffy0qvmhg9rfh38f2lpnenjy9wnmdv33ces37amxkzq3qmkwz8sssm68cr7](https://blockchair.com/litecoin/address/ltc1ffy0qvmhg9rfh38f2lpnenjy9wnmdv33ces37amxkzq3qmkwz8sssm68cr7). Currently I'm going off the assumption that the longer getrawtransaction output, before it gets cut-through at 6 confirms, is the full transaction format that would have to be sent, and I'm trying to pull it apart. But the behavior I see on testnet transactions doesn't quite match the docs - as an example, https://github.com/litecoin-project/lips/blob/master/lip-0003.mediawiki suggests there should only be a single EB output, but all peg-in transactions seem to have 2.

Current progress: serialization.txt

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

1 participant