Stephen 🔺

320 posts

Stephen 🔺 banner
Stephen 🔺

Stephen 🔺

@stephenbuttolph

avaͨlanche͢go iś͖̩͇̗̪̏̈́ not a fo͛ͫrk of go͞ ether̶eüm

Katılım Mayıs 2018
80 Takip Edilen2.6K Takipçiler
Stephen 🔺 retweetledi
Georgios Konstantopoulos
please do not greenlight eip8141, if we want pq accounts we can do it another way but eip8141 is just bad about mempool validation rules and will put us into erc7562 land which is terrible add the validation rules to the eip and examine holistically eip8141 is a mistake as-is
English
9
3
87
14.2K
Seb 🔺
Seb 🔺@Seb_1716·
So we were just exit liquidity for these guys the whole time? Quite disappointed in the lack of follow through of the core team. When I invested in $AVAX back then I felt this team was different, now Kevin has dropped the project to build sci-fi batteries, Luigi will enjoy his life in Portofino and Emin hasn't been seen in months... What is happening ? You guys pitched a life changing blockchain technology. I don't think the job is done. What does this signal to investors ?
Seb 🔺 tweet media
Luigi D'Onorio DeMeo@luigidemeo

Some personal news* - After nearly 5 years, I’ve made the decision to step down from my role as Chief Strategy Officer of @AvaLabs. This comes after a lengthy period of conversations and reflection. Officially, and for the past several months, I’ve been transitioning out of my responsibilities and preparing for a new chapter. Since joining in early 2021, just months after Avalanche's mainnet launch, when our team was a lean group of ~20 people, @avax has been my home, my passion, and a defining part of my career. We've delivered countless upgrades, scaled a network attracting billions in capital across more than 80 chains, brought major banks, asset managers, and enterprises onchain, powered gaming ecosystems, and fostered a vibrant community. I'm proud of what we've built together and the role I was able to play in it. I will forever be grateful to all the people at Ava Labs and the broader Avalanche ecosystem but in particular @el33th4xor, @John1wu, @kevinsekniqi and @JohnNahas84 for the opportunities to grow both personally and professionally. It's a rare privilege to contribute to such a talented team driven by an ambitious mission. As for Avalanche, I remain a believer in the technology, the opportunity, and many of my colleagues. I’ll continue observing, building, advising where valuable, and supporting from the sidelines. I plan to complete my non-operating term as one of the Board Directors for the Avalanche Foundation, which concludes in a few months. As for what’s next, for now I'm pausing to recharge. I’ll be catching up on precious family time (including with our third child, now six months old) and investing in myself a bit. I have and will continue having conversations about where I’m best positioned to contribute to this industry, perhaps as a founder or in another role. I remain as optimistic as ever that blockchains will transform the internet and I intend to contribute my energy towards that future. Stay tuned! -Luigi

English
53
12
144
31.8K
Stephen 🔺 retweetledi
Avalanche Developers 🔺
Avalanche Developers 🔺@AvaxDevelopers·
We’re hosting a major ACP discussion on Thursday, December 18, at 13:30 UTC / 10:30 ET, and you should be there. @rrazvan1 will break down ACP-236 (continuous staking on the P-Chain), and @iJaack will lead a discussion on his proposal to change the delegation dynamics (ACP-247) These updates could meaningfully shift validator workflows, economics, and decentralization. We want the whole community in the room!
English
15
45
198
32.8K
Stephen 🔺 retweetledi
Furkan 🔺
Furkan 🔺@thefurkan·
🚨 P256 (secp256r1) curve precompile is now live on @avax C-Chain! 🚨 Verification of ECDSA signatures over secp256r1 now costs just 6,900 gas. 🔺 This unlocks native compatibility with Apple Secure Enclave, Android Keystore, HSMs, and WebAuthn devices, enabling device-native signing without seed phrases. Wallets leveraging this precompile can deliver native, effortless onboarding, eliminating one more barrier to mainstream crypto adoption. build.avax.network/docs/acps/204-…
English
7
13
59
3K
Stephen 🔺 retweetledi
Daniel Gruesso
Daniel Gruesso@danielgruesso·
@avax Already seeing Teleporter messaging costs drop by 87% in some instances, thanks to ACP-181 🚀
Daniel Gruesso tweet media
English
1
3
16
1.7K
Stephen 🔺
Stephen 🔺@stephenbuttolph·
@twitt_tr @Keidaten The minimum block time has already been decreasing. It's currently at 1979 ms per block.
English
1
1
7
554
tactical_retreat
tactical_retreat@twitt_tr·
The target block production has never really mattered though. If you wanted 2 second blocktimes, it was always just an (existing) flag away. But no one wants 2 second blocktimes. They want faster blocktimes. And we had faster blocktimes (than this). Another option could have been to set it at 1 second? So things would be better from the start? Why is making things worse even on the table here? I shouldn't need to advocate for not making things worse. What world are we living in here? Is there no awareness of competition? It's 2025 and you guys are making changes like limiting sustained throughput to ethereum levels and forcing blocktime to 2 seconds. Yeah, it's great that it's adjustable by validators. And gas limit did eventually come up, months later. Are we going to wait for months for minimum block time to drop now?
English
2
2
15
1.8K
Stephen 🔺
Stephen 🔺@stephenbuttolph·
@twitt_tr @Keidaten The prior block production mechanism attempted (poorly) to target 2s block times. Another option could have been to instead set it to the long running average block time (around 1.6s). I'd love for you to advocate for any such opinions during the ACP calls next time!
English
1
1
7
689
tactical_retreat
tactical_retreat@twitt_tr·
@Keidaten A bold move to reduce performance until the same people who reduced performance can vote to increase performance.
English
2
0
12
710
Stephen 🔺 retweetledi
Me🔺g
Me🔺g@MeagFitzgerald·
ACP-236 introduces continuous staking to the Avalanche Primary Network. Validators can stake their tokens continuously, allowing their stake to compound and accrue rewards over time. Questions? Post them in the discussion! github.com/avalanche-foun…
English
3
11
28
1.1K
Stephen 🔺 retweetledi
Avalanche Developers 🔺
Avalanche Developers 🔺@AvaxDevelopers·
The Mainnet release for the Avalanche Granite upgrade has been published. The Mainnet activation is scheduled for November 19th, 2025 @ 11am ET / 3pm UTC. All Mainnet node operators must upgrade to v1.14 before the scheduled activation time 👇 build.avax.network/blog/granite-u…
English
21
115
382
51.3K
Suyan Qu
Suyan Qu@suyan_qu·
This is my Day -1 interning at Ava Labs. The past three months have been amazing. It is a great pleasure to work with such a group of talented people who share the same passion as I do. Saying farewell is never easy, but I am sure we will meet again soon :)
Suyan Qu tweet media
English
1
0
2
329
Stephen 🔺 retweetledi
Furkan 🔺
Furkan 🔺@thefurkan·
This is actually a bigger deal than it seems. Proper on-chain privacy has been promised many times before, but none of the previous solutions have been remotely practical due to high gas costs, poor performance, the need for custom wallets, and more. As a result, they mostly stayed as research papers or ended up in clunky implementations. eERC not only delivers the first truly usable confidentiality protocol on EVM, but also makes it incredibly straightforward to use—so much so that you can now send encrypted meme coins with it. That’s huge. While others are still hoping institutions will adopt their custom solutions, eERC is already being used by degens on existing platforms.
yellowcatdao@yellowcatdao

BIG DAY KETTOOORS! eKET is finally here! Follow the step below if you're an orb holder to register for the upcoming eKET airdrop. If you aren't an orb holder do not worry you can test all of this out regardless. 1) Encrypted $ket is here, you can access it at ketorbs.xyz/eerc ! $eKET uses the new EERC standard by @AvaCloud. Your current balance and the amount you transfer are kept private using Zero Knowledge Proofs. Learn more at avacloud.gitbook.io/encrypted-erc/… 2) Before getting started, you'll need to take a few steps. First, generate an off-chain decryption key (can be done many times, is saved to your browser, no need to save this key) Next, do a one-time registration for $eKET (you need to submit a transaction for this). 3) Once you've done that, you will be able to deposit $ket to $eKET or withdraw from $eKET to $ket 4) If you have a balance if $eKET, either by depositing or receiving it from someone else, you can transfer it to another user. But note that the user MUST be registered in order to send to them! 5) If you're a Ket Orb holder, you'll be receiving an airdrop of $eKET as long as you complete the following steps! * Register your wallet address holding the orbs (requirement for $eKET!) * Send any amount of $eKET to any other address! It can even be your own, just help us test out the protocol. The airdrop will happen in 1 week! Make sure to register before then. 6) We're currently reviewing the EERC bounty submissions and will announce a winner soon!

English
17
28
118
25.1K
Stephen 🔺
Stephen 🔺@stephenbuttolph·
@CryptoSlowKoala @luigidemeo @0xGasless So the benefit is: Rather than having users make a new smart contract wallet, the L1 provides the ability to convert an existing EOA into a smart contract wallet. The end result isn’t really meaningfully modified, just the transition?
English
2
0
4
127
Slow Koala 🔺
Slow Koala 🔺@CryptoSlowKoala·
Any EOA acts like a smart wallet, dapps can sponsor tx fees of users and not have to worry about creating a smart wallet and then fund it be able to do that. Let’s say pharaoh integrates @0xGasless paymasters and bundler, the user could have a metamask wallet and make a swap without having Avax in the wallet. I am at avalanche summit right now, let’s talk if you are here.
Slow Koala 🔺 tweet media
English
5
8
22
665
Stephen 🔺
Stephen 🔺@stephenbuttolph·
@EvaderSpace To clarify: > It uses a new execution model where transactions are streamed to validators in real-time. No batching delays Transactions are still batched into blocks for sequencing by consensus.
English
0
0
3
59
spaced9000
spaced9000@EvaderSpace·
2/ ACP-194 is a proposal to make Avalanche’s C-Chain faster by streaming transactions asynchronously It cuts latency by processing transactions as they arrive It uses a new execution model where transactions are streamed to validators in real-time. No batching delays
English
2
0
9
251
Stephen 🔺 retweetledi
Me🔺g
Me🔺g@MeagFitzgerald·
Stealth mode deactivated❗️ 📢 Calling all devs for our next community call on 5/16 to discuss ACP-194: Streaming Asynchronous Execution ⚡️ github.com/avalanche-foun…
English
10
26
106
30.7K
Stephen 🔺
Stephen 🔺@stephenbuttolph·
@twitt_tr Im not sure I understand your expectations. It’s pretty hard to make assumptions like this on mainnet with all the different moving pieces of different validators having different mempools. (Along with potentially different block building algorithms)
English
0
0
1
82
tactical_retreat
tactical_retreat@twitt_tr·
@stephenbuttolph Sure, but that's not what happened here right? My expectation would be: *223 - mined as normal *224 - mined 1s later with some subset of the 'cheap' tx that actually got mined in *224 *225-*226 - mined with some subset of the tx in *224 *227ish - capacity refilled enough, big tx
English
1
0
1
115
Stephen 🔺
Stephen 🔺@stephenbuttolph·
@twitt_tr I mean, don’t get me wrong, higher throughput is better. But, from a system health perspective, extended bursts are not good. If you disagree, you should definitely write up an ACP to increase the ratio of R/T from ACP-176
English
0
0
0
53
tactical_retreat
tactical_retreat@twitt_tr·
@stephenbuttolph The prior mechanism 'targeted' that rate but it could still process gas at a higher rate. Yeah, the fee significantly and rapidly increased, but the blocks still got generated. You don't see any issue with limiting the gas consumption to 3m/s at busy times?
English
2
0
1
99
Stephen 🔺
Stephen 🔺@stephenbuttolph·
@twitt_tr I’m not sure, the normal block building logic can certainly skip over transactions whose GasLimit exceeds the available capacity.
English
1
0
1
101
tactical_retreat
tactical_retreat@twitt_tr·
@stephenbuttolph There's really no reason for them to have been mined so far apart, other than the capacity refilling, right? I would have expected there to be intermediate blocks mined with a lower gas usage that fill in the other transactions. Is there an unexpected delay to those tx here?
English
1
0
0
179
Stephen 🔺
Stephen 🔺@stephenbuttolph·
@twitt_tr The sliding window could result in “fee momentum.” This meant the price could continue to increase even after the spike in demand had ended. The new mechanism correctly hits the target usage and correctly moves the fee up/down based on chain demand (unlike the prior mechanism)
English
0
0
2
43
tactical_retreat
tactical_retreat@twitt_tr·
@stephenbuttolph The fees were predictable before (sliding window of gas usage), and the execution requirements were also stable (max 15M gas per block, 1 block per sec). It seems like both of those things are just different now, and harder to understand.
English
2
0
1
162
Stephen 🔺
Stephen 🔺@stephenbuttolph·
@twitt_tr Additionally, it could have runs (of blocks at the same timestamp) with large amounts of gas, causing lower powered nodes to fall behind.
English
1
0
0
60
Stephen 🔺
Stephen 🔺@stephenbuttolph·
@twitt_tr The prior mechanism targeted 1.5Mg/s. The new mechanism is dynamic (but is currently targeting 1.6Mg/s). The refill rate is currently 3.2Mg/s. The prior mechanism’s “bursty”ness resulted in significant (rapid) fee increases.
English
1
0
1
67