| Name | Related DEX | Address | Token Price (USD) |
|---|---|---|---|
| TBTC / crvRenWSBTC | curve | 0xc250...cb66 | 189384.20852469 |
| TBTC / WBTC | sushiswap | 0x2dbc...7f68 | 195851.803256526 |
| TBTC / WETH | uniswap_v2 | 0x8540...33f6 | 192000.905608729 |
| TBTC / KEEP | uniswap_v2 | 0x38c8...f081 | 192042.385027376 |
| TBTC / WBTC 0.3% | uniswap_v3 | 0x0273...e234 | 78363.6240570382 |
| TBTC / WETH | sushiswap | 0xee6d...00a9 | 208398.757723885 |
| TBTC / VBTC | sushiswap | 0xbced...46db | 198513.330876236 |
| TBTC / cbBTC 0.3% | uniswap-v4-ethereum | 0x3582...35f0 | 97980.0304190291 |
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.