The technical session opens the black boxes around signing. The second session focuses on people, continuity, recovery and physical-world risk.
Securing Bitcoin · 22 Oct · Lugano

https://luma.com/yawcgo0t

Bitcoin gives us control. Security is what we build around that responsibility.
In Annecy last Sep 24th we discussed self-custody, multisig, delayed transactions and what happens when the threat reaches beyond the seed itself.

Explore BitVault: https://www.bitvault.sv/

You may hold the keys across several devices while every spend still depends on one coordination path. Rafael Turon asks what that path observes and what fails when it fails.

22 Oct · Lugano

https://luma.com/yawcgo0t

A sunny day talking Bitcoin, security and self-custody at Bitcoin Social Forum in Florence ☀️₿

We brought BitVault on stage and then spent the day at our booth answering questions, showing how it works and, even better, listening to feedback from people actually trying it.

That’s the part we love. Building in the open, talking to Bitcoiners and learning from real users. 🧡

Thanks to everyone who stopped by!

A secure signer is not a complete security plan. Ask about loss and recovery, digital attacks, physical threats, and human or operational mistakes.

📅 Securing Bitcoin · 22 Oct · Lugano

Registration free, limited seats:
https://luma.com/yawcgo0t

« Not your keys, not your coins » est une excellente première règle.

Mais que se passe-t-il lorsque ce n’est plus seulement la clé qui est attaquée… mais son propriétaire ?

Demain à Annecy, BitVault présentera son approche Bitcoin-only, non-custodiale et open source de la sécurité : multisig, séparation des dispositifs et délais avant règlement définitif.

🎤 20–30 min
💬 Discussion ouverte
🎟 Gratuit

https://www.meetup.com/alpinechain-xyz/events/316526556

Keys are only step one. Devices fail. Software integrations break. Privacy leaks. Recovery plans collapse.
Securing Bitcoin brings the full threat model into one practical afternoon.

22 Oct · 13:30–19:00 · Lugano

https://luma.com/yawcgo0t

At @Noderunners Conference we stress-tested B-SSL instead of just explaining it.

In the simulator, participants could mark keys as compromised or unavailable, then move forward in time and see how the vault state changed.

One of the scenarios explored a compromised Convenience Service key.

The important result: key compromise does not necessarily mean immediate loss. Timelocks can create a window in which the legitimate owner may still be able to react before an attacker can use a spending path.

Change the keys. Advance time. See who can spend, through which path, and when.

That was the idea behind the B-SSL Vault Challenge.

Read the full workshop recap:
https://blog.bitvault.sv/when-things-go-south-stress-testing-a-bitcoin-vault-at-noderunners/

Today at @Noderunners Conference Arnhem: When Things Go South — The B-SSL Vault Challenge.

Predict what happens when a service disappears, a key is compromised or connectivity deteriorates. Then watch how the vault state changes as time passes.

16:00–17:00 · Workshops: Greenhouse

https://noderunners.network/en/conference/activity/when-things-go-south-b-ssl-vault-challenge

Your vault works. Until something stops working. What happens next?


At Noderunners Arnhem, our lead developer Riccardo Biffi will run an interactive B-SSL failure-mode workshop.


We’ll put a timelocked multisig vault under three kinds of pressure:
- service failure;
- compromised keys;
- poor network conditions.


The challenge is to predict the vault outcome first, then watch how the simulator changes the state over time.


The point is not to label everything “safe” or “broken.” Temporary unavailability, recoverability and exposure to theft are different states, and time matters.


19 Sep · 16:00–17:00 · Workshops: Greenhouse


https://noderunners.network/en/conference/activity/when-things-go-south-b-ssl-vault-challenge

Is owning your keys enough to be sovereign?
On 24 September, BitVault joins AlpineChain in Annecy for Souveraineté 3.0.

The discussion will cover Bitcoin self-custody, multisig, timed transactions, compromised devices and human/coercion risk.

🎤 20–30 min presentation
💬 Then questions, criticism and open discussion
🍽 Several planchas offered by BitVault

📍 Refuge du Craic — Novotel Annecy Centre
🕖 From 19:00
🎟 Free

https://www.meetup.com/alpinechain-xyz/events/316526556

Package relay, P2A, ephemeral dust, and TRUC are mempool and relay policy, not consensus changes.
That is both their strength and their limitation. They improve fee management without requiring a soft fork, but support can vary across peers, services, and miners. Policy cannot guarantee propagation.

A production design should therefore combine modern node software, multiple broadcast paths, mempool monitoring, fee estimation at broadcast time, and an escalation path when timing is critical.

The article’s practical baseline is Bitcoin Core 29.0 for the standard zero-value ephemeral-anchor pattern, with 31.0 preferred for the most mature package-aware behavior in the discussed version range.

Explore BitVault: https://www.bitvault.sv/