Rafael Cárdenas

Thanks for your review @jcnelson , I've addressed your observations and I've also added a new section covering considerations for metadata indexers. Looking forward to your comments.

@zone117x and myself were discussing abuse vectors for NFT metadata updates, here's a brief summary on some conclusions we reached: > We should disallow the ability for anyone to trigger...

@jcnelson this SIP is ready for a formal review. Looking forward to their findings.

> Can this SIP be a specification for notifications in general and define more notification types and payloads in the future? @friedger while this SIP wasn't meant to be a...

Done, thanks @jcnelson @kantai !

Thanks for your input @nickgamma , based on your suggestions I think we can introduce a new enum property on the notification payload tuple called `update-mode` with the following possible...

@Jamil > Is that just for backwards compatibility or a more general solution? Exactly. For example, the reference contract allows a token owner to still emit a notification for their...

Hi @friedger, thanks, that is a good question. I really believe these notifications should be on-chain primarily for the following reasons: 1) For newer token contracts, emitting a notification on...

Hi @314159265359879 sorry for the late response. Unfortunately I believe there's no way for the API to give that specific information other than the data it currently returns in the...

Marking as blocked. We need to work alongside the DevOps on this one so we can instantiate testnet ordhook pods with a bitcoin node we can use to test. Also,...