Chief Strategy Officer @Anza_xyz. Prev GC @solanalabs, @joinrepublic
Venice
Joined January 2007
- Tweets200
- Following995
- Followers2.5K
- Likes1.6K
Jed retweeted
1/ It’s a new year and a new Anza.
I’ve stepped into the CEO role at the start of what is sure to be an exhilarating 2026.
Let’s look at what Anza is cooking
Amazing work by @Austin_Federa @MariTomunen and the @doublezero team getting out what we (should) have known for some time! Happy @anza_xyz is playing a (small) role as a contributor to the network
Today is a monumental day for crypto in America.
The @SECGov Division of Corporation Finance confirmed that the DoubleZero Networks’ native token (2Z) flows to contributors of the network are not subject to the registration requirements under the Securities Acts, and has issued a No-Action Letter for DoubleZero’s 2Z token.
This No-Action Letter adds further weight to the understanding many of us have always believed: tokens are not inherently securities.
Treasury Sale terms have gone full circle back to the @Consensys Token Foundry days. Look just like Foam and Civil token sale terms
Nobody "chose" memecoins to become highest rev for the network, and so you can't "choose" low-risk defi as a fee savior. It already kind of exists, and is not being used for a reason
Low-risk defi can be for Ethereum what search was for Google
vitalik.eth.limo/general/202…
Jed retweeted
Agave v2.3 is almost here. Here are the most important updates so you can monitor the situation:
- Faster epoch transitions
- AccountsDB optimizations to reduce I/O overhead
- Greedy scheduler enabled by default
- RPC API updates to simulate data usage
- New TPU client
Jed retweeted
The v2.3 schedule is up. Here's a 9 week notice for when to upgrade 😉
github.com/anza-xyz/agave/wi…
Jed retweeted
As someone who’s been in the crypto industry since 2013, one of the simplest yet most challenging questions I’ve faced is how to think about noncustodial trading interfaces. Do operators or developers of these NTIs have any regulatory obligations? Ideally not.
I’m thrilled to finally have an opportunity to voice my opinion on the question in an effort to make a real change and provide a long-awaited answer. Today, I’ve submitted written comments to @SECGov’s crypto task force in an effort to make clear that NTIs—and folks developing or operating them—have no obligations under the securities laws to register as a broker or an exchange. NTIs serve simply as informational tools and technology layers that make communicating with blockchain systems easier.
@HesterPeirce looking forward to hearing your thoughts!
sec.gov/files/ctf-written-in…
Jed retweeted
Read our latest Root Cause Analysis blog post by @apfitzge and @cavemanloverboy
anza.xyz/blog/precompile-ali…
Jed retweeted
We are hiring!
• Developer Relations Lead 🌍
• Rust Engineer (Zürich-based) 🇨🇭
• Sr. DevOps Engineer (EU-based) 🇪🇺
• Sr. Smart Contract Engineer 🌎
Come build the future with us: anza.xyz/careers
Not everything is politics!
There seems to be a lot of confusion about what is going on with SIMD 96 rollout so let me clarify a few things. First SIMD 96 "Reward full priority fee to validators" feature flag will be activated when the supermajority of the network (>67%) is updated to 2.1 for 2+ epoch boundaries. (On occasion there may be slight additional delays if RPCs have trouble upgrading but no concerns on this front for 96 have so far been raised.)
The feature flag is part of Agave 2.0 as listed on the schedule, not 2.1. The only reason we have not pushed this feature flag is because of security best practices. @anza_xyz core devs do not push feature flags while the network is in the process of upgrading to the new version.
We also try to roll out features one at a time to make debugging new features easier. In this case there were many scheduled features in Agave 2.0. It was a big release! Since we only roll out one feature gate per epoch, there wasn’t enough time between 2.0 and 2.1 to make it through all of the activations. 96 isn't the only 2.0 gated activation that isn't out yet. There are 5 others also waiting.
We have a diversity of opinions within Anza, I happen to be supportive of 96, but those opinions are irrelevant to the feature release schedule. Our goal with the release schedule is to safely roll out changes to the network as fast as we can and these were the only considerations at play here.
