yonada

feat(cli): generate system ABI's from World address

1

Adds a new MUD `generate-abi` command that generates an ABI for a given World by reading the onchain system registrations fixes https://github.com/latticexyz/mud/issues/2845

feat(cli): `mud init` command

1

The initial scaffolding for `mud init`, simply generating `worlds.json`, as https://github.com/latticexyz/mud/issues/2847 This allows projects that are extending an existing World to define what address they are interacting with. Later PR's...

feat(cli): generate mud config from world address

1

fixes https://github.com/latticexyz/mud/issues/2848

Given a system address, we can fetch its Solidity code from a verifier such as [Sourcify](https://sourcify.dev/). With the code, users can then run `mud build` to generate the system interface...

We can fetch the function definitions for a given system ID from the `FunctionSignatures` table and use them to codegen the system ABI. This can start as a helper function...

We can get all of a World's registered tables by reading `tableId`, `keySchema`, `valueSchema`, `abiEncodedKeyNames`, and `abiEncodedFieldNames` from the `Tables` table. Given the uncertainty of multi-namespace support and `mud init`...

Given a world address, we can get the deployment block number by fetching `HelloWorld` events from the RPC (the earliest one in case the world is a proxy).

feat(docs): add codesandbox to intro page

1

docs at https://mud-docs-git-yonadaaa-docs-sandbox-latticexyz.vercel.app/quick-start created from https://github.com/yonadaaa/my-project

chore(world): generate init system function signatures

2

Fixes https://github.com/latticexyz/mud/issues/2155

docs: onchain indices guide

1

https://mud-docs-git-yonadaaa-how-to-indices-latticexyz.vercel.app/guides/onchain-indices