@midnight-ntwrk/wallet-sdk-capabilities 4.0.0-beta.3 → 4.0.0-beta.4

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.
@@ -187,6 +187,15 @@ export declare const resolveProvingBackends: (configuration: DefaultProvingConfi
187
187
  */
188
188
  export declare const makeWasmProvingServices: (sinceVersion: ProtocolVersion.ProtocolVersion, configuration?: WasmProvingConfiguration) => ProvingServices<V9UnboundTransaction>;
189
189
  export declare const makeV9ServerProvingServiceEffect: (configuration: ServerProvingConfiguration) => ProvingServiceEffect<V9UnboundTransaction>;
190
+ /**
191
+ * Proves ledger-v9 transactions in this process.
192
+ *
193
+ * @remarks
194
+ * The ledger-v9 twin of `makeV8WasmProvingServiceEffect`: the same bundled prover, with ledger-v9's key material —
195
+ * circuit generation 10 ({@link WasmProver.makeV9KeyMaterialProvider}) — unless it is given key material of its own.
196
+ * @param configuration Optional key material override.
197
+ * @returns A backend that proves ledger-v9 transactions in-process.
198
+ */
190
199
  export declare const makeV9WasmProvingServiceEffect: (configuration?: WasmProvingConfiguration) => ProvingServiceEffect<V9UnboundTransaction>;
191
200
  export declare const makeSimulatorProvingServiceEffect: () => ProvingServiceEffect<ledger.ProofErasedTransaction>;
192
201
  export declare const makeDefaultProvingServiceEffect: (configuration: ServerProvingConfiguration) => ProvingServiceEffect<V9UnboundTransaction>;
@@ -135,9 +135,18 @@ export const makeV9ServerProvingServiceEffect = (configuration) => {
135
135
  url: configuration.provingServerUrl,
136
136
  }), Effect.map((client) => client.asProvingProvider()), fromV9ProvingProviderEffect);
137
137
  };
138
+ /**
139
+ * Proves ledger-v9 transactions in this process.
140
+ *
141
+ * @remarks
142
+ * The ledger-v9 twin of `makeV8WasmProvingServiceEffect`: the same bundled prover, with ledger-v9's key material —
143
+ * circuit generation 10 ({@link WasmProver.makeV9KeyMaterialProvider}) — unless it is given key material of its own.
144
+ * @param configuration Optional key material override.
145
+ * @returns A backend that proves ledger-v9 transactions in-process.
146
+ */
138
147
  export const makeV9WasmProvingServiceEffect = (configuration) => {
139
148
  return pipe(WasmProver.create({
140
- keyMaterialProvider: configuration?.keyMaterialProvider ?? WasmProver.makeDefaultKeyMaterialProvider(),
149
+ keyMaterialProvider: configuration?.keyMaterialProvider ?? WasmProver.makeV9KeyMaterialProvider(),
141
150
  }), Effect.map((prover) => prover.asProvingProvider()), fromV9ProvingProviderEffect);
142
151
  };
143
152
  export const makeSimulatorProvingServiceEffect = () => {
@@ -43,10 +43,10 @@ export declare const makeV8ServerProvingServiceEffect: (configuration: ServerPro
43
43
  * Proves ledger-v8 transactions in this process.
44
44
  *
45
45
  * @remarks
46
- * The zkir runtime the bundled prover drives is shared by both ledger lines, so there is nothing version-specific about
47
- * the proving loop — and the key material ledger-v8 accepts turns out to be the same line the current one uses, which
48
- * is why no key-material override is applied here. See the ledger-v8 spike in `prover-client`'s
49
- * `v8WasmProver.integration.test.ts` for the evidence.
46
+ * The zkir runtime the bundled prover drives is shared by both ledger versions, so there is nothing version-specific
47
+ * about the proving loop — but there is about the key material. Ledger-v8's circuits are generation 9 and ledger-v9's
48
+ * generation 10, and a node rejects a Dust spend proved with the other version's, so this backend reads ledger-v8's
49
+ * own ({@link WasmProver.makeV8KeyMaterialProvider}) unless it is given key material of its own.
50
50
  * @param configuration Optional key material override.
51
51
  * @returns A backend that proves ledger-v8 transactions in-process.
52
52
  */
@@ -59,13 +59,13 @@ export const makeV8ServerProvingServiceEffect = (configuration) => pipe(HttpProv
59
59
  * Proves ledger-v8 transactions in this process.
60
60
  *
61
61
  * @remarks
62
- * The zkir runtime the bundled prover drives is shared by both ledger lines, so there is nothing version-specific about
63
- * the proving loop — and the key material ledger-v8 accepts turns out to be the same line the current one uses, which
64
- * is why no key-material override is applied here. See the ledger-v8 spike in `prover-client`'s
65
- * `v8WasmProver.integration.test.ts` for the evidence.
62
+ * The zkir runtime the bundled prover drives is shared by both ledger versions, so there is nothing version-specific
63
+ * about the proving loop — but there is about the key material. Ledger-v8's circuits are generation 9 and ledger-v9's
64
+ * generation 10, and a node rejects a Dust spend proved with the other version's, so this backend reads ledger-v8's
65
+ * own ({@link WasmProver.makeV8KeyMaterialProvider}) unless it is given key material of its own.
66
66
  * @param configuration Optional key material override.
67
67
  * @returns A backend that proves ledger-v8 transactions in-process.
68
68
  */
69
69
  export const makeV8WasmProvingServiceEffect = (configuration) => pipe(WasmProver.create({
70
- keyMaterialProvider: configuration?.keyMaterialProvider ?? WasmProver.makeDefaultKeyMaterialProvider(),
70
+ keyMaterialProvider: configuration?.keyMaterialProvider ?? WasmProver.makeV8KeyMaterialProvider(),
71
71
  }), Effect.map((prover) => prover.asProvingProvider()), fromV8ProvingProviderEffect);
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@midnight-ntwrk/wallet-sdk-capabilities",
3
- "version": "4.0.0-beta.3",
3
+ "version": "4.0.0-beta.4",
4
4
  "type": "module",
5
5
  "main": "./dist/index.js",
6
6
  "module": "./dist/index.js",
@@ -64,23 +64,23 @@
64
64
  "dependencies": {
65
65
  "@midnight-ntwrk/ledger-v8": "^8.1.0",
66
66
  "@midnight-ntwrk/zkir-v2": "^2.1.0",
67
- "@midnightntwrk/ledger-v9": "1.0.0-rc.4",
68
- "@midnight-ntwrk/wallet-sdk-abstractions": "3.0.0-beta.1",
67
+ "@midnightntwrk/ledger-v9": "1.0.0-rc.5",
68
+ "@midnight-ntwrk/wallet-sdk-abstractions": "3.0.0-beta.2",
69
69
  "@midnight-ntwrk/wallet-sdk-indexer-client": "2.0.0-beta.2",
70
- "@midnight-ntwrk/wallet-sdk-node-client": "2.0.0-beta.3",
71
- "@midnight-ntwrk/wallet-sdk-prover-client": "2.0.0-beta.3",
70
+ "@midnight-ntwrk/wallet-sdk-node-client": "2.0.0-beta.4",
71
+ "@midnight-ntwrk/wallet-sdk-prover-client": "2.0.0-beta.4",
72
72
  "@midnight-ntwrk/wallet-sdk-utilities": "1.2.2-beta.0",
73
73
  "effect": "^3.19.19",
74
74
  "rxjs": "^7.8.2"
75
75
  },
76
76
  "devDependencies": {
77
- "@effect/cluster": "0.59.0",
78
- "@effect/experimental": "0.60.0",
79
- "@effect/platform": "0.96.2",
80
- "@effect/platform-node": "0.107.0",
81
- "@effect/rpc": "0.75.1",
82
- "@effect/sql": "0.51.1",
83
- "@effect/workflow": "0.18.2",
77
+ "@effect/cluster": "0.60.2",
78
+ "@effect/experimental": "0.61.1",
79
+ "@effect/platform": "0.97.1",
80
+ "@effect/platform-node": "0.108.1",
81
+ "@effect/rpc": "0.76.2",
82
+ "@effect/sql": "0.52.1",
83
+ "@effect/workflow": "0.19.1",
84
84
  "@midnight-ntwrk/wallet-sdk-state-translation": "workspace:^"
85
85
  },
86
86
  "scripts": {