Skip to main content

Troubleshooting

Most ALX failures come from mismatched input, normalization, authorization, or verification context. Start with the failing layer and compare the exact values supplied to the verifier.

Find the Failing Layer

ResultCheck
Invalid Block hashRecompute from the original content and normalized parents.
Invalid content hashConfirm the content has not changed and canonicalization matches.
Malformed parent hashUse 0x followed by 64 hexadecimal characters.
Missing parentLoad the referenced Block or report the graph as incomplete.
Cycle detectedRemove the relationship that points back to an ancestor.
Signature mismatchConfirm signer, domain, chain ID, contract, and typed-data fields.
Merkle proof failedConfirm the Merkle root hash, leaf, sibling values, and sorted-pair algorithm.
Commitment transaction rejectedConfirm the local contract address, signer policy, nonzero commitment value, and implementation-specific authorization.

Recover from a Failure

Preserve the original input and expected output before changing data. Reproduce the failure with synthetic values, then rerun the relevant conformance or negative test.

When to Reject

Reject malformed hashes, unsupported canonicalization values, mismatched identities, invalid signatures, unauthorized submissions, and failed proofs. Report missing lineage separately when the graph is incomplete rather than invalid.