Maybe couldn’t afford a proper tattoo artist after spending all their money on V-Bucks 🙃
Good point, there is a good tutorial made by @Ron, I should use the screenshots and link to it as well
Yeah, compiling to different platforms has worked quite well. Haven’t tried browser as it doesn’t fit the project but that’s definitely a plus as well
It used fyne a go package. Very lightweight and BSD 3-Clause
Yes, receive is SP only. Send is obviously to any standard address type.
First alpha release for testing of BlindBit Desktop. BlindBit Desktop is a pure Silent Payments (Bip 352) wallet for desktop. All scanning is happening locally, so the public indexing server does not learn anything about your transactions.
*Core Features:*
- Local scanning, reaping the full benefits of high privacy with Silent Payments
- Background scanning in tray, you will always be at or close to chaintip
- Simple GUI to manage the wallet
If you are keen on playing around with Silent Payments (BIP 352), this Desktop Wallet might be for you.
https://github.com/setavenger/blindbit-desktop/releases/tag/v0.1.0-alpha.1
*SHA256 Sums:*
b9c025f0c22a419248d2aa9000a905c90290b7182d5eafdca927f55357e9a465 BlindBit-darwin-amd64.zip
70e230bfb69ceaf2d7e03e02c23f099cebf26d45f933cb233ca7fa409e28ec0c BlindBit-darwin-arm64.zip
76f08a27a256a5940af024d28efd53fe22b5c1b5df0cbcc8a4b4dba3e6861da9 BlindBit-linux-amd64.tar.xz
745394ca580e454c63da4a37c51aa79ee9d5be02ae9c34ce56fc09b58ba3dce9 BlindBit-linux-arm64.tar.xz
2829dd3e430a681ea3a49501db18707f2a18823a478990429d9daedcd3a51d89 BlindBit-windows-amd64.exe
A little reminder, if you’d like to test out Silent Payments on Desktop, try this out. Receive and Send support for Silent Payments
nostr:nevent1qqsy2x9mquqmyfe7ds4evtguudn7hhrkxvrd2c6cxfa209gx752nh2gex8e5v
Nostr DMs sind prinzipiell immer verschlüsselt (auch NIP-04). Die erste Idee der DMs (NIP-04) hat, wie richtig beschrieben, signifikante Privatsphäre Probleme. Jeder kann sehr einfach sehen wer mit wem kommuniziert. Aber wichtig man kann nicht sehen WAS kommuniziert wurde. Wenn wirklich jemand NIP-04 lesen kann, würde das eigentlich nur eine von zwei Sachen sein:
- private keys wurden geleaked
- secp256k1 cryptography ist gebrochen (wird auch in Bitcoin genutzt), ich denke mal das hätten wir gemerkt
Ich würde mal schätzen, dass die Nuss einfach vom Sender selbst eingelöst wurde oder es keine DMs waren sondern ein wirklich öffentlicher Kanal.
https://fountain.fm/episode/WMzDGqV19RDAB4FTKLHa
nostr:nevent1qvzqqqpxquqzpsejtqmfphtmtqq93v2yfavx0xxjeg0dul5zm7pu00yc909kwqke6k6u2c
First alpha release for testing of BlindBit Desktop. BlindBit Desktop is a pure Silent Payments (Bip 352) wallet for desktop. All scanning is happening locally, so the public indexing server does not learn anything about your transactions.
*Core Features:*
- Local scanning, reaping the full benefits of high privacy with Silent Payments
- Background scanning in tray, you will always be at or close to chaintip
- Simple GUI to manage the wallet
If you are keen on playing around with Silent Payments (BIP 352), this Desktop Wallet might be for you.
https://github.com/setavenger/blindbit-desktop/releases/tag/v0.1.0-alpha.1
*SHA256 Sums:*
b9c025f0c22a419248d2aa9000a905c90290b7182d5eafdca927f55357e9a465 BlindBit-darwin-amd64.zip
70e230bfb69ceaf2d7e03e02c23f099cebf26d45f933cb233ca7fa409e28ec0c BlindBit-darwin-arm64.zip
76f08a27a256a5940af024d28efd53fe22b5c1b5df0cbcc8a4b4dba3e6861da9 BlindBit-linux-amd64.tar.xz
745394ca580e454c63da4a37c51aa79ee9d5be02ae9c34ce56fc09b58ba3dce9 BlindBit-linux-arm64.tar.xz
2829dd3e430a681ea3a49501db18707f2a18823a478990429d9daedcd3a51d89 BlindBit-windows-amd64.exe
GM. To anybody who is interested in Silent Payments or likes to experiment. If you want to move the available software stack further, it would be great to test and give feedback 🙏
nostr:nevent1qqsy2x9mquqmyfe7ds4evtguudn7hhrkxvrd2c6cxfa209gx752nh2gex8e5v
i rotate the qr manually, but if you click the donate link it gives you a fresh address or lightning
Maybe this will make things easier once more stable. Silent Payments Desktop wallet. Currently in alpha stage
nostr:nevent1qqsy2x9mquqmyfe7ds4evtguudn7hhrkxvrd2c6cxfa209gx752nh2gex8e5v
Static support address - when silent payments?
Working on Silent Payments. There’s an alpha release for testing a desktop wallet application. First milestone
nostr:nevent1qqsy2x9mquqmyfe7ds4evtguudn7hhrkxvrd2c6cxfa209gx752nh2gex8e5v
Finally an alpha release for people to dip their toes into Silent Payments through BlindBit
First alpha release for testing of BlindBit Desktop. BlindBit Desktop is a pure Silent Payments (Bip 352) wallet for desktop. All scanning is happening locally, so the public indexing server does not learn anything about your transactions.
*Core Features:*
- Local scanning, reaping the full benefits of high privacy with Silent Payments
- Background scanning in tray, you will always be at or close to chaintip
- Simple GUI to manage the wallet
If you are keen on playing around with Silent Payments (BIP 352), this Desktop Wallet might be for you.
https://github.com/setavenger/blindbit-desktop/releases/tag/v0.1.0-alpha.1
*SHA256 Sums:*
b9c025f0c22a419248d2aa9000a905c90290b7182d5eafdca927f55357e9a465 BlindBit-darwin-amd64.zip
70e230bfb69ceaf2d7e03e02c23f099cebf26d45f933cb233ca7fa409e28ec0c BlindBit-darwin-arm64.zip
76f08a27a256a5940af024d28efd53fe22b5c1b5df0cbcc8a4b4dba3e6861da9 BlindBit-linux-amd64.tar.xz
745394ca580e454c63da4a37c51aa79ee9d5be02ae9c34ce56fc09b58ba3dce9 BlindBit-linux-arm64.tar.xz
2829dd3e430a681ea3a49501db18707f2a18823a478990429d9daedcd3a51d89 BlindBit-windows-amd64.exe
So it's an actual algorithm change which brought these performance benefits? How come we don't find this in libsecp256k1 - Could your optimisations also be ported into libsecp? 🤔
so, i have to stop because i think i have exhausted the possibilities for now, but...
https://github.com/mleku/p256k1/blob/main/bench/BENCHMARK_REPORT.md
this is a comparison of this new ported-from-the-c version of the nostr EC necessaries - deriving pubkeys, signing, verifying, and ecdh shared secret generation.
it now is the fastest at all (keep in mind the CGO one has a small CGO overhead but it's the one in bitcoin core)... except that pesky goddamn verification.
so, best i can figure out, the GLV optimization is the secret sauce. i've done every other trick and it squashed it to better than btcec, but only by a margin of like 15%, core's verify function is soaring out ahead at nearly 4x faster.
however, ironically, the ECDH is faster now, where core and btcec are about the same. i dunno if the pubkey derivation is actually correct, that looks like craziness. looks like it's looping many times and rejecting something or idk. loads of memory and time.
anyhow. signing is fast, which is a plus.
maybe i can do better on the verify function in the future. the impression i'm getting is that getting GLV to work right will be a tedious and long winded, probably days long process. but then it will probably run as fast as core's version. maybe. buut even still, all things considered, ~4x slower isn't that bad and my library is now officially the best choice for Go nostr dev except for the verification.
puzzles me how this stuff is so arcane after dozens of times looking at it 50 different ways it still couldn't make the GLV not bugger up the r1/r2 ... tbh i barely even grasp what any of this shit is in anything much more than an abstract, wibbly wobbly sorta way.
i'm just pleased that i made it basically mad to not use pure Go for secp256k1 signatures for a Go app.
i am gonna keep hunting that GLV solution though. i'm tired i still have a big W to note. i'll just leave it as is. orly will upgrade to it soon
i'm still kinda shocked that it is actually faster at signing, most of the time, than the core secp256k1 library, i mean, really. that was actually just the result of a bit minimizing allocations that dropped it that low.
might have been other things too.
has been quite interesting, to watch that when some operations got better, others got worse, at the same time. wandered down a few paths like this. i do wish i could get better verification speed tho 😭
> however, ironically, the ECDH is faster now, where core and btcec are about the same
Might be a constant time thing?
Frigate v1.2.0 has been released.
Frigate is an experimental Electrum server testing efficient Silent Payments scanning with ephemeral keys.
The major feature in this release is GPU acceleration of the cryptographic computation required for Silent Payments scanning. This provides a dramatic (over 10x) performance improvement over CPU computation, and makes a public Silent Payments Electrum server a practical reality for the first time.
To learn more, see https://github.com/sparrowwallet/frigate
More and more infrastructure for Silent Payments is being built and further improved, love to see it!
Does nostr:npub10r8xl2njyepcw2zwv3a6dyufj4e4ajx86hz6v4ehu4gnpupxxp7stjt2p8 also work for signing binaries/packaged applications for desktop? #asknostr
BlindBit Desktop alpha is quite soon™
so, i'm trying a new thing with Junie
i've asked it to take the NWC package of https://github.com/getAlby/js-sdk and translate it to #golang
i'm sure it's gonna not work but it might be good enough that i can fix it and make it work.
why alby built half of their infra with go and never considered building the client/server parts of the NWC SDK so they can be used by go based apps is beyond me. but hopefully i will fix this, and i'm NOT porting it to go-nostr, because that is a bag of dicks, slathered in blueberry and pickles.
Maybe this can help. It's an implementation of me hijacking the spec to transfer utxos and other data via nostr for a silent payment thing I've been working on. It's server side code but at least it's GO...
https://github.com/setavenger/blindbit-scan/tree/master/pkg/networking/nwc
I think LNBIG disclosed their numbers just a month or two ago and I faintly remember that the yield was definitely not in that ballpark. It was mentioned in some rabbit hole recap a while back
Actually I don’t even know what ntag 213 is. I have not dabbled in physical transfers in Bitcoin yet. Only heard of opendime. So in my head I’m comparing the tradeoffs to that.
Why would I want to sign with the keys on the chip. The chip has its own key pair which is not related to the server right?