Zapper Celebrates 5th Anniversary
Zapper Celebrates 5th Anniversary
馃巶 Zapper's Got Some Candles
Web3 portfolio management platform Zapper marks its 5-year milestone this week. The platform has evolved from a simple DeFi dashboard to become a comprehensive portfolio tracking solution.
Key highlights:
- 5 years of continuous development and community growth
- Consistent platform improvements and feature additions
- Strong focus on user experience and portfolio management
The team expresses gratitude to its user base while hinting at significant developments planned for the next five years.
Zapper just turned 5 years old! 馃コ馃帄 Thank you for supporting us- it's been an incredible journey so far, and we're even more excited about the 5 years ahead of us. Time to zap it back 鈿★笍
Zapper Launches Onchain Search API with Cross-Chain Support
Zapper has released their Onchain Search API, enabling developers to integrate comprehensive blockchain search capabilities with minimal code: - Supports 49+ blockchain networks - Unified search across tokens, NFTs, accounts & transactions - Pre-enriched results including token prices, NFT floor prices, and user identity data - Chain & category-specific filtering options The API is designed for various applications including wallets, AI agents, portfolio trackers, NFT marketplaces, and social apps. Developers can access the infrastructure at [protocol.zapper.xyz/onchain-search](https://protocol.zapper.xyz/onchain-search).
Zapper Regains Control of .fi Domain After Security Incident
Zapper has successfully recovered control of their zapper.fi domain following a security incident where an attacker socially engineered their domain provider Netim. While the original website has been restored, users are advised to exclusively use **zapper.xyz** moving forward to ensure security. - Previous .fi domain was compromised through social engineering - Original website now restored and secured - Users should only use zapper.xyz for access - Previous domain (zapper.fi) no longer recommended *Note: This incident highlights the importance of verifying official domain addresses when accessing web3 services.*