Feed transactions and events from GraphOps into your monitoring and case systems. Your controls supply screening, attribution, and decisions.
Transfer from 0x4d…a6 to 0x9e…51
Transfer from 0xa1…03 to 0xc2…08
Your transfer-review control flags a 2,500 USDC transfer because the receiving address has sent funds to an address your attribution data lists.
A reviewer decides the case now, and an audit may later ask exactly what they saw.
0xa1…030xc2…080x76…d1 Listed in your data0xb9…44 Your consumer receives each USDC transfer with its block, block hash, transaction, and event index.
Policy transfer-review.v3 checks the receiver’s counterparties against your attribution data. One of them, 0xb9…44, is listed, so case REV-018 opens.
The transaction, receipt, and log confirm 2,500 USDC from 0xa1…03 to 0xc2…08 at event index 2 in block 1,100.
An undo signal reverts block 1,100. Your consumer marks that observation superseded and stores the transfer again from block 1,101.
Your policy decides whether the new revision changes the review. The case keeps both observations next to the decision.
ResultAn auditor can open REV-018 and see both evidence revisions, the parser and policy versions, and the reviewer’s decision.
GraphOps supplies chain records. Screening, attribution, and case decisions come from your controls and stay in your systems.
Link each revision to its block, block hash, retrieval time, parser version, and case identifier. Store the policy version and reviewer action separately from the chain observation.
Feed selected events into your screening rules.
GraphOps SubstreamsRetrieve transactions, receipts, and logs behind a flag.
GraphOps RPCQuery indexed account and protocol entities for review context.
GraphOps SubgraphsStore events alongside case history, interpretation, and policy versions.
GraphOps SubstreamsUse a sanitized case format to test whether a later reviewer can rebuild what an earlier reviewer saw.
Trace its amount and counterparty address back to stored source values, with the parser and policy versions used at the time.
Check who receives the change, whether the decision reopens, and how the earlier observation stays visible.
Map each request and its destination. Keep case narratives and customer identity records in your controlled systems.
Create an account and fund access to retrieve source records. Discuss an engagement around your evidence integration, history, and retention requirements.