Open protocol

Don’t Panic
This is infrastructure.

42 Chain is blockchain infrastructure. An improbabilistic distributed ledger.

~2 sper block
1 blockto be final
IBC v2connection to other networks
EVMstandard tools
Apache 2.0open source

01 — The engine

Five parts. One ledger.

Each one carries part of the agreement among the people who use the ledger.

01 · Consensus

Agrees on each block.

Validators propose and sign blocks. With more than two thirds of the voting power, the block is confirmed and final.

  • Finality in one block.
  • Tolerates faults of less than a third of the voting power.
  • Without a majority, the network halts rather than take risks.
How a block is agreed →

02 · Execution

Runs the contracts.

Contracts run on the Ethereum Virtual Machine (EVM). Every node reaches exactly the same result.

  • Solidity and Vyper, without code changes.
  • Hardhat, Foundry, Viem and EVM wallets.
  • The network's own functions available from contracts.
How the rules run →

03 · Fees

Measures and pays for the work.

Every transaction pays a fee proportional to the work it requires, in the native unit: Improbability.

  • Public rules: the cost is known before sending.
  • Someone else can pay the fee for whoever signs.
  • Units in drops and cups.
How the work is paid →

04 · Interoperability

Connects to other networks.

With IBC, each network checks for itself, with cryptographic proofs, what happened on the other. Nobody holds the units in transit.

  • IBC, versions 1 and 2.
  • No trusted intermediaries.
  • Data and units across networks.
How networks connect →

05 · Governance

Decides the changes.

Changes are proposed and voted on the chain. Each vote weighs according to the units in staking.

  • Proposals recorded on the chain.
  • Public quorum, threshold and veto.
  • The network applies what is approved.
How changes are decided →

02 — Use cases

What it is for, in practice.

See the use cases (in Spanish) →

When several people need the same data and the same rules, the ledger does not have to sit with any one of them. Each person can keep a copy, any tampering is visible and anyone can check the result. Three examples:

Two people exchanging an object

Agreements

Agreements between strangers.

Two parties who do not know each other leave a record of an exchange. No platform has to custody or decide.

Generated image

Small group sharing a device

Memory

Collective memory.

Several people contribute the same fact. Anyone can audit the set and see if something changed.

Generated image

03 — For builders

Familiar tools.
Verifiable rules.

Contracts are written with standard languages and tools: Solidity, Hardhat, Foundry. An application that already works on an EVM-compatible network works here without changing its code.

04 — How it is organized

Each role, in different hands.

The code, the operation of the network and the decisions about its rules are separate, and each part can be checked: the code in a public repository, operation and decisions on the chain itself.

Code contributorsPropose and review changes in a public repository.
Validators and node operatorsVerify every block and give access to the network.
On-chain governanceValidators and those who delegate to them vote on what changes and when.
BuildersOffer applications and services on the network, and each is responsible for their own.
How it is organized (in Spanish) →

05 — The name

Why 42?

In Douglas Adams's novel, 42 is the answer to the great question of life, the universe and everything. The answer is exact, but the meaning comes from those who ask. The protocol works the same way: it offers precise rules, and what is built with them is decided by those who use it.

Why 42 (in Spanish) →

06 — Where to start

Choose your way in.

Shared infrastructure, rules in plain sight.