Here is a little article about what was broken with NIP-03 and how i fixed it.
Unfortunately the blossom server gods seem to hate me, so the beefy android APK and zapstore release will have to wait. But you can always build it yourself from the repository. Links to the repository and the two NIPs are in the article. Devs please have a look, especially @utxo the webmaster 🧑💻 because i abused wisp to make the client :). And @Vitor Pamplona because i think amethyst is the only client that uses NIP-03 anyway i think.
Im going for a walk
View article →
With 3 different GUI apps, for each system one:
A db that shows you in a fancy way that, and how, things are verified (and a bunch of settings and knobs and bells and whissles)
There is a client that can apply the new timestamping method on Nostr events right now today!
And an OTS aware relay:
They are all connected such that this post from 
I marked the event ID so you can see it is the same as here in the OTS proof database, what it indeed passes verify. The client extracts OTS proofs from kind1040 events, and sends them to the db automatically:
But as you can see, the db itself is fully capable of verifying all the proofs. Even Peter Todd's old NIP03 style proof, because it is just another OTSproof after all.
Things land on the relay just fine.
Thats it.
I want to reiterate that I have no idea what the robot wrote, other than that it works. so be careful. It is opensaus:
