Akash mainnet 2 (v0.10.1[1]) went live on March 8th, and since then we have seen a variety of applications deployed on Akash, and we will be sharing these groundbreaking use cases in the coming weeks . Since the launch of Mainnet 2, our deployments have increased 10x.

Since launching the world's first decentralized cloud platform, our team has focused on strengthening and improving the ecosystem's security and interoperability, vendor capabilities, and deployment user experience so developers can deploy faster.

The second update of Mainnet 2 is the latest version (v0.12.1[2]) which contains all the changes since the release of Mainnet 2[3].

We are building an ecosystem of partners to support production-grade applications: traditional cloud-native platforms, serverless, machine learning, and decentralized projects (DeFi, dApps, dao). We will democratize access to computing by giving developers unprecedented choice—not just in terms of where and how quickly they deploy, but at the price they want.

Our goal is to change the power dynamics and put developers in control (autonomy).

network usage

network usage

The most important KPI we monitor is Active Leases - Daily, Monthly (DAL/MAL).

This shows that there are new deployments every day. Note: Deployments can be active for more than 1 day. On day two of our launch, our DAL was 3 and now averages 50.

There are also some other KPIs that we are tracking. We will soon have a web stats page that will showcase KPIs related to web usage and growth.

Improve user experience for tenants

We've made some improvements to the command line interface (CLI) to make deployment faster and smoother for developers.

1165[5] - If no argument is provided, defaults to querying all provider properties. This makes it faster to vouch for the provider by signing all properties at once. 1153[6] - Error reporting improvements 1187[7] - Improved support for hardware wallets (like Ledger[8]) 1151[9] - Output and error messages flow to stdout/stderr 1149[10] - Improved use of option flags output information at the time. The default scope is option flags

Security function

We recently added a safety net for our tenants. If no inventory is sent to the provider within a certain period of time after the lease is created, the provider will close the lease. This safety net prevents tenants from paying for leases without any workloads running.

supplier pricing

Pricing Update [11]: In order to address the rising price of Akash Token (AKT), vendors will need to find a way to quote prices lower than the current minimum of 1 uAKT or 0.000001 AKT. Included in this update is the first step in implementing fractional uAKT pricing, which involves converting the pricing variable from an integer type to a decimal type.

Eventually, providers will be able to structure their pricing in such a way that they may earn 0.25 uAKT per block and be able to withdraw 1 uAKT every four blocks.

In the future, we will support partial uAKT.

Improve network performance

We stop broadcasting for now so that as more providers come online, invalid transactions don't impact network performance. Providers only bid on deployments that pass the audit and have the correct signature. This determines the order in which suppliers will be allowed to bid.

This reduces network congestion on the blockchain to improve performance and enables pre-filtering of acceptable matches. An additional filter has been added that prevents suppliers from bidding on groups whose calculated prices are too high (#1147[12]).

Automatic client certificate creation

Client Certificate Checking [13]: In order to establish a secure connection between a tenant and provider on Akash, an mTLS certificate must be created and stored on-chain. If the certificate is not created and the tenant tries to create a deployment using the deployment tool, the process will fail and the user's transaction fees will be wasted.

ecosystem

ecosystem

Ecosystem Security Improvements: Cosmos SDK[14] and Tendermint[15].

Improved reliability [16] - This improves the reliability of transactions written to the blockchain. Today, the transaction has a timeout of 10 seconds. Sometimes, it may take longer to get approval from enough validators. We ensure that this timeout does not cause errors. We now automatically retry to check that the transaction was recorded, enabling the deployment workflow.

WeChat external link

WeChat external link

[1] Version v0.10.1:https://github.com/ovrclk/akash/releases/tag/v0.10.1

[2] Version v0.12.1:https://github.com/ovrclk/akash/releases/tag/v0.12.1

[3] Variation:https://github.com/ovrclk/akash/compare/v0.10.1...v0.12.1

[4] Released:https://github.com/ovrclk/akash/releases

[5]1165:https://github.com/ovrclk/akash/pull/1165

[6]1153:https://github.com/ovrclk/akash/issues/1153

[7]1187:https://github.com/ovrclk/akash/issues/1187

[8]Ledger:https://shop.ledger.com/pages/hardware-wallets-comparison

[9]1151:https://github.com/ovrclk/akash/pull/1151

[10]1149:https://github.com/ovrclk/akash/pull/1149

[11]Pricing update:https://github.com/ovrclk/akash/pull/1173

[12]1147:https://github.com/ovrclk/akash/pull/1147

[13] Client certificate check:https://github.com/ovrclk/akash/pull/1169

[14]Cosmos SDK:https://github.com/ovrclk/akash/pull/1171

[15]Tendermint:https://github.com/ovrclk/akash/pull/1202

[16] Reliability improvement:https://github.com/ovrclk/akash/pull/1193