-
Notifications
You must be signed in to change notification settings - Fork 717
Use is-in-mainnet in pox-4.clar #4117
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
Use is-in-mainnet in pox-4.clar #4117
Conversation
moodmosaic
left a comment
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.
LGTM!
| # path = "../../stackslib/src/chainstate/stacks/boot/pox-testnet.clar" | ||
| [contracts.pox-4] | ||
| path = "./contracts/pox/pox-4-testnet.clar" | ||
| path = "../../stackslib/src/chainstate/stacks/boot/pox-4.clar" |
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.
🎉
hugoclrd
left a comment
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.
LGTM! thx @friedger
jcnelson
left a comment
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.
I wish I'd had a chance to review this before it got merged, because this patch could use some improvement. Namely, the organization of the ADDRESS_VERSION constants are confusing. If you look in pox-4.clar, you'll see code comments to the effect that the four address versions here are included in a separate file, and yet here they are. Could you send another PR that cleans up pox-4.clar's ADDRESS_VERSIONs?
|
This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Description
This PR changes the way how pox-4 contracts for mainnet and testnet are created. Instead of string concatenation, we now use
is-in-mainnetin clarity.Applicable issues
Additional info (benefits, drawbacks, caveats)
pox_4_body is only used to create pox-4 contract for mainnet and testnet. It is not used for creating pox-4 contract with other constants.
Checklist
docs/rpc/openapi.yamlandrpc-endpoints.mdfor v2 endpoints,event-dispatcher.mdfor new events)clarity-benchmarkingrepobitcoin-tests.yml