staking4all

Category Labs is proud to introduce Cadence, our multiple-concurrent-proposers (MCP) consensus protocol that matches the optimal good-case latency of single-leader consensus while supporting arbitrarily short block intervals. When combined with BTX, our design for encrypted mempools, this represents a significant step towards solving the problem of MEV at the protocol level. In nearly every blockchain today, a single party ends up in control of each block: it decides which transactions get in, and can reorder them at will. MCP is the natural fix, but most recent designs pay for it with a separate aggregation phase, adding two extra communication rounds per block. Cadence makes the proposers part of consensus itself. Its fast path finalizes in an optimal three communication rounds, even when proposers are offline. Cadence also offers speculative finality, similar to MonadBFT, after just two rounds, revertible only if a proposer provably equivocated. In a simulation using estimated network delays between Monad mainnet's 200 globally distributed validators, finalization takes 219 ms on average, speculative finality 167 ms. Cadence pushes pipelining to the extreme: each block is proposed and finalized in its own independent consensus instance, without waiting on preceding blocks. The block interval then becomes a protocol parameter that can be arbitrarily small. At our initial target of 100 ms, a transaction waits on average just 50 ms to enter a proposal, and oracle prices, liquidations, and auctions can update every 100 ms. Cadence dynamically throttles the opening of new instances to bound the number of outstanding slots even during periods of network instability. When the network is healthy (under synchrony), a transaction included by an honest proposer can be neither dropped nor deferred (short-term censorship resistance), and no proposer can see the others' proposals in time to react (hiding). We prove both, together with safety and liveness under partial synchrony at the optimal 3f+1 fault bound. The Cadence protocol is modular: each module is simple on its own, and any of them can be swapped out without touching the rest. Cadence also builds on components already being deployed: proposals are disseminated as erasure-coded chunks over Deterministic RaptorCast, now rolling out on Monad, and validators vote on proposal digests, so voting does not wait for the full data to arrive. Start with the interactive tutorial: category.xyz/cadence. Full paper: arxiv.org/abs/2607.02275. Joint work by Kushal Babel, Fatima Elsheimy, Lioba Heimbach, Mohammad Mussadiq Jalalzai, Tobias Klenze, Jovan Komatovic, Jason Milionis, Mike Setrin, and Victor Shoup.

Aave V3 is now live on Monad @aave brings a battle-tested lending and borrowing market to Monad with support for 12 assets on day one

Introducing the @metamask Money Account, live exclusively on Monad Your new account that earns yield in DeFi with a card that spends straight from it. A new era of personal finance starts now - only possible on Monad Get started with one click: link.metamask.io/money?sig_para…

Native Bitcoin-backed borrowing is live on Public Testnet with @aave v4. Powered by Babylon Trustless Bitcoin Vaults, users can post Bitcoin as collateral and borrow without giving up custody, wrapping, or bridging. This is the latest step in building native Bitcoin-backed credit markets.

$NEAR exposure, no wallets, no keys, no custody headaches. Grayscale NEAR Trust (ticker: $GSNR) gives investors exposure to $NEAR, the native asset of @NEARProtocol, a Layer-1 powering peer-to-peer value exchange onchain.

@iotex_io v2.4.0 is shipping — our biggest mainnet upgrade of 2026. It's a mandatory hardfork activating at block 48,985,561 (≈ June 7, 2026 · 23:52 UTC). Two things we've been working toward all year: ⚡ Pectra EVM — IoTeX is now aligned with Ethereum's latest execution layer: · EIP-7702 — EOAs can act as smart accounts · EIP-2537 — native BLS12-381 (bridges, light clients, ZK) · EIP-2935 — historical block hashes from state · EIP-7623 — recalibrated calldata pricing 🛡️ Candidate Exit Queue — delegates can no longer unwind their self-stake instantly. Exits now go through a request → schedule → confirm flow, with admission rate-limited at the protocol level. A cleaner, more predictable lifecycle for our delegate set. What you need to do 👇 ▸ Delegates / Full Nodes / API Nodes — upgrade to v2.4.0 before block 48,985,561. Miss it = fork off mainnet. ▸ Wallets & dApps — check your gas estimator against the new EIP-7623 calldata floor, and add support for TxType 0x04 (SetCode) if you serialize raw transactions. ▸ Indexers / Explorers — new on-chain events from the exit queue and 7702 authorization tuples are ready to be indexed. Release notes: github.com/iotexproject/i… Huge thanks to the core team, delegates, and every dev who helped pressure-test this release. Run a node. Build on it. See you on the other side of 48,985,561. LFG. 🟢