QUICK staking rewards have been replenished 🔥 Stake QUICK on @base, earn QUICK (~16.45% APR). dapp.quickswap.exchange/dash…

⏰ Only 24 hours left! Voting for SparkDEX's first DAO proposal ends tomorrow. If you haven't voted yet, there's still time to share your opinion onchain. SparkDEX community ftw 💪 sparkdex.ai/governance/propo…

Another 2,600,000 QUICK were accumulated back over the last week 🐲 Current value: ~$29,536

DeFi Governance with SparkDEX 🗳️ Join us for an upcoming livestream with @0xQuantic and @AlexiAtlas, Co-founder of SparkDEX, to explore how governance works in DeFi and why it matters for protocols, and long-term ecosystem growth. We’ll discuss governance design, community participation, and how @SparkDexAI is approaching this on Flare. Set your reminder and join us live this Wednesday! youtube.com/watch?v=hgYjVesz…

The SparkDEX DAO's first governance proposal is HERE! It's time for the SparkDEX community to decide how protocol revenue and SPRK emissions should be distributed. 🗓 Voting: Begins May 13 at 11:00 AM UTC 🗣 Discussion: x.com/SparkDexAI/status/2052…

Aave LLC has filed an emergency motion to vacate a restraining notice served on Arbitrum DAO on May 1, 2026 that attempts to seize approximately $71 million in ETH belonging to victims of the April 18 exploit. A thief does not gain lawful ownership of stolen property simply by taking it, and the law is clear on this. Those assets were recovered to be returned to users victimized in the April 18, 2026 exploit. Freezing them harms the very people this recovery effort is designed to protect. We’ve asked the court for an expedited hearing and a temporary vacatur, and we are continuing to work alongside the Arbitrum community and DeFi United to make affected users whole.

UPDATE: DeFi United, a recovery fund spearheaded by @Aave after the @KelpDAO exploit, has raised ~$303M in commitments from across the ecosystem to make affected $rsETH holders whole.

Update on rsETH incident: WETH reserves on the Ethereum Core V3 market have been unfrozen and users can supply WETH to Ethereum Core V3 again. WETH LTV remains at 0. WETH reserves on Ethereum Prime, Arbitrum, Base, Mantle, and Linea remain frozen. Aave service providers will continue to work on next steps and provide updates accordingly.

The Arbitrum Security Council has taken emergency action to freeze the 30,766 ETH being held in the address on Arbitrum One that is connected to the KelpDAO exploit. The Security Council acted with input from law enforcement as to the exploiter’s identity, and, at all times, weighed its commitment to the security and integrity of the Arbitrum community without impacting any Arbitrum users or applications. After significant technical diligence and deliberation, the Security Council identified and executed a technical approach to move funds to safety without affecting any other chain state or Arbitrum users. As of April 20 11:26pm ET the funds have been successfully transferred to an intermediary frozen wallet. They are no longer accessible to the address that originally held the funds, and can only be moved by further action by Arbitrum governance, which will be coordinated with relevant parties.

يستأنف أبناؤنا وبناتنا الطلبة اليوم الدراسة الحضورية في كافة جامعاتنا ومدارسنا.. بعد أن أثبتت منظومتنا التعليمية قدرتها الاستثنائية على استمراريتها الكاملة في ظل الظروف التي مرّت بها المنطقة. رسالتي إلى الطلبة والطالبات : نحن دولة لا تقف عند التحديات.. نحن دولة لا تقف عن التعلم والتعليم .. نحن دولة لا تقف مسيرتها ولا تتعطل تنميتها .. نحن دولة تراهن عليكم وتصنع مستقبلها بكم ومعكم ومن أجلكم . #فخورين_بالإمارت

FIP.16 🤝 SparkDEX Remember: SparkDEX isn’t just built on @FlareNetworks. It has an FTSO provider too. FIP.16 shifts rewards to data contribution and accuracy. That means SparkDEX is earning at the application AND protocol layer.

5,191,500 QUICK tokens accumulated back over the last week. This marks our largest buyback to date, currently valued at ~$57,417. Dragons raising the bar 🐲

Cohort 1 of new Sky Agents coming from Obex is a game changer for Sky These agents will showcase the power of the Sky Agent Framework: parallel scaling and innovation at the edges of the ecosystem, while the core can stay stable, reliable and focused on risk management

Huge milestone unlocked: we've just surpassed 60,000,000 QUICK burned 🔥🔥 Just to put that into perspective, that's: • 6.39% of the total supply • 7.64% of the circulating supply • Over $590,000 in value Burns for the QUICK token continue to accelerate, also increasing scarcity of the token. Couple that with the ongoing buybacks, and you've got the perfect storm. Dragons on a mission.

A very important document. Let's walk through this one "goal" at a time. We'll start with fast slots and fast finality. I expect that we'll reduce slot time in an incremental fashion, eg. I like the "sqrt(2) at a time" formula (12 -> 8 -> 6 -> 4 -> 3 -> 2, though the last two steps are more speculative and depend on heavy research). It is possible to go faster or slower here; but the high level is that we'll view the slot time as a parameter that we adjust down when we're confident it's safe to, similar to the blob target. Fast slots are off in their own lane at the top of the roadmap, and do not really seem to connect to anything. This is because the rest of the roadmap is pretty independent of the slot time: we would need to do roughly the same things whether the slot time is 2 seconds or 32 seconds There are a few intersection areas though. One is p2p improvements. @raulvk has recently been working on an optimized p2p layer for Ethereum, which uses erasure coding to greatly improve on the bandwidth/latency tradeoff frontier. Roughly speaking: in today's design, each node receives a full block body from several peers, and is able to accept and rebroadcast it as soon as it receives the first one. If the "width" (number of peers sending you the block) is low, then one bad peer can greatly delay when you receive the block. If width is high, there is a lot of unneeded data overhead. With erasure coding, you can choose a k-of-n setup, eg: split each block into 8 pieces so that with any 4 of them you can reconstruct the full block. This gives you much of the redundancy benefits of high width, without the overhead. We have stats that show that this architecture can greatly reduce 95th percentile block propagation time, making shorter slots viable with no security tradeoffs (except increased protocol complexity, though here the performance-gain-to-lines-of-code ratio is quite favorable) Another intersection area is the more complex slot structure that comes with ePBS, FOCIL, and the fast confirmation rule. These have important benefits, but they decrease the safe latency maximum from slot/3 to slot/5. There's ongoing research to try to pipeline things better to minimize losses (also note: the slot time is lower-bounded not just by slot latency, but also by the fixed-cost part of ZK prover latency), but there are some tradeoffs here. One way we are exploring to compensate for this is to change to an architecture where only ~256-1024 randomly selected attesters sign on each slot. For a fork choice (non-finalizing) function, this is totally sufficient. The smaller number of signatures lets us remove the aggregation phase, shortening the slots. Fast finality is more complex (the ultimate protocol is IMO simpler than status quo Gasper, but the change path is complex). Today, finality takes 16 minutes (12s slots * 32 slot epochs * 2.5 epochs) on average. The goal is to decouple slots and finality, so allow us to reason about both separately, and we are aiming to use a one-round-finality BFT algorithm (a Minimmit variant) to finalize. So endgame finality time might be eg. 6-16 sec. Because this is a very invasive set of changes, the plan is to bundle the largest step in each change with a switch of the cryptography, notably to post-quantum hash-based signatures, and to a maximally STARK-friendly hash (there are three possible responses to the recent Poseidon2 attacks: (i) increase round count or introduce other countermeasures such as a Monolith layer, (ii) go back to Poseidon1, which is even more lindy than Poseidon2 and has not seen flaws, (iii) use BLAKE3 or other maximally-cheap "conventional" hash. All are being researched). Additionally, there is a plan to introduce many of these changes piece-by-piece, eg. "1-epoch finality" means we adjust the current consensus to change from FFG-style finalization to Minimmit-style finalization. One possible finality time trajectory is: 16 min (today) -> 10m40s (8s slots) -> 6m24s (one-epoch finality) -> 1m12s (8-slot epochs, 6s slots) -> 48s (4s slots) -> 16s (minimmit) -> 8s (minimmit with more aggressive parameters) One interesting consequence of the incremental approach is that there is a pathway to making the slots quantum-resistant much sooner than making the finality quantum-resistant, so we may well quite quickly get to a regime where, if quantum computers suddenly appear, we lose the finality guarantee, but the chain keeps chugging along. Summary: expect to see progressive decreases of both slot time and finality time, and expect to see these changes to be intertwined with a "ship of Theseus" style component-by-component replacement of Ethereum's slot structure and consensus with a cleaner, simpler, quantum-resistant, prover-friendly, end-to-end formally-verified alternative.

We're officially live with @FlareNetworks! Join the livestream now to hear our Co-Founders walk through: • Liquid staking (stFLR) • V4 DEX & rewards migrations • Future SparkDEX updates x.com/i/broadcasts/1jMJgRRmy…

Tune into an exlusive livestream with Flare, where SparkDEX Co-Founders @AlexiAtlas and @0xMetavault will walk through updates and new features for our stFLR and V4 DEX launch. 📅 Tuesday, February 17 at 2:30 PM UTC