>>> luke's server responds with a list of transaction IDs that contain "spam", and provides a "zero knowledge proof" that proves to knots nodes that those "spam" transactions are valid, without having to download them. >>> A "zero knowledge proof" solution, that proves transaction is valid without having to download the "spam" part of it, is an excellent idea. Every node operator can define their own definition of "spam" and choose the authoritative server(s) providing the list of txid containing the "spam". This will bring to life new competing full node implementations that will stay 100% compatible with current network protocol. #Bitcoin future is bright!

I highly value what you have done for Bitcoin, but this time you are wrong! I would be very sorry if this unfortunate debate left you with an irreparable bitter disappointment and you became an enemy of Bitcoin, like some other prominent figures among developers in the past. Bitcoin is at its very core the right to choose for yourself. There is no excuse for taking away the right of a node operator to determine the settings of their own node.

Two questions if somebody can help? We have BOLT12 and BIP353 setup for a human readable Lightning address - ฿[email protected] - and it is functioning properly. Why is it marked as Invalid Lightning Address on our profile? We have user address [email protected] on our profile and the nostr.json file on our domain is correctly formatted and accessible. Why is this address also marked as invalid? #asknostr #nostr