Added an experimental option to help sync from load balanced RPCs, where nodes may be slightly out of sync, causing data inconsistencies while fetching logs.

To enable this, use INTERNAL__VALIDATE_BLOCK_RANGE=true environment variable when starting up any of the indexers. This requires RPC_HTTP_URL to also be set.

Note that using this option makes an additional call to eth_getBlockByNumber for each eth_getLogs call and expects the RPC to support batched calls.

feat(explorer): save searched namespace (#3470) (@latticexyz/explorer)

The context for the searched namespace and selected table is now preserved when reopening the table search and selection menu.

fix(store-sync): handle user ops in waitForTransaction (#3518) (@latticexyz/store-sync)

Updated waitForTransaction to handle receipt status for user operations.

fix(cli): support verifying systems with linked libraries (#3514) (@latticexyz/cli)

The verify command should now be able to correctly verify systems using public libraries.

feat(create-mud): new react template with stash/entrykit (#3478) (create-mud)

Updated React template with Stash client state library, EntryKit for wallet support, and a cleaned up app structure.

feat(store-indexer): add flag to validate block ranges (#3531) (@latticexyz/block-logs-stream, @latticexyz/store-sync)

Added an experimental option to help sync from load balanced RPCs, where nodes may be slightly out of sync, causing data inconsistencies while fetching logs.

To enable this, replace publicClient: Client with internal_clientOptions: { chain: Chain, validateBlockRange: true } when calling any sync method (e.g. syncToStash). For <SyncProvider>, only a internal_validateBlockRange prop is needed.

-syncToStash({ publicClient, ... });
+syncToStash({ internal_clientOptions: { chain, validateBlockRange: true }, ... });

-<SyncProvider adapter={createSyncAdapter(...)}>
+<SyncProvider adapter={createSyncAdapter(...)} internal_validateBlockRange>

Note that using this option makes an additional call to eth_getBlockByNumber for each eth_getLogs call and expects the RPC to support batched calls.

docs: changeset for #3538 (#3539) (@latticexyz/common)

Improved approach for checking for nonce errors.

feat(create-mud): new react-ecs template (#3485) (create-mud)

Updated React ECS template with EntryKit for wallet support and a cleaned up app structure.

feat(create-mud): rip out create-create-app (#3479) (create-mud)

Replaced internal usage of create-create-app with a simpler recursive copy operation.

feat(world): strip world prefix from function names when encoding system calls (#3527) (@latticexyz/world)

Using encodeSystemCall (and others) with a world ABI and namespace-prefixed function name will now attempt to strip the prefix when encoding it as a system call.

It's recommended to use a system ABI with these functions rather than a world ABI.

import systemAbi from "contracts/out/ISomeSystem.sol/ISomeSystem.sol.abi.json";
encodeSystemCall({ abi: systemAbi, ... });

feat(entrykit): deploy prereqs to any chain (#3529) (@latticexyz/entrykit)

Renamed deploy-local-prereqs bin to entrykit-deploy, which now accepts an RPC URL so that you can deploy the EntryKit prerequisites to your chain of choice.

RPC_URL=http://rpc.garnetchain.com pnpm entrykit-deploy

This bin supports specifying the RPC URL via RPC_URL, RPC_HTTP_URL, FOUNDRY_ETH_RPC_URL environment variables or FOUNDRY_PROFILE if using eth_rpc_url in foundry.toml.

feat(store-indexer): add flag to validate block ranges (#3531) (@latticexyz/block-logs-stream)

Added an experimental option to help sync from load balanced RPCs, where nodes may be slightly out of sync, causing data inconsistencies while fetching logs.

To enable this, replace publicClient: Client with internal_clientOptions: { chain: Chain, validateBlockRange: true } when calling fetchLogs or fetchBlockLogs.

-fetchLogs({ publicClient, ... });
+fetchLogs({ internal_clientOptions: { chain, validateBlockRange: true }, ... });

Note that using this option makes an additional call to eth_getBlockByNumber for each eth_getLogs call and expects the RPC to support batched calls.

feat(store-sync): recs sync adapter (#3486) (@latticexyz/store-sync)

Added an RECS sync adapter to be used with SyncProvider in React apps.

import { WagmiProvider } from "wagmi";
import { QueryClientProvider } from "@tanstack/react-query";
import { SyncProvider } from "@latticexyz/store-sync/react";
import { createSyncAdapter } from "@latticexyz/store-sync/recs";
import { createWorld } from "@latticexyz/recs";
import config from "./mud.config";

const world = createWorld();
const { syncAdapter, components } = createSyncAdapter({ world, config });

export function App() {
  return (
    <WagmiProvider config={wagmiConfig}>
      <QueryClientProvider client={queryClient}>
        <SyncProvider chainId={chainId} address={worldAddress} startBlock={startBlock} adapter={syncAdapter}>
          {children}
        </SyncProvider>
      </QueryClientProvider>
    </WagmiProvider>
  );
}

fix(explorer): create a separate flag and port for the indexer created by the explorer (#3511) (@latticexyz/explorer)

Add a separate flag and port for the indexer created by the Explorer.

feat(entrykit): deploy prereqs to any chain (#3529) (@latticexyz/cli)

Added an empty line to the end of .json output files for consistency. Removed some unnecessary defaults to allow them to pass through via environment variables.

feat(explorer): enable re-executing query (#3471) (@latticexyz/explorer)

Previously, queries could only be executed if they had changed, as data fetching was tied to query updates. Now, it’s possible to trigger a new table data fetch explicitly, regardless of whether the query has changed.

fix(protocol-parser): add padding for encodedLengths (#3507) (@latticexyz/protocol-parser)

Added padding to make sure the encodedLengths field of a Store log is always 32 bytes.

feat(world): support batchCall in callFrom action (#2796) (@latticexyz/world)

Updated callFrom action to automatically translate batchCall to batchCallFrom. Also fixed encodeSystemCallFrom and encodeSystemCallsFrom to return the right format for use with batchCall and batchCallFrom respectively.

fix(cli): use system label when verifying (#3503) (@latticexyz/cli)

Fixed an issue with mud verify where system contract artifacts were being resolved incorrectly.

feat: move CallWithSignature module to its own package (#3491) (@latticexyz/cli, @latticexyz/entrykit, @latticexyz/world-module-callwithsignature, @latticexyz/world-modules)

CallWithSignature module has been moved out of @latticexyz/world-modules and into its own package at @latticexyz/world-module-callwithsignature. This module is now installed by default during deploy as its needed by EntryKit.

If you previously had this module installed in your MUD config, you can now remove it.

 export default defineConfig({
   tables: {
     ...
   },
-  modules: [
-    {
-      artifactPath:
-        "@latticexyz/world-modules/out/Unstable_CallWithSignatureModule.sol/Unstable_CallWithSignatureModule.json",
-      root: true,
-    },
-  ],
 });

fix(explorer): return empty array for empty results (sqlite indexer) (#3469) (@latticexyz/explorer)

The Explorer now returns an empty array for empty results, instead of throwing an error, when using the local indexer.

fix(explorer): show loader only on initial table data load (#3517) (@latticexyz/explorer)

The loader in the Explore table now appears only during the initial data load. Additionally, a loading spinner has been added to the query submit button for non-live queries to indicate when a query is being refetched.

feat(entrykit): deploy prereqs to any chain (#3529) (@latticexyz/common)

Updated Rhodolite chain config with new contract addresses.

fix(cli): checksum deployed world addresses (#3465) (@latticexyz/cli)

The world address stored in worlds.json and deploys/latest.json is now checksummed.

chore(cli): print mud version in deploy (#3476) (@latticexyz/cli)

Deploy now prints the current MUD CLI version for easier debugging.