IoTeX Developers
@iotex_dev
Official account of the @iotex_io dev community Dev docs: https://docs.iotex.io/
You might like
Hello World! 🌎🤖 @iotex_dev is the official Twitter account for IoTeX developer + tech updates. Follow us to stay up-to-date on the latest IoTeX code releases, DApps, tools, and all things tech! $IOTX
🚨 IIP-52: BLS Signature Aggregation — Voting is Live ℹ️ Right now, every @iotex_io L1 block finalized by consensus carries a signature from each delegate: that’s ~2.3KB of extra data in every block. It's been working faultlessly until now, but it slows propagation and limits…
At @iotex_io, protocol upgrades follow a clear, transparent path: Every change — from consensus rules to scalability features — goes through the IoTeX Improvement Proposal (IIP) process: ✅Drafted openly by devs & community ✅Reviewed in the Forum ✅Voted on-chain via the…
🚨 IIP-52: BLS Signature Aggregation is open for discussion in the @iotex_io community forum 🗳️ ℹ️ This proposal introduces BLS signature aggregation, compressing all delegate signatures for block finality into one single proof instead of storing them individually. Today, every…
🚨 IIP-50 is now open for voting on the @iotex_io Hub! 🔹 This proposal introduces slashing for underperforming delegates, adding a real economic cost to missed blocks. 👉 It’s a big step toward fairness and stronger network reliability. Why it matters: ✅ Delegates under…
🚨 IIP-50 is open for discussion! The goal of this proposal is to strengthen @iotex_io consensus by holding validators accountable. The proposal introduces slashing for chronically underperforming delegates, protecting network reliability and rewarding those who keep IoTeX…
The @Bino_AI swarm just got an update that our community will surely enjoy: Thanks to the new Discourse integration, Bino will be able to participate in our community discussions on @iotex_io IIPs, governance, and general community debates. Head over to…
🔄 IoTeX L1 v2.2.1 is out! 📦 Upgrade recommended, especially for API nodes. This non-hard-fork release includes: ✅ Improved API performance under high TPS ✅ More stable p2p networking ✅ Enhanced state management ✅ Faster shutdown for indexers ✅ General performance &…
To unlock real cross-chain DePIN, advanced DeFi, and AI systems, $IOTX needs a unified, liquid presence across ecosystems. IIP-48 proposes to formalize $CIOTX as the standard cross-chain IOTX token — live today on Ethereum, Solana, Polygon, and BSC, bridged via @wormhole,…
🚨 Just 2 days left to vote on IIP-42 — a major upgrade to @iotex_io Layer 1 Core. ℹ️ This proposal halves blocktime from 5s → 2.5s, doubling TPS to 2,000 — a huge step forward for real-time DePIN, autonomous machines, and low-latency AI. ✅ The proposal includes: •…
Real-time DePIN applications — from machine-to-machine networks to sensor-triggered payments or autonomous physical agents — demand low-latency, on-chain execution. IIP-42 proposes halving IoTeX Layer 1's blocktime, effectively doubling TPS to 2,000 — putting it among the…
United States Trends
- 1. Good Sunday 50.5K posts
- 2. Discussing Web3 N/A
- 3. #HealingFromMozambique 17.4K posts
- 4. #SundayMorning 1,315 posts
- 5. Blessed Sunday 16.6K posts
- 6. #sundayvibes 4,430 posts
- 7. Trump's FBI 10.5K posts
- 8. Wordle 1,576 X N/A
- 9. Auburn 47.8K posts
- 10. Gilligan's Island 5,394 posts
- 11. #SEVENTEEN_NEW_IN_TACOMA 41.1K posts
- 12. QUICK TRADE 2,157 posts
- 13. The CDC 31.7K posts
- 14. #SVT_TOUR_NEW_ 32.8K posts
- 15. FDV 5min 2,158 posts
- 16. Pegula 5,116 posts
- 17. Utah 25.2K posts
- 18. Market Cap Surges N/A
- 19. Whale - Buy 1,772 posts
- 20. Boots 51.3K posts
You might like
-
mimo protocol
@mimoprotocol -
IoTeX
@iotex_io -
qevan.io
@qevan -
Larry Pang
@larrypang -
IoTeX_Daily
@iotex_daily -
HealthBlocks
@HealthBlocks -
raullen.eth
@Raullen -
enviroBLOQ™️
@envirobloq -
IoTeX Ecosystem Updates
@iotex_community -
Jing
@cbetass -
ioPay
@iopaywallet -
Miguel
@COSmonautBE -
Luff 🕷️/IoTeX/DW3/马来西亚比特币吹水站
@LuffLiew -
Simone | Head of DevRel @ IoTeX
@zimne1 -
IoTeXLab Delegate
@iotexlab
Something went wrong.
Something went wrong.