You're three hours into reconciliation and the TokenTable vesting attestations won't line up with the ERP. The on-chain schemas show fully unlocked tranches but your internal audit reference points to a schema ID that Sign deprecated last month when they updated the compliance hooks for cross-chain verification.
This is the part nobody explained during implementation. Ops marked the distribution "complete" the moment the merkle drop hit 100% claims. But Treasury is staring at SignScan queries that return attestation UIDs linking to Arweave payloads with unlock schedules that don't match the spreadsheet Finance approved last Tuesday. The CFO wants to close the quarter tonight and the discrepancy is material.
You keep toggling between the Sign Protocol explorer and your internal reconciliation tool. Same wallet addresses, different universes. On-chain, the attestation says "vested." In your system, it says "pending review." The schema registry shows version 2.1 now handles cliff dates differently than the 1.4 version locked into your Q1 attestations, and there's no migration path mentioned in the docs.
Compliance thinks this is a data sync issue. You know it's actually a trust boundary problem, Sign Protocol promised immutable evidence but nobody defined which schema version constitutes "canonical" for audit purposes. The attestation is permanent. Your interpretation of it just became a moving target that shifts under regulatory scrutiny.
You draft the email to the auditors suggesting they verify on-chain directly, then delete it. If they query the current schema instead of the historical one, the math shifts. The quarter can't close with ambiguity this foundational.