Skip to main content

Local testnet development flow

This guide describes the end-to-end flow for developing with a local testnet.

CLI from source, not from GitHub

This guide is not correct if you're using the aptos CLI from a GitHub release or from cargo install, only if you build it yourself from aptos-core as described below.

Please read this guide carefully. This guide specifically addresses the local testnet development flow. This flow will not work if you're building against devnet.

Run a local testnet from aptos-core

Pull and go into aptos-core:

git clone ~/aptos-core && cd ~/aptos-core

Run a local testnet:

cargo run -p aptos -- node run-local-testnet --with-faucet --faucet-port 8081 --force-restart --assume-yes

You may add the --release flag after cargo run if you want to build a release version of the CLI for running the local testnet.

You are now running a local testnet built from aptos-core main.

Typescript: Use the SDK from aptos-core

Important: With this development flow, it is essential that you do not use the SDK from npmjs. Instead, you must use the same SDK as the aptos CLI is built from, which we describe below.

This guide assumes you have done the previous local testnet step. We also assume you have yarn installed.

First, go into aptos-core and build the SDK:

cd ~/aptos-core/ecosystem/typescript/sdk
yarn install
yarn build

Make a new project if you don't have one already:

mkdir ~/project && cd ~/project
yarn init

Make your project target the SDK from your local aptos-core:

yarn add ../aptos-core/ecosystem/typescript/sdk

You could also use the absolute path, e.g. /home/daniel/aptos-core/ecosystem/typescript/sdk.

Install everything:

yarn install

Now you're set up! You should see in package.json that your project targets your local aptos-core:

"name": "project",
"version": "1.0.0",
"main": "index.js",
"license": "MIT",
"dependencies": {
"aptos": "../a/core/ecosystem/typescript/sdk/"

This way your local testnet and the SDK you're using match, meaning you won't see any compatibility issues.

Now you can use the Aptos module like this in your code:

import { AptosClient, AptosAccount, FaucetClient } from "aptos";

const NODE_URL = "";
const FAUCET_URL = "";

(async () => {
const client = new AptosClient(NODE_URL);
const faucetClient = new FaucetClient(NODE_URL, FAUCET_URL);

Note: See that this code builds clients that talk to your local testnet, not devnet.