janniks
janniks
This seems to be working (tested on latest main playground example)
Forgot about this one. A lot of recursive viewing doesn't really work in our explorer due to security concerns, so it might not be too important to have these endpoints...
Currently not shown, would need API changes
Yes, these are great!!!
 _minor notes, might already be covered elsewhere or already todo:_ - Make space between a number+symbol non-breaking (to keep them on the same line)...
Thanks, yes `https://api.hiro.so/ordinals/v1/inscriptions?limit=20&offset=0&order=desc&order_by=rarity` is timing out -- we'll look into it 🙏
Thinking this could become a nested `.metadata` field or similar. Thinking out loud below, nothing final ```js { ...inscription, "protocol": "brc-20", // ^-- maybe as single `protocol` field, providing the...
@rafaelcr what are your thoughts on this? I think keeping logs/reasons is too complicated for now. (although it would make debugging easier as well, e.g. keeping the reason for a...
Maybe also add an additional endpoint/filter to get activity by inscriptionId. 🤔 Mainly thinking from an explorer perspective. → If the inscription isBrc20, then fetch the events data, to nicely...
Careful. This was the intended behavior. It is confusing, yes. The “end” cycle is non-inclusive (range style). This way a event that didn‘t make it into the intended reward cycle...