We are upgrading our Bitcoin Mainnet Ordinals infrastructure from ord 0.23.2 to 0.29.1. This release rolls up several versions of indexer improvements, including richer inscription metadata in API responses, new gallery and bulk lookup endpoints, a new recursive endpoint for raw block data, and a fix for indexing transactions that include pay-to-anchor outputs. During the maintenance window, brief interruptions to Ordinals API availability may occur.
RPC Changes: - Inscription JSON responses — added. Inscription responses now include a properties object (attributes, traits, title, and gallery items) along with the metaprotocol field. - Inscription parents — fixed. Invalid parents are now filtered out and no longer returned for inscriptions. - /children routes — added. Child inscription routes now support JSON responses. - /gallery — added. New JSON endpoint for retrieving gallery inscriptions, with paginated gallery items. - /galleries and /collections — changed. /collections now returns results in reverse order, and hidden inscriptions are excluded from both /collections and /galleries. - /missing — added. New endpoint to check whether a batch of inscriptions exists in a single request. - /r/block/ — added. New recursive endpoint that returns the raw block hex for a given block hash or height. - Block inscriptions pagination — changed. Requests for an out-of-range page now return an empty page instead of an error. - Outpoint and TXID lookups — fixed. Outpoints and TXIDs made up entirely of decimal digits now resolve correctly instead of being misrouted. - Sat lookups — fixed. "Not found" sat index responses are no longer cached, so subsequent lookups return current data. - Rune amounts — fixed. Decimal amounts with excessive precision or values that would overflow now return a proper error. - Pay-to-anchor outputs — fixed. Transactions containing pay-to-anchor (P2A) outputs are now indexed correctly. Prior versions could return incorrect inscription and output data for these transactions.