frost/bdk
3
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Apply typo fixes from @tcharding

Browse Source 
Co-authored-by: Tobin C. Harding <me@tobin.cc>
This commit is contained in:
Lloyd Fournier 2021-02-12 10:20:11 +11:00 committed by LLFourn
parent 1fbfeabd77
commit 7c1dcd8a72
No known key found for this signature in database
GPG Key ID: A27093B54DA11F65
2 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
src/wallet/mod.rs
View File

@ -2380,7 +2380,7 @@ mod test {
builder
.add_foreign_utxo(utxo2.outpoint, psbt_input2, satisfaction_weight)
.is_ok(),
"shoulld be ok when outpoing does match psbt_input"
"shoulld be ok when outpoint does match psbt_input"
);
}

4
src/wallet/tx_builder.rs
View File

@ -314,7 +314,7 @@ impl<'a, B, D: BatchDatabase, Cs: CoinSelectionAlgorithm<D>, Ctx: TxBuilderConte
self.add_utxos(&[outpoint])
}
/// Add a foreign UTXO i.e. A UTXO not owned by this wallet.
/// Add a foreign UTXO i.e. a UTXO not owned by this wallet.
///
/// At a minimum to add a foreign UTXO we need:
///
@ -325,7 +325,7 @@ impl<'a, B, D: BatchDatabase, Cs: CoinSelectionAlgorithm<D>, Ctx: TxBuilderConte
/// There are several security concerns about adding foregin UTXOs that application
/// developers should consider. First, how do you know the value of the input is correct? If a
/// `non_witness_utxo` is provided in the `psbt_input` then this method implicitly verifies the
/// value by checking it against the transaction. If only a `wintess_utxo` is provided then this
/// value by checking it against the transaction. If only a `witness_utxo` is provided then this
/// method doesn't verify the value but just takes it as a given -- it is up to you to check
/// that whoever sent you the `input_psbt` was not lying!
///