| Name | Related DEX | Address | Token Price (USD) |
|---|---|---|---|
| DIGG / WBTC | sushiswap | 0x9a13...35e3 | 204.8663907995 |
| DIGG / WBTC | uniswap_v2 | 0xe862...6c52 | 205.317628102 |
| DIGG / WBTC / graviAURA 1% | balancer_ethereum | 0x8eb6...8b7c | 202.995061228 |
| DIGG / WETH | sushiswap | 0xf41e...8724 | 185.8743088443 |
| DIGG / WETH | uniswap_v2 | 0x9f51...cb0f | 181.5133619289 |
| DIGG / WETH 1% | uniswap_v3 | 0x1744...e3ee | 292.2496125946 |
| BADGER / DIGG | sushiswap | 0x438f...e000 | 604.027962019343 |
| DIGG / WBTC 1% | uniswap_v3 | 0x1352...af35 | 3745.42421371934731170399029397263136 |
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.