diff --git a/.llms-snapshots/llms-full.txt b/.llms-snapshots/llms-full.txt
index 2a0fe3cc..9bb413ba 100644
--- a/.llms-snapshots/llms-full.txt
+++ b/.llms-snapshots/llms-full.txt
@@ -268,7 +268,7 @@ This enables:
* A smooth dev loop, from prototype to deployment
* A unique way to build, debug, and validate smart contract logic and frontend behavior — all in one place
-
+
---
@@ -376,8 +376,8 @@ Likewise, not all services are mounted by default - but they can be turned on (o
| ICP Index | ✅ | ✅ |
| NNS Governance | ✅ | ➖ |
| Cycles Minting (CMC) | ✅ | ➖ |
-| Cycles Ledger | ➖ | ➖ |
-| Cycles Index | ➖ | ➖ |
+| Cycles Ledger | ✅ | ➖ |
+| Cycles Index | ✅ | ➖ |
| Registry | ➖ | ➖ |
| SNS | ➖ | ➖ |
| NNS-dapp | ➖ | ➖ |
@@ -447,16 +447,16 @@ await initSatellite({ satelliteId: "aaaaa-bbbbb-ccccc-ddddd-cai", container: f
The admin server running on port `5999` provides a variety of internal management. Below are some tips and example scripts to make use of this little server.
-### Get ICP
+### Get Cycles
-If you're using the full environment, the Console UI includes a "Get ICP" button in the wallet. It's a quick way to get ICP out of the box.
+If you're using the full environment, the Console UI includes a "Get Cycles" button in the wallet. It's a quick way to get Cycles out of the box.
-
+
-You might want to transfer some ICP from the ledger to a specified principal, which can be particularly useful when you're just getting started developing your app and no users currently own ICP. This can be achieved by querying:
+You might want to transfer some Cycles from the ledger to a specified principal, which can be particularly useful when you're just getting started developing your app and no users currently own Cycles. This can be achieved by querying:
```
-http://localhost:5999/ledger/transfer/?to=$PRINCIPAL
+http://localhost:5999/ledger/transfer/?to=$PRINCIPAL&ledgerId=um5iw-rqaaa-aaaaq-qaaba-cai&amount330000000000000
```
For example, you can use the following script:
@@ -8094,8 +8094,8 @@ Keeping your modules running smoothly is essential for any application. The moni
* **Cycle refilling**: Monitored modules are automatically topped up when their balance falls below what's needed to stay active.
* **Self-Monitoring**: The monitoring monitors itself to maintain sufficient cycles, with full control remaining in your hands at all times.
-* **Automatic ICP Conversion**: Can mint new cycles from the ICP in your wallet, ensuring your modules stay adequately funded.
* **Hourly Checks**: The system evaluates balances once an hour.
+* **Automatic ICP Conversion**: Can mint new cycles from the ICP in your wallet, ensuring your modules stay adequately funded.
---
@@ -8749,95 +8749,92 @@ For most applications, we recommend using the default subnets and staying on the
# Wallet
-This section provides guidance on managing your assets and cycles with your [wallet](/docs/terminology.md#wallet), which are essential for maintaining and providing enough resources for your modules in the Juno ecosystem.
+This section provides guidance on managing your cycles with your wallet (your account), which are essential for maintaining and providing enough resources for your modules in the Juno ecosystem.
**Important:**
-Just like your modules, your wallet is fully under your control — Juno cannot access, move, or recover the ICP or cycles held inside.
+Just like your modules, your wallet is under your control — Juno cannot access, move, or recover the cycles held inside.
-Because of this non-custodial model, there are no refunds, reversals, or recovery options. Always double-check destination addresses before sending funds.
+Because of this model, there are no refunds, reversals, or recovery options. Always double-check destination addresses before sending funds.
-As a best practice, we recommend not holding large amounts of ICP in your Juno wallet unless necessary. Use it as a utility wallet for fueling your modules — not as a long-term vault.
+As a best practice, we recommend not holding large amounts of cycles unless necessary. Use it as a utility for fueling your modules — not as a long-term vault.
-We also recommend enabling [monitoring](/docs/management/monitoring.md) to ensure your Mission Control stays alive and responsive at all times.
+We also recommend enabling [monitoring](/docs/management/monitoring.md) to ensure your projects and analytics stay alive and responsive at all times.
---
-## What are ICP?
-
-ICP are the native cryptocurrency of the [Internet Computer](https://internetcomputer.org). They provide utility for powering the network and are also used for governance.
+## What are Cycles?
-One key usage is converting ICP tokens to cycles, which are used to cover the computational and storage costs of running modules.
-
----
+Cycles are used to pay for infrastructure usage. Your Satellite, Mission Control or Orbiter consume cycles while they are active.
-## Why do I need ICP?
+The amount of cycles available determines whether a module will be active, inactive, or eventually decommissioned (deleted).
-Given that Juno is built on top of the Internet Computer (see [architecture](/docs/miscellaneous/architecture.md)), your modules require cycles to stay alive.
+This ensures that related costs cannot surpass the amount of cycles available.
-While you don’t necessarily need ICP in the Juno ecosystem since you can acquire cycles with Stripe through [cycle.express](https://cycle.express), having some ICP can still be interesting.
+Think of cycles like prepaid mobile data:
-It provides independence by allowing you to top up your modules without relying on third-party services. Depending on how you obtain your tokens, using ICP can also help lower transaction costs and offers interoperability with other Internet Computer projects, making it a flexible and practical option.
+* Just like your mobile plan allows you to make calls and browse the internet, cycles enable your containers to process computations and store data.
+* When your data (cycles) runs out, your service becomes inactive.
+* To keep your modules running smoothly, you need to top up your cycles regularly (manually or automatically).
+* If you don’t top it up, after some time, it will be decommissioned, similar to losing your prepaid number due to prolonged inactivity.
---
-## Buying ICP
+## Buying Cycles
-To get ICP from the outside world into your wallet, you can use most cryptocurrency exchange platforms that allow you to buy ICP (refer to this [list](https://coinranking.com/fr/coin/aMNLwaUbY+internetcomputerdfinity-icp/exchanges) of major ones). These platforms let you convert dollars (or other currencies) into ICP. Keep in mind that exchanges charge a fee for this service.
+The easiest way to purchase cycles — and get the best deal — is through [Cycle.express](https://cycle.express), which lets you pay with a credit card via Stripe.
-Once you have obtained ICP on those platforms, you can initiate a transaction to send it to your wallet. For this purpose, you will need to provide a destination address where the ICP should be sent. This destination address corresponds to the [Account Identifier](/docs/terminology.md#account-identifier) of your wallet.
+The service is integrated directly into the Juno Console. From your wallet, click "Buy" and follow the steps.
-You can locate the destination address in Juno's [console](https://console.juno.build). Once you've logged in, go to your [wallet](https://console.juno.build/wallet) and click "Receive".
+**Note:**
-
+The default purchase amount is $1 USD. You can change this amount on Stripe's payment page (maximum $100).
-Select "Account identifier".
+
-
+---
-Either copy your account identifier or use the provided QR code. This is the address you should use to receive ICP from the outside world.
+## Receiving Cycles
-
+If you already hold cycles or want to swap some, you can use the [OISY Wallet](https://oisy.com).
----
+To initiate a transaction manually, you will need to provide a destination address. To find it in the [console](https://console.juno.build), open the shortcut to your [wallet](https://console.juno.build/wallet) and click "Receive" select "Wallet ID".
-## Receiving ICP
+
-If you already hold ICP, you can transfer it from wallets within the ecosystem such as the [NNS dapp](https://nns.internetcomputer.org/), [OISY](https://oisy.com) or [others](https://internetcomputer.org/ecosystem?tag=Wallet).
+
-To initiate a transaction to send it to your wallet, you will need to provide a destination address, which in this case is your wallet ID.
+You can also connect OISY to Juno's console to initiate the transaction and proceed with the approval. This eliminates the need to copy, paste, or scan any addresses.
-You can locate your wallet ID in Juno's [console](https://console.juno.build). Once you've logged in, go to your [wallet](https://console.juno.build/wallet), where the information is easy to find.
+
-
-
-If you wish to use a QR code, click "Receive" and select "Wallet ID".
+---
-
+## Send Cycles
-Either copy your account identifier or use the provided QR code. This is the address you should use to transfer ICP within the ecosystem.
+Sending Cycles to the ecosystem or the outside world can be initiated from your wallet in Juno's [console](https://console.juno.build). To start a transaction, click "Send".
-
+**Important:**
-If you are using OISY, you can also connect this third-party wallet to Juno's console to initiate the transaction and proceed with the approval. This eliminates the need to copy, paste, or scan any addresses.
+Sending cycles transfers them to another wallet. To add manually cycles (resources) to your modules (Satellites, Orbiters, or Mission Control), use the **Top-up** feature instead.
-
+
----
+Enter the destination wallet ID or account identifier where you want to send cycles, along with the amount.
-## Send ICP
+
-Sending ICP to the ecosystem or the outside world can be initiated from your wallet in Juno's [console](https://console.juno.build). To start a transaction, click "Send".
+Review the transaction details and confirm to execute it.
-
+
-Enter the destination wallet ID or account identifier where you want to send ICP, along with the amount.
+---
-
+## Legacy Support
-Review the transaction details and confirm to execute it.
+For backwards compatibility with Mission Control that operated in ICP, the wallet features still support those tokens. You can receive and send ICP if needed.
-
+However, using cycles is now the recommended approach for all operations.
# Workarounds
@@ -9813,7 +9810,7 @@ You can customize the ports exposed by the emulator:
| Field | Description | Default |
| --- | --- | --- |
| server | The local Internet Computer replica port. Your app or project interacts with it. | `5987` |
-| admin | Admin server used for internal tasks (e.g., ICP transfer). | `5999` |
+| admin | Admin server used for internal tasks (e.g., Cycles transfer). | `5999` |
| console | Console UI port (only used with `skylab`). | `5866` |
**Note:**
@@ -10306,13 +10303,13 @@ However, in some cases, it may be useful to explicitly reference their IDs or UR
| Service | Canister ID |
| --- | --- |
| [Internet Identity](https://dashboard.internetcomputer.org/canister/rdmx6-jaaaa-aaaaa-aaadq-cai) | `rdmx6-jaaaa-aaaaa-aaadq-cai` |
+| [Cycles Ledger](https://dashboard.internetcomputer.org/canister/um5iw-rqaaa-aaaaq-qaaba-cai) | `um5iw-rqaaa-aaaaq-qaaba-cai` |
+| [Cycles Index](https://dashboard.internetcomputer.org/canister/ul4oc-4iaaa-aaaaq-qaabq-cai) | `ul4oc-4iaaa-aaaaq-qaabq-cai` |
| [ICP Ledger](https://dashboard.internetcomputer.org/canister/ryjl3-tyaaa-aaaaa-aaaba-cai) | `ryjl3-tyaaa-aaaaa-aaaba-cai` |
| [ICP Index](https://dashboard.internetcomputer.org/canister/qhbym-qaaaa-aaaaa-aaafq-cai) | `qhbym-qaaaa-aaaaa-aaafq-cai` |
| [CMC (Cycles Minting Canister)](https://dashboard.internetcomputer.org/canister/rkp4c-7iaaa-aaaaa-aaaca-cai) | `rkp4c-7iaaa-aaaaa-aaaca-cai` |
| [NNS Governance](https://dashboard.internetcomputer.org/canister/rrkah-fqaaa-aaaaa-aaaaq-cai) | `rrkah-fqaaa-aaaaa-aaaaq-cai` |
| [Registry](https://dashboard.internetcomputer.org/canister/rwlgt-iiaaa-aaaaa-aaaaa-cai) | `rwlgt-iiaaa-aaaaa-aaaaa-cai` |
-| [Cycles Ledger](https://dashboard.internetcomputer.org/canister/um5iw-rqaaa-aaaaq-qaaba-cai) | `um5iw-rqaaa-aaaaq-qaaba-cai` |
-| [Cycles Index](https://dashboard.internetcomputer.org/canister/ul4oc-4iaaa-aaaaq-qaabq-cai) | `ul4oc-4iaaa-aaaaq-qaabq-cai` |
| [SNS-Wasm](https://dashboard.internetcomputer.org/canister/qaa6y-5yaaa-aaaaa-aaafa-cai) | `qaa6y-5yaaa-aaaaa-aaafa-cai` |
| [NNS-dapp](https://dashboard.internetcomputer.org/canister/qoctq-giaaa-aaaaa-aaaea-cai) | `qoctq-giaaa-aaaaa-aaaea-cai` |
@@ -11892,8 +11889,8 @@ Do you have more questions or need further assistance? Feel free to reach out to
Juno has a simple starting point:
-* ✅ Free to get started: new developers receive credits to create one managing container and one project container.
-* 💰 Pay as you grow: additional modules (for projects or analytics) cost 0.4 ICP each to create.
+* ✅ Free to get started: new developers receive credits to create a container for their first project, with initial resources included, ready to use.
+* 💰 Pay as you grow: additional modules (for projects, monitoring or analytics) cost 3 T Cycles each to create.
* 📦 Operating costs: ongoing costs for storage, compute, and deployments are paid with cycles.
From there, you can dive into the details below to estimate storage, deployment, and data costs more precisely.
@@ -11908,21 +11905,28 @@ To ensure that your infrastructure usage is covered, you must maintain a minimum
You can top up your cycle balance in the Juno [console](https://console.juno.build/) through one of the following methods:
-* Using ICP from your wallet.
* Purchasing cycles with Stripe, thanks to our friends at [cycle.express](https://cycle.express).
+* Using cycles from your [wallet](/docs/miscellaneous/wallet.md).
* Transferring cycles between modules, such as moving cycles from one Satellite to another.
---
## Transaction costs
-New developers who join Juno are granted credits to create a Mission Control and their initial [satellite](/docs/terminology.md#satellite).
+New developers who join Juno are granted credits to create an initial [Satellite](/docs/terminology.md#satellite).
-To create additional Satellites, a fee of 0.4 ICP is necessary, along with the infrastructure costs for setting up the container.
+To create additional Satellites, a fee of 3 T Cycles is necessary, along with the infrastructure costs for setting up the container.
-Similarly, enabling analytics by creating an [orbiter](/docs/terminology.md#orbiter) entails a fee of 0.4 ICP.
+Similarly, enabling analytics by creating an [Orbiter](/docs/terminology.md#orbiter) or monitoring with a [Mission Control](/docs/terminology.md#mission-control) entails a fee of 3 T Cycles.
-Please note that additional transaction fees may be introduced in the future, and pricing and models are subject to change.
+Each module is provisioned with approximately 1.5 T Cycles in usable resources.
+
+**Note:**
+
+* For backwards compatibility, modules can still be created using Mission Control (deprecated). The transaction cost for this approach is 1.5 ICP.
+
+* Additional transaction fees may be introduced in the future, and pricing and models are subject to change.
+
---
@@ -11956,11 +11960,11 @@ It's important to note that subsequent deployments of your project can have sign
Querying data on the Internet Computer is currently free, so there are no additional costs to expect when reading data.
-In terms of persisting data, based on our experience, storing 100 instances of a JSON sample data with approximately 90 fields, totaling around 900 bytes, costs approximately 0.0005 TCycles or 0.00017 ICP ($0.000675). This means that the cost for a single transaction of this nature would be approximately 0.000005 TCycles or 0.0000017 ICP ($0.00000675).
+In terms of persisting data, based on our experience, storing 100 instances of a JSON sample data with approximately 90 fields, totaling around 900 bytes, costs approximately 0.0005 TCycles ($0.000675). This means that the cost for a single transaction of this nature would be approximately 0.000005 TCycles or 0.0000017 ICP ($0.00000675).
**Note:**
-Pricing information was last reviewed on Sept. 26, 2025.
+Pricing information was last reviewed on Jan. 7, 2026.
Figures are estimates and may change as the Internet Computer evolves.
@@ -11968,13 +11972,9 @@ Figures are estimates and may change as the Internet Computer evolves.
In Juno, we use some terms that may be unfamiliar to some. This page provides a summary of the most commonly used terms.
-## Account Identifier
-
-An "Account Identifier" is an address, serving as the textual representation of an account on the Internet Computer (ICP) ledger. It can represent an account owned by an individual or a smart contract.
-
## Canister
-A canister is the term for a smart contract on the Internet Computer. It includes both logic and state (memory), bundled together and deployed as a WebAssembly (WASM) container.
+A canister is the term for a container on the Internet Computer. It includes both logic and state (memory), bundled together and deployed as a WebAssembly (WASM).
All ([modules](#modules)) in Juno — such as ([satellites](#satellite)), ([mission controls](#mission-control)), and ([orbiters](#orbiter)) — are canisters under the hood.
@@ -11992,7 +11992,7 @@ For current usage and setup, refer to the [Access Keys documentation](/docs/misc
## Cycles
-Cycles are used to pay for [infrastructure](/docs/miscellaneous/infrastructure.md) usage. Your [mission control](/docs/terminology.md#mission-control) or [satellite](/docs/terminology.md#satellite) consumes cycles while it's active.
+Cycles are used to pay for [infrastructure](/docs/miscellaneous/infrastructure.md) usage. Your [satellite](/docs/terminology.md#satellite), [mission control](/docs/terminology.md#mission-control) or [orbiter](/docs/terminology.md#orbiter) consume cycles while they are active.
The amount of cycles available determines whether a module will be active, inactive, or eventually decommissioned (deleted).
@@ -12005,18 +12005,10 @@ Think of cycles like prepaid mobile data:
* To keep your modules running smoothly, you need to top up your cycles regularly (manually or automatically).
* If you don’t top it up, after some time, it will be decommissioned, similar to losing your prepaid number due to prolonged inactivity.
-Learn more about [computation and storage costs](https://internetcomputer.org/docs/current/developer-docs/gas-cost).
-
## Doc
"doc" is a commonly used shorthand in Juno for a "document of the Datastore". Wherever you see the term "doc" in the codebase or documentation, it refers specifically to a document entity managed by the [Datastore](/docs/build/datastore.md). This abbreviation is used for brevity and consistency throughout the project.
-## ICP
-
-The ICP token is the cryptocurrency used to pay for transactions on Juno's [infrastructure](/docs/miscellaneous/infrastructure.md).
-
-It can also be converted into cycles, which are used to pay for computation and storage. Unlike the market price of ICP, the price of cycles remains constant, ensuring predictable costs for infrastructure usage.
-
## Internet Identity
[Internet Identity](https://internetcomputer.org/internet-identity) is a decentralized authentication provider that offers a secure blockchain login experience with a user-friendly Web2 interface.
@@ -12071,15 +12063,17 @@ By picking the right group (or subnet), everyone can play faster and have more f
## Wallet
-A wallet is your secure repository for managing and storing crypto money. Your wallet is controlled exclusively by you, ensuring that no one, including Juno, can ever access it.
+A wallet is your secure repository for managing and storing resources in Juno.
+
+Think of it like a prepaid account:
-Think of it like a digital vault:
+* It holds your available resources (cycles).
+* It lets you allocate resources to your projects and modules - e.g. with top-up.
+* It's automatically created when you sign in to the Console.
-* It securely stores your ICP tokens.
-* It acts as your gateway for transactions within the Juno ecosystem.
-* It allows you to top up your modules with cycles.
+Your wallet is tied to your identity, which is generated when you first log in.
-Because your wallet is also your ([mission-control](#mission-control)), which requires resources to stay alive, we recommend holding a reasonable amount of tokens. Think of it like a day-to-day wallet for frequent operations rather than one for savings.
+For more information see [Wallet](/docs/miscellaneous/wallet.md) documentation.
# Troubleshooting
diff --git a/.llms-snapshots/llms.txt b/.llms-snapshots/llms.txt
index f3e574bb..0a2af9d1 100644
--- a/.llms-snapshots/llms.txt
+++ b/.llms-snapshots/llms.txt
@@ -158,7 +158,7 @@ Juno is your self-contained serverless platform for building full-stack web apps
- [Infrastructure](https://juno.build/docs/miscellaneous/infrastructure.md): Discover how Juno's infrastructure blends self-hosted deployment with WebAssembly containers, focusing on simplicity, control, and modern Web2-compatible tooling.
- [Memory](https://juno.build/docs/miscellaneous/memory.md): This page explains how memory works conceptually and how you can monitor its usage through the Console.
- [Provisioning Options](https://juno.build/docs/miscellaneous/provisioning-options.md): The creation wizard for Satellites and Orbiters includes advanced provisioning options for developers who need more control.
-- [Wallet](https://juno.build/docs/miscellaneous/wallet.md): This section provides guidance on managing your assets and cycles with your wallet, which are essential for maintaining and providing enough resources for your modules in the Juno ecosystem.
+- [Wallet](https://juno.build/docs/miscellaneous/wallet.md): This section provides guidance on managing your cycles with your wallet (your account), which are essential for maintaining and providing enough resources for your modules in the Juno ecosystem.
- [Workarounds](https://juno.build/docs/miscellaneous/workarounds.md): This page is dedicated to helping you make the most of Juno features, even when some functionalities are not yet fully supported out of the box. Below, you'll find practical workarounds and guidance for processes which in the future will be resolved by new features.
## Reference
diff --git a/docs/build/analytics/index.md b/docs/build/analytics/index.md
index fbcf5294..233d97f7 100644
--- a/docs/build/analytics/index.md
+++ b/docs/build/analytics/index.md
@@ -81,7 +81,7 @@ You have the capability to delete all collected data within your Analytics at an
## How does it work?
-To gather analytics for your dapps, you need to create a module called [orbiter]. Creating an Orbiter requires ICP, and its price is defined in the [transaction costs](../../pricing#transaction-costs).
+To gather analytics for your dapps, you need to create a module called [orbiter]. Creating an Orbiter requires Cycles, and its price is defined in the [transaction costs](../../pricing#transaction-costs).
Each Orbiter is used to collect analytics for one or multiple [satellites].
diff --git a/docs/components/cycles.md b/docs/components/cycles.md
new file mode 100644
index 00000000..eda2dd22
--- /dev/null
+++ b/docs/components/cycles.md
@@ -0,0 +1,10 @@
+The amount of cycles available determines whether a module will be active, inactive, or eventually decommissioned (deleted).
+
+This ensures that related costs cannot surpass the amount of cycles available.
+
+Think of cycles like prepaid mobile data:
+
+- Just like your mobile plan allows you to make calls and browse the internet, cycles enable your containers to process computations and store data.
+- When your data (cycles) runs out, your service becomes inactive.
+- To keep your modules running smoothly, you need to top up your cycles regularly (manually or automatically).
+- If you don’t top it up, after some time, it will be decommissioned, similar to losing your prepaid number due to prolonged inactivity.
diff --git a/docs/guides/local-development.mdx b/docs/guides/local-development.mdx
index fe9e7212..10e4a09c 100644
--- a/docs/guides/local-development.mdx
+++ b/docs/guides/local-development.mdx
@@ -29,7 +29,7 @@ This enables:
- A smooth dev loop, from prototype to deployment
- A unique way to build, debug, and validate smart contract logic and frontend behavior — all in one place
-
+
---
@@ -131,8 +131,8 @@ Likewise, not all services are mounted by default - but they can be turned on (o
| ICP Index | ✅ | ✅ |
| NNS Governance | ✅ | ➖ |
| Cycles Minting (CMC) | ✅ | ➖ |
-| Cycles Ledger | ➖ | ➖ |
-| Cycles Index | ➖ | ➖ |
+| Cycles Ledger | ✅ | ➖ |
+| Cycles Index | ✅ | ➖ |
| Registry | ➖ | ➖ |
| SNS | ➖ | ➖ |
| NNS-dapp | ➖ | ➖ |
@@ -214,16 +214,16 @@ await initSatellite({
The admin server running on port `5999` provides a variety of internal management. Below are some tips and example scripts to make use of this little server.
-### Get ICP
+### Get Cycles
-If you're using the full environment, the Console UI includes a "Get ICP" button in the wallet. It's a quick way to get ICP out of the box.
+If you're using the full environment, the Console UI includes a "Get Cycles" button in the wallet. It's a quick way to get Cycles out of the box.
-
+
-You might want to transfer some ICP from the ledger to a specified principal, which can be particularly useful when you're just getting started developing your app and no users currently own ICP. This can be achieved by querying:
+You might want to transfer some Cycles from the ledger to a specified principal, which can be particularly useful when you're just getting started developing your app and no users currently own Cycles. This can be achieved by querying:
```
-http://localhost:5999/ledger/transfer/?to=$PRINCIPAL
+http://localhost:5999/ledger/transfer/?to=$PRINCIPAL&ledgerId=um5iw-rqaaa-aaaaq-qaaba-cai&amount330000000000000
```
For example, you can use the following script:
diff --git a/docs/img/dev-console/login.png b/docs/img/dev-console/login.png
new file mode 100644
index 00000000..b1809853
Binary files /dev/null and b/docs/img/dev-console/login.png differ
diff --git a/docs/img/dev-console/login.webp b/docs/img/dev-console/login.webp
deleted file mode 100644
index 3cdf4d18..00000000
Binary files a/docs/img/dev-console/login.webp and /dev/null differ
diff --git a/docs/img/dev-console/wallet.png b/docs/img/dev-console/wallet.png
new file mode 100644
index 00000000..1227a2a2
Binary files /dev/null and b/docs/img/dev-console/wallet.png differ
diff --git a/docs/img/dev-console/wallet.webp b/docs/img/dev-console/wallet.webp
deleted file mode 100644
index 46122f7d..00000000
Binary files a/docs/img/dev-console/wallet.webp and /dev/null differ
diff --git a/docs/img/wallet/wallet-buy.png b/docs/img/wallet/wallet-buy.png
new file mode 100644
index 00000000..67574ebd
Binary files /dev/null and b/docs/img/wallet/wallet-buy.png differ
diff --git a/docs/img/wallet/wallet-id.png b/docs/img/wallet/wallet-id.png
deleted file mode 100644
index e89a95f8..00000000
Binary files a/docs/img/wallet/wallet-id.png and /dev/null differ
diff --git a/docs/img/wallet/wallet-receive-account-identifier-qrcode.png b/docs/img/wallet/wallet-receive-account-identifier-qrcode.png
deleted file mode 100644
index 2c9880b0..00000000
Binary files a/docs/img/wallet/wallet-receive-account-identifier-qrcode.png and /dev/null differ
diff --git a/docs/img/wallet/wallet-receive-account-identifier.png b/docs/img/wallet/wallet-receive-account-identifier.png
deleted file mode 100644
index f79196a4..00000000
Binary files a/docs/img/wallet/wallet-receive-account-identifier.png and /dev/null differ
diff --git a/docs/img/wallet/wallet-receive-oisy.png b/docs/img/wallet/wallet-receive-oisy.png
index 9f806137..d3538487 100644
Binary files a/docs/img/wallet/wallet-receive-oisy.png and b/docs/img/wallet/wallet-receive-oisy.png differ
diff --git a/docs/img/wallet/wallet-receive-wallet-id-qrcode.png b/docs/img/wallet/wallet-receive-wallet-id-qrcode.png
deleted file mode 100644
index a0c99d61..00000000
Binary files a/docs/img/wallet/wallet-receive-wallet-id-qrcode.png and /dev/null differ
diff --git a/docs/img/wallet/wallet-receive-wallet-id.png b/docs/img/wallet/wallet-receive-wallet-id.png
index 42da3d27..9c2920f9 100644
Binary files a/docs/img/wallet/wallet-receive-wallet-id.png and b/docs/img/wallet/wallet-receive-wallet-id.png differ
diff --git a/docs/img/wallet/wallet-receive.png b/docs/img/wallet/wallet-receive.png
index b5919caa..5ba19576 100644
Binary files a/docs/img/wallet/wallet-receive.png and b/docs/img/wallet/wallet-receive.png differ
diff --git a/docs/img/wallet/wallet-send-form.png b/docs/img/wallet/wallet-send-form.png
index 9a4f0baa..acef666b 100644
Binary files a/docs/img/wallet/wallet-send-form.png and b/docs/img/wallet/wallet-send-form.png differ
diff --git a/docs/img/wallet/wallet-send-review.png b/docs/img/wallet/wallet-send-review.png
index 3c41fb1a..d1010094 100644
Binary files a/docs/img/wallet/wallet-send-review.png and b/docs/img/wallet/wallet-send-review.png differ
diff --git a/docs/img/wallet/wallet-send.png b/docs/img/wallet/wallet-send.png
index 772a3b14..aeff88ed 100644
Binary files a/docs/img/wallet/wallet-send.png and b/docs/img/wallet/wallet-send.png differ
diff --git a/docs/management/monitoring.md b/docs/management/monitoring.md
index e6a27c03..0572e375 100644
--- a/docs/management/monitoring.md
+++ b/docs/management/monitoring.md
@@ -24,8 +24,8 @@ Keeping your modules running smoothly is essential for any application. The moni
- **Cycle refilling**: Monitored modules are automatically topped up when their balance falls below what's needed to stay active.
- **Self-Monitoring**: The monitoring monitors itself to maintain sufficient cycles, with full control remaining in your hands at all times.
-- **Automatic ICP Conversion**: Can mint new cycles from the ICP in your wallet, ensuring your modules stay adequately funded.
- **Hourly Checks**: The system evaluates balances once an hour.
+- **Automatic ICP Conversion**: Can mint new cycles from the ICP in your wallet, ensuring your modules stay adequately funded.
---
diff --git a/docs/miscellaneous/wallet.mdx b/docs/miscellaneous/wallet.mdx
index 0b3a9cd5..cecbdc81 100644
--- a/docs/miscellaneous/wallet.mdx
+++ b/docs/miscellaneous/wallet.mdx
@@ -1,90 +1,76 @@
# Wallet
-This section provides guidance on managing your assets and cycles with your [wallet](../terminology.mdx#wallet), which are essential for maintaining and providing enough resources for your modules in the Juno ecosystem.
+This section provides guidance on managing your cycles with your wallet (your account), which are essential for maintaining and providing enough resources for your modules in the Juno ecosystem.
:::important
-Just like your modules, your wallet is fully under your control — Juno cannot access, move, or recover the ICP or cycles held inside.
+Just like your modules, your wallet is under your control — Juno cannot access, move, or recover the cycles held inside.
-Because of this non-custodial model, there are no refunds, reversals, or recovery options. Always double-check destination addresses before sending funds.
+Because of this model, there are no refunds, reversals, or recovery options. Always double-check destination addresses before sending funds.
-As a best practice, we recommend not holding large amounts of ICP in your Juno wallet unless necessary. Use it as a utility wallet for fueling your modules — not as a long-term vault.
+As a best practice, we recommend not holding large amounts of cycles unless necessary. Use it as a utility for fueling your modules — not as a long-term vault.
-We also recommend enabling [monitoring](../management/monitoring.md) to ensure your Mission Control stays alive and responsive at all times.
+We also recommend enabling [monitoring](../management/monitoring.md) to ensure your projects and analytics stay alive and responsive at all times.
:::
---
-## What are ICP?
+## What are Cycles?
-ICP are the native cryptocurrency of the [Internet Computer](https://internetcomputer.org). They provide utility for powering the network and are also used for governance.
+Cycles are used to pay for infrastructure usage. Your Satellite, Mission Control or Orbiter consume cycles while they are active.
-One key usage is converting ICP tokens to cycles, which are used to cover the computational and storage costs of running modules.
+import Cycles from "../components/cycles.md";
----
-
-## Why do I need ICP?
-
-Given that Juno is built on top of the Internet Computer (see [architecture](architecture.md)), your modules require cycles to stay alive.
-
-While you don’t necessarily need ICP in the Juno ecosystem since you can acquire cycles with Stripe through [cycle.express](https://cycle.express), having some ICP can still be interesting.
-
-It provides independence by allowing you to top up your modules without relying on third-party services. Depending on how you obtain your tokens, using ICP can also help lower transaction costs and offers interoperability with other Internet Computer projects, making it a flexible and practical option.
+
---
-## Buying ICP
+## Buying Cycles
-To get ICP from the outside world into your wallet, you can use most cryptocurrency exchange platforms that allow you to buy ICP (refer to this [list](https://coinranking.com/fr/coin/aMNLwaUbY+internetcomputerdfinity-icp/exchanges) of major ones). These platforms let you convert dollars (or other currencies) into ICP. Keep in mind that exchanges charge a fee for this service.
+The easiest way to purchase cycles — and get the best deal — is through [Cycle.express](https://cycle.express), which lets you pay with a credit card via Stripe.
-Once you have obtained ICP on those platforms, you can initiate a transaction to send it to your wallet. For this purpose, you will need to provide a destination address where the ICP should be sent. This destination address corresponds to the [Account Identifier](../terminology.mdx#account-identifier) of your wallet.
+The service is integrated directly into the Juno Console. From your wallet, click "Buy" and follow the steps.
-You can locate the destination address in Juno's [console]. Once you've logged in, go to your [wallet](https://console.juno.build/wallet) and click "Receive".
+:::note
-
+The default purchase amount is $1 USD. You can change this amount on Stripe's payment page (maximum $100).
-Select "Account identifier".
-
-
-
-Either copy your account identifier or use the provided QR code. This is the address you should use to receive ICP from the outside world.
+:::
-
+
---
-## Receiving ICP
+## Receiving Cycles
-If you already hold ICP, you can transfer it from wallets within the ecosystem such as the [NNS dapp](https://nns.internetcomputer.org/), [OISY](https://oisy.com) or [others](https://internetcomputer.org/ecosystem?tag=Wallet).
+If you already hold cycles or want to swap some, you can use the [OISY Wallet](https://oisy.com).
-To initiate a transaction to send it to your wallet, you will need to provide a destination address, which in this case is your wallet ID.
+To initiate a transaction manually, you will need to provide a destination address. To find it in the [console], open the shortcut to your [wallet](https://console.juno.build/wallet) and click "Receive" select "Wallet ID".
-You can locate your wallet ID in Juno's [console]. Once you've logged in, go to your [wallet](https://console.juno.build/wallet), where the information is easy to find.
+
-
+
-If you wish to use a QR code, click "Receive" and select "Wallet ID".
+You can also connect OISY to Juno's console to initiate the transaction and proceed with the approval. This eliminates the need to copy, paste, or scan any addresses.
-
-
-Either copy your account identifier or use the provided QR code. This is the address you should use to transfer ICP within the ecosystem.
+
-
+---
-If you are using OISY, you can also connect this third-party wallet to Juno's console to initiate the transaction and proceed with the approval. This eliminates the need to copy, paste, or scan any addresses.
+## Send Cycles
-
+Sending Cycles to the ecosystem or the outside world can be initiated from your wallet in Juno's [console]. To start a transaction, click "Send".
----
+:::important
-## Send ICP
+Sending cycles transfers them to another wallet. To add manually cycles (resources) to your modules (Satellites, Orbiters, or Mission Control), use the **Top-up** feature instead.
-Sending ICP to the ecosystem or the outside world can be initiated from your wallet in Juno's [console]. To start a transaction, click "Send".
+:::
-Enter the destination wallet ID or account identifier where you want to send ICP, along with the amount.
+Enter the destination wallet ID or account identifier where you want to send cycles, along with the amount.
@@ -92,4 +78,12 @@ Review the transaction details and confirm to execute it.
+---
+
+## Legacy Support
+
+For backwards compatibility with Mission Control that operated in ICP, the wallet features still support those tokens. You can receive and send ICP if needed.
+
+However, using cycles is now the recommended approach for all operations.
+
[console]: https://console.juno.build
diff --git a/docs/pricing.md b/docs/pricing.md
index 71ca4ce4..be0e06a2 100644
--- a/docs/pricing.md
+++ b/docs/pricing.md
@@ -5,7 +5,6 @@ keywords:
Juno pricing,
operating costs,
transaction fees,
- ICP,
cycles,
infrastructure costs,
storage costs,
@@ -18,8 +17,8 @@ keywords:
Juno has a simple starting point:
-- ✅ Free to get started: new developers receive credits to create one managing container and one project container.
-- 💰 Pay as you grow: additional modules (for projects or analytics) cost 0.4 ICP each to create.
+- ✅ Free to get started: new developers receive credits to create a container for their first project, with initial resources included, ready to use.
+- 💰 Pay as you grow: additional modules (for projects, monitoring or analytics) cost 3 T Cycles each to create.
- 📦 Operating costs: ongoing costs for storage, compute, and deployments are paid with cycles.
From there, you can dive into the details below to estimate storage, deployment, and data costs more precisely.
@@ -34,21 +33,29 @@ To ensure that your infrastructure usage is covered, you must maintain a minimum
You can top up your cycle balance in the Juno [console](https://console.juno.build/) through one of the following methods:
-- Using ICP from your wallet.
- Purchasing cycles with Stripe, thanks to our friends at [cycle.express](https://cycle.express).
+- Using cycles from your [wallet](miscellaneous/wallet.mdx).
- Transferring cycles between modules, such as moving cycles from one Satellite to another.
---
## Transaction costs
-New developers who join Juno are granted credits to create a Mission Control and their initial [satellite].
+New developers who join Juno are granted credits to create an initial [Satellite].
-To create additional Satellites, a fee of 0.4 ICP is necessary, along with the infrastructure costs for setting up the container.
+To create additional Satellites, a fee of 3 T Cycles is necessary, along with the infrastructure costs for setting up the container.
-Similarly, enabling analytics by creating an [orbiter] entails a fee of 0.4 ICP.
+Similarly, enabling analytics by creating an [Orbiter] or monitoring with a [Mission Control] entails a fee of 3 T Cycles.
-Please note that additional transaction fees may be introduced in the future, and pricing and models are subject to change.
+Each module is provisioned with approximately 1.5 T Cycles in usable resources.
+
+:::note
+
+- For backwards compatibility, modules can still be created using Mission Control (deprecated). The transaction cost for this approach is 1.5 ICP.
+
+- Additional transaction fees may be introduced in the future, and pricing and models are subject to change.
+
+:::
---
@@ -84,11 +91,11 @@ It's important to note that subsequent deployments of your project can have sign
Querying data on the Internet Computer is currently free, so there are no additional costs to expect when reading data.
-In terms of persisting data, based on our experience, storing 100 instances of a JSON sample data with approximately 90 fields, totaling around 900 bytes, costs approximately 0.0005 TCycles or 0.00017 ICP ($0.000675). This means that the cost for a single transaction of this nature would be approximately 0.000005 TCycles or 0.0000017 ICP ($0.00000675).
+In terms of persisting data, based on our experience, storing 100 instances of a JSON sample data with approximately 90 fields, totaling around 900 bytes, costs approximately 0.0005 TCycles ($0.000675). This means that the cost for a single transaction of this nature would be approximately 0.000005 TCycles or 0.0000017 ICP ($0.00000675).
:::note
-Pricing information was last reviewed on Sept. 26, 2025.
+Pricing information was last reviewed on Jan. 7, 2026.
Figures are estimates and may change as the Internet Computer evolves.
diff --git a/docs/reference/configuration.mdx b/docs/reference/configuration.mdx
index e70c54e9..b83fb614 100644
--- a/docs/reference/configuration.mdx
+++ b/docs/reference/configuration.mdx
@@ -416,7 +416,7 @@ You can customize the ports exposed by the emulator:
| Field | Description | Default |
| ------- | -------------------------------------------------------------------------------- | ------- |
| server | The local Internet Computer replica port. Your app or project interacts with it. | `5987` |
-| admin | Admin server used for internal tasks (e.g., ICP transfer). | `5999` |
+| admin | Admin server used for internal tasks (e.g., Cycles transfer). | `5999` |
| console | Console UI port (only used with `skylab`). | `5866` |
:::note
diff --git a/docs/reference/emulator/infrastructure.md b/docs/reference/emulator/infrastructure.md
index a8ab4793..a8c6a4e3 100644
--- a/docs/reference/emulator/infrastructure.md
+++ b/docs/reference/emulator/infrastructure.md
@@ -7,12 +7,12 @@ However, in some cases, it may be useful to explicitly reference their IDs or UR
| Service | Canister ID |
| ------------------------------------------------------------------------------------------------------------ | ----------------------------- |
| [Internet Identity](https://dashboard.internetcomputer.org/canister/rdmx6-jaaaa-aaaaa-aaadq-cai) | `rdmx6-jaaaa-aaaaa-aaadq-cai` |
+| [Cycles Ledger](https://dashboard.internetcomputer.org/canister/um5iw-rqaaa-aaaaq-qaaba-cai) | `um5iw-rqaaa-aaaaq-qaaba-cai` |
+| [Cycles Index](https://dashboard.internetcomputer.org/canister/ul4oc-4iaaa-aaaaq-qaabq-cai) | `ul4oc-4iaaa-aaaaq-qaabq-cai` |
| [ICP Ledger](https://dashboard.internetcomputer.org/canister/ryjl3-tyaaa-aaaaa-aaaba-cai) | `ryjl3-tyaaa-aaaaa-aaaba-cai` |
| [ICP Index](https://dashboard.internetcomputer.org/canister/qhbym-qaaaa-aaaaa-aaafq-cai) | `qhbym-qaaaa-aaaaa-aaafq-cai` |
| [CMC (Cycles Minting Canister)](https://dashboard.internetcomputer.org/canister/rkp4c-7iaaa-aaaaa-aaaca-cai) | `rkp4c-7iaaa-aaaaa-aaaca-cai` |
| [NNS Governance](https://dashboard.internetcomputer.org/canister/rrkah-fqaaa-aaaaa-aaaaq-cai) | `rrkah-fqaaa-aaaaa-aaaaq-cai` |
| [Registry](https://dashboard.internetcomputer.org/canister/rwlgt-iiaaa-aaaaa-aaaaa-cai) | `rwlgt-iiaaa-aaaaa-aaaaa-cai` |
-| [Cycles Ledger](https://dashboard.internetcomputer.org/canister/um5iw-rqaaa-aaaaq-qaaba-cai) | `um5iw-rqaaa-aaaaq-qaaba-cai` |
-| [Cycles Index](https://dashboard.internetcomputer.org/canister/ul4oc-4iaaa-aaaaq-qaabq-cai) | `ul4oc-4iaaa-aaaaq-qaabq-cai` |
| [SNS-Wasm](https://dashboard.internetcomputer.org/canister/qaa6y-5yaaa-aaaaa-aaafa-cai) | `qaa6y-5yaaa-aaaaa-aaafa-cai` |
| [NNS-dapp](https://dashboard.internetcomputer.org/canister/qoctq-giaaa-aaaaa-aaaea-cai) | `qoctq-giaaa-aaaaa-aaaea-cai` |
diff --git a/docs/terminology.mdx b/docs/terminology.mdx
index f7af606d..1145a824 100644
--- a/docs/terminology.mdx
+++ b/docs/terminology.mdx
@@ -2,13 +2,9 @@
In Juno, we use some terms that may be unfamiliar to some. This page provides a summary of the most commonly used terms.
-## Account Identifier
-
-An "Account Identifier" is an address, serving as the textual representation of an account on the Internet Computer (ICP) ledger. It can represent an account owned by an individual or a smart contract.
-
## Canister
-A canister is the term for a smart contract on the Internet Computer. It includes both logic and state (memory), bundled together and deployed as a WebAssembly (WASM) container.
+A canister is the term for a container on the Internet Computer. It includes both logic and state (memory), bundled together and deployed as a WebAssembly (WASM).
All [modules](#modules) in Juno — such as [satellites](#satellite), [mission controls](#mission-control), and [orbiters](#orbiter) — are canisters under the hood.
@@ -26,31 +22,16 @@ For current usage and setup, refer to the [Access Keys documentation](miscellane
## Cycles
-Cycles are used to pay for [infrastructure] usage. Your [mission control] or [satellite] consumes cycles while it's active.
-
-The amount of cycles available determines whether a module will be active, inactive, or eventually decommissioned (deleted).
-
-This ensures that related costs cannot surpass the amount of cycles available.
-
-Think of cycles like prepaid mobile data:
+Cycles are used to pay for [infrastructure] usage. Your [satellite], [mission control] or [orbiter] consume cycles while they are active.
-- Just like your mobile plan allows you to make calls and browse the internet, cycles enable your containers to process computations and store data.
-- When your data (cycles) runs out, your service becomes inactive.
-- To keep your modules running smoothly, you need to top up your cycles regularly (manually or automatically).
-- If you don’t top it up, after some time, it will be decommissioned, similar to losing your prepaid number due to prolonged inactivity.
+import Cycles from "./components/cycles.md";
-Learn more about [computation and storage costs](https://internetcomputer.org/docs/current/developer-docs/gas-cost).
+
## Doc
"doc" is a commonly used shorthand in Juno for a "document of the Datastore". Wherever you see the term "doc" in the codebase or documentation, it refers specifically to a document entity managed by the [Datastore](build/datastore/index.mdx). This abbreviation is used for brevity and consistency throughout the project.
-## ICP
-
-The ICP token is the cryptocurrency used to pay for transactions on Juno's [infrastructure].
-
-It can also be converted into cycles, which are used to pay for computation and storage. Unlike the market price of ICP, the price of cycles remains constant, ensuring predictable costs for infrastructure usage.
-
## Internet Identity
[Internet Identity](https://internetcomputer.org/internet-identity) is a decentralized authentication provider that offers a secure blockchain login experience with a user-friendly Web2 interface.
@@ -105,19 +86,22 @@ By picking the right group (or subnet), everyone can play faster and have more f
## Wallet
-A wallet is your secure repository for managing and storing crypto money. Your wallet is controlled exclusively by you, ensuring that no one, including Juno, can ever access it.
+A wallet is your secure repository for managing and storing resources in Juno.
+
+Think of it like a prepaid account:
-Think of it like a digital vault:
+- It holds your available resources (cycles).
+- It lets you allocate resources to your projects and modules - e.g. with top-up.
+- It's automatically created when you sign in to the Console.
-- It securely stores your ICP tokens.
-- It acts as your gateway for transactions within the Juno ecosystem.
-- It allows you to top up your modules with cycles.
+Your wallet is tied to your identity, which is generated when you first log in.
-Because your wallet is also your [mission-control](#mission-control), which requires resources to stay alive, we recommend holding a reasonable amount of tokens. Think of it like a day-to-day wallet for frequent operations rather than one for savings.
+For more information see [Wallet](miscellaneous/wallet.mdx) documentation.
[console]: terminology.mdx#console
[satellite]: terminology.mdx#satellite
[satellites]: terminology.mdx#satellite
+[orbiter]: terminology.mdx#orbiter
[orbiters]: terminology.mdx#orbiter
[mission control]: terminology.mdx#mission-control
[mission controls]: terminology.mdx#mission-control