TESTNET

Deploy signer-manager

Deploy the reviewed signer-manager contract. The deploying address becomes the manager admin, so deploy from a wallet you control, then move admin to a cold key below.i

Pick a wallet at connect. Xverse is shown but can't be used — it can't enforce the post-conditions these calls rely on. Why? →

Reference contract and hash

The difference between networks is the embedded PoX-5 boot principal and the sBTC contracts. Compare the canonical hash: the raw hash shifts with whitespace and line endings.

Contract

Raw source SHA-256…
Canonical SHA-256i…
Structure SHA-256i…
Reference match…
Embedded PoX-5 principal…
Deploys as…
Payloadi…
Post-condition modedeny, no conditions (deploy moves no assets)

Admin rotation

Move admin control to a cold key (e.g. Ledger or multisig). update-admin is a normal contract call the Ledger signs.i

  1. From the hot deploy key: add the cold key (admin = cold, action = add).
  2. Reconnect as the cold key and remove the hot key (admin = hot deployer, action = remove). This proves the cold key works and removes the hot key in one call.
  3. Treat the hot deploy key as retired.
Do not disable the last remaining admin before a replacement has called update-admin at least once. update-admin requires an existing admin, so bricking the only admin permanently freezes fee and registration control.

Set fee

Set the pool fee taken from staker rewards, from the connected admin wallet. update-fees is a normal contract call the Ledger signs.i

Contract default at deploy0% (0 bips)
Allowed range0% to 99.99% (contract requires below 100%)
Granularity0.01% (1 basis point)
Sends new-fees…

Keys stay in the wallet. Testnet uses the violet accent, mainnet the Stacks orange. Signer Sidekick is interim tooling: verify the source hash and every on-chain result yourself.