✳flâneur — a map of the web's best reading

Introduction - MagicBlock Documentation

docs.magicblock.gg · 117 words · saved by 1 readers

The core intuition is that by harnessing the SVM’s account structure and its capacity for parallelization, we can split the app/game state into clusters. Users can lock one or multiple accounts to temporarily transfer the state to an auxiliary layer, which we define as the “ephemeral rollup”, a configurable dedicated runtime. This process temporarily entrusts the sequencer to modify the accounts in the ephemeral rollup, where the state can be forcefully reverted and unlocked on the L1 if constraints are not satisfied. Read the whitepaper for more details. Despite this delegation, operations and transactions can still use the delegate accounts as readable on the base layer. Non-delegated accounts remain unaffected and modifiable. The ephemeral rollup operates as a specialized SVM runtime to facilitate transaction processing at an elevated throughput. Additionally, this specialized runtime can be customized to include configurations like gasless transactions, quicker block-time, and the

Products - MagicBlock Documentation Documentation Index Fetch the complete documentation index at: /llms.txt Use this file to discover all available pages before exploring further. Skip to main content Ephemeral Rollup (ER) Execute real-time, zero-fee transactions securely on Solana. Private Ephemeral Rollup (PER) Protect sensitive data with compliance — built on top of Ephemeral Rollups. Private Payment API Add private onchain transfers to your app in seconds — compliant by default. Solana VRF Add provably fair onchain randomness to games, raffles, and real-time apps. Pricing Oracle Access lo

Explore this link on the map →

saved by

related reading