-
Notifications
You must be signed in to change notification settings - Fork 316
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
fix: remove stacking into period3 check #1402
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
Codecov Report
@@ Coverage Diff @@
## master #1402 +/- ##
==========================================
- Coverage 63.52% 63.49% -0.04%
==========================================
Files 116 116
Lines 8508 8500 -8
Branches 1879 1875 -4
==========================================
- Hits 5405 5397 -8
Misses 2974 2974
Partials 129 129
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. |
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.
To clarify my understanding, this change ensures "if stacking and if PoX-2 contract is deployed, then submit tx for the pox-2 contract", right?
Essentially, the behavior already previously was: This PR just removes the This check was buggy, since it didn't check the current contract at all. And the check doesn't make sense now anyway — since non-Period1 will always use pox-2. So, either overlapping-into-Period3 would be allowed (in Period1 via pox-1) or we use pox-2 anyway. |
I believe, the check to see if something overlaps into Period 3 is no longer needed (and was implemented incorrectly before).
It's not needed since Stacks.js will prefer PoX-2 if available, so @stacks/stacking shouldn't be able to generate txs that target PoX-1 after the 2.1 fork.
fix:
ensurePox1DoesNotCreateStateIntoPeriod3
checktest: