| Name | Related DEX | Address | Token Price (USD) |
|---|---|---|---|
| weETH / weETHs / weETHk | curve | 0x6a8a...1ae6 | 1707.969095849 |
| weETHk / weETH | curve | 0x2fd6...f8c4 | 1656.5709898933 |
| weETHk / ETH 70% | uniswap-v4-ethereum | 0x1d47...ba38 | 1274.13038382 |
| weETHk / USDC 94.8% | uniswap-v4-ethereum | 0x41f3...e186 | 1419.5665311335 |
| weETHk / WETH 1% | uniswap_v3 | 0xd3d1...3148 | 3131.1903888895 |
| weETHk / USDC 95% | uniswap-v4-ethereum | 0x6deb...17e6 | 1401.8044687758 |
| weETHk / USDT 90% | uniswap-v4-ethereum | 0x5dcb...9cf3 | 34415.1233832312 |
| weETHk / WETH 0.3% | uniswap_v3 | 0x7f15...d36c | 2631.35692916665 |
| weETHk / weETH 1% | uniswap_v3 | 0x3d72...fe49 | 3372.2112638782 |
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.