Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Do not merge] Ord5 - explorer #17

Draft
wants to merge 63 commits into
base: master
Choose a base branch
from
Draft

[Do not merge] Ord5 - explorer #17

wants to merge 63 commits into from

Conversation

ericatallah
Copy link

No description provided.

raphjaph and others added 30 commits March 1, 2023 19:25
Co-authored-by: ericatallah <[email protected]>
```
error: Failed to send reveal transaction
because: JSON-RPC error: RPC error response: RpcError { code: -26, message: "non-mandatory-script-verify-flag (Invalid Schnorr signature)", data: None }
```
```
thread 'main' panicked at 'signature hash should compute: PrevoutKind', src/subcommand/wallet/inscribe.rs:360:8
```
reveal TX for inscriptions containing a parent.
Ignore malformed inscriptions.

Co-authored-by: Clarke Benedict <[email protected]>
raphjaph and others added 28 commits March 22, 2023 14:25
* blue text only on hover in navbar

* white text in navbar

* add missing semicolon in css

* change navbar background to black

* switch search button from text to symbol

* improve navbar submit element style
Clippy
Co-authored-by: Greg Martin <[email protected]>
Co-authored-by: raphjaph <[email protected]>
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:
The child inscription must have a parent inscription.
The child inscription's body data must be valid JSON.
The child inscription's body JSON data must contain a field named
"use_p", with any value.
Proposed JSON standard:

```
{
   "use_p": 1,
   "params": ["tokenID=4969"]
}
```

Co-authored-by: clrke <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants