@crewhaus/tool-chaincall 0.7.0 → 0.8.1

package/LICENSE

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

package/NOTICE

@@ -0,0 +1,9 @@
+CrewHaus Factory
+Copyright 2026 Max Meier
+
+This product includes software developed by Max Meier
+(operating as StudioMax — https://studiomax.io) and contributors.
+
+The CrewHaus name and logo are trademarks of Max Meier. See
+https://github.com/crewhaus/factory/blob/main/TRADEMARK.md for the
+use-of-marks policy.

package/README.md

@@ -46,6 +46,32 @@ SUCCEEDS in the EVM and returns nothing. Decode that as `uint256` and you get
 zero, which reads as a balance. Every such row is marked `emptyReturn` and
 left undecoded, and the result says how many there were.
 
+## Who answers a batch
+
+A batch is one `eth_call` to Multicall3, and every row in it — each call's
+return data, whether it succeeded, the block number that pins it — is what
+that contract returns. Any contract can implement `aggregate3` and make rows
+up, so which one answers is the operator's decision, not a call's: batches go
+to the canonical deployment (`0xcA11bde05977b3631167028862bE2a173976CA11`)
+unless `tool_config.chaincall.multicall3` names another for the chain. A
+call's `multicall3Address` is accepted only when it is that same address, and
+anything else is refused before any read. `EvmMulticall`, `ContractInspect`
+(when it batched) and a balance-tracking `EvmSimulateBundle` say who answered:
+`aggregator: { address, source }`, with `source` either `canonical` or
+`config`.
+
+```yaml
+tool_config:
+  chaincall:
+    multicall3:                 # only where the canonical deployment is absent
+      "324": "0xF9cda624FBC7e059355ce98a31693d299FACd963"
+```
+
+`EvmSimulateBundle` runs under `stateOverrides` the caller chose, so its
+results describe the chain as overridden; it says so in `limitations`, and
+names the aggregator when an override rewrote the one that read the tracked
+balances.
+
 ## Verified, and claimed
 
 `ContractInspect` splits its answer in two, because they are different kinds
@@ -97,10 +123,14 @@ is not the same thing as one.
 A probe that **reverts** is an answer: a contract that is not ERC-165 reverts
 on `supportsInterface`, one that is not a proxy reverts on `implementation()`.
 A probe the node could not answer at all — it is down, it is rate-limiting, it
-pruned the block — is not, and the two are counted separately. When *every*
-probe fails that way the whole read is **refused**, because the report it would
-otherwise produce ("not a proxy, not ERC-165") is a set of claims about a
-contract nobody managed to ask.
+pruned the block — is not, and the two are counted separately. With several
+nodes in the chain's `rpcUrls`, a probe counts as reverted when every node that
+answered said so; a node that could not be reached counts neither way. A
+`quorum` of two or more nodes stops waiting once no answer can win, so there a
+probe that fails on every node counts as unanswered. When *every* probe fails
+that way the whole read is **refused**, because the report it would otherwise
+produce ("not a proxy, not ERC-165") is a set of claims about a contract nobody
+managed to ask.
 
 The same line is held one probe at a time. When it is the `0xffffffff`
 sentinel that the node would not answer, the claims are still dropped — but
@@ -138,7 +168,10 @@ providers use instead of it mean the method is unimplemented. A **timeout**,
 a **rejected parameter**, a **rate limit** and a **revert** do not — degrading on
 any of those would turn a transient fault into a permanently weaker answer
 that still reads like an answer. A timed-out simulation is a refusal that says
-so, and no `eth_call` is attempted after it.
+so, and no `eth_call` is attempted after it. With several nodes, every one
+must say it lacks the method: one that rejected the bundle, could not be
+reached or was not heard may have it. A `quorum` of two or more nodes stops
+waiting once no answer can win, so it never falls back.
 
 `allowFallback: false` refuses instead of answering the lesser question.
 
@@ -174,7 +207,8 @@ one:
 - a block with no `baseFeePerGas` is a **legacy** chain, priced from
   `eth_gasPrice`, with no 1559 projection at all;
 - a node without `eth_feeHistory` is reported as such — no percentiles, rather
-  than percentiles from somewhere else;
+  than percentiles from somewhere else. With several nodes, every one must lack
+  it, as for the simulation fallback above;
 - a base fee that is **identical in every sampled block** is flagged. Several
   chains hold it at a floor and price congestion elsewhere; that is not a
   quiet market;
@@ -220,10 +254,32 @@ A tool that cannot say no is not finished. These say no, with the reason:
 - **balance tracking without a chained simulation**;
 - **fee percentiles that are not strictly ascending**, which `eth_feeHistory`
   requires, and a **block the node does not have**;
+- **a `multicall3Address` other than the canonical deployment or the one the
+  operator configured** for the chain, before anything is dialled;
+- **a node that answers with any redirect**, even to its own address: a chain
+  read never follows one, and the error says where it pointed. Under
+  `fallback`, the next node named is asked instead. Point `rpcUrls` at the
+  address that answers directly;
 - **an address that is not 20 hex bytes**, before anything is dialled. A
   lowercase address is answered, with `checksumVerified: false` attached,
   because EIP-55 can only verify a checksum that is there.
 
+## Permission rules
+
+A rule's argument for these tools is `<chainId>/<address>`, the chain first
+and written as your spec's `chains[].id` names it:
+`EvmMulticall(8453/0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913)` is one contract
+on a chain declared `id: "8453"`, `EvmMulticall(base-mainnet/0x8335…)` the same
+contract on one declared `id: base-mainnet`, and `ContractInspect(**0x8335…)`
+that address on any chain.
+
+An allow must be written that way: `*` does not cross the `/`, so
+`alwaysAllow ContractInspect(*)` or `ContractInspect(0x8335…)` grants nothing
+(write `**` for "any"). A deny or ask also fires on the address alone and on
+the chain alone, so `alwaysDeny ContractInspect(0x8335…)` denies that contract
+on every chain. A deny or ask ignores the letter case of the hex: an EIP-55
+address and its lower-case spelling are one account.
+
 ## Numbers
 
 No chain quantity is ever a JS number. Wei, balances, gas and block numbers
@@ -238,10 +294,22 @@ an integer nor the value that was computed.
 
 ## Wiring
 
-The transport is bound once at boot, per chain, from the spec's `chains[]`
-block — the same shape `@crewhaus/tool-evm` uses. No caller supplies a URL
+The transport is bound once at boot, per chain, from the spec's `chains`
+block — the same block `@crewhaus/tool-evm` reads. A compiled bundle,
+`crewhaus run` and `crewhaus eval` call `bindChainCallChains` with it; without
+one, every call refuses and names the block to write. No caller supplies a URL
 anywhere in this package, and there is no endpoint list inside it.
 
+```yaml
+chains:
+  - id: "8453"
+    kind: evm
+    rpcUrls: [$BASE_RPC_URL]     # read from the environment, never compiled in
+    finality: { kind: finalized }
+```
+
+A host that builds its own adapters binds them directly:
+
 ```ts
 import { setChainRpcResolver, chainRpcFromAdapter } from "@crewhaus/tool-chaincall";
 

package/dist/index.d.ts

@@ -1,6 +1,7 @@
 import type { RegisteredTool } from "@crewhaus/tool-catalog";
-export { ChainCallError, type ChainRpc, type ChainRpcResolver, _setRpc, chainRpcFromAdapter, setChainRpcResolver, } from "./lib/rpc";
+export { ChainCallError, type ChainRpc, type ChainRpcResolver, _setRpc, bindChainCallChains, chainRpcFromAdapter, setChainRpcResolver, } from "./lib/rpc";
 export { MULTICALL3_ADDRESS } from "@crewhaus/tool-onchain";
+export { type Aggregator, type ChaincallConfigInput, registerChaincallConfig, } from "./lib/aggregator";
 export { EIP1822_SLOT, EIP1967_ADMIN_SLOT, EIP1967_BEACON_SLOT, EIP1967_IMPLEMENTATION_SLOT, ERC165_INVALID_ID, KNOWN_INTERFACES, } from "./lib/proxy";
 export declare const evmMulticall: RegisteredTool;
 export declare const contractInspect: RegisteredTool;

package/dist/index.js

@@ -38,15 +38,17 @@
 import { buildTool } from "@crewhaus/tool-builder";
 import { MULTICALL3_ADDRESS, decodeAggregate3, decodeRevertData, encodeAggregate3, } from "@crewhaus/tool-onchain";
 import { z } from "zod";
+import { resolveAggregator } from "./lib/aggregator";
 import { chunk, runAggregate3 } from "./lib/batch";
 import { SELECTORS, balanceOfData, checkAddress, decodeValues, encodeCallData, getEthBalanceData, supportsInterfaceData, } from "./lib/codec";
 import { changeBps, nextBaseFee, summarisePercentile } from "./lib/fees";
 import { ZERO_ADDRESS, data as asData, blockParam, byteLength, isZeroWord, optionalQuantity, quantity, toQuantity, wordAt, wordToAddress, wordToBigint, wordToBool, } from "./lib/hex";
 import { DIAMOND_LOUPE_ID, EIP1822_SLOT, EIP1967_ADMIN_SLOT, EIP1967_BEACON_SLOT, EIP1967_IMPLEMENTATION_SLOT, ERC165_INVALID_ID, KNOWN_INTERFACES, minimalProxyTarget, reconcileProxy, } from "./lib/proxy";
-import { ChainCallError, isAbort, isMethodUnsupported, resolveRpc, rpcError, rpcErrorText, rpcRead, startDeadline, } from "./lib/rpc";
+import { ChainCallError, firstRefusal, isAbort, isMethodUnsupported, nodeAnswers, resolveRpc, rpcErrorText, rpcRead, startDeadline, } from "./lib/rpc";
 import { FALLBACK_LIMITATIONS, parseSimulateV1, revertFromCallError, toWireCall, unchainedLimitation, } from "./lib/simulate";
-export { ChainCallError, _setRpc, chainRpcFromAdapter, setChainRpcResolver, } from "./lib/rpc";
+export { ChainCallError, _setRpc, bindChainCallChains, chainRpcFromAdapter, setChainRpcResolver, } from "./lib/rpc";
 export { MULTICALL3_ADDRESS } from "@crewhaus/tool-onchain";
+export { registerChaincallConfig, } from "./lib/aggregator";
 export { EIP1822_SLOT, EIP1967_ADMIN_SLOT, EIP1967_BEACON_SLOT, EIP1967_IMPLEMENTATION_SLOT, ERC165_INVALID_ID, KNOWN_INTERFACES, } from "./lib/proxy";
 const json = (value) => JSON.stringify(value);
 const DEFAULT_TIMEOUT_MS = 30_000;
@@ -97,7 +99,7 @@ const multicallAddressField = z
     .string()
     .regex(/^0x[0-9a-fA-F]{40}$/)
     .optional()
-    .describe(`Multicall3 on this chain; default ${MULTICALL3_ADDRESS}`);
+    .describe(`leave it out: batches go to the canonical Multicall3 (${MULTICALL3_ADDRESS}) or the one the operator configured for the chain, and any other address is refused`);
 /** The block parameter, and whether the caller pinned it themselves. */
 function blockOf(input) {
     return {
@@ -147,6 +149,7 @@ async function calldataFor(call, index) {
 }
 export const evmMulticall = buildTool({
     name: "EvmMulticall",
+    operativeArgs: [{ field: "calls.target", kind: "id", within: "chainId" }],
     description: "Run many view calls against a chain in one request through Multicall3, returning one decoded row per call at a SINGLE block height. Use it for any question that reads more than one contract — a hundred balances, a token's whole metadata, a pool's reserves plus its fee — because a hundred separate reads land at a hundred different block heights and the answers do not add up. A sub-call that reverts is a row with its revert reason, not a failed request, so one bad token does not lose the other ninety-nine. When a batch is too large for one request it is split, and the block is PINNED from the first batch so every row still answers at the same height. A call that succeeds with empty return data is flagged rather than decoded: in the EVM, calling an address with no code succeeds and returns nothing, which is how a missing contract becomes a zero balance. It reads only, and nothing here signs or submits anything.",
     inputSchema: z
         .object({
@@ -170,7 +173,10 @@ export const evmMulticall = buildTool({
         const deadline = startDeadline(input.timeoutMs ?? DEFAULT_TIMEOUT_MS, ctx?.signal);
         try {
             const rpc = resolveRpc(input.chainId, "EvmMulticall");
-            const multicall3 = input.multicall3Address ?? MULTICALL3_ADDRESS;
+            // Resolved before any read: an aggregator the operator did not name
+            // is refused, not asked.
+            const aggregator = resolveAggregator(input.chainId, input.multicall3Address, ctx?.toolConfig, "EvmMulticall");
+            const multicall3 = aggregator.address;
             const { param, pinnedByCaller } = blockOf(input);
             const calls = [];
             for (const [index, call] of input.calls.entries()) {
@@ -270,6 +276,8 @@ export const evmMulticall = buildTool({
             return json({
                 chainId: input.chainId,
                 multicall3,
+                // Who answered every row, since each one is its word.
+                aggregator,
                 block: {
                     requested: param,
                     number: pinned === undefined ? null : pinned.toString(),
@@ -306,10 +314,14 @@ export const evmMulticall = buildTool({
 function looksLikeRevert(err) {
     if (revertFromCallError(err) !== undefined)
         return true;
-    const { code, message } = rpcError(err);
-    // Geth answers a reverted eth_call with code 3. Nodes that do not attach
-    // revert data still say so in the message.
-    return code === 3 || /revert|out of gas|invalid opcode/i.test(message ?? "");
+    // Every node that answered must have said it reverted, and one must have
+    // answered: a node that could not be reached taught nothing either way, and
+    // one that answered anything else contradicts the revert. Geth answers a
+    // reverted eth_call with code 3; nodes that do not attach revert data still
+    // say so in the message.
+    const answers = nodeAnswers(err).flatMap(({ answer }) => (answer === undefined ? [] : [answer]));
+    return (answers.length > 0 &&
+        answers.every(({ code, message }) => code === 3 || /revert|out of gas|invalid opcode/i.test(message ?? "")));
 }
 async function runViews(rpc, chainId, views, multicall3, block, signal) {
     try {
@@ -382,7 +394,8 @@ function addressResult(row, what) {
 }
 export const contractInspect = buildTool({
     name: "ContractInspect",
-    description: "Ask an address what it is before calling it: whether there is code there at all, how big it is, whether it is a proxy and what it delegates to, and which ERC-165 interfaces it claims. Use it whenever an address arrives from somewhere you did not write — a proxy's ABI is the implementation's, not the proxy's, and calling the wrong ABI produces calldata a node accepts and a contract misreads. The answer is split into what was VERIFIED and what the contract CLAIMS, because those are different kinds of fact: a proxy's implementation slot is storage, read with eth_getStorageAt, while supportsInterface is the contract answering a question about itself and a contract can lie. Contracts that claim to support the reserved 0xffffffff interface id are reported as non-compliant and their claims are dropped entirely rather than listed. A proxy whose mechanisms disagree, and a diamond that has no single implementation, come back unresolved with the reason instead of a guessed address. Read-only: it never signs, sends or deploys.",
+    operativeArgs: [{ field: "address", kind: "id", within: "chainId" }],
+    description: "Ask an address what it is before calling it: whether there is code there, how big it is, whether it is a proxy and what it delegates to, and which ERC-165 interfaces it claims. Use it whenever an address arrives from somewhere you did not write: a proxy's ABI is the implementation's, and calling the wrong ABI produces calldata a node accepts and a contract misreads. The answer separates what was VERIFIED from what the contract CLAIMS: a proxy's implementation slot is storage, read with eth_getStorageAt, while supportsInterface is the contract answering about itself, and a contract can lie. A contract claiming the reserved 0xffffffff interface id is reported as non-compliant and its claims are dropped. A proxy whose mechanisms disagree, or a diamond with no single implementation, comes back unresolved with the reason instead of a guessed address. Read-only: it never signs, sends or deploys.",
     inputSchema: z
         .object({
         chainId: chainIdField,
@@ -407,9 +420,10 @@ export const contractInspect = buildTool({
         const deadline = startDeadline(input.timeoutMs ?? DEFAULT_TIMEOUT_MS, ctx?.signal);
         try {
             const rpc = resolveRpc(input.chainId, "ContractInspect");
+            const aggregator = resolveAggregator(input.chainId, input.multicall3Address, ctx?.toolConfig, "ContractInspect");
             const target = await checkAddress(input.address, "address");
             const { param } = blockOf(input);
-            const multicall3 = input.multicall3Address ?? MULTICALL3_ADDRESS;
+            const multicall3 = aggregator.address;
             const caveats = [];
             const code = asData(await rpcRead(rpc, input.chainId, "eth_getCode", [target.address, param], deadline.signal), "eth_getCode");
             const codeSize = byteLength(code);
@@ -558,6 +572,8 @@ export const contractInspect = buildTool({
                 address: target.address,
                 checksumVerified: target.checksumVerified,
                 block: { requested: param },
+                // Who answered the batched view calls, when they were batched.
+                aggregator: mode === "multicall3" ? aggregator : null,
                 verified: {
                     isContract: true,
                     codeSize,
@@ -668,7 +684,8 @@ function readProbeBlob(returnData, count) {
 }
 export const evmSimulateBundle = buildTool({
     name: "EvmSimulateBundle",
-    description: "Simulate an ordered sequence of calls against a block and report what each one would do — status, gas, return data, revert reason, logs — without submitting anything. Use it to check a plan before approving it: an approve followed by a swap, a multi-step position change, a governance execution. The point is that state CHAINS, so the second call sees what the first one did. That needs eth_simulateV1, which many endpoints do not implement; when one does not, this falls back to independent eth_calls and says so in `mode`, sets `chained: false`, and OMITS logs and balance deltas entirely rather than reporting the half that survives — a partially-true effects summary is precisely what a policy gate would trust and be wrong about. A timeout or a rejected parameter is never degraded into a fallback, because neither says the node cannot answer the real question. Optional balance tracking brackets the bundle with Multicall3 balance reads, so native and ERC-20 deltas come from the chain's own accounting rather than from summing Transfer logs, which miss fee-on-transfer and rebasing tokens. It simulates only: no key is accepted, nothing is signed, and nothing is broadcast.",
+    operativeArgs: [{ field: "calls.to", kind: "id", within: "chainId" }],
+    description: "Simulate an ordered sequence of calls against a block and report what each would do (status, gas, return data, revert reason, logs) without submitting anything. Use it to check a plan before approving it: an approve then a swap, a multi-step position change, a governance execution. State CHAINS, so each call sees what the one before it did, and that needs eth_simulateV1. When the endpoint lacks it, this falls back to independent eth_calls, says so in `mode`, sets `chained: false`, and OMITS logs and balance deltas rather than report a half-true effects summary a policy gate would trust. A timeout or a rejected parameter is never degraded into that fallback. Optional balance tracking brackets the bundle with Multicall3 balance reads, so native and ERC-20 deltas come from the chain's own accounting rather than from summing Transfer logs. It simulates only: no key is accepted, nothing is signed, and nothing is broadcast.",
     inputSchema: z
         .object({
         chainId: chainIdField,
@@ -719,7 +736,12 @@ export const evmSimulateBundle = buildTool({
         try {
             const rpc = resolveRpc(input.chainId, "EvmSimulateBundle");
             const { param } = blockOf(input);
-            const multicall3 = input.multicall3Address ?? MULTICALL3_ADDRESS;
+            // Multicall3 reads the tracked balances, and nothing else here; without
+            // trackBalances a multicall3Address is ignored, as it always was.
+            const aggregator = input.trackBalances === undefined
+                ? undefined
+                : resolveAggregator(input.chainId, input.multicall3Address, ctx?.toolConfig, "EvmSimulateBundle");
+            const multicall3 = aggregator?.address ?? MULTICALL3_ADDRESS;
             const traceTransfers = input.traceTransfers ?? true;
             const userCalls = input.calls.map((call, index) => toWireCall(call, index));
             let probes = [];
@@ -760,7 +782,11 @@ export const evmSimulateBundle = buildTool({
                     throw new ChainCallError("EvmSimulateBundle: the call was cancelled — the deadline elapsed, or the run was cancelled — before the node answered eth_simulateV1. This is NOT treated as an unimplemented method, so no eth_call fallback was attempted; raise timeoutMs or retry.", err);
                 }
                 if (!isMethodUnsupported(err, deadline.signal)) {
-                    throw new ChainCallError(`EvmSimulateBundle: the node refused this bundle — ${rpcErrorText(err)}. The node implements eth_simulateV1, so this is an answer about the bundle and not a reason to fall back to eth_call.`, err);
+                    const refusal = firstRefusal(err);
+                    const one = nodeAnswers(err).length === 1;
+                    throw new ChainCallError(refusal !== undefined
+                        ? `EvmSimulateBundle: ${one ? "the node" : "a node"} refused this bundle — ${refusal}. ${one ? "The node" : "That node"} implements eth_simulateV1, so this is an answer about the bundle and not a reason to fall back to eth_call.`
+                        : `EvmSimulateBundle: no node simulated this bundle — ${rpcErrorText(err)}. The eth_call fallback is used only when every node says it lacks eth_simulateV1, and not every node did, so it was not used. Retry, or check the nodes in the chains block.`, err);
                 }
                 if (input.allowFallback === false) {
                     throw new ChainCallError(`EvmSimulateBundle: this endpoint does not implement eth_simulateV1 (${rpcErrorText(err)}) and allowFallback is false. The eth_call fallback cannot chain state between calls, so it answers a different question; re-run with allowFallback, or point at an endpoint that implements eth_simulateV1.`, err);
@@ -775,6 +801,14 @@ export const evmSimulateBundle = buildTool({
             const inner = tracking ? block.calls.slice(1, -1) : block.calls;
             const calls = inner.map((call, index) => ({ ...call, index }));
             const limitations = [];
+            const overridden = Object.keys(input.stateOverrides ?? {});
+            if (overridden.length > 0) {
+                const aggregatorOverridden = aggregator !== undefined &&
+                    overridden.some((a) => a.toLowerCase() === aggregator.address.toLowerCase());
+                limitations.push(`stateOverrides rewrote ${overridden.length} address(es) for this simulation, so every result describes the chain as overridden, not as it is${aggregatorOverridden
+                    ? ` — including the Multicall3 (${aggregator.address}) that read the tracked balances, so balanceChanges are whatever the override's code returns`
+                    : ""}.`);
+            }
             if (traceTransfers) {
                 limitations.push("traceTransfers is on, so native value movements appear as synthetic ERC-20-shaped Transfer logs emitted by the zero address. They are not events any contract actually emitted.");
             }
@@ -801,7 +835,7 @@ export const evmSimulateBundle = buildTool({
                 callCount: calls.length,
                 reverted: calls.filter((c) => c.status === "reverted").length,
                 calls,
-                ...(balanceChanges !== undefined ? { balanceChanges } : {}),
+                ...(balanceChanges !== undefined ? { balanceChanges, aggregator } : {}),
                 ...(limitations.length > 0 ? { limitations } : {}),
             });
         }
@@ -958,7 +992,8 @@ async function resolveFallbackBlock(rpc, chainId, block, signal) {
 const OP_GAS_PRICE_ORACLE = "0x420000000000000000000000000000000000000F";
 export const gasMarketRead = buildTool({
     name: "GasMarketRead",
-    description: "Read a chain's fee market: the current base fee, priority-fee percentiles from eth_feeHistory over a window of blocks, and the next block's base fee computed by the EIP-1559 rule. Use it to decide when to send and what to pay, instead of a model recalling a gwei figure. It reports WHICH mechanism the chain is running rather than assuming one — a chain with no baseFeePerGas has no 1559 market and is reported as legacy, a node without eth_feeHistory is reported as such instead of being filled in, and a base fee that never moves across the window is flagged rather than trended. The projection is computed from the block's integer gasUsed and gasLimit, never from feeHistory's floating-point gasUsedRatio, and is compared against the node's own next-block figure so a chain with a non-standard elasticity shows up as a disagreement rather than as a confident wrong number. It does not price rollup L1 data fees, and says so — on an OP-stack chain it checks whether the GasPriceOracle predeploy is there and warns that the cost it does not report is often the larger one.",
+    operativeArgs: [{ field: "chainId", kind: "id" }],
+    description: "Read a chain's fee market: the current base fee, priority-fee percentiles from eth_feeHistory over a window of blocks, and the next block's base fee by the EIP-1559 rule. Use it to decide when to send and what to pay, instead of a model recalling a gwei figure. It reports which mechanism the chain runs rather than assuming one: a chain with no baseFeePerGas is reported as legacy, a node without eth_feeHistory is reported as such rather than filled in, and a base fee that never moves is flagged rather than trended. The projection uses the block's integer gasUsed and gasLimit, never feeHistory's floating-point ratio, and is compared with the node's own next-block figure, so a non-standard elasticity shows as a disagreement. It does not price rollup L1 data fees, and says so: on an OP-stack chain it checks for the GasPriceOracle predeploy and warns that the unreported cost is often the larger one.",
     inputSchema: z
         .object({
         chainId: chainIdField,

package/dist/lib/aggregator.d.ts

@@ -0,0 +1,24 @@
+/** Who served a batch, as every batched answer reports it. */
+export type Aggregator = {
+    /** EIP-55. */
+    readonly address: string;
+    /** `canonical`: the deterministic deploy. `config`: the operator's tool_config. */
+    readonly source: "canonical" | "config";
+};
+/** The spec's `tool_config.chaincall` block. */
+export type ChaincallConfigInput = {
+    /** chain id → the Multicall3 deployment batches on that chain go to. */
+    readonly multicall3?: Readonly<Record<string, string>>;
+};
+/**
+ * Apply `tool_config.chaincall` at boot: the Multicall3 deployments in
+ * `multicall3`, each held to the address check (shape and EIP-55 checksum).
+ * A block without it leaves every chain on the canonical deployment.
+ */
+export declare function registerChaincallConfig(input: ChaincallConfigInput): void;
+/**
+ * The aggregator a batch on `chainId` goes to, and where that came from. A
+ * `requested` address other than that one is refused: which contract answers
+ * every row is not a per-call choice.
+ */
+export declare function resolveAggregator(chainId: string, requested: string | undefined, toolConfig: unknown, toolName: string): Aggregator;

package/dist/lib/aggregator.js

@@ -0,0 +1,70 @@
+/**
+ * Which Multicall3 answers a batch — decided by the operator, never by a call.
+ *
+ * A batch is ONE `eth_call` to Multicall3, and every row in it — each view
+ * call's return data, whether it succeeded, the block number the batch pins —
+ * is whatever that contract returns. Any contract can implement `aggregate3`
+ * and return rows it made up. So a model-supplied `multicall3Address` was a
+ * way to make EvmMulticall report a balance nobody holds as `success: true`,
+ * ContractInspect report interfaces a contract never claimed, and
+ * EvmSimulateBundle's balance tracking report deltas that never happened.
+ *
+ * The aggregator is the canonical deployment unless the operator names
+ * another for that chain in `tool_config.chaincall.multicall3` (a chain whose
+ * Multicall3 is elsewhere, such as zkSync Era). A call may still pass
+ * `multicall3Address`, which older callers do, but only the address that
+ * would be used anyway is accepted; anything else is refused before a read.
+ * This is `@crewhaus/tool-token`'s rule, applied to this package's batches.
+ */
+import { MULTICALL3_ADDRESS, parseMulticallMap } from "@crewhaus/tool-onchain";
+import { ChainCallError } from "./rpc";
+/**
+ * The operator's Multicall3 deployments by chain id, from
+ * `tool_config.chaincall.multicall3`. Only {@link registerChaincallConfig}
+ * writes it.
+ */
+let configured = new Map();
+function parseChaincallMulticall(input) {
+    try {
+        return parseMulticallMap(input, "tool_config.chaincall.multicall3");
+    }
+    catch (err) {
+        throw new ChainCallError(err.message);
+    }
+}
+/**
+ * Apply `tool_config.chaincall` at boot: the Multicall3 deployments in
+ * `multicall3`, each held to the address check (shape and EIP-55 checksum).
+ * A block without it leaves every chain on the canonical deployment.
+ */
+export function registerChaincallConfig(input) {
+    const block = (input ?? {});
+    configured = parseChaincallMulticall(block["multicall3"]);
+}
+/**
+ * The map one call runs under: the serving candidate's own `tool_config`
+ * block when it has one (it replaces the boot registration, as every
+ * tool_config block does), else the boot registration.
+ */
+function mapFor(toolConfig) {
+    if (typeof toolConfig === "object" && toolConfig !== null && !Array.isArray(toolConfig)) {
+        return parseChaincallMulticall(toolConfig["multicall3"]);
+    }
+    return configured;
+}
+/**
+ * The aggregator a batch on `chainId` goes to, and where that came from. A
+ * `requested` address other than that one is refused: which contract answers
+ * every row is not a per-call choice.
+ */
+export function resolveAggregator(chainId, requested, toolConfig, toolName) {
+    const override = mapFor(toolConfig).get(chainId);
+    const aggregator = override === undefined
+        ? { address: MULTICALL3_ADDRESS, source: "canonical" }
+        : { address: override, source: "config" };
+    if (requested !== undefined &&
+        requested.trim().toLowerCase() !== aggregator.address.toLowerCase()) {
+        throw new ChainCallError(`${toolName}: multicall3Address ${JSON.stringify(requested.slice(0, 64))} is not the Multicall3 chain "${chainId}" reads through (${aggregator.address}). The aggregator answers every row of a batch — return data, success, the block number — so which contract that is belongs to the operator: name it in tool_config.chaincall.multicall3 for chain "${chainId}", and leave multicall3Address out.`);
+    }
+    return aggregator;
+}