- Topic
53k Popularity
32k Popularity
9k Popularity
11k Popularity
4k Popularity
4k Popularity
15k Popularity
22k Popularity
13k Popularity
3k Popularity
- Pin
- 🌟 Photo Sharing Tips: How to Stand Out and Win?
1.Highlight Gate Elements: Include Gate logo, app screens, merchandise or event collab products.
2.Keep it Clear: Use bright, focused photos with simple backgrounds. Show Gate moments in daily life, travel, sports, etc.
3.Add Creative Flair: Creative shots, vlogs, hand-drawn art, or DIY works will stand out! Try a special [You and Gate] pose.
4.Share Your Story: Sincere captions about your memories, growth, or wishes with Gate add an extra touch and impress the judges.
5.Share on Multiple Platforms: Posting on Twitter (X) boosts your exposure an
- 🎉 [Gate 30 Million Milestone] Share Your Gate Moment & Win Exclusive Gifts!
Gate has surpassed 30M users worldwide — not just a number, but a journey we've built together.
Remember the thrill of opening your first account, or the Gate merch that’s been part of your daily life?
📸 Join the #MyGateMoment# campaign!
Share your story on Gate Square, and embrace the next 30 million together!
✅ How to Participate:
1️⃣ Post a photo or video with Gate elements
2️⃣ Add #MyGateMoment# and share your story, wishes, or thoughts
3️⃣ Share your post on Twitter (X) — top 10 views will get extra rewards!
👉
User negligence led to a loss of 20,000 USDT, and the configuration error in the Uniswap V3 liquidity pool has attracted attention.
According to the Gate News bot, data from Etherscan shows that user 0x7e…3207 completed a transaction of SPK and USDT through the Uniswap V3 platform at 16:00 UTC+8, exchanging 1 SPK for 19,686.87 USDT.
According to the analysis report by researcher @web3_mario, user teochew.eth previously created a liquidity pool with a 1% transaction fee on Uniswap and injected 20,000 USD into it as unilateral liquidity. Due to the set price being too high, a single transaction resulted in the majority of the USDT in the pool being swapped.
teochew.eth subsequently sent a message to 0x7e…3207 via on-chain transaction, acknowledging the oversight of misreading the pool direction and requesting the other party to return part of the funds.
Original Link