| Name | Related DEX | Address | Token Price (USD) |
|---|---|---|---|
| ETH+ / WETH | curve | 0x2c68...353e | 3176.00302257943 |
| ETH+ / eUSD / RSR | curve | 0xdb69...44b4 | 3174.65278753011 |
| ETH+ / WETH 0.05% | uniswap_v3 | 0xf649...a348 | 3220.20827310513 |
| ETH+ / WETH | curve | 0x7fb5...364b | 3514.8316976979 |
| dgnETH / ETH+ | curve | 0x5ba5...3b4f | 3511.12233663837 |
| USDC+ / ETH+ / SDT | curve | 0x1830...9c78 | 3202.2967252471 |
| dgnETH / ETH+ 0.05% | uniswap-v4-ethereum | 0x1c31...118c | 3322.24320032 |
| ETH+ / pxETH | curve | 0xaec7...25ed | 3834.6935225358 |
| dgnETH / ETH+ | curve | 0x021c...72c7 | 3102.3146345405 |
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.