Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Add functionality to handle JSON doc child inscriptions as special case
Why: - Some generative art collections have inscribed all art within a single parent inscription to save considerable storage space on the blockchain. - The ord explorer is unable to currently support collections inscribed in this manner. This commit adds this support. What: - In order to support these generative art collections, we need to be able to inscribe the metadata for children in an agreed upon JSON spec. - These child inscriptions are JSON documents containing url parameters that instruct the parent inscription to render a specific item in the collection. How: - Since all art is contained in the parent, we added a simple redirect to render the parent inscription with included url parameters. - There are 3 constraints which must be in the child inscription before the redirect can happen: 1. The child inscription must have a parent inscription. 2. The child inscription's body data must be valid JSON. 3. The child inscription's body JSON data must contain a field named "is_ord_pointer", with any value. Proposed JSON standard: ``` { "is_pointer": 1, "url_params": ["tokenID=4969"], } ``` Related Issue: - https://github.com/casey/ord/issues/783 Co-authored-by: Clarke Plumo <[email protected]>
- Loading branch information