Function is not broken, you might have to wait a while, it depends on how often the timestamp-server decides to do a bitcoin transaction, which i thin...
Function is not broken, you might have to wait a while, it depends on how often the timestamp-server decides to do a bitcoin transaction, which i think is only a couple of times a day. In general, this type of timestamping is not suited for minute/hour timescale stuff anyway, more on the level of multiple hours/day basis
NIP-03 itself is broken, but thats for a different reason entirely. When designing the standard, it did not occur to us that in Nostr, you sign the event-ID of an event. Because the current standard timestamps that event-ID, you technically don't know when something was signed, someone could have actually signed it after the fact.
This, in theory, could lead to some weird exploit. Lets say i am planning to steal your keys. I could start creating all kind of events in your name today, and timestamp them, even though i am not able to sign them yet.
Then later, when i successfully stole your keys, i could sign those messages after the fact, and then from the outside worlds perspective, those seem like legitimate timestamped events that you posted before your keys got compromised; which would undermine the entire purpose of it all.
The fix is not that difficult, but its annoying we will have to deprecate the current standard blablabla etc.