| Name | Related DEX | Address | Token Price (USD) |
|---|---|---|---|
| sfrxUSD / frxUSD | curve | 0xf292...5978 | 1.1659118958091316347235674702009764256823192552589945630654682209 |
| reUSD / sfrxUSD | curve | 0xed78...a441 | 1.188616475894021360144289401176675790619031309645305663670048498 |
| sfrxUSD / scrvUSD | curve | 0x15e4...5752 | 1.188819375328608149110700959238155440547995979663160132201287941 |
| sfrxUSD / USDe | curve | 0x86fe...a25e | 1.16820459520359 |
| litUSD / sfrxUSD | curve | 0x640b...cfa6 | 1.1772778118604777112340218908373607141058478883670511393464521262 |
| sfrxUSD / sUSDe | curve | 0x3bd1...d6e2 | 1.15595331218953 |
| sfrxUSD / WETH | uniswap_v2 | 0x001d...5324 | 0.02610790666 |
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.