| Name | Related DEX | Address | Token Price (USD) |
|---|---|---|---|
| cUSD / crvUSD | curve | 0x2d1e...5b09 | 0.955049056722485 |
| USDC / cUSD 5% | uniswap-v4-ethereum | 0x59e2...79ae | 0.9774931013 |
| USDC / cUSD 86% | uniswap-v4-ethereum | 0x61f6...a91b | 0.397870798 |
| cUSD / ETH 79% | uniswap-v4-ethereum | 0x3a04...7aba | 0.3008116641 |
| USDC / cUSD 87% | uniswap-v4-ethereum | 0xf6be...0954 | 0.4105628001 |
| USDC / cUSD 89% | uniswap-v4-ethereum | 0x9fe4...d9ee | 0.2786069305 |
| USDC / cUSD 50% | uniswap-v4-ethereum | 0x517c...3746 | 0.4959503358 |
| kpCAPS-1 / cUSD 1% | uniswap_v3 | 0x1955...f007 | 0.9913201046 |
Generally, a honeypot Detector operation consists of a computer, applications and data that simulate the behavior of a real system that would be attractive to attackers, such as a financial system, internet of things (IoT) devices, or a public utility or transportation network. It appears as part of a network but is actually isolated and closely monitored. Because there is no reason for legitimate users to access a honeypot, any attempts to communicate with it are considered hostile.