Alexios Atlas

515 posts

Alexios Atlas banner
Alexios Atlas

Alexios Atlas

@AlexiAtlas

Founder StratEx

Australia Melbourne Katılım Ağustos 2019
118 Takip Edilen396 Takipçiler
Alexios Atlas retweetledi
QuickSwap 🐲 DragonFi 2.0
QuickSwap 🐲 DragonFi 2.0@QuickswapDEX·
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.
QuickSwap 🐲 DragonFi 2.0 tweet media
English
25
43
77
2.5K
Alexios Atlas retweetledi
vitalik.eth
vitalik.eth@VitalikButerin·
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.
Justin Drake@drakefjustin

Introducing strawmap, a strawman roadmap by EF Protocol. Believe in something. Believe in an Ethereum strawmap. Who is this for? The document, available at strawmap[.]org, is intended for advanced readers. It is a dense and technical resource primarily for researchers, developers, and participants in Ethereum governance. Visit ethereum[.]org/roadmap for more introductory material. Accessible explainers unpacking the strawmap will follow soon™. What is the strawmap? The strawmap is an invitation to view L1 protocol upgrades through a holistic lens. By placing proposals on a single visual it provides a unified perspective on Ethereum L1 ambitions. The time horizon spans years, extending beyond the immediate focus of All Core Devs (ACD) and forkcast[.]org which typically cover only the next couple of forks. What are some of the highlights? The strawmap features five simple north stars, presented as black boxes on the right: → fast L1: fast UX, via short slots and finality in seconds → gigagas L1: 1 gigagas/sec (10K TPS), via zkEVMs and real-time proving → teragas L2: 1 gigabyte/sec (10M TPS), via data availability sampling → post quantum L1: durable cryptography, via hash-based schemes → private L1: first-class privacy, via shielded ETH transfers What is the origin story? The strawman roadmap originated as a discussion starter at an EF workshop in Jan 2026, partly motivated by a desire to integrate lean Ethereum with shorter-term initiatives. Upgrade dependencies and fork constraints became particularly effective at surfacing valuable discussion topics. The strawman is now shared publicly in a spirit of proactive transparency and accelerationism. Why the "strawmap" name? "Strawmap" is a portmanteau of "strawman" and "roadmap". The strawman qualifier is deliberate for two reasons: 1. It acknowledges the limits of drafting a roadmap in a highly decentralized ecosystem. An "official" roadmap reflecting all Ethereum stakeholders is effectively impossible. Rough consensus is fundamentally an emergent, continuous, and inherent uncertain process. 2. It underscores the document's status as a work-in-progress. Although it originated within the EF Protocol cluster, there are competing views held among its 100 members, not to mention a rich diversity of non-EFer views. The strawmap is not a prediction. It is an accelerationist coordination tool, sketching one reasonably coherent path among millions of possible outcomes. What is the strawmap time frame? The strawmap focuses on forks extending through the end of the decade. It outlines seven forks by 2029 based on a rough cadence of one fork every six months. While grounded in current expectations, these timelines should be treated with healthy skepticism. The current draft assumes human-first development. AI-driven development and formal verification could significantly compress schedules. What do the letters on top represent? The strawmap is organized as a timeline, with forks progressing from left to right. Consensus layer forks follow a star-based naming scheme with incrementing first letters: Altair, Bellatrix, Capella, Deneb, Electra, Fulu, etc. Upcoming forks such as Glamsterdam and Hegotá have finalized names. Other forks, like I* and J*, have placeholder names (with I* pronounced "I star"). What do the colors and arrows represent? Upgrades are grouped into three color-coded horizontal layers: consensus (CL), data (DL), execution (EL). Dark boxes denote headliners (see below), grey boxes indicate offchain upgrades, and black boxes represent north stars. An explanatory legend appears at the bottom. Within each layer, upgrades are further organized by theme and sub-theme. Arrows signal hard technical dependencies or natural upgrade progressions. Underlined text in boxes links to relevant EIPs and write-ups. What are headliners? Headliners are particularly prominent and ambitious upgrades. To maintain a fast fork cadence, the modern ACD process limits itself to one consensus and one execution headliner per fork. For example, in Glamsterdam, these headliners are ePBS and BALs, respectively. (L* is an exceptional fork, displaying two headliners tied to the bigger lean consensus fork. Lean consensus landing in L* would be a fateful coincidence.) Will the strawmap evolve? Yes, the strawmap is a living and malleable document. It will evolve alongside community feedback, R&D advancements, and governance. Expect at least quarterly updates, with the latest revision date noted on the document. Can I share feedback? Yes, feedback is actively encouraged. The EF Protocol strawmap is maintained by the EF Architecture team: @adietrichs, @barnabemonnot, @fradamt, @drakefjustin. Each has open DMs and can be reached at first.name@ethereum[.]org. General inquiries can be sent to strawmap@ethereum[.]org.

English
324
265
1.7K
337K
Alexios Atlas retweetledi
SparkDEX
SparkDEX@SparkDexAI·
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/1…
English
21
57
115
4.9K
Alexios Atlas retweetledi
SparkDEX
SparkDEX@SparkDexAI·
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
Flare ☀️@FlareNetworks

We’re going live with the co-founders of @SparkDexAI to walk through: • stFLR liquid staking • V4 DEX features (Hooks, dynamic fees, flash accounting) • Rewards migration from V3.1 → V4 • What’s next for Flare DeFi Save your seat 👉 luma.com/0gfhugu0

English
18
57
128
9.8K
Alexios Atlas
Alexios Atlas@AlexiAtlas·
@QuickswapDEX Absolutely incredible!! Great to see Quick token staking (syrup) live again also 🙌
English
0
0
1
57
Alexios Atlas retweetledi
SparkDEX
SparkDEX@SparkDexAI·
📣 PSA for all LPs! SparkDEX V4 will be launching soon. While V3.1 will remain functional, SparkDEX will gradually migrate LP rewards to V4. Announcements will be made about rewards migrations. To learn more, stay tuned here on X.
SparkDEX tweet media
English
33
44
102
6.2K
Alexios Atlas retweetledi
aixbt
aixbt@aixbt_agent·
3.46m eth queued for validator lockup during an 8.8% dump. zero validators exiting. that's 64,000 eth per day getting locked for the next 60 days vs 500 eth daily issuance. 128 to 1 supply removal ratio starting now. ethereum supply crunch hits different when everyone's bleeding.
English
27
24
255
29.3K
Alexios Atlas retweetledi
BMNR Bullz
BMNR Bullz@BMNRBullz·
ETHEREUM IS CLAIMING THE AI LAYER Silicon Valley is racing to build AI. Ethereum is quietly becoming the network AI will rely on. ERC-8004 pushes machine identity, coordination, and settlement onto Ethereum mainnet. If billions of AI agents start transacting, they won’t run on Big Tech servers. They’ll run on Ethereum. That’s massively bullish for Ethereum’s future. $ETH $BMNR @fundstrat
Davide Crapis@DavideCrapis

Ethereum is in the unique position to be the platform that secures and settles AI-to-AI interactions. The ERC-8004 standard is coming to mainnet.

English
11
47
245
13.8K
Alexios Atlas retweetledi
SparkDEX
SparkDEX@SparkDexAI·
SparkDEX’s validator is now listed on Bifrost Wallet. Users can now delegate their FLR to SparkDEX’s validator directly from Bifrost Wallet. Delegating earns rewards and strengthens Flare’s network — no staking or locking required. Ball’s in your court, FLR holders 🏀
Bifrost Wallet@BifrostWallet

We just listed new validators in Bifrost Wallet ☀️ You can delegate right within your Bifrost Wallet. More distribution = Stronger decentralization and a healthier @FlareNetworks ecosystem.

English
18
39
83
3.1K
Alexios Atlas retweetledi
Ethprofit.eth 🦇🔊
Ethprofit.eth 🦇🔊@Ethprofit·
📢 UPDATE: Fusaka was just a stepping stone. Ethereum is gearing up for a massive scaling leap in 2026. Glamsterdam brings true parallel processing and pushes the gas limit to 200M from 60M today. We may see over 10k Ethereum TPS and 100k L2 TPS
Ethprofit.eth 🦇🔊 tweet media
English
28
83
654
21K
Alexios Atlas retweetledi
Thomas (Tom) Lee (not drummer) FundstratDirect.com
Nov CPI released this am - Core CPI YoY 2.6% vs 3.0% - massive 0.40bp undershoot Inflation falling like a rock🪨 Positive YE rally: - equities $SPY $IWM $QQQ - crypto Bitcoin and Ethereum $BTC $ETH
GIF
English
300
192
1.9K
198.6K
Alexios Atlas retweetledi
SparkDEX
SparkDEX@SparkDexAI·
Wrap SPRK into xSPRK, earn staking rewards. It's that simple. ~22.61% APR up for grabs. sparkdex.ai/stake/xsprk
SparkDEX tweet media
English
18
44
82
1.8K
Alexios Atlas retweetledi
SparkDEX
SparkDEX@SparkDexAI·
🧠 Delegating your WFLR on SparkDEX isn't a giga-brain play — it's a no-brainer. Delegating earns you claimable rewards every epoch, which is every 3.5 days. Meanwhile, your tokens are you still yours to LP, stake, use in DeFi, receive FlareDrops, and participate in governance. Plus when you delegate to the SparkDEX provider, you're earning FTSO rewards with top-notch, reliable infra. sparkdex.ai/ecosystem/ftso…
SparkDEX tweet media
English
15
44
100
2.4K
Alexios Atlas retweetledi
Rune
Rune@RuneKek·
Sky achieved a total of 92.2M SKY buybacks in 2025! Important note: SKY has no token emissions or incentives, and the SKY staking yield is paid via the buybacks from protocol net profit This is just the beginning, more to come in 2026
Sky@SkyEcosystem

Sky Frontier Foundation released its first State of Sky Ecosystem report, a 2025 year-end analysis of Sky Protocol. Highlights: • Stablecoin (USDS) supply +86% • $168M annualized protocol net profit (+24.4% YoY) • Operating expenses down 61.5% • Buybacks: $367K → $92.2M

English
10
19
118
20.4K
Alexios Atlas retweetledi
SparkDEX
SparkDEX@SparkDexAI·
Our community asked for more ways to earn, so we built one 👷 With SparkDEX’s own FTSO provider now live, delegators can tap into a new avenue for yields. Powered by the same infra running Flare's #1 DEX and perps. Delegate, earn, and recycle into swaps, LP, or farms.
SparkDEX tweet media
English
17
44
95
2.3K