salvatoshi

https://twitter.com/salvatoshi

#bitcoin

Public Key

npub157y6gz0l0rfhw220rfwnujeff6q2mec33nzkwz23umkrt6482exq8e60gr

NIP-57 Address

yummyowl20@primal.net

Profile Code

nprofile1qqs20zdyp8lh35mh99835hf7fv55aq9duugce3t8p9g7dmp4a2n4vnqx2rz7u

Author Public Key

npub157y6gz0l0rfhw220rfwnujeff6q2mec33nzkwz23umkrt6482exq8e60gr

Show more details

Last Notes

2025-05-28 05:42:18

What happens in Vegas,
hopefully doesn't stay in Vegas.
See you on Thursday!
https://image.nostr.build/3c07e6c6c6cd7a5c347de6e92263e6362ec0cb1aee707d4f08a52dfa59b0ef2a.jpg

2025-05-22 09:38:44

EUR people wondering why is everyone talking about ATH
https://image.nostr.build/21be5df342906e6937fd475c8325e6b0c42cae3700c3c90d417cfbe39e62b6a4.gif

2025-05-21 14:38:08

My talk at @nprofile…lf72 is Thursday 29th May 1:30pm in the Developer Zone.
Let's chat about useful opcodes.
https://image.nostr.build/c632d7fe6e3bfaa98a95c0225b9333fdfb2868332673b03283315163d8509cfa.jpg

2025-05-02 21:47:11

- reply

Yes, of you provide a chain code yourself and it has enough entropy, then it works somewhat. But it's not better than a 2-of-2 between the device and the software wallet in terms of security model, and I think the latter is easier to analyze.

2025-05-02 21:21:57

- reply

I'm gonna shill this blog post I wrote some time back: https://www.ledger.com/blog/towards-a-trustless-bitcoin-wallet-with-miniscript
If you don't trust a signing device, it's really hard to meaningfully use it without additional devices - I don't think creative paths can help much. For example, a device could lie about the xpubs you ask.

2025-05-02 20:33:15

- reply

> Just trying to think about how you can Guarantee that neither the manufacturer or yourself knows the private key
What for? I see footguns in this scheme, but I don't quite see the benefits.
In general, I think that both cosigners and blind signers are unlikely to make much much sense in multisig setups - much more useful in miniscript wallets, where you can do more 'experimental' stuff with the primary spending path, while keeping recovery paths straightforward.

2025-05-02 19:57:18

- reply

The derivation paths doesn't really change anything in the meaning of the policy, so as long as it's a path you can export from your signer, everything will work.
(some devices might have path restrictions for xpubs they export, though - so using standard patterns maximizes compatibility)
What is your goal?

2025-05-02 19:50:16

- reply

YOU TAKE THAT BACK

2025-05-02 09:44:19

I will be at @nprofile…5m55 in Vegas with a session on `OP_CHECKCONTRACTVERIFY`.
What should I talk about?

2025-04-25 21:21:07

"MuSig2 is the cherry on top of the taproot cake"
I'm somewhat of a poet myself.
Read about Ledger Bitcoin app's support of MuSig2 in this blog post - written with the legend Yannick Seurin in person.
https://image.nostr.build/35b3c88b9fe426da75def37c5069fd1a34093aee7c621d8592fb44139b2b5991.jpg
https://www.ledger.com/blog-musig2-ledger-bitcoin-app

2025-04-22 22:44:57

- reply

Zaps are all custodial over here 🥲

2025-04-15 20:23:48

Not sure why people think Merkle trees are hard.
https://image.nostr.build/a66983a8c1ae9406c2686d4332cb7ba2ed13d592d4eaa9419017f66f6d97bf38.jpg

2025-04-09 13:52:21

When Ruben Somsen writes a gist, you know it's going to be good:
https://gist.github.com/RubenSomsen/a61a37d14182ccd78760e477c78133cd
On improving IBD time.

2025-04-03 10:33:22

- reply

I have Phoenix wallet in the phone, and an @nprofile…jjxr node at home - it feels like this should be a solvable problem!

2025-04-03 08:40:14

Self-custody can't be evil.
Minimize evil in bitcoin by holding the keys.
#nevent1q…tq2d

2025-04-03 08:29:45

"Don't be evil", as Google taught us, is not a viable long-term strategy for businesses working with content.
"Can't be evil" is the way.

2025-03-28 16:52:20

- reply

Anything you'd like to build?

2025-03-28 10:59:31

Writing apps for hardware signing devices is about to get this easy
```
#![cfg_attr(target_arch = "riscv32", no_std, no_main)]
extern crate alloc;
use alloc::vec::Vec;
sdk::bootstrap!();
fn process_message(_app: &mut sdk::App, msg: &[u8]) -> Vec<u8> {
msg.to_vec()
}
pub fn main() {
sdk::App::new(process_message).run();
}
```

2025-03-11 09:26:13

- reply

Oh, I will! But you might not like what I replace it with 🤣

2025-03-10 09:53:51

GM, I'm trying to compile rust-bitcoin without rust-secp256k1. How's your day?

2024-12-20 19:36:22

- reply

The Italian-approved size is 25-30 ml, that's already in the "lungo" realm :P

2024-10-16 07:47:29

- reply

Who gave Skippy a gun??

2024-10-04 04:23:58

If you often use regtest, you often need to manually mine blocks to test things.
If you're on linux, add this to ~/.bashrc:
```
mine() {
if [ "$#" -eq 0 ]; then
bitcoin-cli -regtest -generate 1
else
bitcoin-cli -regtest -generate "$1"
fi
}
alias mine=mine
```
Now you can write:
```
$ mine
```
to mine a block, or:
```
$ mine 100
```
to mine 100 blocks and make your Liana timelocks expire.
Another useful alias for .bashrc:
```
alias lastblock='bitcoin-cli -regtest getblock $(bitcoin-cli -regtest getbestblockhash) 2'
```
So you can just write 'lastblock' on the terminal to see all the transactions in the last block.
Please reply below with your best regtest aliases and scripts.

2024-08-29 20:53:34

- reply

Interesting opinion

2024-08-29 13:02:38

- reply

I will zap them if they do 🤣

2024-08-29 13:02:11

- reply

Can the devs do something? 🫣

2024-08-29 12:57:08

I use Amethyst and Phoenix. Can I use it to receive zaps? If not... why not?

2024-08-29 12:36:45

- reply

I have Amethyst and Phoenix, I seem to be too dumb to make it work (or can it work?)

2024-08-29 08:43:36

- reply

I think Liana can just add a "sign by endpoint" feature, meaning that there is a webserver somewhere that expects your PSBTs and returns then signed (if they respect whichever conditions you it's programmed for) for one of the xpubs in the wallet policy.
The cosigner could be a third-party service, or a simple webservice running in your umbrel node (or your friend's node), etc.

2024-08-29 08:37:02

- reply

Memes apart, support and integration of hot/automatically signing keys should probably come before MuSig2.
(That's what I want to use MuSig2 with!)
In a multisig/MuSig2 with a hot/online key, you can give the user the singlesig user experience, and the programmability/UX benefits of hot keys.

2024-08-29 08:14:05

- reply

Currently on Ledger, BitBox02, Jade and Coldcard (on the test firmware because @nprofile…7dju is a miniscript hater :P)
Taproot miniscript still only with Ledger and Coldcard (edge) - harass your vendor if not in the list! :D

2024-08-29 07:54:48

- reply

Use Liana!

2024-08-29 07:48:19

Nostr needs more #miniscript discussions.
Have you tried Liana?
==> https://wizardsardine.com/liana
If you did but you still don't use it: why not?

2024-08-28 07:16:56

Is there any tool to automate posting on both Nostr and Twitter?

2024-08-27 19:48:52

I hope y'alls like Merkle trees!
#nevent1q…7krl

2024-08-27 19:47:03

- reply

'); DROP TABLE Users;--

2024-08-27 12:01:22

How many people read me on Nostr? Should I post here more often?

2023-09-05 04:18:21

No point in talking drivechains, as they are obsolete.
Covenants are bitcoin's native approach to smart contracts.

2023-08-12 17:11:36

With my first answer on StackExchange, I try to explain the core concepts of MATT with as little technicalities as I could.
Not quite an explanation for your grandma yet, unless you have an exceptionally cool grandma.
https://bitcoin.stackexchange.com/questions/119239/what-are-matt-opcodes/119268#119268

2023-08-10 11:01:42

- reply

A subset of MATT's utility, with more risks and bigger consensus changes.

2023-07-05 19:50:17

The problem with drivechains is that while they enable "everything", we want some of the features on native L1 bitcoin.
For example, vaults.
A powerful enough covenant is better: you can get the programmability of drivechains on layer 2s, but also some useful layer 1 features.

2023-06-25 11:28:46

Is there an easy way of using my Umbrel node with Amethyst for zaps?

2023-06-09 19:06:54

- reply

I didn't ignore it, so I guess test failed

2023-05-16 21:56:26

- reply

There have been times when I thought serializing and deserializing was my job.

2023-05-16 21:02:43

- reply

Ever tried writing embedded apps? 🙃

2023-03-09 15:08:19