Skip to main content

January 2023 Product Changelog

Overview

As Hiro works to provide the most complete and up-to-date information on product releases and updates, the format of the Product Changelog has been altered slightly to make the content easier to read and understand. Instead of deep dives into each product, the focus has shifted to the developer experience and how these updates and changes improve the overall "developer journey."

The sections below describe the changes and updates made in January 2023.

Developer onboarding

The Hiro documentation team has been making significant progress in updating the technical documentation. The following updates/changes were added:

  • Overview of Stacks 2.1 Upgrades.
  • New Deployment Plans feature guide.
  • Additional references for Hiro Archive and Stacks Connect.
  • Hiro Contributors Guide that describes how to contribute to the technical documentation.

Empowering developers to do their best work

Hiro wants to empower developers to do their best work with the latest updates and enhancements to the Hiro product offerings. The Stacks 2.1 upgrade, and its support across different products, include:

  • API release candidate (v7.0.0) that supports Stacks 2.1, including a resolution for a known issue (genesis sync).

Note:

This API release candidate is currently in beta.

  • Stacks 2.1 now supports Clarinet 1.4.1, Hiro Explorer, and Stacks.js.
  • Subnets has been improved with an updated Subnets contract compatible with Clarity2.
  • A new trait for NFTs and FTs has been added on the subnet, which specifies a required name and signature for registration. This update ensures the Stacks Blockchain API always knows the correct name for the mint function.

Additional bitcoin support across Hiro products

New API endpoints are being developed to support Bitcoin-related queries and a Stacks.js client library to connect Bitcoin Core RPC. These improvements enable STX-to-BTC and BTC-to-STX to address conversions.

Additional resources

For more detailed information on these updates, please refer to the following resources: