testing zaps for this note… we made six attempts to⚡zap this note, at walletscrutiny@btcpay.nz, over a period of 1 minute. in each case, we found that your lightning address server did not respond correctly. (the failure point was when we did a get request to your specified callback url: https://btcpay.nz/BTC/UILNURL/pay/lnaddress/walletscrutiny ). your server did not produce an invoice, thus the zap failed. the error we got was "Lightning node could not generate invoice with description hash". if you wanted to fix this... you could try getting a free rizful lightning address -- https://rizful.com ... if u get it set up, pls reply here so we can do this ⚡zap test again.
We’ve been busy but quiet these last months. nostr:npub1qw6sxmwrmwpxqsc8cxty62ujvst6j8pmz8hhtwnv54gpn6dh5c4qms4882 improved the site a lot by adding new features around #nostr based build verifications.
We hope other projects in the nostr ecosystem like nostr:npub1wf4pufsucer5va8g9p0rj5dnhvfeh6d8w0g6eayaep5dhps6rsgs43dgh9 nostr:npub10r8xl2njyepcw2zwv3a6dyufj4e4ajx86hz6v4ehu4gnpupxxp7stjt2p8 will see the value of these verifications and start integrating them. The more products that build on reproducibility, the more users can truly apply the principle of “Don’t trust - verify.” Binary transparency shouldn’t remain a niche feature - it needs to become the default.
If you run software that touches your private keys - be it nostr clients or bitcoin wallets - without binary transparency, only whoever built the binary really knows what code you’re running.
nostr:npub1r709glp0xx2zvgac45wswufjst5xgr7cear5a8me7x9vazhjzmksp2sf7d and nostr:npub1vf6wyw9j38sm96vwfekwvqxucr9jutqrmwdc2qnql79a66al9fzsuvt9ys checked the reproducibility of almost 300 binaries. The 304 verifications by nostr:nprofile1qqspdzm69nvthys9c06hfhj5qcrddaxyvutu29j0gumnlhxw9wwdxdgpz3mhxue69uhhyetvv9ujuerpd46hxtnfduqs6amnwvaz7tmwdaejumr0ds0h54vv are all the old verifications we had migrated to nostr. And the backlog keeps growing as we cover more and more products with frequent updates.
Are we doing something valuable for the space? A nostr:npub1spralxq6jlw5rdy0249vqr5sh43rfrlx2wzv3rhjjqedw559w9psrs8s72 grant says yes, and community endorsements confirm it - but the project itself also needs scrutiny.
We recently introduced "verification endorsements":
This is a simple contribution many could provide. If you read a verification and it looked plausible and complete and you trust the author, mark the verification as verified. If you ran the documented commands yourself on your hardware and got to similar results, please endorse the verification!
Even more importantly label verifications as invalid and leave a comment about what's missing when you find issues! Don't be shy!
Our goal is to document all steps such that all mildly technical users (you should be comfortable with a Linux shell) can reproduce our findings. If that's not the case, please provide your feedback and we will improve ✋.
And if you maintain one of the products we check, share your own verification as a template for others!
Discussion
No replies yet.