What is AIcuNet

AIcuNet is a Layer-1 network built toward three goals: decentralized AI, a platform for independent applications (dApps), and an independent decentralized space for its users. The foundation has been live since 12 July 2026 — mining on an ordinary PC, no transaction fees. The smart-contract engine for dApps is already in the network's code; opening it to developers, like shared AI compute, is on the roadmap and is named as such, not as a finished feature. This page is the short, honest answer to "what is AIcuNet, what does it already do, and is it worth reading further".

A holographic globe with glowing network nodes in front of a window over a neon city at night.

What AIcuNet is

AIcuNet is a Layer-1 blockchain: a single public ledger maintained by the project nodes running the same protocol, with code under the MIT license. The project ships a web wallet and a launcher for home miners. The code is open under MIT on GitHub; the protocol — not the website — is the product.

A blockchain is not a website and not a wallet. The chain holds the rules, the wallet holds the keys, the launcher keeps a node online. AIcuNet ships all three because the chain still needs people willing to run a node on a home PC.

What works today (Phase 1)

Phase 1 is the live network. Three properties hold:

  1. Time-driven proof-of-work. Time is divided into three-second slots, one block per slot, one chain.
  2. Memory-hard mining. Blocks are produced by CPUs and RAM, with no ASIC required. More RAM means a better chance of finding the next block. Phones do not mine; contributing from other devices (storage and light compute) is a Phase 2 concept.
  3. No fees, priority instead. Transactions have no fee. The protocol uses a priority mechanism instead of a gas market to order them.

A few more facts:

  • The mainnet has been running since 12 July 2026 on a single public chain.
  • Today the nodes that carry the network through its launch phase run on three continents (Europe, North America, Asia), in four countries: the United States, Thailand, the Netherlands and Switzerland. The Mining Map shows them and will grow with the network; cities and providers are not published.
  • The code carries an MIT license and is open on GitHub; multi-pass security review has been done internally with different models (cross-checked), and a public bug-bounty is planned.

What is on the roadmap (Phases 2 and 3)

Two layers sit above Phase 1. Both are concepts, not shipped products:

  • Phase 2 — resource layer. Nodes contribute storage and light compute; an internal token (CuJoule) is paid out for resource contribution. Mining on phones is not part of Phase 2.
  • Phase 3 — GPU and AI compute. Shared AI resources are planned to run on the same chain as the consensus layer.

The dApp engine is already in the network's code: smart contracts written in JavaScript, app interfaces stored in the chain itself, user-issued tokens and a built-in dApp editor. Opening it to developers is the next step on the roadmap; until developers can use it, we do not call it a live feature. No partner names, no working AI demo yet. What is done and what comes next is listed on the Roadmap page.

Where this is heading: a network carried by ordinary computers around the world, where the network itself supplies storage and compute for AI and for independent applications, and where people hold their own keys and their own data. In Web3 terms: applications and data that belong to the people who use them. We name the phases plainly: Phase 1 runs today; everything above it is roadmap.

What makes AIcuNet different from "another L1"

Four properties do most of the work. None of them is a slogan; none is a one-of-a-kind claim:

  1. Memory-hard mining. CPU plus RAM, no specialised hardware. A laptop with a few gigabytes of free RAM is enough to take part.
  2. dApps inside the chain. The engine is already in the code: smart contracts in JavaScript, app interfaces stored in the chain, user-issued tokens. With no fees, nobody has to buy "gas" before pressing a button in an app. The network's first application, Miner's Hour, has been running on the network since 30 September 2026 in a trial period, and a network upgrade is planned that gives smart contracts data storage and cryptographic functions. Opening this layer to developers is the next step; until then dApps from other developers and AI are not a live feature.
  3. No fees, with priority. Transactions settle without a fee; a priority mechanism orders them.
  4. Open source under MIT. The code carries an MIT license. No outside review firm has signed off on the code; the multi-pass internal review is on file, but details are not published.

These four are the differences, not the marketing. AIcuNet is a small early-stage network; the wallet page describes what you actually do on it today.

Who is behind it

AIcuNet is built by one independent developer. The code is open under MIT: github.com/aicunet/aicunet-core. The network itself is the result of that work: a Layer-1 built for decentralized AI and independent applications, running on home PCs today.

What you see once a node runs on your machine is described on the AIcuNet wallet page.

Risks

AIcuNet is an early-stage network. The block reward is tied to network growth; the mechanism is being refined and its parameters will be published separately, with no promises of price or return. No outside review firm has signed off on the code; the project has done a multi-pass internal review with different AI models (cross-checked) and applied hardening fixes, but findings are not published. A public bug-bounty is planned, not launched.

Private key

The only truly critical thing on this network is your private key. If you lose it, access is gone permanently — there is no recovery, no support hotline, and no one on the project will ever ask for it. Keep an offline copy, never type it into a website, and treat any "recovery service" as fraud. The private-key safety page covers the operational steps.

What next

Next, read about the AIcuNet wallet or the FAQ and risks. The Windows node package goes to invited participants first — request an invitation.