- Pin
- #Over 100 Companies Hold Over 830,000 BTC#
According to reports as of June 19, more than 100 companies collectively hold over 830,000 BTC, worth about $86.476 billion.
💬 Do you think Bitcoin will become a new norm for corporate asset allocation? How might this impact Bitcoin’s price? What’s your recent BTC trading strategy? Post to share your price predictions, market analysis, and strategies with us using the topic tag!
🎁 Meanwhile, Gate’s BTC Staking event is in full swing! Simply stake your BTC and earn up to 3% APY. Click the link to start staking and enjoy your earnings: https://ww - 🏁 Gate Red Bull Racing Tour 2025 In Full Swing!
Up to now, the total trading volume exceeded $2 billion, with top trader trading volume nearing $200 million
Join the race now & fuel your trades for real-world rewards:
✅ 5,000 GT Prize Pool
✅ VIP Seat at an F1 Grand Prix
✅ Futures Vouchers for New Signups
Start your engines & trade fast
Top the leaderboards. The Race is ON!
👉 Go Now: www.gate.com/competition/f1rb/s1
#GateRedBullRacingTour# - 📢 Gate releases its latest Reserve Audit Report!
💰 Total reserves: $10.453B
🟢 Excess reserves: $1.96B — ensuring full coverage and extra security for user assets.
Gate continues to uphold 100% proof-of-reserves and full transparency.
🔗 Read the full report: https://www.gate.com/zh/announcements/article/45617
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