This week, we added the ability to sign up to Walnut using a GitHub Account.
This week, we built an automation that allows our Contract Verification Service to automatically support new Cairo versions as soon as they are released. No more "unsupported Cairo version" messages during smart contract verification on Starknet!
2.9.1 and 2.9.2.3 as the default option.This week, we focused on bug fixing. And we also extended our Contract Verification service to support Cairo 2.8.5.
execute account function when it fails due to an undeployed contract. The transaction status now shows REVERTED with a clear error indicator.sierra-replace-ids to the Scarb.toml configuration, ensuring sierra_program_debug_info is included in the contract class during the build process.
This week, we streamlined loop handling in the call trace by removing loops and ensuring function calls within them are displayed at the correct level.
We've enhanced the contract verification process by enabling users to verify contracts using only the source code, simplifying the process and making it more user-friendly.
license-file field in Scarb.toml caused verification to fail.
We're excited to introduce a brand new Memory Window in the Debugger to display function call arguments and results.
In this release, we've introduced a new Class Page that displays details about the class, including the Class Hash, the list of networks where the class is declared, and the associated source code.
ContractState function argument in the Call Trace, enabling users to explore these values.
This week, we simplified the Call Trace by removing argument and result namespaces and skipping system arguments. This reduces visual complexity, making it easier for users to navigate function calls!
b — Step Backn — Step Intoo — Step Over
We finally added the 'Step Over' button, one of the most requested features from our early users. It speeds up the debugging experience by allowing developers to skip over functions and focus on the main logic, saving time and reducing the need to manually step through each line in deeply nested code.
__validate__ Account call, to better express Starknet's Account Abstraction model.
This week, we updated the homepage to enable users to simulate transactions and configure custom networks directly, without opening a tranasction first.
This week, we added a search feature to the call trace, allowing developers to search by contract address, contract name, entrypoint, or any Cairo function name.
In the latest release, we added a footer to search results that shows the networks being queried, making it easier to recognize when a custom network should be set if the search doesn't return expected results.
Last week, we introduced several updates to enhance the Call Trace feature and improve overall product quality.
In the latest release, we introduced support for verifying multiple classes in a single request. This improves the Class Verification user experience and boosts performance.
The step-by-step debugger now supports nested contract flows. When you reach a contract call in the source code, just hit “Next” to seamlessly move into the new contract and continue debugging.
This week we added support for debugging transactions on custom networks, a key request from DOJO on-chain game developers. Walnut now connects to any Starknet network via custom RPC URLs, with full support for debugging, simulating, and verifying smart contracts. Next week, we will pilot custom networks with hosted Slot instances in New York, meeting DOJO game developers and demonstrating Walnut.
In the latest release, we moved contract class verification to run in the background, making the service more resilient when verifying larger contracts or multiple contracts.
/v1/verification/{:id}/status. Try it here.
In the latest release, we introduced highlighting for both Cairo attributes and Code snippets in the step-by-step debugger.
In the latest release, we introduced aggregated search, allowing users to search for transactions, contracts, or classes across all networks.
chain_id is available at /v1/verify/. This is an important prerequisite for making Walnut work with fully on-chain games deployed to appchains like Slot.2.7.0.
In the latest release, we improved the debugging experience by allowing switching between source files in the debug window.
In the latest release, we focused on enhancing the information box on the transaction page. We now display the transaction type, timestamp, and transaction version.
In the latest release, we focused on improving the call trace. Concretely, we worked on displaying contract calls within internal function calls. In the screenshot above, you can see the IVerificationHelper.calculation_proof correctly placed right after the internal function call IVerificationHelperDispatcherImpl::calculation_proof.
In the latest release, we added full support for contract verification to Walnut. Developers can verify their contracts to get detailed call traces, step-by-step debugging, and execution mapping to the source code in the Cairo contracts.
In the latest release, we focused on displaying errors in the call trace.
Function arguments and return results are now visible in the step-by-step-debugger. In the screenshot above, the extract_age function returns a single result: 18.
Class ID. Available at the /{network_id}/classes/{class_id} endpoint. Try it here.
In the latest release, we have introduced the contract class verification API endpoint.
/verify endpoint for Cairo Smart Contract Verification.
In the latest release, we finally launched the first version of the step by step debugger. It comes with support for multiple contracts in the transaction, and moves the code execution accordingly.
In the latest release, we added support for displaying the corresponding Cairo source code for each call in the call trace.
In this release we added support for transaction simulations into Walnut. You can simulate a new transaction, or re-simulate an existing one.
In this release we added support for internal function calls in the call trace. After verifying contracts, the call trace presents calls to every Cairo function, and will also present details about each call's arugments and return values.
This is our first changelog message. We started building Walnut to make transaction debugging and simulations on Starknet easier. In the initial version, we plan the following features: