No changes in wallet-core

wallet-core/src/transaction.rs

@@ -4,8 +4,7 @@
 //
 // Copyright (c) DUSK NETWORK. All rights reserved.
 
-//! Implementations of basic wallet functionalities to create phoenix
-//! transactions.
+//! Implementations of basic wallet functionalities to create transactions.
 
 use alloc::vec::Vec;
 
@@ -30,7 +29,16 @@ use execution_core::{
     BlsScalar, ContractId, Error, JubJubScalar,
 };
 
-/// Generate a phoenix-transaction with a given prover.
+/// An unproven-transaction is nearly identical to a [`PhoenixTransaction`] with
+/// the only difference being that it carries a serialized [`TxCircuitVec`]
+/// instead of the proof bytes.
+/// This way it is possible to delegate the proof generation of the
+/// [`TxCircuitVec`] after the unproven transaction was created while at the
+/// same time ensuring non-malleability of the transaction, as the transaction's
+/// payload-hash is part of the public inputs of the circuit.
+/// Once the proof is generated from the [`TxCircuitVec`] bytes, it can
+/// replace the serialized circuit in the transaction by calling
+/// [`Transaction::replace_proof`].
 ///
 /// # Errors
 /// The creation of a transaction is not possible and will error if:
@@ -40,7 +48,6 @@ use execution_core::{
 /// - the `inputs` vector contains duplicate `Note`s
 /// - the `Prove` trait is implemented incorrectly
 /// - the Memo provided with `data` is too large
-/// - the transaction-data is incorrect
 #[allow(clippy::too_many_arguments)]
 pub fn phoenix<R: RngCore + CryptoRng, P: Prove>(
     rng: &mut R,