Name | Related DEX | Address | Token Price (USD) |
---|---|---|---|
BOND / USDC | uniswap_v2 | 0x6591...a244 | 0.262766242310941 |
BOND / WETH | sushiswap | 0x613c...5d5a | 0.266932048026153 |
BOND / OHM 1% | balancer_ethereum | 0xf5f6...64df | 0.275366895602109 |
BOND / WETH 0.3% | uniswap_v3 | 0x5772...deda | 16.0717489210642 |
BOND / WETH 1% | uniswap_v3 | 0xce96...bf96 | 2.45346867458514 |
BOND / USDC 0.3% | uniswap_v3 | 0x0df4...0462 | 4.84847647533274 |
BOND / WETH | uniswap_v2 | 0xb17b...43d9 | 0.26902589273938 |
BOND / USDT 0.3% | uniswap_v3 | 0x5d87...d82c | 2512.93428831444198212850300464 |
BOND / USDC | sushiswap | 0x073d...7289 | 6.02629319611209 |
BOND / WETH | shibaswap | 0x371c...4283 | 6.34227633055027 |
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.