Repository navigation
Description
Goal
Reconsider whether verifier bonding and admission into a delegation cluster's selectable verifier registry should require two instructions.
Why
The current onboarding flow calls RegisterVerifier to create and fund VerifierBond, followed by UpdateVerifierRegistry(Add) to make that verifier selectable. The separation currently has no clear operational benefit:
- The cluster config authority must sign both instructions.
- A funded
VerifierBondis unusable until the registry update succeeds. UpdateVerifierRegistrycurrently supports onlyAdd;Removeis rejected, so the intended independent membership lifecycle is not yet realized.
The split also creates another synchronization boundary when selection data such as bonded stake is copied into the registry.
Options
- Merge initial onboarding. For the current permissioned model, make
RegisterVerifieratomically create and fund the bond and add the verifier toVerifierRegistry. Remove the separateAddoperation, and retain a registry-update instruction only when remove, pause, or re-add behavior exists. - Make bond creation self-service. Allow a verifier to create and fund its own bond without the config authority. Keep authority-controlled registry admission as the separate permissioned step. Here, permissionless applies only to bond creation; an unapproved verifier must not become selectable.
Keeping the current two authority-gated instructions is reasonable only if we introduce an independent bond and registry-membership lifecycle that needs them.
Follow-up
After choosing the model:
- update Implement RegisterVerifier #208 and Implement UpdateVerifierRegistry #209, PR feat(fraud-proofs): Implement RegisterVerifier #198, PR feat(fraud-proofs): Implement UpdateVerifierRegistry #199, and the v2 implementation notes to use the selected onboarding flow;
- update Implement UpdateVerifierRegistry #209 to cover only the registry operations that remain, including remove, pause, or re-add if they are needed; and
- update the verifier-specific rules in Implement RequestStakeWithdrawal #210 and Implement WithdrawStake #211 so withdrawal and registry membership cannot get out of sync.
Outcome
Choose and document one onboarding model. The selected design must define how bonded stake and verifier eligibility remain synchronized across registration, admission, removal, withdrawal, and slashing.
Activity