diff options
Diffstat (limited to 'bip-0119.mediawiki')
| -rw-r--r-- | bip-0119.mediawiki | 10 |
1 files changed, 5 insertions, 5 deletions
diff --git a/bip-0119.mediawiki b/bip-0119.mediawiki index f30e35c..11a90bb 100644 --- a/bip-0119.mediawiki +++ b/bip-0119.mediawiki @@ -61,14 +61,14 @@ structured in a tree-like fashion to reduce individual costs of redemption. The below chart showcases the structure of these transactions in comparison to normal transactions and batched transactions. -<img src="ctv/states.svg" align="middle"></img> +<img src="bip-0119/states.svg" align="middle"></img> A simulation is shown below of what impact this could have on mempool backlog given 5% network adoption, and 50% network adoption. The code for the simulation is provided in this BIP's subdirectory. -<img src="ctv/five.png" align="middle"></img> -<img src="ctv/fifty.png" align="middle"></img> +<img src="bip-0119/five.png" align="middle"></img> +<img src="bip-0119/fifty.png" align="middle"></img> ===Payment Channels=== There are numerous payment channel related uses. @@ -91,7 +91,7 @@ With CHECKTEMPLATEVERIFY, it’s possible for a single party to construct a chan party can exit from without requiring signatures from both parties. These payment channels can operate in one direction, paying to the channel "listener" without need for their private key to be online. -<img src="ctv/nic.svg" align="middle"></img> +<img src="bip-0119/nic.svg" align="middle"></img> ====Increased Channel Routes==== In the Lightning Network protocol, Hashed Time Locked Contracts (HTLCS) are used in the construction @@ -123,7 +123,7 @@ ability for a support desk to improperly move funds. Furthermore, all such designs can be combined with relative time locks to give time for compliance and risk desks to intervene. -<img src="ctv/vaults.svg" align="middle"></img> +<img src="bip-0119/vaults.svg" align="middle"></img> ===CoinJoin=== |