| Name | Related DEX | Address | Token Price (USD) |
|---|---|---|---|
| BBTC / crvRenWSBTC | curve | 0x071c...8f4b | 7801.58698326883 |
| TBTC / crvRenWSBTC | curve | 0xc250...cb66 | 7990.29278721081 |
| oBTC / crvRenWSBTC | curve | 0xd81d...f8dd | 7672.65794259509 |
| pBTC / crvRenWSBTC | curve | 0x7f55...dbef | 8121.8390591222 |
| crvRenWSBTC / USDC 90.2% | uniswap-v4-ethereum | 0xc1cf...3912 | 1435.7301714213 |
| tBTC / crvRenWSBTC | curve | 0xfa65...cc4d | 7310.3905440815 |
| pBTC / crvRenWSBTC | curve | 0xc946...2587 | 0.0 |
| crvRenWSBTC / wibBTC | curve | 0xfbdc...aa9b |
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.