Contents
Let’s take a look at what we shipped in May across all of Hiro’s devtools, and share some of our priorities in June.
DevTools
Platform
- We shipped the API Usage Dashboard to bring more certainty to every Hiro developer account. No more guessing, no more spreadsheets. Open the Platform console, glance at the chart, and know whether today’s traffic spike is healthy growth or a sign you should upgrade before the next release goes live.
Explorer
- We shipped the first phase of our newly redesigned Stacks Explorer, starting with a faster, cleaner homepage and a transactions page built for the next generation of the Stacks ecosystem. This update brings a sleek new interface, streamlined navigation, and noticeable performance improvements. It also lays the groundwork for a fully modernized Explorer experience that we’ll continue expanding in the coming weeks.
Clarinet
- In addition to Clarity support in VS code, we also have released built in support for Clarity in Zed and Helix. This adds Clarity syntax highlighting and LSP support to the Zed and Helix code editors bringing the Clarity language to a new inflection point in developer adoption. Providing devs with Clarity support in different code editors will not only expand Clarity usage, but we're meeting developers where they are most comfortable in writing code.
- We also released the latest Clarinet v3.1.0, which fixes native LSP support for non-VSCode editors. Now if you want to build a plugin for your favorite editor to add Clarity support, you can!
Stacks.js
- Fixed <code-rich-text>@stacks/transactions<code-rich-text> methods <code-rich-text>Cl.parse<code-rich-text> and <code-rich-text>Cl.stringify<code-rich-text> to match <code-rich-text>JSON.parse<code-rich-text> and <code-rich-text>JSON.stringify<code-rich-text> in escaping characters and string handling. Previously, there were edge cases where certain values weren't serialized correctly: e.g. a string with a double quote inside it, would not produce valid stringified Clarity syntax. This is likely a rare problem in production, but could happen, so we took care of that.
- Added a new argument to the contract call CLI feature. This means that the CLI now allows passing Clarity function arguments directly as a comma-separated string. Now we can pass Clarity arguments directly: e.g. <code-rich-text>stx … … "u123, (list 1 2 3)"<code-rich-text> where the last argument is a comma separated string of the Clarity arguments for the function call.
Infrastructure Services
Stacks Blockchain API
- Added a new endpoint under <code-rich-text>/extended/v2/block-tenures/:height/blocks<code-rich-text> so users can get blocks only for a specific tenure. This endpoint builds over the code for the v2 blocks endpoint so it also inherits cursor pagination.
- Store and expose <code-rich-text>vm_error<code-rich-text> for failed transactions. This allows API consumers to read ClarityVM errors returned by Stacks miners when confirming failed transactions. For example, you’d be able to determine which post-condition failed in a transaction.
Looking Ahead to June
Here are some of the big things we’re working on in June:
- Production readiness for Store and Push integration with the Stacks Blockchain API: This initiative represents a significant update for the Stacks Blockchain API. Ensuring the API’s readiness for Store and Push integration is crucial to guaranteeing resilience and bug-free operation of the API before deployment in Production.
- Stripe Integration: We launched our paid tier system as fast as we could to get you access, but we had to follow up with a better way for you to manage your subscriptions, accounts, and payment information. Soon, no more invoices! You will be able to upgrade, downgrade, and autopay directly through a secure Stripe portal on the Platform. Instant self service for all account management needs.
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:
