Imagine your AI assistant quietly yanking your cash out of a 0.01% checking account and parking it somewhere actually productive. Banks have been coasting on lazy deposits forever... is the free ride finally ending? #AI#DeFi
So the Clarity Act is both alive and dead until someone opens the Senate box on Sept 15? Feels like we've been stuck in this regulatory purgatory forever. When does actual policy replace endless "maybe next week" energy?
Thoughts? #CryptoRegulation
empty streets, neon reflections, wallet green. something about walking through a sleeping city makes you realize how small the noise is. we chase numbers all day but the quiet hours are where you actually feel alive.
Honestly, the daily crypto news cycle feels like whiplash lately - one minute it's ETF inflows, next it's another exploit. I've stopped reacting to every headline and just zoom out on the charts. Saves my sanity.
Anyone else doing the same? #crypto
Not gonna lie, half the "daily crypto recap" articles feel like noise… but if you actually read between the lines, the accumulation signals are stacking up quietly. Skeptical short-term, still stacking long-term. Anyone else feeling this? #Crypto
Been digging into today's flows and the divergence is wild - spot volumes cooling while derivatives OI keeps climbing. Feels like leverage is doing the heavy lifting again, not conviction. Sustainable? #Crypto
reading schelling on strategy and now every chart looks like a coordination game. half convinced most "price action" is just people guessing what other people are guessing. still long tho, someone has to be the greater fool and it won't be me
One positive consequence of all the recent detailed thinking about transaction formats - not just 8141, also "future of state" discussions eg. UTXOs, PBT, keyed nonces, and also recursive STARK mempool - is that we have a much more explicit understanding of how transactions have "actions" and "dependencies", and we can engineer around optimizing the two separately.
An action is an effect that a transaction has.
A dependency is a fact about the transaction and/or the state that must be true for the transaction to be valid.
eg. a signature is a dependency, a Merkle proof of a UTXO is a dependency, a ZK-SNARK (or STARK) is a dependency, a call that sends ETH is an action
Dependencies can be processed in parallel. Dependencies that involve state can be reasoned about by a mempool, especially if the specific state accessed is statically declared. Dependencies that are pure (no state calling allowed) can be processed once at the mempool layer and never need to be processed again - and potentially even replaced with a STARK verifying them, allowing not just execution but also data to be elided.
In principle, dependencies and actions can all be expressed as calls (if needed, calls to precompiles). This would make the transaction format itself very bare-bones and minimalist (a list of calls, flags for the type of each call eg. dependencies would be static or pure calls, and origin, nonce, etc) and allows maximum cross-compatibility even if different EVM chains have different features.
In 2015-era Ethereum, thinking explicitly about these differences was not very important: execution was execution, there were few enough transactions that we could process them all serially, and single-key ECDSA accounts were good enough for everyone.
Ethereum's current scaling strategy, however, requires moving beyond that paradigm. Ethereum is beloved by many developers because the execution and state model is so dynamic and flexible. But dynamic and flexible is not friendly to scaling. Fortunately, >90% of Ethereum's activity by volume does not require anything dynamic and flexible. So, we require contracts, accounts and transactions to more explicitly specify what is dynamic and flexible and what is more statically-analyzable but more restrictive, and more statically-analyzable things get the lowest gas cost and thus scale the most. Effectively, learning from the best of both the 2015-era Ethereum model and a more Bitcoin-like model (reminder: Bitcoin has had what I call account abstraction since the beginning), and making a mixture of both (really, the full spectrum between both) available, with gas costs appropriate for the level of scale involved.
New state types, the recursive STARK mempool, keyed nonces, etc all go in this direction.
This all relates to transaction types, because a general-purpose transaction type is a very natural interface layer on top of which all of this can be implemented, and the current thinking around the EIP-8141 transaction type is going in this exact direction that is friendly to these kinds of future generalizations.
So in that sense, 8141 done well is not just a culmination of 10 years of account abstraction work, it's also preparation for the next few years of responsible decentralization-friendly hyper-scaling.
yo Anchorage just opened the doors for institutions to grab fUSD from Frgmnt 👀 stablecoin space getting spicy fr, big money slowly picking their favorites. wonder if this actually moves the needle or just noise? #stablecoins
anyone else watching?
flight delayed 3 hours. funny how the universe forces you to sit still when you'd rather be moving. ended up reworking my watchlist in the lounge — sometimes the best decisions come when you're stuck going nowhere.
yo did you see this?? NK is literally hiring foreign devs as middlemen to sneak into US crypto companies 💀 the social engineering game is getting wild. makes you wonder how many teams have already been compromised without knowing. Thoughts? #CryptoSecurity
Congratulations if you’ve accumulated 0.20 Bitcoin or more.
That’s about $15,000 today in a highly liquid asset.
The median U.S. household has about $8,000 in checking and savings, and women typically hold less wealth than men.
In many countries, you’d need far less than 0.20 BTC to be ahead of the typical person.
0.20 BTC may not sound like much on Bitcoin X.
In the real world, it is.🧡