Build Your First Token

Create a fixed-supply ERC-20 in a sandbox, transfer it, and check who controls the supply.

1. Write the specification

The classroom needs 1,000 transferable workshop credits. The deployer receives them once. The model gives no administrator a mint, pause or upgrade function. Write down who starts with the supply before deciding whether those rules fit your project.

2. Compile the example

Open Remix, create WorkshopToken.sol and paste the code. Select compiler 0.8.20 and compile. The pinned dependency makes it possible for a second learner to inspect the same implementation.

// SPDX-License-Identifier: MIT
pragma solidity ^0.8.20;
import "@openzeppelin/contracts@5.0.2/token/ERC20/ERC20.sol";

contract WorkshopToken is ERC20 {
    constructor() ERC20("Workshop Token", "LAB") {
        _mint(msg.sender, 1000 * 10 ** decimals());
    }
}

3. Deploy and test

Under Deploy & Run, choose a Remix VM environment, select WorkshopToken, and deploy. Copy the contract address and first account address. Call totalSupply and balanceOf. With 18 decimals, 1,000 LAB appears as 1000000000000000000000 raw units. Transfer 1000000000000000000 units to a second VM account. Check that it now holds 1 LAB and the first holds 999.

4. Reproduce on a public test network

To produce a shareable record, use a dedicated test wallet on Sepolia, obtain test ETH, select the browser-wallet environment in Remix and confirm the network before deploying. Record the deployment transaction and verify the source with the same compiler and settings. A local VM address alone cannot identify a public deployment.

Complete the Workshop Token File →. Sources: OpenZeppelin ERC-20 · Remix deployment guide.