@zkproofport-app/sdk 0.5.0-beta.1 → 0.5.0-beta.3

package/dist/offChainVerifier.d.ts

@@ -35,6 +35,7 @@
  * two pieces, so nothing is joined back here.
  */
 import { type CircuitId } from './circuits';
+import { type OidcRequestContext } from '@zkproofport-app/core';
 export interface OffChainVerifyResult {
     valid: boolean;
     error?: string;
@@ -48,6 +49,12 @@ export interface OffChainVerifyOptions {
     verificationKey?: Uint8Array;
     /** Milliseconds before the fetch is abandoned. Default 30000. */
     timeoutMs?: number;
+    /**
+     * For `oidc_domain_attestation`: the request the proof answers. A proof made
+     * with a request-bound nonce (the app path) must be bound to exactly this
+     * scope and requestId. See core's `checkOidcPolicy`.
+     */
+    request?: OidcRequestContext;
 }
 /**
  * Verify a proof off-chain, against its verification key.
@@ -55,6 +62,12 @@ export interface OffChainVerifyOptions {
  * Needs no setup from the caller: the verifier ships with this SDK and is
  * loaded on first use.
  *
+ * For `oidc_domain_attestation` it first checks the token's audience, nonce and
+ * time (core's `checkOidcPolicy`, against `options.request` when given) and the
+ * proof's RSA key against the provider's published JWKS (core's
+ * `checkOidcProviderKey`); any refusal, or a JWKS that cannot be fetched, is
+ * `{ valid: false }`.
+ *
  * @param circuit - Canonical circuit identifier
  * @param proof - Proof bytes as hex, WITHOUT public inputs (as the relay sends it)
  * @param publicInputs - Public inputs as hex strings, in circuit order

package/dist/types.d.ts

@@ -350,6 +350,14 @@ export interface ProofportConfig {
     relayUrl?: string;
     /** Custom verifier contract addresses per circuit type (overrides defaults) */
     verifiers?: Partial<Record<CircuitType, VerifierContract>>;
+    /**
+     * @internal Which environment's chains a circuit with no configured
+     * verifier is verified on (the pinned verifier on that chain).
+     * `ProofportSDK.create(env)` sets it; set it yourself only alongside a custom
+     * `relayUrl`, e.g. a local relay on a LAN address. Without it, and without a
+     * configured verifier, verification fails rather than guessing.
+     */
+    environment?: SDKEnvironment;
 }
 /**
  * Parsed deep link URL components.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@zkproofport-app/sdk",
-  "version": "0.5.0-beta.1",
+  "version": "0.5.0-beta.3",
   "description": "ZKProofport SDK for requesting zero-knowledge proofs from the ZKProofport mobile app and verifying them on-chain",
   "main": "dist/index.js",
   "module": "dist/index.esm.js",
@@ -42,7 +42,7 @@
     "buffer": "^6.0.3",
     "qrcode": "^1.5.3",
     "socket.io-client": "^4.8.0",
-    "@zkproofport-app/core": "0.1.2"
+    "@zkproofport-app/core": "0.3.0"
   },
   "devDependencies": {
     "@rollup/plugin-commonjs": "^25.0.7",