MagicBlock

• Name: MagicBlock
• URL: https://www.magicblock.xyz/
• Category: Solana execution infrastructure / ephemeral rollup platform / private payments and low-latency data tooling
• Tags: solana-ecosystem
• Summary: MagicBlock at the project layer is the delegated-execution and real-time application stack: ephemeral rollups, private execution lanes, router-mediated transaction delivery, tokenized private-payment flows, VRF, and low-latency oracle delivery on top of Solana. The broader operator boundary now lives in magicblock.
• What it does:
  • Lets developers upgrade existing Solana programs with delegation hooks so execution can move into MagicBlock ephemeral rollups for real-time, zero-fee interaction patterns
  • Provides a router API that preserves broad Solana JSON-RPC compatibility while handling node selection, delegation-aware routing, and multi-endpoint complexity behind one endpoint
  • Offers private ephemeral rollup infrastructure and a Private Payments / Ephemeral SPL Token surface for deposits, transfers, withdrawals, swaps, auth, and shielded settlement flows across Solana and MagicBlock environments
  • Ships additional data and execution primitives including verifiable randomness and low-latency onchain oracle updates sourced from Pyth Lazer feeds
  • Maintains an active open-source footprint spanning validator software, SDKs, delegation infrastructure, examples, session-key tooling, and Unity-oriented Solana integrations
• Key claims:
  • The homepage frames MagicBlock as a real-time engine and the backend for the new financial internet, claiming 1 ms block time, under-50 ms end-to-end latency through co-location, zero fees, and compliant privacy through Ephemeral Rollups plus Intel TDX-backed trusted execution environments
  • The main docs present MagicBlock as a multi-product platform, not a single feature, with Ephemeral Rollups, Private Ephemeral Rollups, Ephemeral SPL Token / Private Payments, VRF, and a pricing oracle all exposed in one first-party documentation surface
  • The Magic Router docs say MagicBlock uses transaction metadata to decide whether execution should happen on Ephemeral Rollups or Solana, hiding manual routing logic behind a single RPC endpoint
  • The Private Payments docs describe private, compliant onchain transfers with shielded amounts, destinations, and timing, plus a broader API for deposits, transfers, withdrawals, balances, stealth pools, swaps, and auth
  • The oracle docs say MagicBlock ingests Pyth Lazer feeds and updates ephemeral-rollup accounts every 50–200 ms depending on the asset, explicitly framing this latency profile as useful for liquidations, copy trading, and other time-sensitive workflows
  • The GitHub organization describes MagicBlock as production-ready open-source infrastructure and highlights validator, SDK, delegation, examples, token, session-key, and Unity repositories, which supports viewing the project as a reusable execution platform rather than only a demo environment
• Whitepaper: MagicBlock does have an Ephemeral Rollups whitepaper, but the clearest current product sources remain the official site, first-party docs across execution/privacy/data products, and the GitHub organization. For refreshed company-boundary source capture, see ../whitepapers/magicblock-company-primary-sources-2026-08-12.md.
• Sources:
  • https://www.magicblock.xyz/
  • https://docs.magicblock.gg/pages/overview/products.md
  • https://docs.magicblock.gg/pages/ephemeral-rollups-ers/introduction/magic-router.md
  • https://docs.magicblock.gg/pages/private-ephemeral-rollups-pers/api-reference/per/introduction.md
  • https://docs.magicblock.gg/pages/tools/oracle/introduction.md
  • https://docs.magicblock.gg/pages/verifiable-randomness-functions-vrfs/how-to-guide/quickstart.md
  • https://docs.magicblock.gg/llms.txt
  • https://github.com/magicblock-labs

Internal linkages

• Company boundary for the broader operating shell: magicblock.
• Keep the comparison set on real-time execution and operator-shaped control planes: helius, tenderly, and astria.
• Reusable lens: MagicBlock matters when delegated execution, routing, token privacy, oracle freshness, and application-side automation collapse into one product surface.

Protocol / company boundary

• This note keeps the product-layer cut: delegated execution on ephemeral rollups, router-mediated transaction delivery, private token/payment flows, VRF, and low-latency oracle distribution as reusable developer surfaces.
• magicblock is the operator note for the broader managed shell around endpoint issuance, regional / TEE infrastructure, pricing and dedicated-resource access, audit publication, and service-health signaling.
• That split matters because teams may compare MagicBlock’s architecture with other execution stacks while still inheriting a named company for the live routing and service boundary.

Control surface

• At the project layer, practical leverage sits in what programs delegate, how router-mediated execution decides between Solana and MagicBlock environments, how private token flows settle, and how oracle / randomness primitives get embedded into applications.

• Once the question shifts to who runs the endpoints, who publishes the status page, or who packages priority and dedicated access, the sharper note is magicblock.

• Last reviewed: 2026-08-12 UTC