DeFi Protocols

Uniswap V4 AMM Swap

Permissionless token swap via concentrated liquidity AMM. V4 hooks enable optional KYC at pool level.

Vendors

Uniswap · Hook Deployers

Compliance Center

Identity — only if hooks deployed. Most pools have no compliance. Honesty marker.

D1 — Uniswap swap · Rails: defi · Protocols: Uniswap v4 · Origin: United States — Federal
CTR (USD 10,000+)TRAVEL-RULE (USD 3,000+)ENHANCED-DUE-DILIGENCE (USD 50,000+)
D1 — UNISWAP SWAPYOU ARE HERE● User WalletPOLICY⬣ Oracle Price Ch…CODE◆ AMM Swap Execut…CODE● User WalletCODEIntentIdentityDiscoveryNegotiationTransportAuthorizationFacilitationFinalitySTEP 1STEP 2STEP 3STEP 4BASEVisual system: StablecoinAtlas.com · Steps mapped to 8 STP Stages
L5 APPLICATIONL4 ACCOUNTL3 EXECUTIONL2 CONSENSUSL1 NETWORKBASE
L5 APPLICATIONWallet UX, consent, policy engineBank customer channel / issuer app
L4 ACCOUNTBalances, addresses, signing keysCore banking ledger / DDA

Step 1 · User Wallet (Base)Policy-EnforcedBlockchain-Native

The trader's brokerage account — identity verified, funds available, order ready to submit.

User's self-custody wallet on Base. L4 Account (token balance, approval) and L5 Application (wallet UX, swap interface) are lit above the enforcement line. The swap order has been constructed but not yet submitted.

⚠ ENHANCED-DUE-DILIGENCE triggered at USD 50,000 — 31 CFR § 1010.312 — Enhanced Due Diligence (United States — Federal)
Counterparty
Self (user holds keys)
Latency
Instant · no on-chain tx yet
Finality
N/A — swap not yet submitted
Vendors
Coinbase Smart Wallet · ERC-4337 Smart Account · Coinbase Paymaster
L5 APPLICATIONL4 ACCOUNTL3 EXECUTIONL2 CONSENSUSL1 NETWORKBASE
L3 EXECUTIONSmart contracts, swap / bridge logicClearing & matching engine
◆ Enforcement Line — code-enforced below, policy-enforced above

Step 2 · Oracle Price CheckCode-EnforcedBlockchain-Native

The exchange's pre-trade price validation — ensuring the order will execute within acceptable slippage.

Price oracle verification at L3 Execution: the swap router checks current pool prices against the user's slippage tolerance. Uniswap v4 hooks may fire additional compliance checks (D16) at this point — MEV protection, front-running detection.

Counterparty
Uniswap v4 pool + oracle
Latency
<1s · on-chain read
Finality
Pre-condition — swap reverts if price moved beyond slippage
Vendors
Uniswap v4 · Chainalysis OFAC Oracle
L5 APPLICATIONL4 ACCOUNTL3 EXECUTIONL2 CONSENSUSL1 NETWORKBASE
L4 ACCOUNTBalances, addresses, signing keysCore banking ledger / DDA
L3 EXECUTIONSmart contracts, swap / bridge logicClearing & matching engine
◆ Enforcement Line — code-enforced below, policy-enforced above

Step 3 · AMM Swap ExecutionCode-EnforcedBlockchain-Native

The exchange matching engine — the trade is executed against available liquidity at the current price.

Uniswap v4 constant-product AMM executes the swap: input tokens are deposited to the pool, output tokens are withdrawn. L3 Execution (AMM logic, v4 hooks) and L4 Account (balance state changes) are lit. The bracket straddles the enforcement line.

⚠ TRAVEL-RULE triggered at USD 3,000 — 31 CFR § 1010.410(f) — Funds Transfer Recordkeeping (United States — Federal)
Counterparty
Uniswap v4 AMM pool
Latency
~2s · single Base block
Finality
Final on Base block confirmation
Vendors
Uniswap v4 · Chainalysis OFAC Oracle · ERC-4337 Smart Account
L5 APPLICATIONL4 ACCOUNTL3 EXECUTIONL2 CONSENSUSL1 NETWORKBASE
L5 APPLICATIONWallet UX, consent, policy engineBank customer channel / issuer app
L4 ACCOUNTBalances, addresses, signing keysCore banking ledger / DDA

Step 4 · User Wallet (Base)Code-EnforcedBlockchain-Native

The trader's updated portfolio — swapped tokens received, position updated.

Swapped tokens arrive in the user's wallet. Same silhouette as Step 1 — L4 Account and L5 Application lit. The DeFi path is complete: fully on-chain, fully atomic, no intermediary touched the value. Recordkeeping is the on-chain transaction receipt.

⚠ CTR triggered at USD 10,000 — 31 CFR § 1010.311 — Currency Transaction Report (United States — Federal)
Counterparty
Self (same wallet as Step 1)
Latency
Instant · same tx as swap
Finality
Final · atomic with swap execution
Vendors
Coinbase Smart Wallet · ERC-4337 Smart Account · Coinbase Paymaster

Resolved 4 steps across 1 chain(s). 3 threshold(s) triggered. Frameworks: Bank Secrecy Act, GENIUS Act, OFAC Sanctions Program, FATF Recommendation 16 (Travel Rule), Common Reporting Standard / FATCA.

TOOL 01 · 7 CHAINS COMPARED

Settlement Chain Comparator

Side-by-side compliance depth across Base, Arc, Solana, Tempo, Ethereum, TRON, and Pharos — which layers each chain lights up.

ArcCircle · Institutional-grade stablecoin L1 · Malachite BFTA-301 · ARC SECTION CUTCOMPLIANCE DEPTH →L5 APPLICATIONWallets, dApps, UIL4 MIDDLEWAREAPIs, bridges, oraclesL3 EXECUTIONSmart contracts, VML2 CONSENSUSBlock production, finalityL1 NETWORKP2P transport, gossipMalachite BFTConfidential TraEVM ContractsCCTP v2Regulatory View Institutional FXreservtransfidentiexecuttoken
EthereumGeneral-purpose L1 · Proof of Stake · Open validator setA-101 · ETHEREUM SECTION CUTCOMPLIANCE DEPTH →L5 APPLICATIONWallets, dApps, UIL4 MIDDLEWAREAPIs, bridges, oraclesL3 EXECUTIONSmart contracts, VML2 CONSENSUSBlock production, finalityL1 NETWORKP2P transport, gossipERC-4337ERC-20 Freeze/BuChainalysis APIsCircle APIs / CCWallets & dAppsneutratransfexecuttoken
MetricArcEthereum
Code-Enforced Ratio67%40%
Deep Blocks (L2-L3 code)3 of 62 of 5
Deepest LayerL2L3
ConsensusMalachite BFT (permissioned validators)Proof of Stake (open)
Finality~1s~12min
Gas ModelUSDC (stablecoin-native)ETH
Categorystablechaingeneral-purpose

HOW TO READ THESE DIAGRAMS

Compliance Depth

Measures how deeply compliance mechanisms are embedded in the chain's architecture. Higher scores indicate mechanisms woven into core consensus rather than bolted on at the edges.

Layer Stack

Five layers from L1 Network through L5 Application. Compliance enforced at lower layers (L2 Consensus, L3 Execution) is more robust than policy enforced at L4–L5.

Enforcement

Solid borders indicate code-enforced (compiled into chain logic), dashed borders indicate policy-enforced (depends on external actors and can be bypassed).