Name | Related DEX | Address | Token Price (USD) |
---|---|---|---|
REPv2 / WETH | uniswap_v2 | 0x8979...1cba | 0.863225003878217 |
REPv2 / WETH 1% | uniswap_v3 | 0xb055...17e7 | 0.863559141133253 |
REPv2 / DAI | uniswap_v2 | 0xada6...0703 | 0.83089489086036 |
REPv2 / USDC 0.3% | uniswap-v4-ethereum | 0xe317...06ca | 0.7349392187 |
REPv2 / PYRENEES | uniswap_v2 | 0x4f14...f405 | 0.7586225634 |
REPv2 / UPP | uniswap_v2 | 0x4476...051b | 0.9199031374 |
REPv2 / HOT | uniswap_v2 | 0x4e89...d328 | 0.894497069 |
REP / REPv2 | uniswap_v2 | 0xb45e...8c58 | 1.68436602708891 |
REPv2 / WETH 0.3% | uniswap_v3 | 0x8770...d92d | 1.377538268227059852536198183202 |
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.