From ad7d36043bb7766dba16f2389c54da4f63d13d07 Mon Sep 17 00:00:00 2001 From: Consensus Guy <49131718+consensuslayer@users.noreply.github.com> Date: Sat, 16 Aug 2025 12:45:55 +0300 Subject: [PATCH 01/15] Update overview.mdx --- abstract-global-wallet/agw-client/wallet-linking/overview.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/abstract-global-wallet/agw-client/wallet-linking/overview.mdx b/abstract-global-wallet/agw-client/wallet-linking/overview.mdx index 1dbeb94..ec0dafd 100644 --- a/abstract-global-wallet/agw-client/wallet-linking/overview.mdx +++ b/abstract-global-wallet/agw-client/wallet-linking/overview.mdx @@ -76,7 +76,7 @@ You can trigger this flow in your application by using the [linkToAgw](/abstract - Given an AGW address as input, returns a list of L1 wallets that have linked to the AGW. + Given an AGW address as input, returns a list of L1 wallets that have been linked to the AGW. Use this to check what EOAs have been linked to a specific AGW (can be multiple). ```solidity From 830e1bbbc78ce68cf1f6a36957cb2517e6101eb7 Mon Sep 17 00:00:00 2001 From: Consensus Guy <49131718+consensuslayer@users.noreply.github.com> Date: Sat, 16 Aug 2025 12:46:56 +0300 Subject: [PATCH 02/15] Update createAbstractClient.mdx --- abstract-global-wallet/agw-client/createAbstractClient.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/abstract-global-wallet/agw-client/createAbstractClient.mdx b/abstract-global-wallet/agw-client/createAbstractClient.mdx index 50bac0e..8cd9a6a 100644 --- a/abstract-global-wallet/agw-client/createAbstractClient.mdx +++ b/abstract-global-wallet/agw-client/createAbstractClient.mdx @@ -108,7 +108,7 @@ If set to `false`, the client will not support offchain CCIP lookups. The name of the client. - Frequency (in ms) for polling enabled actions & events. Defaults to `4000` milliseconds. + Frequency (in ms) for polling-enabled actions & events. Defaults to `4000` milliseconds. Request function wrapped with friendly error handling. From 8a6cbb70b69cd1add0ef777a0390bfb1d9cdbc9a Mon Sep 17 00:00:00 2001 From: Consensus Guy <49131718+consensuslayer@users.noreply.github.com> Date: Sat, 16 Aug 2025 12:50:43 +0300 Subject: [PATCH 03/15] Update useGlobalWalletSignerClient.mdx --- .../agw-react/hooks/useGlobalWalletSignerClient.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/abstract-global-wallet/agw-react/hooks/useGlobalWalletSignerClient.mdx b/abstract-global-wallet/agw-react/hooks/useGlobalWalletSignerClient.mdx index 25cea99..61475b0 100644 --- a/abstract-global-wallet/agw-react/hooks/useGlobalWalletSignerClient.mdx +++ b/abstract-global-wallet/agw-react/hooks/useGlobalWalletSignerClient.mdx @@ -5,7 +5,7 @@ description: Hook to get a wallet client instance of the approved signer of the import TanStackQueryReturnTypeSnippet from "/snippets/tanstack-query-return-type.mdx"; -Use the `useGlobalWalletSignerClient` hook to get a [wallet client](https://viem.sh/docs/clients/wallet) +Use the `useGlobalWalletSignerClient` hook to get an [wallet client](https://viem.sh/docs/clients/wallet) instance that can perform actions from the underlying [EOA](https://ethereum.org/en/developers/docs/accounts/#types-of-account) approved to sign transactions for the Abstract Global Wallet smart contract. From e5234ffaf623188cff5ded3018057828f6e5de73 Mon Sep 17 00:00:00 2001 From: Consensus Guy <49131718+consensuslayer@users.noreply.github.com> Date: Sat, 16 Aug 2025 12:52:50 +0300 Subject: [PATCH 04/15] Update useWriteContractSponsored.mdx --- .../agw-react/hooks/useWriteContractSponsored.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/abstract-global-wallet/agw-react/hooks/useWriteContractSponsored.mdx b/abstract-global-wallet/agw-react/hooks/useWriteContractSponsored.mdx index afadaa9..7776bb4 100644 --- a/abstract-global-wallet/agw-react/hooks/useWriteContractSponsored.mdx +++ b/abstract-global-wallet/agw-react/hooks/useWriteContractSponsored.mdx @@ -75,7 +75,7 @@ Returns a `UseWriteContractSponsoredReturnType`. - The error if the transaction failed. + The error occurs if the transaction failed. From 77ef66a9b9965e6b62ce9f193a732801d0224f2b Mon Sep 17 00:00:00 2001 From: Consensus Guy <49131718+consensuslayer@users.noreply.github.com> Date: Sat, 16 Aug 2025 13:30:56 +0300 Subject: [PATCH 05/15] Update going-to-production.mdx --- abstract-global-wallet/session-keys/going-to-production.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/abstract-global-wallet/session-keys/going-to-production.mdx b/abstract-global-wallet/session-keys/going-to-production.mdx index 3defe74..d917d7a 100644 --- a/abstract-global-wallet/session-keys/going-to-production.mdx +++ b/abstract-global-wallet/session-keys/going-to-production.mdx @@ -48,7 +48,7 @@ or will be rejected with "Unconstrained token approval/transfer destination in c Session keys specify a **signer** account; an EOA that is permitted to perform the actions specified in the session configuration. Therefore, the private key of the signer(s) you create are **SENSITIVE VALUES**! -Exposing the signer private key enables attackers to execute any of the actions specified in a session configuration for any AGW that has approved a session key with that signer’s address. +Exposing the signer's private key enables attackers to execute any of the actions specified in a session configuration for any AGW that has approved a session key with that signer’s address. ```typescript await agwClient.createSession({ From c911b9ce93fb8e58bf550b6c04f72afeeb7d0065 Mon Sep 17 00:00:00 2001 From: Consensus Guy <49131718+consensuslayer@users.noreply.github.com> Date: Sat, 16 Aug 2025 13:31:17 +0300 Subject: [PATCH 06/15] Update architecture.mdx --- abstract-global-wallet/architecture.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/abstract-global-wallet/architecture.mdx b/abstract-global-wallet/architecture.mdx index d631452..cc7a0d1 100644 --- a/abstract-global-wallet/architecture.mdx +++ b/abstract-global-wallet/architecture.mdx @@ -5,7 +5,7 @@ description: "Learn more about how Abstract Global Wallet works under the hood." Abstract Global Wallet makes use of [native account abstraction](/how-abstract-works/native-account-abstraction), by creating [smart contract wallets](/how-abstract-works/native-account-abstraction/smart-contract-wallets) -for users that have more security and flexibility than traditional EOAs. +for users who have more security and flexibility than traditional EOAs. Users can connect their Abstract Global Wallet to an application by logging in with their email, social account, or existing wallet. Once connected, applications can begin prompting users to approve transactions, which are executed from the From 1311c40132d632ee45b24b1d467c0cf1119bb733 Mon Sep 17 00:00:00 2001 From: Consensus Guy <49131718+consensuslayer@users.noreply.github.com> Date: Sat, 16 Aug 2025 13:32:14 +0300 Subject: [PATCH 07/15] Update abstract-json-rpc-api.mdx --- api-reference/overview/abstract-json-rpc-api.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/api-reference/overview/abstract-json-rpc-api.mdx b/api-reference/overview/abstract-json-rpc-api.mdx index a99cad4..cdb0b36 100644 --- a/api-reference/overview/abstract-json-rpc-api.mdx +++ b/api-reference/overview/abstract-json-rpc-api.mdx @@ -5,7 +5,7 @@ description: "View the full reference for the Abstract JSON-RPC API." --- Information about the state of Abstract such as the chain ID, block number, status of transactions and state changing operations -such as submitting transactions are executed via Abstract’s JSON RPC API. +such as submitting transactions that are executed via Abstract’s JSON RPC API. The JSON RPC API has 4 namespaces: | Namespace | Description | Example | From d4b01a6d950903403733ce05e5615b9e14cf6ec9 Mon Sep 17 00:00:00 2001 From: Consensus Guy <49131718+consensuslayer@users.noreply.github.com> Date: Sat, 16 Aug 2025 13:32:41 +0300 Subject: [PATCH 08/15] Update ethers.mdx --- build-on-abstract/applications/ethers.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/build-on-abstract/applications/ethers.mdx b/build-on-abstract/applications/ethers.mdx index 1939f69..b2f0322 100644 --- a/build-on-abstract/applications/ethers.mdx +++ b/build-on-abstract/applications/ethers.mdx @@ -14,7 +14,7 @@ alongside [ethers](https://docs.ethers.io/v6/). ## 1. Create a new project -Create a new directory and change directory into it. +Create a new directory and change the directory into it. ```bash mkdir my-abstract-app && cd my-abstract-app From 4973dee836b0e6c4fa52fdd20ccee8101a3f7a6b Mon Sep 17 00:00:00 2001 From: Consensus Guy <49131718+consensuslayer@users.noreply.github.com> Date: Sat, 16 Aug 2025 13:35:51 +0300 Subject: [PATCH 09/15] Update get-started.mdx --- build-on-abstract/smart-contracts/foundry/get-started.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/build-on-abstract/smart-contracts/foundry/get-started.mdx b/build-on-abstract/smart-contracts/foundry/get-started.mdx index e5aa997..d3aa20b 100644 --- a/build-on-abstract/smart-contracts/foundry/get-started.mdx +++ b/build-on-abstract/smart-contracts/foundry/get-started.mdx @@ -79,7 +79,7 @@ You may need to restart your terminal session after installation to continue. ## 2. Create a new project -Create a new project with `forge` and change directory into the project. +Create a new project with `forge` and change the directory into the project. ```bash forge init my-abstract-project && cd my-abstract-project From b7f16bc74b8d627c16b1156f21822e7e74c3f05a Mon Sep 17 00:00:00 2001 From: Consensus Guy <49131718+consensuslayer@users.noreply.github.com> Date: Sat, 16 Aug 2025 13:36:06 +0300 Subject: [PATCH 10/15] Update installation.mdx --- build-on-abstract/smart-contracts/foundry/installation.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/build-on-abstract/smart-contracts/foundry/installation.mdx b/build-on-abstract/smart-contracts/foundry/installation.mdx index bc00082..622bf61 100644 --- a/build-on-abstract/smart-contracts/foundry/installation.mdx +++ b/build-on-abstract/smart-contracts/foundry/installation.mdx @@ -69,7 +69,7 @@ You may need to restart your terminal session after installation to continue. - Create a new project with `forge` and change directory into the project. + Create a new project with `forge` and change the directory into the project. ```bash forge init my-abstract-project && cd my-abstract-project From ec637cdcfc3b2ed7c92618dce013ccab6c6d9cf5 Mon Sep 17 00:00:00 2001 From: Consensus Guy <49131718+consensuslayer@users.noreply.github.com> Date: Sat, 16 Aug 2025 13:38:02 +0300 Subject: [PATCH 11/15] Update testing-contracts.mdx --- build-on-abstract/smart-contracts/foundry/testing-contracts.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/build-on-abstract/smart-contracts/foundry/testing-contracts.mdx b/build-on-abstract/smart-contracts/foundry/testing-contracts.mdx index 49809b2..0d31a60 100644 --- a/build-on-abstract/smart-contracts/foundry/testing-contracts.mdx +++ b/build-on-abstract/smart-contracts/foundry/testing-contracts.mdx @@ -78,7 +78,7 @@ contract HelloWorld { href="https://getfoundry.sh/reference/cheatcodes/overview" > -Reference for all cheatcodes available in Foundry. +Reference for all cheat codes available in Foundry. From d5dfc1e671528d470c15fca954ffc4deb397de3b Mon Sep 17 00:00:00 2001 From: Consensus Guy <49131718+consensuslayer@users.noreply.github.com> Date: Sat, 16 Aug 2025 13:39:23 +0300 Subject: [PATCH 12/15] Update deploying-contracts.mdx --- .../smart-contracts/hardhat/deploying-contracts.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/build-on-abstract/smart-contracts/hardhat/deploying-contracts.mdx b/build-on-abstract/smart-contracts/hardhat/deploying-contracts.mdx index e3eab65..2af90df 100644 --- a/build-on-abstract/smart-contracts/hardhat/deploying-contracts.mdx +++ b/build-on-abstract/smart-contracts/hardhat/deploying-contracts.mdx @@ -159,7 +159,7 @@ export default async function (hre: HardhatRuntimeEnvironment) { ## Create2 & Smart Wallet Deployments -Specify different deployment types through using the third `deploymentType` parameter: +Specify different deployment types by using the third `deploymentType` parameter: - **create**: Standard contract deployment (default) - **create2**: Deterministic deployment using CREATE2 From 1f585600b7330adab4e78492a5dc852f5528a154 Mon Sep 17 00:00:00 2001 From: Consensus Guy <49131718+consensuslayer@users.noreply.github.com> Date: Sat, 16 Aug 2025 13:42:44 +0300 Subject: [PATCH 13/15] Update layer-2s.mdx --- how-abstract-works/architecture/layer-2s.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/how-abstract-works/architecture/layer-2s.mdx b/how-abstract-works/architecture/layer-2s.mdx index 851cf1d..9a3e6d0 100644 --- a/how-abstract-works/architecture/layer-2s.mdx +++ b/how-abstract-works/architecture/layer-2s.mdx @@ -52,7 +52,7 @@ without having to re-execute the transactions on Ethereum. ## What is the ZK Stack? Abstract uses the [ZK stack](https://zkstack.io/components); -an open-source framework for building sovereign ZK rollups. +An open-source framework for building sovereign ZK rollups. Date: Sat, 16 Aug 2025 13:50:33 +0300 Subject: [PATCH 14/15] Update contract-deployment.mdx --- how-abstract-works/evm-differences/contract-deployment.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/how-abstract-works/evm-differences/contract-deployment.mdx b/how-abstract-works/evm-differences/contract-deployment.mdx index a8ee986..2ac8aac 100644 --- a/how-abstract-works/evm-differences/contract-deployment.mdx +++ b/how-abstract-works/evm-differences/contract-deployment.mdx @@ -4,7 +4,7 @@ description: "Learn how to deploy smart contracts on Abstract." --- Unlike Ethereum, Abstract does not store the bytecode of smart contracts directly; -instead, it stores a hash of the bytecode and publishes the bytecode itself to Ethereum. +Instead, it stores a hash of the bytecode and publishes the bytecode itself to Ethereum. This adds several benefits to smart contract deployments on Abstract, including: From 4cc00f2bc49b43cd7dadc49c072d7b784d08f1fd Mon Sep 17 00:00:00 2001 From: Consensus Guy <49131718+consensuslayer@users.noreply.github.com> Date: Sat, 16 Aug 2025 14:00:17 +0300 Subject: [PATCH 15/15] Update evm-opcodes.mdx --- how-abstract-works/evm-differences/evm-opcodes.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/how-abstract-works/evm-differences/evm-opcodes.mdx b/how-abstract-works/evm-differences/evm-opcodes.mdx index 029f44b..a076a96 100644 --- a/how-abstract-works/evm-differences/evm-opcodes.mdx +++ b/how-abstract-works/evm-differences/evm-opcodes.mdx @@ -41,7 +41,7 @@ For this reason: ### Address Derivation The addresses of smart contracts deployed using `create` and `create2` will be different on Abstract -than Ethereum as they use different bytecode. This means the same bytecode deployed on Ethereum +than on Ethereum as they use different bytecode. This means the same bytecode deployed on Ethereum will have a different contract address on Abstract.