| Name | Related DEX | Address | Token Price (USD) |
|---|---|---|---|
| USDS / RADIO | radioshack_ethereum | 0x4c55...72bf | 0.009177006489 |
| USDS / USDC | spice_trade_ethereum | 0x09e1...8e20 | 0.009847132258 |
| USDS / USV | spice_trade_ethereum | 0x2957...f049 | 0.01059850847 |
| USDS / 3Crv | curve | 0xde49...3ad3 | 0.009121598064 |
| USDS / USDS | radioshack_ethereum | 0x4444...b551 | 0.33711536553649451010277892586477214313785022100531876315348027755101829155290869542589029916959696165117486 |
| SPICE / USDS | spice_trade_ethereum | 0x72eb...4cd2 | 0.0 |
| USDS / AGS | radioshack_ethereum | 0x45fa...1a0d | 1.0735960706 |
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.