However, for common satoshis, all revelation transactions will now only include one input. And thanks to opportunistic batching, this means that you can now make 10,000 (or more!) common-satoshi inscriptions in a single order! Happy inscribing!

Typically, the expensive component of a bitcoin transaction is its inputs, as besides specifying a 36-byte-outpoint, each usually also has a 64-vByte-signature. Chisel's unique algorithm for selecting arbitrary-offset satoshis preclude applying this technique to non-common sats.

By harnessing the power of envelope concatenation, batch inscription orders on common satoshis can now see a mining fee reduction of up to 70% when using @chiselxyz! How is this possible?

What if, hear me out, each rune token was tracked individually? Ordinals for Runes is the logical evolution of the protocol.

Thank you so much for trusting @chiselxyz with your halving-block-etching, and congrats on securing rune ID 17!

Thank you so much for the endorsement, @thatwagmigirl!

Thank you so much for trusting @chiselxyz with your collection!

Create some of the first multi-parent-inscriptions today! Head to https://t.co/UR3GSuAdyA and happy inscribing!

https://t.co/bUZBQ2iBv6

The incident has been resolved; happy inscribing!

Chisel is temporarily unavailable while our infrastructure provider is resolving some internal DNS routing issues. Hoping to get it resolved as soon as possible, and apologies for the inconvenience!

Thanks so much for using @chiselxyz to create what remains one of the earliest multi-parent-inscriptions!

@ChiselXYZ @BlackxBTC @DomoDucks And the current record holder of the most parents: https://t.co/Oyo9v7jnmc (by @Nuroblob)

Here are some example multi-parent inscriptions created using @chiselxyz: https://t.co/aZ6MoSEcIE (by yours truly) https://t.co/QdzDO00AXl (by @BlackxBTC) https://t.co/3R6OpxQNb0 (by @DomoDucks)

Here are some example multi-parent inscriptions created using @chiselxyz: https://t.co/aZ6MoSEcIE (by yours truly) https://t.co/QdzDO00AXl (by @BlackxBTC) https://t.co/3R6OpxQNb0 (by @DomoDucks)

Multi-parent indexing has recently been merged into ord, and I'm thrilled to announce that @chiselxyz has embraced this feature with an updated UI! Visit https://t.co/UR3GSuALo8 to craft some inaugural multi-parent inscriptions. Huge shoutout to @raphjaph and @rodarmor!

Thank you so much for using @chiselxyz for your parent/child reinscription! I would wager there are a very precious few examples of that being done so far.

For the parent field (3), in lieu of concatenation, ord would simply need to treat each value as a push to an array, verifying each parent individually. A similar technique could open up fascinating possibilities with the delegate tag (11), enabling fallback delegation.

Thank you so much for trusting @chiselxyz with your multi-parent collection! How does that work? For most tagged fields, ord only parses the first value for a given key. An exception is the metadata field (5), where values are concatenated. 🧵

Thanks so much for trusting @chiselxyz with your innovative art! The masks have undergone quite the evolution.