Astar Network - Development Updates (Read Only)

Astar Development Updates

Report # 1

Date: 2024/06/07


Welcome to Astar’s weekly development update! In this topic, we provide you with the latest advancements, enhancements, and fixes across our protocol, portal, and network. Our goal is to keep you informed about the ongoing improvements and ensure you have the best possible experience.

This week, there are no new runtime or network upgrades to announce, but we do have an exciting Portal update to share with the community.

Portal Updates

:gear: Features

  • The Portal Dashboard page was updated via #1289, which introduced inflation charts and redesigned the Data dashboard. The community can monitor real-time token inflation on this dashboard.
  • A Wallet Connect feature was incorporated into the wallet connection modal as detailed in #1278. Users can now connect their EVM wallets to the Astar portal using wallet connect.
  • Finally, a banner highlighting the start of the next dApp Staking voting period was added to the Portal in #1299.

:bug: Fixes

  • A bug in the XCM transfer interface concerning the switching between different XC20 tokens has been fixed. This fix can be found in #1294.

:arrows_counterclockwise: Refactors

  • A series of code refactors have been executed: the ledger migrate UIs for dApp staking V3 have been eliminated #1293, the dApp Staking v2 code has been scrapped in #1283, and the Yoki campaign banner has been removed in #1297.

Thank you for your continuous support and feedback!

The Astar Foundation Team


Great update, Astar team! Loving the new inflation charts—super handy for keeping an eye on token dynamics.

The Wallet Connect addition is a game-changer for ease of access.

Cheers for squashing that XCM transfer bug too! It’s these little fixes that make a big difference. Can’t wait to see what’s next.

Keep it up! :rocket::star2:

Thank you!

For the sake of transparency, I am glad to see the reports coming out every week.

1 Like

Hi G,

Thank you for the wonderful report :tada:
People who access the portal daily may have casually noticed that the portal has been updated. However, the general public does not often pick up detailed information from Github, so I think this kind of report is appreciated.

One thing I noticed while looking at this report is about the official documentation. I believe Astar Doc v3 is planned for the future. The documentation may not be updated very frequently, but I thought it would be good to have some sort of update announcement. I would like to help with that as well. If you have any suggestions for an appropriate reporting method, I would appreciate your comments.

By the way, until now, I personally checked Github at particular milestones or when I had time, and if there was an update to the official documentation, I announced it by posting on X or Discord/TG.

I am of the opinion that this thread should be closed to prevent the community from writing and losing the flow of weekly news. Just my opinion :sweat_smile:.

It’s very useful information. Thank you so much =)

Thank you for the update.
Having regular reports like this is very helpful for the community.

Astar Technical Development Updates

Report # 2

Date: 2024/06/14


Greetings, Astar Community!

Welcome to our weekly technical development update, where we bring you the latest advancements and improvements from our dedicated development teams.

This week, we’re excited to share updates across our protocol and portal. Our focus is to enhance user experience, improve protocol stability, and ensure the security of our ecosystem.

Stay tuned for detailed insights into the recent upgrades, fixes, and new features that will elevate your interaction with Astar.


After a recent Astar runtime upgrade a few weeks ago, which introduced an oracle feed for price, the tier thresholds in dApp Staking increased significantly more than expected. This issue stemmed from a flaw in the formula used to calculate the difference between the number of slots. The issue has been fixed in #1252.

As a consequence, some projects were incorrectly demoted to lower tiers, causing them to miss out on rewards they would have otherwise earned. To address this, a script has been developed to determine the accurate earnings for each project and prepare a call to reimburse the difference.

The code for this reimbursement script can be found on GitHub: AstarNetwork/dapp-staking-reimbursement-script.

The community could be particularly interested in the following resources:

Portal Updates

:gear: Features

The new dApp Staking Period is starting soon. Therefore, significant updates and improvements have been prepared and successfully implemented in #1302. These updates feature several enhancements to improve both the staking process and user experience. Specific changes include:

  • New Staking UI: A new staking UI has been developed to enhance user experience and simplify the staking process. It features clearer instructions, streamlined workflows, and intuitive design elements to help users navigate the staking features more effectively.
  • Dashboard Enhancements: Updated interface to provide more detailed insights and user-friendly navigation.
  • New Metrics: Additional metrics and analytics to help users make decisions.

A Ledger dApp Staking V3 Promotion Card has been introduced in #1304. This promotion card aims to encourage users to utilize the Ledger hardware wallet for staking, offering enhanced security and ease of use.

:bug: Fixes

Several key fixes have been made to enhance the stability and functionality of the portal:

  • Improved getDapp Method Error Handling: In #1307, error handling in the getDapp method has been enhanced, ensuring more robust and reliable operation. This fix resolves issues with error handling and allows developers to correctly register new dApps on the Portal again.
  • Fix Recent History Link for zkEVM: In #1311, a fix has been deployed to correct the transaction links in the transfer history for zkEVM, ensuring users can now access their transaction history without issues.
  • Disable XCM Transfer for Shiden: In #1313, XCM transfer functionality for Shiden was disabled. This was necessary due to Kusama’s recent runtime upgrade, which introduced significant changes, including a breaking change for transaction encoding with the CheckMetadataHash extension. Disabling XCM transfers prevents potential cross-chain issues.
    This is temporary until Kusama runtime compatibility with Shiden is tested and confirmed.

Thank you for your continuous support and active participation in our community!

The Astar Foundation Team