Release roundups are organized into primary themes which we use to track our progress and that better reflect the developer experience. Let’s take a closer look at what we shipped in June.
- Code and documentation for subnets are ready for mainnet! The subnets alpha implementation we shared earlier this year included key features such as Stacks 2.1 compatibility, improved throughput and block confirmation times, and multi-miner support. We also shared a demo app (GitHub repo here) to illustrate the full end-to-end experience for developers building and using a subnet. With this latest release, subnets are mainnet ready and are supported across Hiro products. Keep an eye out for updated subnets documentation coming later today.
- Last year, we shared that the costs of maintaining the Hiro-hosted Gaia hub have become prohibitive. As part of the migration of Hiro-hosted services, and to cut down this expense, we have made important headway on migrating the data in Hiro’s hosted Gaia hub to Google Cloud Platform, and we will also be archiving old, unused data. Learn more about this migration here.
Visibility, Verification, & Insights
- The Stacks Explorer added STX price to post conditions to increase visibility for transactions. Additionally, we added support for custom network IDs, unlocking the ability to view blocks and transactions for subnets. We have also updated the pox-2 contract with the pox-3 contract in the list of popular contracts and made pox-3 the default contract in the sandbox. We also had many contributions from the community this month (we love to see it!) including Raphael Pereira, Niaz Morshed, Ruchit Bhandari, Friedger Müffke, and Shamim Ahmed.
- We shipped a number of updates for the Ordinals Explorer. A JSON viewer has been added in the inscription previews for arbitrary JSON inscriptions, which even shows nested data structures. A protocol badge has also been added to the JSON preview for highlighting the intended protocol of the inscription (e.g. BRC-20, BRC-721, ORC-20, etc). The badge shows the text content for the .p or .protocol string of the JSON content. We have also simplified how JSON text is being shown. A custom visualization for BRC-20 events is shown instead of the default JSON content, though the JSON viewer is available for those inscriptions as well. We shipped support for Recursive inscriptions. Last but not least, the inscription page can show content in expanded fullscreen mode now.
- Clarinet saw a few updates in June. The team improved clarity test code coverage to be able to handle code branches. This is a big improvement for developers. Previously, if an expression was on one line but only partially covered, the line was reported as fully covered. This update makes Clarinet tests aware of code branches, which is especially useful for things like an “if statement” and will ensure that all branches on a line are covered to give a more precise coverage report.
- There were a few small bug fixes shipped this month for Stacks.js. The team added a missing none type for delegation status without a <code-rich-text>until_burn_ht<code-rich-text> allowing for an unlimited pooling delegation for stacking. Additionally, we removed post-conditions from STX transfer to keep transfers from getting stuck in the mempool.
- We launched API keys for developers who need access to higher rate limits for our API services—congrats to the teams that applied and received API keys. We’re excited to support you and help you scale your application. Learn more and apply for an API key here.
- For those running their own Stacks Blockchain API, an update adds a new environment variable that can be used to specify the network (mainnet or testnet) for a given <code-rich-text>chain_id<code-rich-text>. This can be used to configure one or multiple values for networks such as subnets.
- The Ordinals API team added support for cursed inscriptions this month including adding <code-rich-text>/sats/:ordinal/inscriptions<code-rich-text> endpoint to list all curse inscriptions for a single sat, support for a new chainhook event <code-rich-text>cursed_inscription_reveal<code-rich-text>, and save and expose <code-rich-text>curse_type<code-rich-text> on all endpoints. We shipped an automatic predicate registration fix to the Ordinals API that solves an issue developers were experiencing where the API would send a predicate to chainhooks and it would trigger a 422 error. Lastly, the team created a new endpoint <code-rich-text>/metadata/ft<code-rich-text> which lists all fungible tokens with valid metadata, results include basic metadata not detailed and allow filtering and ordering by name or symbol.
- We added a new endpoint to the Token Metadata API that lists all fungible tokens and their metadata and allows users to fetch that data in bulk.
Hosted Developer Experience
- The Hiro Platform team has been hard at work this month adding a powerful new feature in deployment plans. Deployment plans are reproducible deployment steps that publish one or more contracts as well as a collection of on-chain transactions to a network. These plans minimize the complexity of smart contract dependencies and interactions in your project deployments. To learn more, read our announcement blog post.
For a full list of releases and improvements by product, please view the following links: