Multisig Wallets

Open the validation ceremony for a signer enrollment

Draw a fresh validator nonce for a pending enrollment — the second half of the SAS input. Only a signer already on the wallet can challenge. The candidate app reads the returned nonce to display its 4-digit code; a new challenge drops any earlier reveal so a stale nonce can never validate.

post/v1/multisig-wallets/{walletId}/signers/{signerId}/challenge

Request

  • Base URL: https://api.prod.keyban.io
  • URL: https://api.prod.keyban.io/v1/multisig-wallets/{walletId}/signers/{signerId}/challenge
  • Auth: one of:
    • API key in header X-Api-Key
    • bearer (a scheme the document does not define)

Path parameters

walletIdstring uuid required

The unique identifier of the multisig wallet

signerIdstring uuid required

The enrollment to challenge

Response

Challenge opened

validatorNoncestring required

Fresh 32-byte nonce the challenge fixes. The candidate app combines it with its own nonce and signer bytes to display the 4-digit code.

Example response

{
  "validatorNonce": "0x2222222222222222222222222222222222222222222222222222222222222222"
}

Changes

No recorded changes to this operation across all 1 revision of this API.