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

Lazyness in getOrElse could cause disagreement between 6.0 and < 6.0 nodes #1042

Open
kushti opened this issue Dec 10, 2024 · 0 comments
Open
Assignees
Labels
Milestone

Comments

@kushti
Copy link
Member

kushti commented Dec 10, 2024

Something like Some(5).getOrElse(emptyColl(0)) would cause network split. V6 nodes would accept this script because the invalid operation (indexing empty coll) is never evaluated whereas v5 nodes would reject. Unless ErgoTree version is also >= 3 in which case old nodes would not evaluate script

Discovered by @SethDusek

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

No branches or pull requests

1 participant