breach_report_invalid: The breach report is malformed
The report's payload is not a well-formed dynamo-breach-v1 payload (its fields, term, times or nonce), names another stream, or reuses a nonce another report already used. Nothing moves.
A report whose signer or signature is missing or malformed never reaches this check: both routes answer 400 invalid_request first.
What to do
- Have the signer issue a well-formed report for this stream with a fresh nonce.
On the wire
HTTP 409, error type state_error.
Only the breach report routes answer this code: POST /owner/v1/streams/{id}/breach-reports (1.7.0) and, where the deployment serves it, the oracle's POST /oracle/v1/attest/breach (1.8.0). Both send errorDetail to every client, with or without Dynamo-Error-Detail: 1:
{
"error": "state",
"reason": "breach_report_invalid",
"detail": "…",
"errorDetail": {
"type": "state_error",
"code": "breach_report_invalid",
"message": "…",
"param": "report",
"doc_url": "…/errors/breach_report_invalid.md",
"fix": "the breach report is malformed (dynamo-breach-v1 payload, signer, 65-byte signature)"
}
}
See all error codes.