Stacking rewards Stacks (STX) token holders with bitcoin for providing a valuable service to the network by locking up their tokens for a certain time. It is crucial to note that this has no impact on block production or validation. Stacks is not a Proof-of-Stake network and stacking is different than staking.
Stacking is a built-in action, required by the "proof-of-transfer" (PoX) mechanism. The PoX mechanism is executed by every miner on the Stacks 2.0 network.
Stacking functionality is implemented as a smart contract, using Clarity. Read more about the contract.
The Stacking mechanism can be presented as a flow of actions:
- Make API calls to get details about the upcoming reward cycle
- For a specific Stacks account, confirm eligibility
- Confirm the BTC reward address and the lockup duration
- The transaction is broadcasted and the STX tokens are locked. This needs to happen before the prepare phase of the next reward cycle, the last 100 Bitcoin blocks of the ongoing reward phase
- The Stacking mechanism executes reward cycles and sends out rewards to the set BTC reward address
- During the lockup period, details about unlocking timing, rewards and more can be obtained
- Once the lockup period is passed, the tokens are released and accessible again
- Display reward history, including details like earnings for previous reward cycles
Keep in mind that the target duration for a reward cycles is ~2 weeks. This duration is based on the target block time of the network (10 minutes) and can be higher at times due to confirmation time variances of the bitcoin network.
Stacking delegation flow
The Stacking flow is different for delegation use cases:
- Before Stacking can be initiated for a token holder, the delegator needs to be granted permission to Stack on behalf of the account owner. The permission is restricted to the maximum amount the delegator is allowed to Stack. The maximum amount is not limited by the available funds and can be set much higher. An account can only be associated with one single delegator
- The account has to define the delegation relationship. They can optionally restrict the Bitcoin reward address that must be used for payouts, and the expiration burn block height for the permission, thus limiting the time a delegator has permission to Stack
- Delegators have to lock Stacks from different accounts ("pooling phase") until they reach the minimum amount of Stacks required to participate in Stacking
- Once a delegator locks enough STX tokens, they can finalize and commit their participation in the next reward cycle
- Certain delegation relationships may allow the STX holder to receive the payout directly from the miner (step 5/6)
- The termination of the delegation relationship can either happen automatically based on set expiration rules or by actively revoking delegation rights
Token holder eligibility
Stacks (STX) token holders don't automatically receive stacking rewards. Instead, they must:
- Commit to participation before a reward cycle begins
- Commit the minimum amount of STX tokens to secure a reward slot, or pool with others to reach the minimum
- Lock up STX tokens for a specified period
- Provide a supported Bitcoin address to receive rewards (native segwit is not supported)
The following diagram describes how the minimum STX tokens per slot is determined. More information on dynamic minimums for stacking is available at stacking.club.
Token holders have a variety of providers and tools to support their participation in Stacking. The Stacks website contains a list of stacking providers and pools.
Stacking in the PoX consensus algorithm
Stacking is a built-in capability of PoX and occurs through a set of actions on the Stacks blockchain. The full proof-of-transfer implementation details are in SIP-007. Below is a summary of the most relevant actions of the algorithm.
- Stacking happens over reward cycles with a fixed length. In each reward cycle, a set of Bitcoin addresses associated with stacking participants receive BTC rewards
- A reward cycle consists of two phases: prepare and reward
- During the prepare phase, miners decide on an anchor block and a reward set. Mining any descendant forks of the anchor block requires transferring mining funds to the appropriate reward addresses. The reward set is the set of Bitcoin addresses which are eligible to receive funds in the reward cycle
- Miners register as leader candidates for a future election by sending a key transaction that burns cryptocurrency. The transaction also registers the leader's preferred chain tip (must be a descendant of the anchor block) and commitment of funds to 2 addresses from the reward set
- Token holders register for the next rewards cycle by broadcasting a signed message that locks up associated STX tokens for a protocol-specified lockup period, specifies a Bitcoin address to receive the funds, and votes on a Stacks chain tip
- Multiple leaders can commit to the same chain tip. The leader that wins the election and the peers who also burn for that leader collectively share the reward, proportional to how much each one burned
- Token holders' locked up tokens automatically unlock as soon as the lockup period finishes
You must provide a BTC address in one of two formats:
Legacy (P2PKH), which starts with
Segregated Witness / Segwit (P2SH), which starts with
3. The "Native Segwit" format (which starts with
bc1), for example, is not supported. :::
The Stacking contract needs a special format for the Bitcoin address (the reward address). This is required to ensure that miners are able to correctly construct the Bitcoin transaction containing the reward address.
The address must be specified in the following format using the Clarity language:
;; a tuple of a version and hashbytes buffer
(pox-addr (tuple (version (buff 1)) (hashbytes (buff 20))))
version buffer must represent what kind of bitcoin address is being submitted. It can be one of the following:
SerializeP2PKH = 0x00, // hash160(public-key), same as bitcoin's p2pkh
SerializeP2SH = 0x01, // hash160(multisig-redeem-script), same as bitcoin's multisig p2sh
SerializeP2WPKH = 0x02, // hash160(segwit-program-00(p2pkh)), same as bitcoin's p2sh-p2wpkh
SerializeP2WSH = 0x03, // hash160(segwit-program-00(public-keys)), same as bitcoin's p2sh-p2wsh
hashbytes are the 20 hash bytes of the bitcoin address. You can obtain that from a bitcoin library, for instance using
const btc = require("bitcoinjs-lib");
Choosing the right Stacking strategy
Here is an interesting article that may help you choose the right Stacking strategy.
Where to Stack?
You can Stack on your own, on a pool or on an exchange:
Stacking on your own
Stacking on your own is non-custodial.
Stacking on your own requires a protocol minimum (amount changes but about 100,000 STX).
Hiro Wallet allows stacking on your own.
Stacking on a pool
Stacking on a pool allows Stacking without the requirement of the protocol minimum.
Some available pools are:
|Pool||Type||Pays rewards in||Fee||Minimum amount|
|Friedger's Pool||Non custodial||STX or xBTC||No||40 STX|
|Planbetter||Non custodial||BTC||5%||200 STX|
|Stacked||Non custodial||BTC||100,000 STX|
|Xverse||Non custodial||BTC||No||100 STX|
Stacking on an exchange
Stacking on an exchange is custodial, meaning you are trusting the exchange with your Stacks.
Several exchanges allow Stacking directly on their sites. Examples are Okcoin and Binance
You can view all sorts of Stacking data and statistics on Stacking Club