SIGNER_FENCED

The signer fenced itself and refuses to sign.

HTTP status	503
Group	Relay path
Retryable	Yes — the same request may be sent again
Re-sign	SAME_BYTES — resend the transaction you already have, byte for byte

What happened

A signer that cannot prove it is not partitioned from its peers stops signing. That is the design: at-most-once beats availability.

What to do

Retry with the same bytes; another host takes over.

The problem document

Every error is application/problem+json (RFC 9457) with the same shape:

{
  "type": "https://docs.co-relayer.com/errors/signer-fenced",
  "title": "The signer fenced itself and refuses to sign.",
  "status": 503,
  "detail": "A sentence about this specific occurrence.",
  "instance": "req_01JB…",
  "code": "SIGNER_FENCED",
  "retryable": true,
  "resign": "SAME_BYTES",
  "hint": "Retry with the same bytes; another host takes over."
}

See the error model for what each member means and how to handle unknown codes.