@cardanowall/sdk-ts 0.4.0 → 0.5.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -423,13 +423,23 @@ interface RecordsListResponse {
423
423
  interface AccountBalance {
424
424
  readonly balanceUsdMicros: string;
425
425
  }
426
+ /**
427
+ * Request body for the hosted verify endpoint.
428
+ *
429
+ * The endpoint is a PUBLIC verifier — structural validation plus record-level
430
+ * signature verification over public chain data. It accepts no decryption
431
+ * credentials: a body carrying any is rejected with 400 validation-failed,
432
+ * and sealed (enc-bearing) items report as unverifiable without decryption.
433
+ * Recipient verification (sealed-envelope decrypt + plaintext-hash recheck)
434
+ * runs locally — use the `verifier` module's `decryption` input, which never
435
+ * leaves the process.
436
+ *
437
+ * `fetch_content` is the master content-fetch switch (item URIs and Merkle
438
+ * leaves lists alike). The server defaults it to `true`; pass `false` to skip
439
+ * content re-fetching — affected claims then report `not_checked`.
440
+ */
426
441
  interface PoeVerifyInput {
427
- readonly verify_uris?: boolean;
428
- readonly decryption?: ReadonlyArray<{
429
- readonly item_idx: number;
430
- readonly recipient_secret_key?: string;
431
- readonly passphrase?: string;
432
- }>;
442
+ readonly fetch_content?: boolean;
433
443
  }
434
444
  /**
435
445
  * Pluggable Ed25519 signer for the high-level publish helpers. The SDK does
@@ -423,13 +423,23 @@ interface RecordsListResponse {
423
423
  interface AccountBalance {
424
424
  readonly balanceUsdMicros: string;
425
425
  }
426
+ /**
427
+ * Request body for the hosted verify endpoint.
428
+ *
429
+ * The endpoint is a PUBLIC verifier — structural validation plus record-level
430
+ * signature verification over public chain data. It accepts no decryption
431
+ * credentials: a body carrying any is rejected with 400 validation-failed,
432
+ * and sealed (enc-bearing) items report as unverifiable without decryption.
433
+ * Recipient verification (sealed-envelope decrypt + plaintext-hash recheck)
434
+ * runs locally — use the `verifier` module's `decryption` input, which never
435
+ * leaves the process.
436
+ *
437
+ * `fetch_content` is the master content-fetch switch (item URIs and Merkle
438
+ * leaves lists alike). The server defaults it to `true`; pass `false` to skip
439
+ * content re-fetching — affected claims then report `not_checked`.
440
+ */
426
441
  interface PoeVerifyInput {
427
- readonly verify_uris?: boolean;
428
- readonly decryption?: ReadonlyArray<{
429
- readonly item_idx: number;
430
- readonly recipient_secret_key?: string;
431
- readonly passphrase?: string;
432
- }>;
442
+ readonly fetch_content?: boolean;
433
443
  }
434
444
  /**
435
445
  * Pluggable Ed25519 signer for the high-level publish helpers. The SDK does
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@cardanowall/sdk-ts",
3
- "version": "0.4.0",
3
+ "version": "0.5.0",
4
4
  "type": "module",
5
5
  "description": "CardanoWall TypeScript SDK — standalone Label 309 verifier + envelope helpers + HTTP client (browser-safe).",
6
6
  "license": "Apache-2.0",
@@ -96,8 +96,8 @@
96
96
  "cbor2": "^2.3.0",
97
97
  "hash-wasm": "4.12.0",
98
98
  "zod": "^4.4.3",
99
- "@cardanowall/crypto-core": "0.4.0",
100
- "@cardanowall/poe-standard": "0.4.0"
99
+ "@cardanowall/poe-standard": "0.5.0",
100
+ "@cardanowall/crypto-core": "0.5.0"
101
101
  },
102
102
  "devDependencies": {
103
103
  "tsup": "^8.5.1"