Apologies in advance for all the test reply messages related to me testing "zaps" using BCH. I'm also experimenting with various expiration settings etc to get everything cleaned up by default. Until I get some rudimentary client support for this I need these messages to make everything working correctly.

Here's a BCH wallet running in my car. Tesla really should do more to encourage in-car software building.

I've been taking a casual look at Nostr npub keys. I'm finding an unexpected number of public keys leading with zeros (after examining only a few thousand). Assuming these are derived from proper public keys using proper hashing algorithms, I would not expect that. Either I'm missing something, or quite a few people are generating npub keys inproperly.

So the browser on Teslas used to have "Tesla" in the user agent string. I just tested on mine. It does not any longer. Anyone know of methods to recognize when running on the screen inside Teslas? I've got a few apps that could use a larger font size for instance, and I don't want to screw around with people using KHTML etc on Linux computers.

What do I need to do to get a "BCH payment receipt" "kind type", similar to kind 9735 "zap receipt"? Assuming I need to demonstrate working code and/or write a complete NIP first, any suggestions on what "kind" to use while testing?

So I'm thinking of doing the unspeakable. Adding support for layer 1 zapping to Nostr using BCH. Hate me gently.