| Name | Related DEX | Address | Token Price (USD) |
|---|---|---|---|
| gOHM / VBTC | uniswap_v2 | 0x7db1...9fe5 | 8256.30272414843 |
| VBTC / WETH | uniswap_v2 | 0xcfdc...bb8a | 8233.53081302194 |
| COOL / PUNK / VBTC / BAYC 1% | balancer_ethereum | 0xd883...9dba | 964.659924526204 |
| $TRDL / VBTC | uniswap_v2 | 0x7e83...208e | 7444.0579007421 |
| TBTC / VBTC | sushiswap | 0xbced...46db | 8067.1707258804 |
| VBTC / oneVBTC | sushiswap | 0x5aa0...3092 | 7917.9763467283 |
| VBTC / WETH | sushiswap | 0x9ff5...c5b7 | 8373.7456914199 |
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.