| Name | Related DEX | Address | Token Price (USD) |
|---|---|---|---|
| ROME / ETH 1% | uniswap-v4-ethereum | 0x5f54...257d | 0.3032994658 |
| ROME / ETH 1% | uniswap-v4-ethereum | 0x8bc8...34b0 | 0.298759249 |
| ROME / ETH 32% | uniswap-v4-ethereum | 0x2256...c9a9 | 3.0707994524 |
| ROME / ETH 25% | uniswap-v4-ethereum | 0x2141...8123 | 5.3850137179 |
| ROME / USDC 1% | uniswap-v4-ethereum | 0x6849...fc52 | 0.6943011766 |
| ROME / USDT 2.5% | uniswap-v4-ethereum | 0xc882...c43e | 1.3600661408 |
| uPEG / ROME 1% | uniswap-v4-ethereum | 0x00c7...63de | 1.1389274891 |
| ROME / USDC 55% | uniswap-v4-ethereum | 0x01be...5eee | 0.5674765229 |
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.