🏴󠁧󠁢󠁥󠁮󠁧󠁿 Chelsea vs Barcelona 🇪🇸 – the headline showdown of the Champions League night 🔥 London gets the biggest blast of the round as an in-form Chelsea hosts Hansi Flick’s free-flowing Barcelona. If you’re looking for pure football fireworks, this is the one. Both sides have already put themselves under pressure in the group stage and, right now, neither sits inside the coveted top eight. Tonight is make-or-break – one club climbs back into the fight, the other sinks deeper into the mid-table mess. High stakes, elite talent, two giants with zero margin for error.

🏴󠁧󠁢󠁥󠁮󠁧󠁿 Chelsea vs Barcelona 🇪🇸 – the headline showdown of the Champions League night 🔥 London gets the biggest blast of the round as an in-form Chelsea hosts Hansi Flick’s free-flowing Barcelona. If you’re looking for pure football fireworks, this is the one. Both sides have already put themselves under pressure in the group stage and, right now, neither sits inside the coveted top eight. Tonight is make-or-break – one club climbs back into the fight, the other sinks deeper into the mid-table mess. High stakes, elite talent, two giants with zero margin for error.

New Discord Announcement from THORChain Devs #🚨thornode-mainnet **Mimir Change Proposal: Improving Swap Queue Throughput** I am proposing a community vote to update an older, rarely-touched mimir parameter: MinSwapsPerBlock. This setting—together with others—governs how many swaps are processed per block. It is important to outline the current behavior so all node operators understand the impact clearly. **Background** The protocol enforces a cap on the number of swaps executed per block to prevent malicious actors from flooding the system with an excessive volume of transactions. Without this cap, a spam campaign involving tens of thousands of swaps could significantly delay block production. Since genesis, this upper limit has been set to 100 swaps per block. The system was originally designed to process roughly half of the swap queue each block, subject to a minimum threshold defined by `MinSwapsPerBlock`, which has remained at 10. In practice: • If the queue holds 30 swaps, the system processes 15 (typically ordered from largest to smallest, though the algorithm includes additional nuances). • If the queue holds 14 swaps, the system processes 10—the enforced minimum—rather than 7. This design parallels Bitcoin’s fee-based prioritization model: higher-value transactions naturally move ahead of smaller ones. Likewise, THORChain’s architecture biases toward larger swaps (which produce more fees), thereby encouraging arbitrageurs to increase their trade sizes and accept tighter margins to outrun competitors). **Why This Matters Now** This mechanism was conceived before streaming swaps existed. Historically, swaps executed in a single block, but under the current model swaps often persist across many blocks (due to streaming). As a result, smaller swaps can experience substantial delays when the queue becomes congested. **Proposed Adjustment** Raising `MinSwapsPerBlock` from 10 → 50 should meaningfully accelerate how quickly the protocol clears the swap queue. This change increases per-block throughput and reduces the likelihood that small swaps remain stuck behind larger flows. There is a possibility that block times may rise modestly, though the magnitude is uncertain and may be negligible. **Request to Node Operators** I am asking all node operators to review this proposal and vote accordingly: `make mimir MinSwapsPerBlock => 50` @everyone

Builders recognized. ✅ World Mobile Token is now live on Coinbase New access. New reach. New opportunities for communities and institutions to join the movement. Welcome to the next chapter. Explore $WMTX on Coinbase:

coinbase.com

Read the full announcement:

worldmobile.io

Checkout our recap from ArbiLink - our local builder meetup in Brazil 🇧🇷

x.com