From 67e96af97fa8b0e81888c673612b39c587c872ef Mon Sep 17 00:00:00 2001 From: Marlene Marz <42071757+JanetMo@users.noreply.github.com> Date: Mon, 5 Feb 2024 17:27:00 +0100 Subject: [PATCH] fix typos / broken links (#302) --- .../guides/deploy-smart-contracts.mdx | 2 +- .../guides/deploy-with-foundry.md | 6 +++--- .../guides/deploy-with-remix.md | 8 ++++---- .../guides/deploy-with-thirdweb.md | 4 ++-- .../blockchain-providers.md | 16 ++++++++-------- .../connecting-with-a-provider.md | 4 ++-- .../debugging-with-hardhat-sbs.md | 8 ++++---- .../hardhat-test-coverage-sbs.md | 2 +- apps/base-docs/docs/tokens.md | 4 ++-- .../docs/tools/account-abstraction.md | 4 ++-- apps/base-docs/docs/tools/block-explorers.md | 2 +- apps/base-docs/docs/tools/bridge-faq.md | 18 +++++++++--------- apps/base-docs/docs/tools/cross-chain.md | 10 +++++----- apps/base-docs/docs/tools/data-indexers.md | 6 +++--- apps/base-docs/docs/tools/network-faucets.md | 2 +- apps/base-docs/docs/tools/node-providers.md | 8 ++++---- apps/base-docs/docs/tools/onboarding.md | 4 ++-- apps/base-docs/docs/tools/onramps.md | 2 +- apps/base-docs/docs/tools/viem.md | 2 +- 19 files changed, 56 insertions(+), 56 deletions(-) diff --git a/apps/base-docs/docs/building-with-base/guides/deploy-smart-contracts.mdx b/apps/base-docs/docs/building-with-base/guides/deploy-smart-contracts.mdx index 01a2112ef9..386703bfee 100644 --- a/apps/base-docs/docs/building-with-base/guides/deploy-smart-contracts.mdx +++ b/apps/base-docs/docs/building-with-base/guides/deploy-smart-contracts.mdx @@ -20,7 +20,7 @@ Hardhat is a developer tool that provides a simple way to deploy, test, and debu ## Objectives -By the end of this guide you should be able to do the following: +By the end of this guide, you should be able to do the following: - Setup Hardhat for Base - Create an NFT smart contract for Base diff --git a/apps/base-docs/docs/building-with-base/guides/deploy-with-foundry.md b/apps/base-docs/docs/building-with-base/guides/deploy-with-foundry.md index aa90e86ffd..580fbc6d05 100644 --- a/apps/base-docs/docs/building-with-base/guides/deploy-with-foundry.md +++ b/apps/base-docs/docs/building-with-base/guides/deploy-with-foundry.md @@ -11,10 +11,10 @@ keywords: ["Foundry", "smart contract", "ERC-721", "Base", "Base test network", This article will provide an overview of the [Foundry](https://book.getfoundry.sh/) development toolchain, and show you how to deploy a contract to **Base Sepolia** testnet. -Foundry is a powerful suite of tools to develop, test, and debug your smart contracts. It is comprised of several individual tools: +Foundry is a powerful suite of tools to develop, test, and debug your smart contracts. It comprises several individual tools: - `forge`: the main workhorse of Foundry — for developing, testing, compiling, and deploying smart contracts -- `cast`: a command-line tool for performing Ethereum RPC calls (e.g. interacting with contracts, sending transactions, and getting onchain data) +- `cast`: a command-line tool for performing Ethereum RPC calls (e.g., interacting with contracts, sending transactions, and getting onchain data) - `anvil`: a local testnet node, for testing contract behavior from a frontend or over RPC - `chisel`: a Solidity [REPL](https://en.wikipedia.org/wiki/Read%E2%80%93eval%E2%80%93print_loop), for trying out Solidity snippets on a local or forked network @@ -30,7 +30,7 @@ For production / mainnet deployments the steps below in this guide will be almos ## Objectives -By the end of this guide you should be able to do the following: +By the end of this guide, you should be able to do the following: - Setup Foundry for Base - Create an NFT smart contract for Base diff --git a/apps/base-docs/docs/building-with-base/guides/deploy-with-remix.md b/apps/base-docs/docs/building-with-base/guides/deploy-with-remix.md index ebc58abd3f..c74e069887 100644 --- a/apps/base-docs/docs/building-with-base/guides/deploy-with-remix.md +++ b/apps/base-docs/docs/building-with-base/guides/deploy-with-remix.md @@ -26,7 +26,7 @@ If you're already familiar with Remix, you probably want to jump down to [here]. ## Objectives -By the end of this lesson you should be able to: +By the end of this lesson, you should be able to: - List the features, pros, and cons of using Remix as an IDE - Deploy and test the Storage.sol demo contract in Remix @@ -44,7 +44,7 @@ The editor pane loads with the Remix home screen, which contains news, helpful l ![Remix Editor](../../../assets/images/deployment-with-remix/editor-pane.png) -You'll edit your code in the editor pane. It also has most of the features you're expecting, such as syntax and error highlighting. Note that in Remix, errors are not underlines. Instead, you'll see an❗to the left of the line number where the error is present. +You'll edit your code in the editor pane. It also has most of the features you're expecting, such as syntax and error highlighting. Note that in Remix, errors are not underlined. Instead, you'll see an❗to the left of the line number where the error is present. At the top, you'll see a big green arrow similar to the _Run_ button in other editors. In Solidity, this compiles your code, but it does not run it because you must first deploy your code to the simulated blockchain. @@ -64,7 +64,7 @@ As with many other editors, the left panel in Remix has a number of vertical tab ## Plugins -Most of the features in Remix are plugins and the ones you'll use the most are active by default. You can view and manage plugins by clicking the plug button in the lower-left corner, right above the settings gear. You can turn them off and on by clicking activate/deactivate, and some, such as the _Debug_ plugin will be automatically activated through other parts of the editor. +Most of the features in Remix are plugins, and the ones you'll use the most are active by default. You can view and manage plugins by clicking the plug button in the lower-left corner, right above the settings gear. You can turn them off and on by clicking activate/deactivate, and some, such as the _Debug_ plugin will be automatically activated through other parts of the editor. ### Solidity Compiler @@ -72,7 +72,7 @@ The first default plugin (after the search function) is the _Solidity Compiler_. The `Compile and Run script` button in this plugin is a little misleading. This is **not** how you will usually run your contract through testing. You can click the `I` button for more information on this feature. -Finally, if you have errors in your contracts, the complete text for each error will appear at the bottom of the pane. Try it out by introducing some typos to `1_Storage.sol`. +Finally, if you have errors in your contracts, the complete text for each error will appear at the bottom of the page. Try it out by introducing some typos to `1_Storage.sol`. ### Deploy & Run Transactions diff --git a/apps/base-docs/docs/building-with-base/guides/deploy-with-thirdweb.md b/apps/base-docs/docs/building-with-base/guides/deploy-with-thirdweb.md index 53ec00425d..e65ae56dff 100644 --- a/apps/base-docs/docs/building-with-base/guides/deploy-with-thirdweb.md +++ b/apps/base-docs/docs/building-with-base/guides/deploy-with-thirdweb.md @@ -35,7 +35,7 @@ In this guide, we'll give you an overview of using the [thirdweb CLI](https://po ## Objectives -By the end of this lesson you should be able to: +By the end of this lesson, you should be able to: - Create a project with a smart contract using thirdweb - Deploy smart contracts using thirdweb @@ -138,7 +138,7 @@ For production / mainnet deployments select `Base` (mainnet) as the network rath ::: -Once your contract is deployed, you'll be redirected to a [dashboard](https://portal.thirdweb.com/dashboard) for managing your contract. +Once your contract is deployed, you'll be redirected to a [dashboard](https://thirdweb.com/dashboard) for managing your contract. --- diff --git a/apps/base-docs/docs/connecting-to-the-blockchain/blockchain-providers.md b/apps/base-docs/docs/connecting-to-the-blockchain/blockchain-providers.md index b3a2e1d247..35c3749776 100644 --- a/apps/base-docs/docs/connecting-to-the-blockchain/blockchain-providers.md +++ b/apps/base-docs/docs/connecting-to-the-blockchain/blockchain-providers.md @@ -21,13 +21,13 @@ keywords: hide_table_of_contents: false --- -Onchain apps need frontends, sometimes called dApps, to enable your users to interact with your smart contracts. A _provider_ makes the connection from frontend to blockchain, and is used to read data and send transactions. +Onchain apps need frontends, sometimes called dApps, to enable your users to interact with your smart contracts. A _provider_ makes the connection from frontend to the blockchain, and is used to read data and send transactions. --- ## Objectives -By the end of this guide you should be able to: +By the end of this guide, you should be able to: - Compare and contrast public providers vs. vendor providers vs. wallet providers - Select the appropriate provider for several use cases @@ -40,13 +40,13 @@ In blockchain development, the term _provider_ describes a company or service th These services enable interacting with smart contracts without the developer needing to run and maintain their own blockchain node. Running a node is expensive, complicated, and challenging. In most cases, you'll want to start out with a provider. Once you start to get traction, you can evaluate the need to [run your own node], or switch to a more advanced architecture solution, such as utilizing [Subgraph]. -Figuring out which type of provider to use can be a little confusing at first. As with everything blockchain, the landscape changes rapidly and search results often return out-of-date information. +Figuring out which type of provider to use can be a little confusing at first. As with everything blockchain, the landscape changes rapidly, and search results often return out-of-date information. :::info New onchain devs sometimes get the impression that there are free options for connecting their apps to the blockchain. Unfortunately, this is not really true. Blockchain data is still 1's and 0's, fetched by computation and served to the internet via servers. -It costs money to run these and you will eventually need to pay for the service. +It costs money to run these, and you will eventually need to pay for the service. ::: @@ -54,7 +54,7 @@ You'll encounter providers divided into three general categories: Public Provide ### Public Providers -Many tutorials and guides, including the getting started guide for [wagmi], use a _Public Provider_ as the default to get you up and running. Public means that they're open, permissionless, and free, so the guides will also usually warn you that you need to add another provider if you don't want to run into rate limiting. Listen to these warnings! The rate-limits of public providers are severe and you'll start getting limited very quickly. +Many tutorials and guides, including the getting started guide for [wagmi], use a _Public Provider_ as the default to get you up and running. Public means that they're open, permissionless, and free, so the guides will also usually warn you that you need to add another provider if you don't want to run into rate limiting. Listen to these warnings! The rate-limits of public providers are severe, and you'll start getting limited very quickly. In wagmi, the `publicClient` is just a wrapper setting up a [JSON RPC] provider using the `chain` and `rpcUrls` listed in Viem's directory of chain information. For example, you can view the [data for Base Sepolia here]. @@ -66,17 +66,17 @@ Many wallets, including Coinbase Wallet and MetaMask, inject an Ethereum provide Under the hood, these are also just JSON RPC providers. Similar to public providers, they are rate-limited. -Older tutorials for early libraries tended to suggest using this method for getting started, so you'll probably encounter references to it. However, it's fallen out of favor and you'll want to use the public provider for your initial connection experiments. +Older tutorials for early libraries tended to suggest using this method for getting started, so you'll probably encounter references to it. However, it's fallen out of favor, and you'll want to use the public provider for your initial connection experiments. ### Vendor Providers A growing number of vendors provide access to blockchain nodes as a service. Visiting the landing pages for [QuickNode] or [Alchemy] can be a little confusing. Each of these vendors provides a wide variety of services, SDKs, and information. -Luckily, you can skip most of this if you're just trying to get your frontend connected to your smart contracts. You'll just need to sign up for an account and get an endpoint, or a key, and configure your app to connect to the provider(s) you choose. +Luckily, you can skip most of this if you're just trying to get your frontend connected to your smart contracts. You'll just need to sign up for an account, and get an endpoint, or a key, and configure your app to connect to the provider(s) you choose. It is worth digging in to get a better understanding of how these providers charge you for their services. The table below summarizes some of the more important API methods, and how you are charged for them by each of the above providers. -Note that the information below may change, and varies by network. Each provider also has different incentives, discounts, and fees for each level of product. They also have different allowances for calls per second, protocols, and number of endpoints. Please check the source to confirm! +Note that the information below may change, and vary by network. Each provider also has different incentives, discounts, and fees for each level of product. They also have different allowances for calls per second, protocols, and number of endpoints. Please check the source to confirm! | | [Alchemy Costs] | [QuickNode Costs] | | :-------------- | :--------------- | :---------------- | diff --git a/apps/base-docs/docs/connecting-to-the-blockchain/connecting-with-a-provider.md b/apps/base-docs/docs/connecting-to-the-blockchain/connecting-with-a-provider.md index 0e3b5c8bf9..7226642775 100644 --- a/apps/base-docs/docs/connecting-to-the-blockchain/connecting-with-a-provider.md +++ b/apps/base-docs/docs/connecting-to-the-blockchain/connecting-with-a-provider.md @@ -26,7 +26,7 @@ hide_table_of_contents: false ## Objectives -By the end of this guide you should be able to: +By the end of this guide, you should be able to: - Set up a provider in wagmi and use it to connect a wallet - Protect API keys that will be exposed to the front end @@ -73,7 +73,7 @@ Note that these providers are using React's context feature to pass the blockcha Before you can do anything else, you need to obtain a _WalletConnect_ `projectId`. -Open up the [WalletConnect] homepage, and create an account and/or sign in using the method of your choice. +Open up the [WalletConnect] homepage, and create an account, and/or sign in using the method of your choice. Click the `Create` button in the upper right of the `Projects` tab. diff --git a/apps/base-docs/docs/hardhat-tools-and-testing/hardhat-debugging/debugging-with-hardhat-sbs.md b/apps/base-docs/docs/hardhat-tools-and-testing/hardhat-debugging/debugging-with-hardhat-sbs.md index 4892931af1..d6ee33968b 100644 --- a/apps/base-docs/docs/hardhat-tools-and-testing/hardhat-debugging/debugging-with-hardhat-sbs.md +++ b/apps/base-docs/docs/hardhat-tools-and-testing/hardhat-debugging/debugging-with-hardhat-sbs.md @@ -37,7 +37,7 @@ In this tutorial, you will explore the essential debugging features offered by H One of the key features of Hardhat is the ability to use `console.log` for writing debugging logs in your smart contracts. In order to use it, you must include `hardhat/console.sol` in the contract you wish to debug. -In the following contract `Lock.sol` for example, you include `hardhat/console.sol` by importing it and adding a few `console.log`s in the constructor with the text "Creating" and the Ether balance of the contract. This can help you not only with tracking that the contract was created successfully but also, more importantly, with the ability to include additional logs such as the balance of the contract after is was created: +In the following contract `Lock.sol` for example, you include `hardhat/console.sol` by importing it and adding a few `console.log`s in the constructor with the text "Creating" and the Ether balance of the contract. This can help you not only with tracking that the contract was created successfully but also, more importantly, with the ability to include additional logs such as the balance of the contract after it was created: ```solidity // SPDX-License-Identifier: UNLICENSED @@ -100,7 +100,7 @@ describe("Lock Tests", function () { }); ``` -Notice a single test is included in order to get proper logs. However, you're only interested in the creation process that happens in the `before` hook. Then, you can run: +Notice that a single test is included in order to get proper logs. However, you're only interested in the creation process that happens in the `before` hook. Then, you can run: ```bash npx hardhat test @@ -143,7 +143,7 @@ These log functions are handy when the type you intend to log doesn't fall withi While debugging your smart contracts, it's crucial to be familiar with common errors that can arise during development. Recognizing these errors and knowing how to resolve them is an important skill. -In our [Basecamp] series of tutorials, we cover a few compile-time errors in [Error Triage]. Other errors such as `reverts` or `index out of bounds errors` can be unexpected during the runtime of the smart contract. +In our [Basecamp] series of tutorials, we cover a few compile-time errors in [Error Triage]. Other errors, such as `reverts` or `index out of bounds errors` can be unexpected during the runtime of the smart contract. The following explores typical techniques to debug these types of errors. @@ -281,7 +281,7 @@ function createLock(uint256 _unlockTime) external payable { Attempting to access arrays at an invalid position can also cause errors. -If you wish to retrieve all the `Lock` contract instances being created in the previous example, you can make the `locks` array public. In order to illustrate this example though, you can create a custom function called `getAllLocks`: +If you wish to retrieve all the `Lock` contract instances being created in the previous example, you can make the `locks` array public. In order to illustrate this example, though, you can create a custom function called `getAllLocks`: ```solidity contract LockCreator { diff --git a/apps/base-docs/docs/hardhat-tools-and-testing/hardhat-test-coverage/hardhat-test-coverage-sbs.md b/apps/base-docs/docs/hardhat-tools-and-testing/hardhat-test-coverage/hardhat-test-coverage-sbs.md index 570f4d4f57..4c00b59a5f 100644 --- a/apps/base-docs/docs/hardhat-tools-and-testing/hardhat-test-coverage/hardhat-test-coverage-sbs.md +++ b/apps/base-docs/docs/hardhat-tools-and-testing/hardhat-test-coverage/hardhat-test-coverage-sbs.md @@ -32,7 +32,7 @@ By the end of this lesson, you should be able to: ## Overview -The Solidity Coverage plugin allow you to analyze and visualize the coverage of your smart contracts' test suite. This enables you to see what portions of your smart contract are being tested and what areas may have been overlooked. It's an indispensable plugin for developers seeking to fortify their testing practices and ensure robust smart contract functionality. +The Solidity Coverage plugin allows you to analyze and visualize the coverage of your smart contracts' test suite. This enables you to see what portions of your smart contract are being tested and what areas may have been overlooked. It's an indispensable plugin for developers seeking to fortify their testing practices and ensure robust smart contract functionality. ## Setting up the Solidity Coverage plugin diff --git a/apps/base-docs/docs/tokens.md b/apps/base-docs/docs/tokens.md index 0967f6c948..c162e613e3 100644 --- a/apps/base-docs/docs/tokens.md +++ b/apps/base-docs/docs/tokens.md @@ -33,11 +33,11 @@ The steps below explain how to get your token on the Base Token List. ### Step 1: Deploy your token on Base -Select your preferred bridging framework and use it to deploy an ERC-20 for your token on Base. We recommend you use the framework provided by Base's [standard bridge](https://github.com/ethereum-optimism/specs/blob/main/specs/bridges.md) contracts, and furthermore deploy your token using the [OptimismMintableERC20Factory](https://docs.base.org/base-contracts/#l2-contract-addresses). Deploying your token on Base in this manner provides us with guarantees that will smooth the approval process. If you choose a different bridging framework, its interface must be compatible with that of the standard bridge, otherwise it may be difficult for us to support. +Select your preferred bridging framework and use it to deploy an ERC-20 for your token on Base. We recommend you use the framework provided by Base's [standard bridge](https://github.com/ethereum-optimism/specs/blob/main/specs/protocol/bridges.md) contracts, and furthermore deploy your token using the [OptimismMintableERC20Factory](https://docs.base.org/base-contracts/#l2-contract-addresses). Deploying your token on Base in this manner provides us with guarantees that will smooth the approval process. If you choose a different bridging framework, its interface must be compatible with that of the standard bridge, otherwise it may be difficult for us to support. ### Step 2: Submit details for your token -Follow the instructions in the [GitHub repository](https://github.com/ethereum-optimism/ethereum-optimism.github.io) and submit a PR containing the required details for your token. You must specify in your token's data.json file a section for ‘base-sepolia' and/or ‘base’ . The change you need to submit is particularly simple if your token has already been added to the Optimism token list. For example, [this PR](https://github.com/ethereum-optimism/ethereum-optimism.github.io/commit/27ab9b2d3388f7feba3a152e0a0748c73d732a68) shows the change required for cbETH, which was already on Optimism's token list and relies on the Base standard bridge. +Follow the instructions in the [GitHub repository](https://github.com/ethereum-optimism/ethereum-optimism.github.io) and submit a PR containing the required details for your token. You must specify in your token's data.json file a section for ‘base-sepolia' and/or ‘base’. The change you need to submit is particularly simple if your token has already been added to the Optimism token list. For example, [this PR](https://github.com/ethereum-optimism/ethereum-optimism.github.io/commit/27ab9b2d3388f7feba3a152e0a0748c73d732a68) shows the change required for cbETH, which was already on Optimism's token list and relies on the Base standard bridge. ### Step 3: Await final approval diff --git a/apps/base-docs/docs/tools/account-abstraction.md b/apps/base-docs/docs/tools/account-abstraction.md index b5524019b8..4c7bff787c 100644 --- a/apps/base-docs/docs/tools/account-abstraction.md +++ b/apps/base-docs/docs/tools/account-abstraction.md @@ -27,7 +27,7 @@ keywords: ## Alchemy Account Kit -[Account Kit](https://www.alchemy.com/account-kit) is a complete solution for account abstraction. Using Account Kit you can create a smart contract wallet for every user that leverages account abstraction to simplify every step of your apps onboaring experience. It also offers Gas Manager and Bundler APIs for sponsoring gas and batching transactions. +[Account Kit](https://www.alchemy.com/account-kit) is a complete solution for account abstraction. Using Account Kit, you can create a smart contract wallet for every user that leverages account abstraction to simplify every step of your app's onboaring experience. It also offers Gas Manager and Bundler APIs for sponsoring gas and batching transactions. --- @@ -67,6 +67,6 @@ WalletKit is compatible with most EVM chains, including Base. You can check out ## ZeroDev -[ZeroDev](https://zerodev.app) is an embedded wallet powered by account abstraction. It offers you the ability to create self-custody wallets for your users, sponsor gas, and simplify user slows by batching and automating transactions. +[ZeroDev](https://zerodev.app) is an embedded wallet powered by account abstraction. It offers you the ability to create self-custody wallets for your users, sponsor gas, and simplify user flows by batching and automating transactions. --- diff --git a/apps/base-docs/docs/tools/block-explorers.md b/apps/base-docs/docs/tools/block-explorers.md index 98fea3924f..c9da1471c5 100644 --- a/apps/base-docs/docs/tools/block-explorers.md +++ b/apps/base-docs/docs/tools/block-explorers.md @@ -78,6 +78,6 @@ A testnet explorer for [Base Sepolia](https://sepolia.basescan.org/) is also ava ## Tenderly Explorer -With [Tenderly](https://tenderly.co/) developer explorer you can get unparalleled visibility into your smart contract code. You can easily view detailed transaction information, spot bugs in your code and optimize gas spend. Supporting Base mainnet and Base Sepolia testnet, Tenderly Explorer helps you track your smart contracts while providing visibility on a granular level. +With the [Tenderly](https://tenderly.co/) developer explorer you can get unparalleled visibility into your smart contract code. You can easily view detailed transaction information, spot bugs in your code, and optimize gas spend. Supporting Base mainnet and Base Sepolia testnet, Tenderly Explorer helps you track your smart contracts while providing visibility on a granular level. --- diff --git a/apps/base-docs/docs/tools/bridge-faq.md b/apps/base-docs/docs/tools/bridge-faq.md index f66f0b1e27..3bc3411a02 100644 --- a/apps/base-docs/docs/tools/bridge-faq.md +++ b/apps/base-docs/docs/tools/bridge-faq.md @@ -41,19 +41,19 @@ Yep! The process is bidirectional, you can bridge from both Ethereum to Base, an ### How long does the transfer take? -Transferring from Ethereum to Base usually only takes a few minutes, but that timeline is not guaranteed. Transferring from Base to Ethereum takes approximately 7 days. This is a security feature designed to help secure Base. If you prefer not to wait, you can alternatively use [Coinbase](https://coinbase.com) with any assets that they support Base network deposits from, or a third-party bridge which allows you to transfer assets much faster! +Transferring from Ethereum to Base usually only takes a few minutes, but that timeline is not guaranteed. Transferring from Base to Ethereum takes approximately 7 days. This is a security feature designed to help secure Base. If you prefer not to wait, you can alternatively use [Coinbase](https://coinbase.com) with any assets that they support Base network deposits from, or a third-party bridge, which allows you to transfer assets much faster! ### How do you withdraw from Base? Connect your wallet and confirm that it is set to Base network. Choose the digital asset you wish to bridge back to Ethereum mainnet and confirm you want to withdraw. -After your withdrawal request is proposed onchain (within an hour) you must verify and complete the transaction in order to access your funds. You can track your progress under the transaction tab. +After your withdrawal request is proposed onchain (within an hour), you must verify and complete the transaction in order to access your funds. You can track your progress under the transaction tab. -Transferring from Base to Ethereum takes approximately 7 days. This is a security feature designed to help secure Base. If you prefer not to wait, you can alternatively use a third-party bridge which allows you to transfer assets much faster. +Transferring from Base to Ethereum takes approximately 7 days. This is a security feature designed to help secure Base. If you prefer not to wait, you can alternatively use a third-party bridge, which allows you to transfer assets much faster. ### Are there any fees involved in using Base Bridge? -There are network fees involved which are used to pay for the gas costs on Ethereum and Base. There are no additional fees specifically for using Base Bridge. +There are network fees involved, which are used to pay for the gas costs on Ethereum and Base. There are no additional fees specifically for using Base Bridge. ### What is the benefit of transferring my digital assets from Ethereum to Base? @@ -61,7 +61,7 @@ By transferring digital assets from Ethereum to Base, you get to experience the ### Can I use the same wallet on Base that I use on Ethereum? -Yes, in most cases you can use the same Ethereum-compatible wallet to interact with Base. +Yes, in most cases, you can use the same Ethereum-compatible wallet to interact with Base. ### Are there any risks involved in using Base Bridge? @@ -77,11 +77,11 @@ Yes, once your digital assets are on Base, you can interact with apps deployed o ### Can I cancel a withdrawal? -No, if a withdrawal has already been initiated on the [Withdraw](https://bridge.base.org/withdraw) page it is not possible to cancel it. Once withdrawn the process needs to be completed. +No, if a withdrawal has already been initiated on the [Withdraw](https://bridge.base.org/withdraw) page it is not possible to cancel it. Once withdrawn, the process needs to be completed. ### Why does it take seven days to withdraw? -This seven day bridge duration is in place as a [challenge period](https://community.optimism.io/docs/developers/bridge/messaging/#fees-for-l2-%E2%87%92-l1-transactions) security measure built into the OP Stack. +This seven-day bridge duration is in place as a [challenge period](https://community.optimism.io/docs/developers/bridge/messaging/#fees-for-l2-%E2%87%92-l1-transactions) security measure built into the OP Stack. If you prefer not to wait, instead of making a withdrawal using Base Bridge, you also have the option to utilize a [third-party bridge](https://base.org/ecosystem?tag=bridge) for quicker withdrawals. @@ -89,8 +89,8 @@ If you prefer not to wait, instead of making a withdrawal using Base Bridge, you Navigate to the [Transactions](https://bridge.base.org/transactions) page. Next to your transaction, use the button to "Switch to L1". This action will ask you to switch to the Ethereum Mainnet network, enabling you to proceed with the verification process. -Proceed to then use the same button which will update to a new status enabling you to "Verify" your withdrawal. This action will prompt you to complete verification with your wallet by signing a transaction. +Proceed to then use the same button, which will update to a new status enabling you to "Verify" your withdrawal. This action will prompt you to complete verification with your wallet by signing a transaction. -Seven days after you have verified your withdrawal, you can complete your withdrawal by returning to the Transactions page. Use the "Complete" button which will appear next to your transaction. +Seven days after you have verified your withdrawal, you can complete your withdrawal by returning to the Transactions page. Use the "Complete" button, which will appear next to your transaction. --- diff --git a/apps/base-docs/docs/tools/cross-chain.md b/apps/base-docs/docs/tools/cross-chain.md index 1899227ef0..e40a75d8db 100644 --- a/apps/base-docs/docs/tools/cross-chain.md +++ b/apps/base-docs/docs/tools/cross-chain.md @@ -36,7 +36,7 @@ keywords: [Axelar](https://axelar.network/) is an interchain platform that connects blockchains to enable universal web3 transactions. By integrating with Axelar, applications built on Base can now easily send messages and assets between the 49+ blockchains connected via Axelar. -To learn more about Axelar visit our [docs](https://docs.axelar.dev/). For complete end-to-end examples demonstrating various Axelar usecases please visit the available [code examples](https://github.com/axelarnetwork/axelar-examples) +To learn more about Axelar visit our [docs](https://docs.axelar.dev/). For complete end-to-end examples demonstrating various Axelar usecases please visit the available [code examples](https://github.com/axelarnetwork/axelar-examples). #### Supported Networks @@ -45,7 +45,7 @@ To learn more about Axelar visit our [docs](https://docs.axelar.dev/). For compl #### Axelarscan -To view current transactions and live stats about the Axelar network please visit the [Axelarscan block explorer](https://axelarscan.io/) +To view current transactions and live stats about the Axelar network, please visit the [Axelarscan block explorer](https://axelarscan.io/) --- @@ -65,7 +65,7 @@ Check out [Crossmint Docs](https://docs.crossmint.com/nft-checkout/introduction/ [Chainlink CCIP](https://chain.link/cross-chain) is a secure interoperability protocol that allows for securely sending messages, transfering tokens, and initiating actions across different blockchains. -To get started with integrating Chainlink CCIP in your Base project, visit the Chainlink CCIP [documentation](https://docs.chain.link/ccip) +To get started with integrating Chainlink CCIP in your Base project, visit the Chainlink CCIP [documentation](https://docs.chain.link/ccip). #### Supported Networks @@ -78,7 +78,7 @@ To get started with integrating Chainlink CCIP in your Base project, visit the C [LayerZero](https://layerzero.network/) is an omnichain interoperability protocol that enables cross-chain messaging. Applications built on Base can use the LayerZero protocol to connect to 35+ supported blockchains seamlessly. -To get started with integrating LayerZero, visit the LayerZero [documentation](https://layerzero.gitbook.io/docs/evm-guides/master/how-to-send-a-message) and provided examples on [GitHub](https://github.com/LayerZero-Labs/solidity-examples) +To get started with integrating LayerZero, visit the LayerZero [documentation](https://layerzero.gitbook.io/docs/evm-guides/master/how-to-send-a-message) and provided examples on [GitHub](https://github.com/LayerZero-Labs/solidity-examples). #### Supported Networks @@ -95,7 +95,7 @@ By integrating Wormhole, a Base application can access users and liquidity on > See [this quickstart](https://docs.wormhole.com/wormhole/quick-start/tutorials/hello-wormhole) to get started with integrating Wormhole in your Base project. -For more information on integrating Wormhole, visit their [documentation](https://docs.wormhole.com/wormhole/) and provided [GitHub examples](https://github.com/wormhole-foundation/wormhole-examples). +For more information on integrating Wormhole, visit their [documentation](https://docs.wormhole.com/wormhole/) and the provided [GitHub examples](https://github.com/wormhole-foundation/wormhole-examples). #### Supported Networks diff --git a/apps/base-docs/docs/tools/data-indexers.md b/apps/base-docs/docs/tools/data-indexers.md index ae169dc120..7d2d0a1444 100644 --- a/apps/base-docs/docs/tools/data-indexers.md +++ b/apps/base-docs/docs/tools/data-indexers.md @@ -61,7 +61,7 @@ To get started, [sign up](https://www.covalenthq.com/platform/?utm_source=base&u Envio [HyperSync](https://docs.envio.dev/docs/hypersync) is an indexed layer of the Base blockchain for the hyper-speed syncing of historical data (JSON-RPC bypass). What would usually take hours to sync ~100,000 events can now be done in the order of less than a minute. -Designed to optimize the user experience, Envio offers automatic code generation, flexible language support, multi-chain data aggregation, and a reliable cost-effective hosted service. +Designed to optimize the user experience, Envio offers automatic code generation, flexible language support, multi-chain data aggregation, and a reliable, cost-effective hosted service. To get started, visit the [documentation](https://docs.envio.dev/docs/overview) or follow the [quickstart](https://docs.envio.dev/docs/quickstart) guide. @@ -74,7 +74,7 @@ To get started, visit the [documentation](https://docs.envio.dev/docs/overview) ## Shovel -[Shovel](https://indexsupply.com/shovel) is an [open source](https://github.com/indexsupply/code) tool for synchronizing Ethereum data to your Postgres database. Shovel can index block data, transaction data, and decoded event data. A single Shovel can index multiple chains simultaneously. Shovel is configured via a declarative JSON config file –no custom functions to save indexed data to your database. +[Shovel](https://indexsupply.com/shovel) is an [open source](https://github.com/indexsupply/code) tool for synchronizing Ethereum data to your Postgres database. Shovel can index block data, transaction data, and decoded event data. A single Shovel can index multiple chains simultaneously. Shovel is configured via a declarative JSON config file – no custom functions to save indexed data to your database. Find out more in the [Shovel Docs](https://indexsupply.com/shovel/docs/) @@ -89,7 +89,7 @@ Find out more in the [Shovel Docs](https://indexsupply.com/shovel/docs/) [SubQuery](https://subquery.network/) is a data indexer that provides developers with fast, reliable, decentralized, and customized APIs for accessing rich indexed data from over 80+ ecosystems (including Base) within their projects. -SubQuery provides the ability to aggregate this data across multiple blockchains all within a single project. +SubQuery provides the ability to aggregate this data across multiple blockchains, all within a single project. Other advantages of SubQuery includes performance with multiple RPC endpoint configurations, multi-worker capabilities and a configurable caching architecture. diff --git a/apps/base-docs/docs/tools/network-faucets.md b/apps/base-docs/docs/tools/network-faucets.md index c4ef13223e..4ccacf8f79 100644 --- a/apps/base-docs/docs/tools/network-faucets.md +++ b/apps/base-docs/docs/tools/network-faucets.md @@ -28,7 +28,7 @@ The [Superchain Faucet](https://app.optimism.io/faucet) provides testnet ETH for :::info -The Superchain faucet allows developers to authenticate via their onchain identity. Developers that choose to authenticate via their onchain identity can claim more testnet ETH versus traditional faucets. For more information see the [FAQ](https://app.optimism.io/faucet). +The Superchain faucet allows developers to authenticate via their onchain identity. Developers that choose to authenticate via their onchain identity can claim more testnet ETH versus traditional faucets. For more information, see the [FAQ](https://app.optimism.io/faucet). ::: diff --git a/apps/base-docs/docs/tools/node-providers.md b/apps/base-docs/docs/tools/node-providers.md index 9fe1919762..05c850dd49 100644 --- a/apps/base-docs/docs/tools/node-providers.md +++ b/apps/base-docs/docs/tools/node-providers.md @@ -41,7 +41,7 @@ keywords: ## 1RPC -[1RPC](https://1rpc.io/) is the first and only on-chain attested privacy preserving RPC that eradicate metadata exposure and leakage when interacting with blockchains. 1RPC offers free and [paid plans](https://www.1rpc.io/#pricing) with additional features and increased request limits. +[1RPC](https://1rpc.io/) is the first and only on-chain attested privacy preserving RPC that eradicates metadata exposure and leakage when interacting with blockchains. 1RPC offers free and [paid plans](https://www.1rpc.io/#pricing) with additional features and increased request limits. #### Supported Networks @@ -73,7 +73,7 @@ keywords: ## Blast -[Blast](https://blastapi.io/public-api/base) provides fast and reliable decentralized blockchain APIs by partnering with third-party Node Providers. Blast offers users the ability generate their own [dedicated RPC endpoint for Base](https://blastapi.io/login). +[Blast](https://blastapi.io/public-api/base) provides fast and reliable decentralized blockchain APIs by partnering with third-party Node Providers. Blast offers users the ability to generate their own [dedicated RPC endpoint for Base](https://blastapi.io/login). #### Supported Networks @@ -84,7 +84,7 @@ keywords: ## Blockdaemon -[Blockdaemon](https://www.blockdaemon.com/protocols/base/) offers access to hosted Base nodes with a free plan at $0/month via Ubiquity Data API Suite. Extra costs may be incurred depending on usage. +[Blockdaemon](https://www.blockdaemon.com/protocols/base/) offers access to hosted Base nodes with a free plan at $0/month via the Ubiquity Data API Suite. Extra costs may be incurred depending on usage. #### Supported Networks @@ -116,7 +116,7 @@ keywords: ## DRPC -[DRPC](https://drpc.org/) offers access to distributed network of independent third-party partners and public nodes for Base. They provide a free tier that allows for an unlimited amount of requests over public nodes, or a paid tier which provides access to all providers, as well as other additional features. +[DRPC](https://drpc.org/) offers access to a distributed network of independent third-party partners and public nodes for Base. They provide a free tier that allows for an unlimited amount of requests over public nodes, or a paid tier which provides access to all providers, as well as other additional features. #### Supported Networks diff --git a/apps/base-docs/docs/tools/onboarding.md b/apps/base-docs/docs/tools/onboarding.md index b9fb91f4bc..8a7a9cecac 100644 --- a/apps/base-docs/docs/tools/onboarding.md +++ b/apps/base-docs/docs/tools/onboarding.md @@ -43,13 +43,13 @@ keywords: [Privy](https://www.privy.io/) is a library designed for progressive user onboarding and authentication. It enables users to connect to your app using traditional methods such as email addresses, phone numbers, or social profiles, as well as through web3 methods like crypto wallets. Additionally, Privy supports embedded wallets, eliminating the need for users to have a self-custodial wallet prior to exploring your app. Privy is compatible with most EVM chains, including Base. -You can [get started with Privy here](https://docs.privy.io/guide/quickstart) and check out these starter repos for [building a Progressive Web App (PWA) on Base](https://github.com/privy-io/create-privy-pwa) and [using the Base Paymaster with Privy](https://github.com/privy-io/base-paymaster-example). +You can [get started with Privy here](https://docs.privy.io/guide/quickstart), and check out these starter repos for [building a Progressive Web App (PWA) on Base](https://github.com/privy-io/create-privy-pwa) and [using the Base Paymaster with Privy](https://github.com/privy-io/base-paymaster-example). --- ## Particle Network -[Particle Network](https://particle.network/) is the intent-centric, modular access layer of Web3. With Particle's Smart Wallet-as-a-Service, developers can curate an seamless user experience through modular and customizable EOA/AA embedded wallet components. Using MPC-TSS for key management, Particle can streamline user onboarding via familiar web2 accounts - such as Google accounts, email addresses, and phone numbers. Particle Network's Smart Wallet-as-a-Service is compatible with most EVM chains, including Base. +[Particle Network](https://particle.network/) is the intent-centric, modular access layer of Web3. With Particle's Smart Wallet-as-a-Service, developers can curate a seamless user experience through modular and customizable EOA/AA embedded wallet components. Using MPC-TSS for key management, Particle can streamline user onboarding via familiar web2 accounts - such as Google accounts, email addresses, and phone numbers. Particle Network's Smart Wallet-as-a-Service is compatible with most EVM chains, including Base. --- diff --git a/apps/base-docs/docs/tools/onramps.md b/apps/base-docs/docs/tools/onramps.md index 0acbb02b7b..1f6070a2c9 100644 --- a/apps/base-docs/docs/tools/onramps.md +++ b/apps/base-docs/docs/tools/onramps.md @@ -39,7 +39,7 @@ keywords: ## Onramp -[Onramp](https://onramp.money/) is a fiat-to-crypto payment gateway which helps users seamlessly convert fiat currency to desired cryptocurrency. Onramp currently supports 300+ cryptocurrencies and 20+ blockchain networks, including ETH on Base. +[Onramp](https://onramp.money/) is a fiat-to-crypto payment gateway, which helps users seamlessly convert fiat currency to the desired cryptocurrency. Onramp currently supports 300+ cryptocurrencies and 20+ blockchain networks, including ETH on Base. --- diff --git a/apps/base-docs/docs/tools/viem.md b/apps/base-docs/docs/tools/viem.md index 8b3cfce8e6..db07bfe82e 100644 --- a/apps/base-docs/docs/tools/viem.md +++ b/apps/base-docs/docs/tools/viem.md @@ -41,7 +41,7 @@ npm install --save viem ## Setup -Before you can start using viem, you need to setup a [Client](https://viem.sh/docs/clients/intro.html) with a desired [Transport](https://viem.sh/docs/clients/intro.html) and [Chain](https://viem.sh/docs/clients/chains.html). +Before you can start using viem, you need to setup a [Client](https://viem.sh/docs/clients/intro.html) with a desired [Transport](https://viem.sh/docs/clients/intro.html) and [Chain](https://viem.sh/docs/chains/introduction). ```javascript import { createPublicClient, http } from 'viem';