iotex_dev's profile picture. Official account of the @iotex_io dev community 
Dev docs: https://docs.iotex.io/

IoTeX Developers

@iotex_dev

Official account of the @iotex_io dev community Dev docs: https://docs.iotex.io/

Fixado

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…

iotex_dev's tweet image. 🚨 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…

iotex_dev's tweet image. 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…

iotex_dev's tweet image. 🚨 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…

iotex_dev's tweet image. 🚨 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…

iotex_dev's tweet image. 🚨 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_dev's tweet image. 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 &…

iotex_dev's tweet image. 🔄 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,…

iotex_dev's tweet image. 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: •…

iotex_dev's tweet image. 🚨 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…

iotex_dev's tweet image. 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…

IoTeX Developers repostou

CGT Semifinals - Ep1 x.com/i/broadcasts/1…


Loading...

Something went wrong.


Something went wrong.