Revm author and maintainer. Part of @tempo. Personal views only
Joined June 2011
- Tweets777
- Following1.2K
- Followers3K
- Likes9.3K
This is going to be big
Introducing Open USD: a stablecoin built for the internet economy, designed by the businesses growing it.
joinopenstandard.com/blog/in…
Wild idea, EF (or EF v2) should have only one purpose: to distribute funds for protocol work.
It should be funded from the base fee (which is now burned), and it should publicly request a budget for all r&d projects, chain and client maintenance.
This incentivises EF to think about the Eth price (as its main funding) and the usage of the chain (no tx, no base fee).
Dragan Rakita retweeted
Enterprises are bringing stablecoin payment flows into production on Tempo, including @DoorDash, @stripe, @CoastalBankWA, and @arq_finance.
We're also launching our Stablecoin Advisory to help more enterprises build real-world payments workloads on stablecoins.
This will have a profound effect on humanity as a whole. How we consume and see responses from our actions/inputs will shape us emotionally and psychologically, and with increased usage, this will become a more dominant way of interaction.
It is scary that one or a few major models will shape us this way, but I do think it is net positive as it becomes a baseline for interactions.
It looks like we are going to use post quantum sigs a lot sooner than expected. fun times
Many are wondering "what Google saw" that caused them to revise their post-quantum cryptography transition deadline to 2029 last week. It was this:
research.google/blog/safegua…
GitHub kinda sucks for doing reviews on bigger diffs, it just fails to load things, and it is slow.
Not even talking about UX, and using only comments as a tool, is not enough anymore.
And with AI coded PRs, this is going to be unbearable.
Dragan Rakita retweeted
I just tried wallet.tempo.xyz/, made a wallet and I will probably build some stuff over the weekend. However, the login experience made me reflect on some things:
1. Account abstraction is actually as easy as the Paradigm bros were telling us.
2. Ethereum needs this ASAP. we can't wait for a bunch of wallets to slowly integrate this. strongly starting to believe that this needs to happen fast and waiting is increasingly a mistake.
Who else hates that this is 38 pages? (It should have been three)🙋♂️
EF is choosing an identity for Ethereum, high praise for this, it was finally time. It was their responsibility and I hope that this continues. It is just a start.
CROPS is awesome, and imo should be the main point of the paper.
Ethereum product market fit is unique from both technical and social standpoints. Scale of validators and consensus that supports this, focus on censorship resistance and big future focus on privacy, gives a good idea of what the guiding principles of the protocol are. And how it would behave in 10 years. There are drawbacks to this path, as in any path. Is it a mistake? Would it crash and burn or become the golden standard, time will tell, I sure don't know.
Love the World Computer analogy, hate infinity garden and next thousand year thing (wtf was that)
And EF deprecating itself feels like a noble thing wrapped as an exit strategy. There should be an entity whose only incentive is to propagate the values of Ethereum (Not centralizing things, for example). If EF is not there, some alternative "Foundation"/s will fill its place. It will be chaotic, and I don't see it happening. I think it is naive to think otherwise. Maybe I am mistaken.
Dragan Rakita retweeted
Software engineering changed more in the last 3 months than the preceeding 30 years.
Everything about running a software company needs to be rethought from first principles.
Testnet lives!
Tempo’s testnet is live!
Any company can now build on a payments-first chain designed for instant settlement, predictable fees, and a stablecoin-native experience.
Tempo has been shaped with a wide group of partners validating real workloads including @AnthropicAI, @Coupang, @DeutscheBank, @DoorDash, @Lead_Bank, @mercury, @nubank, @OpenAI, @Revolut, @Shopify, @StanChart, and @Visa.
Since our announcement, @brexHQ, @Coastal, @crossriverbank, @deel, @faire_wholesale, @Figure, @GustoHQ , @Kalshi, @Klarna, @Mastercard, @Payoneer, @withpersona, @tryramp, and @UBS have also joined as design partners.
Dedicated payment lanes, stablecoin gas, deterministic finality, a built-in stable asset DEX, and programmable smart accounts are all live on testnet.
If you’re building or modernizing payment flows, you can start integrating and testing today.
This is a big one! Imagine the current 60M gas block with faster block time, it would double the throughput and make any gas limit changes twice as effective.
6-second slots are fully spec’d, prototyped in Geth and Prysm, and ready to ship next year.
Easily one of the most impactful upgrades we can deliver in the Heka/Bogotá fork.
h/t @jih2nn and @MorphNetrunner for getting a first local devnet running.
Would group gas changes in:
* State growth (bump by n times): All opcodes that increase state (or/and history). Or introduce a hard limit mechanism to it.
* zkVM (bump by a factor): All stuff expensive to zk (precompiles). EVM and zkVM gas need to cover the worst case scenario of both.
* Levelling: price all things better, so the block is more compact.
* Multidim gas/state expire: but they are a new mechanism to use resources.
Expect continued growth but more targeted / less uniform growth for next year.
eg. one possible future is: 5x gas limit increase together with 5x gas cost increase for operations that are relatively inefficient to process
Potential targets for such increases (my current view):
* SSTORE when creating new storage
* SSTORE in general (slightly)
* Precompiles (all except elliptic curve stuff)
* CALLs to contracts with large contract size
* Some complex arithmetic opcodes (MODMUL maybe?)
* Calldata (slightly)
Running Ethereum should be as easy as
`brew install eth`
`eth run`
Expanding on this idea, in a blog post 👇
If you want to see what is happening in Serbia, please watch this. It is one of the better explanations of the situation.
This was one of the biggest gatherings in Serbian history, with ~150k people out on the streets. The second only to the 15 March protest of this year. People marched for days over 400km to come to Novi Sad. And corrupted buses and railroads stopped transporting people on this day, and yet this didn't matter.
Our corrupted President, who is calling students fascists and terrorists, said two days before about this day, "And what about Saturday, is there a game or what?". What else can I say, disgraceful and shameful!
1. 11. will be remembered in Serbian history.
Tens of thousands of people have gathered in Novi Sad, Serbia, to commemorate the victims of last year's railway station disaster, which killed 16 people and sparked nationwide protests.
Sky's @AliBunkallSKY reports.
🔗 trib.al/UuabG40
text is from: forkcast.org/calls/acdc/168/
Based on the ACDC (All Core Developers Consensus) call #168 transcript, here are the key decisions made:
Major Decisions:
1. Fusaka Mainnet Dates - CONFIRMED
Mainnet releases: November 3rd (Monday)
Mainnet fork: December 3rd
BPO1 on Mainnet: December 9th
BPO2: January 7th, 2025
Despite Prysm reporting a peering bug on Hoodie (where Prysm nodes were kicking out non-Prysm peers after a few hours), the decision was made to proceed with these dates. Prysm indicated they likely wouldn't release on Monday but would work on fixes.
2. Glamsterdam Fork Scoping Process
Client teams to provide written proposals with their views on CL-side EIPs by November 13th (next ACDC, two weeks from the call)
EIPs would be moved to CFI (Consider for Inclusion) status, not directly to SFI
ePBS remains SFI as the headliner
3. H-star Fork Named "Heka"
The next fork after Glamsterdam will be called "Heka" (winning the informal poll)
Potential portmanteaus with EL's Bogota fork: Hecta, Hogota, Hekota, Bogeka
EIPs Discussed for Glamsterdam (No Final Decisions):
The following CL-side EIPs were presented for consideration:
EIP-7688: SSZ stable containers
EIP-8045: Exclude slashed validators from proposer shuffling (one-line change)
EIP-8061: Increase churn limits (4x for exits/activations, 2x for consolidations)
EIP-8062: Add fee (0.25%) to sweep withdrawals
EIP-8068: Neutral effective balance design for consolidations
EIP-8056: Prevent consolidations as withdrawals
EIP-7805 (FOCIL): Remains CFI'd, decision pending
Additional Important Points:
PeerDAS cell-level deltas: Planned for deployment before Glamsterdam (ex-fork) to enable blob scaling
Proposed BPO schedule extending to 72 blobs max through gradual increases
Emphasis on maintaining fork discipline and not overloading Glamsterdam scope given the networking improvements also planned
The call established a clear timeline for decision-making on Glamsterdam scope while confirming the Fusaka mainnet schedule despite the discovered bugs.
