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

[docs] clarify when the fee could be unknown

Browse Source
This commit is contained in:
Riccardo Casatta 2021-07-12 10:06:08 +02:00
parent c1077b95cf
commit a6ce75fa2d
No known key found for this signature in database
GPG Key ID: FD986A969E450397
1 changed files with 4 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
src/types.rs
View File

@ -160,7 +160,10 @@ pub struct TransactionDetails {
pub received: u64, pub received: u64,
/// Sent value (sats) /// Sent value (sats)
pub sent: u64, pub sent: u64,
/// Fee value (sats) if available /// Fee value (sats) if available.
/// The availability of the fee depends on the backend. It's never `None` with an Electrum
/// Server backend, but it could be `None` with a Bitcoin RPC node without txindex that receive
/// funds while offline.
pub fee: Option<u64>, pub fee: Option<u64>,
/// If the transaction is confirmed, contains height and timestamp of the block containing the /// If the transaction is confirmed, contains height and timestamp of the block containing the
/// transaction, unconfirmed transaction contains `None`. /// transaction, unconfirmed transaction contains `None`.