| Name | Related DEX | Address | Token Price (USD) |
|---|---|---|---|
| pBTC / WBTC | uniswap_v2 | 0x9f8d...89df | 58638.3633758898 |
| pBTC / WETH | uniswap_v2 | 0x8d50...db09 | 58721.7336252386 |
| pBTC / crvRenWSBTC | curve | 0x7f55...dbef | 76897.1685484332 |
| pBTC / pBTC | curve | 0xb146...61c5 | 77708.8116556251 |
| pBTC / SPANK 1% | sushiswap-v3-ethereum | 0x9d3b...ed8b | 95998.6583258589 |
| pBTC / SPANK | curve | 0x182f...9e93 | 77011.0243906767 |
| pBTC / SPANK | swapr_ethereum | 0x4925...89a6 | 96525.9347569042 |
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.