batch staking planner

plan a staking sequence that fits inside a staking day window. each bond stays a separate orchard action for privacy. consolidation is not possible by design.

staking cycle 0

cycle pos 2/150 staking day LIVE, 68 blocks left in window

why a sequence and not a single tx

consolidation is not possible by design for privacy reasons, confirmed apr 17 in the crosslink updates channel. each bond is a separate orchard action. every stake creates one on-chain event, visible as a count not an identity. keeping bonds separate is the privacy guarantee, not a ui bug.

how to stake now

staking is done in the crosslink desktop wallet during the staking day window. pubkey to paste as the finalizer identity (use revhex on the node log to match this byte order):

operator finalizer pubkey

bb93fde13cfc03f430af8d03f9114f711897170c18192a3524e48251d8f77e64

see /stake for the support page with copy-paste flow. live roster on /finalizers. live participation on /finalizers/participation.

open upstream gap

a wallet-side batch helper that submits n stake transactions in sequence remains an open upstream gap. the existing zingo-cli has no stake command and zebrad has no rpc that both funds and delegates in one call. wallet/src/lib.rs:1924 stake_orchard_to_finalizer is the real path if someone wants to build a thin rust cli wrapper. out of scope for this explorer.