MetaMask Plans Consumer Split from Consensys

Consensys Software Inc. is breaking into two companies. The existing legal entity will be renamed MetaMask and run the wallet and its consumer products. A newly formed Consensys will take the protocol and institutional business. The companies will operate independently, with the separation expected to complete by the end of 2026, according to MetaMask's September 9 announcement.

For existing MetaMask users, the immediate message is narrow: there is no migration, account change, or request to move funds. The app, assets, private keys, and access remain as they are. The corporate change sits behind the product, rather than inside a user's wallet.

A renamed parent, a new sibling

Joseph Lubin will be chairman and chief executive of MetaMask. The new Consensys will be led by chief executive Mike Kriak and president David Cunningham; Lubin will be its executive chairman. MetaMask's corporate separation release says the current Consensys Software Inc. continues as the same company under a different name, while the protocols group and institutional business are placed in the new company.

That distinction is easy to miss. This is not a sale of MetaMask to an outside buyer, and the public announcement does not describe a new wallet operator arriving after a handover. The company that has operated MetaMask is adopting the MetaMask name. The business that will carry the Consensys name is the new entity built around teams and products on the other side of the split.

The announcement also says the two companies will continue in the same Ethereum ecosystem and that Consensys will remain a channel partner for MetaMask. It does not set out the commercial terms for that relationship. Those details may matter later for products that depend on shared infrastructure, but the release does not provide them.

MetaMask's consumer business

MetaMask is describing its remit as consumer finance built around self-custody. In its own statement on the split, the company says it wants users to hold, move, earn, trade, and spend assets through the platform. That is a wider brief than the browser extension through which many people first encountered MetaMask.

The clearest example is Money Account, announced in June. MetaMask says the account is self-custodial and combines automated earning, spending through the MetaMask Card where available, and trading from one balance. It runs on Monad and uses mUSD, MetaMask's dollar-denominated stablecoin, according to the Money Account release.

Those features turn a wallet into a place where a user may leave funds for longer and use them more often. That does not make Money Account a bank account. MetaMask's own disclosure says it is not a bank account, savings account, or regulated investment product, and that mUSD balances are not insured by the FDIC or another government agency. The stated yield is variable, and the company warns that third-party DeFi platforms and smart contracts carry risks, including the possibility of loss.

The product also illustrates the limits of the phrase "self-custodial financial platform." Users hold their private keys, and MetaMask says it cannot access, freeze, or move a Money Account balance. Users are still responsible for their recovery information and for approving transactions. The split does not change those obligations. A new name above the product does not reduce the consequences of a compromised seed phrase, a malicious approval, or an incorrectly sent transaction.

For MetaMask, the operational question is whether consumer products can add convenience without concealing those trade-offs. A wallet prompt is often treated as a technical step. A product that blends payments, stablecoin balances, yield, swaps, perpetuals, and prediction markets asks users to assess several kinds of risk in one place. The corporate separation gives the consumer team a single product agenda; it does not make that agenda simple.

The infrastructure company

The new Consensys inherits Linea, Besu, Teku, the protocols group, and the institutional blockchain infrastructure business. MetaMask names those products directly in its announcement. Its press release says the new company will continue protocol work and build infrastructure for financial institutions and enterprises using tokenization, stablecoins, and programmable settlement.

These are not consumer-wallet products. Linea is an Ethereum Layer 2 network. Besu is an Ethereum execution client used in public-network and permissioned-network settings. Teku is a consensus client. Their users include node operators, application teams, infrastructure providers, and institutions evaluating Ethereum-compatible systems. The work is shaped by software releases, network upgrades, client interoperability, uptime, security review, and long procurement cycles.

The institutional business also has a different set of promises to keep. MetaMask's press release refers to privacy, resilience, scale, and compliance needs. A company selling into financial institutions must support those claims with product documentation, implementation work, and operating performance. Announcing an independent company is only the first step. The release does not specify customer contracts, revenue, staffing allocations, or which future products will sit with each company.

That absence is not unusual in an initial corporate announcement. It does mean that the practical shape of the new Consensys will emerge from later disclosures: product roadmaps, changes to support arrangements, hiring, network development, and customer deployments. None of those should be assumed from the separation announcement alone.

Product boundaries during the transition

MetaMask says its SDKs, APIs, and developer tooling will continue. The FAQ attached to its announcement repeats that commitment but does not publish a revised product map, pricing schedule, or support policy. Builders therefore have a clear answer for the present and fewer answers about the later operating model.

The immediate rule for developers is to rely on published documentation and release notes, not on inferences from the corporate chart. An integration with MetaMask, Linea, Besu, or Teku remains an integration with its existing technical documentation, versioning, service terms, and support channels until the relevant product team says otherwise. The split itself does not announce a change to an API, SDK, wallet connection flow, or network endpoint.

There may be collaboration at the boundary. MetaMask says Consensys will be a channel partner, and the companies will continue building in the same ecosystem. That language establishes continued contact, not a detailed technical or commercial agreement. It would be premature to describe a future dependency, partnership structure, or product bundle beyond what the companies have stated.

The user-facing position

The most important practical point is the one MetaMask has already made: no action is required. A corporate restructuring can attract phishing attempts because users expect a migration notice or an urgent account prompt. MetaMask says there is neither. Wallet holders should treat messages asking them to disclose a recovery phrase, sign an unexplained transaction, or transfer funds because of this announcement as a warning sign.

The standard wallet precautions still apply. Check the domain before connecting a wallet, read the transaction request before approving it, keep recovery information offline, and do not rely on a social-media post as a substitute for product documentation. Those are not new policies from the separation; they are the ordinary safeguards for a self-custodial wallet.

There is no announced change to who controls keys. MetaMask says users' keys and assets remain unchanged, while the Money Account materials state that MetaMask cannot access, freeze, or move a user's balance. The company has also said the product is unavailable in the UK and other restricted jurisdictions. Availability and financial-product terms should be checked in MetaMask's current documentation rather than assumed from the corporate announcement.

The remaining work

The companies have named their leaders, product groups, and target completion date. They have not disclosed every operating detail that will follow from the split. That leaves concrete administrative work: separating teams and systems, defining agreements between the businesses, and explaining any revised product ownership as it becomes relevant.

The timetable leaves room for those decisions to be made without forcing an immediate product disruption. MetaMask says the companies are already operating independently, while completion of the separation is expected by the end of 2026. Its public materials give users and developers continuity now: the wallet remains unchanged, no action is required from account holders, and SDKs, APIs, and developer tools continue. The transition will become more visible only when a product, service agreement, or support arrangement changes and the relevant company documents it.

That makes later announcements more useful than broad corporate language. A revised developer agreement, a Linea roadmap, a change to MetaMask's product terms, or a published support contact would establish something concrete. Until then, the reported facts are limited to the split, the leadership assignments, the listed product groups, and the companies' stated plan to keep current user access and developer tooling in place. Those are the terms described in MetaMask's separation announcement and FAQ.

For MetaMask, the test is whether its consumer products remain intelligible as they expand. Its stated plan joins a familiar wallet with payments, trading, stablecoin balances, and yield. Clear disclosures, safe transaction flows, and accurate eligibility information will matter more to users than the new corporate name.

For Consensys, the test is different. Linea, Besu, Teku, and institutional infrastructure serve customers who need dependable software and long-lived technical commitments. The new company begins with recognizable products and an established role in Ethereum development. Its future performance will be visible in releases, deployments, client maintenance, and the support it provides to institutional users.