Alta Finance vs Solana: institutional settlement vs an open L1

Alta Finance is building a compliance-first, EVM-compatible Layer 1 for banks and payment firms. Solana is a public general-purpose L1 where privacy and policy are additive. Same asset class — different jobs.

On 10 November 2026, Alta announced $80 million in total funding, including a $47.5 million Series A led by Index Ventures, to build what it calls institutional-grade blockchain infrastructure for tokenized finance. Coverage of that round listed Ethereum, Solana, and Avalanche as the existing options Alta is trying to unseat for banks.

That framing is useful, and a little misleading. Alta is not trying to be another open trading chain. It is a payments-and-treasury L1 aimed at regulated institutions, with protocol-level privacy, programmable compliance, and a planned hook into Airwallex's fiat rails. Solana is a public, permissionless L1 where markets, apps, and payments already share one execution environment. This piece compares them for Solana developers, and is careful about what is live versus what is still a claim.

What Alta is

Alta (site: alta.finance) is building its own Layer 1 for regulated institutions. The co-founders are Loong Wang (CEO; previously founded Ren, later acquired by Alameda Research), Catherine Porter (President; previously on the leadership team around Meta's digital payments work), and Jack Zhang (co-founder and CEO of Airwallex). Fortune reported about 25 employees in San Francisco and Melbourne. The company recently rebranded from Metal. X @altaxyz.

The Series A was led by Index Ventures, with participation from GV, Blackbird Ventures, Square Peg, and Capital 49. A $32.5 million seed was backed primarily by Airwallex, which is also an early design partner. The companies say the collaboration will support stablecoin pay-ins and pay-outs plus connectivity to local payment networks across 200 countries and 90 currencies. Those figures describe Airwallex's existing rails, which Alta plans to connect to — they are not Alta mainnet activity.

The first product, per the company, is liquidity management: cutting cash held in prefunded accounts (it cites an estimate of $4 trillion globally) with just-in-time funding, FX, and movement in and out of yield-bearing tokenized assets. Other target use cases are tokenized deposits, cross-border payments, and agentic payments.

Public marketing describes "a new blockchain architecture built on recursive zero-knowledge cryptography." Wang has said they "wouldn't have built an L-1 if we didn't have to." Index Ventures writes that Alta does not issue its own currency; it is a stablecoin ledger institutions can trust without exposing customer data. The company also says addresses can refuse unsolicited transfers — the "anti-airdrop" property Wang highlighted to Fortune — and that institutions can refuse or refund money, with bank rules travelling with the payment.

As of mid-November 2026, Alta has not announced a public mainnet or a launch date. A developer testnet and a devnet are live, but the public docs are still published under the previous Metal name at docs.metalntwx.com. Testnet chain ID is 63825 (0xf951); the explorer is testnet.metalntwx.com; the default test gas token is *USDZ. The Metal marketing domain now serves the Alta homepage, so this article treats those docs as the current technical surface. Re-check them if they are renamed or if mainnet parameters differ.

Two naming collisions are worth flagging: an earlier, unrelated real-estate project also used alta.finance (ALTA Finance / altafinprotocol, circa 2020–2024), and some of those pages are still indexed; Metal Blockchain (metalblockchain.org) is a different, Avalanche-derived project and is not Alta. I could not find a public GitHub organisation for this Alta; github.com/altafinprotocol belongs to the older real-estate project.

How the chain is specified today

The Metal developer docs describe an EVM-compatible chain, not an SVM chain. Execution is Reth and revm. Developers can use Solidity, Foundry, Hardhat, viem, and ethers, plus a TypeScript SDK, @metalntwx/metal-ts. An x402 path (@metalntwx/metal-pay, a hosted facilitator, and metal-agent) settles test payments in *USDZ.

Consensus is Simplex, Commonware's BFT voting protocol. Validators execute a proposed block independently, then vote on its hash. A block finalizes once a quorum is reached, under the usual assumption that fewer than one-third of validators are faulty. Finality is deterministic, and applications are told to treat a payment as settled only after a successful receipt and a consensus_status check against the finalized head. The docs say the chain supports sub-second blocks with millisecond timestamps, but they do not publish a measured finality target, and they note that if the required votes cannot be collected, finality can stall.

The validator set is permissioned. Docs say validators "are configured participants" and that "joining that set requires inclusion in the network's validator configuration." Observer nodes also need explicit peer configuration. "The process for authorizing validator membership changes remains an open design decision." Users can still hold tokens, submit transactions, and deploy contracts without joining the set, subject to admission rules and any application-level policy.

Assets use two protocol primitives:

• MIP20 is a public, ERC-20-like token with send and receive policies. A transfer credits the recipient only if both sides' policies approve. A refusal can revert, or place funds in quarantine for authorized recovery. MIP20 tokens pay gas; there is no native gas asset, and transaction value must be zero.
• MIP410 is a shielded pool for supported MIP20 assets. Zero-knowledge proofs hide asset, amount, sender, and recipient from public observers while proving authorization, value conservation, and policy compliance. Timing and the public submitter remain visible. Shielding and unshielding still reveal the public MIP20 account, asset, and amount. Viewing keys can be delegated for audits without granting spend authority.

Fees are priority-fee-only: the execution base fee is zero so fee payment does not burn the stable gas token. On testnet the default gas token is *USDZ. The testnet block gas limit is 500 million gas, with a 100 million per-transaction cap. The docs do not publish a TPS figure. Wang's Series A post says the stack "can scale to the millions of transactions per second"; treat that as a company claim, not a measured result.

Press materials present recursive zero-knowledge cryptography as the core of the architecture. The public docs put zero-knowledge proofs on the payment and policy path (MIP410 and private policy evidence), and put agreement on blocks in Simplex. Those are compatible, but they are not the same claim, and there is no public protocol paper that shows how recursive ZK sits inside consensus itself.

Side-by-side

Solana facts in that table come from official upgrade and fee docs. Alpenglow replaced TowerBFT's ~12.8-second finality path; Votor is live, and Rotor (the planned replacement for Turbine) is not yet scheduled. Execution is unchanged. Firedancer and Frankendancer were not supported for the migration; mainnet voting validators currently run Agave-based clients at v4.3.2.

Where each fits

Alta is a thesis about regulated money movement: privacy for institutional payments, policy enforced in the same transaction that moves the asset, stablecoin gas so a bank does not have to hold a volatile native token, and a planned hook into real-world payment rails. If that works, the buyers are banks, PSPs, corporate treasuries, and later agents acting under onchain mandates. It is closer in job description to Tempo — another payments-first L1 with a large fintech sponsor — than to a general-purpose chain. The differences versus Tempo are the Airwallex distribution, refuse/quarantine, and the shielded-payment path.

Solana is a thesis about one open L1 that already runs markets, consumer apps, RWAs, and stablecoin payments together. Privacy and compliance exist, but they are opted into at the token or application layer. Finality is now in the same ballpark Alta markets as "instant," and it is live on a public mainnet with a large, independent validator set.

The honest overlap is stablecoins, agent payments, and settlement fast enough for treasury and checkout. The honest divergence is openness. Alta's docs are clear that operating the network is a configured privilege. Solana's docs are clear that anyone who meets the validator requirements can participate. That is a product choice, not a bug in either design.

What this means for Solana developers

You do not have to pick a tribe. You pick a settlement surface for a product path.

1. Keep shipping on Solana if the product is a wallet, a market, a consumer app, an LST, or an open RWA issue. That is Solana's home turf, and Alpenglow has already moved finality into the sub-second range payments UX needs. See the app readiness checklist.
2. Treat Alta as an institutional rail to watch, not a rewrite trigger. There is a public testnet if you want to try Solidity and @metalntwx/metal-ts, but there is no mainnet, no published production fee schedule, and no public validator-set size. Design partners are not live volume.
3. If a bank or PSP customer asks for protocol-level receive policy, quarantine, or shielded settlement, map those requirements onto what Solana already offers — confidential transfers, transfer hooks, attestations — and be honest about the gaps. Solana can do a lot of this at the token layer. It does not, today, make "refuse this inbound transfer" a default property of every address.
4. Abstract the settlement hop in the app (pay intent → route). A merchant or treasury may want an institutional rail, while users still hold and trade on Solana. Issuers and bridges decide how painful that hop is.
5. Do not take marketing TPS, "recursive ZK," or "200 countries" as chain metrics. The first is a claim. The second is a press description the public docs have not fully specified at the consensus layer. The third is Airwallex's payment network, which Alta intends to connect to.

Resources

• Alta
• Raising $80M to Optimise Global Finance (Loong Wang, 10 November 2026)
• GlobeNewswire press release (10 November 2026)
• Index Ventures: Alta: Fixing the Pipes Behind Global Payments
• Fortune: Alta raises $48 million Series A
• crypto.news coverage (Ren / rebrand / team background)
• What is Metal
• Architecture (Simplex, Reth, permissions)
• EVM compatibility and gas
• Programmable compliance
• Private payments (MIP410)
• Protocol constants
• Settlement and finality
• TypeScript SDK
• Connect to testnet
• Alpenglow upgrade
• Solana network upgrades
• Solana fees
• Alpenglow on devrels.xyz
• Alpenglow app readiness checklist
• Tempo vs Solana
• Stablecoins on Solana
• Solana privacy landscape
• Token-2022 confidential transfers
• Token-2022 extensions field guide
• Kora fee abstraction
• X @altaxyz (official)
• X @bzlwang (Loong Wang)
• X @cclayporter (Catherine Porter)
• X @awxjack (Jack Zhang)

No public GitHub organisation was found for this Alta. github.com/altafinprotocol is the older, unrelated real-estate project. Verify mainnet status and fee model on primary sources before you commit architecture.