Understand the importance of key share verification in MPC Wallets and how to set it up effectively.
Status | Definition | Available Actions |
---|---|---|
Never Verified | The key share has not been verified since its creation. | - Verify key share manually. |
Effective | The key share has been successfully verified. | - View verification details and results. - Verify key share manually. |
Pending | A verification process has been initiated but is not yet completed. - Pending Signature: If the TSS Node is stored on Cobo Guard, this status indicates that the system is waiting for the key share holder to sign the verification message on their Cobo Guard device. If the TSS Node is deployed on a server, this status indicates that the system is waiting for the key share holder to start their TSS Node, which will automatically sign the verification message. - Pending Verification: The message signing is complete and is awaiting final verification by Cobo. | - View verification details and results. |
Verification Failed | - Failed to Send Verification Message: The system could not send the key share verification message to the TSS Node due to an error. - Blocked by Policy: Applies only if your TSS Node is deployed on a server. This status means the message sent to the TSS Node did not meet the callback risk control policies. - Rejected By Key Share Holder: Applies only if your TSS Node is stored on Cobo Guard. This status indicates that the message sent to the key share holder was rejected. - Verification Message Expired: This status appears when the message sent to the server or Cobo Guard is not signed within 48 hours. - Signing Failed: The message signing process failed either on the server or on Cobo Guard. - Signature Verification Failed: The signature was received, but Cobo could not verify its validity. | - Cancel failed verification. - View verification details and results. - Resend verification message. |