diff --git a/docs/developer-docs/defi/dex/overview.mdx b/docs/developer-docs/defi/dex/overview.mdx
index 7f396784ba..3ac89097e9 100644
--- a/docs/developer-docs/defi/dex/overview.mdx
+++ b/docs/developer-docs/defi/dex/overview.mdx
@@ -26,7 +26,7 @@ Some examples of DEXs running on ICP include:
- [ICPSwap](https://icpswap.com/)
-- [ICDex](https://avjzx-pyaaa-aaaaj-aadmq-cai.raw.ic0.app/ICDex)
+- [ICDex](https://iclight.io/ICDex/DKP/ICP)
- [Sonic](https://sonic.ooo/)
diff --git a/docs/developer-docs/multi-chain/chain-key-tokens/ckbtc/overview.mdx b/docs/developer-docs/multi-chain/chain-key-tokens/ckbtc/overview.mdx
index 536142df99..c843dc0dfe 100644
--- a/docs/developer-docs/multi-chain/chain-key-tokens/ckbtc/overview.mdx
+++ b/docs/developer-docs/multi-chain/chain-key-tokens/ckbtc/overview.mdx
@@ -81,7 +81,7 @@ Learn more in the [Bitcoin integration technical overview](/docs/current/referen
## ckBTC production application examples
-- [ICDex](https://avjzx-pyaaa-aaaaj-aadmq-cai.raw.ic0.app/ICDex).
+- [ICDex](https://iclight.io/ICDex/DKP/ICP).
- [ICPSwap](https://icpswap.com/).
diff --git a/docs/developer-docs/multi-chain/chain-key-tokens/cketh/overview.mdx b/docs/developer-docs/multi-chain/chain-key-tokens/cketh/overview.mdx
index f63f138f99..ef465c0036 100644
--- a/docs/developer-docs/multi-chain/chain-key-tokens/cketh/overview.mdx
+++ b/docs/developer-docs/multi-chain/chain-key-tokens/cketh/overview.mdx
@@ -68,7 +68,7 @@ ckETH has many of the same use cases as ckBTC, such as:
## ckETH production application examples
-- [ICDex](https://avjzx-pyaaa-aaaaj-aadmq-cai.raw.ic0.app/ICDex).
+- [ICDex](https://iclight.io/ICDex/DKP/ICP).
- [ICPSwap](https://icpswap.com/).
diff --git a/docs/developer-docs/smart-contracts/advanced-features/https-outcalls/https-outcalls-get.mdx b/docs/developer-docs/smart-contracts/advanced-features/https-outcalls/https-outcalls-get.mdx
index b5265ab111..35877a0f31 100644
--- a/docs/developer-docs/smart-contracts/advanced-features/https-outcalls/https-outcalls-get.mdx
+++ b/docs/developer-docs/smart-contracts/advanced-features/https-outcalls/https-outcalls-get.mdx
@@ -719,9 +719,9 @@ Committing batch.
Deployed canisters.
URLs:
Frontend canister via browser
- send_http_get_motoko_frontend: https://ff5va-7qaaa-aaaap-qbona-cai.ic0.app/
+ send_http_get_motoko_frontend: https://ff5va-7qaaa-aaaap-qbona-cai.icp0.io/
Backend canister via Candid interface:
- send_http_get_motoko_backend: https://a4gq6-oaaaa-aaaab-qaa4q-cai.raw.ic0.app/?id=fm664-jyaaa-aaaap-qbomq-cai
+ send_http_get_motoko_backend: https://a4gq6-oaaaa-aaaab-qaa4q-cai.raw.icp0.io/?id=fm664-jyaaa-aaaap-qbomq-cai
```
@@ -740,12 +740,12 @@ Committing batch.
Deployed canisters.
URLs:
Frontend canister via browser
- send_http_get_rust_frontend: https://ff5va-7qaaa-aaaap-qbona-cai.ic0.app/
+ send_http_get_rust_frontend: https://ff5va-7qaaa-aaaap-qbona-cai.icp0.io/
Backend canister via Candid interface:
- send_http_get_rust_backend: https://a4gq6-oaaaa-aaaab-qaa4q-cai.raw.ic0.app/?id=fm664-jyaaa-aaaap-qbomq-cai
+ send_http_get_rust_backend: https://a4gq6-oaaaa-aaaab-qaa4q-cai.raw.icp0.io/?id=fm664-jyaaa-aaaap-qbomq-cai
```
-You can see play with the dapp's `get_icp_usd_exchange` method onchain here: [https://a4gq6-oaaaa-aaaab-qaa4q-cai.raw.ic0.app/?id=fm664-jyaaa-aaaap-qbomq-cai](https://a4gq6-oaaaa-aaaab-qaa4q-cai.raw.ic0.app/?id=fm664-jyaaa-aaaap-qbomq-cai).
+You can see play with the dapp's `get_icp_usd_exchange` method onchain here: [https://a4gq6-oaaaa-aaaab-qaa4q-cai.raw.icp0.io/?id=fm664-jyaaa-aaaap-qbomq-cai](https://a4gq6-oaaaa-aaaab-qaa4q-cai.raw.icp0.io/?id=fm664-jyaaa-aaaap-qbomq-cai).
diff --git a/docs/developer-docs/smart-contracts/advanced-features/https-outcalls/https-outcalls-post.mdx b/docs/developer-docs/smart-contracts/advanced-features/https-outcalls/https-outcalls-post.mdx
index fcfb962334..e750ab4f23 100644
--- a/docs/developer-docs/smart-contracts/advanced-features/https-outcalls/https-outcalls-post.mdx
+++ b/docs/developer-docs/smart-contracts/advanced-features/https-outcalls/https-outcalls-post.mdx
@@ -712,12 +712,12 @@ Committing batch.
Deployed canisters.
URLs:
Frontend canister via browser
- send_http_post_motoko_frontend: https://fx3cz-taaaa-aaaap-qbooa-cai.ic0.app/
+ send_http_post_motoko_frontend: https://fx3cz-taaaa-aaaap-qbooa-cai.icp0.io/
Backend canister via Candid interface:
- send_http_post_motoko_backend: https://a4gq6-oaaaa-aaaab-qaa4q-cai.raw.ic0.app/?id=fc4tu-siaaa-aaaap-qbonq-cai
+ send_http_post_motoko_backend: https://a4gq6-oaaaa-aaaab-qaa4q-cai.raw.icp0.io/?id=fc4tu-siaaa-aaaap-qbonq-cai
```
-You can see play with the dapp's `send_http_post_request` method onchain here: [https://a4gq6-oaaaa-aaaab-qaa4q-cai.raw.ic0.app/?id=fc4tu-siaaa-aaaap-qbonq-cai](https://a4gq6-oaaaa-aaaab-qaa4q-cai.raw.ic0.app/?id=fc4tu-siaaa-aaaap-qbonq-cai).
+You can see play with the dapp's `send_http_post_request` method onchain here: [https://a4gq6-oaaaa-aaaab-qaa4q-cai.raw.icp0.io/?id=fc4tu-siaaa-aaaap-qbonq-cai](https://a4gq6-oaaaa-aaaab-qaa4q-cai.raw.icp0.io/?id=fc4tu-siaaa-aaaap-qbonq-cai).
@@ -735,12 +735,13 @@ Committing batch.
Deployed canisters.
URLs:
Frontend canister via browser
- send_http_post_rust_frontend: https://f6yjf-fiaaa-aaaap-qbopq-cai.ic0.app/
+ send_http_post_rust_frontend: https://f6yjf-fiaaa-aaaap-qbopq-cai.icp0.io/
Backend canister via Candid interface:
- send_http_post_rust_backend: https://a4gq6-oaaaa-aaaab-qaa4q-cai.raw.ic0.app/?id=fzzpr-iqaaa-aaaap-qbopa-cai
+ send_http_post_rust_backend: https://a4gq6-oaaaa-aaaab-qaa4q-cai.raw.icp0.io/?id=fzzpr-iqaaa-aaaap-qbopa-cai
```
-You can see play with the dapp's `send_http_post_request` method onchain here: [https://a4gq6-oaaaa-aaaab-qaa4q-cai.raw.ic0.app/?id=fm664-jyaaa-aaaap-qbomq-cai](https://a4gq6-oaaaa-aaaab-qaa4q-cai.raw.ic0.app/?id=fm664-jyaaa-aaaap-qbomq-cai).
+You can see play with the dapp's `send_http_post_request` method onchain here: [https://a4gq6-oaaaa-aaaab-qaa4q-cai.raw.icp0.io/?id=fm664-jyaaa-aaaap-qbomq-cai](https://a4gq6-oaaaa-aaaab-qaa4q-cai.raw.icp0.io/?id=fm664-jyaaa-aaaap-qbomq-cai).
+
diff --git a/docs/developer-docs/smart-contracts/write/overview.mdx b/docs/developer-docs/smart-contracts/write/overview.mdx
index 2d3b20685f..89fefcf998 100644
--- a/docs/developer-docs/smart-contracts/write/overview.mdx
+++ b/docs/developer-docs/smart-contracts/write/overview.mdx
@@ -64,7 +64,7 @@ The typical development workflow of the frontend is:
1. The developer writes HTML, JS, CSS code.
1. The developer uses the default asset canister created by `dfx` or writes their own custom canister to store the web assets onchain.
-1. Users open the application in the browser by navigating to the URL `https://.ic0.app` or a custom domain that the developer has registered for the canister.
+1. Users open the application in the browser by navigating to the URL `https://.icp0.io` or a custom domain that the developer has registered for the canister.
1. The canister serves the web assets to the browser via its `http_request` endpoint that gets invoked for each HTTP request.
1. When the JS code runs in the browser, it can call the backend canister endpoints using the [agent-js](/docs/current/developer-docs/web-apps/browser-js/js-request-api) library, which is analogous to `web3.js` and `ethers.js` of Ethereum.
diff --git a/docs/developer-docs/web-apps/application-frontends/default-frontend.mdx b/docs/developer-docs/web-apps/application-frontends/default-frontend.mdx
index 4ba0636f3e..0a94b0b22d 100644
--- a/docs/developer-docs/web-apps/application-frontends/default-frontend.mdx
+++ b/docs/developer-docs/web-apps/application-frontends/default-frontend.mdx
@@ -33,9 +33,9 @@ Assets can come in many forms, such as:
When a dapp is deployed to ICP and has a frontend configured, the frontend assets will be displayed via a URL that contains the canister's ID. For local deployments, canisters are accessible through local URLs such as `http://127.0.0.1:4943/?canisterId=`. The port `4943` is the default local deployment port, though this can be changed via the `dfx` configuration or using a `dfx` flag. [Learn more about custom local networks](/docs/current/developer-docs/developer-tools/cli-tools/advanced-dfx/networks-json).
-For canisters deployed to the mainnet, the canister can be accessed in a web browser using the canister's ID followed by `.ic0.app` or `raw.ic0.app`. For example, the [playground](https://m7sm4-2iaaa-aaaab-qabra-cai.ic0.app/) is an application with a frontend user interface that can be used to deploy canisters in a temporary, sandbox environment. This dapp can be accessed via the URL `https://m7sm4-2iaaa-aaaab-qabra-cai.ic0.app/`.
+For canisters deployed to the mainnet, the canister can be accessed in a web browser using the canister's ID followed by `.ic0.app`, `.icp0.io` or `raw.icp0.io`. For example, the [playground](https://m7sm4-2iaaa-aaaab-qabra-cai.ic0.app/) is an application with a frontend user interface that can be used to deploy canisters in a temporary, sandbox environment. This dapp can be accessed via the URL `https://m7sm4-2iaaa-aaaab-qabra-cai.ic0.app/`.
-The `raw.ic0.app` domain is used for canisters deployed to the mainnet, and provides a way to access the raw HTTP interface of that canister. For local deployments that want to simulate the behavior of the `raw.ic0.app` domain, you must implement a method in your canister that consumes an HTTP request and outputs an HTTP response.
+The `raw.icp0.io` domain is used for canisters deployed to the mainnet, and provides a way to access the raw HTTP interface of that canister. For local deployments that want to simulate the behavior of the `raw.icp0.io` domain, you must implement a method in your canister that consumes an HTTP request and outputs an HTTP response.
By default, projects created with `dfx new` have the option to include a frontend canister that uses a template for one of several frontend frameworks. This guide illustrates using the default React template generated by `dfx new` and guides you through some basic modifications to customize the interface displayed.
@@ -300,7 +300,7 @@ Then, open a browser and navigate to `http://localhost:4943`.
To view the frontend on the mainnet, navigate to the frontend canister URL returned when you ran `dfx deploy`, such as:
```
-https://.ic0.app/
+https://.icp0.io/
```
- #### Step 2: Verify that you are prompted to type a name.
diff --git a/docs/developer-docs/web-apps/application-frontends/existing-frontend.mdx b/docs/developer-docs/web-apps/application-frontends/existing-frontend.mdx
index 32d061b106..a6d7febe6e 100644
--- a/docs/developer-docs/web-apps/application-frontends/existing-frontend.mdx
+++ b/docs/developer-docs/web-apps/application-frontends/existing-frontend.mdx
@@ -17,7 +17,7 @@ While numerous starter projects and examples exist for those who prefer to start
This guide provides an overview of how to deploy an existing Next.js application as a frontend canister.
:::caution
-Server methods such as `getServerSideProps` are not supported, since it will be deployed as a client-only application.
+Server methods such as `getServerSideProps` are not supported, since it will be deployed as a client-only application.
:::
## Next.js
@@ -117,7 +117,7 @@ dfx deploy --network ic
Deploying to the mainnet will cost [cycles](/docs/current/developer-docs/getting-started/cycles/overview).
:::
-After running either command, you will see a generated link that is now hosting your Next.js application. The local url will be in the format `http://127.0.0.1:4943/?canisterId=`, while the mainnet URL will be in the format `https://.ic0.app/`.
+After running either command, you will see a generated link that is now hosting your Next.js application. The local url will be in the format `http://127.0.0.1:4943/?canisterId=`, while the mainnet URL will be in the format `https://.icp0.io/`.
### Step 5: Navigate to the frontend canister to view the application
diff --git a/docs/developer-docs/web-apps/custom-domains/using-custom-domains.mdx b/docs/developer-docs/web-apps/custom-domains/using-custom-domains.mdx
index 148f736381..0935e24fa8 100644
--- a/docs/developer-docs/web-apps/custom-domains/using-custom-domains.mdx
+++ b/docs/developer-docs/web-apps/custom-domains/using-custom-domains.mdx
@@ -281,7 +281,7 @@ following troubleshooting steps:
You may need to specify a `host` in your frontend code when you are using a
custom domain, as the `HttpAgent` may not be able to automatically infer the
-host like it can on `icp0.io` and `ic0.app`. To configure your agent, it will
+host like it can on `icp0.io` and `icp0.io`. To configure your agent, it will
look something like this:
```ts
diff --git a/docs/tutorials/hackathon-prep-course/4-exploring-the-frontend.mdx b/docs/tutorials/hackathon-prep-course/4-exploring-the-frontend.mdx
index 1e2e202f17..ee79c07349 100644
--- a/docs/tutorials/hackathon-prep-course/4-exploring-the-frontend.mdx
+++ b/docs/tutorials/hackathon-prep-course/4-exploring-the-frontend.mdx
@@ -300,7 +300,7 @@ You can learn more about agents in the documentation [here](/docs/current/develo
### Serving HTTP content
-Canister smart contract are able to serve HTTP content natively, allowing for dapp frontends to be served directly in a web browser using the canister's URL at `http://.ic0.app` and `http://.raw.ic0.app`. Frontend canisters can be used to deliver HTML, CSS and JavaScript pages, and answer API requests.
+Canister smart contract are able to serve HTTP content natively, allowing for dapp frontends to be served directly in a web browser using the canister's URL at `http://.icp0.io` and `http://.raw.icp0.io`. Frontend canisters can be used to deliver HTML, CSS and JavaScript pages, and answer API requests.
If a canister wants to serve HTTP content, it should implement a method that consumes a HTTP request, which contains a URL, HTTP method and headers, then outputs a HTTP response that contains a status, headers and the response body. The canister method can return HTML, CSS and JavaScript content as part of the HTTP response.
diff --git a/submodules/internetidentity b/submodules/internetidentity
index c18f7bc83e..29f7f61ae3 160000
--- a/submodules/internetidentity
+++ b/submodules/internetidentity
@@ -1 +1 @@
-Subproject commit c18f7bc83e2f10b56717ca6014c6e99c9d705d6a
+Subproject commit 29f7f61ae375ab2a0250db9df3e94efff1ad23b7
diff --git a/submodules/motoko b/submodules/motoko
index 1219a50cc9..074ffca17f 160000
--- a/submodules/motoko
+++ b/submodules/motoko
@@ -1 +1 @@
-Subproject commit 1219a50cc957f6628a1dc27f10a26729a3f9ce10
+Subproject commit 074ffca17f95a3da876d8d0dda4d123cd5c16674
diff --git a/submodules/response-verfication b/submodules/response-verfication
index d4f6f6771a..58770d8ae3 160000
--- a/submodules/response-verfication
+++ b/submodules/response-verfication
@@ -1 +1 @@
-Subproject commit d4f6f6771a798f11bcc5f38b515b0418039cd88f
+Subproject commit 58770d8ae39b99bfa5bb5ddd341e422f76552839
diff --git a/submodules/samples b/submodules/samples
index 845c0be9c2..24aca5b979 160000
--- a/submodules/samples
+++ b/submodules/samples
@@ -1 +1 @@
-Subproject commit 845c0be9c2f4f0f56732b18d8138c4df77e27e1e
+Subproject commit 24aca5b979fd7f3690ee31890b466c19f45a027d
diff --git a/submodules/sdk b/submodules/sdk
index babc9db3bb..3e8757694c 160000
--- a/submodules/sdk
+++ b/submodules/sdk
@@ -1 +1 @@
-Subproject commit babc9db3bb5f79426454e3c3cc4c6e6a295fa518
+Subproject commit 3e8757694cc04e51069fbbdae256498830833033