SIGNER SIDEKICK, STANDALONE dAPPSINTERIM TOOLING

PoX-5 signer onboarding

Open a step below. Each dApp has its own Testnet or Mainnet switch (testnet default; mainnet is a deliberate Tier 2 switch). Follow the numbered order the first time through.

1 Preflight → 2 Key → signer host → 3 Deploy → generate-staking-signature → 4 Register → 5 Stake → 6 Verify
1
Connect and preflight READ
Connect the funded manager-admin wallet, verify chain, balance, PoX-active, and readiness.
→
2
Signer key helper OFFLINE
Generate the signer's BIP39 seed, account-0 address, private key, and public key. Run offline; keep it separate from the hardware-backed wallet.
→
3
Deploy signer-manager SIGNS
Deploy the reviewed signer-manager contract in deny mode. The deployer becomes admin. Links to the reference contract and expected hash.
→
4
Register-self SIGNS
Verify the signer grant against live PoX-5, then broadcast register-self. Shows STX already staked to the signer.
→
5
Stake to a signer SIGNS
Lock STX toward a signer via pox-5 stake, for a delegator or a signer staking their own STX. Shows the currently-staked amount and registration.
→
6
Rewards and status READ
Confirm registration, grant validity, delegated amount against the minimum, and recent activity. No wallet needed.
→
7
Claim rewards SIGNS
Ongoing, after setup. Claim sBTC yield: collect the pool's cycle rewards (claim-rewards), then claim a staker's share (claim-staker-rewards). Permissionless, so anyone can run either for anyone.
→
8
Signer manager SIGNS
Manage a deployed signer-manager: admins, fee, fee withdrawals, and grant revocation. Admin and fee also live in step 3. Revoke is the one call that needs the signer key.
→
Standalone apps → these apps on GitHub ↗ Guide and mainnet checklist → signer-sidekick repo ↗
Two keys, kept apart: the signer key lives on the node (step 2, more exposed); the manager-admin wallet is the funded, hardware-backed key you connect in steps 1, 3, and 4, and it becomes the manager's admin on deploy. Never paste the signer private key into these pages. They only need the public key.

Staking has no pool manager and no aggregate-commit: anyone stakes to a signer by naming its signer-manager in stake (step 5); the lock takes effect the next cycle.

Network: PoX-5 is pinned per network. ST000000000000000000002AMW42H.pox-5 on testnet, SP000000000000000000002Q6VF78.pox-5 on mainnet.

Opening these: double-clicking works for navigation, but wallet connection and API reads are most reliable when the folder is served over http:// (for example python3 -m http.server in this folder), since some wallets restrict file:// origins.