Ideas on anonymous delivery of secret events

GitHub

nostr-secure-messaging/anonymous-delivery.md at main · shafemtol/nostr-secure-messaging

Contribute to shafemtol/nostr-secure-messaging development by creating an account on GitHub.

#nostr

Having scanned through all of the NIPs, I'm still not sure exactly what is meant by a "note". All notes are events, but I'm guessing not all events are to be called notes? #nostr

NIP: Proof of Freshness

GitHub

Add NIP-XX: Proof of Freshness by shafemtol · Pull Request #296 · nostr-protocol/nips

Proof of freshness based on Bitcoin block hashes. I came up with the use for this while working on another concept which I've currently named s...

#nostr

Going down the rabbit hole of secure, private DMs. I think a good design will require multiple smaller, composable NIPs. #nostr

Exploring a method to reduce the risk of block storms on Bitcoin testnet

There you have it. #777777 2023-02-22T09:58:27Z UpdateTip: new best=00000000000000000005d35085cbcb510c14917f928aaa45facb0c0d24d471ce height=777777 version=0x2feaa000 log2_work=94.018808 tx=807684568 date='2023-02-22T09:58:09Z' progress=1.000000 cache=139.8MiB(1043516txo)

Issues with #nostr NIP-57 Lightning Zaps: - Can be faked, as noted in the NIP itself - Includes payment info that may aid LN surveillance entities, for no good reason (see above) - If you later change your LNURL server or your LNURL server changes the `nostrPubkey` key for whatever reason, you lose all previously received zaps as the old zap notes can no longer be validated

I've been observing issues with sending and receiving #nostr events on certain relays. Added some relays that don't seem to be blocking #Tor as often, hoping that will improve things a little.

Hello 🦝