@zkp2p/zkp2p-attestation 1.6.2 → 2.0.0

package/CHANGELOG.md

@@ -1,5 +1,16 @@
 # Changelog
 
+## Unreleased
+
+## 2.0.0
+
+- Hard-cut the preprod hostname to the isolated preprod enclave PCR8. Production remains pinned only at `attestation-service.zkp2p.xyz`.
+- BREAKING: Buyer TEE Zelle verification now accepts only `platform: "zelle"` with `transfer_zelle_bofa`, `transfer_zelle_chase`, or `transfer_zelle_citi`. All three actions attest the generic Zelle payment-method hash.
+
+## 1.6.3
+
+- Bind the default global `fetch` fallback to `globalThis` so browser and extension callers that rely on SDK defaults do not hit receiver-sensitive `Illegal invocation` failures. Caller-provided `fetch` overrides are still used unchanged.
+
 ## 1.6.2
 
 - Default the production environment to `https://attestation-service.zkp2p.xyz` and bundle a production PCR8 pin for that hostname. The historical `attestation-service-preprod.zkp2p.xyz` hostname remains pinned to the same production PCR8.
@@ -11,7 +22,7 @@
 
 ## 1.6.0
 
-- Add generic buyer TEE Zelle typing for `platform: "zelle"` and bank-specific action types `transfer_zelle_bofa`, `transfer_zelle_chase`, and `transfer_zelle_citi`; direct bank-specific Zelle routes and method hashes remain legacy drain-only.
+- Add generic buyer TEE Zelle typing for `platform: "zelle"` and bank-specific action types `transfer_zelle_bofa`, `transfer_zelle_chase`, and `transfer_zelle_citi`.
 
 ## 1.5.1
 

package/README.md

@@ -31,7 +31,7 @@ Environment defaults:
 | `staging` | `https://attestation-service-staging.zkp2p.xyz` | bundled staging pin |
 | `production` | `https://attestation-service.zkp2p.xyz` | bundled production pin |
 
-Callers can still pass `attestationServiceUrl` and `trust.expectedPcr8Hex` directly. Explicit trust pins always win. The historical `https://attestation-service-preprod.zkp2p.xyz` hostname remains pinned to the same production PCR8 while it continues to serve the Nitro prod deployment.
+Callers can still pass `attestationServiceUrl` and `trust.expectedPcr8Hex` directly. Explicit trust pins always win. The preprod hostname is pinned to the isolated preprod enclave; it is not a production alias.
 
 ## Fast Path
 
@@ -75,7 +75,7 @@ const verifiedCredentialBundle = verifySellerCredentialBundle(credentialBundle,
 });
 ```
 
-Venmo, Cash App, PayPal, and Zelle still require a top-level `payeeId`; existing callers can keep using the same call shape:
+Venmo, Cash App, and PayPal still require a top-level `payeeId`; existing callers can keep using the same call shape:
 
 ```ts
 const encryptedUpload = await nitro.createEncryptedSellerCredentialUpload({
@@ -88,8 +88,6 @@ Venmo seller uploads can use either the existing session material or Google OAut
 
 PayPal Gmail OAuth seller uploads use the same app-selection model. Pass the seller PayPal email as `payeeId` and use `sessionMaterial: { credentialSource: "google_oauth", authorizationCode, redirectUri }`; the service validates Gmail access against paypal.com DKIM-signed payment receipts. To onboard through a partner-owned Google OAuth app, include `oauthClient: { clientId, clientSecret }` inside the encrypted `sessionMaterial`. The PayPal partner client secret is handled as seller credential material: it rides only in the compact JWE upload plaintext, is sealed with the Gmail refresh token in the KMS-envelope seller credential bundle, and is reused only to refresh that seller's Gmail access token.
 
-Zelle seller uploads use the same Gmail OAuth shape with `platform: "zelle"` and a top-level `payeeId` for the seller's Zelle recipient identifier. The service validates the OAuth mailbox by finding at least one DKIM-verified incoming Zelle receipt from a supported bank/Zelle sender, then later resolves `/seller/verify/zelle` by matching `txId` against the received receipt's transaction, confirmation, reference, or payment id. Seller Zelle attestations use the generic on-chain payment method `keccak256("zelle")`; receipt providers such as Chase, Citi, and Bank of America are metadata only.
-
 Buyer TEE requests use the same attested upload key and compact JWE envelope. The typed helper encrypts the captured
 session material, posts `{ encryptedSessionMaterial, params, chainId, intent }` to
 `POST /buyer/verify/:platform/:actionType`, unwraps the service envelope, and returns a typed `AttestationOutput`.
@@ -150,18 +148,14 @@ Buyer TEE platform matrix:
 | `monzo` | `transfer_monzo` | `Authorization` | `TX_ID` |
 | `wise` | `transfer_wise` | `Cookie` or `X-Access-Token` | `PROFILE_ID`, `TRANSACTION_ID` |
 | `revolut` | `transfer_revolut` | `Cookie`, `x-device-id` | `index` |
-| `citi` | `transfer_zelle` | `Cookie` | `index` |
 | `chime` | `transfer_chime` | `Cookie`, `body` | `{}` |
-| `chase` | `transfer_zelle` | `Cookie`, `x-jpmc-channel`, `x-jpmc-csrf-token`, `Referer`, `Origin` | `index` |
-| `bankofamerica` | `transfer_zelle` | `Cookie` | `index` |
 | `zelle` | `transfer_zelle_bofa` | `Cookie` | `index` |
 | `zelle` | `transfer_zelle_chase` | `Cookie`, `x-jpmc-channel`, `x-jpmc-csrf-token`, `Referer`, `Origin` | `index` |
 | `zelle` | `transfer_zelle_citi` | `Cookie` | `index` |
 | `paypal` | `transfer_paypal` | `Cookie` | `PAYMENT_ID` |
 
-The generic Zelle buyer routes use bank-specific action types and attest `intent.paymentMethod = hashUtf8("zelle")`.
-New Zelle deposits and intents should use generic `zelle`. Direct bank-specific routes remain available only for
-legacy drain support with `hashUtf8("zelle-citi")`, `hashUtf8("zelle-chase")`, or `hashUtf8("zelle-bofa")`.
+Zelle buyer verification uses only `platform: "zelle"` with bank-specific action types. Every Zelle action attests
+`intent.paymentMethod = hashUtf8("zelle")`; direct bank-specific platforms are unsupported.
 
 Per-platform session-material types require these headers using the canonical names shown above while still allowing
 additional captured headers. Captured request bodies are session material because they can contain sensitive data and
@@ -215,7 +209,7 @@ For Cash App identity, pass the replayable Cash App session cookie as `sessionMa
 
 Buyer TEE and identity expose discriminated unions keyed by `platform` and `actionType`, including per-platform
 `params`, so invalid pairings fail during TypeScript compilation. Seller credential upload keeps its existing
-platform narrowing (`wise` derives payee id from the credential; Venmo, Cash App, PayPal, and Zelle require `payeeId`) but
+platform narrowing (`wise` derives payee id from the credential; Venmo, Cash App, and PayPal require `payeeId`) but
 does not add exhaustive `sessionMaterial` typing: each seller platform can accept multiple credential sources, such as
 cookie headers or Google OAuth with optional partner OAuth client material, and encoding all combinations would make
 the SDK brittle without improving the wire contract.

package/dist/cli/verify.js

@@ -3809,11 +3809,16 @@ async function wrapCryptoFailure(promise, code, message) {
 
 // src/crypto/env.ts
 function resolveFetch(fetchOverride) {
-  const fetcher = fetchOverride ?? globalThis.fetch;
-  if (typeof fetcher !== "function") {
+  if (fetchOverride !== void 0) {
+    if (typeof fetchOverride !== "function") {
+      fail("CRYPTO_UNAVAILABLE", "fetch is unavailable; pass a fetch implementation");
+    }
+    return fetchOverride;
+  }
+  if (typeof globalThis.fetch !== "function") {
     fail("CRYPTO_UNAVAILABLE", "fetch is unavailable; pass a fetch implementation");
   }
-  return fetcher;
+  return globalThis.fetch.bind(globalThis);
 }
 function resolveSubtle(subtleOverride) {
   const subtle = subtleOverride ?? globalThis.crypto?.subtle;
@@ -4505,9 +4510,10 @@ var DEFAULT_TIMEOUT_MS = 1e4;
 // src/trust/pins.ts
 var STAGING_PCR8 = "5636e3bd96f847cf12cfd9de7faa8cad0e6fa00962ce16ba185f8e5ea57105abb3cc9cc34f1e1e4de3444ceabcca7485";
 var PRODUCTION_PCR8 = "41a4ae0b9b96752cab5addb7d22689b3070e564e29f90a54316fa33fa38ea51387a6e887ea4f5a4b0cc34f69cea3f40e";
+var PREPROD_PCR8 = "5453c5bfb7d040285be5ba9af142f4fbdd9685d082f244b66c62bf7b22d8d02a638fa2e02b9a6fe8877953a9429209e0";
 var DEFAULT_EXPECTED_PCR8_BY_HOST = {
   "attestation-service-staging.zkp2p.xyz": normalizePcr8Pin(STAGING_PCR8, "bundled staging PCR8"),
-  "attestation-service-preprod.zkp2p.xyz": normalizePcr8Pin(PRODUCTION_PCR8, "bundled production PCR8"),
+  "attestation-service-preprod.zkp2p.xyz": normalizePcr8Pin(PREPROD_PCR8, "bundled preprod PCR8"),
   "attestation-service.zkp2p.xyz": normalizePcr8Pin(PRODUCTION_PCR8, "bundled production PCR8")
 };