From a1d16d3cdd589f44fc5d41b20c2127cdeda1dea5 Mon Sep 17 00:00:00 2001 From: ryanRfox Date: Tue, 28 Aug 2018 09:45:50 -0400 Subject: [PATCH] BSIP44: Hashed Timelock Contracts --- README.md | 3 ++- bsip-0000.md => bsip-0044.md | 14 +++++--------- 2 files changed, 7 insertions(+), 10 deletions(-) rename bsip-0000.md => bsip-0044.md (97%) diff --git a/README.md b/README.md index 2d23357..1626bfa 100644 --- a/README.md +++ b/README.md @@ -47,5 +47,6 @@ Number | Title | [37](bsip-0037.md) | Allow new asset name to end with a number | oxarbitrage | Protocol | Installed [38](bsip-0038.md) | Add target collateral ratio option to short positions | Abit More | Protocol | Installed [39](bsip-0039.md) | Automatically approve proposals by the proposer | Fabian Schuh | Protocol | Draft -[40](bsip-0040.md) | Custom active permission | Stefan Schießl | Protocol | Draft +[40](bsip-0040.md) | Custom active permission | Stefan Schießl | Protocol | Draft [42](bsip-0042.md) | Adjust price feed to influence trading price of SmartCoins | Abit More | Protocol | Draft +[44](bsip-0044.md) | Hashed Time-Locked Contract | Fox, Jones, taconator | Protocol | Draft diff --git a/bsip-0000.md b/bsip-0044.md similarity index 97% rename from bsip-0000.md rename to bsip-0044.md index 59355e7..c7a5f29 100644 --- a/bsip-0000.md +++ b/bsip-0044.md @@ -1,8 +1,8 @@ -BSIP: xxxx\ +BSIP: 0044\ Title: Hashed Time-Locked Contract\ -Authors: John M. Jones, Ryan R. Fox, taconator\ +Authors: Ryan R. Fox, John M. Jones, taconator\ Status: Draft\ -Type: Informational\ +Type: Protocol\ Created: 2018-08-22\ Discussion: TBD @@ -90,8 +90,6 @@ The `timeout threshold` of the contract is defined by `depositor` within the HTL To protect the `recipient`, early termination of an HTLC is not allowed by any party. Placing a `timeout threshold` far into the future is valid. User protection from locking up funds for an extremely long period could be provided by the UI used to create the HTLC. -**TODO:** Consider adding an `Update_HTLC` operation to allow `depositor` to extend the `timeout threshold` - ### **Automatic Transfers Upon Expiry** Upon expiry of the `timeout threshold`, the `escrow assets` held within the HTLC will **not** automatically be returned to `depositor`. A separate transaction must be initiated by the `depositor` to request `escrow assets` be transferred to `depositor`. @@ -102,14 +100,10 @@ Code _could_ be added to automate the return of funds. This could be part of blo Creating and fulfillment are two operations that add data to the blockchain. The `fee` for each operation is based on the standards set for blocks, and is similar to costs of other items stored on-chain. -**TODO:** Discuss fees may be variable, as it is possible to store a variable length preimage hash. - ## **Existing Escrow Proposals** This section describes various escrow concepts that have been proposed either for BitShares or for other blockchains or services in terms of the elements that have been defined above. This is intended to provide some background and comparison to the concepts that follow. -**TODO:** Elaborate Interledger - ## **Existing Graphene Features that are Similar to What is Needed for Blockchain Escrowing** ### **BitShares Escrow** @@ -164,6 +158,8 @@ Bob has now observed the `preimage` Alice used to "unlock" his HTLC, and he will # **Discussion** +TBD + # **Summary for Shareholders** TBD