| Name | Related DEX | Address | Token Price (USD) |
|---|---|---|---|
| BOND / USDC | uniswap_v2 | 0x6591...a244 | 0.0852037683606195 |
| BOND / WETH | sushiswap | 0x613c...5d5a | 0.0863225152513042 |
| BOND / WETH | uniswap_v2 | 0xb17b...43d9 | 0.0799967161455688 |
| BOND / USDC 1% | uniswap-v4-ethereum | 0xa943...69c9 | 0.3086213808 |
| BOND / OHM 1% | balancer_ethereum | 0xf5f6...64df | 0.08672057062687 |
| BOND / USDC 0.3% | uniswap_v3 | 0x0df4...0462 | 4.84847647533274 |
| BOND / WETH | shibaswap | 0x371c...4283 | 1.4303874489 |
| BOND / USDC | sushiswap | 0x073d...7289 | 0.1606443566 |
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.