Nakamoto for Stacking Providers
Remember that Nakamoto is being rolled out in two phases. This represents the first phase. Understanding this process is key to understanding the information below, read it here: Nakamoto Rollout Plan
Upgrading your Stacking pool or service
There are a few basic steps you'll need to follow to get your Stacking pool set up to work with this first Nakamoto hard fork as this fork brings us the new pox-4 contract:
Setup a Stacks node and signer by following the How to Run a Signer doc.
Update your user-facing products and contracts to point to the new pox-4 contract
i.e. if you use a wrapper contract with pox-3 hardcoded, you'll need to deploy a new contract referencing pox-4
Update any internal infrastructure or automation that you use to manage your pool
Familiarize yourself with the new
stack-aggregation-commitfunction arguments, along with how to generate a signer key signature.
Other notes:
Once you are running a signer as described in the How to Run a Signer doc, you'll initiate Stacking transactions as normal, but you'll need to pass an additional Signer signature field. This is covered extensively in the How to Stack doc.
For delegated stacking flows, the functions
delegate-stxanddelegate-stack-stxare unchanged. If your pool makes use of custom smart contracts for allowing Stackers to delegate to you, those contracts may need to be updated to point to the newpox-4address.The function
stack-aggregation-commitnow requires pool operators to provide their Signer’s public key, along with other related information. Learn more about generating Signer key signatures using the stacks-signer CLI or with Lockstacks. Again, this entire flow is covered extensively in the How to Stack doc.Depending on your pool’s infrastructure, you may need to update any tools or automations that you use to finalize your pool’s delegations.
Reminder: The network does not depend on Signers for block production until the second hard fork expected in May. Learn More: Nakamoto Rollout Plan
Last updated