Lesson 1 — What Is Vara.eth?

This course walks through the complete lifecycle of a real program on Vara.eth, from source code to on-chain interaction. You are not writing business logic from scratch here; the program already exists. The goal is to understand how it works and how to bring it to life on Ethereum.

The program is called One of Us. It stores Ethereum addresses of members. No duplicates. Anyone can check how many members exist. Simple logic, real chain behavior.

How Vara.eth differs

Vara.eth is not another L2. It does not produce its own blocks and does not require bridging. It adds a high-performance execution layer to Ethereum:

WASM program execution happens off-chain on decentralized Executors.
State is anchored to Ethereum L1 via Router contract.
Users can interact in two ways:
- Classic path: Ethereum wallet -> Mirror contract on L1.
- Injected path: direct message to validators for fast pre-confirmation.

Three key properties

Reverse gas: program pays execution with wVARA.
Parallel execution: isolated actor model per program.
Pre-confirmations: sub-second feedback on injected path.

You will run every lifecycle step against live-style flow in this tutorial.

Next Next

Meet Your Program

Vara.eth Architecture

ETHEREUM L1
  [ Mirror Contract ] --> [ Router Contract ]
          ^                      ^
          |                      |
          +-------- Executors ----+
                     (off-chain)

Program: One of Us (WASM)
- own isolated state
- message queue
- actor execution model

Two interaction paths:
A) Classic: Wallet -> Mirror.sendMessage() -> L1 -> Executors
B) Injected: SDK -> Validators directly (pre-confirmation)