Plasma

• Name: Plasma
• URL: https://www.plasma.to/
• Category: stablecoin-first Layer 1 / stablecoin payments infrastructure / EVM execution and Bitcoin-bridge stack
• Tags: ethereum-ecosystem
• Summary: Plasma is a stablecoin chain with EVM compatibility and a Bitcoin bridge, not a generic L1 chasing payments later. The reusable part is zero-fee USD₮ transfers, custom gas-asset support, confidential-payment work, and the way the project packages stablecoin apps, account abstraction, and Bitcoin ingress around that base.
• What it does:
  • Builds a high-performance Layer 1 focused on stablecoin payments and settlement
  • Uses PlasmaBFT consensus together with a Reth-based execution client to provide EVM-compatible execution
  • Targets stablecoin-specific features such as zero-fee USD₮ transfers, custom gas tokens, and confidential payments
  • Exposes standard EVM developer workflows, with public RPC endpoints, browser-wallet setup, Hardhat-based quickstarts, and a block explorer
  • Plans or supports adjacent payments infrastructure through ecosystem integrations for smart accounts, bundlers, paymasters, wallets, card issuance, on/offramps, and compliance tooling
  • Includes a native Bitcoin bridge intended to move BTC into Plasma’s EVM environment without a centralized custodian
• Key claims:
  • The homepage says Plasma is a “high-performance layer 1 blockchain purpose-built for stablecoins” and frames the network as stablecoin infrastructure for a new global financial system
  • The get-started docs say Plasma is purpose-built for stablecoins and highlight zero-fee USD₮ transfers, custom gas tokens, confidential payments, and throughput for global scale
  • The architecture docs say Plasma combines PlasmaBFT consensus, a Reth-based execution client, and a native trust-minimized Bitcoin bridge, with EVM behavior matching Ethereum mainnet
  • The network-information docs expose a public mainnet beta and testnet with chain IDs, RPC endpoints, block explorers, and a note that public RPC endpoints are rate-limited for production use
  • The quickstart docs show a standard Ethereum-developer flow using Hardhat, MetaMask/Trust Wallet/Rabby, and testnet RPC + explorer infrastructure, which supports the claim that Plasma is aiming for familiar EVM onboarding rather than a bespoke developer stack
  • The account-abstraction tooling page explicitly lists Safe, Gelato Relay, Thirdweb, ZeroDev, Privy, and Turnkey as supported or documented providers, which is strong evidence that Plasma is packaging a broader stablecoin-app ecosystem rather than only a base chain
• Whitepaper: No canonical standalone Plasma whitepaper or litepaper surfaced in this pass. The clearest current sources of truth were the official site and docs corpus; see ../whitepapers/plasma-primary-sources-2026-05-02.md.
• Sources:
  • https://www.plasma.to/
  • https://www.plasma.to/docs/get-started/introduction/start-here
  • https://www.plasma.to/docs/plasma-chain/architecture/system-overview
  • https://www.plasma.to/docs/plasma-chain/network-information/connect-to-plasma
  • https://www.plasma.to/docs/plasma-chain/tools/account-abstraction
  • https://www.plasma.to/docs/guides/development/quickstart

Internal linkages

• Strongest payment-chain peers: stable and tempo.
• Structural bridge contrast that matters here: bitvm-bridge.

Governance / control risk

• The leverage sits in validator admission, zero-fee transfer policy, custom gas-token support, confidentiality defaults, and the bridge path that moves Bitcoin-side value into the chain.

• So the right cut is not stablecoin L1 as branding. It is a payments chain whose throughput, privacy, and ingress policy can still be shaped by a fairly concentrated operator stack.

• Last reviewed: 2026-06-02 UTC