The latest update of Ord, version 0.21.3, introduces a series of features that look set to please its active user base. Central to this release is the opportunity for more expressive interactions, with the addition of metadata to burned inscriptions. Users can now attach unstructured, human-readable details to their burned inscriptions, visible on the inscriptions’ respective pages. It’s an entertaining tweak that enhances how inscriptions tell stories or mark moments, appealing to those who value the narrative potential of inscriptions.
Another feature that brings practical flexibility to users is the new ord wallet split
command. This command makes it possible to perform arbitrary asset splits using a YAML file to specify outputs. This includes designating a destination address and setting values in BTC as well as in runes. It’s an improvement that could simplify complex asset management scenarios, providing the precision that many have been waiting for.
Complementing this is the ord wallet sign
command, designed to sign messages using an address from the wallet. Users have the option to choose a specific address or even sign using the address holding a given inscription. This addition should prove especially useful for those who need verifiable proof of wallet ownership or want to use Ord to perform authenticated message signing.
The new /outputs/:address
server endpoint extends Ord’s capabilities further. It gives users a way to retrieve outputs linked to an address while enabling filtering by different types—whether cardinal, runic, or inscribed outputs. This endpoint provides a smoother path to access data, which should simplify asset tracking and analytics.
A quirky and fun enhancement comes in the form of the charm now attached to palindromic sats. This charm reflects a community-approved aesthetic and continues to draw attention to these symmetrical satoshis. It’s a playful addition that adds a bit of visual flair for those hunting for these rare beauties. It might be the last sat-based charm introduced, but who knows what the future holds?
A welcome fix in this update addresses wallet restoration from a mnemonic phrase. Previously, rescanning the chain correctly when restoring a wallet was missing, but now this has been patched up. Users can also specify a starting timestamp, making the process more efficient and streamlined. It’s a small yet significant repair, and one that could save users considerable time and trouble.
Ord now also handles runestones more smoothly, with no more splitting into multiple data pushes. This approach was previously in place under the assumption that OP_RETURNS had a 520-byte script element limit, which, as it turns out, they don’t. Consequently, runestones remain intact, which should avoid any unnecessary complications when dealing with script elements.
Another quality-of-life update involves the visual presentation of long strings on ordinals.com. If a page is displayed on a narrow screen, long hashes, inscription IDs, and addresses will collapse, replacing excess characters with …
. It’s a small but sensible interface improvement that makes the platform more accessible and easier to navigate, especially for users on devices with limited screen real estate.
These updates make Ord 0.21.3 a release packed with a mix of functional improvements and fun flourishes. By expanding expressivity and refining tools for asset management and signing, it caters to both serious users and those who appreciate the platform’s playful elements. It’s clear that the development team is responding to user feedback while also adding thoughtful details that could attract even more interest to the community.