pull down to refresh
100 sats \ 0 replies \ @Scoresby OP 10h \ parent \ on: The BitVault B-SSL vault proposal doesn't make any sense bitcoin
How does the use of a 2hr - 15 day timelock on key C (from your whitepaper) help protect the user from loss of keys?
Here's how I understand the B-SSL system as laid out in your whitepaper:
- user sets up a wallet with 3 keys (A, B, C)
- at least 2 keys are required to sign to move coins from this wallet
- Keys A and C can generate a sign transactions spending coins out of the vault 2 hrs - 15 days after coins enter the vault (depending on how the user configures it)
- Keys A and B can sign transactions spending coins out of the vault 1 year after coins enter the vault
- Keys B and C can sign transactions spending coins out of the vault 3 years after coins enter the vault
I believe I understand the spending paths used by A+B and B+C, but I'm very confused about the purpose of the A+C spending path.
If the timelock on the A+C spending path begins counting as soon as coins are moved into the vault, what purpose does it serve? Do you plan on having users self-send their coins to refresh this timelock before it expires? If not, users will only benefit from the timelock for (at most) the first 15 days of using the vault. This is what confuses me. Can you help me understand this part of it?