RELAYER_RETIRED
The relayer in the transaction has been retired.
| HTTP status | 410 |
| Group | Relay path |
| Retryable | No — sending it again changes nothing |
| Re-sign | NONE — do not ask the user to sign anything |
What happened
A retired address is permanently out of service — for example after a key was rotated.
What to do
Assign again and sign the new transaction once. On the native path this normally arrives as RESIGN_REQUIRED instead.
The problem document
Every error is application/problem+json (RFC 9457) with the same shape:
{
"type": "https://docs.co-relayer.com/errors/relayer-retired",
"title": "The relayer in the transaction has been retired.",
"status": 410,
"detail": "A sentence about this specific occurrence.",
"instance": "req_01JB…",
"code": "RELAYER_RETIRED",
"retryable": false,
"resign": "NONE",
"hint": "Assign again and sign the new transaction once. On the native path this normally arrives as `RESIGN_REQUIRED` instead."
}
See the error model for what each member means and how to handle unknown codes.