The Future of Blockchains Is Off-Chain

Bobbin Threadbare & Dominik Schmid

The future of blockchains is off-chain. Blockchain is one of the most transformative technologies of our generation. However, no L1 or L2 is currently ready for mass adoption. Either because they do not scale, cannot provide privacy, are difficult to develop on, or sacrifice fundamental principles of web3 (self-custody and censorship-resistance). The underlying cause is that virtually all current blockchains were designed before the advent of the Zero-Knowledge (ZK) technology. Even the existing ZK-based solutions are frequently just carbon-copies of pre-ZK designs with ZK technology added on, and thus, carry over design limitations of the previous generations.

Miden prioritizes ZK-friendliness over EVM compatibility. It also uses a novel state model to exploit the full power of a ZK-centric design. These design decisions allow developers to create applications that are currently difficult or impractical to build on account-based systems.

Miden is the next-generation blockchain protocol engineered to leverage the full potential of ZK technology, pushing both execution and state to the edge (i.e., the client side). This resolves fundamental issues in blockchain scalability, privacy, and safety, ensuring a new level of performance and user experience. The three main benefits of the Miden design are:

  1. Unbounded scalability: Through client-side proving, Miden allows users to execute and prove transactions locally without requiring the network to re-execute them. This enables the network to verify massive volumes of transactions concurrently and drastically reduces on-chain state storage requirements.
  2. Privacy by default: With client-side execution and a self-custodied state, users maintain complete control over their data and transaction details. The network only needs to know commitments to states, enabling private transactions and applications.
  3. Safe development for the masses: Miden prioritizes developer safety and accessibility by leveraging Rust as the primary smart contract language and incorporating in-protocol safeguards like account abstraction and self-custodied state. These features make smart contracts more safe, reducing attack surfaces and making blockchain development more approachable for crypto-native and traditional developers alike.

Scalability

To achieve ultimate scalability, Miden radically changes how blockchains are designed and the paradigm that everything in a blockchain must be transparent to be verifiable. Blockchains verify by re-executing. Re-executing requires transparency and processing power. Verification by re-execution slows blockchains down. Zero-knowledge proofs offer the possibility to verify without re-execution. Zero-knowledge verification doesn’t need transparency or processing power. In Miden, users can generate their own proofs, and the network verifies them.

This is the most important change in Miden. Users can execute smart contracts locally. Specifically, for anything that doesn’t touch the public state, users can execute smart contracts on their devices and then send ZK proofs to the network. The operators can then verify these ZK proofs exponentially faster than executing the original transactions and update the state accordingly.

Not only does this reduce the computational burden on the operators, but it also makes such transactions inherently parallelizable. Even more exciting is that it lifts the limits on what can go into a smart contract. For example, anything that a user can execute and prove locally - no matter how complex - can be processed by the network with minimal costs. On Miden, it will be cheap to run even complex computations.

Another important change in Miden is ensuring that most transactions do not need to touch the public state. We achieve this by making all interactions between smart contracts asynchronous. With Miden, token transfers, NFT swaps, and many others do not need to touch the public state. For actions that change the public state,Miden does allow regular network execution of transactions (same as most other blockchains). Still, because of the asynchronous execution model, interactions between locally executed transactions and network transactions are done seamlessly.

Safety

Assets need to be safe and easy to handle. No one should lose their tokens when losing a key or sending them to the wrong address. Miden’s approach aims to reduce the risks of using crypto on multiple fronts.

First, every account on Miden is a smart contract. This is frequently referred to as account abstraction. This enables developers building on Miden to create safer user wallets with features like social recovery of keys, rate-limiting spending tokens, transaction risk analysis, etc.

Next, because of Miden’s asynchronous execution model, it is possible to create recallable transactions, which mitigate the risk of sending funds to a non-existent address. This provides a safer environment for users.

Another change that increases safety is that in Miden, fungible and non-fungible assets are stored locally in accounts (rather than in global token contracts). This makes exploiting potential bugs more difficult, as every account needs to be attacked individually.

Speaking of bugs, to make smart contract development safer, Miden aims to support modern smart contract languages such as Rust which is designed with an emphasis on safety and correctness.

Privacy

Lastly, absolute transparency is one of the main drawbacks of blockchains. The ability to transact in private is a fundamental right and a practical necessity. And thus, we put privacy at the core of Miden’s design.

But we go beyond simple private transactions: Miden’s architecture enables expressive private smart contracts. These are almost exactly the same as regular smart contracts but are executed locally so that the user does not reveal its code, state, and interaction graph to the network. And the coolest part is that private smart contracts can interact seamlessly with public smart contracts. So, for example, private rate-limited wallets can make calls to public DEXs. Businesses and financial institutions can build and execute their business logic on Miden. They would keep information hidden from competitors but visible to auditors.

Another important point regarding privacy is that users should not have to pay extra for it. In Miden’s design, private smart contracts impose minimal burden on the network (much smaller than public smart contracts), so on Miden, it is cheaper to remain private.

We understand that privacy is a complex area in the public domain. Privacy is a complex subject requiring careful study and consideration. We plan to enable privacy on Miden in stages. Initially, users can maintain privacy from other users but not from the operators (similar to Web2 privacy). This will give us time to figure out how to enable stronger levels of privacy without opening floodgates to potential abuses.

Architecture: actor-based model with concurrent off-chain state

Miden’s architecture departs considerably from typical blockchain designs to support the above mentioned features. In future blog posts, we will cover this in much more detail, but two foundational aspects are worth covering even now.

Actor-based execution model

The actor model inspires Miden’s execution model. This is a well-known design paradigm in concurrent systems. In the actor model, actors are state machines responsible for maintaining their own state. In the context of Miden, each account is an actor. Actors communicate with each other by exchanging messages asynchronously. One actor can send a message to another, but it is up to the recipient to apply the requested change to their state.

Miden’s architecture takes the actor model further and combines it with zero-knowledge proofs. Now, actors not only maintain and update their own state, but they can also prove the validity of their own state transitions to the rest of the network. This ability to independently prove state transitions enables local smart contract execution, private smart contracts, and much more. And it is quite unique in the rollup space. Normally only centralized entities - sequencer or prover - create zero-knowledge proofs, not the users.

Hybrid state model

The actor-based execution model requires a radically different approach to recording the system's state. Actors and the messages they exchange must be treated as first-class citizens. Miden addresses this by combining the state models of account-based systems like Ethereum and UTXO-based systems like Bitcoin and Zcash.

Additionally, Miden accounts can live either on-chain or off-chain. For on-chain accounts, the full account state is always recorded on-chain (meaning on Miden). For off-chain accounts, only the commitment to the account state (i.e., state hash) is recorded on-chain. This is possible because, as described before, in the actor-based model, users can apply updates to their accounts locally and then send a zero-knowledge proof to the network attesting that the commitment to the account state was updated correctly. The network can verify the correctness of the transition without knowing the details of an off-chain account’s state.

Having on-chain and off-chain account data combined with the ability to prove state changes locally or by the network leaves us with flexible transaction modes.

At DevCon 6, in Bogotá, Colombia, Miden co-founder Bobbin Threadbare spoke about flexible transaction modes and how our state model is designed to build a decentralized scalable rollup.

Bobbin Bogota

Paradigm shifts

Miden aims to unlock new use cases and applications. The prevailing idea is that everything in a blockchain must be transparent to be verifiable. But in Miden, actors can prove correctness and don’t need to be transparent.

Miden combines core concepts of Ethereum, Bitcoin, and modern concurrent databases, all powered by the trustless security of ZK proofs. What will emerge are the dimensions of an elastic, general-purpose ZK rollup that is optimized for high-throughput, computation-heavy applications where privacy is also a priority.

Our architectural foundations are set to enable enormous throughput, low fees and privacy in future iterations. However, like all rollups, we will start with training wheels. We will communicate our roadmap soon.

More blogs

>> Explore more articles