Detect a bridge transfer in a fund flow
Cross-chain hops break naive tracing. When a fund-flow path lands on an address the intel engine labels as a bridge, that is where value crossed chains. Read the terminal entity and category to detect it, then resume on the destination chain.
- A live API key with a positive credit balance
- A source address, chain and direction to trace
1Trace the fund flow
Run a multi-hop fund-flow trace from the source. This is C4-metered — the heaviest primitive — because it walks paths across several hops.
curl "https://api.1st-node.com/v1/intel/eth/0x9a..f2/flow?dir=out&hops=3" \ -H "Authorization: Bearer sk_live_..."
2Spot the bridge terminal
Inspect each path's terminal entity. A category of bridge means the funds left the chain there. The label carries a confidence you should record.
> { "paths": [ { "hops": [
> "0x9a..f2", "0x28..a1", "0x77..bd" ],
> "terminal_entity": "Stargate",
> "category": "bridge", "confidence": 0.87,
> "value_usd": 150000 } ] }3Confirm the bridge label
Call labels on the terminal address to confirm the bridge attribution independently before you treat the path as a cross-chain exit.
curl https://api.1st-node.com/v1/intel/eth/0x77..bd/labels \ -H "Authorization: Bearer sk_live_..."
4Resume on the destination chain
Record the bridge hop, then continue the investigation with a fresh trace on the destination chain (for example tron) so the flow stays connected across the gap.
Частые вопросы
How is a bridge identified?
By a cluster-level entity label with category bridge and a confidence value. Confirm it with a direct labels call before treating a path as a cross-chain exit.
Can the trace follow funds across the bridge automatically?
Not in one call. Detect the bridge terminal, then start a new trace on the destination chain and stitch the paths together.
Читать дальше
Пополнили, получили ключ, запустили.
Полное самообслуживание. Оплата криптой или картой. Тарификация в кредитах — тяжёлые примитивы дороже, простые дёшевы.
Получить API-ключ