AppLayer Engine is live for testing AI work rules · Being built
AppLayer

AppLayer Testnet

One chain.
Two ways to run code.

AppLayer runs standard EVM code and fast C++ programs on the same blockchain. Both use the same shared state, network checks, and block history.

See the testnet liveSee how it works

Is the testnet live?

Checking the testnet…

We ask the real testnet for this status. We do not show fake numbers.

See transactions and blocks ↗

Wallet settings

Add AppLayer to your wallet.

Add these settings to MetaMask or another EVM wallet. Check the public guide for the latest values.

TestnetAppLayer Testnet
RPC URLhttps://testnet-api.applayer.com/
Chain ID75338
CurrencyAPPL
EVM revisionShanghai
Explorertestnet-explorer.applayer.com ↗
DocumentationWallet setup guide ↗

What runs the chain

Six parts that keep AppLayer running.

01

Pick the next block maker

rdPoS picks one validator to make the next block, so two validators do not race to make it.

02

Run EVM or C++

EVMOne runs standard EVM code. AppLayer runs compiled C++ programs through its direct path.

03

One shared state

Accounts, balances, contracts, and saved program data all live in the same state.

04

All-or-nothing calls

AppLayer treats connected EVM and C++ calls as one job. It saves everything together or undoes everything.

05

Apps + network nodes

Wallets and apps use familiar JSON-RPC. Network nodes share transactions, make blocks, and stay in sync.

06

Save the history

Checked blocks save transactions, accounts, contracts, and events as a history that cannot be quietly changed.

How the engine works

Two code paths.
One saved result.

Every transaction reaches the same router. The contract address tells AppLayer to run EVM code or compiled C++.

PATH / EVMReady to test

EVM contracts

Deploy Solidity, Vyper, or any contract that compiles to EVM code. EVMOne runs it against AppLayer’s shared state.

  1. Ethereum-compatible transaction
  2. EVM bytecode dispatch
  3. EVMC host calls
  4. Atomic state transition
PATH / NATIVEReady to test

Fast C++ Programs

Run C++ contracts as compiled machine code while keeping familiar addresses, ABIs, and calls between EVM and C++.

  1. ABI-compatible contract call
  2. Native C++ dispatch
  3. Typed contract composition
  4. Save or undo

How a block is made

From signed request to saved history.

  1. 01

    Receive + check

    A node checks the signature, sender, balance, order number, duplicate protection, and waiting list.

  2. 02

    Share + order

    Nodes share valid transactions while rdPoS picks who makes the next block.

  3. 03

    Execute

    AppLayer sends each call to EVM or C++ and tracks every change.

  4. 04

    Save + check

    The whole block change is saved together and checked by the network.

  5. 05

    Store + show

    The checked block is stored and appears in apps and the public explorer.

What the speed numbers mean

Code speed is not network speed.

A local code test measures only the program. Public network speed also includes sharing, building, checking, agreeing, indexing, and saving.

01Transaction arrives
02Contract runs
03Change is proposed
04rdPoS checks the block
05Apps can read the block

Learn more

See exactly how it works.

ConsensusHow rdPoS picks a validator↗Node architectureState, network checks, storage, and syncing↗EVM runtimeHow EVM code runs↗SourceSee the BDK C++ code↗

Start with one real job

Build on the public testnet.

See the live testnet, connect a contract, and try both code paths.

Plan a pilot Try the testnet