Signer Onboarding

The Stacking DAO protocol delegates stake to onboarded signers in the ecosystem (see Signer Delegations & Analytics). Running a signer on the Stacks network is permissionless. Anyone can run the software and participate in signing. The onboarding process for a new signer on Stacking DAO however is permissioned in order to prevent malicious actors.

To onboard as a signer, you may get in touch over X (@StackingDAO or @philiphacks). The steps to onboard are as follows:

  • After a short intro call with the Stacking DAO team, we would formalise the agreement with a simple SLA (which has details on required uptime and rewards processing)

  • The Stacking DAO Signer program requires signers to run a separate pool for Stacking DAO delegations. An example of such a pool can be found here (e.g. for Kiln). We (Stacking DAO) will take care of this deployment and then set your signer as the pool owner (IMPORTANT: needs to be the signer address, i.e. the keys with which you will be signing blocks with)

  • Once the Clarity pool is deployed and your Signer address is pool owner, we require a signature for this pool every PoX cycle (set-cycle-signer-info' on the pool). This can be generate through our own UI (see here) or through a script of your own. The Bitcoin reward address to be set to the Stacking DAO reward address (bc1q9ll6ngymkla8mnk5fq6dwlhgr3yutuxvg3whz5 in hashbytes).

  • With each signature, we can then aggregate commit the delegations into PoX and receive the BTC rewards on our address, with your signer signing the blocks

Delegations will happen based on a queuing system and depend on the net inflow that the protocol sees each PoX cycle.

Last updated