Quickstart
Welcome to the Base quickstart guide! In this walkthrough, we'll create a simple onchain app from start to finish. Whether you're a seasoned developer or just starting out, this guide has got you covered.
What You'll Achieve
By the end of this quickstart, you'll have built an onchain app by:
- Configuring your development environment
- Deploying your smart contracts to Base
- Interacting with your deployed contracts from the frontend
Our simple app will be an onchain tally app which lets you add to a total tally, stored onchain, by pressing a button.
Set Up Your Development Environment
Bootstrap with OnchainKit
OnchainKit is a library of ready-to-use React components and Typescript utilities for building onchain apps. Run the following command in your terminal and follow the prompts to bootstrap your project.
npm create onchain@latest
The prompots will ask you for a CDP API Key which you can get here.
Once you've gone through the prompts, you'll have a new project directory with a basic OnchainKit app. Run the following to see it live.
cd my-onchainkit-app
npm install
npm run dev
You should see the following screen.

Once we've deployed our contracts, we'll add a button that lets us interact with our contracts.
Install and initialize Foundry
The total tally will be stored onchain in a smart contract. We'll use the Foundry framework to deploy our contract to the Base Sepolia testnet.
- Create a new "contracts" folder in the root of your project
mkdir contracts && cd contracts
- Install and initialize Foundry
curl -L https://foundry.paradigm.xyz | bash
foundryup
forge init --no-git
Open the project and find the Counter.sol
contract file in the /contracts/src
folder. You'll find the simple logic for our tally app.
Configure Foundry with Base
To deploy your smart contracts to Base, you need two key components:
- A node connection to interact with the Base network
- A funded private key to deploy the contract
Let's set up both of these:
- Create a
.env
file in yourcontracts
directory and add the Base and Base Sepolia RPC URLs
BASE_RPC_URL="https://mainnet.base.org"
BASE_SEPOLIA_RPC_URL="https://sepolia.base.org"
-Load your environment variables
source .env
Secure your private key
A private key with testnet funds is required to deploy the contract. You can generate a fresh private key here.
- Store your private key in Foundry's secure keystore
cast wallet import deployer --interactive
- When prompted enter your private key and a password.
Your private key is stored in ~/.foundry/keystores
which is not tracked by git.
Deploy Your Contracts
Now that your environment is set up, let's deploy your contracts to Base Sepolia. The foundry project provides a deploy script that will deploy the Counter.sol contract.
Run the deploy script
- Use the following command to compile and deploy your contract
forge create ./src/Counter.sol:Counter --rpc-url $BASE_SEPOLIA_RPC_URL --account deployer
Note the format of the contract being deployed is <contract-path>:<contract-name>
.
Save the contract address
After successful deployment, the transaction hash will be printed to the console output
Copy the deployed contract address and add it to your .env
file
COUNTER_CONTRACT_ADDRESS="0x..."
Load the new environment variable
source .env
Verify Your Deployment
To ensure your contract was deployed successfully:
- Check the transaction on Sepolia Basescan.
- Use the
cast
command to interact with your deployed contract from the command line
cast call $COUNTER_CONTRACT_ADDRESS "number()(uint256)" --rpc-url $BASE_SEPOLIA_RPC_URL
This will return the initial value of the Counter contract's number
storage variable, which will be 0
.
Now lets connect the frontend to interact with your recently deployed contract.
Interacting with your contract
To interact with the smart contract logic, we need to submit an onchain transaction. We can do this easily with the TransactionDefault
component. This is a simplified version of the Transaction
component, designed to streamline the integration process. Instead of manually defining each subcomponent and prop, we can use this shorthand version which renders our suggested implementation of the component and includes the TransactionButton
and TransactionToast
components.
Add the TransactionDefault
component
Lets add the TransactionDefault
component to our page.tsx
file. Delete the existing content in the main
tag and replace it with the snippet below.
import { TransactionDefault } from '@coinbase/onchainkit/transaction';
import { calls } from '@/calls';
<main className="flex flex-grow items-center justify-center">
<div className="w-full max-w-4xl p-4">
<div className="mx-auto mb-6 w-1/3">
<TransactionDefault calls={calls} />
</div>
</div>
</main>;
Defining the contract calls
In the previous code snippet, you'll see we imported calls
from the calls.ts
file. This file provides the details needed to interact with our contract and call the increment
function. Create a new calls.ts
file in the same folder as your page.tsx
file and add the following code.
const counterContractAddress = '0x...'; // add your contract address here
const counterContractAbi = [
{
type: 'function',
name: 'increment',
inputs: [],
outputs: [],
stateMutability: 'nonpayable',
},
] as const;
export const calls = [
{
address: counterContractAddress,
abi: counterContractAbi,
functionName: 'increment',
args: [],
},
];
Testing the component
Now, when you connect a wallet and click on the Transact
button and approve the transaction, it will increment the tally onchain by one.
We can verify that the onchain count took place onchain by once again using cast
to call the number
function on our contract.
cast call $COUNTER_CONTRACT_ADDRESS "number()(uint256)" --rpc-url $BASE_SEPOLIA_RPC_URL
If the transaction was successful, the tally should have incremented by one!
We now have a working onchain tally app! While the example is simple, it illustrates the end to end process of building on onchain app. We:
- Configured a project with frontend and onchain infrastructure
- Deployed a smart contract to Base Sepolia
- Interacted with the contract from the frontend
Further Improvements
This is just the beginning. There are many ways we can improve upon this app. For example, we could:
- Make the
increment
transaction gasless by integrating with Paymaster - Improve the wallet connection and sign up flow with the WalletModal component
- Add onchain Identity so we know who added the most recent tally