Kevin Ingersoll

would be nice if the deployer supported something like ``` DEPLOYER_PRIVATE_KEY_31337=... DEPLOYER_PRIVATE_KEY_690=... DEPLOYER_PRIVATE_KEY_1=... ``` to set up per-chain accounts for deploying (can always still fall back to `PRIVATE_KEY`)

- [x] `CreateStoreResult` -> `CreateStashResult` or maybe `ExtendedStash` - [ ] `getRecord` doesn't account for namespace/table not existing, can runtime error - [ ] `getRecord`, `getTable` should return `| undefined`...

add `disabled` to table codegen input/output

1

I want to be able to define client-only tables in my MUD config that aren't deployed or codegen'ed

this sort of error is annoying for first time users and hard to copy inside mprocs, so we could automate this away ``` [MUDError]: Missing PRIVATE_KEY environment variable. Run 'echo...

``` running "forge build" Nothing to compile (node:36669) ExperimentalWarning: Importing JSON modules is an experimental feature and might change at any time (Use `node --trace-warnings ...` to show where the...

The `observer` sends a `ping` event on an interval. We could use this on the Observe page to detect presence of a connected app and, when not connected, display instructions...

currently not possible or very nice to deploy with e.g. Safe wondering if we could 1) deploy a world 2) register temporary "deploy signer" 3) deploy the rest

follow up of https://github.com/latticexyz/mud/pull/3131 we now have two methods of getting contract artifacts and should consolidate on `findContractArtifacts` https://github.com/latticexyz/mud/blob/main/packages/world/ts/node/findContractArtifacts.ts

follow up of https://github.com/latticexyz/mud/pull/3131