@layerzerolabs/protocol-stellar-v2 0.2.60 → 0.2.62

package/docs/layerzero-v2-on-stellar.md

@@ -139,7 +139,8 @@ Base framework for building cross-chain applications.
 
 Standardized cross-chain token bridge implementation.
 
-**Location**: `contracts/oapps/oft/`
+**Location**: `contracts/oapps/oft-core/` (core traits) and `contracts/oapps/oft/`
+(token types and extensions)
 
 **Key traits**:
 
@@ -197,11 +198,15 @@ sequenceDiagram
     participant OApp
 
     rect rgb(240, 248, 255)
-        Note over DVN, Endpoint: Step 1: Verification
+        Note over DVN, ReceiveLib: Step 1a: DVN Attestation
         Note over DVN: Monitor source chain for PacketSent
         Note over DVN: Wait for block confirmations
-        DVN->>ReceiveLib: verify(packet_header, payload_hash)
+        DVN->>ReceiveLib: verify(dvn, packet_header, payload_hash, confirmations)
         Note over ReceiveLib: Record DVN attestation
+        Note over ReceiveLib: (repeat for each DVN in quorum)
+
+        Note over ReceiveLib, Endpoint: Step 1b: Commit (permissionless)
+        ReceiveLib->>ReceiveLib: commit_verification(packet_header, payload_hash)
         Note over ReceiveLib: Check if quorum reached
         ReceiveLib->>Endpoint: verify(origin, receiver, payload_hash)
         Note over Endpoint: Store payload_hash
@@ -372,17 +377,30 @@ EVM DVN Flow (external calls):
 The self-call pattern for configuration fails on Soroban because the DVN cannot
 call itself. The solution is to implement DVN as an **Abstract Account** (custom
 account). Soroban's custom account interface allows contracts to define
-authorization logic via `__check_auth`. Instead of self-calling, the DVN
-authorizes calls made on its behalf—both self-configuration and external calls:
+authorization logic via `__check_auth`. The DVN's `__check_auth` only authorizes
+**self-calls** (calls targeting the DVN contract itself). For self-configuration,
+the multisig quorum directly authorizes calls to the DVN's own functions (e.g.,
+`set_admin`, `set_signer`). For external calls like `ULN302.verify()`, the DVN
+exposes an `execute_transaction(calls)` function that is itself a self-call
+validated by `__check_auth`, then dispatches each call to the target contract:
 
 ```
-Stellar DVN Flow (Abstract Account):
+Stellar DVN Flow (self-configuration via Abstract Account):
 ┌─────────────┐    ┌─────────────┐
-│    Admin    │───►│   ULN302    │  DVN authorizes via __check_auth
-│  (submits   │    │  .verify()  │  (signature verification happens
-│   tx with   │    │             │   in the auth context, not as
-│   DVN auth) │    │             │   a separate call)
+│    Admin    │───►│     DVN     │  __check_auth validates multisig
+│  (submits   │    │ .set_admin()│  for the self-call
+│   tx with   │    │             │
+│   DVN auth) │    │             │
 └─────────────┘    └─────────────┘
+
+Stellar DVN Flow (external calls via execute_transaction):
+┌─────────────┐    ┌─────────────┐    ┌─────────────┐
+│    Admin    │───►│     DVN     │───►│   ULN302    │
+│  (submits   │    │  .execute_  │    │  .verify()  │
+│   tx with   │    │  transaction│    │             │
+│   DVN auth) │    │ (__check_   │    │             │
+│             │    │  auth)      │    │             │
+└─────────────┘    └─────────────┘    └─────────────┘
 ```
 
 The DVN's `__check_auth` validates:

package/package.json

@@ -1,15 +1,15 @@
 {
   "name": "@layerzerolabs/protocol-stellar-v2",
-  "version": "0.2.60",
+  "version": "0.2.62",
   "private": false,
   "license": "LZBL-1.2",
   "devDependencies": {
     "@types/node": "^22.18.6",
     "tsx": "^4.19.3",
     "typescript": "^5.8.2",
-    "@layerzerolabs/common-node-utils": "0.2.60",
-    "@layerzerolabs/stellar-ts-bindings-gen": "0.2.60",
-    "@layerzerolabs/vm-tooling-stellar": "0.2.60"
+    "@layerzerolabs/vm-tooling-stellar": "0.2.62",
+    "@layerzerolabs/stellar-ts-bindings-gen": "0.2.62",
+    "@layerzerolabs/common-node-utils": "0.2.62"
   },
   "publishConfig": {
     "access": "restricted",