Greg Osuri

Confidential Compute Comes to Akash

Tue, 28 Jul 2026 00:00:00 +0000

Decentralized compute has always faced an underlying question that requires a direct, transparent answer rather than a reassuring platitude: what prevents a completely unknown provider from accessing your data when you rent their GPU?

Previously, the solution relied on provider reputation, security audits, and the assumption that operators lacked the time or incentive to inspect individual containers. While acceptable for minor tasks like hosting a game server, this baseline falls short when protecting sensitive medical records, proprietary algorithmic trading models, or core company intellectual property embedded in model weights.

Akash is introducing a definitive solution today with the launch of confidential compute across the network. Workloads can now run inside hardware-enforced trusted execution environments (TEEs). In this setup, memory encryption is managed directly by the CPU, rendering the data inaccessible to the host operating system, the hypervisor, and anyone with physical access to the infrastructure.

The most notable aspect of this feature is the minimal effort required to implement it.

One Line

Here is the entire SDL change:

services:
  my-workload:
    image: my-image:latest
    params:
      tee: cpu-gpu

Integrating confidential computing requires no SDKs, rebuilt container images, separate orchestrators, or new deployment types. You simply utilize params.tee, which configures cpu for CPU-isolated workloads or cpu-gpu when an enclave-protected GPU is necessary.

The marketplace handles matching seamlessly behind the scenes. The SDL builder translates the designated tee value into a placement requirement, ensuring only providers verifying confidential compute capability bid on your order. Rather than manually selecting a specific TEE vendor, the hardware infrastructure dictates whether you receive Intel TDX or AMD SEV-SNP, while provider software automatically provisions the appropriate runtime class.

Once a lease is finalized, your container runs isolated within a Kata Containers micro-VM, utilizing a dedicated kernel and encrypted memory instead of sharing host kernel resources. If your configuration requests a GPU, pass-through is managed via VFIO into NVIDIA Confidential Computing mode, safeguarding all data moving across the PCIe bus with AES-GCM-256 encryption.

Developed publicly under AEP-83 and inheriting foundations from AEP-65 and AEP-29, this architecture maintains a deliberately constrained SDL surface. By prioritizing the reuse of existing frameworks and minimizing new additions, confidential computing remains strictly opt-in, preserving current deployments entirely without disruption.

A private LLM in one deployment

To demonstrate how this abstraction works in practice without overstating its simplicity, a complete, functional example called ollama-tee has been added to the awesome-akash repository.

It runs Ollama with Llama 3.2 3B on a GPU, inside a TEE:

---
version: "2.0"

services:
  ollama:
    image: ollama/ollama:latest
    expose:
      - port: 11434
        as: 11434
        to:
          - global: true
    command:
      - bash
      - "-lc"
    args:
      - |
        /bin/ollama serve &
        until /bin/ollama ps >/dev/null 2>&1; do sleep 1; done
        /bin/ollama pull llama3.2:3b
        wait
    params:
      tee: cpu-gpu

profiles:
  compute:
    ollama:
      resources:
        cpu:
          units: 4
        memory:
          size: 16Gi
        storage:
          - size: 20Gi
        gpu:
          units: 1
          attributes:
            vendor:
              nvidia:
  placement:
    dcloud:
      pricing:
        ollama:
          denom: uact
          amount: 100000
      signedBy:
        anyOf:
          - akash1365yvmc4s7awdyj3n2sav7xfx76adc6dnmlx63

deployment:
  ollama:
    dcloud:
      profile: ollama
      count: 1

Note the image: it’s the stock ollama/ollama:latest from Docker Hub. Nothing in it knows or cares that it’s running in an enclave.

Deploy it, wait for the model to pull, and query it the way you’d query any Ollama instance:

curl http://<your-endpoint>/api/generate -d '{
  "model": "llama3.2:3b",
  "prompt": "Which continent is the USA in?",
  "stream": false
}'

{
  "model": "llama3.2:3b",
  "created_at": "2026-07-27T17:14:48.038986841Z",
  "response": "The United States of America (USA) is located on the continent of North America."
}

An ordinary API response, but with one crucial difference: the weights, prompt, and completion were all handled within memory that remains completely hidden from the machine’s operator.

This encapsulates the entire value proposition of confidential computing, explaining why the SDL modifications are restricted to a single line. Most people will simply avoid privacy measures if they demand a complete application rewrite.

What this protects, and what it doesn’t

Let’s be exact about our security guarantees.

Hardware Protection Capabilities: The CPU’s memory encryption engine encrypts guest memory, keeping it hidden from the host OS, the hypervisor, or root operators on the machine. It also encrypts CPU-to-GPU communication via the PCIe bus, turns off GPU performance counters to eliminate side channels, and runs every workload with a dedicated kernel inside its own micro-VM.

Limitations of TEE Configuration Alone: Simply requesting a TEE does not confirm that you are operating within a genuine, uncompromised environment, as isolation is distinct from proof. Verification requires remote attestation, which gathers signed data from within the VM (such as an SEV-SNP report or TDX quote, alongside GPU data from NVIDIA’s NVTrust) to validate it against baseline measurements and generate a token for relying parties. In setups combining CPU and GPU TEEs, this becomes composite attestation, where the CPU TEE serves as the primary trust anchor for the GPU.

While the ollama-tee demonstration highlights isolation and placement, it does not perform attestation. Because attestation is mandatory for regulated applications, we want to be straightforward instead of overstating TEE capabilities. We are currently developing tooling to integrate attestation as a smooth, integrated component of the deployment lifecycle.

We should also note two technical details regarding Hopper GPUs: CPU-to-GPU data transfers within a TEE are restricted to roughly 4 GB/s due to a software bounce buffer, which slows down model loading rather than active inference. This bottleneck is resolved in Blackwell through PCIe IDE and TDISP. Additionally, NVLink communication between Hopper GPUs lacks encryption, which is important when sharding models, but Blackwell introduces NVLink encryption to fix this.

Why this matters now

Historically, the exact workloads that stood to benefit the most from decentralized infrastructure were completely blocked from adopting it. For example, a medical network reviewing an AI diagnostics system cannot expose confidential health records to an unaudited machine. Similarly, engineering groups managing high-value proprietary model weights cannot risk deploying them to an unidentified operator. Furthermore, any autonomous agent managing client PII must fully comply with the privacy mandates bound to that data.

The core obstacle for these operations has never been about infrastructure costs or hardware constraints, especially since Akash has continuously delivered compute resources at a fraction of traditional hyperscaler pricing. Instead, the real limitation stemmed from compliance; a policy requiring teams to simply “trust the operator” cannot serve as a verifiable security control within formal regulatory documentation.

By introducing hardware-enforced confidentiality, reliance on operational trust is substituted with a far more narrow and verifiable premise: that the physical silicon executes precisely as specified by the manufacturer. This shift fundamentally alters the security dynamic, finally making decentralized compute accessible for sensitive, enterprise-grade workloads that require absolute data privacy.

Get started

Deploy the example: ollama-tee in awesome-akash
Read the spec: AEP-83
Deploy from the browser: Akash Console
Bring questions: Akash Discord

Because confidential compute remains opt-in and provider capacity is in its early stages, you might encounter initial challenges—such as receiving no bids, facing SDL validation errors, or discovering attestation questions left unanswered by the documentation. If you run into these obstacles, please reach out to us on Discord. The specification is completely open, the core implementation uses the Apache 2.0 license, and user feedback at this critical phase directly influences the final design.

Testimony on AI, energy, and distributed compute

Wed, 21 May 2025 00:00:00 +0000

I’m Greg Osuri, Founder and CEO of Overclock Labs, the team behind the Akash Network. I’m an open-source developer and cloud infrastructure engineer.

Akash is a decentralized cloud platform used by hundreds of thousands of developers. By tapping into idle servers worldwide, it delivers compute power at a fraction of the cost of traditional cloud providers.

Our open network—supported by hundreds of global contributors—empowers developers to build and deploy AI and other applications without relying on Big Tech.

Artificial Intelligence isn’t just a breakthrough—it’s becoming the substrate of civilization.

Like electricity in the 20th century and the internet in the 21st, AI is the next foundational layer. It’s not a feature—it’s the foundation. From curing cancer to defending the homeland, AI will enhance everything we do.

There is no domain that AI won’t transform.

Yet we’re only at the starting line. Superintelligence is coming—an invention that could define the next 500 years. We will either master it—or be mastered by it.

America is leading—for now. But we’re in a sprint, and China is gaining ground. Their DeepSeek R1 model, trained for just $5 million, delivered results that rival OpenAI’s. They’re scaling faster, investing more, and moving with purpose.

We cannot afford to fall behind. The future of AI must be built on freedom, transparency, and trust—not surveillance and control. That is America’s edge. And we must defend it.

To lead in AI, we must confront the energy crisis it’s creating.

According to the Department of Energy, U.S. data centers consumed 176 terawatt-hours of electricity in 2023—4.4% of the nation’s total. By 2028, that number could triple. At the high end, AI infrastructure could consume 12% of all U.S. electricity—an enormous burden on our grid.

Here’s the problem: our national power generation isn’t doubling every two years, but the energy needed to train and run AI is.

AI demand is on an exponential curve. Our response can’t be linear.

Gartner warns that by 2026, energy demands may exceed utility capacity, leaving 40% of AI data centers without sufficient power.

Meanwhile, China is racing ahead—outbuilding us, outpowering us, and scaling fast. DeepSeek R1 is a glimpse of how quickly the lead can slip.

Without bold action, this energy bottleneck won’t just slow AI innovation—it could cost us global leadership.

To maintain momentum, we must use every tool available—including fossil fuels as a temporary bridge. But that’s just a stopgap, not a long-term plan.

Fortunately, we don’t need to wait for massive new data centers or power plants. Leading AI labs have shown that training doesn’t need to happen in hyperscale facilities. It can be distributed across smaller compute clusters.

That opens the door to a decentralized grid, powered by solar, renewables, and local energy sources from homes, campuses, and communities.

This model isn’t just more efficient—it’s more secure. Decentralization builds resilience. No single point of failure. No single target. That matters, especially in a world of cyber threats and geopolitical risk.

We need distributed infrastructure to meet AI’s energy demands today, while we scale sustainable energy for tomorrow.

Yes, we must ease barriers for advanced nuclear to ensure long-term energy stability. But decentralization is how we scale now.

That’s exactly what Akash Network enables: a decentralized AI cloud—open, efficient, and built for the future.

AI will shape the future of every industry, every economy, and every nation. The question is: who will shape the infrastructure behind it?

We cannot rely solely on Big Tech or centralized power. We must build a distributed, resilient, and inclusive AI infrastructure—rooted in American ingenuity, powered by clean energy, and open to all.

Congress has a chance to lead:

Incentivize decentralized cloud infrastructure
Fund federal R&D for distributed computing
Open federal lands to power edge innovation
Accelerate clean, flexible energy solutions

Let’s ensure America doesn’t just participate in the AI revolution—we lead it, shape it, and share it.

Let’s unleash AI’s full promise—not just through code, but through the infrastructure that defines our future.

Thank you. I look forward to your questions.

Akash Roadmap 2025

Tue, 14 Jan 2025 00:00:00 +0000

Introducing Akash’s Roadmap for 2025 and Beyond as the Network Expands to Agent-Centric Infrastructure

Cloud computing has become an integral part of modern digital infrastructure, reshaping how organizations, governments, and individuals create, store, and consume information.

Almost every digital service we interact with for profit or pleasure is hosted by one of four hyperscaler companies.

As we naively traded control for comfort, these hyperscalers experienced exponential growth, raking in record profits and amassing immense power, which is to be expected from corporations that act in the self-interest of their shareholders. These companies control who gets access, how much they pay, and what content they can distribute.

Such power leads to oligopolization of the industry, stifling open-source innovators and silencing political dissent. They impose an invisible tax that all of us have to pay without having a say in how it is spent.

Adam and I founded Overclock Labs, the organization that gave birth to Akash, in 2015 when it became obvious that so much power should not be held by the few — cloud computing infrastructure needed to be democratized.

We believe access to computing infrastructure should be a public good.

Inspired by Bitcoin’s decentralization of money, we chose to decentralize the cloud, to ensure the critical fabric of modern digital society is a public utility, like the air we breathe and the water we drink.

We built Akash so humanity retains its right to compute, freedom from censorship, and liberty of free thought.

Building a decentralized network means that we, the developers, have no control over the network once it’s launched. Updating the software once it’s deployed becomes extremely time-consuming as we need consensus from individuals that actually run the nodes, which is not necessarily its builders. Building in the open means being extremely transparent, which leaves little room for mistakes.

We chose not to take shortcuts and to do it the right way from the get-go. We chose to be open-source and decentralized from the start because we believe doing it any other way will create a culture of complacency where companies that launched with closed-source codebases and complete control over their network rarely open-source their code or relinquish control. A community’s culture becomes nearly impossible to change once established, hence it was critical for us to start with an open and permissionless culture.

We launched Akash Mainnet 1 in 2020 to establish a base level foundational security to launch the Platform (Mainnet 2) in March of 2021. This was the first time in history that cloud computing could be accessible with full self custody. In 2022, we introduced several other firsts like high-performance storage and IP discovery. In 2023, we introduced accelerated computing (GPUs) to enable AI use cases, marking another first in history where GPUs can be accessible on a non-custodial cloud. In 2024, we optimized for user experience that resulted in over 10x growth in on-chain revenue. We’re now excited to share the next phase of Akash as we transition from a resource network to a services network, realizing the vision of the supercloud.

As we designed our roadmap, we laid out key priorities:

Improve client experience to eliminate the need for support.
Increase adoption by eliminating barriers and adding capabilities.
Increase AKT demand to strengthen Akash economy.
Push boundaries of cloud technologies and enhance open source experience.

Some highlights from the roadmap:

Sovereign AI Agents: Akash is the only general-purpose decentralized network that allows AI Agents to operate with sovereignty at scale. With confidentiality coming this year, Akash is well-positioned to be the premier decentralized hosting network for AI agents.

With generative AI, we see AI being helpful in making us smarter. With AI agents, AI will make us much faster. There is little doubt that AI agents are the future of applications.

On-chain Provider Incentives: In 2024, we observed that demand increased fairly linearly as supply increased in the several provider incentive pilots we executed. In 2025, we bring incentives on-chain to unlock network effects-driven supply growth.

Sovereign Services: The Managed Service Market (MSM) strengthens the Akash ecosystem by unlocking a new wave of service providers and strengthens AKT. Services enable creators of software to generate meaningful income while sustaining and improving their work and keeping software open. Today, the value capture is at a massive imbalance where Cloud Service Providers (CSPs) are the biggest benefactors. MSM balances this asymmetry.

Improved Developer Experience: Increasing distribution is a key aspect for gaining adoption and core improvements in developer experience when integrating with Akash, remove friction points for developers to interate Akash into their core offerings

Akash at Home: We believe personal AI will run on home servers for privacy and security. Akash at Home aims to use spare computing power in homes to host AI workloads and bring Akash to home users.

Access Akash’s roadmap at akash.network/roadmap

Public Cloud Is a Public Utility

Thu, 12 Jan 2023 00:00:00 +0000

The Akash Network was created approximately two years ago to decentralize cloud infrastructure and put it in the hands of the people. It’s now run by a network of globally distributed node operators who secure the Akash blockchain and provide cloud-grade server space for tenant applications.

The source code developed by Overclock Labs has been open since inception, and now we are taking the next step of opening up the process that produces it. Removing single failure points from one company makes Akash Network more resilient to institutional attack vectors.

The development of the Akash Network involves multiple steps that are managed by Overclock Labs. The process begins by determining user needs and creating technical specifications based on them. Once the specification is made, it is implemented by a developer and then released to the public. Afterward, validators vote to accept the new code and upgrade their systems with the latest version of Akash Node.

The process has functioned well so far, and Overclock achieved great success with shipping, two major mainnet upgrades that brought us Persistent Storage, and IP Leasing.

But as the saying goes, “If you want to go faster, go alone; if you want to go far, go together.” We believe that by opening up the process, we can achieve our goal of radical decentralization faster and further.

If you want to go faster, go alone; if you want to go far, go together.

Akash should utilize the strong developer community and open organization tools available to reach its potential. The Akash community is much larger than Overclock’s employee pool. By allowing people to participate voluntarily, we can leverage their skills and values to help achieve the goal of executing our product strategy.

We propose a set of community groups inspired by successful projects like Kubernetes. These groups are open to anyone who wants to join, except for Committees that already have designated members.

Special Interest Groups (SIGs)

SIGs are long-term groups that will be present for the project’s duration. SIGs are dedicated teams working on specific parts of the Akash Network. They help to define and create products and features, as well as provide ongoing support for them.

Working Groups (WGs)

Working Groups (WGs) are community groups that collaborate on large-scale initiatives that involve multiple Special Interest Groups (SIGs). They do not develop or create projects but rather define major projects with aspects across the whole system, potentially involving external partners and relevant parties. A Working Group may operate for a short time rather than being a permanent group like SIGs.

User Groups (UGs)

UGs help people communicate openly, find topics that can become WGs or SIGs, discuss broad use cases (like ML/AI or Big Data), and discuss ideas we don’t prioritize for product development according to the current strategy.

Committees

A committee is a designated group of people who discuss sensitive topics. They are expected to be transparent in their work, but there may be some circumstances where private conversations are necessary. Some examples of committees include the Steering Committee and special committees such as ‘security’ or ‘code of conduct.’

Steering Committee

Regular meetings help the Akash Network community operate more efficiently. If needed, it also resolves conflicts. The Steering Committee is a particular SIG that evaluates projects, prioritizes, and assigns them to the proper SIG or WG.

Whats Next?

New Website ✨

We’re super excited to launch and open-source the completely rebuilt Akash website. The source code and all its content are available on GitHub for anyone to contribute. Browse through and suggest a feature or report a bug.

The new website allows people to quickly post content that was created by the community. It has a modern design which makes it easier to navigate and read.

New GitHub Home 🏡

We also migrated key repositories from ovrclk GitHub organization to akash-network organization. The new organization will be the home of all Akash Network-related repositories. The migration is still in progress, and we will update the list as we move more repositories.

Kick Off 🚀

Our new working model is already underway, and we have already had several successful WG meetings with the Akash Community and ecosystem partners.

The first Steering Committee meeting is scheduled for January 26th, 2023. In the meantime, browse Akash’s GitHub to learn about the various SIGs and WGs that are currently active — and head over to our Discord to join the conversation.

How can you contribute?

If you are a …

Technical Operator (non-programmer) that never used Akash: Review the documentation for Akash and attempt to deploy a Tetris game. If you have any ideas for changes or improvements to the documentation, please create an issue in sig-documentation.
Frontend (node, JS) developer that never used Akash: Review the documentation and deploy an application. Check the code base of Akash Console or Cloudmos Deploy, set up a local environment. Look at open issues for either project, select something (like a minor bug fix) that interests you, and leave a comment or submit a pull request for review.
Backend (Go) developer that never used Akash: Review the documentation and deploy an application on Akash using the Command Line Interface. Review the code bases for Akash CLI and Provider Services, and set up a local development environment. Additionally, review any open issues for either code base, comment on potential solutions to any problems, and submit a Pull Request for review.
Technical developer building on Akash: Consider joining one of our SIGs, or WGs, and writing a spec for one of the projects in the list or suggesting a new project to add to the list of tasks.

If you’re unsure and want to chat, reach out to us on Discord or Telegram. We’re happy to help you get started.

Annoucment Video

Watch me discuss this annoucment live on Cryptocito

Watch the announcement video.

Q4 Update on Akash Roadmap 2022

Mon, 20 Dec 2021 00:00:00 +0000

At the beginning of this quarter, the Akash core team published an ambitious roadmap, the Akash Roadmap 2022. Now we are at the end of our first quarter, here’s is an update on how we are progressing through the roadmap.

In summary, WAGMI.

Persistent Storage

Akash now supports persistence storage (the most requested feature) in the Testnet. This feature requires a chain upgrade for Mainnet, which is currently planned for Q1 2022.

Persistence storage allows workloads to persist data between restarts, ideal for data-intensive workloads such as blockchain nodes, Solana and Ethereum.

Status: Testnet

Since: 0.15.0 (rc4)

Related Pull Request(s):

Network Usage Dashboard

The first version of the Network usage dashboard is complete and deployed in production, naturally running on Akash, and available at stats.akash.network.

This version is inspired by Akashlytics; the future version will include several provider-related metrics.

The source code is now being cleaned up and open-sourced momentarily with an announcement planned for early next year.

Status: Live (stats.akash.network)

Hostname Migration

Akash now supports Hostname Migration in the upcoming Testnet. Usage documentation is available here. This feature requires a chain upgrade for Mainnet, which is currently planned for Q1 2022.

Deployment of an updated workload encounters a challenge when the DNS hostname remains active on the existing deployment. An example scenario is presented to ensure understanding of the challenge - followed by a review of the mechanism introduced in this release to migrate a hostname to the new deployment.

Status: Testnet

Since: 0.14.0

Related Pull Request(s):

feat(provider): rework hostname management to use a kube operator #1365

TTY (Shell) Access

TTY Access is implemented in the Testnet. This feature requires a chain upgrade for Mainnet, which is currently planned for Q1 2022.

TTY Access allows developers to access the shell of the container that the application is running in. This provides the ability to easily debug. Currently, debugging and running applications on Akash is difficult, as users can not run arbitrary commands on a running container. TTY access unblocks this and allows users to run any command.

Status: Testnet

Since: 0.14.0

Related Pull Request(s):

Add provider lease-shell command #1293

Inflation Decay Curve

Inflation Decay Curve is implemented in the Testnet. This feature requires a chain upgrade for Mainnet, which is currently planned for Q1 2022.

On-chain inflation decay curve ensures inflation decay occurs every block period without needing governance proposals.

Status: Testnet

Since: 0.15.0 (rc4)

Related Pull Request(s):

feat(inflation): Implement Akash custom inflation function according to the whitepaper. #1352

Airdrop Faucet

The first version of the Faucet is complete and deployed in production, available at drip.akash.network. This version emits 20 Akash Token (AKT) and has a minor delay (for manual verification) to prevent fraud. The future versions will employ automatic algorithms that will transmit tokens in real-time.

The source code is now being cleaned up and open-sourced momentarily. Announcement planned for January.

Status: Live (drip.akash.network)

Provider Onboarding Framework

Currently, there is an enormous and intricate set of steps that a provider needs to execute in order to provide compute on the Akash Network. This leads to confusion and instability of the provider. A new provider onboarding framework will increase adoption, optimize the onboarding process, and eliminate potential issues with the provider in the future.

A provider onboarding framework is to ease new providers selling compute on Akash, planned to be released in Q4 of 2021 is now delayed.

The automation for bootstrapping a node is code-complete and tested internally for Testnet and Devnets; the documentation is, however, still pending, so we’re moving this deliverable to next quarter. The helm charts for installing various components are available at akash-network/helm-charts.

Status: Incomplete

Related Repositories:

akash-network/helm-charts

Developer Hub

The developer hub will be a one-stop shop for all developer-related content such as guides, tutorials, documentation, architecture, and discussions.

Status: Not Started

Estimate (Updated): Q1 2022

ASN (IP Addresses) Market

This Feature Dedicated IP addresses (and ports) for workloads and the marketplace to source them.

Workloads hosted on Akash share IP addresses because there is no facility to assign individual IP addresses to applications. This presents limitations with routing. Hostname name-based routing has to rely on HTTP or SSL. To accommodate for TCP / UDP, Akash assigns random ports and there is no way to multiplex TCP services over a single port. This also slows down fault recovery as DNS services require record updates which are slow to propagate. An ability to assign a dedicated IP address will solve this issue.

Status: Incomplete

Estimate (Updated): Q1 2022

Log Retention

The Log Retention feature provides the ability to retain logs between restarts

Status: Incomplete

Estimate (Updated): Q1 2022

Related Pull Request(s):

Provider JWT Service #1417

Ethereum Bridge

The Ethereum Bridge enables AKT users to acquire AKT using various ERC-20 tokens (USDT). By enabling users with more options to buy and sell AKT, we can increase liquidity, eliminate friction points found in the new developer onboarding process, and attract additional AKT buyers and traders from the crypto retail market. Additionally, this will increase our likelihood of working with Tier 1 exchanges and DEXs like Uniswap.

The Gravity Bridge went live on December 14. We’re currently testing the bridge and the AKT ERC-20 contract is currently under development and audit.

Status: Mainnet

Related Repositories:

Gravity Bridge

Akash Javascript SDK

Javascript SDK simplifies extending Akash in Javascript applications by providing libraries to improve access to the Akash API. The SDK also abstracts standard functions like credential management, retries, data marshaling, serialization, and deserialization.

The first version is complete and currently being tested on a new notification service to be announced next quarter.

Status: Incomplete

Updated Estimate: Q1 2022

AKCMD Deploy Tool

AKCMD is a command-line utility that simplifies workload management on the Akash network. AKCMD is a complementary tool to core Akash CLI that focuses on improving tenant workflow by taking an opinionated approach to deployment on Akash Network.

Much progress has been made and the first version will be ready by mid-January.

Status: Incomplete

Updated Estimate: Q1 2022

Lease Renegotiation

This feature provides the ability for users to renegotiate the AKT price without breaking the lease. The volatility of AKT leads to unstable value exchanges, as the AKT denominated price is set during lease creation and doesn’t change until the lease terminates. When the dollar AKT is higher than it was during lease creation, it may benefit the provider at the cost of the tenant and vice versa. An ability to renegotiate the lease during its life cycle solves this issue.

We’re exploring a new stable payment mechanism for Akash as part of Akashian Economics 2.0. This feature may be obsolete.

Status: Not Started

Updated Estimate: Not Planned

Supermini Update

Wed, 06 Oct 2021 00:00:00 +0000

We have an important announcement today, but first, I want to give a brief update on how Akash Network is progressing. We are seeing strong and consistent growth since releasing Akash’s distributed peer-to-peer marketplace for cloud compute in March.

New deployments have been averaging about 200 per day for several weeks, active deployments are steadily increasing, and we crossed the 25,000 deployments milestone in just six months.

The adoption continues to grow, with developer tooling, guides, and integrations rising alongside deployments. Akash is meeting a real market demand at a fraction of the cost of centralized cloud services.

Today, we are at a critical phase in Akash’s growth—one that sometimes includes pivots to our path forward to ensure the long-term success of the network, so we are postponing the Akash Supermini. While I know many of you have been eagerly anticipating the Supermini, this is a situation where a good idea came at the wrong time.

People think focus means saying yes to the thing you’ve got to focus on. But that’s not what it means at all. It means saying no to the hundred other good ideas that there are. You have to pick carefully. I’m actually as proud of the things we haven’t done as the things I have done. Innovation is saying no to 1,000 things.

Steve Jobs

In October of 2019, just before the COVID-19 pandemic put the entire world on pause, we demonstrated the flexibility of our platform by running Akash’s software on a low-power ARM-based Raspberry Pi. The “Akash Pi” was the genesis of the Akash Supermini. Engineering teams around the world use Pis for testing, running scripts, and even acting as servers on test networks. The Pi is a versatile device, but we knew the market wanted something with high performance for running machine-learning workloads and supporting production applications.

We set out to design a miniature supercomputer for the home office, a powerful machine that you could use to offload heavy workloads and rent to others looking for high-performance compute. The Supermini’s design was fit for the home office, and the spec sheet of its hardware included a powerful GPU. We believed that a GPU was critical to support machine learning. Since we needed to explore the viability of the Supermini both technically and economically, we planned to make just 300 units.

We intended the Supermini to be a consumer-focused appliance that would enable almost anyone to enjoy the benefits of cloud computing while maintaining data sovereignty. Excess compute from Supermini could be contributed to Akash’s decentralized cloud to support the network and earn passive income in AKT. This goal is still our long-term intention, but as Akash has grown over the last couple years, we found that introducing the Supermini now would be premature for four key reasons.

The Market has Spoken

First, the market is demanding a different product, and we are responding to the massive growth in deployments on our network. We have seen impressive growth, reaching the first hundred daily application deployments in 120 days, but the next hundred in less than 30. Now we are seeing roughly a doubling of deployed applications every month. A few star applications like Osmosis DEX and Skynet (a decentralized S3 alternative) live on Akash’s open-source decentralized cloud, and ShapeShift is considering using Akash for its decentralized autonomous organization (DAO).

We are in a crucial phase of building application reliance on Akash, particularly for workloads that have no real alternatives among centralized providers, such as data services for DAOs. We are still early in our journey, but Akash is maturing quickly, both technologically and in the diverse set of applications that require a permissionless, decentralized cloud. As reliance on Akash grows, we will be better positioned to reconsider the Supermini to take full advantage of its utility and powerful use case.

Technical Support

The second reason is technical. GPU support on Akash is still under development, and this feature is necessary to make the Supermini profitable for its users. Until we roll out GPU functionality, the Supermini simply would not work as intended. In order for the Supermini to be viable, Akash needs multitenant GPU infrastructure, and we are several months away from testing and deploying that functionality. Right now, Akash supports CPUs, storage, and memory. Building out bandwidth marketplaces and working around the limitations of home bandwidth also need to be deployed before the Supermini could work properly. We strongly believe it would be better not to launch a product that would leave customers waiting for the full functionality to be unleashed.

Economic Viability

The third reason is economic. Today Akash is focused on converting data centers into Akash providers because it’s more competitive than launching home-based hardware.

Our number one risk is competition from datacenter compute. Why would anyone choose a Supermini over a compute cluster in a data center?

We can compete on cost, but we need a critical mass of users first to make contributing compute economically viable for the Supermini.

The Revolution Will Not Be Centralized

The fourth reason is more philosophical. The Supermini is intended to be a managed product, a plug-and-play appliance. Our team would have directly managed firmware development and update deployment so that the Supermini owners would not need technical expertise. But as a result, releasing Supermini now would potentially introduce too much centralization to the network, which is against our ethos at Akash. Once Akash is more fully built out, the risks posed by a centrally managed appliance like the Supermini will be diminished, but we are not there yet.

What’s Next?

For those of you who preordered a Supermini, we want to make sure that you are properly compensated for your enthusiasm and trust in our vision. We recognize that your deposit came with an opportunity cost that went beyond just the hundred dollars you spent, so for each Supermini unit reserved, you will be refunded in full plus an additional 100 AKT. We hope that this refund will do more than just give you back your money. We hope that it will demonstrate our commitment to Akash’s bright future. You will be receiving an email to the address that was used to place your order with reimbursement details and instructions on claiming your AKT.

Onward and Upward

As I mentioned at the beginning, Akash is gaining momentum, and we will continue capitalizing on that. Later down the road, we can revisit the idea of the Supermini. It is still a good idea for the right time. But for now, we will be pouring our energy into making sure that Akash fulfills its promise of a decentralized cloud ecosystem that is permissionless and censorship-resistant—delivering data sovereignty to all.

Product Roadmap 2022

Wed, 06 Oct 2021 00:00:00 +0000

Since the launch of Akash Network, a distributed peer-to-peer marketplace for cloud compute, we’ve been hyper-focused on stability while pursuing product-market fit. We’re excited to have achieved both in under six months since the launch.

As we continue to improve the user experience on Akash Network and navigate users’ needs, we see accelerated growth in network usage and revenue. New deployments have averaged about 200 per day for several weeks, with active deployments steadily increasing, and we’re proud to have crossed the 25,000 milestone in total deployments.

Most recently, to make the provider/tenant relationship more seamless, we released the Akash Provider Upgrade (v0.14) that allows end-users to troubleshoot their deployments and includes other essential features that improve provider performance.

The possibilities of building on Akash are endless. Our approach is to identify a community where Akash’s value proposition can be communicated clearly, increase awareness, and improve user experience by building onboarding tools to gain adoption within the community.

At the present, we have a solid platform optimized for builders and have seen the emergence of community tools like Akashlytics and Deploy Tool that bring in a steady set of users with a simplified graphical user interface (GUI). And, with Akash Omnibus, where one can launch a scalable proof of stake (PoS) node network in just a few steps, we saw impressive growth and adoption within the Cosmos ecosystem as a whole. Additionally, community-generated content such as this Guide to Mining PKT on Akash at Scale takes users one step further into the power of mining on Akash.

Scaling this approach to broader use cases such as machine learning will impact Akash’s growth exponentially.

This roadmap is how we get there.

2020 to 2021: Acceleration to the DeCloud

Tue, 19 Jan 2021 00:00:00 +0000

In 2020, the pandemic shifted more of our work and personal lives online, accelerating explosive demand for cloud computing and services, projected to be a $370 billion market by 2022 (IDG 2019).

We saw how developers and organizations had few options beyond the four CSPs (Amazon Web Services, Google Cloud, Microsoft Azure, and Alibaba Cloud) who dominate with 71% market share.

We witnessed how much cloud access and costs constrained growth and scale for startups and organizations weathering the difficulties of the past year. In the race to find a vaccine and treatments for COVID-19, access to cloud computing has been critical, not just for startups, but also for academic institutions, researchers, and clinicians.

My cofounder and CTO Adam Bozanich and I started Akash Network to enable developers and organizations around the world to have greater access, freedom, and flexibility to build and grow. As open source developers, we wanted to create an alternative to the pricing inefficiency, inflexibility, and anti-competitive practices of centralized cloud service providers.

The pandemic has been a humbling experience that not only made us revisit our priorities, but strengthened our focus and commitment to materializing The Unstoppable Cloud, the first viable alternative to centralized cloud providers like Amazon Web Services, Google Cloud, and Microsoft Azure.

More than ever, we need a decentralized, permissionless, and open cloud where people become participants in their future.

Progress to our vision is a marathon and not a sprint, and our success depends on a team that relentlessly ships, and the continued support of Akashians around the world.

I’m proud to share 2020 milestones that we achieved across our product, partnerships, promotions, and people, that accelerate us to the DeCloud in 2021.

Highlights from 2020 in the Cloud

_____

PRODUCT

2020 was a landmark year for our product milestones. In Q1 2020, we migrated to Cosmos SDK and in the process, we reduced our codebase by a massive 150,000 lines. In order to provide a framework for others to create and run their own testnets, we captured our learnings in the Decentralized Cloud Standards.

We also evolved our Akash Network Token Economic Model. We introduced two additional powerful drivers for growth and income generation in the ecosystem–the allocation of subsidies, in the form of a Subsidy Pool and the distribution of a network dividend from a portion of the lease fees, Take Income.

In Q2 2020, we launched The Akashian Challenge Incentivized Testnet, one of the largest and most ambitious testnets in the decentralized ecosystem. During Phase 1, our testnet withstood an AWS outage that brought down the centralized cloud (and internet). It also weathered a massive zero fee transaction attack. Both the AWS outage and the attack showcased the resilience of our decentralized platform.

In the initial phases of The Akashian Challenge, we tested governance and voting, and improved the process for network upgrades to strengthen our platform. These explorations gave us critical insights on how to build a healthy and vital community for growth, and led to the successful launch of our Mainnet 1 with a full 64-validator set.

In The Akashian Challenge Phase 3, we integrated performance enhancements from Cosmos SDK v0.40, and tested Akash DeCloud’s deployment platform. With 500,000 Akash Token (AKT) in rewards and hundreds of participants joining from around the world, The Akashian Challenge Phase 3: Developer Operations included guided and open ended challenges.

Phase 3 testnet participation, deployments, and learnings, exceeded our expectations:

3800+ applications deployed
500+ developers
149 registered validators

During Phase 3, Forbole deployed their Big Dipper block explorer on Akash DeCloud, making it the first instance of a prominent block explorer to migrate from centralized cloud to decentralized cloud.

Serum DEX UI became the first instance a major DeFi project is hosted on the DeCloud. You can check out the full Awesome Akash list for a complete listing of the apps that were deployed in Phase 3.

In the middle of all this action, Akash surpassed 1,000,000 blocks.

Through running three phases of The Akashian Challenge, we’ve been able to gather data, identify critical issues, and ensure our network’s scalability, security, and usability before launching our DeCloud: Mainnet 2.

Leveraging Akash’s proprietary cloud and blockchain technologies, developed over five years, Supermini will be manufactured and launched in the United States with premium materials and powerful processors.

We progressed design, technical specifications, and production on Supermini. We worked with design duo Guillermo Sanchez del Corral and Rafael Saenz of debuti, and industrial designer Sungbum Park, to come up with Supermini’s distinctive chassis and infinity mirror design.

We launched a test online pre-order campaign and sold out within 3 weeks of the campaign launch. Production is underway for a limited launch later this year.

AKT Token Initial Exchange Offering & Liquidity

In Q3, we launched Akash Mainnet 1 and held the Akash Token (AKT) IEO on BitMax, one of the world’s top exchanges. Mainnet 1 was the beginning of Akash DeCloud and network governance, enabling staking and governance operations including the ability to delegate to validators and vote on governance proposals.

Shortly after, we announced a second exchange listing on BitMart, a premier global digital asset platform and ranked among the top crypto exchanges on CoinMarketCap!

As the first Akash exchange partner to enable residents of the United States to access AKT, BitMart enabled more Akashians around the world access to AKT, and to AKT staking rewards.

PARTNERSHIPS

Our goal is to provide developers with increased access to decentralized services. Towards this end, we announced that we were partnering with Solana to bring web-scale smart contracts to Akash DeCloud.

Akash users will be able to run secure and scalable smart contracts on Solana’s hyper-performant platform and pay using Akash Token (AKT). Solana’s users will soon be able to run distributed applications (like machine learning or web apps) and settle using Solana Token (SOL) on Akash. Our partnership will also give Solana Validators the ability to run their nodes on a truly decentralized cloud and significantly decrease their cloud costs.

We announced a partnership with Cosmos’s ICF to make IBC protocol a reality, enabling us to integrate interchain technologies faster than any other company. With this partnership, Akash solidifies an essential position in the Cosmos ecosystem to accelerate development of the IBC interoperability protocol.

We’ll be working on the leading edge of research, deploying live production systems to make IBC a reality. Our partnership will increase composability and massive scaling for decentralized projects like DeFi.

In Q3, we announced an integration with Kava, the first cross-blockchain DeFi platform, to enable Kava’s stablecoin USDX as the first coin for fee settlement on Akash’s DeCloud platform. The integration with Kava will also enable Akash Token (AKT) to be used as collateral for USDX loans.

This integration strengthens AKT’s liquidity and provides Akash users with a stable medium of exchange, while achieving greater adoption for Kava’s stablecoin and an increased debt ceiling from AKT collateral.

We announced that Akash Network is to integrate with Chainlink, the market-leading decentralized oracle network. By integrating with Chainlink, we’ll be able to ensure that Akash’s users have access to the most secure and accurate price data available. We look forward to expanding the integration with Chainlink to bring on-chain data for application uptime to Akash DeCloud.

We announced our integration with Cosmostation, the number one wallet for the Cosmos ecosystem. A trusted wallet provider for other top Cosmos projects including Akash partner Kava Labs, Terra, and Iris, Cosmostation is built on the Cosmos SDK and has mobile wallet apps on Android and iOS.

PROMOTIONS

In support of aggressive company and product goals, our team worked across branding, content, community, communication, events, partnership marketing, KOL/media engagement, and acquisition marketing to achieve key Growth metrics in 2020:

Growth Metrics

Product:
- AKT Token: 5x growth in price in 3 months
- The Akashian Challenge Phase 3: 3,800 Applications; ~500 Developers
- Supermini: $300,000 Supermini Pre-Orders (Sold Out)
- Mainnet 1: 64 Validators
Community:
- 10,700 Twitter Followers (10x)
- 7,236 Telegram Members (5x)
- 5,000 WeChat Members
Thought Leadership:
- 71 Blog Articles
- 38 AMAs / Events

Global Expansion

At Akash Network, outside of the US, our Chinese audience makes up the second largest group of visitors to our website and communities. We’re also fortunate to have a number of Chinese investors and partners, including Huobi Pool, SNZ, Outpost Capital, Hone Capital, Forbole, and Steven Fan of Tencent.

We la unched the Akash Network Chinese Community, and expanded our vision for the world’s first decentralized cloud marketplace to Chinese audiences. We also produced and hosted three Cosmos Ecosystem Summit events in China with 5,000+ attendees for each event.

Outside of the US, Akash’s Russian audience is our second largest community. We’ve also been fortunate to have a large number of Russian participants in The Akashian Challenge, our incentivized testnet. We were excited to launch the Akash Network Russian Community, and welcomed Russian audiences around the world to learn more about Akash Network and Akash Token (AKT) by visiting our Russian website and joining our Russian Telegram Group.

With a long history and familiarity with tokens and digital payments that has spanned decades, Koreans have been at the forefront of crypto adoption and growth. Korea has the highest percentage of citizens who use crypto, and the Korean government has made regulatory and investment commitments to expand the crypto/blockchain industry. We welcomed Korean audiences around the world to learn more about Akash Network and Akash Token (AKT) through the launch of our Korean Community.

This past year, our team developed and launched 71 blogs. Following are our favorite articles launched in 2020:

PEOPLE

We’ve been intentional about building a team with a legacy of successfully implementing developer-focused and SaaS go-to-market strategies that scale. This past year, we grew a team that relentlessly ships by 3x.

Artur Troian, a multi-talented architect and builder, joined our team as Senior Software Engineer. Artur is known in the open-source community for his work on VolantMQ, a High-Performance MQTT Server, and has an exciting Github.

With a background encompassing hardware and software solutions in the IoT and wearables industry, Artur previously led product architecture and engineering at NotifAi, an IoT hardware company he cofounded.

After stints at Moxie Software and Spiceworks, Eric Urban joined as Distributed Systems Engineer. Eric is helping build the foundation for our decentralized cloud computing marketplace.

As our first Creative Content Manager at Akash, Olive Kimoto joined our team to develop and expand our visual brand framework, and spearheads our global content and localization efforts to engage audiences around the world. She approaches her work with empathy, one of Akash’s core values, and a value that makes Olive such an adaptable and exceptional creative designer.

Known in the Cosmos community, Ryan Sumpter joined Akash as a Developer Relations Engineer after spending 8 years at an engineering consulting firm designing power substations, and mining Bitcoin in 2012.

If you’ve ever used the GNU Bash, GNU Makeinfo, GNU Info, GNU Finger, GNU Echo, or GNU Emacs, chances are, you’ve heard of open source pioneer and innovator Brian Fox and have leveraged his ubiquitous open source contributions. We were excited to announce that Brian joined as an Akash Advisor. His strategic and technical guidance, experience, and ideas will be invaluable as we build the world’s first decentralized cloud to enable greater access, flexibility, and freedom for builders of the future.

2021 Journey to the DeCloud

_____

Early in 2021, our first priority will be launching Mainnet 2, the materialization of our DeCloud. Mainnet 2 will be the world’s first non-custodial cloud with a decentralized attribution model. Users will be able to set up their own provider and deploy their applications onto Akash DeCloud.

Our team will also be improving the developer experience, which includes building improved provider tooling, enhanced deployment tooling, and enabling more customizable attribute matching in the deployment process.

Our continuing work with Inter-Blockchain Communication (IBC) will unlock unprecedented levels of value exchange between networks in the Cosmos Ecosystem at first, and expand to other networks such as Ethereum, eventually connecting the entire crypto space.

The implementation and adoption of IBC within the Cosmos ecosystem will allow more projects to exchange value across the Cosmos Hub, and participate in Akash’s decentralized marketplace. With IBC, Akash will reduce the barrier to adoption by enabling other currencies to access our cloud marketplace and pay for cloud compute.

In the immediate future, Akash will leverage money markets such as THORChain and Kava to improve liquidity. With the launch of Althea’s Peggy, Akash will be able to interoperate with Etherum, enabling AKT access via DEXs such as Uniswap.

Akash’s upcoming Mainnet 2 is IBC enabled, running on Cosmos SDK 0.4.0. The first use case for IBC is DEX support, both for the Cosmos ecosystem and for Ethereum—with strong demand from our users, we’re excited about this.

IBC will progress our vision for a truly decentralized and interoperable cloud. One could store data on a storage network FileCoin on Sia, use KMS on NuCypher, manage DNS on Handshake, and pay for all of these services using Akash Token (AKT).

As we’ve accelerated our milestones and expanded globally, we’ve focused on expanding liquidity for AKT to support our growth, and to meet increasing global demand for access to AKT. In January, we announced our third exchange listing on Bithumb Global, and we’ll continue to increase AKT liquidity this year.

Akash will become a gateway to the decentralized cloud, powered by IBC.

Later in 2021, we’ll be launching the first production run of our Supermini portable supercomputers and enabling people around the world to join DeCloud and earn AKT.

This year, Akash is truly Unstoppable!

Don’t Miss the Latest News!

_____

Join our Telegram for the latest news, giveaways, and invites to special events!

CEO Statement on Total AKT Token Circulation

Tue, 20 Oct 2020 00:00:00 +0000

Greetings Akashians, I hope you’ve been staying safe and well!

Since 2016, when my cofounder and CTO Adam Bozanich and I started building Akash Network, we staked our lives and our reputation to enable developers and organizations around the world to have greater access, freedom, and flexibility to build and grow.

Together, we lead a small global team of experienced technology platform and open source experts, and we’ve been working to materialize The Unstoppable Cloud, the first viable alternative to centralized cloud providers like Amazon Web Services, Google Cloud, and Microsoft Azure.

In the past month, we’ve gotten much closer to realizing our vision for Akash’s decentralized cloud marketplace with the launch of Akash Mainnet 1 and our Initial Exchange Offering (IEO) on BitMax–two critical milestones for securing and growing our platform.

We recognize that this is a marathon and not a sprint, and our success depends on the continued support of Akashians around the world who believe in our vision.

Based on feedback we’ve received from our global community following the IEO, we’ve since realized that there was confusion around how staking rewards accrued, and how the staking rewards affect total token circulation.

We would not do anything to jeopardize your trust, and our team has taken this feedback very seriously.

First, we take full accountability for not providing more communications and information on how our staking rewards impact the total circulating supply.

####
Clarification on Total Akash Token (AKT) Supply
_____

To clarify several points around token supply since our IEO:

On Akash Network, AKT holders stake AKT to secure the Akash PoS network and in exchange earn rewards.
a. In the early days of the network, when meaningful income is not yet realized from network utilization, stakers earn ~54% APR rewards from inflation (new tokens minted).
b. The ~54% APR staking reward starts accruing at Mainnet 1 launch.
c. This APR is subject to change as we aim to lower inflation as the network matures. We will likely submit the first governance proposal change to this before the end of October 2020.
On September 25th, BitMax announced our IEO on the same day our Mainnet 1 launched. The circulating supply at the Genesis block was 2.8M AKT with 54% APR as staking rewards announced, as reflected in BitMax promotions that day.
To provide more information to prospective investors, we launched and announced our AKT Token mini-site with our unlock schedule included.
On October 16th, when our listing went live on BitMax (Block #284,500), our total token in circulation of 5,651,695 AKT included 2,800,000 AKT unlocked at Genesis and 2,851,695 AKT from accrued Staking Rewards.
As of today (Block #342,312), we have a total of 6,239,818 AKT in circulation, including 2,800,000 AKT unlocked at Genesis and 3,439,818 AKT from accrued Staking Rewards.
As of this post’s writing (Block #342,467), Akash has a staking ratio of 85.10%, meaning 88.03M of AKT is locked up for at least 21 days:
a. Akash has one of the highest bonding ratios in the Proof-of-Stake and highest in the Cosmos Ecosystem.
b. For comparison, Band Protocol has an 81.28% staking ratio, and Kava has a 73.93% staking ratio.

How We’ll Improve Our Communications About AKT

_____

Going forward, we are committed to ensuring clearer communications and education around our token economics:

We’ve updated our AKT Token mini-site to include a more dynamic and detailed unlock and circulating supply schedule for your reference.
We’ll also provide and share a biweekly token supply and rewards update from our CFO Cheng Wang, on The Unstoppable Blog.
For those new to staking, we’ll be releasing a guide on how to stake your AKT and earn our generous token rewards.

As I’ve mentioned before, we couldn’t have achieved our Mainnet 1 and BitMax IEO milestones without your support. We’re excited to share more soon about Phase 3 and Mainnet 2–the realization of Akash DeCloud aka The Unstoppable Cloud.

I’m grateful for your belief in our vision, and for your patience and understanding as we improve our communications efforts.

I invite you to join our Telegram and continue to give us feedback so we can improve our communications, product, and community.

####

Join The Unstoppable Cloud

The Unstoppable Update: October 2020

Wed, 07 Oct 2020 00:00:00 +0000

At an accelerating pace, we find more of the ways we connect, play, transact, and work transitioning to the cloud. Developers and organizations need cloud computing and services that enable greater scale, flexibility, and price performance to meet this global demand for throughput and content.

And yet, they continue to have few options beyond the four cloud service providers (Amazon Web Services, Google Cloud, Microsoft Azure, and Alibaba Cloud).

We set out to build a decentralized alternative, a faster, more efficient, and lower cost cloud–one that would make developers and organizations unstoppable.

With the recent launch of Akash Mainnet 1 and our upcoming IEO this month on BitMax, we are much closer to realizing this vision of The Unstoppable Cloud.

We couldn’t have gotten here without your support, and we thank you for joining us on our journey.

For Akashians around the world, this is just the beginning.

####

Mainnet 1 Launch & BitMax IEO
_____

On September 25th, we launched Akash Mainnet 1 and announced our upcoming IEO on BitMax, one of the world’s top exchanges. Mainnet 1 is the beginning of Akash DeCloud and network governance, enabling staking and governance operations including the ability to delegate to validators and vote on governance proposals. The auction will begin on October 15th at 10:00am EDT, and the listing will go live on October 16th, at 10:00am EDT. [Learn More >

](https://akash.network/blog/announcing-akash-mainnet-live-and-bitmax-ieo/)

####
AKT: Akash Token Page
_____

We recently launched a new Token web page to share more information about AKT. Akash Network is a sovereign proof-of-stake chain built on Cosmos Hub, that leverages Akash Token (AKT), a native utility token, as the primary means to govern, secure the blockchain, and provide a default mechanism to store and exchange value. AKT will act as the reserve currency in Akash’s multi-currency and multi-chain ecosystem, while ensuring economic security of the platform’s public blockchain by means of Staking. Check out our new AKT Token page for information on Token supply, staking rewards, and unlock schedule. Learn More >

Akash to Integrate Kava’s USDX
_____

A few weeks ago, we announced an integration with Kava, the first cross-blockchain DeFi platform, to enable Kava’s stablecoin USDX as the first coin for fee settlement on Akash’s DeCloud platform. The integration with Kava will also enable Akash Token (AKT) to be used as collateral for USDX loans.

####

Get the Latest Akash and AKT Token Updates and Giveaways!

Greg Osuri

Confidential Compute Comes to Akash

One Line

A private LLM in one deployment

What this protects, and what it doesn’t

Why this matters now

Get started

Testimony on AI, energy, and distributed compute

Akash Roadmap 2025

Public Cloud Is a Public Utility

Special Interest Groups (SIGs)

Working Groups (WGs)

User Groups (UGs)

Committees

Steering Committee

Whats Next?

New Website ✨

New GitHub Home 🏡

Kick Off 🚀

How can you contribute?

Annoucment Video

Q4 Update on Akash Roadmap 2022

Persistent Storage

Network Usage Dashboard

Hostname Migration

TTY (Shell) Access

Inflation Decay Curve

Airdrop Faucet

Provider Onboarding Framework

Developer Hub

ASN (IP Addresses) Market

Log Retention

​​Ethereum Bridge

Akash Javascript SDK

AKCMD Deploy Tool

Lease Renegotiation

Supermini Update

The Market has Spoken

Technical Support

Economic Viability

The Revolution Will Not Be Centralized

What’s Next?

Onward and Upward

Product Roadmap 2022

2020 to 2021: Acceleration to the DeCloud

Highlights from 2020 in the Cloud

2021 Journey to the DeCloud

Don’t Miss the Latest News!

CEO Statement on Total AKT Token Circulation

How We’ll Improve Our Communications About AKT

The Unstoppable Update: October 2020

.: Join Our Telegram :.

Ethereum Bridge