You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If you inspect the Auth header coracle sends for NIP-96 uploads, you'll see that the payload tag does not change for different files. It is always 44136fa355b3678a1146ad16f7e8649e94fb4fc21fe77e8310c060f61caaff8a (which happens to be sha256("{}"))
This is because the body passed to nip98Fetch() in commands.ts is a FormData which stringifies to "{}"
Evidently, nostr.build (and other?) NIP-96 servers are not checking the payload tag, because this doesn't appear to cause an issue.
Furthermore, what the payload tag should actually be, appears ambiguous (to me).
If you inspect the Auth header coracle sends for NIP-96 uploads, you'll see that the
payload
tag does not change for different files. It is always44136fa355b3678a1146ad16f7e8649e94fb4fc21fe77e8310c060f61caaff8a
(which happens to besha256("{}")
)This is because the
body
passed tonip98Fetch()
in commands.ts is aFormData
which stringifies to"{}"
Evidently, nostr.build (and other?) NIP-96 servers are not checking the
payload
tag, because this doesn't appear to cause an issue.Furthermore, what the
payload
tag should actually be, appears ambiguous (to me).See nostr-protocol/nips#1376 for details.
The text was updated successfully, but these errors were encountered: