Kevin Ingersoll
Kevin Ingersoll
I thought this pattern would be nice to simplify importing codegen things from one place, e.g. ```solidity import { Tables, ResourceIds, StoreHooks } from "./codegen/index.sol"; ``` but it turns out...
we should have some process to deploy + catalog deterministic mud contracts for major chains (maybe just starting with redstone+garnet) for each mud protocol version thinking about the case where...
If we expect folks to use/install examples, we should probably gitignore the lockfile. But we should make sure our tests, etc. don't depend on this lockfile for consistency.
(from https://github.com/latticexyz/mud/pull/2823#issuecomment-2111072372) ``` packages/store-sync test:ci: close timed out after 500ms packages/store-sync test:ci: Failed to terminate worker while running /home/runner/work/mud/mud/packages/store-sync/src/recs/recsStorage.test.ts. packages/store-sync test:ci: Tests closed successfully but something prevents Vite server from...
lots of new goodies in latest foundry-std might also fix https://github.com/latticexyz/mud/issues/2755 ?
we should turn off this setting in foundry.toml throughout: otherwise whitespace changes can change bytecode, which throws of deterministic deployment and verification
apparently broke for node 18.19 https://github.com/privatenumber/tsx/issues/421
most likely these will be from hosted providers and different per provider (alchemy, infura, quicknode, etc.) https://github.com/latticexyz/mud/blob/0f3e2e02b5114e08fe700c18326db76816ffad3c/packages/block-logs-stream/src/fetchLogs.ts#L82 https://github.com/latticexyz/mud/blob/0f3e2e02b5114e08fe700c18326db76816ffad3c/packages/block-logs-stream/src/fetchLogs.ts#L91
If we tag RPC requests and indexer requests with a header containing the MUD version, that'd let us keep track of usage for backwards compatibility, etc.
closes #2779 (couldn't push to their branch so re-opening here)