| Name | Related DEX | Address | Token Price (USD) |
|---|---|---|---|
| TEMPLE / DAI 1% | uniswap_v3 | 0x9097...1b32 | 3.75418075295288 |
| TEMPLE / FRAX | templedao | 0x6021...fc03 | 3.79705740409426 |
| TEMPLE / DAI 0.5% | balancer_ethereum | 0x1b65...a60d | 3.78885125031643 |
| TEMPLE / DAI 0.5% | balancer_ethereum | 0x8bd4...4ba0 | 3.8020821291 |
| bb-euler-USD-BPT / TEMPLE 0.5% | balancer_ethereum | 0xa718...1bbe | 3.6025285209 |
| TEMPLE / bb-a-USD 0.5% | balancer_ethereum | 0x1730...014e | 3.5123958317 |
| TEMPLE / FRAX | uniswap_v2 | 0x9fe4...ebcd | 3.5838220645 |
| TEMPLE / WETH 1% | uniswap_v3 | 0xab44...1102 | 3.5205296365 |
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.