@ninsei-labs/sdk 0.46.0 → 0.46.1

package/CHANGELOG.md

@@ -1,3 +1,14 @@
+## 0.46.1 — 2026-10-21
+
+THE FACTORY SELECTORS FOLLOW THE 20-FIELD QUOTE.
+
+- `FACTORY_METHODS.predict` is `0x3e949279` and `createOrderAndFund` is `0x3a504547` (the 19-field values were
+  `0x0824d205` and `0x4703a9d3`). With the old selectors the node's calldata reverted at the factory on the first
+  call, so no order could be created even though the quote itself was correct.
+- `tools/check-factory-selectors.mjs` derives both selectors from `QUOTE_FIELDS` and the ABI types, and a
+  breaking run mutates a copy of the module to prove the check reddens. The pair can no longer go stale in
+  silence when a field joins the signed tuple.
+
 ## 0.46.0 — 2026-10-21
 
 THE QUOTE CARRIES THE CLAIM TIP, AND THE CLAIM PAYS IT.

package/engine/evm/factory.js

@@ -10,15 +10,16 @@
 // feeFor() (the router was removed), so there is nothing to ask. All arguments are static, so calldata is a
 // selector plus 32-byte words, built here in one place and checked mechanically.
 //
-//   cast sig "predict((address,address,address,address,address,address,uint256,uint64,uint64,bytes32,bytes32,bytes32,uint256,uint256,uint256,address,uint64,uint256,uint256),bytes32,bytes32,uint8,bytes32,bytes32,bytes32)" -> 0x0824d205
-//   cast sig "createOrderAndFund(<same tuple>,...)"                                                                                                                -> 0x4703a9d3
+//   cast sig "predict((address,address,address,address,address,address,uint256,uint64,uint64,bytes32,bytes32,bytes32,uint256,uint256,uint256,address,uint64,uint256,uint256,uint256),bytes32,bytes32,uint8,bytes32,bytes32,bytes32)" -> 0x3e949279
+//   cast sig "createOrderAndFund(<same tuple>,...)"                                                                                                                -> 0x3a504547
 
 export const FACTORY_METHODS = {
-  // THE QUOTE GREW THE xmrAmount FIELD: the XMR side of the deal is part of the signed set, so both selectors
-  // changed a second time (earlier for the cashier field).
-  predict: "0x0824d205",
+  // THE SELECTORS FOLLOW THE 20-FIELD QUOTE. claimTip is the last field of the tuple, so both selectors changed when
+  // it joined the signed set; the old 19-field values (0x0824d205 / 0x4703a9d3) address a function this factory no
+  // longer has.
+  predict: "0x3e949279",
   // create the escrow AND deposit funds in ONE transaction (a value transfer with the call).
-  createOrderAndFund: "0x4703a9d3",
+  createOrderAndFund: "0x3a504547",
 };
 
 // The OrderCreated event topic. It grew the registry address, the provider and the signing key:

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@ninsei-labs/sdk",
-  "version": "0.46.0",
+  "version": "0.46.1",
   "publishConfig": {
     "access": "public",
     "registry": "https://registry.npmjs.org/"
@@ -39,6 +39,7 @@
     "check:arrival-read": "node tools/check-arrival-read.mjs",
     "check:daemon-address": "node tools/check-daemon-address.mjs",
     "check:ci-scripts": "node tools/check-ci-scripts.mjs",
+    "check:factory-selectors": "node tools/check-factory-selectors.mjs",
     "check:fee-estimate": "node tools/check-fee-estimate.mjs",
     "check:deadline-scale": "node tools/check-deadline-scale.mjs",
     "check:node-probe": "node tools/check-node-probe.mjs"

package/src/version.mjs

@@ -6,4 +6,4 @@
 // tools/sync-version.mjs. Do not edit it by hand - set the version in package.json and run `npm run sync:version`.
 // The `version` check in tools/check.mjs refuses a mismatch, and refuses a runtime read of package.json here.
 
-export const SDK_VERSION = "0.46.0";
+export const SDK_VERSION = "0.46.1";