proof_invalid: The identity proof does not verify
An identity link on an economic account (POST /owner/v1/accounts/:id/links) carries a proof that this deployment checked and refused:
- a signature that does not verify (a two-key proof, a
w3c_vcissuer signature, an agent card, a Web Bot Auth signature, or an SD-JWT); - malformed proof material: a JWT or JWS that is not compact, a header or payload that is not JSON, or a JWT with no
kidoriss; - an SD-JWT (
paramsdJwt) that fails a check of its shape, keys and algorithm (ES256 or EdDSA), disclosures, key-binding JWT, or times (exprequired,iat,nbf), or whose subject is not the account's address; - a credential from an issuer this deployment does not trust, or whose subject is not the account's address;
- an agent card whose address is not the account's;
- a challenge that is not a
dynamo-account-link-v2challenge issued byPOST /owner/v1/link-challengesfor this proof type, this account's address and this deployment (a challenge the client wrote itself, such as the earlierdynamo-account-link:text, is refused at everyDynamo-Version); - a
w3c_vcJWT whose headertypis notvc+jwtor whosetypedoes not includeVerifiableCredential, or an agent card whose headertypis notagent-card+jwsor that carries nochallenge; - a Web Bot Auth
keyIdthat is not in the domain's key directory; - an address that is not on the ERC-8004 registry.
param names the field that failed. Nothing was linked and the account's level is unchanged.
What to do
- Issue the proof again against this account's address, and send it unchanged.
- For a
w3c_vcproof: the JWT'skid(oriss) must name an issuer this deployment trusts, and the credential subject must be the account's address. - For a
two_key,web_bot_authora2a_cardproof: fetch a challenge withPOST /owner/v1/link-challengesand thatproofType(Dynamo-Version1.9.0 or later), and sign itsmessageunchanged; a used or expired challenge answerslink_challenge.
On the wire
HTTP 400, error type invalid_request_error.
{
"error": "proof_invalid",
"errorDetail": {
"type": "invalid_request_error",
"code": "proof_invalid",
"message": "issuer signature does not verify",
"param": "issuerSignature",
"doc_url": "…/errors/proof_invalid.md",
"fix": "re-issue the proof against this account's address and retry"
}
}
The account routes always add errorDetail, with or without Dynamo-Error-Detail: 1. The doc_url shown is the one a client pinned at Dynamo-Version 1.8.0 or later receives. A client pinned before 1.8.0, or a request naming no version on a single-tenant core, receives a doc_url ending in errors/errors/proof_invalid.md, a page that forwards here. On the multi-tenant hosted tier a request naming no version is served the account's default version (1.8.0 for new accounts).
See all error codes.