@zkproofport-app/sdk 0.4.2 → 0.4.3

package/README.md

@@ -477,6 +477,8 @@ const relay = await sdk.createRelayRequest('coinbase_attestation', {
 
 Every field of the third argument is optional: `message`, `dappName` and `dappIcon` are shown to the user in the ZKProofport app, `nonce` is a value of your own choosing that the relay refuses to accept twice, and `returnScheme` is described next.
 
+The relay never reads your circuit inputs. So that ZKProofport can count requests per app, the SDK also sends `scope` alongside them, unchanged. The proof itself uses the scope in your inputs.
+
 #### Switching back: `returnScheme`
 
 When ZKProofport finishes a proof, the user is sitting in the ZKProofport app. `returnScheme` answers one question: **which app should come back to the foreground?**

package/dist/index.esm.js

@@ -5989,6 +5989,13 @@ class ProofportSDK {
             inputs,
             challenge,
         };
+        // The relay never reads `inputs`, so the scope is also sent on the envelope,
+        // where the relay counts requests per scope. The app proves the scope inside
+        // `inputs` and uses the envelope copy only when `inputs` has none; both are
+        // the same string here.
+        const scope = inputs.scope;
+        if (typeof scope === 'string' && scope.length > 0)
+            body.scope = scope;
         // Sign challenge for circuits that require wallet signature
         if (needsSignature && this.signer) {
             body.signature = await this.signer.signMessage(challenge);