Re-apply Multisig Key

This API can be called with a Global Token. If the private key of a wallet whose key management type is multisig (co-managed) could not be recovered from the encryptedUserKey submitted with the request, submits a new encryptedUserKey to recover the bridge. The failed side (source/destination) is determined from the bridge status.

Target side

Which wallet the key applies to is determined automatically from the bridge status.

• SOURCE_FETCH_KEY_FAILED → encryptedUserKey of the source wallet
• DESTINATION_FETCH_KEY_FAILED → encryptedUserKey of the destination wallet

The request body takes only encryptedUserKey.

Prerequisites

• The bridge status must be one of the two *_FETCH_KEY_FAILED statuses above.
• The key management type of the failed side's wallet must be multisig (co-managed).
• encryptedUserKey must not be an empty string.

On success, WithdrawalUserKey is updated with the new key and the status is reset to the corresponding awaiting status, so the scheduler picks the bridge up again.

What about failed on-chain steps?

Gas or network failures such as SOURCE_APPROVE_ERC20_FAILED / SOURCE_BRIDGE_FAILED / DESTINATION_ACTIVATE_ADDRESS_FAILED / DESTINATION_BRIDGE_FAILED are not key problems and cannot be recovered with this endpoint. Check the cause in errorCode / errorMessage and contact the operations team.