
vitalik.eth (@VitalikButerin) X analytics
@VitalikButerin
I choose balance. First-level balance. mi pinxe lo crino tcati https://t.co/gCQrmCby7P
@VitalikButerin has 7.9M followers, a median of 393.9K views per post and a 0.60% engagement rate.
Based on 30 recent original posts (high confidence). Updated November 19, 2026.
At a glance
Key stats
- Followers
- 7.9M7,905,923 followers on November 19, 2026−18.8K in 7 days−79.4K in 30 days
- Median views per post
- 393.9K
- Average views per post
- 630.6K
- Engagement rate (by views)
- 0.60%
- Original posts per week
- 3.5
- Average engagements per post
- 3,761
Engagement grade
Developing
This is near the lower benchmark range for accounts with 1M+ followers.
Profile score
78/100
- Profile completeness85
- Audience shape100
- Engagement25
- Consistency100
- Positioning clarity79
Monetization
Estimated X creator earnings
$601–$1,503 in the last 30 days
From 6M views on @VitalikButerin's original posts in the last 30 days.
Rewards eligibility: likely
Rough estimate. X publishes no payout rate, so this assumes about $100–250 per 1M original-post impressions, based on real creator payouts. Payouts vary with how many of your viewers have Premium.
Free report
How does your account compare with @VitalikButerin?
Get the same report for your own account by email: engagement grade, median views, best times to post and estimated earnings.
Growth
Follower growth
−18.8K followers in the last 7 days. −79.4K in the last 30 days. Tracked by Xholic since October 4, 2026.
| Date | Followers | Change |
|---|---|---|
| Nov 19, 2026 | 7,905,923 | −5,748 |
| Nov 18, 2026 | 7,911,671 | −1,540 |
| Nov 17, 2026 | 7,913,211 | −1,362 |
| Nov 16, 2026 | 7,914,573 | −3,093 |
| Nov 13, 2026 | 7,917,666 | −7,079 |
| Nov 10, 2026 | 7,924,745 | −108 |
| Nov 9, 2026 | 7,924,853 | −5,251 |
Timing
Best times to post
When @VitalikButerin's recent posts performed best (UTC).
- #1 slot
8:07 PM
Monday · UTC
- #2 slot
7:18 PM
Tuesday · UTC
- #3 slot
7:23 PM
Wednesday · UTC
What worked
Top recent posts
- 01

@VitalikButerin ·
I don't recommend anyone scramble to move their funds to new wallets today. But we should take the risks to cryptography from AI-accelerated math seriously, and minimize our exposure to not just quantum-vulnerable cryptography, but also potentially AI-vulnerable cryptography. The core new area of risk from this viewpoint is, unfortunately, ML-DSA / FHE / lattices. (and it's also another reason, along with quantum, why ECDSA might fall even faster than expected, hence the "fresh address" recommendation) So far most people have been in the mode of thinking "elliptic curves broken, hashes safe, lattices safe". But there is a good chance that the concrete security of lattices will take serious hits from the next two years of AI math. The basic threat model is: factoring is something that naively takes 2^(n/2) time, but over decades smart people have found and optimized number field sieves, and degraded that to 2^O(n^(1/3)), which is why RSA keys and signatures need to be ~400 bytes (and not 64 bytes). What if there are skeletons in the closet like that, both for elliptic curves and lattices, that we are simply not smart enough to discover - but bots soon will be? This is a major part of the reason why for the past year ethereum's lean roadmap has been going in the "hash-only" direction: no lattices, no ML-DSA, no Falcon, no lattice-based commitments inside ZK proofs, etc. Signatures in lean ethereum are all hash-based, either WOTS or SPHINCS-. For signatures and proofs, we already know how to go hash-only. The bigger challenge is for *public-key encryption* - and this goes far beyond blockchains. Secure communication, anonymizing protocols, lots of things need public-key encryption. And unfortunately there are long-standing mathematical theorems showing why public-key encryption cannot be done with hashes alone. You have to have some kind of trapdoor object that has at least one form of usable "structure" - either group theory (incl. isogenies) or lattices or code-based or potentially in the future even more newfangled and spooky things (local mixing?). But for anything that has structure, you should assume that AI will make at least some progress in breaking that structure. Here, one reasonable inference is that if you want to make something plausibly long-term secure, multiply the key sizes by 10. To me that's a very plausible world and something not at all extreme to predict. If AI will bring us 50 years of math in 2 years, then that 50 years of math may very plausibly include a "naive factoring -> GNFS" level of improvement to our ability to break lattices. In that world, lattices will still exist, but they will have to be significantly bigger to guarantee the same level of safety. And at those new larger sizes, hash-based constructions will beat lattice-based constructions on concrete efficiency in every use case where hash-based constructions are possible at all. Theoretically, of course it's possible that hashes are broken too (eg. P = NP would imply that). But I think P = NP is very unlikely. And intuitively, it's much more likely that a mathematical object has exactly no exploitable structure (like hashes are intended to), than that a mathematical object has exactly ~3 forms of exploitable structure (for elliptic curves: associativity, Schoof, pairings) and not some secret fourth form of structure we have not yet discovered that greatly degrades its security (for elliptic curves, ECDLP and pairing security). Similar for LWE, SVP, RLWE and the zoo of lattice problems. For this reason, we do not yet see any reason to worry and start padding the byte size of hashes (if we start to worry more, we would pad the round count first before doing anything to the byte size). Concrete TLDR, my own personal views: * Hash-based > lattice-based, in those situations where hash-based is possible at all * For anything lattice-based, be much more paranoid on param sizes. Remember that blockchains are only a small portion of the cryptography story; this point goes far beyond blockchains and applies to eg. access to websites, secure messaging, Tor / VPNs ... * For privacy protocols, strongly favor NOT putting encrypted notes onchain. Instead, send them offchain through some third-party mechanism. * If it's not difficult for you, keeping your funds in addresses which have not yet been used to make a transaction is a good idea. If it's easy for you, do it. **But be careful about migrations; I personally have lost more money in botched migrations than I have lost in all hacks combined**. * For multisig wallets, doing confirmations offchain is better than onchain, because this way the signatures of signer wallets do not get exposed to the public, so if ECDSA falls to AI much faster than expected, at least the multisig "gracefully degrades" to a 1-of-1 where the 1 is whoever was gathering the signatures - a much better place to be than "anyone can take the money" https://t.co/oVjwZog2lL
- 1.2KReplies
- 1.9KReposts
- 11.2KLikes
- 4MViews
5.8x average engagementShares a linkLong post (over 200 characters)Posted Wed 23:00 UTC - 02

@VitalikButerin ·
Expanding on why I believe "ETH as store of value (SoV)" makes much more sense to focus on than "ETH as fee-burning token". Three primary reasons: 1. ETH as fee-burning token never was as strong as it seemed 2. Optimizing for ETH as fee-burning token would demand Ethereum and ETH function in ways that are very hard to make compatible with decentralization and capture resistance. 3. Meanwhile, optimizing for ETH as SoV is aligned with Ethereum focusing on its unique strengths (decentralization and CROPS) EIP-1559 (including its burn) is fine and good, we should keep them. But we should not feel sad if fee burn is < 10% of breakeven indefinitely; the value of ETH comes from elsewhere. The core idea: the big thing that people appreciate about Ethereum is decentralization and CROPS. The main pragmatic benefit that these things translate into is stability. SoV is the category where that is not an unneeded extra we merely put effort into for ideological reasons, but rather a pragmatic strength from the perspective of people putting in their assets. And in the era of AI disruption, stability will be highly valued.
- 1KReplies
- 1.2KReposts
- 6.9KLikes
- 2.1MViews
2.7x average engagementText onlyLong post (over 200 characters)Posted Sun 12:00 UTC - 03

@VitalikButerin ·
The cryptographic world computer: https://t.co/LF2JGU38Rx My attempt to express in somewhat concise terms the true meaning of basically everything planned to happen to Ethereum starting from the fork after Hegota. It's really not just a blockchain anymore. It's a hybrid architecture that combines together blockchains and modern cryptography, to enable much more powerful properties. FOCIL, EIP-8288, Lean consensus, state management, formal verification, advanced mempool improvements (including privacy), and the longer-term specter of obfuscation all mentioned.
- 588Replies
- 1KReposts
- 5.7KLikes
- 1.5MViews
2.6x average engagementShares a linkLong post (over 200 characters)Posted Sun 10:00 UTC - 04

@VitalikButerin ·
Digital minimalism https://t.co/UF9M3Kx1fm
- 579Replies
- 512Reposts
- 4.4KLikes
- 1.1MViews
2.6x average engagementShares a linkShort post (under 100 characters)Posted Sat 03:00 UTC - 05

@VitalikButerin ·
Just arrived in Mumbai! Looking forward to seeing familiar faces and new faces and all the wonderful Ethereum and open/secure/private/decentralized tech projects that everyone is working on over the next week.
- 820Replies
- 379Reposts
- 6.3KLikes
- 543.7KViews
1.2x average engagementText onlyLong post (over 200 characters)Posted Sat 19:00 UTC - 06

@VitalikButerin ·
Also this thing is done now https://t.co/1VFk2f0fZx
- 635Replies
- 292Reposts
- 3.2KLikes
- 907.7KViews
1.2x average engagementShares a linkShort post (under 100 characters)Posted Sun 14:00 UTC
Latest
Recent posts by vitalik.eth
The latest 30 original posts from @VitalikButerin, newest first, as of November 19, 2026. Replies and reposts aren't included.

@VitalikButerin ·
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://t.co/4uV8Q1rGuN
- 281Replies
- 116Reposts
- 1.1KLikes
- 192.5KViews

@VitalikButerin ·
Canada is going through its own version of the Chat Control mess with the C-22 bill: https://t.co/BTXwaRJ3Ws 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.
- 185Replies
- 262Reposts
- 1.4KLikes
- 170.6KViews

@VitalikButerin ·
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…
- 290Replies
- 195Reposts
- 1.5KLikes
- 266KViews

@VitalikButerin ·
My views on EIP-8037: https://t.co/WUeR5lxJiC


- 163Replies
- 95Reposts
- 932Likes
- 266.9KViews

@VitalikButerin ·
Expanding on why I believe "ETH as store of value (SoV)" makes much more sense to focus on than "ETH as fee-burning token". Three primary reasons: 1. ETH as fee-burning token never was as strong as it seemed 2. Optimizing for ETH as fee-burning token would demand Ethereum and ETH function in ways that are very hard to make compatible with decentralization and capture resistance. 3. Meanwhile, optimizing for ETH as SoV is aligned with Ethereum focusing on its unique strengths (decentralization and CROPS) EIP-1559 (including its burn) is fine and good, we should keep them. But we should not feel sad if fee burn is < 10% of breakeven indefinitely; the value of ETH comes from elsewhere. The core idea: the big thing that people appreciate about Ethereum is decentralization and CROPS. The main pragmatic benefit that these things translate into is stability. SoV is the category where that is not an unneeded extra we merely put effort into for ideological reasons, but rather a pragmatic…
- 1KReplies
- 1.2KReposts
- 6.9KLikes
- 2.1MViews

@VitalikButerin ·
I know this is a predictable opinion from me but I don't agree with the strong emotional reaction against the anti-data-center movements that I've seen this week. As I see it, algorithmic progress means that whatever you would be able to do with more and bigger data centers in 2 years, you will be able to do with the data centers we have today in 4 years - probably sooner. So nothing remotely apocalyptically bad will happen from even extreme levels of success by anti-data-center people. Meanwhile we need all the time we can get to better harden the world against both already-visible cybersecurity issues and any bio and other risks soon to come. Science applications are bottlenecked by many things other than AI, so slowing AI down by one year will slow those down by much less than one year. Given this, a slowdown in compute hyper-scaling seems quite net good? Notice this is without any controversial "doomer arguments", RSI etc. Even if net-bad, it's certainly not worse than like 10+…
- 526Replies
- 300Reposts
- 3.9KLikes
- 451.3KViews

@VitalikButerin ·
Just arrived in Mumbai! Looking forward to seeing familiar faces and new faces and all the wonderful Ethereum and open/secure/private/decentralized tech projects that everyone is working on over the next week.
- 820Replies
- 379Reposts
- 6.3KLikes
- 543.7KViews

@VitalikButerin ·
Digital minimalism https://t.co/UF9M3Kx1fm
- 579Replies
- 512Reposts
- 4.4KLikes
- 1.1MViews

@VitalikButerin ·
For anyone getting into biology, please consider taking airborne disease resistance more seriously. It's a super important area of medicine that is a huge cause of death and sickness but easily gets forgotten. We're likely to get many more airborne plagues in the future due to the combination of not just extremely dense and interconnected society (including city and farm animals), but also accidents from bio research and offensive biotech (both from random people and from secret government programs that can easily get themselves exempted from safety restrictions), all enhanced by powerful AI. Right now, this area is getting way less love than longevity research (which continues to be super important!), but it's an area where there are lots of unclaimed wins that we know exactly how to do (but are not yet doing) with present-day tech: * early detection * passive universal testing * filtration/ventilation/UVC * better vaccines (including making them open source and open science) *…
- 440Replies
- 372Reposts
- 3.4KLikes
- 429KViews

@VitalikButerin ·
I am okay with Kimi 3.1 deliberately leaving out top-end offensive cyber capabilities from their training data. Discriminating against use cases is MUCH less bad than discriminating against users. And the world does need all the time it can get to prepare, harden, check old code, (properly) formally verify new code, etc before the full weight of very powerful cyber attacks is upon us. And if this first big wave of AI risk is not handled well, then we may well get a dystopia of highly locked down models, KYC gating on everything, highly intrusive surveillance on everything, a society where you may be a second or third or fourth-class citizen in terms of model access based on your credentials and nationality.
- 397Replies
- 233Reposts
- 2.7KLikes
- 442.3KViews
Show all 30Show fewer

@VitalikButerin ·
Ultimately, precompiles and EVM are both the wrong place to put most cryptography support into Ethereum. The reason is that precompiles and EVM both operate on data that has to be included into the ethereum chain somehow, which realistically means included in a block as calldata. That space is limited - even with PeerDAS and blocks-in-blobs, there's a practical cap of ~8 MB/s before it starts getting uncomfortable. Remember: it's not a blockchain. It's a cryptographic world computer. Any data/computation that does not need to be in the "main thread" of data/execution should not be put into the main thread. Instead, the correct solution is... EIP-8288 maximalism. If you have any heavy computation that's self-contained, compute it and STARK it client-side (this is quickly getting faster and faster, even on phones), and push the STARK through the EIP-8288 recursive aggregation mechanism. The chain sees the fact that the computation was done and what the result is; it never needs to…
- 457Replies
- 284Reposts
- 2KLikes
- 419.9KViews

@VitalikButerin ·
Fun fact of the day: Bitcoin mining cost is split about 50/50 between compute capex and electricity. Meanwhile, AI inference is almost completely dominated by compute capex.


- 507Replies
- 177Reposts
- 2KLikes
- 368KViews

@VitalikButerin ·
Wrapped zkAPI + Tor + extra cover traffic + local LLM prompt rewriting in an open-AI compatible daemon, and made a "paranoid mode" wrapper for my agent harness (pi): Each conversation gets assigned a separate Tor circuit, your requests are masked with random cover traffic, zkAPI ensures you don't leak your identity through payments, and all prompts are locally rewritten (bring-your-own-local-model; I'm using qwen3.8-flash-next) https://t.co/MepCFCrLv1 My agent harness is wrapped with a bwrap sandbox (also experimenting with MicroVM) and wrapped again with torsocks, so everything it does goes through Tor. Here's what me asking it to do a simple research task looks like. It's getting quite usable! Though you definitely still pay quite a bit in increased latency, especially when starting a new conversation. Also, Tor is far from optimal here for privacy; the cover traffic mechanism is okay against passive adversaries but much weaker if the LLM provider is colluding with the guard…




- 508Replies
- 235Reposts
- 2.1KLikes
- 325.1KViews

@VitalikButerin ·
Big congratulations to the @zksync airbender team for this milestone. At this point, I consider the battle for speed to be definitively won, and the top priority for zkEVMs should shift fully to security. To me that means formally verifying (i) equivalence of the arithmetization to the ethereum spec (ii) a hard maximum bound on (prover cost) / (amount of gas in block) (iii) security of the proof system itself https://t.co/cgtFXBpicf
- 400Replies
- 345Reposts
- 2.5KLikes
- 428.2KViews

@VitalikButerin ·
For anyone who is either a fan of vaccines, or a critic of vaccines but open-minded to the idea that vaccines *could* be great if they were made with a more open-source open-science and public-spirited approach, I highly recommend checking out PopVax. https://t.co/aEQT73Rnhd https://t.co/2InntVg15h

- 317Replies
- 185Reposts
- 1.8KLikes
- 256.2KViews

@VitalikButerin ·
Correction: for multisigs the ideal "safe" rule is that you want each signer to change their key after each operation. (This is making an implicit assumption that ECDSA might become weak, but not to the point where any crack of it would be literally instant so you would literally have to worry about eg. in-mempool frontrunning) You definitely still want to gather sigs offchain if possible, to minimize the number of hours between "sig revealed" and "key no longer active" But again: it's very easy to lose funds from a misconfigured rushed upgrade, so ... don't rush anything.
- 340Replies
- 205Reposts
- 1.7KLikes
- 421.1KViews

@VitalikButerin ·
I don't recommend anyone scramble to move their funds to new wallets today. But we should take the risks to cryptography from AI-accelerated math seriously, and minimize our exposure to not just quantum-vulnerable cryptography, but also potentially AI-vulnerable cryptography. The core new area of risk from this viewpoint is, unfortunately, ML-DSA / FHE / lattices. (and it's also another reason, along with quantum, why ECDSA might fall even faster than expected, hence the "fresh address" recommendation) So far most people have been in the mode of thinking "elliptic curves broken, hashes safe, lattices safe". But there is a good chance that the concrete security of lattices will take serious hits from the next two years of AI math. The basic threat model is: factoring is something that naively takes 2^(n/2) time, but over decades smart people have found and optimized number field sieves, and degraded that to 2^O(n^(1/3)), which is why RSA keys and signatures need to be ~400 bytes…
- 1.2KReplies
- 1.9KReposts
- 11.2KLikes
- 4MViews

@VitalikButerin ·
Nethermind continues doing excellent work and making Ethereum more efficient and faster. https://t.co/PCyDfWIvpB
- 242Replies
- 105Reposts
- 1.2KLikes
- 269.4KViews

@VitalikButerin ·
Doing a bit of a self-experiment. Goal: use my personal health and travel data to provide personalized diet and exercise recommendations for me, using frontier models but in a way that avoids leaking to them any private information. Strategy: use a local model (Qwen 3.8 Flash Next) to orchestrate, and use powerful remote models as a tool call to benefit from higher-level thinking and knowledge that the local model does not have. Three-layer approach to privacy: Avoid leaking personally identifiable information, or leaking my identity through writing style -> local model writes the queries to the frontier model, not me Avoid leaking who I am through the payment channel -> zkAPI Avoid leaking who I am through networking / IP -> Tor You need all three (and finally we have all three, at least to some extent) A skill file teaches the local model when and how to construct minimally-data-revealing requests to remote models. Use zkAPI-wrapped-with-Tor as a CLI tool. And everything…


- 412Replies
- 207Reposts
- 2.1KLikes
- 477.7KViews

@VitalikButerin ·
Also this thing is done now https://t.co/1VFk2f0fZx
- 635Replies
- 292Reposts
- 3.2KLikes
- 907.7KViews

@VitalikButerin ·
The cryptographic world computer: https://t.co/LF2JGU38Rx My attempt to express in somewhat concise terms the true meaning of basically everything planned to happen to Ethereum starting from the fork after Hegota. It's really not just a blockchain anymore. It's a hybrid architecture that combines together blockchains and modern cryptography, to enable much more powerful properties. FOCIL, EIP-8288, Lean consensus, state management, formal verification, advanced mempool improvements (including privacy), and the longer-term specter of obfuscation all mentioned.
- 588Replies
- 1KReposts
- 5.7KLikes
- 1.5MViews

@VitalikButerin ·
It's an underappreciated triumph of Ethereum client developers that PeerDAS has now been running for nearly a year with basically no problems. PeerDAS was a complex task: it's the first large-scale instance of a blockchain that achieves consensus on the availability of data without needing any single node to download the entire block. Decentralized consensus without replication. And yet, it worked.
- 281Replies
- 268Reposts
- 2.7KLikes
- 318.4KViews

@VitalikButerin ·
Testing out some of the mobile offline local knowledge apps that people have been trying to build (see here https://t.co/cjtSqLgbc6 ) Definitely getting much better than the one I tried to build myself 2 months ago. But also still much slower and less effective at difficult questions than the models that can run on a laptop. It's weakest at specialized travel-related queries (eg. my eval is "Tell me the best vegan restaurants in [city I am currently in]", unfortunately none of these performed well on that) Looking forward to seeing these continue to improve! I hope we can soon get to the point where you can comfortably look up any facts about the world that you care about without needing to access the internet at all.




- 290Replies
- 187Reposts
- 1.4KLikes
- 345.8KViews

@VitalikButerin ·
qwen3.8-flash-next ethereum client 100+ GB of local downloaded wikipedia + gutenberg + science articles what else? (Getting rid of the need for centralized pinning services in IPFS is definitely high up the prio list)
- 171Replies
- 96Reposts
- 1.1KLikes
- 307.8KViews

@VitalikButerin ·
Reminder: you can now sync an ethereum node within half a day and with aggressive settings the space it takes up on disk can be under half a terabyte. EIP-4444 and hard work by client teams on optimizing snap sync has improved things *a lot*. Glamsterdam will improve the sync situation further still (eg. Nimbus's new sync protocol uses it)

- 187Replies
- 217Reposts
- 1.9KLikes
- 283.9KViews

@VitalikButerin ·
new solidity compiler dropped https://t.co/F42fXhUklm
- 149Replies
- 84Reposts
- 751Likes
- 275.5KViews

@VitalikButerin ·
Glad to see that Ethereum L1 will have a new strong prediction market contender that is dedicated to decentralization, and being ethical and not corposlop, and to actually trying to do interesting and meaningful things with this class of economic primitive. https://t.co/Rj86ZJl3G4
- 406Replies
- 347Reposts
- 3KLikes
- 857.6KViews

@VitalikButerin ·
There continues to be a lot of quiet dissent against the regime, which expresses itself any time some kind of channel appears (in this case, the "election" taking place right now) (The goal is not to literally get Putin to politely step off his chair; the election is of course manipulated to hell on multiple levels, and even if he loses he will just ignore it. Rather, the realistic goal is to delegitimize the regime as much as possible, denying it the internal cohesion it needs to pursue the "total war" path so that it has no choice but to take the peace path) https://t.co/gJRFiZ713O
- 193Replies
- 65Reposts
- 880Likes
- 255.8KViews

@VitalikButerin ·
It's only dead if you give up I'm not giving up on privacy. I'm doubling down. https://t.co/CdLNAiCC9h
- 494Replies
- 375Reposts
- 3.3KLikes
- 580.9KViews
Formats
Content mix
- Text only
- 33%
- With media
- 23%
- With links
- 18 posts
- With hashtags
- 0 posts
Creator style: High-reach broadcaster
See the full app
This creator report is one small part of Xholic
Click through a sample creator's account in the real app. No sign-up, nothing to install.
- Posts written in your voice and scheduled for your best hours
- Buyers found on 𝕏, with a reply drafted for each one
- Analytics that show which posts grow you
No sign-up or login needed · Takes about 2 minutes

Want numbers like @VitalikButerin's?
Xholic writes posts in your voice, schedules them for the hours your audience is active, and tracks what's working every day.
No card needed · Nothing to cancel
Live demo: no sign-up or login needed · takes about 2 minutes
Keep browsing
More in Business, investing & crypto
Keep exploring
Free tools
- Compare Twitter AccountsPut two public accounts head to head and see who leads on views, engagement, grade and posting pace.
- Twitter Engagement Rate CalculatorCalculate engagement rate from your numbers or a public profile and grade it against your tier.
- X Monetization CalculatorChange the assumptions behind six X revenue models and compare gross revenue with direct contribution.
Guides
- X/Twitter Analytics Glossary: Every Metric Explained (2026)Definitions, formulas, benchmarks, and actions for X/Twitter analytics metrics including impressions, reach, engagement, followers, clicks, and revenue.
- How Much Is My Twitter Account Worth?What an X account is worth at 1K, 10K, 100K and 1M followers, worked out with the exact median-views formula our free calculator uses, plus real results.
From the blog
- X Analytics for Brands & Businesses: A Practical GuideHow brands and businesses use X/Twitter analytics to track reach, engagement, and ROI — with the KPIs that actually matter.
- X (Twitter) for Business: The Complete 2026 GuideSet up X for business, build an organic and paid strategy, use DMs responsibly, and track the metrics that connect X activity to revenue.
Best tweets on this topic
- Best tweets about Micro SaaSExplore the best tweets about micro SaaS, featuring niche ideas, validation, product building, pricing, distribution, recurring revenue, and founder results.
- Best tweets about Creator EconomyExplore the best tweets about the creator economy, covering platforms, audience ownership, monetization, products, sponsorships, and creator businesses.
- Best tweets about BootstrappingDiscover the best tweets about bootstrapping, including profitability, customer funding, lean teams, distribution, tradeoffs, and founder experiences.
About this data
- Analytics are inferred from public profile and recent post data. They do not include private impressions, profile visits, link clicks, or follower-source data.
- Deleted, protected, unavailable, or rate-limited posts may be missing from the sample.
- Stats come from public posts Xholic has stored, not private X Analytics. Xholic is not affiliated with X Corp or @VitalikButerin.
- Own this account and want it hidden? Email support@xholic.ai — we verify ownership and handle requests within 2 working days.