| Name | Related DEX | Address | Token Price (USD) |
|---|---|---|---|
| iUSD / USDC | curve | 0x2e2d...986e | 0.993843493798753 |
| iUSD / USDe | fluid-ethereum | 0xc6ca...a819 | 0.999131560412283 |
| iUSD / msUSD 0.01% | balancer-v3-ethereum | 0x7a1f...b2ef | 0.997346253922388 |
| iUSD / USDC 0.005% | balancer-v3-ethereum | 0x8b84...d4ce | 1.0024112226 |
| iUSD / frxUSD | curve | 0x3e82...0de7 | 0.979753711453672 |
| iUSD / USDC 59% | uniswap-v4-ethereum | 0x2286...0b16 | 0.4429104047 |
| iUSD / waEthLidoGHO 0.01% | balancer-v3-ethereum | 0x733f...5470 | 0.9693985609 |
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.