Pairing and Revocation

Pairing connects a signer device to a Beav3r project. Revocation removes that device so another one can take over.

Pairing controls human approval routing for guarded requests. Pairing does not register the onchain authorization signer in the onchain signer registry.

Pair a signer

When pairing succeeds:

• the signer device becomes the active signer
• push delivery is enabled for that device

Expected result:

• approval notifications are delivered to the paired device

Revoke a signer

To move to another device:

1. revoke the current signer
2. pair the new signer

Expected result:

• the previous device is no longer the active signer
• the new device becomes the active signer

If something seems wrong

Check:

• is the intended device currently the active signer?
• was the previous signer revoked?
• did the new pairing complete successfully?
• is the mobile device able to receive push notifications?

Pairing vs onchain signer registration

• A paired mobile signer is for dashboard/app approval decisions.
• Onchain execution authorization also requires a configured onchain signer key in the signer registry for the target (account, keyId).
• If onchain authorization fails with signer/key errors, fix registry signer configuration, not mobile pairing.