Vitalik Buterin (@VitalikButerin): live posts and tweet count

The latest @VitalikButerin posts on X as they land, with today's post count, the last 7 days and the pace against the usual daily rate.

Updated 0s ago · Free board, delayed at least 60 s

Vitalik Buterin @VitalikButerin on X

Vitalik Buterin has posted 0 times so far today, Sunday, November 22 (New York time), against a usual 0 by this hour.

Today
0
Usual by now
0
Last 7 days
7
Daily average
1.0

On usual pace

Latest posts

  1. Post

    One benefit of younger generations investing more in stonks and other digital things instead of housing is that it reduces perverse incentives that drive people to push to keep housing expensive, instead of rejoicing when prices drop as we do for all other life necessities. That said, an advantage housing has/had is that it's a culture and policy-encouraged default of investing in a safe non-crazy thing that you can't easily liquidate. Modern platforms encourage the opposite of this, leading to more irresponsible behavior. We need the equivalent of those good properties that housing investment has, for modern digital assets. https://firefly.social/post/x/2122828302121636286

    CryptoVitalik Buterin post countCaught in 100 ms

  2. Post

    Canada is going through its own version of the Chat Control mess with the C-22 bill: https://blog.mozilla.org/netpolicy/2026/10/08/canadas-bill-c-22-threatens-encryption-users-privacy-and-the-security-of-digital-economies/ Highly encourage fellow Canadians to contact senators and make clear how you feel about the importance of (backdoor-free, no asterisks) end-to-end encryption, and its benefits to a secure, free and open society. Particularly given that we're entering a difficult transition period for cybersecurity due to AI, it's even more important than before that we (i) minimize all backdoors and mass data collection, and (ii) give users very clear and legible guarantees about what kind of security they are getting, with no weasel language.

    Post image

    CryptoVitalik Buterin post countCaught in 160 ms

  3. Post

    Over the past few weeks I've gone from thinking leanPCS is total bull to being a total bull. So let me explain some of these buzzwords in more detail. At the core, 8288 is about hyper-scaling data and execution for any computation that needs to get performed on a piece of data once, the chain learns the answer, and then we never need to see that data again. This sounds very specific, but it includes most "heavy" things happening on Ethereum: * Signatures * STARKs * Merkle branches * FHE computation * ... Really the first two are the most important. Once we go quantum-safe, signatures get bigger (65 bytes ECDSA -> 1-6 kB WOTS/SPHINCS depending on params) and ZKPs get much bigger (200-1000 bytes with groth16, PLONK, etc -> 128 kB with STARKs). This is unsustainable to put on chain, and 8288 fixes this. 8288 works by aggregating STARKs in the mempool. First, you as a user generate the STARK or SPHINCS signature or PCS opening (more on that last one later), and publish it. Then, each node listens. Each tick, each node takes all of the new objects that it has seen, and generates a STARK containing a list of "claims": "pubkey P has signed message M" "program X run on data D has output Y" "p(X) = Y for some polynomial P whose hash is H" and a proof that it has seen a signature, STARK or PCS opening verifying those claims. So the only information getting re-broadcasted is: (i) hashes of inputs and outputs (~64-96 bytes per claim) (ii) a single STARK proof per tick These aggregate proofs themselves get re-aggregated, and eventually you get to a single "master proof" in the block, that verifies that all of those statements are true. And so the only other data that has to actually go on chain is the statements (the (P, M), (X, D, Y), (X, Y, H) tuples I described above), not the actual signatures or proofs. This gets put into a specialized frame type. Now, let's get into the leanSPHINCS vs leanSTARK vs leanPCS part. The core distinction is: *what is the underlying object that the user is creating?* In leanSPHINCS, it's a signature, and specifically this particular type of purely-hash-based signature: https://ethresear.ch/t/sphincs-minus-efficient-stateless-post-quantum-signature-verification-on-the-evm/25165 If we add leanSPHINCS, then users will be able to make quantum-safe accounts, and pay only a little bit of gas (4096 for the 64 bytes) for each signature. So we get scalable quantum-safety for regular accounts, multisigs, etc. But it's only one specific signature scheme, you can't do anything else. In leanSTARK, it's a STARK. This means it's fully general: the user runs whatever computation they want, and publish a STARK of it. So you can use it for: * Any signature scheme (including eg. lattice-based ones if you like those) * A multisig that hides its internal logic * Privacy protocols * Private account abstraction: authorization logic that depends on some value hidden elsewhere in the state, so you can have one key that controls all your accounts without publicly linking them to each other Basically, it's a free for all, in the same way the EVM is a free for all. But leanSTARK has a practical downside. The protocol would have to specify the language in which users write their programs (we call this the "ISA"). So we would have to agree on that language. This is a really big deal - it's the first big case of "Ethereum moving beyond the EVM" - and so it's likely to take time to agree on the details of it, especially since the ISA would be hard to upgrade. There are benefits to taking longer on this, figuring out the ideal ISA, and then even giving access to it inside regular contracts. LeanPCS is the third option. PCS stands for "polynomial commitment scheme": a proof that P(x) = y. The most important thing to know about PCSes is that they are by far the most important "hard" component of a STARK (see here: https://vitalik.eth.limo/general/2021/01/26/snarks.html ). If you have a "magic PCS oracle" (which from the EVM's point of view, 8288 is), you can verify a STARK in ~20-40k gas. The most important gain with PCS is that there is far less that we need to choose. Specifying a PCS only requires specifying a field, and there is a natural option: the 128 bit binary field (technically, we can go more general than that, and say the 2^k-bit binary recursive tower field, going up to 256) LeanPCS is less efficient than leanSTARK onchain, because you would have to put multiple claims to prove one thing. But it's arguably more efficient offchain, because you have much more flexibility to choose proof systems. But most importantly, leanPCS gives you the same generality as leanSTARK, in a way that could potentially be implemented very quickly. And once we figure out the ISA, we can add leanSTARK later. So there is a route to getting "the cryptographic proof singularity" much faster than any of us expected, and that route runs through 8288 with leanPCS. https://firefly.social/post/x/2120922104002486765

    Post image

    CryptoVitalik Buterin post countCaught in 166 ms

  4. CryptoVitalik Buterin post countCaught in 202 ms

  5. CryptoVitalik Buterin post countCaught in 279 ms

  6. Repost
    vitalik.eth reposted

    This is culturally so important to realize: eth as sov is the ambitious and inspiring path for Ethereum too. Ethereum as a civilizational root of trust is infinitely more exciting and valuable to the world than the myopic path of optimizing for revenue today, running it like a business, and in the process driving away everything that makes Ethereum special in the first place. Bitcoin has the credible neutrality and security but not the architecture to become a root of trust beyond itself. It will be Ethereum or no one. We mustn’t forget the scale of our target. Be ambitious.

    Replying to @0xNairolf

    @0xNairolf The beauty of ETH as store of value is that it’s not giving up on Ethereum the technology. It won’t be a “boring ledger”. In fact ETH is special because Ethereum is special. It is Ethereum that is credibly neutral, secure, and architecturally set up to be the root of…

    CryptoVitalik Buterin post countCaught in 162 ms

About this tracker

This page follows Vitalik Buterin (@VitalikButerin) on X, one of the accounts on TweetStream's live board of posts that move markets, in its Crypto group. New posts are listed newest first with their catch speed: the time from the post's own timestamp to TweetStream's first receipt. TweetStream catches X posts in typically 166 ms.

The count includes what shows on the account's main feed: main posts, quote posts, reposts, and replies that continue its own thread. Other replies are left out. Polymarket's weekly post-count rules describe the same kinds of post, but this is not their settlement figure: each market settles on the tracker its rules name. "Today" runs from midnight New York time. "Usual by now" is the average over the previous 7 days, scaled to the share of today that has passed, and the pace label says whether today is above or below it. A post deleted after TweetStream caught it stays in the count. Posts appear here at least 60 seconds after TweetStream receives them.

More in Crypto: Michael Saylor, Brian Armstrong, Coinbase, Binance, Watcher.Guru.

Questions

How many times has Vitalik Buterin posted today?
The Today figure at the top counts @VitalikButerin's posts on X since midnight New York time, next to the usual count by this hour and the last 7 days. It refreshes every 10 seconds.
How often does Vitalik Buterin post?
The Daily average at the top is @VitalikButerin's average posts per day over the 7 days before today, and the bars show each of those days.
Do replies count?
Only the replies that show on the account's main feed: a reply to its own post that continues its thread. Replies to other accounts, and its replies inside someone else's conversation, are left out. Polymarket's weekly tweet-count rules also count replies that show on the main feed, though each market settles on its own tracker's figure.
Which time zone does the count use?
New York time. Today runs from midnight to midnight Eastern. For the accounts with weekly tweet-count markets, the count rounds start at 12:00 PM Eastern on Tuesdays and Fridays.

Get these alerts in your bot or Discord, 3-day free trial

Pick your own accounts and get each post in your bot over WebSocket or in your Discord server without this board's 60-second delay. TweetStream catches X posts in typically 166 ms.