Nakamoto for Stacking Providers
Last updated
Was this helpful?
Last updated
Was this helpful?
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 :
Setup a Stacks node and signer by following the 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-commit
, along with .
Once you are running a signer as described in the 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 doc.
For delegated stacking flows, the functions delegate-stx
and delegate-stack-stx
are 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 new pox-4
address.
The function stack-aggregation-commit
now requires pool operators to provide their Signer’s public key, along with other related information. Learn more about generating Signer key signatures using the or with . Again, this entire flow is covered extensively in the 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.