I’m really stoked about new nostr:npub1cvqlzvmjercdn0ypsmv8f7j9lge6ahsnueh5rparh53wuswftv4q49yjt3 Wallet enabling core miniscript functionality.

I have one important suggestion regarding UI that will go a long way to assist users with restoring from backup: wallet identifier should be visible from within the application. I can see the wallet id if I email myself a copy of the descriptor, but as best I can tell it’s not in the app.

You have to assume there will be users who do a decaying or expanding multisig and all they have are the 3 seed phrases, time info, and m of n for each time segment but not the descriptor…it take surprisingly little info to restore such a wallet, far far less data than a descriptor contains…

Reply to this note

Please Login to reply.

Discussion

I would also put keys in “numerical” order before putting them in a miniscript and making a wallet. Having only one order keys can be loaded reduces number of variables for restoring wallet with imperfect descriptor info. But as it is now, if I change the order of the 3 of 3 on my decaying multisig I get a different wallet ID.

Right, Miniscript currently doesn’t support sortedmulti descriptor.

Hi nostr:npub1cvqlzvmjercdn0ypsmv8f7j9lge6ahsnueh5rparh53wuswftv4q49yjt3, something like this is possible on Bitcoin? Thanks

A smart contract feature I'd like to see in Bitcoin:

People would agree to lock up any amount of Bitcoins for a specific period, for example, 5 years. If someone in the group decides to redeem before the 5-year period, it would be possible, but to do so, they would have to pay, for example, 10% of the amount they deposited to everyone else in the group who are still following the 5-year contract term.

This would allow us to determine who truly has skin in the game and who would be holding Bitcoin for the long term. It would also reduce the supply of Bitcoins in the market, forcing a potential appreciation.

Interesting idea…I don’t think this sort of “tontine” is possible as bitcoin script can’t do introspection. Maybe liquid network or lightning could support this?

Yes, it's like a tontine. I'm not a dev but would be great to have this possibility on Bitcoin natively.

Neither am I. But my gut says no…

But it is a cool smart contracting idea…I wonder what basic functions would be necessary to make it happen…some sort of covenant based on time and amount I guess.

By ID, do you mean the descriptor checksum?