Contents
Stacks API
- This month, the API team was focused on the Stacks 2.1 network upgrade, including work on:
- The team introduced the new property <code-rich-text>miner_address<code-rich-text> to the <code-rich-text>miner_rewards<code-rich-text> event payload to indicate the principal that mined the block. This also stores that value so that later queries are able to use it to find things like unique miners. A key Stacks 2.1 feature is the option to choose alternative recipients for rewards. This change enables the ability to track the <code-rich-text>miner_rewards<code-rich-text> event for alternative recipients via <code-rich-text>miner_address field<code-rich-text>, which encodes the miner address. This replaces the "recipient” field with the generalized recipient, which is currently hard-coded to the miner.
- The team implemented parsing for the new PoX-2 print events. This update adds account balance locked state validations tests to ensure API and stacks-node have matching balance and locked state after each of the various Stacking operations and through each of the PoX transition periods.
- Finally, we added aggregating query limit logic this month. This change sets query limits based on the resource type being queried, which mostly determines which tables are queried. Categorizing queries in this way meant modifying some of the existing query limits for some endpoints. This will help reduce and avoid out of memory (OOM) errors in the future.
- Visit the GitHub repo for an overview of PRs merged and issues closed in the past 30 days. Current stable release: v6.2.1 and the latest pre-release: v7.0.0-stacks-2.1.1
Blockchain
- This month, the Hiro team helped reach a big ecosystem milestone with code complete on the Stacks 2.1 network upgrade. For more details regarding the Stacks 2.1 update, check out Developer’s Guide to Stacks 2.1, and a blog post on how the upgrade will impact stacking.
Clarinet
- In November, the team made several updates to chainhooks, a feature that lets developers add IFTTT logic across both the Bitcoin and Stacks blockchains to their applications. The first chainhook update modifies the developer experience by adding a new mode: <code-rich-text>$ chainhook-node replay –testnet<code-rich-text>. This enables developers to replay devnet / testnet / mainnet dumps. The team is also working on improving the <code-rich-text>chainhookd-node<code-rich-text> experience by adding presets. Developers can now use commands like: <code-rich-text>$ chainhook-node start –<code-rich-text> and identify devnet, testnet, or mainnet and have their local environments set up in just a few minutes. Check out instructions for how to use chainhooks in this feature guide.
- To support the Stacks 2.1 upgrade, the Clarinet team has improved error management in event observer, added support for new event types and clarity version in deployment plans, among other improvements.
- Visit the GitHub repo for an overview of PRs merged and issues closed in the past 30 days. Current release: Clarinet v1.1.0.
Stacks.js
- Last month, the Stacks.js team shipped a few updates and features to support Stacks 2.1. The most notable added new stacking methods, support for new BTC address formats, helpers for the PoX transition, and more.
- Visit the GitHub repo for an overview of PRs merged and issues closed in the past 30 days. Current release: v6.0.2.
Hiro Wallet
- Last month, the Hiro Wallet team shipped an update to the fee estimate query that is used to suggest fee rates to a user. The team also added the option to easily transfer assets within the same wallet. Lastly, they added support for BNS recipients allowing users to add a .btc name in the recipient field and send to the associated address.
Stacks Explorer
- To support Stacks 2.1, we now display the Clarity version for smart contract transactions, alt recipient for coinbase transactions, and memo for STX transfer events.
- The team added the ability to see the historical STX price on transactions in the Explorer. Please note that the price listed will be on the day of the transaction, not the exact moment of the transaction.
- There is now tooltip support when a user hovers over the icons in the Sandbox, improving navigation.
- Lastly, the team has added a feature that allows users to easily copy and paste the exact local time of any transaction, instead of having to manually write it drown, by clicking on the tooltip. This improvement came directly from user feedback and was implemented in order to simplify the process of collecting a transaction’s time and date.
- Visit the GitHub repo for an overview of PRs merged and issues closed in the past 30 days. Current release: v1.61.0
That’s it for November. Have questions? Chat with us on Discord.
.jpg)
