I spent some time digging into the history of Hyperledger Besu to understand how
@Consensys may have monetized it over the past 7-8 years after Besu was moved into open-source / Hyperledger.
Here is what I found.
ConsenSys did not only have Besu core - a free open-source execution client. It also had a commercial version, which was described publicly as a commercial distribution of Hyperledger Besu.
In practice, it was an enterprise package around Besu:
β’ advanced enterprise features;
β’ 24/7 production support;
β’ customized training;
β’ encryption at rest / RocksDB encryption;
β’ advanced monitoring;
β’ event streaming via Kafka / Kinesis;
β’ group privacy modifications;
β’ contract permissioning.
It is impossible to know exactly how much ConsenSys earned from this business line, because ConsenSys is a private company and did not publicly disclose separate revenue figures for Besu / PegaSys Plus.
Now letβs move to Lineth / Linea (
@LineaBuild).
If we treat Lineth as a kind of βBesu V2β, which is roughly how Lubin seems to position it, then one phrase from the public Linea Stack documentation becomes especially important:
βReach out to enquire about our rollup-as-a-service or to access our dedicated design team who will configure the stack to your business needs.β
In my view, this phrase gives the clearest indication of ConsenSysβ potential monetization model around Lineth:
β’ rollup-as-a-service;
β’ enterprise support;
β’ stack configuration for specific business needs;
β’ architecture design;
β’ integrations;
β’ support for corporate deployments.
And this is the important point: this does not really look like a direct source of value accrual for the
$LINEA token economy.
Most likely, cash flow from these services would go directly to ConsenSys, similar to how enterprise monetization around Besu previously went to ConsenSys / PegaSys, not to any public token.
So the main question becomes:
What real economic value capture models remain specifically for
$LINEA?
Based on publicly available information, Lineth can be used to launch several types of networks:
1. L2 Private Validium on Ethereum
2. L2 Public on Ethereum
3. L3 Private Validium on Linea Mainnet
4. L3 Public on Linea Mainnet
In my view, options 1 and 2 do not create direct economic value for
$LINEA.
Why?
Because if a company launches a separate L2 based on Lineth and finalizes directly on Ethereum, the economic flow looks roughly like this:
Users pay fees on the corporate L2 -> the L2 operator collects revenue -> the L2 operator pays Ethereum L1 costs for proofs / blobs / settlement -> the remaining surplus belongs to that L2βs own economic design.
In other words, Linea Mainnet may not be involved in this flow at all.
Yes, Lineth as an open-source stack can strengthen the status of Linea / ConsenSys, increase trust in the technology, and attract more enterprise attention. But I do not currently see a direct mechanism that forces such L2s to send surplus fees to buy back / burn
$LINEA.
Especially after Lineth was contributed to the Linux Foundation / LF Decentralized Trust, it is hard to imagine ConsenSys being able to require all users of the stack to redirect remaining fees into the
$LINEA economy.
βοΈBut in options 3 and 4, there is already a direct connection to Linea Mainnet.βοΈ
If a network is launched as an L3 on top of Linea, the economic flow looks like this:
Users pay fees on the L3 -> the L3 operator collects revenue -> the L3 operator pays Linea Mainnet for finalization / commitments / proof-related transactions -> these payments become activity and gas revenue on Linea Mainnet -> after costs, Linea Mainnet surplus goes to 20% ETH burn and 80% LINEA buyback / burn.
This is where real value capture for
$LINEA starts to appear.
But there is an important nuance.
Not all fees paid by users inside the L3 will reach the burn mechanism. Only the part that the L3 pays to Linea Mainnet for finalization / commitments / proof-related transactions will reach Linea Mainnet.
So a single L3 may not generate much revenue for Linea Mainnet. But if there are many such L3s, the effect could become meaningful.
Who could potentially need an L3 on top of Linea?
β’ those who need stronger privacy;
β’ those who need cheaper finalization because the economics do not work with direct settlement on Ethereum L1;
β’ banks, fintech companies, payment networks, RWA platforms, and corporate consortia;
β’ applications that need their own controlled environment, but do not necessarily need maximum L1 finalization for every batch publication.
For example, SWIFT could theoretically choose an L3 model on top of Linea instead of launching a separate L2. But this is not a fact and not insider information, just my own scenario analysis.
To summarize:
L2s built on top of Lineth primarily give Linea status, trust, technology distribution, and enterprise legitimacy. In some cases, they may even become competitors to Linea Mainnet.
But L3s that use Linea Mainnet as their finalization layer can create direct economic value for
$LINEA through Linea Mainnet gas revenue and the subsequent ETH / LINEA burn.
So for the
$LINEA token, the key question is not simply βhow many networks will be built on Linethβ.
The key question is different:
How many of these networks will choose Linea Mainnet as their finalization layer?
In my view, this is what will determine whether Lineth becomes just an enterprise open-source stack for ConsenSys or a real source of economic value for
$LINEA.