@zkp2p/sdk 0.3.1 → 0.3.2

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.
package/README.md CHANGED
@@ -12,7 +12,7 @@ Current version: `0.3.1`
12
12
 
13
13
  - Build maker, taker, vault, and embedded ramp flows from one client.
14
14
  - Read live protocol state directly from ProtocolViewer instead of waiting on indexer sync.
15
- - Route against the upgraded escrow/orchestrator stack while preserving historical deposit visibility.
15
+ - Route against the EscrowV2/OrchestratorV2 stack legacy V1 resolution has been removed.
16
16
  - Use prepareable write methods for smart accounts, relayers, gas estimation, and batching.
17
17
  - Keep advanced analytics, fund activity history, and vault stats behind `client.indexer.*`.
18
18
 
@@ -28,7 +28,7 @@ Current version: `0.3.1`
28
28
 
29
29
  - RPC-first reads: primary reads use ProtocolViewer and on-chain fallbacks, so `getDeposits()`, `getDeposit()`, `getIntents()`, `getIntent()`, and the `getPv*` methods are not blocked on indexer lag.
30
30
  - Indexer for history and filtering: use `client.indexer.*` for pagination, historical volumes, fund activities, daily snapshots, and vault analytics.
31
- - Current-stack routing: the client resolves against the upgraded escrow and orchestrator contracts, with historical escrow lookups available for reads and legacy deposits.
31
+ - V2-only routing: the client resolves against EscrowV2 and OrchestratorV2. Legacy V1 escrow/orchestrator fallbacks have been removed from both read and write paths.
32
32
  - Modular internals: intent, vault, and ProtocolViewer logic are extracted into `IntentOperations`, `VaultOperations`, and `ProtocolViewerReader`, keeping `Zkp2pClient` focused on orchestration.
33
33
  - App-level rollout control: the SDK is capability-based. Product gating and phase flags belong in your app layer, not inside transaction helpers.
34
34
 
@@ -0,0 +1,9 @@
1
+ var __defProp = Object.defineProperty;
2
+ var __export = (target, all) => {
3
+ for (var name in all)
4
+ __defProp(target, name, { get: all[name], enumerable: true });
5
+ };
6
+
7
+ export { __export };
8
+ //# sourceMappingURL=chunk-J5LGTIGS.mjs.map
9
+ //# sourceMappingURL=chunk-J5LGTIGS.mjs.map
@@ -0,0 +1 @@
1
+ {"version":3,"sources":[],"names":[],"mappings":"","file":"chunk-J5LGTIGS.mjs"}