A beginner-friendly, end-to-end template for tokenizing real-world assets (RWAs) on Algorand testnet using Algorand Standard Assets (ASAs).
This repository is designed for:
- Founders exploring RWA proofs-of-concept
- Builders new to Algorand
- Hackathons, demos, workshops, and early product experiments
No prior blockchain or smart contract experience required. By the end, you'll have a working tokenized asset with a real Algorand Asset ID.
- ✅ Complete Algorand starter app (user interface + backend)
- ✅ Simple flow to create and send Algorand assets (tokens)
- ✅ Easy sign-in options (Email login + wallet login)
- ✅ Ready to test on Algorand TestNet
- ✅ Quick one-step setup (no complex installation)
- ✅ Can be deployed online (Vercel), with analytics included
This template covers the blockchain “token” part of real-world asset (RWA) tokenization:
- Each real-world asset is represented as an token on the Algorand blockchain (ASA)
- Ownership, supply and transfers are tracked on the blockchain
- The real-world paperwork (documents, custody, legal structure) stays off the blockchain
⚠️ This is a technical proof-of-concept template, not legal or financial advice.
Option 1: GitHub Codespaces (Recommended)
This is the fastest and easiest way to run the project.
Click Fork (top-right of this page) to create your own copy.
Forking.mp4
- Go to your forked repository
- Click Code → Codespaces → Create codespace
- Wait for the environment to load and enter the workspace
When the Codespace loads, you may see an "Open Workspace?" popup in the bottom-right — click Yes.
Or manually enter it like below:
In the Codespaces terminal, run:
bash setup.shThis script will:
- Install everything needed
- Set up the required files automatically
- Start the app for you (open the website)
👉 When it finishes, a web app link will open automatically in Codespaces.
⚠️ You do not need to manually create.envfiles for the frontend.
To enable email/social login, you must configure Web3Auth in your Web3Auth dashboard first.
- Go to the Web3Auth Dashboard
- Create a new project
- Copy your Client ID
Open the file:
frontend/.env
Add (or update) the following value:
VITE_WEB3AUTH_CLIENT_ID=YOUR_CLIENT_ID_HERESave the file and restart the frontend if it's already running.
Next, go to your Web3Auth Dashboard. Inside your project settings, find Domains and paste your website link there, just like in the screenshot below. Click Add URL.
This step is very important — it allows the Web3Auth wallet to work properly on your website.
Note* Make sure you pick the network to work on is Algorand Testnet on the Web3 Auth Dashboard!
If you want to create NFTs (with images/metadata), you’ll need to set up a small backend service for uploads.
⚠️ Only do this if you plan to mint NFTs and upload metadata.
projects/TokenizeRWATemplate-contracts/NFT_mint_server
- Go to https://app.pinata.cloud/developers/api-keys
- Create a new API key
- Copy the JWT token
Open:
projects/TokenizeRWATemplate-contracts/NFT_mint_server/.env
Add:
PINATA_JWT=YOUR_PINATA_JWT_HERESave the file.
After adding your Pinata JWT, start the NFT mint backend server.
Navigate to the server folder:
projects/TokenizeRWATemplate-contracts/NFT_mint_server
Run the server:
npm run dev
Important (Codespaces / Remote Environments)
After you run setup.sh once, you have two simple options each time you reopen your Codespace - so you don’t need to run the setup again:
cd frontend
npm run devYou can also start the frontend directly using the GitHub Codespaces UI, which is useful for demos and workshops.
GitHub Codespaces is available on free accounts, but it includes up to 60 hours per month. To avoid losing your work, commit and sync your changes regularly (as shown in the demo video) so everything is saved to your forked repository.
A “commit” is like hitting save with a short note, it records your changes in Git so you can keep them and come back to them later.
Screen.Recording.2025-08-14.at.13.38.44.mov
- ✅ The app setup is mostly automatic
- ✅ You must add a Web3Auth Client ID (to use the app/login)
- ✅ Pinata is optional (only for NFT images/metadata)
- Your Web3Auth Client ID is missing
- You don’t have TestNet ALGO or USDC in your wallet
This template walks you through the basic steps to represent a real-world asset as a token on the Algorand blockchain (ASA).
-
Connect with Algorand
Use Pera, Defly, Lute, or Web3Auth to interact with the app. -
Define your asset parameters
Choose the asset name, unit name, total supply, decimals, and optional metadata. -
Create an Algorand Standard Asset (ASA)
The asset is created on-chain and represents your real-world asset digitally. -
Receive an Asset ID
Algorand assigns a unique Asset ID, which becomes the on-chain identifier for your tokenized asset. -
Use or extend the token as your RWA representation
The ASA can now be transferred, held, integrated into apps, or extended with additional logic.
ASAs support advanced management features commonly used in RWA and compliance-focused setups:
| Role | Description |
|---|---|
| Manager | Can modify asset configuration |
| Reserve | Holds non-circulating supply |
| Freeze | Can freeze/unfreeze accounts |
| Clawback | Can revoke assets from accounts |
These controls are optional and depend on your use case and trust model.
This repository is provided for educational and experimental purposes only.
It does not constitute legal, financial, or investment advice.
Below are videos on:
- How to connect to TestNet on Pera
- How to use the Algo Dispenser
- How to use the USDC Dispenser