uh

Someone build decentralized Kaito with TLSNotary

Someone make Among Us using MPC

Prop AMM (?) looks awfully suited for Intmax/Plasma Fold architecture

@VitalikButerin Do you support 6s slot time in Hegota? do you worry that it might render real time proving impossible?

Increasing bandwidth is safer than reducing latency With PeerDAS and ZKPs, we know how to scale, and potentially we can scale thousands of times compared to the status quo. The numbers become far more favorable than before (eg. see analysis here, pre and post-sharding vitalik.eth.limo/general/2021/0… ). There is no law of physics that prevents combining extreme scale with decentralization. Reducing latency is not like this. We are fundamentally constrained by speed of light, and on top of that we are also constrained by: * Need to support nodes (especially attesters) in rural environments, worldwide, and in home or commercial environments outside of data centers. * Need to support censorship-resistance and anonymity for nodes (especially proposers and attesters). * The fact that running a node in a non-super-concentrated location must be not only possible, but also economically viable. If staking outside NYC drops your revenues by 10%, over time more and more people will stake in NYC. Ethereum itself must pass the walkaway test, and so we cannot build a blockchain that depends on constant social re-juggling to ensure decentralization. Economics cannot handle the entire load, but it must handle most. Now, we can decrease latency quite a bit from the present-day situation without making tradeoffs. In particular: * P2P improvements (esp erasure coding) can decrease message propagation times without requiring individual nodes to have lower bandwidth * An available chain with a smaller node count per slot (eg. 512 instead of 30,000) can remove the need for an aggregation step, allowing the entire hot path to happen in one subnet This plausibly buys us 3-6x. Hence, I think moderate latency decreases, to a 2-4s level, are very much in the realm of possibility. But Ethereum is NOT the world video game server, it is the world heartbeat. If you need to build applications that are faster than the heartbeat, they will need to have offchain components. This is a big part of why L2s will continue to have a role even in a greatly scaled Ethereum (there are other reasons too, around VM customization, and around applications that need _even more scale_). Ultimately, AI will necessitate applications that go faster than the heartbeat no matter what we do. If an AI can think 1000x faster than humans, then to the AI, the "subjective speed of light" is only 300 km/s. Hence, it can talk near-instantly within the scope of a city, but not further. As a result, there will inevitably be AI-focused applications that will need "city chains", potentially even chains localized to a single building. These will have to be L2s. And on the flipside, it would be too much of a cost to make it viable to run a staking node on Mars. Even Bitcoin does not strive for this. Ultimately, Ethereum belongs to Terra, and its L2s will serve both hyper-localized needs in its cities, and hyper-scaled needs planet-wide, and users on other worlds. Milady.

right now GNOME has better UI design than macOS

i don't know why people simp for Steam and Gabe. It's literally unnecessary evil middle man

@shemnon I was thinking in post-OrbitSSF setting where only 8192 validators are active at a slot. idk the state of SSF research... I agree that it's not feasible in current Ethereum!

@pnyda333 When did we go down to 10k validators? Eth just barely went below 980k. We need to budget for half of all eth being staked at the minimum possible stake,

10 UOV signatures fit in a single IP packet so to handle 10000 validators the leader just has to receive 1000 IP packets in a slot

@shemnon if we want to allow raspberry pi to be a validator sure pk size becomes a problem but modern laptops have plenty of RAM anyway. 300KB expanded pk * 10000 validators = 3GB RAM requirement feels... not a big deal?

@pnyda333 But that's tens of gigabytes of just public key data you need to keep handy to validate signatures. And by handy I really me in memory.

@shemnon validators already have 4TB SSD anyway. I don't think it's that unreasonable to require people to upload a 66KB public key to start staking

@pnyda333 But those public keys ...

In my understanding Passkey is secure only when iCloud password is super long and sampled from uniformly random distribution. I wanna know how many people does that

I wanna hear a retrospective talk from Irreducible team such as (1) Was FPGA clock speed too slow (2) Why was Cysic able to fund their ASIC development and Irreducible couldn't (3) Is binary field misfit for GPU proving era since PTX doesn't have something like GFNI

stablecoin is not crypto

is ethnonationalism plurality

so paradigm and ream labs are both building lean consensus client in Rust...!

Since Gemini 3 came out I'm addicted to studying math like this is better than Halo 3

Implement RLNC in XDP

It bothers me that Rustaceans are fine with using trait object for error handling even though (1) it's totally avoidable (2) weren't you guys fawning over "zero-cost abstraction"

Seriously I can't love jj enough

arkworks don't have small fields and plonky3 doesn't have struct for polynomials in coefficients form