# Mixers & Bridge Tracking

<figure><img src="/files/BgG948p2Zrz4Y3IQKFJs" alt=""><figcaption></figcaption></figure>

### Equinox AI monitors transactional flows through mixers and bridges to uncover asset movements that attempt to hide origin, timing, or destination. These tools are often used to fragment traceability, but Equinox maintains resolution by building structured tracking models around known routes and obfuscation methods.

#### Monitored Entities

| Category | Examples                             |
| -------- | ------------------------------------ |
| Mixers   | Tornado Cash, Railgun, private pools |
| Bridges  | Multichain, Stargate, Hop, Synapse   |

Each category is tracked independently, then merged into cross-chain tracing models that connect source wallets, interaction timing, transaction patterns, and known social signals (if available).

***

#### Tracking Methodology

* **Entry & Exit Profiling**\
  Each interaction with a mixer or bridge is logged with timestamp, gas usage, token type, and pre/post wallet balance states.
* **Transaction Fingerprinting**\
  Patterns are analysed across multiple hops — token denominations, gas anomalies, contract sequences — to build reusable detection signatures.
* **Bridge Event Linking**\
  Source chain contracts are matched with destination chain arrival contracts. Known relayers or predictable delays are factored in.
* **Mixer Coordination Analysis**\
  When a mixer event aligns with a public call (tweet, Telegram message, or post), Equinox flags this and links to the social record.

***

#### Cross-Chain Behaviour Mapping (Text Format)

```
[Wallet A - ETH] → [Tornado Cash] → [Wallet X - ETH] → [Bridge] → [Wallet Y - BSC]
    ↑                                                            ↓
  Matched with Twitter Call                         Telegram Group Mention (T+5min)
```

This behaviour is scored, logged, and retraceable. Users can query chains of activity using wallet tags, transaction IDs, or social handles if linked.

***

#### API Endpoint Sample

Equinox API allows querying mixer-to-bridge patterns:

```json
GET /api/v1/flowtracker?wallet=0xABC123&depth=4&type=mixer_bridge

Response:
{
  "origin": "Ethereum",
  "entry_mixer": "Tornado Cash",
  "exit_wallet": "0xDEF456",
  "bridged_to": "BSC",
  "final_wallet": "0x789XYZ",
  "correlated_social": ["@user_xyz", "@alpha_group"]
}
```

***

#### Use Cases

* Identify token launches where devs anonymised pre-sale wallets
* Detect KOLs obfuscating call-related buys/sells
* Trace stolen funds routed across chains via mixer-bridge stacks
* Monitor protocol teams moving treasury out with concealed paths

***

**Equinox AI builds tracking systems that preserve traceability even across obfuscation layers. When traditional tools lose visibility at mixers or bridges, Equinox continues mapping.**


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://equinoxai.gitbook.io/equinox-ai-whitepaper/core-features/mixers-and-bridge-tracking.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.