Kevin Ingersoll
Kevin Ingersoll
creating system contracts eats up a lot of the gas used in a module install so we should figure out how to separate the system deploy, esp since we can...
probably want to deprecate everything < 2.0.6?
key name and field name could be bytes32 and then we could store them as `bytes32[]` instead of an abi encoded bytes of the original `string[]` also makes things like...
`WorldResourceId` uses `namespace` and `name` (with corresponding getters), but that makes it hard to work with the "name" (bytes30) part of Store's `ResourceId` because the names/methods would collide. Maybe we...
this is not a delegation module? https://github.com/latticexyz/mud/blob/c74a66474169d16a2ed4b7fd9046984d4ceabc3f/packages/world-modules/src/modules/callwithsignature/constants.sol#L8-L10
Right now it seems to default to the factory (the thing that created the world) and we transfer the root namespace to the factory caller, but not store/world namespaces. This...
so we can quickly get back to the the deploy tx of each contract would help in cases where we don't have [a manifest](#2491) but want to see e.g. what...
JSON representation of systems (can use abi-ts for strong types) that include system IDs and ABIs for strongly typed calls to systems (e.g. batch call) should also prob generate interfaces...
If a table has too many static fields (>14?), compiling can return "stack too deep" due to our `decodeStatic` implementation ```solidity /** * @notice Decode the tightly packed blob of...
right now the protocol version just looks at the store/world ABIs, but what's also important is the schema of internal tables (e.g. `store.Tables`) in case fields change, encodings change, etc.