Possible next steps:
- Enable CLTV-by-time in wallet.
- Add date/time lock chooser to Receive tab in GUI.
- Some way for the recipient to prove to the sender that the address is CLTV.
(this feature was requested on reddit)
Possible next steps:
(this feature was requested on reddit)
1069 | @@ -1070,7 +1070,10 @@ UniValue addmultisigaddress(const UniValue& params, bool fHelp) 1070 | " \"address\" (string) bitcoin address or hex-encoded public key\n" 1071 | " ...,\n" 1072 | " ]\n" 1073 | - "3. \"account\" (string, optional) DEPRECATED. An account to assign the addresses to.\n" 1074 | + "3. options (object, optional)\n" 1075 | + " {\n" 1076 | + " \"cltv_height\" (numeric, optional) Minimum block height before received funds can be spent\n"
What about cltv_time as in the createmultisig RPC?
This is more complex. SelectCoins will need to be taught not to mix height and time locked coins, and FundTransaction to use time rather than height (preferably in more than merely cases that require it, for privacy). Note the code in this RPC call specifically blocks cltv_time for now.
160 | + try { 161 | + sn = CScriptNum(vch1, true, 5); 162 | + } catch (scriptnum_error) { 163 | + break; 164 | + } 165 | + // 0 CLTV is pointless, so expect at least height 1
Maybe we should keep OP_U32INT independent from CLTV? Allow 0 as value?
Concept ACK.
Closing due to apparent lack of interest... If you want to review, poke me and I'll rebase/reopen...
The concept is great, puts new BIPs to the front, if this could get more interest , could result in developers making easy use of new functionality.