From 5f64cb0877ddc284dbee55aaa88a0c2bec77ab62 Mon Sep 17 00:00:00 2001 From: jmjatlanta Date: Fri, 21 Sep 2018 00:57:27 +0200 Subject: [PATCH] Added summary for tokenholders --- bsip-0044.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/bsip-0044.md b/bsip-0044.md index e9beda7..6b9c687 100644 --- a/bsip-0044.md +++ b/bsip-0044.md @@ -277,9 +277,11 @@ transaction_obj htlc_extend_expiry(depositor, id, timeout_threshold, htlc_extent https://github.com/bitshares/bsips/pull/104 -# **Summary for Shareholders** +# **Summary for Tokenholders** -TBD +Hashed Timelock Contracts (HTLCs) allow account holders to transfer funds from their account (sender) to another account (receiver) before a certain time, only if the receiver knows the preimage (a.k.a. password). If used, the preimage is then published on the blockchain. If the transfer is not claimed before expiry, the funds return to the original account holder. + +Creating these contracts in pairs allow users to do a trustless exchange, even across blockchains. The typical scenario is that Account holder A agrees to make a transfer Account holder B on the Bitshares blockchain, and Account Holder B agrees to make a transfer to Account holder A on a foreign blockchain. Account holder A creates an HTLC on Bitshares, that includes a hash (an encrypted form of the preimage). Account holder B can view the HTLC, and decide to agree by creating an HTLC on the foreign blockchain, using the same hash. Account holder A then uses their preimage to receive the funds on the foreign blockchain, and in the process exposes the preimage. Account holder B can now use that preimage to receive the funds on the Bitshares blockchain. # **Copyright**