2.9.26
Released 2 Nov 2026
WaveClamp 2.9.26 is a Windows agent that reads your Solidity files, runs your own compile and test commands on a test network and shows each edit as a diff you accept or reject.
MultiTokenMinimal.sol14 linesbalanceOf1 matchMultiTokenMinimal.sol+3 linesyour compile commandexit 0your test commandexit 0Released 2 Nov 2026
Installer for Windows 10/11
Single .exe build
App interface languages
Auto-run, Ask first, Plan only
No sign-up to run the app
The ERC1155 standard lets one contract manage many token types, each identified by a numeric id. That suits game items. WaveClamp reads your Solidity files, runs your own compile and test commands on a local chain or a test network, and shows each edit as a diff you accept or reject. Version 2.9.26 runs on Windows 10/11.
You wrote an item contract for a game and want to know who can mint tokens. The agent runs glob to list your .sol files, uses grep to find every call to _mint and _mintBatch, and opens the surrounding functions with read_file. It then lists each minting function that has no access check, with its line number. Review that first. With Ask first selected, edit_file pauses on a diff before it adds a check, and Shell runs your test command so you read the real exit code of the ERC-1155 tests before you accept anything.
glob **/*.sol → 3 files
grep _mintBatch → 2 matches
read_file GameItems.sol → 62 lines
edit_file GameItems.sol → +4 linesA venue wants tickets that are unique seats and also shared passes, and you must pick a standard. In Plan only the agent writes the research steps and runs nothing, so you read them first. The choice is yours. After you switch to Ask first, web_search finds the public EIP text, http_get downloads one page, and write_file saves your notes. ERC-721 gives one contract one collection of unique tokens, while the multi-token standard holds unique, fungible and semi-fungible types together. A sketch of the ERC 1155 Solidity interface goes into the same notes file, and you review it before any code is written.
web_search EIP-1155 multi token standard → 5 results
http_get eips page → saved
write_file compare-standards.md → savedPlayers need to move several item types in one transaction. The agent opens the contract with read_file, uses edit_file to add safeBatchTransferFrom and shows the diff, then Shell runs your compile command and your test command. Read the exit code. If a token transaction and a balance are not aligning in a test, grep for TransferSingle and TransferBatch shows where the events are emitted, so you can compare them with the balances. A receiving contract must implement onERC1155Received and onERC1155BatchReceived or the transfer is rejected, and you review each fix as a diff before saving it.
Each token id needs a metadata file that wallets can read. The agent uses write_file to create the JSON, edit_file to set the uri(id) pattern in the contract and read_file to check the result. Clients replace {id} in that pattern with the token id in lowercase hexadecimal, padded to 64 characters, so one pattern serves every id. Bounded storage for ephemeral tokens is an interesting research topic, yet a first contract only needs one JSON file per id. The pattern is short. Shell then runs your compile command, and you accept the diff once the file names match the padded ids.
A chat only describes. WaveClamp 2.9.26 runs the steps itself and puts each result on a card, so you review real output instead of a description of it.
| Typical chat assistant | WaveClamp | |
|---|---|---|
| Actions | Describes commands that you must run yourself | Calls the tool and shows the card with its result |
| Files | Pastes code into the chat for you to copy | Edits your .sol files and shows a diff |
| Results | Says what should happen when you run it | Reports the real exit code of your command |
| Review | You judge the code by eye | Ask first shows a diff before a change is saved |
Beginners who finished a Solidity course will find the standard easier to read with an agent beside them. Start small. Ask it to explain balanceOf(account, id), then check the answer against the contract, because a no code ERC20 deployment hides the file from you while WaveClamp keeps it open and shows every edit as a diff.
Game developers who want swords, potions and keys in one contract use it to draft the item set, add batch transfers and write tests for balances and events. Tests matter most here. The agent runs your test command on a local chain or a test network, and the coins there have no value, which suits practice.
Practitioners who review contracts for a living or for a team compare designs before any code is written. An ERC 721 smart contract gives each token its own owner, while the multi-token standard defines 4 events, TransferSingle, TransferBatch, ApprovalForAll and URI, that a review can check one by one. Run the checks yourself.
ERC-1155 is the Ethereum multi-token standard, written EIP-1155, where one contract manages many token types at once and each type has a numeric id and can be fungible, non-fungible or semi-fungible. Picture a game. WaveClamp helps you write, edit and test such a Solidity file.
Yes, mirazcode.com is the official WaveClamp website. Download the setup program here, compare its SHA-256 checksum with the published manifest, and run it only after the two match. Check the hash first. The installer is not code-signed yet, so Windows SmartScreen may warn, and questions go through the Send feedback button inside the app.
An ERC-721 contract is a Solidity contract in which every token is unique and has exactly one owner, unlike the multi-token standard, where one contract holds many token types. It suits one-of-a-kind items. WaveClamp can read both kinds of file, compare their functions and write tests for either one on a local chain or a test network.
No. WaveClamp is meant for learning and for testing on a local chain or a test network, whose coins have no value. A deployed contract cannot be changed, so get an independent security review before any real-value use. The agent gives no financial advice and does not replace a review.
No. Never put private keys or seed phrases in files, chat or code, because the agent reads files in the working folder and prompts go to the model endpoint you picked. Use throwaway test accounts instead. Anything you paste into a file can reach a cloud model if the agent reads it.
A cloud AI provider through a standard API endpoint, a model running on your PC, or the built-in model that is ready to use without your own endpoint. Pick whichever fits. The Test button shows the response time and the context window. With a cloud model, prompt text and any file text the agent reads go to that provider, while a local model keeps everything on your PC.
Yes. The agent runs the tools itself, and every action appears in the chat as a card with its real result. In Auto-run it acts at once, in Ask first it pauses before actions that change something, and in Plan only it writes the steps and runs nothing. You review each diff before accepting it.
Download version 2.9.26 for Windows, connect a model and point the chat at the folder with your Solidity files, then pick Ask first so every edit arrives as a diff. Begin on a test network.
Download WaveClamp for Windows ↗Every page of this website is available in 20 languages, while the app interface itself has 13.
What the agent can do ↗ Cloud, local or built-in model ↗ Add minting step by step ↗ Download the setup program ↗ Questions and answers ↗ Privacy and data handling ↗