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

Backwards Compatibility for Cursed Inscriptions #2149

Open
veryordinally opened this issue Jun 4, 2023 · 3 comments
Open

Backwards Compatibility for Cursed Inscriptions #2149

veryordinally opened this issue Jun 4, 2023 · 3 comments

Comments

@veryordinally
Copy link
Collaborator

Originally posted by @lgalabru in #2045 (comment)

We may have to add another rule, to get cursed inscription fully backward compatible: satoshis inscribed with a cursed inscription can be re-inscribed, with a cursed inscription (multiple times) or an inscription (only once).
There are many instances of satoshis that have been mis-inscribed in the past (inscription on 2nd input or whatever), and that were re-inscribed correctly later.
With your current spec, the satoshi would be bound to a cursed inscription with the first transaction, and the second, "legit" inscription would fail (because the satoshi is already bound to a cursed inscription). As a consequence, the inscription number sequence as we know it would break.

@veryordinally
Copy link
Collaborator Author

We encountered this issue when implementing #2145 - this is a tracking issue to document the solution we implemented to maintain backwards compatibility.

@BatBushRacks

This comment was marked as off-topic.

@BatBushRacks

This comment was marked as off-topic.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants