Casey Rodarmor

BRC-721 is a nonstarter: - Uses inefficient text based encoding - Doesn't provide blockspace savings, since recursive inscription can be as small as `` - Uses pubkeys, doesn't fit in...

I'm not sure we need a formal OIP structure at the moment. GitHub issues are probably okay for now. Others are free to do this though.

Nice find! Just opened #2189 with a fix.

Deplaning in Lisbon at the moment, so I can't give this a proper review, but the additional endpoints need to be combined into one CSP headers, instead of adding new...

> Hey, can we also make available inside inscriptions the inscription number and id? I think those are cool as well to be used as seeds for generative art algos...

I'm fine with ditching `/-/`, and just whitelisting `/content/` directly. The CSP header will get longer as we whielist more endpoints, but in practice it won't be an issue unless...

> Before I merge this `self` binds to the same URL scheme but `*:*/content` allows any scheme (i.e.`http` or `https`) but the layering will make sure the stricter of the...

@eloremarc Yup, I just opened #2173 to support inscribing CSS and JS files. No changes should be needed to the CSP headers, they use `default-src`, which covers all kinds of...

@jerryfane You can't, although you could compose text files from an HTML file.

> We've just launched one of the first recursive collections (10k): ["Recursive Punks"](https://github.com/RecursivePunks/RecursivePunks) and all people have minted using /-/ and : in the syntax: > > Example: https://ordinals.com/content/edf8823de582b35d1b4d32679227c7cd6c86d46e29665626ec40f0f16bb3347ai0 >...