From df47e5aaf0c964a0b4d2e79cc4afbc8c30e13f24 Mon Sep 17 00:00:00 2001 From: Esteban Ordano Date: Wed, 7 Jan 2015 12:18:24 -0300 Subject: [PATCH] Docs: drop outdated paragraph --- docs/guide/transaction.md | 6 ------ 1 file changed, 6 deletions(-) diff --git a/docs/guide/transaction.md b/docs/guide/transaction.md index 2607ede..a655ff5 100644 --- a/docs/guide/transaction.md +++ b/docs/guide/transaction.md @@ -82,12 +82,6 @@ There are a number of data structures being stored internally in a `Transaction` * `_fee`: if user specified a non-standard fee, the amount (in satoshis) will be stored in this variable so the change amount can be calculated. * `_change`: stores the value provided by calling the `change` method. -### Unspent Output Selection - -If you have a larger set of unspent outputs, only some of them will be selected to fulfill the amount. This is done by storing a cache of unspent outputs in a protected member called `_utxos`. When the `to()` method is called, some of these outputs will be selected to pay the requested amount to the appropriate address. - -A detail that you should have in mind is that when the transaction is serialized, this cache can't be included in the serialized form. - ## Upcoming changes We're debating an API for Merge Avoidance, CoinJoin, Smart contracts, CoinSwap, and Stealth Addresses. We're expecting to have all of them by some time in early 2015. First draft implementations of Payment Channel smart contracts extensions to this library are already being implemented independently.