@zkproofport-app/sdk 0.2.14 → 0.2.16

package/dist/index.mjs

@@ -4342,26 +4342,33 @@ const CIRCUIT_SUPPORT_STATUS = Object.freeze({
     mdl_kr_region: 'planned',
 });
 /**
- * Where each circuit's verification key lives inside the `zkproofport/circuits`
- * repository, relative to its root.
+ * Where each circuit's verification key FILE lives inside the
+ * `zkproofport/circuits` repository, relative to its root.
  *
  * Off-chain verification needs the verification key and nothing else — no
  * circuit bytecode, no witness. The key is public by nature: it is what anyone
  * checking a proof must already have, and the Solidity verifiers deployed
  * on-chain embed the same key.
  *
+ * NOTE THE TRAILING `/vk` TWICE. In that repository `target/vk` is a DIRECTORY
+ * holding `vk`, `vk_hash` and `SHA256SUMS`; the key itself is `target/vk/vk`.
+ * These paths were first copied here from the mobile app, which keeps the
+ * directory and the filename as two fields and joins them — so taking only the
+ * directory produced a URL that answers 404, and the first browser to try
+ * off-chain verification said "Could not fetch the verification key (HTTP 404)".
+ *
  * Exhaustive over {@link CircuitId} on purpose. A new circuit whose key path is
  * not listed here fails to compile rather than failing at verification time,
  * where the only symptom would be a proof that cannot be checked.
  */
 const CIRCUIT_VK_PATHS = Object.freeze({
-    coinbase_attestation: 'coinbase-attestation/target/vk',
-    coinbase_country_attestation: 'coinbase-country-attestation/target/vk',
-    oidc_domain_attestation: 'oidc-domain-attestation/target/vk',
-    giwa_attestation: 'giwa-attestation/target/vk',
-    mdl_kr_ownership: 'mdl/kr-ownership/target/vk',
-    mdl_kr_age: 'mdl/kr-age/target/vk',
-    mdl_kr_region: 'mdl/kr-region/target/vk',
+    coinbase_attestation: 'coinbase-attestation/target/vk/vk',
+    coinbase_country_attestation: 'coinbase-country-attestation/target/vk/vk',
+    oidc_domain_attestation: 'oidc-domain-attestation/target/vk/vk',
+    giwa_attestation: 'giwa-attestation/target/vk/vk',
+    mdl_kr_ownership: 'mdl/kr-ownership/target/vk/vk',
+    mdl_kr_age: 'mdl/kr-age/target/vk/vk',
+    mdl_kr_region: 'mdl/kr-region/target/vk/vk',
 });
 /**
  * Every canonical circuit identifier, in declaration order.
@@ -4477,6 +4484,38 @@ const CIRCUITS_VK_BASE = 'https://raw.githubusercontent.com/zkproofport/circuits
 /** How long a fetched verification key is reused. Keys change only on a recompile. */
 const VK_CACHE_TTL_MS = 60 * 60 * 1000;
 const vkCache = new Map();
+/**
+ * Make sure a Node-shaped `Buffer` exists before Barretenberg is loaded.
+ *
+ * WHY THE SDK DOES THIS RATHER THAN THE CALLER. bb.js's own BROWSER build —
+ * not just its node build — converts field elements through `Buffer.alloc` and
+ * `buf.writeBigUInt64BE`. Browsers have no Buffer, and bundlers stopped
+ * polyfilling Node globals years ago, so in a browser the first verification
+ * dies with "r.writeBigUInt64BE is not a function" — a message that names
+ * nothing a caller could act on. Measured on the demo page, 2026-09-04, against
+ * a real GIWA proof.
+ *
+ * Leaving it to callers would mean every browser customer editing their
+ * bundler config to make an SDK method work, which is the configuration this
+ * SDK promises not to require.
+ *
+ * Deliberately narrow:
+ *  - It only fills a GAP. A real Buffer (Node, or a page that already has one)
+ *    is left alone, so nothing is shadowed by a lesser implementation.
+ *  - It checks for the METHOD, not just the global. A partial Buffer — which is
+ *    what several bundlers leave behind, and what the demo page actually had —
+ *    passes a `typeof Buffer` test and then fails inside Barretenberg.
+ */
+async function ensureBufferForBarretenberg() {
+    const existing = globalThis.Buffer;
+    if (existing?.alloc) {
+        const probe = existing.alloc(8);
+        if (typeof probe.writeBigUInt64BE === 'function')
+            return;
+    }
+    const { Buffer } = await import('buffer/');
+    globalThis.Buffer = Buffer;
+}
 /** @internal Hex string (with or without 0x) to bytes. */
 function hexToBytes(hex) {
     const clean = hex.startsWith('0x') || hex.startsWith('0X') ? hex.slice(2) : hex;
@@ -4586,6 +4625,8 @@ async function verifyProofOffChain(circuit, proof, publicInputs, options = {}) {
     //
     // The dynamic import is what keeps the cost off everyone else — a bundler
     // splits it out, and a caller who never verifies off-chain never loads it.
+    // Before bb.js, not after: its module-level code already reaches for Buffer.
+    await ensureBufferForBarretenberg();
     let bb;
     try {
         bb = await import('@aztec/bb.js');