'The Bank Stack of Ethereum' is a sharp claim buried under proof
Clara · July 1, 2026
Here's what stands out to me right away: your headline is genuinely good. "The Bank Stack of Ethereum" is specific, it stakes a claim, and it tells me exactly who you built this for. That is rarer than you think in crypto infrastructure, where most homepages read like a physics paper.
But then the page gets nervous. Below that confident headline, you pile on four solution blocks, three case studies, a prover, a developer section, a security section, and a news wall. You have the receipts to back the claim, and that is your real strength. Fidelity, CoinDesk, CNBC, five regional banks, a bug bounty at $1.1M. Most of your competitors would kill for this evidence.
The problem is not what you say. It is that the page never slows down to tell me why a bank was stuck before you showed up, or what happens to them if they keep waiting. You show me the destination and the vehicle, but never the reason the journey matters.
Clarity Score
69/100
Emerging
'The Bank Stack of Ethereum' is a sharp claim buried under proof
Messaging Shape
My honest take
I want to start with the win, because it's a real one. "The Bank Stack of Ethereum" does the hardest job on the page in five words. It names the audience (banks), the category (infrastructure stack), and the credibility anchor (Ethereum). I know instantly whether I'm the right visitor. Most infrastructure brands make me scroll three times to figure that out.
Your proof is also unusually strong. The logos are not decoration: Fidelity, Circle, Fireblocks, Anchorage, and then case studies with named partners (BitGo, Cari Network, ADI Chain) and press from CoinDesk, CNBC, S&P Global. You even attribute the vision to a named founder in the news links. This is the receipt drawer most crypto companies wish they had.
Here is where I get stuck. The page tells me what ZKsync does with beautiful precision, but never tells me the story of the customer's pain. What was the bank trying to do before? Why couldn't they do it? "Privacy is the first gating criterion for banks moving onchain" lives in a buried video description. That is your insight, and it should be doing work near the top, not hiding in a caption.
The body copy also assumes I already believe the premise. Phrases like "capture MEV under your rules" and "orchestrate collateral atomically across systems" are correct, but they speak to someone already sold on going onchain. You've written for the converted, not the curious bank executive who still needs to be convinced this is worth the risk.
And there's no cost of standing still. Nowhere do you tell me what a bank loses by waiting, what the competitive threat is, or why now. The whole page is capability and proof, with the emotional and strategic stakes left silent. That's the gap between a strong page and a compelling one.
Why this keeps happening
I think this page was built by people who deeply understand the technology and have accumulated genuine proof, but who haven't codified a single spine for the customer's story: the specific pain a bank feels, the reframe that makes them lean in, and the stakes of doing nothing. Without that spine written down, the page defaults to listing everything the product can do, in the confident hope that the visitor will assemble the narrative themselves.
What your website actually says
What does your site communicate?
ZKsync is a cryptographically secured network of public and private chains built to bring banks and financial institutions onchain with privacy, performance, and compliance.
Who is it for?
Financial institutions, banks, and enterprises evaluating blockchain infrastructure, plus the developers who would implement it.
What problem does it solve?
Institutions need privacy, performance, and connectivity to operate onchain, and existing options force tradeoffs between compliance and interoperability, though the problem is asserted more than dramatized.
What outcome does it promise?
Launch and control your own compliant chain, tokenize real-world assets with user-level privacy, and settle cross-border in real time without trusted third parties.
Visual signal
congruentrestrained navy, soft blues, and white with a clean sans-serif; connotes institutional seriousness and trust
Your palette and typography read as calm, credible, and institutional, which is exactly right for a page claiming to be the bank stack, so the visual register reinforces rather than fights your words.
Detailed Analysis
A killer headline carrying copy written for the converted
Your headline is the star. "The Bank Stack of Ethereum" could not be pasted onto a competitor's site without being wrong, and it carries a clear point of view. "Secured by cryptography, not validators" reinforces that voice with a genuine reframe. When you're sharp, you're very sharp.
Proof density is excellent: specific numbers, named institutions, attributed press, and dollar-denominated bug bounties. This is the difference between claiming trust and demonstrating it, and you consistently demonstrate it.
Where it slips is emotional registration and, in places, accessibility. The body copy speaks fluently to someone already sold on going onchain ("capture MEV under your rules," "orchestrate collateral atomically") but does little to make a hesitant bank executive feel the recognition or urgency that moves a decision. The prose is competent and dense, rarely repetitive, but it registers as a capability inventory more than a message that makes someone feel something.
Instantly clear who and what, muddier on the sequence
On the two questions that matter most, this page is strong. Identity is unmistakable within the first viewport (banks, institutions), and the category is plain (a network of chains, blockchain infrastructure). A cold institutional visitor knows within seconds whether they belong here.
Differentiation is present and occasionally sharp: "secured by cryptography, not validators" and "the only Ethereum-secured blockchain platform purpose-built for institutions" give real reasons to choose. Jargon is heavier: for a qualified evaluator the terms are followable, but phrases like "capture MEV under your rules" and "atomic, privacy-preserving settlement" assume insider fluency.
The weaker spot is cognitive sequencing. After a clean hero, the page fans out into four solution blocks, then products, then a prover, then developers, then security, then news. It answers "what can it do" many times before it ever answers "why does this matter to me and what happens if I wait." The information is all here; the order rewards the already-interested more than the newly-curious.
Strong proof and clear customer, silent on pain and stakes
You nail the top of the story. The customer is unmistakable (banks and institutions), the functional job is concrete (launch a chain, tokenize assets, settle cross-border), and your authority is loaded with named partners, real metrics, and tier-one press. That combination alone puts you ahead of most infrastructure pages I read.
Where the story thins out is the friction and the outcome contrast. You reference the need for privacy and compliance, but you never dramatize the specific obstacle a bank hits today: what breaks, what it costs, why the current path fails. Your insight (privacy is the gating criterion for institutional adoption) exists, but it lives in a video caption instead of anchoring the page.
The stakes beat is entirely absent. There is no articulation of what a bank loses by waiting or what the competitive threat looks like. And the transformation is described in feature terms (own your UX, capture MEV under your rules) rather than at the identity level of how a bank's world changes on the other side. The result is a page that is proof-rich and pain-poor.
Banks and institutions are named clearly in the headline and reinforced throughout, with functional jobs like launching chains and cross-border settlement made concrete.
Obstacles like "complex banking integrations" and "third-party risk" are named, but abstractly rather than as a pain the reader recognizes viscerally.
Authority is exceptional with named partners, metrics, and tier-one press, but empathy and the core insight are underdeveloped or buried.
The plan exists across the developer and product sections ("self-hosted or managed," EVM-native, testnets) but is scattered rather than shown as one clear sequence.
Transformation is framed as features ("Own your UX, data, and economics") and the cost of inaction is entirely absent.
Your primary CTAs are visible and, unusually, specific. "Launch a public chain" and "Launch a private chain" sit above the fold and tell me exactly what I'm choosing between. That specificity is better than the "Get Started" boilerplate most infrastructure sites default to.
The friction is well-managed too: both buttons lead to documentation, which is a low-commitment, self-serve entry point that suits a technical evaluator. There is also a "Contact us" path for institutions who need the human route.
Where it comes up short is motivation and hierarchy. There is no reason to act now rather than later, no articulation of what the visitor gains today. And offering two co-equal primary buttons at the very top, before I understand which one is for me, creates a small fork in the road before I've been given the map. A visitor who doesn't yet know whether they want public or private has to make a decision the page hasn't prepared them to make.
How we score
Clarity Score v7 reads each company's live homepage, words and visuals together, and scores four dimensions on a 0 to 100 scale.
What does Clarity Score measure?
Four dimensions, weighted into the overall score:
Narrative Completeness30% · does the page tell a complete story, from who it is for to what changes for them.
Message Quality30% · is the writing actually good: specific, distinctive, and worth reading.
Signal Clarity20% · does a stranger get what this is and who it is for, fast.
CTA20% · does it say what to do next, with a reason to do it.
How often is the board updated?
Every company is re-scored monthly. The Change column shows movement since the prior reading; the board baselined on Clarity Score v7 in June 2026.
What does Clarity Score not measure?
It measures how clearly a homepage communicates. It does not measure product quality, funding, traction, or whether a company is winning.
How we score
Top five1Ethereum762Helius743Highloop734Akash Network715io.net70
zkSync sits in Sharp but Shallow, with every company on the board. The strong bands open at 75.