✒️
EVM INK
  • 🛡️EVM INK
  • 📜LitePaper v0.0.7
  • 🗝️Token
  • 🛣️Roadmap
  • 🔗Official Links
    • Website
    • Twitter
    • Discord
    • Telegram
  • 🌐Overview
    • ❓What are inscriptions?
    • ⁉️How to inscribe?
    • 🔢What is an indexer?
    • 📥Our Current Indexer
    • 🏁Benefits of an indexer
    • ❤️Advantages of EVM INK
    • 🎓Inscription types support
  • 🏗️Proposals
    • INSK-1 : Tokens (Outdated)
    • INSK-2 : Collection
    • INSK-3 : Recursive inscriptions
    • INSK-4 : Unified Token Standard
  • 📈Infrastructure
    • 🌉Going Bridgeless
    • 💻Indexed Virtual Machine
    • 🗺️Non Arbitrary Tokens
    • 💠Cross-chain inscriptions
    • 🎞️Inscribed Domains
    • 🎮On-chain games
  • 🎯Indexing Rules
    • 🔤For Text-based
    • 🎨For Art-based
    • 🎞️For Domain-based
    • 🗺️For Map-based NATs
    • 💠For Cross-Chain
    • ⛓️How to host your indexer
  • 🛒Marketplace
    • 📚How does it work?
Powered by GitBook
On this page
  • How to make it
  • Interesting use cases
  1. Proposals

INSK-3 : Recursive inscriptions

PreviousINSK-2 : CollectionNextINSK-4 : Unified Token Standard

Last updated 1 year ago

The recursive inscription includes/loads/refers to the content of other inscriptions. In simple terms, it would mean that first, you inscribe an image and then refer to it in another inscription. Here is example

The final that includes all three images above

How to make it

You will see a button under the image if you open any of the above. Once you click it, you will see a full screen with the inscription. This is the URL you can use to refer to the inscription.

To refer to it, you would need to use HTML. Here is an example of an HTML file you can use.


<!DOCTYPE html>
<html>
<h1>
RECURSION!
</h1>
<img src="https://evm.ink/eip155:1/content/0x73952ed79a934b7b84d1ac776ee6d4845adb24efd15af7347a00b18b1b9aca53:0">
<img src="https://evm.ink/eip155:137/content/0x4bf1b4babfa814ede9048eea937316166016ca97aae48dd01604709f97a3858e:0">
<img src="https://evm.ink/eip155:56/content/0x8bb64a09f82061219d4e26d8eee085986c5c4e32edede4606dc770a26eacabcd:0">
</body>
</html>

We use an absolute path here instead of a relative because many platforms show inscriptions, and even if it works on one platform, it will not work on another platform because there is no standard for the path to use. We can use a relative path if everyone agrees on the same path to inscription data.

Interesting use cases

  • Inscribe traits on a cheap chain and then build a complete image on Ethereum.

  • Inscribe one huge file by first slicing it into multiple files

  • Inscribe the game by inscribing game assets first

🏗️
Image inscribed on Ethereum
Image inscribed on polygon
Image inscribed on bnb
image