Merge pull request #113 from ChainSafe/irubido/updateWebZJSWalletComments

webzjs-wallet description comments update

Author: irubido

crates/webzjs-wallet/src/bindgen/wallet.rs

@@ -79,15 +79,19 @@ pub type NoteRef = <MemoryWalletDb<Network> as InputSource>::NoteRef;
 /// The proposal should be presented to the user for review before being authorized.
 ///
 /// To authorize the transaction the caller must currently provide the seed phrase and account index of the account that will be used to sign the transaction. This method also perform the SNARK proving which is an expensive operation and performed in parallel by a series of WebWorkers.
-/// Note: Handing the sensitive key material this way is not recommended for production applications. Upcoming changes to how proposals are authorized will allow separation of proof generation and signing but currently these are coupled.
 ///
 /// Finally, A transaction can be sent to the network by calling `send_authorized_transactions` with the list of transaction IDs that were generated by the authorization step.
 ///
+/// ## PCZT Transactions
+///
+/// PCZT (Partially Constructed Zcash Transaction)
+///
+/// 1. **`pczt_create`** - Creates a PCZT which designates how funds from this account can be spent to realize the requested transfer (does NOT sign, generate proofs, or send)
+/// 2. **`pczt_sign`** - Signs the PCZT using USK (should be done in secure environment)
+/// 3. **`pczt_prove`** - Creates and inserts proofs for the PCZT
+///
 /// The full flow looks like
-/// ```javascript
-/// const proposal = wallet.propose_transfer(1, "...", 100000000);
-/// const authorized_txns = wallet.create_proposed_transactions(proposal, "...", 1);
-/// await wallet.send_authorized_transactions(authorized_txns);
+/// The full PCZT flow: `pczt_create` → `pczt_sign` → `pczt_prove` → `pczt_send`
 /// ```
 ///
 #[wasm_bindgen]