@zkp2p/zkp2p-attestation 1.4.0 → 1.5.0

package/CHANGELOG.md

@@ -1,5 +1,10 @@
 # Changelog
 
+## 1.5.0
+
+- Change Venmo identity registration to require the captured stories URL in session material. Venmo identity session material now requires `url`, `params` only requires `SENDER_ID`, and `params.SENDER_ID` must match the URL `externalId`.
+- Require `callerAddress` on identity attestation requests and bind it into the signed `IdentityAttestation`; `verifyIdentityAttestation` now requires `expectedCallerAddress`.
+
 ## 1.4.0
 
 - Add typed identity flow helpers: `encryptIdentitySessionMaterial`, `createEncryptedIdentitySessionMaterial`, and `requestIdentityAttestation`.

package/README.md

@@ -160,15 +160,16 @@ are encrypted before being sent to the service.
 
 Identity requests use the same attested upload key and compact JWE plaintext shape as buyer TEE, but with a narrower
 platform/action matrix. The typed helper encrypts captured session material, posts
-`{ platform, actionType, encryptedSessionMaterial, params }` to `POST /identity`, unwraps the service response, and
+`{ platform, actionType, callerAddress, encryptedSessionMaterial, params }` to `POST /identity`, unwraps the service response, and
 returns an `IdentityAttestationOutput`. `verifyIdentityAttestation` checks the EIP-712 signature, trusted signer,
-platform/action binding, expected payee hash, canonical identity `dataHash`, and `validUntil`, then returns normalized
-identity details.
+platform/action binding, expected caller address, expected payee hash, canonical identity `dataHash`, and `validUntil`,
+then returns normalized identity details.
 
 ```ts
 const identityPayload = await nitro.requestIdentityAttestation({
   platform: "wise",
   actionType: "register_wise",
+  callerAddress: "0x0000000000000000000000000000000000000002",
   sessionMaterial: {
     Cookie: "<captured-cookie-header>",
     "X-Access-Token": "<captured-token>",
@@ -180,6 +181,7 @@ const identity = verifyIdentityAttestation(identityPayload, {
   trustedSigners,
   expectedPlatform: "wise",
   expectedActionType: "register_wise",
+  expectedCallerAddress: "0x0000000000000000000000000000000000000002",
   expectedPayeeIdHash: hashUtf8("<wise-recipient-id>"),
 });
 // identity: { payeeIdHash, payeeId, username, metadata, ... }
@@ -189,10 +191,14 @@ Identity platform matrix:
 
 | Platform | `actionType` | Required encrypted session material | Public params fields |
 |---|---|---|---|
-| `venmo` | `register_venmo` | `Cookie` | `SENDER_ID`, `index` |
+| `venmo` | `register_venmo` | `url`, `Cookie` | `SENDER_ID` |
 | `paypal` | `register_paypal` | `Cookie` | `{}` |
 | `wise` | `register_wise` | `Cookie`, `X-Access-Token` | `PROFILE_ID` |
 
+For Venmo identity, pass the captured `https://account.venmo.com/api/stories?feedType=me&externalId=...` request URL
+inside encrypted `sessionMaterial.url`; the service validates that `params.SENDER_ID` matches the URL `externalId` and
+that Venmo returns a valid stories response with an explicit `stories` array.
+
 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, and PayPal require `payeeId`) but

package/dist/cli/verify.js

@@ -4672,7 +4672,7 @@ Options:
   --expected-pcr8 <hex>       Strict PCR8 pin
   --expected-signer <addr>    Strict signer pin for --verify-signature
   --expected-verifying-contract <addr>  Strict verifyingContract pin
-  --verify-signature <path>   Optional path to a prior /verify or /seller/verify JSON response
+  --verify-signature <path>   Optional path to a prior buyer or seller verify JSON response
   --help                      Show this help text
 `);
 }