Bullshit!!!!
Are we earn $100+really ?
Everyone promoting meaningless truth, We know its Paid promo
We can make this type of money printing SS Easyy with AI, 🤐
Its way to loss 3$ to 5$ ( small but what if 100k users try this )
#Truth
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.
I am spotted Another Reasonable worth look project
Follow @ashenthronegame
• Post-apocalyptic 4X Strategy MMO
• Play directly in your browser, Android, or iOS
❌ No installation required
❌ No invite code required
❌ No wallet required to start playing
❌ No token farming system
💰 Real USDC cash tournaments on Base
✅ A genuine strategy game where skill matters more than grinding
New players 🫵
• Crawler – A mobile fortress that moves across the world map
•Extraction raids – Collect unbanked loot while defending it from other players
• 24/7 Citadel siege battles across four districts
And Participate Alliance Cup Event (August 21–30)
• Prize pool: $1,000 USDC
• Network: Base
• Participate in just one siege battle or hold a wall for one hour
• Become eligible for tournament rewards
• 30% of the winning alliance's prize pool is shared equally among all eligible members
✅ Proven payouts
-> 27 players received $95.86 USDC
-> Rewards were distributed on July 24–25
-> All transactions were published with on-chain verification
Bonus for new players
• Use code: ASHEN-THRONE (Get 500 ASH token worth $5 value)
Play 👇
https://t.co/j5Dx2KuHrP
> لم تنشر DexScreener أي تغريدة منذ 9 أشهر.
ومع ذلك، لديهم أكثر من 10 ملايين مستخدم شهريًا، ولا يواجهون أي منافسة حقيقية، ويسيطرون بالكامل على ساحة التداول.
وحققوا أكثر من 100 مليون دولار العام الماضي.
لا تحديثات، ولا منشورات "GM"، ولا ضجيج.
مجرد منتج ممتاز يستخدمه الجميع.
وهناك درس يستحق التأمل في ذلك.
#Crypto
🌙 What a room at Build N Build Night!
On the sidelines of SBC, YZi Labs & @BNBChain brought researchers, founders, and investors under one roof to explore how technical breakthroughs become products, companies, and new markets.
Thank you to everyone who joined us in Palo Alto. We can’t wait to do it again!
🤝 @BNBChain@CBRStanford@initc3org@theBBFund@StanfordSBA
@Spores_Network@MSTBlockchain Just complete the Gleam tasks before July 9 & grab your chance!
If you’re watching the upcoming #SporesNode_Sale, this is a simple way to join early + earn rewards 🔥
Click 👇
https://t.co/VPUEF7CvAP
Don't miss this opportunity 🤝
This year, the EF is decreasing its budget by roughly 40%, which entails some difficult decisions. The goal of the decreases was set out in the Treasury Management Policy last year: the EF is transitioning into being a long-term-oriented endowment-based organization, shifting from its pre-2026 average of spending ~15% of its remaining funds each year, toward a post-2030 target of ~5% per year.
Often, when an organization goes through something like this, people try to pretend that nothing of great value was lost, that it is an efficiency increase, that the only people cut are unproductive dead weight, and everyone else stopped partying, studied the blade, entered cracked S-tier beast mode, and this was sufficient to make up for the downside. I will not try to pretend this. I respect my EF colleagues far too much to pretend that there was not much that is lost. They are brilliant people. They are dedicated engineers of whom some have worked on the Ethereum protocol for nearly a decade. They have brought a bright light to the Ethereum ecosystem with their code, their words, their warmth as human beings and their actions. My dearest hope is that they find a path that brings them fulfillment and happiness whether inside Ethereum or outside. Hopefully many will be able to bring their excellent talents and mindset to the wider Ethereum ecosystem, or the even wider CROPS world.
Instead, I will try to explain what *are* some of the grand sacrifices being made. The Ethereum Strawmap is no small thing. It is an extremely ambitious undertaking seeking to replace and augment almost every part of the protocol - consensus, proofs, privacy, account model, state, and more. This is the third iteration of Ethereum, in the same way that the Merge was the second, even if the shipping style is less Big Bang and more one-piece-at-a-time. On top of this, the EF is increasing its role in the Access Layer. We are not compromising on Ethereum being a Deeply Impressive protocol, something worthy of its place in a world with quantum computing, rockets to Mars and powerful biotech and AI, and capable of meeting the challenges that this era will bring.
Some of the deficit will be recovered through more work happening outside the EF. But not all. So what are the grand sacrifices that will enable a leaner effort to accomplish all of this? I will give a few examples (though far from an exhaustive list):
* The multi-client model will shift in the direction of multiple clients existing less for _redundancy_, and more for _specialization_. Up to this point, redundancy has been the main security strategy: if one client has a bug, if it has less than 33%, the chain keeps going and does not even stop finalizing. We are increasingly exploring moving more pieces of the protocol to a different security strategy: AI-assisted formal verification. Some smaller pieces of Ethereum (eg. BLS libraries) have worked this way already for a long time. But soon many more parts of Ethereum will likely function on this model. This may greatly reduce resource requirements of shipping a large number of EIPs. The resources saved by client teams can ideally instead be used to better serve different specialized user needs, including EF Access Layer goals.
* PSE (Privacy and Scaling Explorations) is winding down as a unit. The number of people working on ZKPs for privacy and scaling is probably as high as ever, but they are working less on "exploration" and more on *implementing* ZKP-based privacy and scaling into the Protocol and Access Layer
* Devcon will likely over time become smaller-scale, somewhat more spartan, much lower-deficit than previous years, in addition to other changes in vision in line with the Mandate.
* Fewer beyond-Ethereum megaprojects coming from EF. As I announced earlier this year, I am taking on some of the responsibility of doing projects in this category that I consider valuable with my personal funds.
* EF institutional work is reducing in scope, specializing more specifically on creating replicable test cases of highly CROPS-friendly deployments, even if at smaller scale.
These do not explain all departures; in some cases they do not explain departures at all and rather explain _reduced need for new spending_. But they are a large part of the strategy at play.
In the longer term, I personally favor a "soft lean-and-done" approach to Ethereum: once the Strawmap is completed, generally stick to security fixes and small high-value changes, and have a much higher bar for considering new feature additions to the protocol. This allows Ethereum to remain capture-resistant without demanding very large budgets. Learn less from multimillion-line-of-code behemoth projects, more from bitcoin.
The past years have been a challenging era for Ethereum. However, the ecosystem is adapting, both inside the EF and outside, and I am confident that Ethereum is very well-positioned to succeed and thrive.
https://t.co/iZiOonRYzR