@ethernauta/cli

Philosophy

This module ships a CLI for working with ABIs in an Ethernauta codebase. Two subcommands:

• ethernauta abi — generate ready-to-use TypeScript methods from an ABI JSON or a Foundry artifact
• ethernauta registry — walk a directory of ABI JSONs and emit a 4-byte selector → method-metadata map (used by the wallet to surface human-readable function names)

Modules

• abi [NPM]
• chain [NPM]
• cli [NPM]
• core [NPM]
• crypto [NPM]
• eip [NPM]
• ens [NPM]
• erc [NPM]
• eth [NPM]
• react [NPM]
• transaction [NPM]
• transport [NPM]
• utils [NPM]
• wallet

API

ethernauta abi

Regenerate contract method TypeScript files from an ABI JSON or a Foundry artifact.

npx ethernauta abi --in abis/IERC20.abi.json --out app/methods

Each function in the ABI emits one file under <out>/methods/. View / pure functions emit Callable<T>; state-changing functions emit Signable<Bytes>. A barrel file at <out>/methods/index.ts re-exports everything.

A typical setup wires this into a package.json script so generated methods stay in sync with the contract:

{
  "scripts": {
    "regen:methods": "ethernauta abi --in contracts/out/MyContract.sol/MyContract.json --out app/generated/my-contract"
  }
}

Flags:

Flag	Description
--in	Path to a raw ABI JSON array or a Foundry artifact with an abi field
--out	Output directory; the generator writes <out>/methods/*.ts + a barrel file

ethernauta registry

Walk a directory for *.abi.json files and emit a single REGISTRY mapping 4-byte selectors to method metadata.

npx ethernauta registry --in src --out src/registry/registry.generated.ts

The registry is used by the wallet to verify and display function names for transactions whose call data carries an unknown selector.

Flags:

Flag	Description
--in	Directory walked recursively for *.abi.json files
--out	Output file path for the generated REGISTRY TypeScript module