# CTV vault output descriptor **URL:** \ **Category:** Implementation\ **Tags:** softfork, descriptors\ **Created:** [June 10, 2025, 11:46am UTC](https://delvingbitcoin.org/t/ctv-vault-output-descriptor/1766 "2025-06-10T11:46:54Z")\ **Posts on this page:** 1\ **Showing post:** 8
**Author:** ![sjors](https://delvingbitcoin.org/user_avatar/delvingbitcoin.org/sjors/32/59_2.png) [@sjors](https://delvingbitcoin.org/u/sjors)\ **Post date:** [June 12, 2025, 6:16pm UTC](https://delvingbitcoin.org/t/ctv-vault-output-descriptor/1766/8 "2025-06-12T18:16:17Z")
> [@AdamISZ](#): > > That’s true but are you not here just pointing to a limitation of using CTV in any case? Yes, if I understand this limitation correctly, and if there’s no elegant way around it, it makes CTV not practical for vaults. Except perhaps for very sophisticated users, in particular those with existing (reliable, frequent) backup infrastructure. > [@AdamISZ](#): > > , if we tend to think of descriptors as “a thing that describes an unboundedly large pot you can put stuff into” The use case I have in mind is a “daily” wallet with a recovery mechanism, where if you don’t use the mechanism it shouldn’t get in your way. Otherwise it’s not going to be a UX improvement over the current state of the art of just rotating coins once a year as a dead man’s switch (and having your wallet reminding you). > [@AdamISZ](#): > > the descriptor could have the preimage of the CTV hash all serialized You can’t know this hash at wallet creation time. Indeed also because you won’t know what lock time to pick. Maybe you could have giant tree of amounts and fixed dates? * * * Maybe the above is a bit too pessimistic; it doesn’t work for the use case I’m describing, and descriptors aren’t the right tool, but the original [Simple-CTV-Vault](https://github.com/jamesob/simple-ctv-vault) design [seems to only require](https://github.com/jamesob/simple-ctv-vault/issues/9) the user to backup: 1. the involved public keys 2. one (?) private key 3. the block delay 4. each deposit transaction id (1) - (3) are known at creation time. (4) requires continuous backups, but may be recoverable with context. --- _[View the full topic](https://delvingbitcoin.org/t/ctv-vault-output-descriptor/1766)._