-
Notifications
You must be signed in to change notification settings - Fork 6
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
feat: added runestone to reveal tx #28
Conversation
This reverts commit 4660214.
src/wallet/builder.rs
Outdated
// tx out | ||
#[cfg(feature = "rune")] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This feature-based logic inside a method seems like something impossible to support in future, and would probably not work correctly for some use cases.
What's even more confusing is that the type is called OrdTransactionBuilder
using RevealTransactionArgs
but we build a runestone transaction instead that has nothing to do with ord or with reveal.
I think if we want to use this crate in future, it would be better to invest some time to refactor the code to be less confusing and more correct.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@Maximkaaa Actually etching requires an inscription. I agree with your point, so at least I've created a dedicated function for this in the rune module.
Motivation
Added the possibility to pass the runestone to the reveal transaction. This allows etching and minting for runes.
Changes
Added
runestone
argument to Reveal transaction args.