Web3 product / Case study
ABI Page Builder
Turn a smart contract ABI into an interface people can actually use.
- Who it serves
- EVM developers and teams that need to inspect and interact with contract functions without building a dedicated frontend.
- What I built
- I built ABI Page Builder to turn EVM contract ABIs into usable interfaces.
- Availability
- Web application
Web applicationEVM · Smart contract interfaces · Web application
CONTRACT INTERFACE DEMO
ABI → GENERATED INTERFACE
{
"name": "balanceOf",
"type": "function",
"stateMutability": "view"
}
{
"name": "balanceOf",
"type": "function",
"stateMutability": "view"
}
balanceOf()READ ONLY
Select a function and run the example.
Illustrative data · No wallet · No network requests
The problem
Interacting with a contract should not require building a frontend first. Developers need a way to inspect and call functions, including contracts without a convenient explorer interface.
How it works
- A contract address, network, and ABI become a function-based interface.
- Read functions can be called from the browser; transactions use a connected wallet.
- Custom RPC endpoints let users work beyond the built-in network list.
Engineering decisions
- Keep contract interaction separate from contract verification: an interface does not establish that a contract is trustworthy.
- Let the ABI describe inputs and functions instead of hand-building a UI for every contract.
The result
A web application for generating contract interfaces, with guides for common tasks.
Current status
Transaction success depends on the network, wallet, ABI, permissions, and contract state. The portfolio demonstration uses fixed sample data and sends no transactions.