The zkEVM that changes nothing about your code
Scroll is a zero knowledge rollup built for bytecode level compatibility with Ethereum, aimed at teams who want proving without rewriting anything. It is deliberately unglamorous and largely made of engineers.
SCR right now.
Pulled live every time this page loads. We do not hardcode market figures, because a stale number on an agency site is worse than no number at all.
What Scroll is actually for.
Scroll is a zero knowledge rollup that took the hardest available path, proving the Ethereum virtual machine at the bytecode level rather than building a new virtual machine and asking developers to adapt to it. The practical result is that contracts, tooling, debuggers and audit assumptions carry over with little modification. That choice cost the team years of research and gives builders something specific in return, which is that the thing running on Scroll is the same thing running on Ethereum, not a translation of it.
The chain is used mostly for standard EVM activity: exchanges, lending, stablecoins, bridges and the infrastructure layer around them, plus a steady flow of teams deploying Scroll as one of several networks rather than as an exclusive home. Its academic and open source posture attracts a particular kind of builder, often one already contributing to Ethereum research or client work. There is a consumer and collectibles layer, but nobody would describe it as the chain's center of gravity, and pretending otherwise helps no one.
Culturally Scroll sits close to Ethereum itself. The values talk is sincere rather than positioning, the community is heavily developer weighted, and marketing that leans on hype tends to be met with polite indifference. Compared with rollups that launched through aggressive incentive campaigns, Scroll's user base is smaller and quieter, and the people there are more likely to read your code than your announcement. That is either exactly what you want or exactly the wrong room, depending entirely on what you are building.
What the SCR token actually does.
The mechanics matter to you because the network token is the thing your own token competes with for the same attention and the same balance sheet.
Fees are paid in ETH
Like most Ethereum rollups, transaction fees on Scroll are denominated in ETH. SCR is not the gas asset, so documentation you publish should be explicit about that to avoid confusing users.
Governance
SCR is the governance token for the network, giving holders a say in protocol decisions, treasury allocation and the direction of ongoing decentralization work on sequencing and proving.
Ecosystem funding
Governance controls programs that fund builders and public goods, which is a practical route for teams whose work aligns with the chain's open source posture.
Participation weighted distribution
A significant share went to users and contributors rather than to a closed sale, shaping a holder base that skews toward people who had actually used the chain.
Scroll's supply is capped and weighted toward community and ecosystem allocations, with core contributor and investor portions vesting over time. Distribution favored onchain participants and contributors to Ethereum aligned open source work, which is consistent with the chain's positioning and produced a holder base that is less purely financial than on incentive led networks. Scheduled releases still matter, and any project timing a launch here should look at them, but the dominant dynamic on this chain is governance rather than emissions.
For attention, the competition on Scroll is not a high yield alternative, it is skepticism. This audience has watched many rollups arrive and has no shortage of places to deploy. What earns notice is technical substance: a clear explanation of what your contracts do, why proving matters for your use case, and what you contribute back. Token launches that lead with allocation percentages and countdown graphics do measurably worse here than one well written engineering post. Budget accordingly, and get a real developer to write the first draft.
Who you are actually launching to.
The single most useful question about any chain, and the one most founders answer last.
Ethereum aligned developers
Builders who care about equivalence, open source and verifiability, often with a foot in client or research work. They evaluate infrastructure choices on merit and say so publicly.
Multi chain DeFi protocols
Established applications adding Scroll as another deployment, bringing their own users with them rather than expecting to find new ones on arrival.
Proving researchers
People interested in zero knowledge systems for their own sake, who treat the chain as a place to test ideas as much as a place to transact.
Good fit for
What to watch
- The rollup field is crowded and Scroll's differentiation is technical rather than cultural. If your growth plan needs a native audience to discover you, there are chains with far more ambient attention.
- Decentralization of sequencing and proving is a work in progress on every rollup including this one. Know the current trust assumptions before you tell your users the chain is trustless.
- Engineering credibility is the only currency that works here. A team without a strong technical story will find that no amount of campaign budget substitutes for having one.
Launching on Scroll with Orca Web3.
The deliverables are the same everywhere. What changes per chain is everything about how they are made.
Technical writing engineers respect
We work with your developers to produce documentation and posts that read as engineering rather than as promotion, because on this chain that writing is the marketing.
Multi deployment positioning
Most teams here ship to several networks. We build a brand and site architecture that presents Scroll properly without pretending it is the only place your product lives.
Restrained visual systems
We design for a room that distrusts polish for its own sake. Clean, dense and functional, with the substance visible rather than buried under a hero animation.
Token launch on Scroll
Positioning, identity, litepaper, tokenomics design, launch site and TGE campaign.
RWA issuance
Institutional grade brand and disclosure aware communications for tokenized assets.
dApp front end
Wallet flows, chain switching and transaction states built for this network's tooling.
Launching on Scroll, answered.
What does bytecode level equivalence actually buy us?
Fewer surprises. Your contracts compile and behave the way they do on Ethereum, existing audits carry more weight, and standard tooling, debuggers and libraries work without special cases. On zkEVMs that compile to a different virtual machine, most things work but the edge cases live in exactly the places security bugs like: precompiles, gas accounting, low level assembly. Equivalence narrows that gap considerably. It costs performance relative to more custom designs, which is a trade the Scroll team made deliberately and says so openly.
Is there enough of an audience here for a consumer launch?
Honestly, probably not as your primary source of users. Scroll's population is smaller and more technical than the rollups that ran heavy incentive campaigns, and consumer culture is not its strength. That does not make it a bad deployment target, it makes it a poor sole one. Teams building consumer products typically launch where the attention already is and treat Scroll as an additional network for users who care about the technical properties. Be clear internally about which role it plays for you.
Do we need to change anything about our contracts?
Usually very little, which is the entire point. Standard Solidity deploys as expected and most tooling works without modification. You should still test against the network rather than assuming, check any dependency on precompiles or unusual opcodes, and review how your application handles the rollup's proving and finality timing, particularly for anything involving bridging or time sensitive settlement. Treat it as a deployment target requiring verification, not as a copy of mainnet requiring none of it.
What does Orca do for a Scroll launch?
Positioning and naming, narrative and litepaper work done alongside your engineers, launch site, application front end design, documentation experience, and the campaign around release. We do not write or audit contracts and we do not make markets. On Scroll our most valuable work tends to be translation, taking real engineering and making it legible and compelling to a technical audience without adding the kind of gloss that audience specifically distrusts.
Chains a project weighing Scroll usually looks at too.
Building on Scroll?
Bring us the project and the date. We will tell you what it takes, whether Scroll is the right room for it, and what we would do differently if it is not.
Scroll and the SCR mark are trademarks of their respective owners and appear here to indicate a network we work on, not to imply endorsement, partnership or affiliation. Nothing on this page is financial, investment, tax or legal advice, and no asset named here is a recommendation to buy or hold anything.