Wallet implementers, what is the best way to drop scrip hashes in the Electrum Protocol?
I'm working on a lightweight client that has an integrated #Electrum Server for wallets to connect (and started a new EPS-like client). The fact that users have to copy their xpub and paste in the software before running sounds very stupid to me.
I also want to use BIP158 compact block filters, so I can allow users to add new wallets with very minimal waiting time, but there's a problem: Electrum (the protocol) sends **hashes** of scripts, not the actual script. That sucks because BIP158 uses the actual script.
We could solve both problems by having a way for wallets to communicate their addresses to a server. AFAIK, the argument for sending hashes instead of addresses is privacy, but it is a very week privacy, there's no forward secrecy, if you ever get paid on that address, the server know what the address actually is.
For my use-case, simply sending the address (at least once) is enough. Now I'm thinking what kind of extension I can make to the basic protocol to let clients communicate the address, without breaking compatibility with other software. Something like some new methods that behaves exactly like the current ones, but you send the address (not hash). What do you guys think?
#bitcoin #wallet #plebchain
Erik
npub1ur8…58yl
2024-06-09 12:25:26
Author Public Key
npub1ur8m24ya8nmakn38xmuwr0yy7cjgdtm6gy54mpnudgcngkgyy55qxc58ylPublished at
2024-06-09 12:25:26Event JSON
{
"id": "b63dc03a38d8ab94b7c6abea84bb191455c181a406517d5ff909fadfc7a5f3a1",
"pubkey": "e0cfb5549d3cf7db4e2736f8e1bc84f62486af7a41295d867c6a313459042528",
"created_at": 1717928726,
"kind": 1,
"tags": [
[
"t",
"Electrum"
],
[
"t",
"electrum"
],
[
"t",
"bitcoin"
],
[
"t",
"wallet"
],
[
"t",
"plebchain"
]
],
"content": "Wallet implementers, what is the best way to drop scrip hashes in the Electrum Protocol?\n\nI'm working on a lightweight client that has an integrated #Electrum Server for wallets to connect (and started a new EPS-like client). The fact that users have to copy their xpub and paste in the software before running sounds very stupid to me. \n\nI also want to use BIP158 compact block filters, so I can allow users to add new wallets with very minimal waiting time, but there's a problem: Electrum (the protocol) sends **hashes** of scripts, not the actual script. That sucks because BIP158 uses the actual script. \n\nWe could solve both problems by having a way for wallets to communicate their addresses to a server. AFAIK, the argument for sending hashes instead of addresses is privacy, but it is a very week privacy, there's no forward secrecy, if you ever get paid on that address, the server know what the address actually is.\n\nFor my use-case, simply sending the address (at least once) is enough. Now I'm thinking what kind of extension I can make to the basic protocol to let clients communicate the address, without breaking compatibility with other software. Something like some new methods that behaves exactly like the current ones, but you send the address (not hash). What do you guys think?\n\n#bitcoin #wallet #plebchain",
"sig": "02883eee534301e890cd31783b815d339b3315e9805a3b0d2f68ae878b19f3c33f9ec33c6ee452276ba7c093a72e44564f436f11734384d9b9f712063f1e4158"
}