Need a crash course on Bitcoin layers?
→ READ OUR FREE GUIDE
Need a crash course on Bitcoin layers?
→ READ OUR FREE GUIDE
Need a crash course on Bitcoin layers?
→ READ OUR FREE GUIDE
Need a crash course on Bitcoin layers?
→ READ OUR FREE GUIDE
Need a crash course on Bitcoin layers?
→ READ OUR FREE GUIDE

Release Roundup - September 2024

In September, we added contract monitoring to the Hiro Platform, so you can get notified anytime a specified function is called in your contract on mainnet. We also shipped Clarity 3 support in Clarinet simnet and pushed an update that enables epoch 3.0 to run more reliably in Clarinet devnet. Let’s get into it.

Type
Product update
Topic(s)
Hiro
Product
Published
October 8, 2024
Author(s)
Team
A pink browser that reads Release Roundup
Contents

Release roundups are organized into a few categories spanning the breadth of the developer experience. From core protocol contributions all the way to the Hiro Platform in the cloud, let’s take a look at what we shipped in September and share some of our priorities in October:

Release Roundup

Hiro Platform

  • We added a new contract monitoring feature to the Platform. Whether you’re monitoring for suspicious activity or simply want to understand contract usage, this feature enables you to get notified when specified functions are called in your contract on mainnet. 

DevTools

Clarinet

  • We released v2.9.x of Clarinet, which comes with several improvements. First, this release offers proper Clarity 3 support in simnet, with realistic block times for Stacks and burn blocks. 
  • Second, this release enables devnet to run epoch 3.0 more reliably, the number of signers in the devnet network is now configurable, and Postgres can be enabled/disabled independently from the Stacks API.

API Services

Token Metadata API

Blockchain

  • We supported the public ecosystem working group focused on the Nakamoto release. In September, we supported the first successful hardfork on the Nakamoto testnet, a major milestone as we enter the final stretch of testing. Now the working group is heads down on debugging and preparing to hardfork the primary testnet, the next step as we gear up for the mainnet hardfork. Learn more in the latest Nakamoto update.

Stacks Explorer

  • In September, we shipped several Nakamoto 3.0 updates, including more granular time stamps for Stacks blocks and more accurate data around previous Bitcoin blocks, and updating the Nakamoto Testnet UI in the Explorer to match the (successful!) epoch 3.0 hard fork.
  • Lastly, Stacks primary testnet now runs on a Bitcoin regtest environment, and we’ve updated the Stacks Explorer to link to that regtest environment instead of Bitcoin testnet, so you can more seamlessly test and harden your code in the Stacks primary testnet network.

Documentation

Looking Ahead to October

Here are our biggest priorities in the coming month:

  • Support Nakamoto launch: The mainnet hardfork is just around the corner, and the public ecosystem working group (which we are supporting) is heads down with final testing as we prepare for the hardfork of primary testnet. All Hiro tools already support Nakamoto, so you can get started with testing your application against Nakamoto today.
  • Launch guides and recipes in docs: We have lots of great content, but it’s not always easy to find what you’re looking for. In October, we plan to launch a new guides section with handy code snippets that makes it simpler to find the solutions you’re looking for.
  • Clarinet testing improvements: We have several workstreams in flight that we plan to ship in October that will improve the testing experience in Clarinet. First, we plan to add mock sBTC support, so developers wanting to build with sBTC can start doing so in Clarinet. Next, we plan to replace Bitcoin regtest with Clarinet devnet when it comes to API testing, which will make maintaining the API easier and allow us to ship faster. Last but not least, we plan to add mainnet data to simnet, which is useful when building on top of already deployed protocols and oracles.
  • Docs-first refactoring of Stacks.js: Stacks.js docs are confusing, and it’s not clear how to get from one object to another. We are refactoring the repo based on concept, so it’s easier to understand and build with all of the packages that Stacks.js offers.

As always, we will be shipping new features and upgrades outside of what’s listed here. Keep an eye out for new updates.

Learn More

For a full list of releases and improvements by product, please view the following links:

Product updates & dev resources straight to your inbox
Your Email is in an invalid format
Checkbox is required.
Thanks for
subscribing.
Oops! Something went wrong while submitting the form.
Copy link
Mailbox
Hiro news & product updates straight to your inbox
Only relevant communications. We promise we won’t spam.

Related stories