Merge branch 'main' into permissioned-signer

Author: gregnazario

.github/workflows/link-check.yml

@@ -47,6 +47,7 @@ jobs:
             --exclude '.*%7BmenuImage%7D.*'
             --exclude '.*imageUrl.*'
             --exclude '^(file:|[./]).*\/network\/faucet.mdx$'
+            --exclude '^https://x\.com/.*'
             --accept '403,401,429'
             --retry-wait-time 1
             --max-retries 2

README.md

@@ -64,30 +64,18 @@ pnpm install
 
 Ensure you have configured your `.env` properly under `apps/nextra/.env`. There is a `.env.example` there that you can duplicate and rename to `.env` for simplicity.
 
-To ensure you have the right setup, you can run:
-
-```sh
-pnpm prebuild
-```
-
 2. Build Nextra
 
 ```bash
-npx turbo run build --filter={apps/nextra}...
+pnpm run build
 ```
 
 This will build `apps/nextra` and all local packages it depends on.
 
-3. Navigate to the correct subdirectory
-
-```sh
-cd apps/nextra
-```
-
-4. Run the development server
+3. Run the development server
 
 ```sh
-pnpm dev
+pnpm run dev
 ```
 
 ## Debugging

apps/nextra/next.config.mjs

@@ -1090,22 +1090,42 @@ export default withBundleAnalyzer(
       },
       {
         source: "/tutorials/build-e2e-dapp/add-wallet-support",
-        destination: "/en/build/guides/build-e2e-dapp/3-add-wallet-support",
+        destination: "/en/build/guides/build-e2e-dapp/2-set-up-react-app",
+        permanent: true,
+      },
+      {
+        source: "/tutorials/build-e2e-dapp/3-add-wallet-support",
+        destination: "/en/build/guides/build-e2e-dapp/2-set-up-react-app",
         permanent: true,
       },
       {
         source: "/tutorials/build-e2e-dapp/fetch-data-from-chain",
-        destination: "/en/build/guides/build-e2e-dapp/4-fetch-data-from-chain",
+        destination: "/en/build/guides/build-e2e-dapp/3-fetch-data-from-chain",
+        permanent: true,
+      },
+      {
+        source: "/tutorials/build-e2e-dapp/4-fetch-data-from-chain",
+        destination: "/en/build/guides/build-e2e-dapp/3-fetch-data-from-chain",
         permanent: true,
       },
       {
         source: "/tutorials/build-e2e-dapp/submit-data-to-chain",
-        destination: "/en/build/guides/build-e2e-dapp/5-submit-data-to-chain",
+        destination: "/en/build/guides/build-e2e-dapp/4-submit-data-to-chain",
+        permanent: true,
+      },
+      {
+        source: "/tutorials/build-e2e-dapp/5-submit-data-to-chain",
+        destination: "/en/build/guides/build-e2e-dapp/4-submit-data-to-chain",
         permanent: true,
       },
       {
         source: "/tutorials/build-e2e-dapp/handle-tasks",
-        destination: "/en/build/guides/build-e2e-dapp/6-handle-tasks",
+        destination: "/en/build/guides/build-e2e-dapp/5-handle-tasks",
+        permanent: true,
+      },
+      {
+        source: "/tutorials/build-e2e-dapp/6-handle-tasks",
+        destination: "/en/build/guides/build-e2e-dapp/5-handle-tasks",
         permanent: true,
       },
       {

apps/nextra/pages/en/build/cli/running-a-local-network.mdx

@@ -96,7 +96,7 @@ called \`Result::unwrap()\` on an \`Err\` value: Os { code: 24, kind: Uncategori
 This means there were too many open files on your system. On many Unix systems you can increase the maximum number of open files by adding something like this to your `.zshrc`:
 
 ```bash filename="Terminal"
-ulimit -n 32768
+ulimit -n 1048576
 ```
 
 ### Docker is not available

apps/nextra/pages/en/build/guides/aptos-keyless/federated-keyless/_meta.tsx

@@ -5,6 +5,9 @@ export default {
   "integration-guide": {
     title: "Integration Guide",
   },
+  "simple-example": {
+    title: "Simple Example",
+  },
   other: {
     title: "FAQs",
   },

apps/nextra/pages/en/build/guides/aptos-keyless/federated-keyless/other.mdx

@@ -6,9 +6,9 @@ title: "FAQ"
 
 **What if I stop using my IAM for my application? What if I switch IAM providers?**
 
-- An account address depends on values of several variables that are specific to an IAM service, including `aud` (client ID) and `iss` (issuer).  If these values are changed, then a different address will be derived. 
-- If you want to switch IAM providers, you will need to develop an account migration flow, resulting in a key rotation from the account derived from the prior IAM provider to the account derived from the new IAM provider. 
-- We recommend allowing your users to add a secondary authentication method to their accounts (e.g., back-up private key) so that they can maintain access should the authentication path into their account via Federated Keyless be disrupted via a service provider change. In order to implement this, you need to do a key rotation to a multikey account. For relevant documentation see [key rotation](https://aptos.dev/en/build/guides/key-rotation) and [multikey SDK](https://aptos-labs.github.io/aptos-ts-sdk/@aptos-labs/ts-sdk-1.29.1/classes/MultiKeyAccount.html).
+- An account address depends on values of several variables that are specific to an IAM service, including `aud` (client ID) and `iss` (issuer).  If these values are changed, then a different address will be derived.
+- If you want to switch IAM providers, you will need to develop an account migration flow, resulting in a key rotation from the account derived from the prior IAM provider to the account derived from the new IAM provider.
+- We recommend allowing your users to add a secondary authentication method to their accounts (e.g., back-up private key) so that they can maintain access should the authentication path into their account via Federated Keyless be disrupted via a service provider change. In order to implement this, you need to do a key rotation to a multikey account. For relevant documentation see [key rotation](https://aptos.dev/en/build/guides/key-rotation) and [multikey SDK](https://aptos-labs.github.io/aptos-ts-sdk/@aptos-labs/ts-sdk-1.35.0/classes/MultiKeyAccount.html).
 
 **Does using an IAM cost money?**
 
@@ -20,4 +20,4 @@ title: "FAQ"
 
 **I use an open source IAM like Keycloak. Can I use Federated Keyless?**
 
-- Not today. Due to the trust placed in the IAM to have sufficient uptime and security standards, we have limited the accepted IAM set to the currently supported issuers. If you believe your provider should be included for consideration, please consider raising an AIP or contact us in the Keyless developers [telegram](https://t.me/+h5CN-W35yUFiYzkx). 
+- Not today. Due to the trust placed in the IAM to have sufficient uptime and security standards, we have limited the accepted IAM set to the currently supported issuers. If you believe your provider should be included for consideration, please consider raising an AIP or contact us in the Keyless developers [telegram](https://t.me/+h5CN-W35yUFiYzkx).

apps/nextra/pages/en/build/guides/aptos-keyless/federated-keyless/simple-example.mdx

@@ -0,0 +1,11 @@
+---
+title: "Federated Keyless Simple Example"
+---
+
+# Federated Keyless Simple Example
+
+The Federated Keyless Example shows how to set up a Federated Keyless account using Auth0 as the IAM provider.
+
+Explore the code in [aptos-keyless-example repository](https://github.com/aptos-labs/aptos-keyless-example/tree/main/examples/federated-keyless-example/).
+
+The Keyless Simple Example is currently undergoing maintenance. Please check back later.

apps/nextra/pages/en/build/guides/aptos-keyless/oidc-support.mdx

@@ -14,7 +14,6 @@ Aptos Keyless supports the following IdPs and IAM providers on our network(s). S
 | Apple             | No             | Live      | Live     | Live     |
 | Auth0             | Yes            | Live      | Live     | Live     |
 | Cognito           | Yes            | Live      | Live     | Live     |
-| Firebase          | Yes            | In review | -        | -        |
 | Microsoft         | No             | In review | -        | -        |
 | Github            | No             | In review | -        | -        |
 | Facebook          | No             | In review | -        | -        |

apps/nextra/pages/en/build/guides/aptos-keyless/simple-example.mdx

@@ -4,11 +4,11 @@ title: "Keyless Simple Example"
 
 # Keyless Simple Example
 
-Explore the code in [aptos-keyless-example repository](https://github.com/aptos-labs/aptos-keyless-example/).
+Explore the code in [aptos-keyless-example repository](https://github.com/aptos-labs/aptos-keyless-example/tree/main/examples/keyless-example/).
 
 The Keyless Simple Example is currently undergoing maintenance. Please check back later.
 
-This is a live Keyless example on CodeSandbox. Follow the instructions in the `README.md` to add your own Google `client_id`. Explore the code in [aptos-keyless-example repository](https://github.com/aptos-labs/aptos-keyless-example/).
+This is a live Keyless example on StackBlitz. Follow the instructions in the `README.md` to add your own Google `client_id`. Explore the code in [aptos-keyless-example repository](https://github.com/aptos-labs/aptos-keyless-example/tree/main/examples/keyless-example/).
 
 <br/>
 

apps/nextra/pages/en/build/guides/build-e2e-dapp.mdx

@@ -2,46 +2,49 @@
 
 A common way to learn a new framework or programming language is to build a simple todo list. In this tutorial, we will learn how to build an end-to-end todo list dapp, starting from the smart contract side through the front-end side and finally use of a wallet to interact with the two.
 
-See the completed code in the [my_first_dapp](https://github.com/aptos-labs/aptos-core/tree/main/aptos-move/move-examples/my_first_dapp).
+See the completed code in the [source-code](https://github.com/aptos-labs/developer-docs/tree/main/apps/nextra/pages/en/build/guides/build-e2e-dapp).
 
 ## Chapters
 
 After meeting the [prerequisites](#prerequisites) and [getting set up](#setup) as described below, you will follow this tutorial in this order:
 
 1. [Create a smart contract](build-e2e-dapp/1-create-smart-contract.mdx)
-2. [Set up React app](build-e2e-dapp/2-set-up-react-app.mdx)
-3. [Add Wallet support](build-e2e-dapp/3-add-wallet-support.mdx)
-4. [Fetch Data from Chain](build-e2e-dapp/4-fetch-data-from-chain.mdx)
-5. [Submit data to chain](build-e2e-dapp/5-submit-data-to-chain.mdx)
-6. [Handle Tasks](build-e2e-dapp/6-handle-tasks.mdx)
+2. [Set up a frontend](build-e2e-dapp/2-set-up-the-frontend.mdx)
+3. [Fetch Data from Chain](build-e2e-dapp/3-fetch-data-from-chain.mdx)
+4. [Submit data to chain](build-e2e-dapp/4-submit-data-to-chain.mdx)
+5. [Handle Tasks](build-e2e-dapp/5-handle-tasks.mdx)
 
 ## Prerequisites
 
 You must have:
 
-- [Aptos CLI](../cli.mdx)
-- [Aptos TypeScript SDK](../sdks/ts-sdk.mdx)
-- [Aptos Wallet Adapter](../sdks/wallet-adapter.mdx)
-- [Create React App](https://create-react-app.dev/)
 - [node and npm](https://nodejs.org/en/)
 
 Although we will explain some React decisions, we are not going to deep dive into how React works; so we assume you have some previous experience with React.
 
 ## Setup
 
-In this section, we will create a `my-first-dapp` directory to hold our project files, both client-side code (React based)and the Move code (our smart contract).
+In this section, we will create a `my-first-dapp` directory to hold our project files, both client-side code (React based) and the Move code (our smart contract).
+
+For that, we will be using [create-aptos-dapp](../create-aptos-dapp.mdx) to create the project.
 
 1. Open a terminal and navigate to the desired directory for the project (for example, the `Desktop` directory).
-2. Create a new directory called `my-first-dapp`, for example:
+2. Run `npx create-aptos-dapp@latest` to create the project.
 
 ```bash filename="Terminal"
-mkdir my-first-dapp
+npx create-aptos-dapp@latest
 ```
 
-3. Navigate into that directory:
+3. Follow the instructions to create the project.
+- Choose a name for the project, for example `my-first-dapp`.
+- Choose the `Full-stack project` option.
+- Choose the `Boilerplate Template` option.
+- For simplicity, choose not to use Surf.
+- Choose the `Vite app` framework option.
+- Choose the `Devnet` network option.
 
-```bash filename="Terminal"
-cd my-first-dapp
-```
+The tool will create the project in a directory with the same name as the project and install the required dependencies.
+
+Follow the `Next Steps` instructions.
 
 Now let's [create a smart contract](build-e2e-dapp/1-create-smart-contract.mdx).