Read on Twitter
@raphjaph recently merged @rodarmor's Recursive Inscriptions PR.
Recursion opens up a lot of interesting new mechanics for Inscriptions, such as making Inscriptions "larger" than 4mb π
What really is "recursion" and what might it mean for the future of Inscriptions?
Recursion opens up a lot of interesting new mechanics for Inscriptions, such as making Inscriptions "larger" than 4mb π
What really is "recursion" and what might it mean for the future of Inscriptions?
Simply put, recursion means that "an Inscription can request the content of other Inscriptions"
Like putting an Inscription inside another Inscription
Like putting an Inscription inside another Inscription
What's an example of this? Take one of our favorite projects: @GhostsBtc:
You have the ghost base layer Inscription and you have a bunch of traits inscriptions. Instead of generating these before Inscribing, the base Inscription references other Inscriptions ON-CHAIN
You have the ghost base layer Inscription and you have a bunch of traits inscriptions. Instead of generating these before Inscribing, the base Inscription references other Inscriptions ON-CHAIN
You can do this with multiple Inscriptions, allowing the Inscription you're viewing to actually contain more than 4mb.
Previously, the largest Inscription ever was the @BitcoinMagazine May edition (we at @LuxorTechTeam Inscribed that)
Now we can *effectively* go bigger.
Previously, the largest Inscription ever was the @BitcoinMagazine May edition (we at @LuxorTechTeam Inscribed that)
Now we can *effectively* go bigger.
Remember the DOOM Inscription? It was only 30kb.
Most video games are larger than 4mb.
What if you could Inscribe different pieces of the code of a game like DOOM and "load" them into another Inscription?
This unlocks a lot for developers.
Most video games are larger than 4mb.
What if you could Inscribe different pieces of the code of a game like DOOM and "load" them into another Inscription?
This unlocks a lot for developers.
It's expensive to inscribe a bunch of high-quality images for a collection.. What if you only had to inscribe the base layer + traits?
Instead of owning the JPEG, your community owns an Inscription that "builds" the Inscription live.
And it's all on-chain π
Instead of owning the JPEG, your community owns an Inscription that "builds" the Inscription live.
And it's all on-chain π
Now it gets really crazy π€―
Imagine you want to upload a whole program (people have done this).
Let's say you want to run the whole Bitcoin Core client. Bitcoin Core is about 15mb. That's bigger than Bitcoin's 4mb block size limit.
Imagine you want to upload a whole program (people have done this).
Let's say you want to run the whole Bitcoin Core client. Bitcoin Core is about 15mb. That's bigger than Bitcoin's 4mb block size limit.
Imagine we could split up parts of Bitcoin Core, load just an executable frontend, and the program "calls" the code it needs from other Inscriptions.
You're now running Bitcoin ON Bitcoin.
We can theoretically do this with a lot of different programs.
You're now running Bitcoin ON Bitcoin.
We can theoretically do this with a lot of different programs.
Recursion unlocks way more than just these simple ideas, stuff we haven't even thought about.
But it's about to get really fun. Inscriptions 2.0 are here.
We'll be doing deep dives on this in on our Youtube channel in the next couple of days!
youtube.com/channel/UCNiotβ¦
But it's about to get really fun. Inscriptions 2.0 are here.
We'll be doing deep dives on this in on our Youtube channel in the next couple of days!
youtube.com/channel/UCNiotβ¦
β’ β’ β’
Missing some Tweet in this thread? You can try to
force a refresh
γ
