Yeah, it is, I'm mostly kidding. It just looks like nostr 2.0 because it has a similar but separate network architecture and content discovery mechanism.

It's different from NIP 96 in that it's simpler and more focused on discovering verifiable file contents based on the file's hash, whereas it's unclear to me how strong the guarantee is with NIP 96 that you can verify a file hasn't changed, since the spec says:

> Note that the "" part is from the original file, not from the transformed file if the uploaded file went through any server transformation.

This could probably all be fixed within NIP 96 itself, but hzrd and stu have decided to go in a different direction.