You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Sender is nonCltvSpender, i.e. can spend anytime with redeem script OP_TRUE.
Beneficiary is cltvSpender, i.e. can spend anytime after OP_CHECKLOCKTIMEVERIFY elapses with redeem script OP_FALSE.
Required Wallet Sugar
(1) Wallet will lookup beneficiaries by registered email (hash lookup in DSC) - note: DSC will need to be extended to expose accounts' BTC pubKeys (also can be a nice viral referral flow - beneficiary refers new wallet signups by email prompt...)
(2) Wallet will prompt Benefactors to "roll over" his non-std outputs periodcally to reset OP_CHECKLOCKTIMEVERIFY interval. If and when that fails to happen, output will become spendable by Beneficiary.
How to make sure that a friend or family member can access your BTC if Something Bad happens to you... (trustlessly)?
Send your BTC to a non-standard output with a locking script like:
Sender is
nonCltvSpender
, i.e. can spend anytime with redeem script OP_TRUE.Beneficiary is
cltvSpender
, i.e. can spend anytime after OP_CHECKLOCKTIMEVERIFY elapses with redeem script OP_FALSE.Required Wallet Sugar
(1) Wallet will lookup beneficiaries by registered email (hash lookup in DSC) - note: DSC will need to be extended to expose accounts' BTC pubKeys (also can be a nice viral referral flow - beneficiary refers new wallet signups by email prompt...)
(2) Wallet will prompt Benefactors to "roll over" his non-std outputs periodcally to reset OP_CHECKLOCKTIMEVERIFY interval. If and when that fails to happen, output will become spendable by Beneficiary.
WIP... see wallet-btc-p2sh.js (and "DMS" comments in-line, various).
The text was updated successfully, but these errors were encountered: