Skip to content

Reconsider verifier bonding and registry admission flow #250

Open

Description

@snawaz

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 VerifierBond is unusable until the registry update succeeds.
  • UpdateVerifierRegistry currently supports only Add; Remove is 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

  1. Merge initial onboarding. For the current permissioned model, make RegisterVerifier atomically create and fund the bond and add the verifier to VerifierRegistry. Remove the separate Add operation, and retain a registry-update instruction only when remove, pause, or re-add behavior exists.
  2. 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:

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions