What happened to Libertas?

Libertas (V1 network) is the V1 testnet and is running today. V2 starts from a new genesis. Balances and names carry over by snapshot. See /v2/.

Status Virtus (V2 testnet) opens in Phase 1.

Build On Revolution.

Q: What does the Revolution SDK cover?

Identity: resolve names and request scoped proofs from RNS credentials. Staking: create a pool, set a creator fee, define tiers, read stake positions. Network data: blocks, transactions, proofs and verifying node status over JSON-RPC.

One SDK, standard Ethereum tooling, and a public testnet that opens with V2.

Start the quickstart

quickstart.sh bash

npm install @revolution/sdk

# Virtus (V2 testnet) values publish in Phase 1
export REVO_RPC_URL="<published at Virtus launch>"
export REVO_CHAIN_ID="<published at Virtus launch>"

Quickstart

Connect in three steps.

Network values publish when Virtus (V2 testnet) opens in Phase 1. The SDK calls below work against them from day one.

Install the SDK

One package covers identity, staking and settlement.

Point at Virtus

Set the RPC URL and chain ID for Virtus (V2 testnet).

Resolve a name

Resolve a .revo Nomen (name) and start building.

client.ts typescript

import { Revolution } from "@revolution/sdk";

const revo = new Revolution({ network: "virtus" });

// Nomen (name): resolve a .revo name
const nomen = await revo.nomen.resolve("rob.revo");

SDKs and APIs

What is covered.

SDK

Reward Pools Create a pool, set a creator fee, define tiers, read stake positions.

SDK

Identity Request scoped proofs from RNS credentials and enforce policy in your app.

API

Network data Blocks, transactions, proofs and verifying node status over JSON-RPC.

Network parameters
Parameter	Value
Network	Virtus (V2 testnet)
Status	Opens in Phase 1
RPC URL	Published at launch
Chain ID	Published at launch
Explorer	Published at launch

Build on V2

What changes for builders.

ERC-4337 smart accounts at the canonical EntryPoint v0.8.
Free cornerstone calls through the network paymaster.
SDK modules for the identity stack, each with a plain-English alias.

SDK modules
Module	Alias	Term
revo.nomen	revo.names	Nomen (name)
revo.sigillum	revo.identity	Sigillum (verified identity)
revo.potestas	revo.permissions	Potestas (permissions)
revo.mandatum	revo.delegation	Mandatum (delegated authority)
revo.agens	revo.agents	Agens (agent)

Node operators

Operate a verifying node.

Verifying nodes are approved by governance. They run an external node, co-sign batches and send heartbeats. Applications open with Virtus (V2 testnet).

Apply

Hardware requirements

Minimum CPU, memory, disk, and bandwidth publish with the operator application in Phase 1. Apply now and the team will send the spec when it is final.

Contracts

Deployed addresses.

Addresses publish when Virtus (V2 testnet) contracts are verified.

Virtus (V2 testnet)
Contract	Address
Reward Pool factory	Published at launch
REVO token	Published at launch
RNS registry	Published at launch
Settlement bridge	Published at launch

Specification

Whitepaper V2 The chain, accounts, identity, staking, ACommerce, token economics, migration and roadmap in full. Version 2.0. Read Whitepaper V2

Get Virtus launch details first.

RPC endpoints, chain ID, explorer, and contract addresses go to builders on the list before they go public.

Notify me Whitepaper V2

V2 is coming.

Tell us what you want to build.