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

Give us your best Inscription examples! will be added to documentation for Issue 949 #3769

Open
wants to merge 6 commits into
base: master
Choose a base branch
from

Conversation

cryptoni9n
Copy link
Collaborator

@cryptoni9n cryptoni9n commented May 20, 2024

The purpose of this PR is to gather good examples for Issue #949

Please submit feedback of any on-chain inscriptions that you feel make exemplary use of following inscription technologies for their respective areas of documentation:

  1. Inscriptions

    3.1. Delegate
    3.2. Metadata
    3.3. Pointer
    3.4. Provenance
    3.5. Recursion

    • a) Remixing the content of existing inscriptions.
    • b) Publishing snippets of code, images, audio, or stylesheets as shared public resources.
    • c) Generative art collections where an algorithm is inscribed as JavaScript, and instantiated from multiple inscriptions with unique seeds.
    • d) Generative profile picture collections where accessories and attributes are inscribed as individual images, or in a shared texture atlas, and then combined, collage-style, in unique combinations in multiple inscriptions.

    3.6. Rendering

Updating the list below with all submissions:

Delegation:

  • This inscription was inscribed as a delegate of this inscription and is also the parent inscription of a rune.
  • The collection Oscillations * utilizes delegate, provenance, recursion, sat-endpoint, and detects the kind of sat that each piece is inscribed on (sattribute-aware). Each piece is a delegate of this inscription.

Metadata:

Pointer:

Provenance:

Recursion

  • The Abstractii Evolved generative collection uses the recursive blockheight endpoint as a seed
  • (b) This code is called recursively in this inscription
  • (b) This code is called recursively in this inscription allowing it to operate as a drawing program.
  • (b&c) Blob is a generative collection that seeds generation with metadata. It also uses delegation as the rendering engine. The Delegate is updatable with the sat endpoint. Delegate uses threeJS, React 3 Fiber and other libraries via recursion. Also each blob is on a satname starting with blob
  • (c) Abstractii Genesis uses the inscriptionID as a seed
  • (d) OnChainMonkey

Rendering:

@cryptoni9n cryptoni9n changed the title Initial commit for discussion PR on Issue 949 Give us your best Inscription examples! will be added to documentation for Issue 949 May 20, 2024
@phorkish
Copy link
Contributor

Here's an inscription that I made that uses recursion, delegation and metadata. And also provenance if you count the structure of its dependencies.

https://ordinals.com/inscription/4fb16cb8362e117f671fdbc105d6738887cd58432d25cec328212e217426f4fdi0

Each inscription is a full application that reads in the metadata and uses it to draw pixel art. The idea is that you can delegate to this inscription with your own metadata and it'll render your pixel art. If you hover over the inscription there's a menu in the top right, which opens up a drawing tool that generates the metadata that you need to inscribe.

For example, I redrew my Bandit here

https://ordinals.com/inscription/454700af2cffd3a872daeb89598a891f5fe9936225838a8c4522f491f246ca0ai0

@elocremarc
Copy link
Contributor

Bitcoin Magazine Cover

Child endpoint where the children are rendered into the parent inscription.
https://ordinals.com/inscription/60902330

Blob

https://ordinals.com/inscription/b10b00bfb146fee3e86d6cbd8e8c954c485da41be480c0b21a6a63de7986892bi0
Generative collection that seeds generation with metadata It also uses delegation as the rendering engine. The Delegate is updatable with the sat endpoint. Delegate uses threeJS, React 3 Fiber and other libraries via recursion. Also each blob is on a satname starting with blob

Sat endpoint:
https://ordinals.com/sat/1749358685368819

Delegate:
https://ordinals.com/inscription/bc6b4132d7772e78eb4b8390ebe9970c6e5315ec0e0f644a88b4e5b35ced43d3i0

Parent:
https://ordinals.com/inscription/648f02fbb36d7841dbf629966ea9c82a60255044fbdd09b31533c0b9fafa573di0

Abstractii Genesis

A generative collection that uses inscriptionId as seed
https://ordinals.com/inscription/b2de70a5658d3659b74a9a349e02ed9396318eab844073b6f35e726dea9e103ei0

Abstractii Evolved

A generative collection that uses blockheight as a seed
https://ordinals.com/inscription/c56795a454a30bb6866686770f14d015d53f3cf2ddfa5154e34a7cd1120a51efi0

Rug Me

Child endpoint and Sat endpoint example collection
Collector can update background color by inscribing a child
Creator can "rug" collection by inscribing an additional image onto the entire collection using the sat endpoint
https://ordinals.com/inscription/f87a6b16a1224b65f9c8ea55e1718585b3075373581689e343860c12a70d15c7i41

@cryptoni9n
Copy link
Collaborator Author

thanks @phorkish & @elocremarc for the excellent examples! I've incorporated them into the list in the OP.

@matthewvollmer
Copy link

*Oscillations

My collection Oscillations * utilizes delegate, provenance, recursion, sat-endpoint, and detects the kind of sat that each piece is inscribed on (sattribute-aware).

Collection Link: https://gamma.io/ordinals/collections/oscillations-mdv
The 500 different pieces are on 7 different types of sats, each with different generative engine parameters.

@cryptoni9n
Copy link
Collaborator Author

cryptoni9n commented May 23, 2024

thanks matthewvollmer, I've added your examples to the list in the OP! I think I minted some runes that are associated with this collection, RUNIC•SUBSTANCE?

@cryptoni9n
Copy link
Collaborator Author

seems like we may have all of the suggestions we're going to get so I'll start working on trying to integrate these examples into the docs.

@cryptoni9n cryptoni9n closed this Jun 10, 2024
@cryptoni9n cryptoni9n reopened this Jun 10, 2024
@cryptoni9n cryptoni9n closed this Jun 10, 2024
@cryptoni9n cryptoni9n reopened this Jun 10, 2024
@cryptoni9n cryptoni9n marked this pull request as ready for review June 10, 2024 16:55
@cryptoni9n cryptoni9n requested a review from casey June 10, 2024 16:56
@cryptoni9n
Copy link
Collaborator Author

Hi @casey & @raphjaph - I've incorporated the suggestions we received here into the docs. Please review and let me know if there are any edits or changes that you'd prefer.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: In Progress
Development

Successfully merging this pull request may close these issues.

None yet

5 participants