Warp SonAR update and Key-Value Storage

0 173

Warp’s SonAR Explorer is a great tool to view SmartWeave contracts as well as any transaction on the Arweave blockchain. The explorer has received several updates and new features that make it faster and more efficient than ever. Warp also recently introduced us with Key-Value Storage, a new feature that helps efficiently store and access the state of smart contracts with large numbers of entries.

Let’s have a closer look at all the new features of SonAR, as well as what Key-Value Storage is!

Warp’s revamped SonAR Explorer

First and foremost, the performance of SonAR has been significantly improved. The Warp infrastructure has undergone several performance optimisations, allowing for a faster and smoother explorer experience. This update is particularly important as the Arweave network recently hit a major milestone of 1 million SmartWeave contracts deployed.

Next, SonAR’s dashboard has been updated to include more information on deployed contracts and interactions. The new User Interface (UI) design is smooth and intuitive, making it easy for users to navigate. Furthermore, users can now sign up with their wallet and easily keep track of their token balances with SonAR. This feature is powered by the Warp Aggregate Node.

Taking a closer look, users will notice that there is now a contract-specific tab that allows them to view contract details such as transaction count, code, and state evaluation. This new feature makes it easier to analyse the details of a specific contract, something that developers (and not only) will find exceptionally useful.

Warp has also introduced state information to the SonAR explorer, that allows users to download a JSON file containing the information from the initial and evaluated state tabs. The state evaluation tab includes a D.R.E link containing raw information from the evaluator node. 

If you don’t already know, D.R.E. stands for Delegated Resolution Environment, and it is a crucial part of Warp Contracts which utilises delegated nodes to evaluate the state of a smart contract and interact with it. It was recently introduced by Warp to help reduce the computational burden on individual users’ devices and ensure that the state is accurately and efficiently updated. 

(Warp D.R.E. brings a new level of efficiency, safety, and transparency to the evaluation and interaction of high-interaction and high-risk contracts on the Warp platform. Read more in depth about it in our recent article covering it here.)

The evaluation logs tab is another new feature of SonAR that allows users to view past evaluations. 

And finally, SonAR has introduced comprehensive error handling. Users can now view error-type descriptions in the transaction list display and in the specific transaction view. This feature makes it easier to troubleshoot and identify potential errors.

Warp recently also introduced what is known as Key-Value Storage.

Warp Key-Value Storage

Warp has introduced a new experimental feature for their Warp Contracts called Key-Value (KV) Storage. The feature was created in response to the challenge of efficiently storing and accessing the state of smart contracts with large numbers of entries. The traditional way of storing the state requires the entire JSON state to be passed to the contract and cached every time a single entry is changed. This results in large amounts of storage and processing time needed for even the smallest changes. The new Key-Value Storage feature offers a solution by allowing only the required parts of the state to be stored and retrieved as needed. This is done via a storage method that is backed up by default by the LevelDB. While this is still an experimental feature, it has already been used in Warp’s own contracts, and could offer significant benefits in terms of performance and storage efficiency for smart contract developers.

KV storage does not currently allow for inner contract calls. This feature will be added in the near future.

Join our

Telegram / Discord / Twitter

Leave A Reply

Your email address will not be published.