- Topic
59k Popularity
16k Popularity
3k Popularity
14k Popularity
4k Popularity
2k Popularity
16k Popularity
22k Popularity
12k Popularity
2k 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!
👉
Ethereum confirms Mainnet upgrade on May 7, the Fusaka upgrade plan includes multiple EIP proposals.
gate News bot message, according to @ralexstokes' summary report on the 155th Ethereum Consensus Layer Core Developers Meeting (ACDC), the meeting confirmed that the Pectra Mainnet upgrade will be executed on May 7.
The meeting also discussed matters related to the Fusaka upgrade and has decided to include EIP-7594/PeerDAS and EIP-7892/BPO in the upgrade plan, while the proposer of EIP-7917's foresight stability and EIP-768 SSZ stable container are still under consideration.
Regarding the Builder API extension issue, developers pointed out that under high blob quantity, the size of the synchronous API response body is large, putting pressure on the resources of small nodes. Therefore, the development team plans to revise the API for Fusaka and will seek specific solution opinions from the builders and relay community.
Source: Wu Says