Add Gnosis script to post an order with hooks in appData

Adds src/scripts/gnosis/postHookOrder.ts: posts a CoW order on Gnosis
Chain carrying CoW hooks in the order's appData, and prints the full
appData document + hash + order URL so we can inspect how the real
backend/solvers convey and treat hooks.

This is to validate the transport assumption behind an enforceable-hooks
wrapper (cow-shed): that pre/post interactions and wrapper routing travel
via appData. This SDK version exposes standard CoW hooks
(metadata.hooks) but no wrapper/Atomic-Bundles field, so the script
probes the hooks-in-appData path (the closest existing mechanism).

Also adds WXDAI/COW Gnosis token constants and registers the script as
the active JOBS entry.

Author: anxolin

src/const/gnosis.ts

@@ -1 +1,3 @@
 export const GNO_ADDRESS = "0x9C58BAcC331c9aa871AFD802DB6379a98e80CEdb";
+export const WXDAI_ADDRESS = "0xe91D153E0b41518A2Ce8Dd3D7944Fa863463a97d";
+export const COW_ADDRESS = "0x177127622c4A00F3d409B75571e12cB3c8973d3c";

src/index.ts

@@ -24,6 +24,7 @@ import { run as swapSellWithSlippageTolerance } from "./scripts/sepolia/swapSell
 import { run as approveTokenMainnet } from "./scripts/mainnet/approveTokenMainnet";
 import { run as getQuoteAndPostOrderMainnet } from "./scripts/mainnet/getQuoteAndPostOrder";
 import { run as approveTokenGnosis } from "./scripts/gnosis/approveTokenGnosis";
+import { run as postHookOrderGnosis } from "./scripts/gnosis/postHookOrder";
 import { run as swapAndBridgeSwapsIo } from "./scripts/bridging/swapAndBridgeSwapsIO";
 import { run as approveTokenArbitrum } from "./scripts/arbitrum/approveTokenArbitrum";
 import { run as swapAndBridgeAccrossArbitrum } from "./scripts/bridging/swapAndBridgeAccrossArbitrum";
@@ -86,7 +87,10 @@ const JOBS: (() => Promise<unknown>)[] = [
   // getEthFlowId,
   // minimalAppData,
   // getIpfsForLegacyDoc,
-  postTwapForEOA,
+  // postTwapForEOA,
+
+  // Post a Gnosis order carrying CoW hooks in appData (enforceable-hooks assumption test)
+  postHookOrderGnosis,
 ];
 
 async function main() {

src/scripts/gnosis/postHookOrder.ts

@@ -0,0 +1,97 @@
+import { gnosis, APP_CODE } from "../../const";
+const { WXDAI_ADDRESS, GNO_ADDRESS } = gnosis;
+import {
+  SupportedChainId,
+  OrderKind,
+  TradeParameters,
+  TradingSdk,
+} from "@cowprotocol/cow-sdk";
+import { MetadataApi } from "@cowprotocol/app-data";
+import { ethers } from "ethers";
+import { getWallet, jsonReplacer } from "../../utils";
+
+/**
+ * Post an order on Gnosis Chain with CoW Protocol hooks carried in the order's `appData`,
+ * so we can inspect end-to-end how the real backend/solvers convey and treat hooks.
+ *
+ * Why this script exists
+ * ----------------------
+ * We're validating an assumption for an "enforceable hooks" wrapper (cow-shed): that the
+ * pre/post interactions and any wrapper routing for an order travel in `appData`, and how the
+ * backend serves that to solvers.
+ *
+ * What this SDK version supports
+ * ------------------------------
+ * `@cowprotocol/app-data` exposes standard **CoW hooks** (`metadata.hooks.pre` / `.post`, each a
+ * `{ target, callData, gasLimit }`). It does NOT (in this version) expose a "wrapper" /
+ * Atomic-Bundles field, so we cannot route an order through a settlement wrapper from here.
+ * This script therefore probes the *hooks-in-appData* path — the closest existing mechanism —
+ * and prints the full appData document + hash so we can inspect exactly what the backend stores
+ * and serves. Extend `HOOKS` below as the wrapper appData schema becomes available.
+ *
+ * Env required: PRIVATE_KEY, RPC_URL_100.
+ */
+
+// --- tweak me -------------------------------------------------------------
+const SELL_TOKEN = WXDAI_ADDRESS;
+const BUY_TOKEN = GNO_ADDRESS;
+const SELL_AMOUNT = ethers.utils.parseUnits("1", 18).toString(); // 1 WXDAI
+
+// A benign no-op post-hook purely to exercise the hooks-in-appData path. Calling address(0)
+// with empty calldata is a harmless no-op a solver can execute. Replace with a real interaction
+// (e.g. a call routed through your cow-shed) once we test meaningful hooks.
+const HOOKS = {
+  pre: [] as { target: string; callData: string; gasLimit: string }[],
+  post: [
+    {
+      target: "0x0000000000000000000000000000000000000000",
+      callData: "0x",
+      gasLimit: "50000",
+    },
+  ],
+};
+// -------------------------------------------------------------------------
+
+export async function run() {
+  const chainId = SupportedChainId.GNOSIS_CHAIN;
+  const wallet = await getWallet(chainId);
+
+  const sdk = new TradingSdk({
+    chainId,
+    signer: wallet,
+    appCode: APP_CODE,
+  });
+
+  const parameters: TradeParameters = {
+    kind: OrderKind.SELL,
+    amount: SELL_AMOUNT,
+    sellToken: SELL_TOKEN,
+    sellTokenDecimals: 18,
+    buyToken: BUY_TOKEN,
+    buyTokenDecimals: 18,
+  };
+
+  const metadataApi = new MetadataApi();
+  const appData = await metadataApi.generateAppDataDoc({
+    appCode: APP_CODE,
+    metadata: {
+      hooks: HOOKS,
+    },
+  });
+
+  // NOTE: `as any` bridges dual-package app-data type drift in this SDK RC (the standalone
+  // `@cowprotocol/app-data` schema vs the copy bundled inside `@cowprotocol/cow-sdk`). The
+  // runtime JSON is identical.
+  // Inspect exactly what will be committed on-chain (hash) and served off-chain (full doc).
+  const { appDataContent, appDataHex } = await metadataApi.getAppDataInfo(appData as any);
+  console.log("📦 appData doc:", JSON.stringify(appData, jsonReplacer, 2));
+  console.log("🧾 appData content (served to solvers):", appDataContent);
+  console.log("#️⃣  appData hash (committed in the order):", appDataHex);
+
+  console.log(`\nPosting order on Gnosis (owner=${wallet.address})...`);
+  const orderId = await sdk.postSwapOrder(parameters, { appData: appData as any });
+
+  console.log(
+    `✅ Order created: https://explorer.cow.fi/gc/orders/${orderId}?tab=overview`
+  );
+}