Totally agree with your assessment of the protocol. I’ve been wrapping my head around it for the past couple of weeks, and it seems simple enough on the surface, but in that time I witness the docs radically change several times just for NIP-01. I spent over an hour just the other day trying to figure out what in the hell the ‘d’ tag for kinds between 30000-40000 even stands for.

To top it off, it’s confusing as hell to my analytical brain. For example:

“

To prevent implementation differences from creating a different event ID for the same event, the following rules MUST be followed while serializing:

No whitespace, line breaks or other unnecessary formatting should be included in the output JSON.

No characters except the following should be escaped, and instead should be included verbatim:

A line break, 0x0A, as \n

”

So, there’s supposed to be line breaks or not? If I want them they have to be escaped properly in the JSON? 🤔

I’ll figure it out, just need time.