Damus
BitVault profile picture
BitVault
@BitVault

New open-source & self-custody wallet utilizing time-delays and multisignature to offset physical attacks and hacks. Beyond keys, we protect humans. Get early access πŸ‘‰ https://bitvault.sv

Relays (6)
  • wss://relay.primal.net – read & write
  • wss://nostr.sebastix.dev/ – read & write
  • wss://relay.nostr.band – read & write
  • wss://pyramid.fiatjaf.com/ – read & write
  • wss://nostr.tools.global.id – read & write
  • wss://nostr.middling.mydns.jp – read & write

Recent Notes

BitVault profile picture
Time changes what a key compromise can actually do.

Even if an attacker reconstructs both user keys A and B, the delayed fallback cannot be used until its CSV condition matures.

Before then, the legitimate owner can use (A or B) + C to spend the current vault output V0 into a new output V1.

Once V0 is spent:

β€’ transactions prepared against V0 become invalid
β€’ V1 becomes the active vault output
β€’ the fallback delay starts again on V1

The keys remain A, B and C.

BitVault does not remove the key compromise. It creates a response window in which the legitimate owner can refresh the UTXO before the attacker’s delayed path becomes available.

Read the full analysis:
https://blog.bitvault.sv/if-your-coldcard-was-integrated-with-bitvault/
BitVault profile picture
P2A and ephemeral dust solve different parts of the same operational problem.
P2A defines a compact, keyless anchor output. A wallet, watchtower, service, or other party can spend it without receiving privileged signing material from the parent.

Ephemeral dust policy allows that anchor to have zero value when a zero-fee parent creates it and the package spends it immediately. The child must still add another confirmed input to pay the fee.

Because the anchor is keyless, TRUC and package replacement behavior are the practical anti-pinning layer. P2A supplies the hook. TRUC keeps competition for the hook manageable.

Read: https://blog.bitvault.sv/package-relay-and-ephemeral-anchors-how-bitcoin-transactions-adapt-to-a-changing-fee-market/
BitVault profile picture
Thank you @Simply Bitcoin for having us to speak about how Bitcoin's protocol-level programmability now enables a flexible vault that is resistant to any physical or cyber vulnerability.

BitVault profile picture
BitVault is now live on iOS.

Self-custody security should not depend on one key, one device or one irreversible moment.

BitVault combines multisig coordination, hardware-wallet signing and time-delayed Bitcoin transactions to create a window to detect and react before funds move.

For the official launch:
β€” 1 year of BitVault Pro + 1 hardware-wallet voucher: $199
β€” 2 years of BitVault Pro + 2 hardware-wallet vouchers: $299

The 2-year package supports any mix of Keystone 3 Pro BTC-Only and Jade Plus, giving new users the two compatible signing devices required for a complete multivendor setup.

BitVault requires two supported hardware wallets. The 1-year package is best suited to users who already own, or plan to acquire separately, a second compatible device.

Limited launch allocation. Explore the packages and download BitVault for iOS: https://www.bitvault.sv/

11❀️1
BitVault profile picture
A pre-signed Bitcoin transaction can be valid, fully authorized, and still fail to propagate when it is finally needed because its fee was chosen for a market that no longer exists.

Package relay addresses the mismatch by letting a node evaluate a low-fee parent and a fee-paying child together. The parent remains a separate transaction with unchanged signatures and outputs. The child contributes the fee required by current conditions.

This is especially relevant for vaults, Lightning channels, inheritance plans, and any system that signs before broadcast.

The authorization can be fixed early. The confirmation priority can remain flexible.

Read: https://blog.bitvault.sv/package-relay-and-ephemeral-anchors-how-bitcoin-transactions-adapt-to-a-changing-fee-market/





BitVault profile picture
Some days ago our @Riccardo Biffi took the stage at #bcc8333 to talk about our approach to a trustless keys recovery system. Give it a look at www.b-ssl.com. Thanks SatoshiPassion for the awesome pics!




13❀️5πŸ’―1
Riccardo Biffi · 12w
It was honor! nostr:nprofile1qy88wumn8ghj7mn0wvhxcmmv9uq36amnwvaz7tmwdaehgu3wvf5hgcm0d9hx2u3wwdhkx6tpdshsqgxxpuvv05y3u47lw3024mksd6q48s75agxaznluyypz7pq6cvqrjg0jhd5m is a wonderful conference. I met some truly amazing people there! πŸ’ͺ See you next year!
LpLiberto · 15w
Guys I'd love to read and fully grasp this but I just can't. Maybe run the first AI drafr through another AI to desloppify it or something, it's all weird similes and antitheses. Every paragrapg is 1-2 sentences and reads like impact marketing. It's painful. Sorry, don't want to put you on the spot...
Signing Room · 20w
What if Bitcoin multisig was as easy as one line html tag? Meet Signing Room v2.0.0 Our zero-knowledge coordination layer is now a drop-in Web Component. No databases. Just one HTML tag.πŸ‘‡ https...
BitVault profile picture
Zero-knowledge coordination with no backend is a real unlock for multisig UX. We've been working on the time-delay and key-management side of the same problem with BitVault β€” curious to hear your thoughts: https://primal.net/bitvault
1❀️2
Signing Room · 18w
Love what you're building with time-delays! Improving OpSec is exactly what we are tackling right now. In fact, we’re dropping v2.1.0 tomorrow focused purely on the physical attack vector - specifically anti-shoulder surfing with a new frosted-glass privacy UI by default. Let us know if there is ...