- Topic
541 Popularity
485 Popularity
130k Popularity
109 Popularity
16k Popularity
- Pin
- 🎉 Hey Gate Square friends! Non-stop perks and endless excitement—our hottest posting reward events are ongoing now! The more you post, the more you win. Don’t miss your exclusive goodies! 🚀
🆘 #Gate 2025 Semi-Year Community Gala# | Square Content Creator TOP 10
Only 1 day left! Your favorite creator is one vote away from TOP 10. Interact on Square to earn Votes—boost them and enter the prize draw. Prizes: iPhone 16 Pro Max, Golden Bull sculpture, Futures Vouchers!
Details 👉 https://www.gate.com/activities/community-vote
1️⃣ #Show My Alpha Points# | Share your Alpha points & gains
Post your - 🚀 ETH jumped to $4,600 this morning, up 8.69% in 24h!
Just shy of the $4,891 ATH—think it breaks through?
📍 Follow Gate_Square, vote and drop your reason.
🎁 4 winners split $100 Futures Voucher! - 📢 Exclusive on Gate Square — #PROVE Creative Contest# is Now Live!
CandyDrop × Succinct (PROVE) — Trade to share 200,000 PROVE 👉 https://www.gate.com/announcements/article/46469
Futures Lucky Draw Challenge: Guaranteed 1 PROVE Airdrop per User 👉 https://www.gate.com/announcements/article/46491
🎁 Endless creativity · Rewards keep coming — Post to share 300 PROVE!
📅 Event PeriodAugust 12, 2025, 04:00 – August 17, 2025, 16:00 UTC
📌 How to Participate
1.Publish original content on Gate Square related to PROVE or the above activities (minimum 100 words; any format: analysis, tutorial, creativ - 💙 Gate Square #Gate Blue Challenge# 💙
Show your limitless creativity with Gate Blue!
📅 Event Period
August 11 – 20, 2025
🎯 How to Participate
1. Post your original creation (image / video / hand-drawn art / digital work, etc.) on Gate Square, incorporating Gate’s brand blue or the Gate logo.
2. Include the hashtag #Gate Blue Challenge# in your post title or content.
3. Add a short blessing or message for Gate in your content (e.g., “Wishing Gate Exchange continued success — may the blue shine forever!”).
4. Submissions must be original and comply with community guidelines. Plagiarism or re - 🎉 The #CandyDrop Futures Challenge# is live — join now to share a 6 BTC prize pool!
📢 Post your futures trading experience on Gate Square with the event hashtag — $25 × 20 rewards are waiting!
🎁 $500 in futures trial vouchers up for grabs — 20 standout posts will win!
📅 Event Period: August 1, 2025, 15:00 – August 15, 2025, 19:00 (UTC+8)
👉 Event Link: https://www.gate.com/candy-drop/detail/BTC-98
Dare to trade. Dare to win.
Shiba Inu Dev Issues Major Clarification for SHIB Community: Details - U.Today
Shiba Inu developer Kaal Dhairya has recently addressed concerns in the SHIB community, which arose after X account "Woof decentra" tweeted that its official Shiba Inu: Deployer 1 wallet was hacked.
Woof decentra warned that recent transactions, including new token launches, have been compromised as attackers have seized control of the wallet, urging the SHIB community to ignore activity from the address: "My official Shiba Inu: Deployer 1 wallet (0xA221af4a429b734Abb1CC53Fbd0c1D0Fa47e1494) was hacked. All recent transactions, including new token launches, are not mine. Be careful and ignore any activity from this address."
This tweet caught the attention of the SHIB community, which enquired about its implications. The Shiba Inu deployer 1 is assumed to be associated with the LEASH contract, hence the concerns from the SHIB community.
SHIB developer responds
Shiba Inu developer Kaal Dhairya has responded to the latest development, waving off concerns of the incident affecting critical Shiba Inu ecosystem systems. "No critical systems are tied to it," Kaal said on X, referring to the Shiba Inu deployer 1 wallet. He, however, highlighted a known LEASH issue with an earlier developer.
While the wallet can and will be used to launch new tokens in the future, as has been happening, Kaal warned the Shiba Inu community that these tokens could be scams.
This clarification from the Shiba Inu developer is deemed essential following the recent LEASH development.
On Aug. 11, the LEASH total supply increased by nearly 10%, contradicting the commonly held belief that its supply was fixed and rebasing was disabled. According to Kaal, while owners had renounced addresses, functional control over supply adjustments remained through an orchestrated contract chain.
Moving forward, two suggestions lie on the table: negotiate with the original developer, which has been fruitless in the past, or launch LEASH v2 on a new, audited, non‑rebase contract, subject to DAO approval.