I reviewed the code to understand how it works and to find vulnerabilities. After about 2 hours, I didn't find anything. It is not a formal audit but it is better than nothing.
nostr:nevent1qqsp330l32drvn9psg8khnjvy40kgz3hqs5vgc3rjanntvkn2xfynzsppemhxue69uhkummn9ekx7mp0qy08wumn8ghj7mn0wd68yttsw43zuam9d3kx7unyv4ezumn9wshsz9thwden5te0dehhxarj9ehhsarj9ejx2a30jync33
Login to reply
Replies (1)
At WalletScrutiny I want to establish something similar. Attestations to have tried to reproduced binaries. "I tried for 4h and failed" is a data point just like your "I tried to find weaknesses for 2h but it looked ok". That's far far better than no external statements at all and I hope to standardize this on nostr. nostr:npub1qw6sxmwrmwpxqsc8cxty62ujvst6j8pmz8hhtwnv54gpn6dh5c4qms4882