# Give reviewers a traceable record of onchain activity.

Feed transactions and events from GraphOps into your monitoring and case systems. Your controls supply screening, attribution, and decisions.

[Discuss your project](https://graphops.xyz/contact#enterprise) [Explore RPC API](https://graphops.xyz/services/rpc#service-example) 

Compliance data 

Worked example 

## Keep a flagged transfer’s evidence exact

Your transfer-review control flags a 2,500 USDC transfer because the receiving address has sent funds to an address your attribution data lists.

At stake 

A reviewer decides the case now, and an audit may later ask exactly what they saw.

Built with 

- GraphOps Substreams

- GraphOps RPC

### Case REV-018

Review pending   Transfer under review and the counterparties your control checked 

- Sender0xa1…03

- 2,500 USDC

- Receiver0xc2…08

- Sent funds to

- Not listed0x76…d1 Listed in your data0xb9…44

#### Source record

NetworkExample EVM network

Transaction0x8a…17

ParserToken transfer parser v2

Policytransfer-review.v3

#### Evidence revisions

- Revision 1Block 1,100 · hash 0xb4…92 · event index 2Superseded

- Undo signalBlock 1,100 replaced

- Revision 2Block 1,101 · hash 0x5d…e0 · event index 4Current

### How it comes together

- GraphOps service

- Your systems and team

- GraphOps Substreams 

#### Stream transfers into your monitoring

Your consumer receives each USDC transfer with its block, block hash, transaction, and event index.

- Your control 

#### Screen the counterparties and open a case

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.

- GraphOps RPC 

#### Retrieve the source record

The transaction, receipt, and log confirm 2,500 USDC from 0xa1…03 to 0xc2…08 at event index 2 in block 1,100.

- GraphOps Substreams 

#### Carry the block replacement

An undo signal reverts block 1,100. Your consumer marks that observation superseded and stores the transfer again from block 1,101.

- Your reviewer 

#### Decide with both revisions in view

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.

What to keep with each revision 

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.

Related workflows 

## Inputs for your control workflows

- ### Ongoing monitoring

Feed selected events into your screening rules.

[GraphOps Substreams](https://graphops.xyz/services/substreams)

- ### Transaction investigations

Retrieve transactions, receipts, and logs behind a flag.

[GraphOps RPC](https://graphops.xyz/services/rpc)

- ### Entity-based review

Query indexed account and protocol entities for review context.

[GraphOps Subgraphs](https://graphops.xyz/services/subgraphs)

- ### Retained review records

Store events alongside case history, interpretation, and policy versions.

[GraphOps Substreams](https://graphops.xyz/services/substreams)

Evaluate with your data 

## Evaluate the evidence lifecycle

Use a sanitized case format to test whether a later reviewer can rebuild what an earlier reviewer saw.

- Test 01 

### Rebuild a closed case

Trace its amount and counterparty address back to stored source values, with the parser and policy versions used at the time.

- Test 02 

### Replace a block under an open case

Check who receives the change, whether the decision reopens, and how the earlier observation stays visible.

- Test 03 

### Limit what leaves your systems

Map each request and its destination. Keep case narratives and customer identity records in your controlled systems.

### Bring to the first conversation

- A sanitized case schema

- Required source fields

- Collection interval and history

- Evidence retention requirements

- Owners for ingestion, screening, and review

[Explore current pricing](https://graphops.xyz/pricing) 

## Build the data integration your controls need.

Create an account and fund access to retrieve source records. Discuss an engagement around your evidence integration, history, and retention requirements.

[Discuss your project](https://graphops.xyz/contact#enterprise)[Create account (opens in a new tab)](https://platform.graphops.xyz/auth/register)