Generate wallet-ready ERC method bindings with per-function files and selector registry updates.
npx skills add https://github.com/niconiahi/ethernauta --skill erc
Please help me install this Agent Skill. Skill: erc Source: https://github.com/niconiahi/ethernauta/tree/main/skills/erc Command: npx skills add https://github.com/niconiahi/ethernauta --skill erc
It solves the problem of adding new Ethereum Request for Comment (ERC) contract standards to Ethernauta without breaking tree-shaking, ABI encoding/decoding, or wallet confirmation behavior.
packages/erc/src/<n>/ layout so generated methods are importable as @ethernauta/erc/<n> after build.<METHOD>_SIGNATURE sidecar so the wallet can render human-readable confirmations based on selector matching.Callable<T> for view/pure methods and Signable<Bytes> for state-changing methods, matching the wallet’s signing flow.union(tuple, object) and Valibot parsing so callers can use either tuple or object argument styles safely.registry.generated.ts rather than editing it by hand.Ask the skill to help you add a new standard by creating packages/erc/src/<n>/IERC<n>.abi.json, generating one method file per ABI function with the required <METHOD>_SIGNATURE, wiring exports through methods/index.ts and <n>/index.ts, writing a behavioral <n>.test.ts, regenerating the selector registry, then validating the build output.
High-intent search queries and answers about installing and using this skill.
To generate wallet-ready ERC bindings, define the required folder structure under `packages/erc/src/<n>/` and create per-function files. This produces `Callable<T>` for view methods and `Signable<Bytes>` for state-changing methods, ensuring ABI-correct encoding and wallet confirmations work.
You need a separate `<METHOD>_SIGNATURE` export for each ERC method file to enable wallet confirmations. The wallet uses this sidecar to render human-readable confirmations by matching the function selector, ensuring users know exactly what state-changing transaction they are signing.
To keep ERC method bundles minimal, the system uses a one-generated-method-per-file rule. This per-function tree-shakable structure ensures you only import the specific methods you need from `@ethernauta/erc/<n>`, preventing unnecessary code from bloating your final bundle.
Yes, you can use either tuple or object argument styles safely for smart contract parameters. The system standardizes method inputs via a `union(tuple, object)` convention and uses Valibot parsing to validate the parameters, ensuring ABI-correct encoding and decoding regardless of the argument style.
To make new ERC methods discoverable without manual edits, regenerate the selector registry. The system automatically updates `registry.generated.ts` during the build process, ensuring all newly generated method files are correctly indexed and discoverable without manual intervention.
NethereumProvide typed C#/.NET services for interacting with standard blockchain contracts.
openharmonyinsightAutomate OpenHarmony unit and fuzz test generation, build, deploy, and execution via hdc.
alexturpinEnforce correct Zod import conventions for tree-shaking in JavaScript and TypeScript projects.
trustwalletDevelop and integrate modular ERC-4337 smart contract wallets using the EIP-2535 Diamond standard.