I have a problem: I’m trying to create a #bitcoin #Miniscript #vault with the ...

Why Nostr? What is Njump? Join Nostr

npub1ah…xj28q

2026-10-28 09:18:50 UTC

I have a problem: I’m trying to create a #bitcoin #Miniscript #vault with the following behaviour:
• First 6 months after receiving a UTXO → completely locked (no one can spend)
• After 6 months → only a 2-of-3 can spend
• After 1 year → either the original 2-of-3 or a second 2-of-3 (recovery set) can spend
• Relative timelocks so that self-transfers reset both clocks
I currently have this policy working in nprofile1qqsvxq03xdev3uxehjqcdkr5lfzl5vawmcf7vm6ps73m6ghwg8y4k2spzemhxue69uhkummnw3ezuumvda6xs7fwwa5kuqg4waehxw309ajkgetw9ehx7um5wghxcctwvsgf0yne (nprofile…0yne)

or_i(
and_v(v:multi(2, key_0_0, key_1_0, key_2_0), older(25920)),
and_v(v:multi(2, key_3_0, key_4_0, key_5_0), older(52560))
)

Both Sparrow and Liana reject this policy.
⬇️⬇️⬇️⬇️⬇️⬇️⬇️⬇️⬇️⬇️
I don’t want to be locked into a single software wallet (Nunchuk only).

I don’t want to rely on only one piece of software.

software can disappear from app stores or repositories , stop being maintained, or become hard to find years from now.

Because of that, I want a Miniscript policy that can be recovered and spent from multiple independent tools .

ANY THOUGHTS??

#asknostr #wallets #miniscript

Author Public Key

npub1ahlxdf0t08y0knmtfdm2y7ut5eh06xcspluwnfufnmu6rqkuwccqdxj28q

Seen on

wss://relay.damus.io

Show more details

Published at

2026-10-28 09:18:50 UTC

Kind type

1 Short Text Note

Event JSON

{ "id": "36652f2ee32f3c1f3c8d5397ac6b51b613ee1124033f8a9febd14ce0164a7c23", "pubkey": "edfe66a5eb79c8fb4f6b4b76a27b8ba66efd1b100ff8e9a7899ef9a182dc7630", "created_at": 1793179130, "kind": 1, "tags": [ [ "p", "c301f13372c8f0d9bc8186d874fa45fa33aede13e66f4187a3bd22ee41c95b2a", "wss://nostr.slothy.win", "mention" ], [ "t", "bitcoin" ], [ "t", "Miniscript" ], [ "t", "vault" ], [ "t", "asknostr" ], [ "t", "wallets" ], [ "t", "miniscript" ], [ "client", "Primal iOS" ] ], "content": "\nI have a problem: I’m trying to create a #bitcoin #Miniscript #vault with the following behaviour:\n• First 6 months after receiving a UTXO → completely locked (no one can spend)\n• After 6 months → only a 2-of-3 can spend\n• After 1 year → either the original 2-of-3 or a second 2-of-3 (recovery set) can spend\n• Relative timelocks so that self-transfers reset both clocks\nI currently have this policy working in nostr:nprofile1qqsvxq03xdev3uxehjqcdkr5lfzl5vawmcf7vm6ps73m6ghwg8y4k2spzemhxue69uhkummnw3ezuumvda6xs7fwwa5kuqg4waehxw309ajkgetw9ehx7um5wghxcctwvsgf0yne \n\nor_i(\nand_v(v:multi(2, key_0_0, key_1_0, key_2_0), older(25920)),\nand_v(v:multi(2, key_3_0, key_4_0, key_5_0), older(52560))\n)\n\nBoth Sparrow and Liana reject this policy.\n⬇️⬇️⬇️⬇️⬇️⬇️⬇️⬇️⬇️⬇️\nI don’t want to be locked into a single software wallet (Nunchuk only).\n\nI don’t want to rely on only one piece of software.\n\nsoftware can disappear from app stores or repositories , stop being maintained, or become hard to find years from now. \n\nBecause of that, I want a Miniscript policy that can be recovered and spent from multiple independent tools .\n\nANY THOUGHTS??\n\n#asknostr #wallets #miniscript ", "sig": "fe1dca81ef2c92266de498262f48d5245f1c5c3f20d24ee5e7be66e2a096d0aaa42512de10ef78e8c25843bf6ad20d08c27c1b3f3b868da2558f22b0aed8a627" }