+
+
+
+
+
+
+#### Tooltips and updates
+
+
+
+ 2. Add your Project ID to your `.env` file.
+
+ ```tsx twoslash [.env]
+ // @noErrors
+ NEXT_PUBLIC_ONCHAINKIT_API_KEY=YOUR_PUBLIC_API_KEY
+ NEXT_PUBLIC_CDP_PROJECT_ID=YOUR_CDP_PROJECT_ID // [!code ++]
+ ```
+
-
-2. Add your Project ID to your `.env` file.
-
-```tsx twoslash [.env]
-// @noErrors
-NEXT_PUBLIC_ONCHAINKIT_API_KEY=YOUR_PUBLIC_API_KEY
-NEXT_PUBLIC_CDP_PROJECT_ID=YOUR_CDP_PROJECT_ID // [!code ++]
-```
-
-### Add Project ID to OnchainKitProvider
-
-```tsx twoslash
-// @noErrors
-
-:::
+
+
+Play with it live [here](https://onchain-app-template.vercel.app).
+
+## Out of the box
+
+- Next.js v14 with App routing 🏗️
+- Ethereum L2 support through Base 🔵
+- Easy account creation with Smart Wallet
+- Live examples for Minting and Paymaster experiences with wagmi and Viem 🚀
+- Latest styling best practices with Tailwind CSS 💅
+- Easy maintenance with linting, formatting, and tests ✅
+
+## Getting Started
+
+
+ 
+
+ In order to use RainbowKit, you'd also need to obtain a Wallet Connector project ID at [WalletConnect](https://cloud.reown.com/app).
+
+ 
+
+ ```tsx [.env]
+ NEXT_PUBLIC_CDP_API_KEY=YOUR_PUBLIC_API_KEY
+ NEXT_PUBLIC_WC_PROJECT_ID=YOUR_WALLETCONNECT_PROJECT_ID
+ ```
+
+
+ Create a `.env` file in your project's root directory.
+
+
+
+ Add your Client API Key to the `.env` file:
+
+ ```dotenv [.env]
+ PUBLIC_ONCHAINKIT_API_KEY=YOUR_CLIENT_API_KEY
+ ```
+
+
+ Create a `.env` file in your project's root directory.
+
+
+
+ Add your Client API Key to the `.env` file:
+
+ ```tsx [.env]
+ NEXT_PUBLIC_ONCHAINKIT_API_KEY=YOUR_CLIENT_API_KEY;
+ ```
+
+
+ Create a `.env` file in your project's root directory.
+
+
+
+ Add your Client API Key to the `.env` file:
+
+ ```dotenv [.env]
+ PUBLIC_ONCHAINKIT_API_KEY=YOUR_CLIENT_API_KEY
+ ```
+
+ Update the `app/root.tsx` file to provide access to your Client API Key
+ through `window.ENV`:
+
+ ```tsx [app/root.tsx]
+ declare global {
+ interface Window {
+ ENV: {
+ PUBLIC_ONCHAINKIT_API_KEY: string; // [!code ++]
+ };
+ }
+ }
+
+ export async function loader() {
+ return json({
+ ENV: {
+ PUBLIC_ONCHAINKIT_API_KEY: process.env.PUBLIC_ONCHAINKIT_API_KEY, // [!code ++]
+ },
+ });
+ }
+ ```
+
+ If this is the first env variable you've added to your project, you will need to
+ update the `Layout` component of `app/root.tsx` to make it available to your app:
+
+ ```tsx [app/root.tsx]
+ export function Layout({ children }: { children: React.ReactNode }) {
+ const data = useLoaderData
+
+ Create a `.env` file in your project's root directory.
+
+
+
+ Add your Client API Key to the `.env` file:
+
+ ```dotenv [.env]
+ VITE_PUBLIC_ONCHAINKIT_API_KEY=YOUR_CLIENT_API_KEY
+ ```
+ 
+
+ ```tsx twoslash
+ // @noErrors: 2304 17008 1005
+
+ 
+
+
+The components are designed to work together hierarchically. For each component, ensure the following:
+
+- `
+
-
-
-
+
+
+
-
-
+
+
+ ```
+
+
+
-
-::::
+
+
+
+
+
+
+
+
+
+
+
-
-
-
-
-
-
-
-
+
+ Kick off your wallet connection setup by configuring the `wagmi` provider.
+
+ And make sure to update the `appName` as that will be displayed to
+ the user when they connect their wallet.
+
+ ```tsx twoslash
+ // @noErrors: 2554
+ import { ReactNode } from 'react';
+ import { WagmiProvider, createConfig, http } from 'wagmi';
+ import { baseSepolia } from 'wagmi/chains';
+ import { coinbaseWallet } from 'wagmi/connectors';
+
+ const wagmiConfig = createConfig({
+ chains: [baseSepolia],
+ connectors: [
+ coinbaseWallet({
+ appName: 'onchainkit',
+ }),
+ ],
+ ssr: true,
+ transports: {
+ [baseSepolia.id]: http(),
+ },
+ });
+
+ function App({ children }: { children: ReactNode }) {
+ return {children} ;
+ }
+ ```
+
+
+
+ Experience the magic by simply dropping in the ``](/builderkits/onchainkit/identity/identity) components
+ like [``](/builderkits/onchainkit/identity/avatar), [``](/builderkits/onchainkit/identity/name),
+ and [``](/builderkits/onchainkit/identity/address) are used in a composable way.
+ Explore their documentation pages to discover various customization options.
+
+ ```tsx twoslash
+ import {
+ ConnectWallet,
+ Wallet,
+ WalletDropdown,
+ WalletDropdownDisconnect,
+ } from '@coinbase/onchainkit/wallet';
+ import {
+ Address,
+ Avatar,
+ Name,
+ Identity,
+ } from '@coinbase/onchainkit/identity';
+ import { color } from '@coinbase/onchainkit/theme';
+
+ export function WalletComponents() {
+ return (
+
-
-
-
-
-
-
+
+
+
+
+
+ );
+ }
+ ```
+
+
+
+
+
-
- );
-}
-```
-
-
+
+ );
+};
+
+export default App;
+```
+
+With everything complete, you're ready to run your application to test it. To do so, go through the following process:
+
+1. Navigate to the root of your project.
+2. Run either `npm run start` or `yarn start`.
+3. Once running, log in with either your Google or Twitter.
+4. Fund the address displayed on the wallet modal in the bottom right.
+5. Click "Execute User Operation".
+
+## Conclusion
+
+Congratulations! You've just built an application from scratch, onboarding users into smart accounts through social logins using Particle Network.
+
+To learn more about using Particle Network on Base, take a look at the following resources:
+
+- [Biconomy Guide (which uses Particle Network)]
+- [Account Abstraction on Base]
+- [Particle Network Documentation]
+- [Particle Network 101: Developer Experience]
+
+[create-react-app]: https://create-react-app.dev
+[Base Faucets]: https://docs.base.org/chain/network-faucets
+[Web3Auth]: https://web3auth.io
+[Privy]: https://docs.base.org/tutorials/account-abstraction-with-privy-and-base-paymaster/
+[Magic]: https://magic.link
+[ERC-4337]: https://eips.ethereum.org/EIPS/eip-4337
+[Biconomy]: https://docs.base.org/guides/account-abstraction-with-biconomy
+[external infrastructure and components]: https://blog.particle.network/announcing-our-smart-wallet-as-a-service-modular-stack-upgrading-waas-with-erc-4337
+[Introduction to Account Abstraction]: https://docs.base.org/cookbook/account-abstraction/account-abstraction-on-base-using-privy-and-the-base-paymaster
+[Particle dashboard]: https://dashboard.particle.network
+[Biconomy Guide (which uses Particle Network)]: https://docs.base.org/cookbook/account-abstraction/account-abstraction-on-base-using-biconomy
+[Account Abstraction on Base]: https://docs.base.org/tools/account-abstraction
+[Particle Network Documentation]: https://developers.particle.network
+[Particle Network 101: Developer Experience]: https://blog.particle.network/particle-network-101-developer-experience-edition
+
diff --git a/_pages/cookbook/account-abstraction/account-abstraction-on-base-using-privy-and-the-base-paymaster.mdx b/_pages/cookbook/account-abstraction/account-abstraction-on-base-using-privy-and-the-base-paymaster.mdx
new file mode 100644
index 00000000..b338dea8
--- /dev/null
+++ b/_pages/cookbook/account-abstraction/account-abstraction-on-base-using-privy-and-the-base-paymaster.mdx
@@ -0,0 +1,734 @@
+---
+title: 'Account Abstraction on Base using Privy and the Base Paymaster'
+slug: /account-abstraction-with-privy-and-base-paymaster
+description: A tutorial that teaches how to implement Account Abstraction into a Base project using Privy and the Base paymaster.
+author: Brian Doyle and Aaron Hayslip
+---
+
+# Account Abstraction on Base using Privy and the Base Paymaster
+
+This tutorial shows you how to use [Privy], [Alchemy's Account Kit], and the [Base Paymaster] to enable your users to use onchain apps without creating a wallet on their own, or even needing to pay for gas fees!
+
+## Objectives
+
+By the end of this tutorial, you should be able to:
+
+### Intro to Account Abstraction
+
+- Explain how Account Abstraction can improve user experience for onchain apps
+- Describe the difference between contract accounts and EOAs, the limitations of contract accounts, and how EIP-4337 uses `UserOperation`s to mitigate these limitations
+- Outline how Account Abstraction works, and how users interact with smart contract wallets
+
+### Intro to Privy
+
+- Implement Privy's quick start to add onchain authentication to a NextJS application
+- Compare Privy's progressive authentication strategy with traditional wallet-based authentication
+- Use Privy's `PrivyProvider` context and `usePrivy` hook to implement basic authentication via an email address, SMS, EOA, and/or social auth
+- Utilize Privy's Embedded Wallets to enable users to utilize wallet-based actions without having to connect to an external wallet or leave your application
+
+### Implementing the Paymaster
+
+- Describe how a third party can use a _paymaster_ to sponsor gas
+- Modify Privy's Base [paymaster example] example to work in another app, using an EOA to allow a user to call a smart contract function without requiring the user to pay any gas
+
+## Prerequisites
+
+### 1. Be familiar with modern, frontend web development
+
+In this tutorial, we'll be working with a React frontend built with [Next.js]. While you don't need to be an expert, we'll assume that you're comfortable with the basics.
+
+### 2. Possess a general understanding of the EVM and smart contract development
+
+This tutorial assumes that you're reasonably comfortable writing basic smart contracts. If you're just getting started, jump over to our [Base Learn] guides and start learning!
+
+## Intro do Account Abstraction
+
+[ERC-4337], also known as _Account Abstraction_, is a standard that allows smart contracts to initiate transactions, thus enabling any logic that users want to implement to be encoded into the smart contract wallet itself for execution on Ethereum.
+
+Account Abstraction has the potential to be a massive game-changer for onchain user experience and many believe it will play a key role in bringing the next billion users onchain.
+
+### The Problem Account Abstraction Solves
+
+Onchain applications are difficult to use for many people, as they require a lengthy onboarding process for the average internet user who already onchain.
+
+For example,the preliminary steps a user needs to go through before they can use an onchain app are:
+
+1. Create a wallet (Coinbase Wallet, Metamask, etc)
+1. Store the wallet mnemonic safely, without losing it or compromising it
+1. Sign a slightly frightening message to connect to an onchain app
+1. Try to do anything with the app and get a popup asking them to approve a transaction
+1. Attempt to do so, learn transactions cost gas, and that they don't have any
+1. Learn that gas is a fee that users must pay in ETH to use onchain apps
+1. Attempt to buy ETH, possibly buying the wrong flavor of ETH in the wrong location
+1. Try the transaction again
+1. Repeat until they finally find the correct path
+
+For widespread adoption of onchain applications, this confusing and alienating process has to change.
+
+That's where Account Abstraction comes in. It allows you to improve the onboarding and usage flow for your users:
+
+1. User goes to the onchain app and authenticates (using email, EOA, or social auth)
+2. User uses the app
+3. Transactions happen under the hood via a smart contract wallet and the app developer sponsors the user's gas fees until after they're onboarded.
+
+To summarize, Account Abstraction enables smart contract accounts to initiate user operations, similar to how an EOA would initiate a transaction. However, unlike EOAs, smart contract accounts are programmable and can enable a number of incredible features, such as:
+
+- **Sponsored Transactions**: Allow application owners to cover the users gas fees with a paymaster or allow a user to use something other than ETH (USDC, for example) to cover gas
+- **Arbitrary Verification Logic**: Verify transactions with custom logic
+- **Account Recovery**: Create account recovery features for when user lose private keys
+- **Batching Transactions**: Change the user experience so that multiple transactions can be submitted at once
+
+### Overview of ERC-4337 - Account Abstraction
+
+"Account Abstraction" comes from [ERC-4337]. The proposal itself is a dense read, but one of stated goals of the proposal is to:
+
+> allow users to use smart contract wallets containing arbitrary verification logic instead of EOAs as their primary account. Completely remove any need at all for users to also have EOAs (as status quo SC wallets and EIP-3074 both require)
+
+In other words, the proposal seeks to allow users to use _smart contract wallets_ **instead** of EOAs to transact onchain.
+
+
+ 
+ 
+
+ {!userInfo ? (
+
+
+
+
+
+
+ ) : (
+
+
+ )}
+ {userInfo.name}
+
+
+
+
+ + Your Smart Wallet Address +
+ + {smartAccountAddress} + ++ Your Signer Address +
+ + {eoa?.address} + +``` + +Paste it above the `` for the `User Object` window. + +You'll need to import `BASE_GOERLI_SCAN_URL` from `constants.ts`. The `useSmartAccount` hook returns `smartAccountProvider` and `eoa`. Import it and add it under the `usePrivy` hook. You don't need them just yet, but go ahead and decompose `smartAccountProvider` and `sendSponsoredUserOperation` as well: + +```tsx +const router = useRouter(); +const { + ready, + authenticated, + user, + logout, + linkEmail, + linkWallet, + unlinkEmail, + linkPhone, + unlinkPhone, + unlinkWallet, + linkGoogle, + unlinkGoogle, + linkTwitter, + unlinkTwitter, + linkDiscord, + unlinkDiscord, +} = usePrivy(); +const { smartAccountAddress, smartAccountProvider, sendSponsoredUserOperation, eoa } = + useSmartAccount(); +``` + +Run the app. You'll now see your familiar wallet address as `YOUR SIGNER ADDRESS`! + +```caution + +The app sometimes gets confused with login state after you've made changes to `config`. If you see the `Log In` button but clicking it does nothing, try manually navigating to `localhost:3000/dashboard` or clearing the cache. + +``` + +#### Calling a Smart Contract Function + +You've adjusted the foundation of the app to allow you to use the Base Goerli Paymaster with your normal wallet as the signer. Now, it's time to call a smart contract function. + +Start by using the `mint` function in the original example. In the `DashboardPage` component, add a state variable holding an empty element: + +```tsx +const [transactionLink, setTransactionLink] = useState(<>); +``` + +Then, add a variant of the original `onMint` function that sets this variable and has the code related to the toast removed. + +**Note:** make sure you change your wallet address in `args` to make sure the NFT is sent to your EOA wallet address! + +```tsx +const onMint = async () => { + // The mint button is disabled if either of these are undefined + if (!smartAccountProvider || !smartAccountAddress) return; + + try { + // From a viem `RpcTransactionRequest` (e.g. calling an ERC-721's `mint` method), + // build and send a user operation. Gas fees will be sponsored by the Base Paymaster. + const userOpHash = await sendSponsoredUserOperation({ + from: smartAccountAddress, + to: NFT_ADDRESS, + data: encodeFunctionData({ + abi: ABI, + functionName: 'mint', + args: [eoa?.address], + }), + }); + + // Once we have a hash for the user operation, watch it until the transaction has + // been confirmed. + const transactionHash = await smartAccountProvider.waitForUserOperationTransaction(userOpHash); + + setTransactionLink( + + Successfully minted! Click here to see your transaction. + , + ); + } catch (error) { + setTransactionLink(
{'Mint failed with error: ' + error}
); + } +}; +``` + +Finally, above where you added the addresses, add a button to call the function, and display the link to the transaction: + +```tsx +; +{ + transactionLink; +} +``` + +Run it and confirm it works. You need the full transaction receipt for the process to finish, so expect to wait as long as 10 or 15 seconds. + +
+ {/* ... other sections ... */}
+
+
+
+
+);
+```
+
+Sweet! Now our conditional rendering is in full force. If a user clicks on the `+ Add funds to transact` button they will be given three options for topping up their smart wallet:
+
+
+
+## Conclusion
+
+Congratulations! You've built a app that checks a user's smart wallet balance and provides appropriate options based on their funds.
+This app can serve as a foundation for more complex onchain applications that require users to have funded smart wallets.
+
+[Onchain Kit]: https://github.com/coinbase/onchainkit
+[Viem]: https://viem.sh/
+[Smart Wallets]: https://keys.coinbase.com/onboarding
+[viem]: https://viem.sh/docs/introduction
+[react hooks]: https://react.dev/reference/react/hooks
+[Onramp config page]: https://portal.cdp.coinbase.com/products/onramp
+[official documentation]: https://react.dev/
+
diff --git a/docs/pages/cookbook/use-case-guides/gating-and-redirects.mdx b/_pages/cookbook/use-case-guides/gating-and-redirects.mdx
similarity index 99%
rename from docs/pages/cookbook/use-case-guides/gating-and-redirects.mdx
rename to _pages/cookbook/use-case-guides/gating-and-redirects.mdx
index 8083f2e2..5d188cb0 100644
--- a/docs/pages/cookbook/use-case-guides/gating-and-redirects.mdx
+++ b/_pages/cookbook/use-case-guides/gating-and-redirects.mdx
@@ -226,11 +226,10 @@ Note that we're returning a `getFrameHtmlResponse` here, **not** a `getFrameMeta
On your own, try changing the "like" gate to require the user to follow you, recast, or all three!
-:::info
-
+
+
+ {address ? (
+ parseFloat(walletBalance) > 0 ? (
+
+
+ + Your Wallet has {walletBalance} ETH +
+
+
+
+ )
+ }
+ ```
+
+
+
+ {callsStatus &&
+ )
+ }
+ ```
+
+ Status: {callsStatus.status}
}
+
+ 
+ How to get your Paymaster service URL
+
+
+
+ How to get your Paymaster service URL
+
+ 
+ How to set your Paymaster contracts allowlist
+
+
+ Congrats! You've set up your Paymaster service and contracts allowlist.
+ It's time to create Wagmi and Viem clients.
+
+
+ How to set your Paymaster contracts allowlist
+
+
+ );
+ }
+ ```
+
+ ```ts twoslash [myNFT.ts] filename="myNFT.ts"
+ // @noErrors
+ export const myNFTABI = [
+ {
+ stateMutability: "nonpayable",
+ type: "function",
+ inputs: [{ name: "to", type: "address" }],
+ name: "safeMint",
+ outputs: [],
+ },
+ ] as const;
+
+ export const myNFTAddress = "0x119Ea671030FBf79AB93b436D2E20af6ea469a19";
+
+ ```
+ Transact With Paymaster
+{JSON.stringify(capabilities)}
+
+
+ {id &&
+
+
+ );
+ }
+ ```
+
+ ```tsx [src/App.tsx]
+ import React from 'react'
+ import { useAccount, useConnect, useDisconnect } from 'wagmi'
+ import { SignInWithEthereum } from './SignInWithEthereum'; // [!code focus]
+
+ function App() {
+ const account = useAccount()
+ const { connector, connect, status, error } = useConnect()
+ const { disconnect } = useDisconnect()
+
+ return (
+ <>
+ SIWE Example
+
+
+ Account
+
+ status: {account.status}
+
+ addresses: {JSON.stringify(account.addresses)} +
+ chainId: {account.chainId} +
+
+ + addresses: {JSON.stringify(account.addresses)} +
+ chainId: {account.chainId} +
+
+ Connect
+ {connectors.map((connector) => ( + + ))} +{status}
+ {error?.message}
+
+
+ );
+ }
+ ```
+
+ SIWE Example
+ + {signature &&Signature: {signature}
} +
+
+ );
+ }
+ ```
+ SIWE Example
+ + {signature &&Signature: {signature}
} + {valid !== undefined &&Is valid: {valid.toString()}
}{/* // [!code focus] */} +
+ ...
+
+ );
+ }
+ ```
+
+ ...
+
+ );
+ }
+ ```
+
+ -:::danger - +
-:::tip - +
diff --git a/docs/pages/learn/imports/imports-vid.mdx b/_pages/learn/imports/imports-vid.mdx
similarity index 78%
rename from docs/pages/learn/imports/imports-vid.mdx
rename to _pages/learn/imports/imports-vid.mdx
index b0186c78..34fce4e3 100644
--- a/docs/pages/learn/imports/imports-vid.mdx
+++ b/_pages/learn/imports/imports-vid.mdx
@@ -6,6 +6,6 @@ hide_table_of_contents: false
# Imports
-import Video from '@/components/VideoPlayer.jsx'
+import { Video } from '/snippets/VideoPlayer.mdx';
diff --git a/docs/pages/learn/inheritance/abstract-contracts-sbs.mdx b/_pages/learn/inheritance/abstract-contracts-sbs.mdx
similarity index 100%
rename from docs/pages/learn/inheritance/abstract-contracts-sbs.mdx
rename to _pages/learn/inheritance/abstract-contracts-sbs.mdx
diff --git a/docs/pages/learn/inheritance/abstract-contracts-vid.mdx b/_pages/learn/inheritance/abstract-contracts-vid.mdx
similarity index 80%
rename from docs/pages/learn/inheritance/abstract-contracts-vid.mdx
rename to _pages/learn/inheritance/abstract-contracts-vid.mdx
index a2241fc0..f8d59358 100644
--- a/docs/pages/learn/inheritance/abstract-contracts-vid.mdx
+++ b/_pages/learn/inheritance/abstract-contracts-vid.mdx
@@ -6,6 +6,6 @@ hide_table_of_contents: false
# Abstract Contracts
-import Video from '@/components/VideoPlayer.jsx'
+import { Video } from '/snippets/VideoPlayer.mdx';
diff --git a/docs/pages/learn/inheritance/inheritance-exercise.mdx b/_pages/learn/inheritance/inheritance-exercise.mdx
similarity index 98%
rename from docs/pages/learn/inheritance/inheritance-exercise.mdx
rename to _pages/learn/inheritance/inheritance-exercise.mdx
index 7dff5d73..f98cd1f0 100644
--- a/docs/pages/learn/inheritance/inheritance-exercise.mdx
+++ b/_pages/learn/inheritance/inheritance-exercise.mdx
@@ -38,11 +38,10 @@ Implement a contract called `Hourly`. It should:
- Have a public variable storing `hourlyRate`
- Include any other necessary setup and implementation
-:::tip
-
+
The annual cost of an hourly employee is their hourly rate \* 2080 hours.
+
-:::
### Manager
@@ -100,8 +99,7 @@ contract InheritanceSubmission {
## Submit your Contracts and Earn an NFT Badge! (BETA)
-:::info
-
+
#### Hey, where'd my NFT go!?
[Testnets](/learn/deployment-to-testnet/test-networks) are not permanent! Base Goerli [will soon be sunset](https://base.mirror.xyz/kkz1-KFdUwl0n23PdyBRtnFewvO48_m-fZNzPMJehM4), in favor of Base Sepolia.
@@ -109,14 +107,13 @@ contract InheritanceSubmission {
As these are separate networks with separate data, your NFTs **will not** transfer over.
**Don't worry!** We've captured the addresses of all NFT owners on Base Goerli and will include them when we release the mechanism to transfer these NFTs to mainnet later this year! You can also redeploy on Sepolia and resubmit if you'd like!
+
-:::
-
-:::caution
+
Submit your address for your copy of the `InheritanceSubmission` contract that contains your other contract addresses.
+
-:::
import CafeUnitTest from '../../../components/CafeUnitTest/index.jsx'
diff --git a/docs/pages/learn/inheritance/inheritance-sbs.mdx b/_pages/learn/inheritance/inheritance-sbs.mdx
similarity index 100%
rename from docs/pages/learn/inheritance/inheritance-sbs.mdx
rename to _pages/learn/inheritance/inheritance-sbs.mdx
diff --git a/docs/pages/learn/inheritance/inheritance-vid.mdx b/_pages/learn/inheritance/inheritance-vid.mdx
similarity index 78%
rename from docs/pages/learn/inheritance/inheritance-vid.mdx
rename to _pages/learn/inheritance/inheritance-vid.mdx
index aa559cd1..2a8270eb 100644
--- a/docs/pages/learn/inheritance/inheritance-vid.mdx
+++ b/_pages/learn/inheritance/inheritance-vid.mdx
@@ -6,6 +6,6 @@ hide_table_of_contents: false
# Inheritance
-import Video from '@/components/VideoPlayer.jsx'
+import { Video } from '/snippets/VideoPlayer.mdx';
diff --git a/docs/pages/learn/inheritance/multiple-inheritance-vid.mdx b/_pages/learn/inheritance/multiple-inheritance-vid.mdx
similarity index 81%
rename from docs/pages/learn/inheritance/multiple-inheritance-vid.mdx
rename to _pages/learn/inheritance/multiple-inheritance-vid.mdx
index c38ab098..f8ca1a37 100644
--- a/docs/pages/learn/inheritance/multiple-inheritance-vid.mdx
+++ b/_pages/learn/inheritance/multiple-inheritance-vid.mdx
@@ -6,6 +6,6 @@ hide_table_of_contents: false
# Multiple Inheritance
-import Video from '@/components/VideoPlayer.jsx'
+import { Video } from '/snippets/VideoPlayer.mdx';
diff --git a/docs/pages/learn/inheritance/multiple-inheritance.mdx b/_pages/learn/inheritance/multiple-inheritance.mdx
similarity index 100%
rename from docs/pages/learn/inheritance/multiple-inheritance.mdx
rename to _pages/learn/inheritance/multiple-inheritance.mdx
diff --git a/docs/pages/learn/interfaces/calling-another-contract-vid.mdx b/_pages/learn/interfaces/calling-another-contract-vid.mdx
similarity index 85%
rename from docs/pages/learn/interfaces/calling-another-contract-vid.mdx
rename to _pages/learn/interfaces/calling-another-contract-vid.mdx
index 01776b86..9e2da311 100644
--- a/docs/pages/learn/interfaces/calling-another-contract-vid.mdx
+++ b/_pages/learn/interfaces/calling-another-contract-vid.mdx
@@ -6,12 +6,11 @@ hide_table_of_contents: false
# Calling Another Contract
-:::caution
-
+
This tutorial has been moved as part of a reorganization! It assumes you are using Hardhat. Everything in this lesson will work with minor adjustments if you are working in Foundry or Remix.
+
-:::
-import Video from '@/components/VideoPlayer.jsx'
+import { Video } from '/snippets/VideoPlayer.mdx';
diff --git a/docs/pages/learn/interfaces/contract-to-contract-interaction.mdx b/_pages/learn/interfaces/contract-to-contract-interaction.mdx
similarity index 99%
rename from docs/pages/learn/interfaces/contract-to-contract-interaction.mdx
rename to _pages/learn/interfaces/contract-to-contract-interaction.mdx
index 01b989f1..7622b558 100644
--- a/docs/pages/learn/interfaces/contract-to-contract-interaction.mdx
+++ b/_pages/learn/interfaces/contract-to-contract-interaction.mdx
@@ -8,11 +8,10 @@ hide_table_of_contents: false
In this article, you'll learn how to interact with other smart contracts using interfaces and the `.call()` function, which allows you to interact with other smart contracts without using an interface.
-:::caution
-
+
This tutorial has been moved as part of a reorganization! It assumes you are using Hardhat. Everything in this lesson will work with minor adjustments if you are working in Foundry or Remix.
+
-:::
---
diff --git a/docs/pages/learn/interfaces/intro-to-interfaces-vid.mdx b/_pages/learn/interfaces/intro-to-interfaces-vid.mdx
similarity index 85%
rename from docs/pages/learn/interfaces/intro-to-interfaces-vid.mdx
rename to _pages/learn/interfaces/intro-to-interfaces-vid.mdx
index b331b7be..12a3d326 100644
--- a/docs/pages/learn/interfaces/intro-to-interfaces-vid.mdx
+++ b/_pages/learn/interfaces/intro-to-interfaces-vid.mdx
@@ -6,12 +6,11 @@ hide_table_of_contents: false
# Intro to Interfaces
-:::caution
-
+
This tutorial has been moved as part of a reorganization! It assumes you are using Hardhat. Everything in this lesson will work with minor adjustments if you are working in Foundry or Remix.
+
-:::
-import Video from '@/components/VideoPlayer.jsx'
+import { Video } from '/snippets/VideoPlayer.mdx';
diff --git a/docs/pages/learn/interfaces/testing-the-interface-vid.mdx b/_pages/learn/interfaces/testing-the-interface-vid.mdx
similarity index 84%
rename from docs/pages/learn/interfaces/testing-the-interface-vid.mdx
rename to _pages/learn/interfaces/testing-the-interface-vid.mdx
index 444da199..d5934b01 100644
--- a/docs/pages/learn/interfaces/testing-the-interface-vid.mdx
+++ b/_pages/learn/interfaces/testing-the-interface-vid.mdx
@@ -6,12 +6,11 @@ hide_table_of_contents: false
# Testing the Interface
-:::caution
-
+
This tutorial has been moved as part of a reorganization! It assumes you are using Hardhat. Everything in this lesson will work with minor adjustments if you are working in Foundry or Remix.
+
-:::
-import Video from '@/components/VideoPlayer.jsx'
+import { Video } from '/snippets/VideoPlayer.mdx';
diff --git a/docs/pages/learn/intro-to-tokens/intro-to-tokens-vid.mdx b/_pages/learn/intro-to-tokens/intro-to-tokens-vid.mdx
similarity index 79%
rename from docs/pages/learn/intro-to-tokens/intro-to-tokens-vid.mdx
rename to _pages/learn/intro-to-tokens/intro-to-tokens-vid.mdx
index a4393659..1fde6e2b 100644
--- a/docs/pages/learn/intro-to-tokens/intro-to-tokens-vid.mdx
+++ b/_pages/learn/intro-to-tokens/intro-to-tokens-vid.mdx
@@ -6,6 +6,6 @@ hide_table_of_contents: false
# Introduction
-import Video from '@/components/VideoPlayer.jsx'
+import { Video } from '/snippets/VideoPlayer.mdx';
diff --git a/docs/pages/learn/intro-to-tokens/misconceptions-about-tokens-vid.mdx b/_pages/learn/intro-to-tokens/misconceptions-about-tokens-vid.mdx
similarity index 81%
rename from docs/pages/learn/intro-to-tokens/misconceptions-about-tokens-vid.mdx
rename to _pages/learn/intro-to-tokens/misconceptions-about-tokens-vid.mdx
index dcb8000e..4b6aa5e0 100644
--- a/docs/pages/learn/intro-to-tokens/misconceptions-about-tokens-vid.mdx
+++ b/_pages/learn/intro-to-tokens/misconceptions-about-tokens-vid.mdx
@@ -6,6 +6,6 @@ hide_table_of_contents: false
# Common Misconceptions
-import Video from '@/components/VideoPlayer.jsx'
+import { Video } from '/snippets/VideoPlayer.mdx';
diff --git a/docs/pages/learn/intro-to-tokens/tokens-overview.mdx b/_pages/learn/intro-to-tokens/tokens-overview.mdx
similarity index 100%
rename from docs/pages/learn/intro-to-tokens/tokens-overview.mdx
rename to _pages/learn/intro-to-tokens/tokens-overview.mdx
diff --git a/docs/pages/learn/introduction-to-ethereum/ethereum-applications.mdx b/_pages/learn/introduction-to-ethereum/ethereum-applications.mdx
similarity index 100%
rename from docs/pages/learn/introduction-to-ethereum/ethereum-applications.mdx
rename to _pages/learn/introduction-to-ethereum/ethereum-applications.mdx
diff --git a/docs/pages/learn/introduction-to-ethereum/ethereum-dev-overview-vid.mdx b/_pages/learn/introduction-to-ethereum/ethereum-dev-overview-vid.mdx
similarity index 81%
rename from docs/pages/learn/introduction-to-ethereum/ethereum-dev-overview-vid.mdx
rename to _pages/learn/introduction-to-ethereum/ethereum-dev-overview-vid.mdx
index 304ee259..9c9a389f 100644
--- a/docs/pages/learn/introduction-to-ethereum/ethereum-dev-overview-vid.mdx
+++ b/_pages/learn/introduction-to-ethereum/ethereum-dev-overview-vid.mdx
@@ -6,6 +6,6 @@ hide_table_of_contents: false
# Ethereum Applications
-import Video from '@/components/VideoPlayer.jsx'
+import { Video } from '/snippets/VideoPlayer.mdx';
diff --git a/docs/pages/learn/introduction-to-ethereum/evm-diagram.mdx b/_pages/learn/introduction-to-ethereum/evm-diagram.mdx
similarity index 99%
rename from docs/pages/learn/introduction-to-ethereum/evm-diagram.mdx
rename to _pages/learn/introduction-to-ethereum/evm-diagram.mdx
index d112f5da..4385522c 100644
--- a/docs/pages/learn/introduction-to-ethereum/evm-diagram.mdx
+++ b/_pages/learn/introduction-to-ethereum/evm-diagram.mdx
@@ -85,7 +85,7 @@ During contract execution, memory serves as a collection of bytes, organized in
To understand the inner workings of the EVM, the following diagram offers a streamlined visualization of its transaction execution process. It begins with the transaction initiation, and progresses to the gas computations for each operation. Integral to the process are the EVM's stack, memory, and storage, which are engaged to manage and persist data throughout the lifecycle of a transaction. Checks and validations at each step ensure the validity of operations, safeguarding the network's integrity. This systemized sequence of actions forms the bedrock of transaction and smart contract execution, ensuring Ethereum's consistent and secure operation.
-:::info
+
**Data Bytecode in the EVM**
Every transaction or smart contract call within the EVM uses "bytecode", which
@@ -105,7 +105,8 @@ Decoding the example sequence: `0x6080604052`
```
This bytecode sequence is not a random set of characters. Each segment corresponds to specific operations or data in the EVM. Opcodes dictate actions, while subsequent data provides specifics.
-:::
+
+
---
diff --git a/docs/pages/learn/introduction-to-ethereum/gas-use-in-eth-transactions.mdx b/_pages/learn/introduction-to-ethereum/gas-use-in-eth-transactions.mdx
similarity index 100%
rename from docs/pages/learn/introduction-to-ethereum/gas-use-in-eth-transactions.mdx
rename to _pages/learn/introduction-to-ethereum/gas-use-in-eth-transactions.mdx
diff --git a/docs/pages/learn/introduction-to-ethereum/intro-to-ethereum-vid.mdx b/_pages/learn/introduction-to-ethereum/intro-to-ethereum-vid.mdx
similarity index 79%
rename from docs/pages/learn/introduction-to-ethereum/intro-to-ethereum-vid.mdx
rename to _pages/learn/introduction-to-ethereum/intro-to-ethereum-vid.mdx
index 510a06eb..2c112c32 100644
--- a/docs/pages/learn/introduction-to-ethereum/intro-to-ethereum-vid.mdx
+++ b/_pages/learn/introduction-to-ethereum/intro-to-ethereum-vid.mdx
@@ -6,6 +6,6 @@ hide_table_of_contents: false
# Introduction
-import Video from '@/components/VideoPlayer.jsx'
+import { Video } from '/snippets/VideoPlayer.mdx';
diff --git a/docs/pages/learn/introduction-to-solidity/anatomy-of-a-smart-contract-vid.mdx b/_pages/learn/introduction-to-solidity/anatomy-of-a-smart-contract-vid.mdx
similarity index 81%
rename from docs/pages/learn/introduction-to-solidity/anatomy-of-a-smart-contract-vid.mdx
rename to _pages/learn/introduction-to-solidity/anatomy-of-a-smart-contract-vid.mdx
index 88b55c34..d43d50d0 100644
--- a/docs/pages/learn/introduction-to-solidity/anatomy-of-a-smart-contract-vid.mdx
+++ b/_pages/learn/introduction-to-solidity/anatomy-of-a-smart-contract-vid.mdx
@@ -6,6 +6,6 @@ hide_table_of_contents: false
# Anatomy of a Smart Contract
-import Video from '@/components/VideoPlayer.jsx'
+import { Video } from '/snippets/VideoPlayer.mdx';
diff --git a/docs/pages/learn/introduction-to-solidity/deployment-in-remix-vid.mdx b/_pages/learn/introduction-to-solidity/deployment-in-remix-vid.mdx
similarity index 80%
rename from docs/pages/learn/introduction-to-solidity/deployment-in-remix-vid.mdx
rename to _pages/learn/introduction-to-solidity/deployment-in-remix-vid.mdx
index c7174a00..1625e677 100644
--- a/docs/pages/learn/introduction-to-solidity/deployment-in-remix-vid.mdx
+++ b/_pages/learn/introduction-to-solidity/deployment-in-remix-vid.mdx
@@ -6,6 +6,6 @@ hide_table_of_contents: false
# Deployment in Remix
-import Video from '@/components/VideoPlayer.jsx'
+import { Video } from '/snippets/VideoPlayer.mdx';
diff --git a/docs/pages/learn/introduction-to-solidity/deployment-in-remix.mdx b/_pages/learn/introduction-to-solidity/deployment-in-remix.mdx
similarity index 100%
rename from docs/pages/learn/introduction-to-solidity/deployment-in-remix.mdx
rename to _pages/learn/introduction-to-solidity/deployment-in-remix.mdx
diff --git a/docs/pages/learn/introduction-to-solidity/introduction-to-remix-vid.mdx b/_pages/learn/introduction-to-solidity/introduction-to-remix-vid.mdx
similarity index 79%
rename from docs/pages/learn/introduction-to-solidity/introduction-to-remix-vid.mdx
rename to _pages/learn/introduction-to-solidity/introduction-to-remix-vid.mdx
index bd7c9012..028871b5 100644
--- a/docs/pages/learn/introduction-to-solidity/introduction-to-remix-vid.mdx
+++ b/_pages/learn/introduction-to-solidity/introduction-to-remix-vid.mdx
@@ -6,6 +6,6 @@ hide_table_of_contents: false
# Introduction to Remix
-import Video from '@/components/VideoPlayer.jsx'
+import { Video } from '/snippets/VideoPlayer.mdx';
diff --git a/docs/pages/learn/introduction-to-solidity/introduction-to-remix.mdx b/_pages/learn/introduction-to-solidity/introduction-to-remix.mdx
similarity index 99%
rename from docs/pages/learn/introduction-to-solidity/introduction-to-remix.mdx
rename to _pages/learn/introduction-to-solidity/introduction-to-remix.mdx
index 2ae3d515..53cb29a8 100644
--- a/docs/pages/learn/introduction-to-solidity/introduction-to-remix.mdx
+++ b/_pages/learn/introduction-to-solidity/introduction-to-remix.mdx
@@ -69,14 +69,13 @@ The _Deploy & Run Transactions_ plugin is what you'll use to deploy your contrac
Fix any errors you introduced to `1_Storage.sol` and then click the orange `Deploy` button. You'll see your contract appear below as _STORAGE AT \_.
-:::caution
-
+
There are two common gotchas that can be very confusing when deploying contracts in Remix.
1. Each time you hit the Deploy button, a new copy of your contract is deployed but the previous deployments remain. Unless you are comparing or debugging between different versions of a contract, or deploying multiple contracts at once, you should click the `Trash` button to erase old deployments before deploying again.
1. If your code will not compile, **clicking the deploy button will not generate an error!** Instead, the last compiled version will be deployed. Visually check and confirm that there are no errors indicated by a number in a red circle on top of the Compiler plugin.
+
-:::
---
diff --git a/docs/pages/learn/introduction-to-solidity/introduction-to-solidity-overview.mdx b/_pages/learn/introduction-to-solidity/introduction-to-solidity-overview.mdx
similarity index 100%
rename from docs/pages/learn/introduction-to-solidity/introduction-to-solidity-overview.mdx
rename to _pages/learn/introduction-to-solidity/introduction-to-solidity-overview.mdx
diff --git a/docs/pages/learn/introduction-to-solidity/introduction-to-solidity-vid.mdx b/_pages/learn/introduction-to-solidity/introduction-to-solidity-vid.mdx
similarity index 79%
rename from docs/pages/learn/introduction-to-solidity/introduction-to-solidity-vid.mdx
rename to _pages/learn/introduction-to-solidity/introduction-to-solidity-vid.mdx
index bb0aa8f7..621f63d9 100644
--- a/docs/pages/learn/introduction-to-solidity/introduction-to-solidity-vid.mdx
+++ b/_pages/learn/introduction-to-solidity/introduction-to-solidity-vid.mdx
@@ -6,6 +6,6 @@ hide_table_of_contents: false
# Introduction
-import Video from '@/components/VideoPlayer.jsx'
+import { Video } from '/snippets/VideoPlayer.mdx';
diff --git a/docs/pages/learn/introduction-to-solidity/solidity-overview.mdx b/_pages/learn/introduction-to-solidity/solidity-overview.mdx
similarity index 99%
rename from docs/pages/learn/introduction-to-solidity/solidity-overview.mdx
rename to _pages/learn/introduction-to-solidity/solidity-overview.mdx
index 94d7230d..b00be240 100644
--- a/docs/pages/learn/introduction-to-solidity/solidity-overview.mdx
+++ b/_pages/learn/introduction-to-solidity/solidity-overview.mdx
@@ -4,6 +4,8 @@ description: An overview of the Solidity programming language.
hide_table_of_contents: false
---
+import { Danger } from "/snippets/danger.mdx";
+
# Solidity Overview
In this article, you'll learn about the origins and history of Solidity, where to find the docs, and review some of the considerations that make programming in Solidity relatively unique. You'll also learn about how to get started with development!
@@ -115,13 +117,12 @@ We'll start with [Remix], an online IDE similar to Codepen, Replit, or CodeSandb
-:::danger
-
+
**BE VERY CAREFUL** while using Remix, as it can also be used by scammers. Remix itself will warn you about this, so take heed! One common scam is for the scammer to convince you to paste and deploy code that is allegedly some sort of automated moneymaker, such as a staking tool, or a bot.
If you paste and run code that you don't understand, you may lose all assets from your currently connected wallet. You should also be careful to always navigate directly to `remix.ethereum.org`. More experienced developers prefer to use static versions of Remix deployed to [IPFS], but be careful. There are also deployments that are compromised and used as a part of a scam!
+
-:::
### Hardhat
diff --git a/_pages/learn/learning-objectives.mdx b/_pages/learn/learning-objectives.mdx
new file mode 100644
index 00000000..59955449
--- /dev/null
+++ b/_pages/learn/learning-objectives.mdx
@@ -0,0 +1,258 @@
+---
+title: "Learning Objectives"
+---
+
+
+### [Ethereum Applications](/learn/introduction-to-ethereum/ethereum-applications)
+
+- Describe the origin and goals of the Ethereum blockchain
+- List common types of applications that can be developed with the Ethereum blockchain
+- Compare and contrast Web2 vs. Web3 development
+- Compare and contrast the concept of "ownership" in Web2 vs. Web3
+
+### [Gas Use in Ethereum Transactions](/learn/introduction-to-ethereum/gas-use-in-eth-transactions)
+
+- Explain what gas is in Ethereum
+- Explain why gas is necessary in Ethereum
+- Understand how gas works in Ethereum transactions
+
+### [EVM Diagram](/learn/introduction-to-ethereum/evm-diagram)
+
+- Diagram the EVM
+
+### [Setup and Overview](/learn/hardhat-setup-overview/hardhat-setup-overview-sbs)
+
+- Install and create a new Hardhat project with Typescript support
+- Describe the organization and folder structure of a Hardhat project
+- List the use and properties of hardhat.config.ts
+
+### [Testing with Hardhat and Typechain](/learn/hardhat-testing/hardhat-testing-sbs)
+
+- Set up TypeChain to enable testing
+- Write unit tests for smart contracts using Mocha, Chai, and the Hardhat Toolkit
+- Set up multiple signers and call smart contract functions with different signers
+
+### [Etherscan](/learn/etherscan/etherscan-sbs)
+
+- List some of the features of Etherscan
+- Read data from the Bored Ape Yacht Club contract on Etherscan
+- Write data to a contract using Etherscan.
+
+### [Deploying Smart Contracts](/learn/hardhat-deploy/hardhat-deploy-sbs)
+
+- Deploy a smart contract to the Base Sepolia Testnet with hardhat-deploy
+- Deploy a smart contract to the Sepolia Testnet with hardhat-deploy
+- Use BaseScan to view a deployed smart contract
+
+### [Verifying Smart Contracts](/learn/hardhat-verify/hardhat-verify-sbs)
+
+- Verify a deployed smart contract on Etherscan
+- Connect a wallet to a contract in Etherscan
+- Use etherscan to interact with your own deployed contract
+
+### [Hardhat Forking](/learn/hardhat-forking/hardhat-forking)
+
+- Use Hardhat Network to create a local fork of mainnet and deploy a contract to it
+- Utilize Hardhat forking features to configure the fork for several use cases
+
+### ['Introduction to Remix'](/learn/introduction-to-solidity/introduction-to-remix)
+
+- List the features, pros, and cons of using Remix as an IDE
+- Deploy and test the Storage.sol demo contract in Remix
+
+### [Deployment in Remix](/learn/introduction-to-solidity/deployment-in-remix)
+
+- Deploy and test the Storage.sol demo contract in Remix
+
+### [Hello World](/learn/contracts-and-basic-functions/hello-world-step-by-step)
+
+- Construct a simple "Hello World" contract
+- List the major differences between data types in Solidity as compared to other languages
+- Select the appropriate visibility for a function
+
+### [Basic Types](/learn/contracts-and-basic-functions/basic-types)
+
+- Categorize basic data types
+- List the major differences between data types in Solidity as compared to other languages
+- Compare and contrast signed and unsigned integers
+
+### [Test Networks](/learn/deployment-to-testnet/test-networks)
+
+- Describe the uses and properties of the Base testnet
+- Compare and contrast Ropsten, Rinkeby, Goerli, and Sepolia
+
+### [Deployment to Base Sepolia](/learn/deployment-to-testnet/deployment-to-base-sepolia-sbs)
+
+- Deploy a contract to the Base Sepolia testnet and interact with it in [BaseScan]
+
+### [Contract Verification](/learn/deployment-to-testnet/contract-verification-sbs)
+
+- Verify a contract on the Base Sepolia testnet and interact with it in [BaseScan]
+
+### [Control Structures](/learn/control-structures/control-structures)
+
+- Control code flow with `if`, `else`, `while`, and `for`
+- List the unique constraints for control flow in Solidity
+- Utilize `require` to write a function that can only be used when a variable is set to `true`
+- Write a `revert` statement to abort execution of a function in a specific state
+- Utilize `error` to control flow more efficiently than with `require`
+
+### [Storing Data](/learn/storage/simple-storage-sbs)
+
+- Use the constructor to initialize a variable
+- Access the data in a public variable with the automatically generated getter
+- Order variable declarations to use storage efficiently
+
+### [How Storage Works](/learn/storage/how-storage-works)
+
+- Diagram how a contract's data is stored on the blockchain (Contract -> Blockchain)
+- Order variable declarations to use storage efficiently
+- Diagram how variables in a contract are stored (Variable -> Contract)
+
+### [Arrays](/learn/arrays/arrays-in-solidity)
+
+- Describe the difference between storage, memory, and calldata arrays
+
+### [Filtering an Array](/learn/arrays/filtering-an-array-sbs)
+
+- Write a function that can return a filtered subset of an array
+
+### [Mappings](/learn/mappings/mappings-sbs)
+
+- Construct a Map (dictionary) data type
+- Recall that assignment of the Map data type is not as flexible as for other data types/in other languages
+- Restrict function calls with the `msg.sender` global variable
+- Recall that there is no collision protection in the EVM and why this is (probably) ok
+
+### [Function Visibility and State Mutability](/learn/advanced-functions/function-visibility)
+
+- Categorize functions as public, private, internal, or external based on their usage
+- Describe how pure and view functions are different than functions that modify storage
+
+### [Function Modifiers](/learn/advanced-functions/function-modifiers)
+
+- Use modifiers to efficiently add functionality to multiple functions
+
+### [Structs](/learn/structs/structs-sbs)
+
+- Construct a `struct` (user-defined type) that contains several different data types
+- Declare members of the `struct` to maximize storage efficiency
+- Describe constraints related to the assignment of `struct`s depending on the types they contain
+
+### [Inheritance](/learn/inheritance/inheritance-sbs)
+
+- Write a smart contract that inherits from another contract
+- Describe the impact inheritance has on the byte code size limit
+
+### [Multiple Inheritance](/learn/inheritance/multiple-inheritance)
+
+- Write a smart contract that inherits from multiple contracts
+
+### [Abstract Contracts](/learn/inheritance/abstract-contracts-sbs)
+
+- Use the virtual, override, and abstract keywords to create and use an abstract contract
+
+### [Imports](/learn/imports/imports-sbs)
+
+- Import and use code from another file
+- Utilize OpenZeppelin contracts within Remix
+
+### [Error Triage](/learn/error-triage/error-triage)
+
+- Debug common solidity errors including transaction reverted, out of gas, stack overflow, value overflow/underflow, index out of range, etc.
+
+### [The New Keyword](/learn/new-keyword/new-keyword-sbs)
+
+- Write a contract that creates a new contract with the new keyword
+
+### ['Contract to Contract Interaction'](/learn/interfaces/contract-to-contract-interaction)
+
+- Use interfaces to allow a smart contract to call functions in another smart contract
+- Use the `call()` function to interact with another contract without using an interface
+
+### [Events](/learn/events/hardhat-events-sbs)
+
+- Write and trigger an event
+- List common uses of events
+- Understand events vs. smart contract storage
+
+### [Address and Payable in Solidity](/learn/address-and-payable/address-and-payable)
+
+- Differentiate between address and address payable types in Solidity
+- Determine when to use each type appropriately in contract development
+- Employ address payable to send Ether and interact with payable functions
+
+### [Minimal Token](/learn/minimal-tokens/minimal-token-sbs)
+
+- Construct a minimal token and deploy to testnet
+- Identify the properties that make a token a token
+
+### [The ERC-20 Token Standard](/learn/erc-20-token/erc-20-standard)
+
+- Analyze the anatomy of an ERC-20 token
+- Review the formal specification for ERC-20
+
+### [ERC-20 Implementation](/learn/erc-20-token/erc-20-token-sbs)
+
+- Describe OpenZeppelin
+- Import the OpenZeppelin ERC-20 implementation
+- Describe the difference between the ERC-20 standard and OpenZeppelin's ERC20.sol
+- Build and deploy an ERC-20 compliant token
+
+### [The ERC-721 Token Standard](/learn/erc-721-token/erc-721-standard)
+
+- Analyze the anatomy of an ERC-721 token
+- Compare and contrast the technical specifications of ERC-20 and ERC-721
+- Review the formal specification for ERC-721
+
+### [ERC-721 Token](/learn/erc-721-token/erc-721-sbs)
+
+- Analyze the anatomy of an ERC-721 token
+- Compare and contrast the technical specifications of ERC-20 and ERC-721
+- Review the formal specification for ERC-721
+- Build and deploy an ERC-721 compliant token
+- Use an ERC-721 token to control ownership of another data structure
+
+### [Wallet Connectors](/learn/frontend-setup/wallet-connectors)
+
+- Identify the role of a wallet aggregator in an onchain app
+- Debate the pros and cons of using a template
+- Scaffold a new onchain app with RainbowKit
+- Support users of EOAs and the Coinbase Smart Wallet with the same app
+
+### [Building an Onchain App](/learn/frontend-setup/building-an-onchain-app)
+
+- Identify the role of a wallet aggregator in an onchain app
+- Debate the pros and cons of using a template
+- Add a wallet connection to a standard template app
+
+### [The `useAccount` Hook](/learn/reading-and-displaying-data/useAccount)
+
+- Implement the `useAccount` hook to show the user's address, connection state, network, and balance
+- Implement an `isMounted` hook to prevent hydration errors
+
+### [The `useReadContract` Hook](/learn/reading-and-displaying-data/useReadContract)
+
+- Implement wagmi's `useReadContract` hook to fetch data from a smart contract
+- Convert data fetched from a smart contract to information displayed to the user
+- Identify the caveats of reading data from automatically-generated getters
+
+### [Configuring `useReadContract`](/learn/reading-and-displaying-data/configuring-useReadContract)
+
+- Use `useBlockNumber` and the `queryClient` to automatically fetch updates from the blockchain
+- Describe the costs of using the above, and methods to reduce those costs
+- Configure arguments to be passed with a call to a `pure` or `view` smart contract function
+- Call an instance of `useReadContract` on demand
+- Utilize `isLoading` and `isFetching` to improve user experience
+
+### [The `useWriteContract` hook](/learn/writing-to-contracts/useWriteContract)
+
+- Implement wagmi's `useWriteContract` hook to send transactions to a smart contract
+- Configure the options in `useWriteContract`
+- Display the execution, success, or failure of a function with button state changes, and data display
+
+### [The `useSimulateContract` hook](/learn/writing-to-contracts/useSimulateContract)
+
+- Implement wagmi's `useSimulateContract` and `useWriteContract` to send transactions to a smart contract
+- Configure the options in `useSimulateContract` and `useWriteContract`
+- Call a smart contract function on-demand using the write function from `useWriteContract`, with arguments and a value
\ No newline at end of file
diff --git a/docs/pages/learn/mappings/how-mappings-are-stored-vid.mdx b/_pages/learn/mappings/how-mappings-are-stored-vid.mdx
similarity index 79%
rename from docs/pages/learn/mappings/how-mappings-are-stored-vid.mdx
rename to _pages/learn/mappings/how-mappings-are-stored-vid.mdx
index 3d2e4fa9..84aee1c3 100644
--- a/docs/pages/learn/mappings/how-mappings-are-stored-vid.mdx
+++ b/_pages/learn/mappings/how-mappings-are-stored-vid.mdx
@@ -6,6 +6,6 @@ hide_table_of_contents: false
# How Mappings are Stored
-import Video from '@/components/VideoPlayer.jsx'
+import { Video } from '/snippets/VideoPlayer.mdx';
diff --git a/docs/pages/learn/mappings/mappings-exercise.mdx b/_pages/learn/mappings/mappings-exercise.mdx
similarity index 99%
rename from docs/pages/learn/mappings/mappings-exercise.mdx
rename to _pages/learn/mappings/mappings-exercise.mdx
index 0bc76732..724af816 100644
--- a/docs/pages/learn/mappings/mappings-exercise.mdx
+++ b/_pages/learn/mappings/mappings-exercise.mdx
@@ -55,8 +55,7 @@ Add a function called `resetUserFavorites` that resets `userFavorites` for the s
### Submit your Contract and Earn an NFT Badge! (BETA)
-:::info
-
+
#### Hey, where'd my NFT go!?
[Testnets](/learn/deployment-to-testnet/test-networks) are not permanent! Base Goerli [will soon be sunset](https://base.mirror.xyz/kkz1-KFdUwl0n23PdyBRtnFewvO48_m-fZNzPMJehM4), in favor of Base Sepolia.
@@ -64,8 +63,8 @@ Add a function called `resetUserFavorites` that resets `userFavorites` for the s
As these are separate networks with separate data, your NFTs **will not** transfer over.
**Don't worry!** We've captured the addresses of all NFT owners on Base Goerli and will include them when we release the mechanism to transfer these NFTs to mainnet later this year! You can also redeploy on Sepolia and resubmit if you'd like!
+
-:::
import CafeUnitTest from '../../../components/CafeUnitTest/index.jsx'
diff --git a/docs/pages/learn/mappings/mappings-sbs.mdx b/_pages/learn/mappings/mappings-sbs.mdx
similarity index 100%
rename from docs/pages/learn/mappings/mappings-sbs.mdx
rename to _pages/learn/mappings/mappings-sbs.mdx
diff --git a/docs/pages/learn/mappings/mappings-vid.mdx b/_pages/learn/mappings/mappings-vid.mdx
similarity index 74%
rename from docs/pages/learn/mappings/mappings-vid.mdx
rename to _pages/learn/mappings/mappings-vid.mdx
index 53a2c757..bab69568 100644
--- a/docs/pages/learn/mappings/mappings-vid.mdx
+++ b/_pages/learn/mappings/mappings-vid.mdx
@@ -6,6 +6,6 @@ hide_table_of_contents: false
# Mappings
-import Video from '@/components/VideoPlayer.jsx'
+import { Video } from '/snippets/VideoPlayer.mdx';
diff --git a/docs/pages/learn/mappings/using-msg-sender-vid.mdx b/_pages/learn/mappings/using-msg-sender-vid.mdx
similarity index 78%
rename from docs/pages/learn/mappings/using-msg-sender-vid.mdx
rename to _pages/learn/mappings/using-msg-sender-vid.mdx
index 884588d1..9403dfa3 100644
--- a/docs/pages/learn/mappings/using-msg-sender-vid.mdx
+++ b/_pages/learn/mappings/using-msg-sender-vid.mdx
@@ -6,6 +6,6 @@ hide_table_of_contents: false
# Using `msg.sender`
-import Video from '@/components/VideoPlayer.jsx'
+import { Video } from '/snippets/VideoPlayer.mdx';
diff --git a/docs/pages/learn/minimal-tokens/creating-a-minimal-token-vid.mdx b/_pages/learn/minimal-tokens/creating-a-minimal-token-vid.mdx
similarity index 80%
rename from docs/pages/learn/minimal-tokens/creating-a-minimal-token-vid.mdx
rename to _pages/learn/minimal-tokens/creating-a-minimal-token-vid.mdx
index 9db59542..b2bb1d0f 100644
--- a/docs/pages/learn/minimal-tokens/creating-a-minimal-token-vid.mdx
+++ b/_pages/learn/minimal-tokens/creating-a-minimal-token-vid.mdx
@@ -6,6 +6,6 @@ hide_table_of_contents: false
# Create a Minimal Token
-import Video from '@/components/VideoPlayer.jsx'
+import { Video } from '/snippets/VideoPlayer.mdx';
diff --git a/docs/pages/learn/minimal-tokens/minimal-token-sbs.mdx b/_pages/learn/minimal-tokens/minimal-token-sbs.mdx
similarity index 99%
rename from docs/pages/learn/minimal-tokens/minimal-token-sbs.mdx
rename to _pages/learn/minimal-tokens/minimal-token-sbs.mdx
index fcab0324..dd878885 100644
--- a/docs/pages/learn/minimal-tokens/minimal-token-sbs.mdx
+++ b/_pages/learn/minimal-tokens/minimal-token-sbs.mdx
@@ -169,11 +169,10 @@ A more guaranteed way to destroy, or _burn_ a token, is to transfer it to the de
The `totalSupply` remains unchanged, and the balance of the zero address is visible, but those tokens are stuck there forever.
-:::info
-
+
The [zero address] currently has a balance of more than 11,000 ETH, worth over **20 million dollars**! Its total holding of burned assets is estimated to be worth more than **200 million dollars**!!!
+
-:::
---
diff --git a/docs/pages/learn/minimal-tokens/minimal-tokens-exercise.mdx b/_pages/learn/minimal-tokens/minimal-tokens-exercise.mdx
similarity index 98%
rename from docs/pages/learn/minimal-tokens/minimal-tokens-exercise.mdx
rename to _pages/learn/minimal-tokens/minimal-tokens-exercise.mdx
index 8697a890..4c920784 100644
--- a/docs/pages/learn/minimal-tokens/minimal-tokens-exercise.mdx
+++ b/_pages/learn/minimal-tokens/minimal-tokens-exercise.mdx
@@ -46,8 +46,7 @@ A failure of either of these checks should result in a revert with an `UnsafeTra
### Submit your Contract and Earn an NFT Badge! (BETA)
-:::info
-
+
#### Hey, where'd my NFT go!?
[Testnets](/learn/deployment-to-testnet/test-networks) are not permanent! Base Goerli [will soon be sunset](https://base.mirror.xyz/kkz1-KFdUwl0n23PdyBRtnFewvO48_m-fZNzPMJehM4), in favor of Base Sepolia.
@@ -55,16 +54,15 @@ A failure of either of these checks should result in a revert with an `UnsafeTra
As these are separate networks with separate data, your NFTs **will not** transfer over.
**Don't worry!** We've captured the addresses of all NFT owners on Base Goerli and will include them when we release the mechanism to transfer these NFTs to mainnet later this year! You can also redeploy on Sepolia and resubmit if you'd like!
+
-:::
-
-:::caution
+
The contract specification contains actions that can only be performed once by a given address. As a result, the unit tests for a passing contract will only be successful the **first** time you test.
**You may need to submit a fresh deployment to pass**
+
-:::
import CafeUnitTest from '../../../components/CafeUnitTest/index.jsx'
diff --git a/docs/pages/learn/minimal-tokens/transferring-a-minimal-token-vid.mdx b/_pages/learn/minimal-tokens/transferring-a-minimal-token-vid.mdx
similarity index 82%
rename from docs/pages/learn/minimal-tokens/transferring-a-minimal-token-vid.mdx
rename to _pages/learn/minimal-tokens/transferring-a-minimal-token-vid.mdx
index fc7ce412..6d250d2a 100644
--- a/docs/pages/learn/minimal-tokens/transferring-a-minimal-token-vid.mdx
+++ b/_pages/learn/minimal-tokens/transferring-a-minimal-token-vid.mdx
@@ -6,6 +6,6 @@ hide_table_of_contents: false
# Transferring a Minimal Token
-import Video from '@/components/VideoPlayer.jsx'
+import { Video } from '/snippets/VideoPlayer.mdx';
diff --git a/docs/pages/learn/new-keyword/creating-a-new-contract-vid.mdx b/_pages/learn/new-keyword/creating-a-new-contract-vid.mdx
similarity index 83%
rename from docs/pages/learn/new-keyword/creating-a-new-contract-vid.mdx
rename to _pages/learn/new-keyword/creating-a-new-contract-vid.mdx
index f5538056..f9795c0b 100644
--- a/docs/pages/learn/new-keyword/creating-a-new-contract-vid.mdx
+++ b/_pages/learn/new-keyword/creating-a-new-contract-vid.mdx
@@ -6,6 +6,6 @@ hide_table_of_contents: false
# Creating a `new` Contract
-import Video from '@/components/VideoPlayer.jsx'
+import { Video } from '/snippets/VideoPlayer.mdx';
diff --git a/docs/pages/learn/new-keyword/new-keyword-exercise.mdx b/_pages/learn/new-keyword/new-keyword-exercise.mdx
similarity index 98%
rename from docs/pages/learn/new-keyword/new-keyword-exercise.mdx
rename to _pages/learn/new-keyword/new-keyword-exercise.mdx
index 4aaadb9b..89a42de8 100644
--- a/docs/pages/learn/new-keyword/new-keyword-exercise.mdx
+++ b/_pages/learn/new-keyword/new-keyword-exercise.mdx
@@ -50,21 +50,21 @@ If the `_id` is not found, it should revert with an error called `ContactNotFoun
The `getContact` function returns the contact information of the supplied `_id` number. It reverts to `ContactNotFound` if the contact isn't present.
-:::tip[Question]
+
+**Question**
For bonus points (that only you will know about), explain why we can't just use the automatically generated getter for `contacts`?
+
-:::
### Get All Contacts
The `getAllContacts` function returns an array with all of the user's current, non-deleted contacts.
-:::caution
-
+
You shouldn't use `onlyOwner` for the two _get_ functions. Doing so won't prevent a third party from accessing the information, because all information on the blockchain is public. However, it may give the mistaken impression that information is hidden, which could lead to a security incident.
+
-:::
## AddressBookFactory
@@ -74,8 +74,7 @@ The `AddressBookFactory` contains one function, `deploy`. It creates an instance
## Submit your Contract and Earn an NFT Badge! (BETA)
-:::info
-
+
#### Hey, where'd my NFT go!?
[Testnets](/learn/deployment-to-testnet/test-networks) are not permanent! Base Goerli [will soon be sunset](https://base.mirror.xyz/kkz1-KFdUwl0n23PdyBRtnFewvO48_m-fZNzPMJehM4), in favor of Base Sepolia.
@@ -83,8 +82,8 @@ The `AddressBookFactory` contains one function, `deploy`. It creates an instance
As these are separate networks with separate data, your NFTs **will not** transfer over.
**Don't worry!** We've captured the addresses of all NFT owners on Base Goerli and will include them when we release the mechanism to transfer these NFTs to mainnet later this year! You can also redeploy on Sepolia and resubmit if you'd like!
+
-:::
import CafeUnitTest from '../../../components/CafeUnitTest/index.jsx'
diff --git a/docs/pages/learn/new-keyword/new-keyword-sbs.mdx b/_pages/learn/new-keyword/new-keyword-sbs.mdx
similarity index 99%
rename from docs/pages/learn/new-keyword/new-keyword-sbs.mdx
rename to _pages/learn/new-keyword/new-keyword-sbs.mdx
index d49a9d44..c514e68b 100644
--- a/docs/pages/learn/new-keyword/new-keyword-sbs.mdx
+++ b/_pages/learn/new-keyword/new-keyword-sbs.mdx
@@ -103,13 +103,12 @@ Click _At Address_ and the instance of `Complimenter` should appear below `Compl
-:::tip
-
+
If the deployed contract appears, but is instead a broken copy of the factory, it's because you didn't change the contract in the _CONTRACT_ dropdown above the deploy button.
Remix is trying to interact with `Complimenter` using the _ABI_ from the factory contract, which won't work.
+
-:::
---
diff --git a/docs/pages/learn/reading-and-displaying-data/configuring-useReadContract.mdx b/_pages/learn/reading-and-displaying-data/configuring-useReadContract.mdx
similarity index 99%
rename from docs/pages/learn/reading-and-displaying-data/configuring-useReadContract.mdx
rename to _pages/learn/reading-and-displaying-data/configuring-useReadContract.mdx
index 3232b184..eb4b5e6f 100644
--- a/docs/pages/learn/reading-and-displaying-data/configuring-useReadContract.mdx
+++ b/_pages/learn/reading-and-displaying-data/configuring-useReadContract.mdx
@@ -72,11 +72,10 @@ It works! Unfortunately, you can't really stop here, unless you're working on a
If you were to take the obvious approach of adding a `useReadContract` for every function you wanted data from, and set it to `watch`, things would quickly get out of hand. A single open web page with 15 functions watched in this way will hit rate-limiting in as short as an hour.
-:::info
-
+
Don't do this, either use multi-call via [`useReadContracts`], or consolidate your `view`s into a single function that fetches all the data you need in one call.
+
-:::
Luckily, you have options to control these calls a little better.
diff --git a/docs/pages/learn/reading-and-displaying-data/useAccount.mdx b/_pages/learn/reading-and-displaying-data/useAccount.mdx
similarity index 100%
rename from docs/pages/learn/reading-and-displaying-data/useAccount.mdx
rename to _pages/learn/reading-and-displaying-data/useAccount.mdx
diff --git a/docs/pages/learn/reading-and-displaying-data/useReadContract.mdx b/_pages/learn/reading-and-displaying-data/useReadContract.mdx
similarity index 99%
rename from docs/pages/learn/reading-and-displaying-data/useReadContract.mdx
rename to _pages/learn/reading-and-displaying-data/useReadContract.mdx
index 31a24068..9699179d 100644
--- a/docs/pages/learn/reading-and-displaying-data/useReadContract.mdx
+++ b/_pages/learn/reading-and-displaying-data/useReadContract.mdx
@@ -28,8 +28,7 @@ The contract creates a very simple DAO, in which users can create issues and vot
But it makes it much easier to test!
-:::caution
-
+
If you're using your own contract, please redeploy it with the following `view` functions:
```solidity
@@ -49,8 +48,8 @@ function getAllIssues() public view returns(ReturnableIssue[] memory) {
```
**You also need to make the `getIssue` function `public`. The original spec called for it to be `external`.**
+
-:::
### Create Demo Issues
@@ -122,11 +121,10 @@ interface Issue {
}
```
-:::warning
-
+
Be very careful here! `bigint` is the name of the type, `BigInt` is the name of the constructor for that type. If you incorrectly use the constructor as the type, much of your code will still work, but other parts will express very confusing bugs.
+
-:::
Now, import `useState` and add a state variable to hold your list of `Issue`s.
@@ -283,11 +281,12 @@ In this guide, you've learned how to use the `useReadContract` hook to call `pur
Use this contract if you don't have your own from the [ERC 20 Tokens Exercise]. You can also use this if you want to cheat to get that badge. Doing so would be silly though!
-:::caution
+
If you use your own contract, redeploy it with the `numberOfIssues` and `getAllIssues` functions from the bottom of the contract below. We'll need this for our first pass solution for getting all the `Issues` in the contract.
**You also need to make the `getIssue` function `public`. The original spec called for it to be `external`.**
-:::
+
+
```Solidity
// SPDX-License-Identifier: MIT
diff --git a/docs/pages/learn/storage/how-storage-works-video.mdx b/_pages/learn/storage/how-storage-works-video.mdx
similarity index 78%
rename from docs/pages/learn/storage/how-storage-works-video.mdx
rename to _pages/learn/storage/how-storage-works-video.mdx
index cd4c4365..4be58f49 100644
--- a/docs/pages/learn/storage/how-storage-works-video.mdx
+++ b/_pages/learn/storage/how-storage-works-video.mdx
@@ -6,6 +6,6 @@ hide_table_of_contents: false
# How Storage Works
-import Video from '@/components/VideoPlayer.jsx'
+import { Video } from '/snippets/VideoPlayer.mdx';
diff --git a/docs/pages/learn/storage/how-storage-works.mdx b/_pages/learn/storage/how-storage-works.mdx
similarity index 100%
rename from docs/pages/learn/storage/how-storage-works.mdx
rename to _pages/learn/storage/how-storage-works.mdx
diff --git a/docs/pages/learn/storage/simple-storage-sbs.mdx b/_pages/learn/storage/simple-storage-sbs.mdx
similarity index 99%
rename from docs/pages/learn/storage/simple-storage-sbs.mdx
rename to _pages/learn/storage/simple-storage-sbs.mdx
index d2354681..453a160e 100644
--- a/docs/pages/learn/storage/simple-storage-sbs.mdx
+++ b/_pages/learn/storage/simple-storage-sbs.mdx
@@ -139,15 +139,14 @@ function updateNumberOfCars(uint8 _numberOfCars) public {
Deploy and test to make sure it works as expected.
-:::warning
-
+
While packing variables can save on gas costs, it can also increase them. The EVM operates on 32 bytes at a time, so it will take additional steps to reduce the size of the element for storage.
Furthermore, the savings in writing to storage only apply when writing multiple values in the same slot at the same time.
Review the **Warning** in the [layout] section of the docs for more details!
+
-:::
### Add a Function to Update `age`
diff --git a/docs/pages/learn/storage/simple-storage-video.mdx b/_pages/learn/storage/simple-storage-video.mdx
similarity index 77%
rename from docs/pages/learn/storage/simple-storage-video.mdx
rename to _pages/learn/storage/simple-storage-video.mdx
index a4b593f9..052dc035 100644
--- a/docs/pages/learn/storage/simple-storage-video.mdx
+++ b/_pages/learn/storage/simple-storage-video.mdx
@@ -6,6 +6,6 @@ hide_table_of_contents: false
# Simple Storage
-import Video from '@/components/VideoPlayer.jsx'
+import { Video } from '/snippets/VideoPlayer.mdx';
diff --git a/docs/pages/learn/storage/storage-exercise.mdx b/_pages/learn/storage/storage-exercise.mdx
similarity index 97%
rename from docs/pages/learn/storage/storage-exercise.mdx
rename to _pages/learn/storage/storage-exercise.mdx
index e4630973..f6a96d73 100644
--- a/docs/pages/learn/storage/storage-exercise.mdx
+++ b/_pages/learn/storage/storage-exercise.mdx
@@ -4,6 +4,8 @@ description: Exercise - Demonstrate your knowledge of storage.
hide_table_of_contents: false
---
+import { Danger } from "/snippets/danger.mdx";
+
# Storage Exercise
Create a contract that adheres to the following specifications:
@@ -44,13 +46,12 @@ For the purposes of the test, you **must** deploy the contract with the followin
### View Salary and View Shares
-:::danger
-
+
In the world of blockchain, nothing is ever secret!\* `private` variables prevent other contracts from reading the value. You should use them as a part of clean programming practices, but marking a variable as private **does _not_ hide the value**. All data is trivially available to anyone who knows how to fetch data from the chain.
\*You can make clever use of encryption though!
+
-:::
Write a function called `viewSalary` that returns the value in `salary`.
@@ -98,8 +99,7 @@ function debugResetShares() public {
### Submit your Contract and Earn an NFT Badge! (BETA)
-:::info
-
+
#### Hey, where'd my NFT go!?
[Testnets](/learn/deployment-to-testnet/test-networks) are not permanent! Base Goerli [will soon be sunset](https://base.mirror.xyz/kkz1-KFdUwl0n23PdyBRtnFewvO48_m-fZNzPMJehM4), in favor of Base Sepolia.
@@ -107,8 +107,8 @@ function debugResetShares() public {
As these are separate networks with separate data, your NFTs **will not** transfer over.
**Don't worry!** We've captured the addresses of all NFT owners on Base Goerli and will include them when we release the mechanism to transfer these NFTs to mainnet later this year! You can also redeploy on Sepolia and resubmit if you'd like!
+
-:::
import CafeUnitTest from '../../../components/CafeUnitTest/index.jsx'
diff --git a/docs/pages/learn/structs/structs-exercise.mdx b/_pages/learn/structs/structs-exercise.mdx
similarity index 99%
rename from docs/pages/learn/structs/structs-exercise.mdx
rename to _pages/learn/structs/structs-exercise.mdx
index 3099abdc..0eb4dc8e 100644
--- a/docs/pages/learn/structs/structs-exercise.mdx
+++ b/_pages/learn/structs/structs-exercise.mdx
@@ -59,8 +59,7 @@ Add a public function called `resetMyGarage`. It should delete the entry in `gar
### Submit your Contract and Earn an NFT Badge! (BETA)
-:::info
-
+
#### Hey, where'd my NFT go!?
[Testnets](/learn/deployment-to-testnet/test-networks) are not permanent! Base Goerli [will soon be sunset](https://base.mirror.xyz/kkz1-KFdUwl0n23PdyBRtnFewvO48_m-fZNzPMJehM4), in favor of Base Sepolia.
@@ -68,8 +67,8 @@ Add a public function called `resetMyGarage`. It should delete the entry in `gar
As these are separate networks with separate data, your NFTs **will not** transfer over.
**Don't worry!** We've captured the addresses of all NFT owners on Base Goerli and will include them when we release the mechanism to transfer these NFTs to mainnet later this year! You can also redeploy on Sepolia and resubmit if you'd like!
+
-:::
import CafeUnitTest from '../../../components/CafeUnitTest/index.jsx'
diff --git a/docs/pages/learn/structs/structs-sbs.mdx b/_pages/learn/structs/structs-sbs.mdx
similarity index 100%
rename from docs/pages/learn/structs/structs-sbs.mdx
rename to _pages/learn/structs/structs-sbs.mdx
diff --git a/docs/pages/learn/structs/structs-vid.mdx b/_pages/learn/structs/structs-vid.mdx
similarity index 74%
rename from docs/pages/learn/structs/structs-vid.mdx
rename to _pages/learn/structs/structs-vid.mdx
index 2f92eecb..f90ed8d6 100644
--- a/docs/pages/learn/structs/structs-vid.mdx
+++ b/_pages/learn/structs/structs-vid.mdx
@@ -6,6 +6,6 @@ hide_table_of_contents: false
# Structs
-import Video from '@/components/VideoPlayer.jsx'
+import { Video } from '/snippets/VideoPlayer.mdx';
diff --git a/docs/pages/learn/welcome.mdx b/_pages/learn/welcome.mdx
similarity index 95%
rename from docs/pages/learn/welcome.mdx
rename to _pages/learn/welcome.mdx
index 79752225..1550f7f1 100644
--- a/docs/pages/learn/welcome.mdx
+++ b/_pages/learn/welcome.mdx
@@ -16,6 +16,8 @@ hide_table_of_contents: false
image: /img/base-learn-open-graph.png
---
+import LearningObjectives from '/snippets/learning-objectives.mdx';
+
# Welcome
@@ -32,7 +34,6 @@ Begin your journey today!
Base Learn covers the following topics. If you're looking for quickstarts, or deeper guides on advanced topics, check out our [Base Builder Tutorials]!
-import LearningObjectives from './learning-objectives.mdx';
In this step-by-step, you're going to start with the [`useWriteContract`] hook. You probably won't want to use this method in production. In the next step-by-step, we'll show you the [`useSimulateContract`] hook, how it works with `useWriteContract`, and how you can use it to create a better user experience.
Exploring them separately will highlight the functionality provided by the prepare hook.
+
-:::
-
-:::caution
+
In this module, you'll extend the onchain app you build in the previous module, [Reading and Displaying Data].
+
-:::
You've built an app that can read from your Simple DAO smart contract, but so far, you've used BaseScan to send transactions that call your write functions. You can use the [`useWriteContract`] hook in a similar way to call those functions directly from your app.
@@ -76,11 +74,10 @@ useEffect(() => {
}, [blockNumber, queryClient]);
```
-:::caution
-
+
Remember, this is an expensive method to watch for data to change on the blockchain. In this case, a more production-suitable solution might be to call `balanceOf` after the user has done something that might change the balance.
+
-:::
Set the `return` for your component to display this balance to the user:
diff --git a/docs/pages/privacy-policy.md b/_pages/privacy-policy.mdx
similarity index 100%
rename from docs/pages/privacy-policy.md
rename to _pages/privacy-policy.mdx
diff --git a/_pages/quickstart.mdx b/_pages/quickstart.mdx
new file mode 100644
index 00000000..e509d250
--- /dev/null
+++ b/_pages/quickstart.mdx
@@ -0,0 +1,250 @@
+---
+title: Quickstart
+description: Deploy on Base and build your first onchain app.
+---
+
+# Quickstart
+
+Welcome to the Base quickstart guide! In this walkthrough, we'll create a simple onchain app from start to finish. Whether you're a seasoned developer or just starting out, this guide has got you covered.
+
+## What You'll Achieve
+
+By the end of this quickstart, you'll have built an onchain app by:
+
+- Configuring your development environment
+- Deploying your smart contracts to Base
+- Interacting with your deployed contracts from the frontend
+
+Our simple app will be an onchain tally app which lets you add to a total tally, stored onchain, by pressing a button.
+
+
+**Why Base?**
+
+Base is a fast, low-cost, builder-friendly Ethereum L2 built to bring the next billion users onchain. By following this guide, you'll join a vibrant ecosystem of developers, creators, and innovators who are building a global onchain economy.
+
+
+
+## Set Up Your Development Environment
+
+
+
+ OnchainKit is a library of ready-to-use React components and Typescript utilities for building onchain apps. Run the following command in your terminal and follow the prompts to bootstrap your project.
+
+ ```bash [Terminal]
+ npm create onchain@latest
+ ```
+
+ The prompots will ask you for a CDP API Key which you can get [here](https://portal.cdp.coinbase.com/projects/api-keys/client-key).
+
+ Once you've gone through the prompts, you'll have a new project directory with a basic OnchainKit app. Run the following to see it live.
+
+ ```bash [Terminal]
+ cd my-onchainkit-app
+ npm install
+ npm run dev
+ ```
+
+ You should see the following screen.
+
+ 
+
+ Once we've deployed our contracts, we'll add a button that lets us interact with our contracts.
+
+
+
+ The total tally will be stored onchain in a smart contract. We'll use the Foundry framework to deploy our contract to the Base Sepolia testnet.
+
+ 1. Create a new "contracts" folder in the root of your project
+
+ ```bash [Terminal]
+ mkdir contracts && cd contracts
+ ```
+
+ 2. Install and initialize Foundry
+
+ ```bash [Terminal]
+ curl -L https://foundry.paradigm.xyz | bash
+ foundryup
+ forge init --no-git
+ ```
+
+ Open the project and find the `Counter.sol` contract file in the `/contracts/src` folder. You'll find the simple logic for our tally app.
+
+
+ **--no-git**
+
+ Because `contracts` is a folder in our project, we don't want to initialize a separate git repository for it, so we add the `--no-git` flag.
+
+
+
+ To deploy your smart contracts to Base, you need two key components:
+
+ 1. A node connection to interact with the Base network
+ 2. A funded private key to deploy the contract
+
+ Let's set up both of these:
+
+ - Create a `.env` file in your `contracts` directory and add the Base and Base Sepolia RPC URLs
+
+ ```bash [contracts/.env]
+ BASE_RPC_URL="https://mainnet.base.org"
+ BASE_SEPOLIA_RPC_URL="https://sepolia.base.org"
+ ```
+
+ -Load your environment variables
+
+ ```bash [Terminal]
+ source .env
+ ```
+
+
+ **Base Sepolia**
+
+ Base Sepolia is the test network for Base, which we will use for the rest of this guide. You can obtain free Base Sepolia ETH from one of the [faucets listed here](/chain/network-faucets).
+
+
+
+ A private key with testnet funds is required to deploy the contract. You can generate a fresh private key [here](https://visualkey.link/).
+
+ 1. Store your private key in Foundry's secure keystore
+
+ ```bash [Terminal]
+ cast wallet import deployer --interactive
+ ```
+
+ 2. When prompted enter your private key and a password.
+
+ Your private key is stored in `~/.foundry/keystores` which is not tracked by git.
+
+
+ Never share or commit your private key. Always keep it secure and handle with care.
+
+
+
+
+## Deploy Your Contracts
+
+Now that your environment is set up, let's deploy your contracts to Base Sepolia. The foundry project provides a deploy script that will deploy the Counter.sol contract.
+
+
+
+ 1. Use the following command to compile and deploy your contract
+
+ ```bash [Terminal]
+ forge create ./src/Counter.sol:Counter --rpc-url $BASE_SEPOLIA_RPC_URL --account deployer
+ ```
+
+ Note the format of the contract being deployed is `:`.
+
+
+ After successful deployment, the transaction hash will be printed to the console output
+
+ Copy the deployed contract address and add it to your `.env` file
+
+ ```bash
+ COUNTER_CONTRACT_ADDRESS="0x..."
+ ```
+
+
+
+ ```bash [Terminal]
+ source .env
+ ```
+
+
+ To ensure your contract was deployed successfully:
+
+ 1. Check the transaction on [Sepolia Basescan](https://sepolia.basescan.org/).
+ 2. Use the `cast` command to interact with your deployed contract from the command line
+
+ ```bash
+ cast call $COUNTER_CONTRACT_ADDRESS "number()(uint256)" --rpc-url $BASE_SEPOLIA_RPC_URL
+ ```
+
+ This will return the initial value of the Counter contract's `number` storage variable, which will be `0`.
+
+
+
+**Congratulations! You've deployed your smart contract to Base Sepolia!**
+
+Now lets connect the frontend to interact with your recently deployed contract.
+
+## Interacting with your contract
+
+To interact with the smart contract logic, we need to submit an onchain transaction. We can do this easily with the `Transaction` component. This is a simplified version of the `Transaction` component, designed to streamline the integration process. Instead of manually defining each subcomponent and prop, we can use this shorthand version which renders our suggested implementation of the component and includes the `TransactionButton` and `TransactionToast` components.
+
+
+
+ Lets add the `Transaction` component to our `page.tsx` file. Delete the existing content in the `main` tag and replace it with the snippet below.
+
+ ```tsx twoslash [page.tsx]
+ // @noErrors: 2307 - Cannot find module '@/calls'
+ import { Transaction } from '@coinbase/onchainkit/transaction';
+ import { calls } from '@/calls';
+
+
+ ;
+ ```
+
+
+ In the previous code snippet, you'll see we imported `calls` from the `calls.ts` file. This file provides the details needed to interact with our contract and call the `increment` function. Create a new `calls.ts` file in the same folder as your `page.tsx` file and add the following code.
+
+ ```ts twoslash [calls.ts]
+ const counterContractAddress = '0x...'; // add your contract address here
+ const counterContractAbi = [
+ {
+ type: 'function',
+ name: 'increment',
+ inputs: [],
+ outputs: [],
+ stateMutability: 'nonpayable',
+ },
+ ] as const;
+
+ export const calls = [
+ {
+ address: counterContractAddress,
+ abi: counterContractAbi,
+ functionName: 'increment',
+ args: [],
+ },
+ ];
+ ```
+
+
+ **Contract Address**
+
+ The `calls.ts` file contains the details of the contract interaction, including the contract address, which we saved in the previous step.
+
+
+
+ Now, when you connect a wallet and click on the `Transact` button and approve the transaction, it will increment the tally onchain by one.
+
+ We can verify that the onchain count took place onchain by once again using `cast` to call the `number` function on our contract.
+
+ ```bash [Terminal]
+ cast call $COUNTER_CONTRACT_ADDRESS "number()(uint256)" --rpc-url $BASE_SEPOLIA_RPC_URL
+ ```
+
+ If the transaction was successful, the tally should have incremented by one!
+
+
+
+We now have a working onchain tally app! While the example is simple, it illustrates the end to end process of building on onchain app. We:
+
+- Configured a project with frontend and onchain infrastructure
+- Deployed a smart contract to Base Sepolia
+- Interacted with the contract from the frontend
+
+## Further Improvements
+
+This is just the beginning. There are many ways we can improve upon this app. For example, we could:
+
+- Make the `increment` transaction gasless by integrating with [Paymaster](/builderkits/onchainkit/transaction/transaction#sponsor-with-paymaster-capabilities)
+- Improve the wallet connection and sign up flow with the [WalletModal](/builderkits/onchainkit/wallet/wallet-modal) component
+- Add onchain [Identity](/builderkits/onchainkit/identity/identity) so we know who added the most recent tally
diff --git a/docs/pages/terms-of-service.md b/_pages/terms-of-service.mdx
similarity index 100%
rename from docs/pages/terms-of-service.md
rename to _pages/terms-of-service.mdx
diff --git a/_pages/use-cases/accept-crypto-payments.mdx b/_pages/use-cases/accept-crypto-payments.mdx
new file mode 100644
index 00000000..48cc15eb
--- /dev/null
+++ b/_pages/use-cases/accept-crypto-payments.mdx
@@ -0,0 +1,231 @@
+---
+title: 'Accept Crypto Payments'
+description: Learn how to integrate Coinbase Commerce payments into your application using OnchainKit.
+authors:
+ - hughescoin
+---
+
+# Accept Crypto Payments with Coinbase Commerce & OnchainKit
+
+Accepting crypto payments can help you **eliminate traditional credit card fees** and **avoid costly chargebacks**, giving you a faster, more global payment experience. In this guide, you'll learn how to quickly integrate Coinbase Commerce and OnchainKit to accept crypto payments for products or services in your application.
+
+## Objectives
+
+By following this guide, you will learn how to:
+
+- Create or configure a product in **Coinbase Commerce**
+- Configure your **OnchainKit** environment
+- Implement a checkout flow for accepting crypto payments
+- Deploy and test your app to confirm the payment flow
+
+
+## Prerequisites
+
+### 1. Coinbase Commerce Account
+
+[Coinbase Commerce](https://beta.commerce.coinbase.com/sign-up) allows you to accept cryptocurrency payments globally. Sign up to get started.
+
+### 2. Coinbase Developer Platform (CDP) Account
+
+[Coinbase Developer Platform](https://www.coinbase.com/cloud) (CDP) provides the tools and APIs you need for integration.
+
+### 3. Reown (WalletConnect) Account
+
+[Reown](https://cloud.reown.com/) (formerly WalletConnect) provides a secure way to connect wallets across different devices and platforms.
+
+
+## Step-by-Step Setup
+
+
+
+ 1. **Log in** to your Coinbase Commerce account.
+ 2. Go to the [product creation page](https://beta.commerce.coinbase.com/products).
+ 3. **Add product details** (name, description, price).
+ 4. Click **Create product**.
+ 5. Once created, select **View product** and copy the **UUID** from the URL.
+
+ 
+
+ **Tip**: Store the product UUID as an environment variable in your `.env` file. This makes it easier to reference safely in your code.
+
+
+ Use the official **OnchainKit app template** to bootstrap your project:
+
+
+ ```bash [Bun]
+ git clone https://github.com/coinbase/onchainkit-app-template.git
+ cd onchainkit-app-template
+ bun i
+ ```
+
+
+ ```bash [npm]
+ git clone https://github.com/coinbase/onchainkit-app-template.git
+ cd onchainkit-app-template
+ npm install
+ ```
+
+
+ ```bash [Yarn]
+ git clone https://github.com/coinbase/onchainkit-app-template.git
+ cd onchainkit-app-template
+ yarn
+ ```
+
+
+
+ In the project folder, open (or create) your `.env` file and add:
+
+ ```bash
+ NEXT_PUBLIC_WC_PROJECT_ID=
+ NEXT_TELEMETRY_DISABLED=1
+ NEXT_PUBLIC_ONCHAINKIT_API_KEY=
+ NEXT_PUBLIC_PRODUCT_ID=
+ ```
+
+ > **Note**:
+ > - `NEXT_PUBLIC_PRODUCT_ID` should be set to the **UUID** from your Coinbase Commerce product.
+ > - `NEXT_PUBLIC_ONCHAINKIT_API_KEY` should be your **CDP** API key.
+ > - `NEXT_PUBLIC_WC_PROJECT_ID` is your Reown (WalletConnect) project ID.
+
+
+
+ Open your Wagmi configuration file (e.g., `src/app/wagmi.ts` or similar) and **after** your `useMemo()` hook, add:
+
+ ```diff
+ // other Wagmi config
+ + coinbaseWallet.preference = 'smartWalletOnly';
+ ```
+
+ This ensures Coinbase Wallet only connects to **smart wallets**.
+
+ In `src/app/components/OnchainProviders.tsx`, set up **OnchainKitProvider** to use your **CDP** API key and **Base** as the chain:
+
+ ```typescript
+ 'use client';
+ import { OnchainKitProvider } from '@coinbase/onchainkit';
+ import { RainbowKitProvider } from '@rainbow-me/rainbowkit';
+ import { QueryClient, QueryClientProvider } from '@tanstack/react-query';
+ import type { ReactNode } from 'react';
+ import { base } from 'viem/chains';
+ import { WagmiProvider } from 'wagmi';
+ import { useWagmiConfig } from '../wagmi';
+
+ type Props = { children: ReactNode };
+ const queryClient = new QueryClient();
+
+ function OnchainProviders({ children }: Props) {
+ const wagmiConfig = useWagmiConfig();
+ return (
+
+
+
+
+ {children}
+
+
+
+
+ );
+ }
+
+ export default OnchainProviders;
+ ```
+
+ Finally, update your `Config.ts` (or similar config file) to read from environment variables and match your hosted URL:
+
+ ```typescript
+ export const NEXT_PUBLIC_URL =
+ process.env.NODE_ENV === 'development'
+ ? 'http://localhost:3000'
+ : 'https://based-jerseys.vercel.app';
+
+ export const NEXT_PUBLIC_CDP_API_KEY =
+ process.env.NEXT_PUBLIC_ONCHAINKIT_API_KEY;
+
+ export const NEXT_PUBLIC_WC_PROJECT_ID =
+ process.env.NEXT_PUBLIC_WC_PROJECT_ID;
+ ```
+
+
+
+ 1. **Open** `src/app/page.tsx` (or similar entry page).
+ 2. **Import** the necessary components:
+
+ ```typescript
+ import { Checkout, CheckoutButton, CheckoutStatus } from '@coinbase/onchainkit/checkout';
+ import Image from 'next/image';
+
+ const productId = process.env.NEXT_PUBLIC_PRODUCT_ID;
+ ```
+
+ 3. **Add an image** of your product or service in the `public` folder (e.g., `/public/based-jersey-front.jpeg`).
+ 4. **Display** that image and conditionally render the checkout UI only when a wallet is connected:
+
+ ```jsx
+
+
+ ```
+
+
+ Use **conditional rendering** to avoid errors when no wallet address is detected.
+
+
+
+
+ 1. **Run** the development server:
+
+
+ ```bash [Bun]
+ bun run dev
+ ```
+
+ ```bash [npm]
+ npm run dev
+ ```
+
+ ```bash [Yarn]
+ yarn dev
+ ```
+
+
+
+ 2. **Visit** `http://localhost:3000` to confirm that the payment button works for your product or service.
+ 3. **Deploy** with your preferred hosting provider (e.g., Vercel).
+
+ 
+
+
+
+## Conclusion
+
+Congratulations! You've successfully **integrated Coinbase Commerce** and **OnchainKit** into your application, enabling crypto payments. By providing this option, you can:
+
+- Eliminate traditional payment fees and chargebacks
+- Expand your audience to crypto users worldwide
+- Easily scale your offerings for more products and services
+
+**Happy building** and enjoy the benefits of a global, decentralized payment system on Base!
+
+
+[Passkeys]: https://www.coinbase.com/blog/introducing-passkeys-a-safer-and-easier-way-to-sign-in-to-coinbase
+[Reown]: https://cloud.reown.com/
+[product creation page]: https://beta.commerce.coinbase.com/products
diff --git a/_pages/use-cases/ai-instructions/eliza.mdx b/_pages/use-cases/ai-instructions/eliza.mdx
new file mode 100644
index 00000000..601bda5c
--- /dev/null
+++ b/_pages/use-cases/ai-instructions/eliza.mdx
@@ -0,0 +1,23 @@
+---
+title: "Edit .env with your own values"
+---
+
+
+
+## Eliza Framework Setup
+
+The fastest way to get started with Eliza is by using the `create-agentkit-app` CLI:
+
+
+
+```bash [Terminal]
+npx create-agentkit-app my-agent
+cd my-agent
+cp .env.example .env
+pnpm install
+pnpm start
+```
+
+
+For additional support, check out the [video tutorial](https://www.youtube.com/live/DlRR1focAiw).
+
diff --git a/_pages/use-cases/ai-instructions/langchain-local.mdx b/_pages/use-cases/ai-instructions/langchain-local.mdx
new file mode 100644
index 00000000..da44003c
--- /dev/null
+++ b/_pages/use-cases/ai-instructions/langchain-local.mdx
@@ -0,0 +1,65 @@
+---
+title: "Edit .env with your credentials"
+---
+
+
+## LangChain Local Environment Setup
+
+### TypeScript
+
+
+
+ ```bash [Terminal]
+ node --version # Should be 18+
+ npm --version # Should be 9.7.2+
+ ```
+
+
+ ```bash [Terminal]
+ git clone https://github.com/coinbase/agentkit.git
+ cd agentkit
+ npm install
+ npm run build
+ cd typescript/examples/langchain-cdp-chatbot
+ ```
+
+
+ ```bash [Terminal]
+ cp .env.local .env
+ ```
+
+
+ ```bash [Terminal]
+ npm run start
+ ```
+
+
+
+### Python
+
+
+
+ ```bash [Terminal]
+ python --version # Should be 3.10+
+ poetry --version # Verify Poetry installation
+ ```
+
+
+ ```bash [Terminal]
+ git clone https://github.com/coinbase/agentkit.git
+ cd agentkit/python/examples/cdp-langchain-chatbot
+ ```
+
+
+ ```bash [Terminal]
+ cp .env.local .env
+ # Edit .env with your credentials
+ ```
+
+
+ ```bash [Terminal]
+ poetry install
+ poetry run python main.py
+ ```
+
+
diff --git a/_pages/use-cases/ai-instructions/langchain-replit.mdx b/_pages/use-cases/ai-instructions/langchain-replit.mdx
new file mode 100644
index 00000000..320e3ee4
--- /dev/null
+++ b/_pages/use-cases/ai-instructions/langchain-replit.mdx
@@ -0,0 +1,30 @@
+## LangChain Replit Setup
+
+
+
+ 1. Fork the template from our [NodeJS](https://replit.com/@lincolnmurr/AgentKitjs-Quickstart-010?v=1) or [Python](https://replit.com/@lincolnmurr/AgentKitpy-01?v=1) Replit templates.
+ 2. Modify your forked project as needed.
+
+
+ 1. Click on "Tools" in the left sidebar and select "Secrets".
+ 2. Add the following secrets:
+
+ ```bash
+ CDP_API_KEY_NAME=your_cdp_key_name
+ CDP_API_KEY_PRIVATE_KEY=your_cdp_private_key
+ OPENAI_API_KEY=your_openai_key # Or XAI_API_KEY if using NodeJS
+ NETWORK_ID="base-sepolia" # Optional, defaults to base-sepolia
+ MNEMONIC_PHRASE=your_mnemonic_phrase # Optional
+ ```
+
+
+
+ 1. Click the "Run" button to start the chatbot.
+
+
+ **Security of wallets on Replit**
+
+ Every agent comes with an associated wallet. Wallet data is read from wallet_data.txt, and if that file does not exist, this repl will create a new wallet and persist it in a new file. Please note that this contains your wallet's private key and should not be used in production environments. Refer to the [CDP docs](https://docs.cdp.coinbase.com/wallet-api/docs/wallets#securing-a-wallet) on how to secure your wallets.
+
+
+
diff --git a/docs/pages/use-cases/decentralize-social-app.mdx b/_pages/use-cases/decentralize-social-app.mdx
similarity index 83%
rename from docs/pages/use-cases/decentralize-social-app.mdx
rename to _pages/use-cases/decentralize-social-app.mdx
index 82710780..b7030967 100644
--- a/docs/pages/use-cases/decentralize-social-app.mdx
+++ b/_pages/use-cases/decentralize-social-app.mdx
@@ -36,33 +36,31 @@ Onchain profiles are built with Basenames and ENS, services which wrap wallet ad
## Integrating `
+
+ Creating a new OnchainKit app is the easiest way to get started.
+
+ ```bash [Terminal]
+ npm create onchain@latest
+ ```
+
+ Or you can integrate OnchainKit into an existing app by following the [installation guide](/builderkits/onchainkit/getting-started/#manual-installation).
+
+
+
+ ```tsx twoslash [App.tsx]
+ // @errors: 2305
+ import { IdentityCard } from '@coinbase/onchainkit/identity'; // [!code focus]
+ import { base } from 'viem/chains';
+
+
+
Just like that, you've added onchain identity into your app! Once a user connects a wallet with a Basename or ENS name, the IdentityCard component will display the user's profile information like you see below.
@@ -75,9 +73,12 @@ Just like that, you've added onchain identity into your app! Once a user connect
/>
-:::tip[Setting the address]
+
+**Setting the address**
+
In the above example, we hardcoded the address. In a real app, you'll dynamically set the address based on the user's connected wallet. [Use OnchainKit's `
+
The IdentityCard component comes with helpful defaults, such as a plain avatar image, for users who don't have a Basename or ENS name.
diff --git a/docs/pages/use-cases/defi-your-app.mdx b/_pages/use-cases/defi-your-app.mdx
similarity index 96%
rename from docs/pages/use-cases/defi-your-app.mdx
rename to _pages/use-cases/defi-your-app.mdx
index 16fa6788..357c2689 100644
--- a/docs/pages/use-cases/defi-your-app.mdx
+++ b/_pages/use-cases/defi-your-app.mdx
@@ -3,6 +3,7 @@ title: Defi your app
description: Add common financial features like token swaps and yield generating strategies to your app with pre-built React components from OnchainKit.q
---
+import { Danger } from "/snippets/danger.mdx";
import { Avatar, Name } from '@coinbase/onchainkit/identity';
import { Swap, SwapAmountInput, SwapButton, SwapDefault, SwapMessage, SwapToggleButton, SwapToast } from '@coinbase/onchainkit/swap';
import { EarnMain, EarnDeposit, RearrangedEarnDeposit, PredefinedInputDeposit } from '@/components/EarnComponents';
@@ -33,16 +34,15 @@ The `Swap` component lets users exchange one token for another directly in your
Lets add the `Swap` component to your app.
-:::steps
-### Install and Configure OnchainKit
- Create a new OnchainKit app
-
- ```bash [Terminal]
- npm create onchain@latest
- ```
-
-### Import and Render the Swap Component
+
+
+ Create a new OnchainKit app
+ ```bash [Terminal]
+ npm create onchain@latest
+ ```
+
+
```typescript [App.tsx]
import { SwapDefault } from '@coinbase/onchainkit/swap'; // [!code focus]
import type { Token } from '@coinbase/onchainkit/token';
@@ -72,7 +72,8 @@ Lets add the `Swap` component to your app.
to={[usdc]} // [!code focus]
/> // [!code focus]
```
-:::
+
+
You should now see the following swap component in your app:
@@ -113,9 +114,12 @@ To learn more about how to customize the Swap component, check out the [Swap doc
The `Earn` component enables users to deposit assets into yield-generating vaults and withdraw them later—all within your app. The `Earn` component currently supports Morpho vaults on Base.
-:::note[Get a vault address]
+
+**Get a vault address**
+
You can get a vault address from Morpho's [Vaults page](https://app.morpho.org/base/earn). You will use this address when setting up the `Earn` component.
-:::
+
+
```tsx twoslash
// @noErrors: 2307
@@ -134,8 +138,7 @@ Similar to the Swap component, the Earn component is highly customizable. Lets c
- `useEarnContext` to access the component's context values, `EarnDeposit` and `EarnDetails`
- `DepositButton` to render custom deposit buttons
-:::code-group
-
+
```tsx twoslash [index.tsx]
// @noErrors: 2307
import { Earn, useEarnContext } from '@coinbase/onchainkit/earn';
@@ -183,7 +186,7 @@ function CustomDepositButtons() {
);
}
```
-:::
+
To use the `FundCard` component, you'll need to provide a Client API Key in `OnchainKitProvider`. You can get one following our [Getting Started](/builderkits/onchainkit/installation/nextjs#get-your-client-api-key) steps.
-:::::
+
+
```tsx [App.tsx]
import { FundCard } from '@coinbase/onchainkit/fund';
@@ -239,9 +243,10 @@ The `Buy` components provide a comprehensive interface for users to purchase [To
The `Buy` component supports token swaps from USDC and ETH by default with the option to provide an additional token of choice using the `fromToken` prop. Users are able to purchase tokens using their Coinbase account, Apple Pay, or debit card.
-:::info
+
This component requires a `projectId` to be set in the `OnchainKitProvider`. You can find your `projectId` on [Coinbase Developer Platform](https://portal.cdp.coinbase.com/products/onchainkit).
-:::
+
+
```tsx twoslash
import { Buy } from '@coinbase/onchainkit/buy'; // [!code focus]
@@ -275,11 +280,12 @@ export default function BuyComponents() { // [!code focus]
-:::danger
+
**Note: This interface is for demonstration purposes only.**
Swap and Onramp flows will execute and work out of the box when you implement the component in your own app.
-:::
+
+
By combining Swap, Earn, Fund, and Buy with these additional tools, you can quickly build a robust in-app DeFi experience with minimal development overhead. This lets you focus on building your unique value proposition.
diff --git a/docs/pages/use-cases/go-gasless.mdx b/_pages/use-cases/go-gasless.mdx
similarity index 98%
rename from docs/pages/use-cases/go-gasless.mdx
rename to _pages/use-cases/go-gasless.mdx
index 49e8ca36..cc510669 100644
--- a/docs/pages/use-cases/go-gasless.mdx
+++ b/_pages/use-cases/go-gasless.mdx
@@ -4,6 +4,8 @@ slug: /gasless-transaction-on-base-using-a-paymaster
description: Learn how to leverage the Base Paymaster for seamless, gasless transactions on the Coinbase Cloud Developer Platform.
---
+import { Danger } from "/snippets/danger.mdx";
+
# Gasless Transactions on Base using Base Paymaster
Base transaction fees are typically less than a penny, but the concept of gas can still be confusing for new users and lead to poor user experience when users don't have gas funds in their wallet. You can abstract this away and improve your UX by using the **Base Paymaster**. The Paymaster allows you to:
@@ -12,9 +14,10 @@ Base transaction fees are typically less than a penny, but the concept of gas ca
- Create custom gasless experiences
- Sponsor up to $15k monthly on mainnet (unlimited on testnet)
-:::tip
+
If you need an increase in your sponsorship limit, please [reach out on Discord][Discord]!
-:::
+
+
## Objectives
@@ -36,10 +39,11 @@ This tutorial assumes you have:
3. **Foundry**
Foundry is a development environment, testing framework, and smart contract toolkit for Ethereum. You’ll need it installed locally for generating key pairs and interacting with smart contracts.
-:::tip
+
**Testnet vs. Mainnet**
If you prefer not to spend real funds, you can switch to **Base Sepolia** (testnet). The steps below are conceptually the same. Just select _Base Sepolia_ in the Coinbase Developer Platform instead of _Base Mainnet_, and use a contract deployed on Base testnet for your allowlisted methods.
-:::
+
+
## Set Up a Base Paymaster & Bundler
@@ -70,10 +74,11 @@ In this section, you will configure a Paymaster to sponsor payments on behalf of
-:::info
+
**Use your own contract**
We use a [simple NFT contract][simple NFT contract] on Base mainnet as an example. Feel free to substitute your own.
-:::
+
+
### Global & Per User Limits
@@ -89,10 +94,11 @@ For example, you might set:
This means **each user** can only have $0.05 in sponsored gas and **1** user operation before the cycle resets.
-:::info
+
**Limit Cycles**
These reset based on the selected cadence (daily, weekly, monthly).
-:::
+
+
Next, **set the Global Limit**. For example, set this to `$0.07` so that once the entire paymaster has sponsored \$0.07 worth of gas (across all users), no more sponsorship occurs unless you raise the limit.
@@ -151,15 +157,21 @@ Now let’s verify that these policies work. We’ll:
Create a `.env` file in the `sponsored_transactions` directory. In the `.env`, you'll add the rpcURL for your paymaster and the private keys for your accounts:
-:::note[Find your Paymaster & Bundler endpoint]
+
+**Find your Paymaster & Bundler endpoint**
+
The Paymaster & Bundler endpoint is the URL for your Coinbase Developer Platform (CDP) Paymaster.
This was saved in the previous section and follows this format: `https://api.developer.coinbase.com/rpc/v1/base/`
Navigate to the [Paymaster Tool] and select the `Configuration` tab at the top of the screen to obtain your RPC URL.
-:::
+
+
+
+
+**Secure your endpoints**
-:::danger[Secure your endpoints]
You will create a constant for our Paymaster & Bundler endpoint obtained from cdp.portal.coinbase.com. The most secure way to do this is by using a proxy. For the purposes of this demo, hardcode it into our `index.js` file. For product, we highly recommend using a [proxy service].
-:::
+
+
```bash
PAYMASTER_RPC_URL=https://api.developer.coinbase.com/rpc/v1/base/
@@ -167,9 +179,10 @@ PRIVATE_KEY_1=0x01c9720c1dfa3c9...
PRIVATE_KEY_2=0xbcd6fbc1dfa3c9...
```
-:::danger
+
Never commit `.env` files to a public repo!
-:::
+
+
## Example `index.js`
diff --git a/docs/pages/use-cases/launch-ai-agents.mdx b/_pages/use-cases/launch-ai-agents.mdx
similarity index 100%
rename from docs/pages/use-cases/launch-ai-agents.mdx
rename to _pages/use-cases/launch-ai-agents.mdx
diff --git a/docs/pages/use-cases/onboard-any-user.mdx b/_pages/use-cases/onboard-any-user.mdx
similarity index 58%
rename from docs/pages/use-cases/onboard-any-user.mdx
rename to _pages/use-cases/onboard-any-user.mdx
index 494d1a93..ea645c86 100644
--- a/docs/pages/use-cases/onboard-any-user.mdx
+++ b/_pages/use-cases/onboard-any-user.mdx
@@ -22,86 +22,81 @@ The component offers:
Lets add the `WalletModal` component to your app.
-:::steps
-
-### Create a new OnchainKit app
-
-```bash [Terminal]
-npm create onchain@latest
-```
-
-### Configure the `OnchainKitProvider` with modal settings:
-
-```tsx [providers.tsx]
-
- {children}
-
-```
-
-### Add the `
-
-
-
-
-
+
+ ```bash [Terminal]
+ npm create onchain@latest
+ ```
+
+
+ ```tsx [providers.tsx]
+
+ {children}
+
+ ```
+
+
+ ```tsx [App.tsx]
+
+
+
-
-
-```
-
-### Wrap with Wallet Modal Context
-
-Ensure that the Wallet Modal is globally accessible by wrapping your key UI components:
-
-```tsx
-
-
+ ```
+
+
+
+ Once we've deployed our contracts, we'll add a button that lets us interact with our contracts.
+
+
+
+
+
+
+
+
+
+
+ {address ? (
+
+
+ ) : (
+
+
-
-
-
+
+
+
-
-
+
+
+ ```
+
+
+ Ensure that the Wallet Modal is globally accessible by wrapping your key UI components:
+
+ ```tsx
+
+
-```
-
-:::
+
+
+
+
+
+
+
+
+
+
+
-
-
@@ -137,11 +132,12 @@ You now have an interface to streamline user onboarding! The `WalletModal` compo
In addition to providing a secure and feature-rich wallet experience, Smart Wallets provide a streamlined onboarding experience through account creation with Passkeys. This allows anyone to securely create a new wallet and begin transacting without ever leaving your app.
-:::info[More on Smart Wallets]
+
+**More on Smart Wallets**
Smart Wallet has advanced features such as sponsored transactions, spend permissions, and Magic Spend. [Learn more about Smart Wallet here](/identity/smart-wallet/quickstart/).
+
-:::
## Conclusion
diff --git a/docs/pages/wallet-app/mini-apps.mdx b/_pages/wallet-app/mini-apps.mdx
similarity index 99%
rename from docs/pages/wallet-app/mini-apps.mdx
rename to _pages/wallet-app/mini-apps.mdx
index 8f90571b..afa937fa 100644
--- a/docs/pages/wallet-app/mini-apps.mdx
+++ b/_pages/wallet-app/mini-apps.mdx
@@ -1,4 +1,7 @@
-# Mini Apps
+---
+title: "Mini Apps"
+---
+
We're so excited that mini apps are coming to Coinbase Wallet! The purpose of this guide is to go over how to build or update your mini app so it works as well as possible in Coinbase Wallet.
@@ -33,9 +36,10 @@ Something important to note is that because of how the current mini app spec is
Currently, using Sign In with Farcaster inside of Coinbase Wallet is **not recommended as the primary method of authentication**. This is because, for Farcaster accounts that were created in Warpcast (which many current accounts were), using Sign In with Farcaster will require deeplinking the user to Warpcast and then back to Coinbase Wallet. While this flow still works inside of Coinbase Wallet, we recommend either wallet auth or creating an auth strategy around the context data (eg. a custom JWT with context data) for a more optimal UX.
-:::info
+
Note: The Sign In with Farcaster flow will no longer require a deeplink to Warpcast when the [auth addresses FIP](https://github.com/farcasterxyz/protocol/discussions/225) lands, which will allow a set of delegated wallets to take actions on behalf of a Farcaster account's custody wallet.
-:::
+
+
## Deeplinks and SDK Actions
diff --git a/api/submitFeedback.ts b/api/submitFeedback.ts
deleted file mode 100644
index 26b15af9..00000000
--- a/api/submitFeedback.ts
+++ /dev/null
@@ -1,73 +0,0 @@
-import { google } from '@googleapis/sheets';
-import type { VercelRequest, VercelResponse } from '@vercel/node';
-
-// Initialize Google Sheets client
-const getGoogleSheetsClient = () => {
- try {
- const credentials = JSON.parse(
- Buffer.from(process.env.GOOGLE_SERVICE_ACCOUNT_KEY || '', 'base64').toString(),
- );
-
- const auth = new google.auth.GoogleAuth({
- credentials,
- scopes: ['https://www.googleapis.com/auth/spreadsheets'],
- });
-
- return google.sheets({ version: 'v4', auth });
- } catch (error) {
- console.error('Failed to initialize Google Sheets client:', error);
- throw new Error('Failed to initialize Google Sheets client');
- }
-};
-
-type FeedbackPayload = {
- likeOrDislike: boolean;
- options: string[];
- comment: string;
- url: string;
- ipAddress: string;
- timestamp: number;
-};
-
-export default async function handler(req: VercelRequest, res: VercelResponse) {
- if (req.method !== 'POST') {
- return res.status(405).json({ error: 'Method not allowed' });
- }
-
- try {
- const { likeOrDislike, options, comment, url, ipAddress, timestamp } =
- req.body as FeedbackPayload;
-
- const sheets = getGoogleSheetsClient();
- const spreadsheetId = process.env.GOOGLE_SHEETS_ID;
-
- if (!spreadsheetId) {
- throw new Error('GOOGLE_SHEETS_ID environment variable is not set');
- }
-
- // Format the row data
- const rowData = [
- new Date(timestamp).toISOString(),
- url,
- ipAddress,
- likeOrDislike ? 'Like' : 'Dislike',
- options.join(', '),
- comment,
- ];
-
- // Append the row to the sheet
- await sheets.spreadsheets.values.append({
- spreadsheetId,
- range: 'Sheet1!A:F', // Adjust range based on your sheet's structure
- valueInputOption: 'USER_ENTERED',
- requestBody: {
- values: [rowData],
- },
- });
-
- return res.status(200).json({ success: true });
- } catch (error) {
- console.error('Error submitting feedback:', error);
- return res.status(500).json({ error: 'Failed to submit feedback' });
- }
-}
diff --git a/contexts/Theme.tsx b/contexts/Theme.tsx
deleted file mode 100644
index 7ef33ff8..00000000
--- a/contexts/Theme.tsx
+++ /dev/null
@@ -1,62 +0,0 @@
-import {
- type ReactNode,
- createContext,
- useCallback,
- useContext,
- useEffect,
- useMemo,
- useState,
-} from 'react';
-
-type Theme = 'light' | 'dark';
-type ThemeContextProps = {
- theme: Theme;
- toggleTheme: () => void;
-};
-
-export const ThemeContext = createContext({
- theme: 'dark',
- toggleTheme: () => {},
-});
-
-export function useTheme() {
- const context = useContext(ThemeContext);
- if (context === undefined) {
- throw new Error('useTheme must be used within a ThemeProvider');
- }
- return context;
-}
-
-export default function ThemeProvider({ children }: { children: ReactNode }) {
- const [theme, setTheme] = useState('dark');
-
- const toggleTheme = useCallback(() => {
- setTheme((prev) => (prev === 'light' ? 'dark' : 'light'));
- }, []);
-
- useEffect(() => {
- const rootElement = document.documentElement;
- const observer = new MutationObserver(() => {
- if (rootElement.classList.contains('dark')) {
- setTheme('dark');
- } else {
- setTheme('light');
- }
- });
-
- observer.observe(rootElement, {
- attributes: true,
- attributeFilter: ['class'],
- });
-
- if (rootElement.classList.contains('dark')) {
- setTheme('dark');
- }
-
- return () => observer.disconnect();
- }, []);
-
- const values = useMemo(() => ({ theme, toggleTheme }), [theme, toggleTheme]);
-
- return {children} ;
-}
diff --git a/docs.json b/docs.json
new file mode 100644
index 00000000..439d31c7
--- /dev/null
+++ b/docs.json
@@ -0,0 +1,402 @@
+{
+ "$schema": "https://mintlify.com/docs.json",
+ "theme": "mint",
+ "name": "Base Documentation",
+ "colors": {
+ "primary": "#578BFA",
+ "light": "#578BFA",
+ "dark": "#578BFA"
+ },
+ "favicon": "/logo/favicon.svg",
+ "contextual": {
+ "options": [
+ "copy",
+ "chatgpt",
+ "claude"
+ ]
+ },
+ "api": {
+ "playground": {
+ "display": "simple"
+ },
+ "examples": {
+ "languages": [
+ "javascript"
+ ]
+ }
+ },
+ "navigation": {
+ "tabs": [
+ {
+ "tab": "Learn",
+ "groups": [
+ {
+ "group": "Building Onchain",
+ "pages": [
+ "learn/welcome"
+ ]
+ },
+ {
+ "group": "Onchain Concepts",
+ "pages": [
+ "learn/onchain-concepts/core-concepts",
+ "learn/onchain-concepts/understanding-the-onchain-tech-stack",
+ {
+ "group": "Web2 vs Building Onchain",
+ "pages": [
+ "learn/onchain-concepts/building-onchain-wallets",
+ "learn/onchain-concepts/building-onchain-identity",
+ "learn/onchain-concepts/building-onchain-gas",
+ "learn/onchain-concepts/building-onchain-nodes",
+ "learn/onchain-concepts/building-onchain-frontend-development",
+ "learn/onchain-concepts/building-onchain-onramps",
+ "learn/onchain-concepts/building-onchain-social-networks",
+ "learn/onchain-concepts/building-onchain-ai"
+ ]
+ },
+ "learn/onchain-concepts/development-flow",
+ "learn/onchain-concepts/continue-building-onchain"
+ ]
+ },
+ {
+ "group": "Ethereum 101",
+ "pages": [
+ "learn/introduction-to-ethereum",
+ "learn/ethereum-dev-overview",
+ "learn/ethereum-applications",
+ "learn/gas-use-in-eth-transactions",
+ "learn/evm-diagram",
+ "learn/guide-to-base"
+ ]
+ },
+ {
+ "group": "Onchain App Development",
+ "pages": [
+ "learn/onchain-app-development/deploy-with-fleek",
+ "learn/onchain-app-development/account-abstraction",
+ "learn/cross-chain-development",
+ "learn/client-side-development",
+ {
+ "group": "Account Abstraction",
+ "pages": [
+ "learn/onchain-app-development/account-abstraction/account-abstraction-on-base-using-biconomy",
+ "learn/onchain-app-development/account-abstraction/account-abstraction-on-base-using-particle-network",
+ "learn/onchain-app-development/account-abstraction/account-abstraction-on-base-using-privy-and-the-base-paymaster",
+ "learn/onchain-app-development/account-abstraction/gasless-transactions-with-paymaster"
+ ]
+ },
+ {
+ "group": "Client-Side Development",
+ "pages": [
+ "learn/onchain-app-development/client-side-development/introduction-to-providers",
+ "learn/onchain-app-development/client-side-development/viem",
+ "learn/onchain-app-development/client-side-development/web3"
+ ]
+ },
+ {
+ "group": "Cross-Chain",
+ "pages": [
+ "learn/onchain-app-development/cross-chain/bridge-tokens-with-layerzero",
+ "learn/onchain-app-development/cross-chain/send-messages-and-tokens-from-base-chainlink"
+ ]
+ },
+ {
+ "group": "Finance",
+ "pages": [
+ "learn/onchain-app-development/finance/build-a-smart-wallet-funding-app",
+ "learn/onchain-app-development/finance/access-real-world-data-chainlink",
+ "learn/onchain-app-development/finance/access-real-time-asset-data-pyth-price-feeds"
+ ]
+ }
+ ]
+ },
+ {
+ "group": "Smart Contract Development",
+ "pages": [
+ {
+ "group": "Introduction to Solidity",
+ "pages": [
+ "learn/introduction-to-solidity/introduction-to-solidity-overview",
+ "learn/introduction-to-solidity/anatomy-of-a-smart-contract-vid",
+ {
+ "group": "Introduction to Solidity",
+ "pages": [
+ "learn/introduction-to-solidity/introduction-to-solidity-vid",
+ "learn/introduction-to-solidity/solidity-overview",
+ "learn/introduction-to-solidity/introduction-to-remix-vid",
+ "learn/introduction-to-solidity/introduction-to-remix",
+ "learn/introduction-to-solidity/deployment-in-remix-vid",
+ "learn/introduction-to-solidity/deployment-in-remix"
+ ]
+ }
+ ]
+ },
+ {
+ "group": "Contracts and Basic Functions",
+ "pages": [
+ "learn/contracts-and-basic-functions/intro-to-contracts-vid",
+ "learn/contracts-and-basic-functions/hello-world-step-by-step",
+ "learn/contracts-and-basic-functions/basic-types",
+ "learn/contracts-and-basic-functions/basic-functions-exercise"
+ ]
+ },
+ {
+ "group": "Deploying to a Testnet",
+ "pages": [
+ "learn/deployment-to-testnet/overview-of-test-networks-vid",
+ "learn/deployment-to-testnet/test-networks",
+ "learn/deployment-to-testnet/deployment-to-base-sepolia-sbs",
+ "learn/deployment-to-testnet/contract-verification-sbs",
+ "learn/deployment-to-testnet/deployment-to-testnet-exercise"
+ ]
+ },
+ {
+ "group": "Control Structures",
+ "pages": [
+ "learn/control-structures/standard-control-structures-vid",
+ "learn/control-structures/loops-vid",
+ "learn/control-structures/require-revert-error-vid",
+ "learn/control-structures/control-structures",
+ "learn/control-structures/control-structures-exercise"
+ ]
+ },
+ {
+ "group": "Storage in Solidity",
+ "pages": [
+ "learn/storage/simple-storage-video",
+ "learn/storage/simple-storage-sbs",
+ "learn/storage/how-storage-works-video",
+ "learn/storage/how-storage-works",
+ "learn/storage/storage-exercise"
+ ]
+ },
+ {
+ "group": "Arrays in Solidity",
+ "pages": [
+ "learn/arrays/arrays-in-solidity-vid",
+ "learn/arrays/writing-arrays-in-solidity-vid",
+ "learn/arrays/arrays-in-solidity",
+ "learn/arrays/filtering-an-array-sbs",
+ "learn/arrays/fixed-size-arrays-vid",
+ "learn/arrays/array-storage-layout-vid",
+ "learn/arrays/arrays-exercise"
+ ]
+ },
+ {
+ "group": "The Mapping Type",
+ "pages": [
+ "learn/mappings/mappings-vid",
+ "learn/mappings/using-msg-sender-vid",
+ "learn/mappings/mappings-sbs",
+ "learn/mappings/how-mappings-are-stored-vid",
+ "learn/mappings/mappings-exercise"
+ ]
+ },
+ {
+ "group": "Advanced Functions",
+ "pages": [
+ "learn/advanced-functions/function-visibility-vid",
+ "learn/advanced-functions/function-visibility",
+ "learn/advanced-functions/function-modifiers-vid",
+ "learn/advanced-functions/function-modifiers"
+ ]
+ },
+ {
+ "group": "Structs",
+ "pages": [
+ "learn/structs/structs-vid",
+ "learn/structs/structs-sbs",
+ "learn/structs/structs-exercise"
+ ]
+ },
+ {
+ "group": "Inheritance",
+ "pages": [
+ "learn/inheritance/inheritance-vid",
+ "learn/inheritance/inheritance-sbs",
+ "learn/inheritance/multiple-inheritance-vid",
+ "learn/inheritance/multiple-inheritance",
+ "learn/inheritance/abstract-contracts-vid",
+ "learn/inheritance/abstract-contracts-sbs",
+ "learn/inheritance/inheritance-exercise"
+ ]
+ },
+ {
+ "group": "Imports",
+ "pages": [
+ "learn/imports/imports-vid",
+ "learn/imports/imports-sbs",
+ "learn/imports/imports-exercise"
+ ]
+ },
+ {
+ "group": "Errors",
+ "pages": [
+ "learn/error-triage/error-triage-vid",
+ "learn/error-triage/error-triage",
+ "learn/error-triage/error-triage-exercise"
+ ]
+ },
+ {
+ "group": "The new Keyword",
+ "pages": [
+ "learn/new-keyword/creating-a-new-contract-vid",
+ "learn/new-keyword/new-keyword-sbs",
+ "learn/new-keyword/new-keyword-exercise"
+ ]
+ },
+ {
+ "group": "Contract to Contract Interactions",
+ "pages": [
+ "learn/interfaces/intro-to-interfaces-vid",
+ "learn/interfaces/calling-another-contract-vid",
+ "learn/interfaces/testing-the-interface-vid",
+ "learn/interfaces/contract-to-contract-interaction"
+ ]
+ },
+ {
+ "group": "Events",
+ "pages": [
+ "learn/events/hardhat-events-sbs"
+ ]
+ },
+ {
+ "group": "Address and Payable",
+ "pages": [
+ "learn/address-and-payable/address-and-payable"
+ ]
+ }
+ ]
+ },
+ {
+ "group": "Development with Foundry",
+ "pages": [
+ "learn/foundry/introduction-to-foundry",
+ "learn/foundry/testing",
+ "learn/foundry/setup-with-base",
+ "learn/foundry/deploy-with-foundry",
+ "learn/foundry/testing-smart-contracts",
+ "learn/foundry/verify-contract-with-basescan",
+ "learn/foundry/generate-random-numbers-contracts"
+ ]
+ },
+ {
+ "group": "Development with Hardhat",
+ "pages": [
+ {
+ "group": "Hardhat Setup and Overview",
+ "pages": [
+ "learn/hardhat/overview",
+ "learn/hardhat/creating-project",
+ "learn/hardhat/setup"
+ ]
+ },
+ {
+ "group": "Testing with Typescript",
+ "pages": [
+ "learn/hardhat/testing",
+ "learn/hardhat/writing-tests",
+ "learn/hardhat/contract-abi-testing",
+ "learn/hardhat/testing-guide"
+ ]
+ },
+ {
+ "group": "Etherscan",
+ "pages": [
+ "learn/hardhat/etherscan-guide",
+ "learn/hardhat/etherscan-video"
+ ]
+ },
+ {
+ "group": "Deploying Smart Contracts",
+ "pages": [
+ "learn/hardhat/installing-deploy",
+ "learn/hardhat/setup-deploy-script",
+ "learn/hardhat/testing-deployment",
+ "learn/hardhat/network-configuration",
+ "learn/hardhat/deployment",
+ "learn/hardhat/deployment-guide"
+ ]
+ },
+ {
+ "group": "Verifying Smart Contracts",
+ "pages": [
+ "learn/hardhat/verify-video",
+ "learn/hardhat/verify-guide"
+ ]
+ },
+ {
+ "group": "Mainnet Forking",
+ "pages": [
+ "learn/hardhat/fork-video",
+ "learn/hardhat/fork-guide"
+ ]
+ },
+ {
+ "group": "Hardhat Tools and Guides",
+ "pages": [
+ "learn/hardhat/deploy-with-hardhat",
+ "learn/hardhat/debugging-smart-contracts",
+ "learn/hardhat/optimizing-gas-usage",
+ "learn/hardhat/reducing-contract-size",
+ "learn/hardhat/analyzing-test-coverage"
+ ]
+ }
+ ]
+ },
+ {
+ "group": "Token Development",
+ "pages": [
+ {
+ "group": "Introduction to Tokens",
+ "pages": [
+ "learn/intro-to-tokens/intro-to-tokens-vid",
+ "learn/intro-to-tokens/misconceptions-about-tokens-vid",
+ "learn/intro-to-tokens/tokens-overview"
+ ]
+ },
+ {
+ "group": "Minimal Tokens",
+ "pages": [
+ "learn/minimal-tokens/creating-a-minimal-token-vid",
+ "learn/minimal-tokens/transferring-a-minimal-token-vid",
+ "learn/minimal-tokens/minimal-token-sbs",
+ "learn/minimal-tokens/minimal-tokens-exercise"
+ ]
+ },
+ {
+ "group": "ERC-20 Tokens",
+ "pages": [
+ "learn/erc-20-token/analyzing-erc-20-vid",
+ "learn/erc-20-token/erc-20-standard",
+ "learn/erc-20-token/openzeppelin-erc-20-vid",
+ "learn/erc-20-token/erc-20-testing-vid",
+ "learn/erc-20-token/erc-20-token-sbs",
+ "learn/erc-20-token/erc-20-exercise"
+ ]
+ },
+ {
+ "group": "ERC-721 Tokens",
+ "pages": [
+ "learn/erc-721-token/erc-721-standard-video",
+ "learn/erc-721-token/erc-721-standard",
+ "learn/erc-721-token/erc-721-on-opensea-vid",
+ "learn/erc-721-token/openzeppelin-erc-721-vid",
+ "learn/erc-721-token/implementing-an-erc-721-vid",
+ "learn/erc-721-token/erc-721-sbs",
+ "learn/erc-721-token/erc-721-exercise"
+ ]
+ }
+ ]
+ },
+ {
+ "group": "Exercise Contracts",
+ "pages": [
+ "learn/exercise-contracts"
+ ]
+ }
+ ]
+ }
+ ]
+ }
+}
\ No newline at end of file
diff --git a/docs/_docs.json b/docs/_docs.json
new file mode 100644
index 00000000..8ab1fe7a
--- /dev/null
+++ b/docs/_docs.json
@@ -0,0 +1,550 @@
+{
+ "$schema": "https://mintlify.com/docs.json",
+ "theme": "mint",
+ "name": "Base Documentation",
+ "colors": {
+ "primary": "#578BFA",
+ "light": "#578BFA",
+ "dark": "#578BFA"
+ },
+ "favicon": "/favicon.svg",
+ "contextual": {
+ "options": ["copy", "chatgpt", "claude"]
+ },
+ "navigation": {
+ "tabs": [
+ {
+ "tab": "Get Started",
+ "groups": [
+ {
+ "group": "Introduction",
+ "pages": ["get-started/base"]
+ },
+ {
+ "group": "Browse by",
+ "pages": ["get-started/products", "get-started/use-cases"]
+ },
+ {
+ "group": "Quickstart",
+ "pages": [
+ "get-started/build-app",
+ "get-started/launch-token",
+ "get-started/deploy-chain",
+ "get-started/deploy-smart-contracts",
+ "get-started/get-funded"
+ ]
+ },
+ {
+ "group": "Build with AI",
+ "pages": ["get-started/ai-prompting", "get-started/prompt-library"]
+ }
+ ],
+ "global": {
+ "anchors": [
+ {
+ "anchor": "Status",
+ "href": "https://status.base.org/",
+ "icon": "signal-bars"
+ },
+ {
+ "anchor": "Faucet",
+ "href": "https://test-184b3b57.mintlify.app/base-chain/tools/network-faucets",
+ "icon": "gas-pump"
+ },
+ {
+ "anchor": "Bridge",
+ "href": "https://test-184b3b57.mintlify.app/base-chain/quickstart/bridge-token",
+ "icon": "coin"
+ }
+ ]
+ }
+ },
+ {
+ "tab": "Base Chain",
+ "groups": [
+ {
+ "group": "General",
+ "pages": [
+ "base-chain/general/network-fees",
+ "base-chain/general/differences-ethereum-base",
+ "base-chain/general/base-contracts"
+ ]
+ },
+ {
+ "group": "Quickstart",
+ "pages": [
+ "base-chain/quickstart/use-base",
+ "base-chain/quickstart/deploy-on-base",
+ "base-chain/quickstart/run-base-node",
+ "base-chain/quickstart/bridge-token"
+ ]
+ },
+ {
+ "group": "Network Information",
+ "pages": [
+ "base-chain/network-information/diffs-ethereum-base",
+ "base-chain/network-information/base-contracts"
+ ]
+ },
+ {
+ "group": "Flashblocks",
+ "pages": [
+ "base-chain/flashblocks/apps",
+ "base-chain/flashblocks/node-providers"
+ ]
+ },
+ {
+ "group": "Node Operators",
+ "pages": [
+ "base-chain/node-operators/performance-tuning",
+ "base-chain/node-operators/snapshots",
+ "base-chain/node-operators/troubleshooting"
+ ]
+ },
+ {
+ "group": "Tools",
+ "pages": [
+ "base-chain/tools/base-products",
+ "base-chain/tools/onchain-registry-api",
+ "base-chain/tools/node-providers",
+ "base-chain/tools/block-explorers",
+ "base-chain/tools/network-faucets",
+ "base-chain/tools/oracles",
+ "base-chain/tools/data-indexers",
+ "base-chain/tools/cross-chain",
+ "base-chain/tools/account-abstraction",
+ "base-chain/tools/onramps"
+ ]
+ },
+ {
+ "group": "Security",
+ "pages": [
+ "base-chain/security/security-council",
+ "base-chain/security/avoid-malicious-flags",
+ "base-chain/security/report-vulnerability"
+ ]
+ }
+ ],
+ "global": {
+ "anchors": [
+ {
+ "anchor": "GitHub",
+ "href": "https://github.com/base",
+ "icon": "github"
+ },
+ {
+ "anchor": "Status",
+ "href": "https://status.base.org/",
+ "icon": "signal-bars"
+ },
+ {
+ "anchor": "Chain Stats",
+ "href": "https://www.base.org/stats",
+ "icon": "chart-line"
+ },
+ {
+ "anchor": "Explorer",
+ "href": "https://basescan.com/",
+ "icon": "magnifying-glass"
+ },
+ {
+ "anchor": "Support",
+ "href": "https://discord.com/invite/base",
+ "icon": "discord"
+ }
+ ]
+ }
+ },
+ {
+ "tab": "Smart Wallet",
+ "groups": [
+ {
+ "group": "Get started",
+ "pages": [
+ "smart-wallet/overview",
+ "smart-wallet/quickstart",
+ "smart-wallet/recommend-libraries",
+ "smart-wallet/base-gasless-campaign"
+ ]
+ },
+ {
+ "group": "Features",
+ "pages": [
+ "smart-wallet/features/single-sign-on",
+ "smart-wallet/features/networks",
+ "smart-wallet/features/passkeys",
+ "smart-wallet/features/recovery",
+ "smart-wallet/features/magicspend",
+ {
+ "group": "Optional Features",
+ "pages": [
+ "smart-wallet/features/gas-free-transactions",
+ "smart-wallet/features/spend-permissions",
+ "smart-wallet/features/batch-transactions",
+ "smart-wallet/features/custom-gas-tokens",
+ "smart-wallet/features/sub-accounts"
+ ]
+ }
+ ]
+ },
+ {
+ "group": "Usage",
+ "pages": [
+ "smart-wallet/usage/signature-verification",
+ "smart-wallet/usage/popups",
+ "smart-wallet/usage/simulations",
+ "smart-wallet/usage/gas-usage",
+ "smart-wallet/usage/self-calls"
+ ]
+ },
+ {
+ "group": "SDK",
+ "pages": [
+ "smart-wallet/sdk/install",
+ "smart-wallet/sdk/setup",
+ "smart-wallet/sdk/make-web3-provider",
+ "smart-wallet/sdk/upgrading-from-3x",
+ "smart-wallet/sdk/coinbase-wallet-provider"
+ ]
+ },
+ {
+ "group": "Guides",
+ "pages": [
+ "smart-wallet/guides/update-existing-app",
+ "smart-wallet/guides/signing-and-verifying",
+ "smart-wallet/guides/sign-in-with-ethereum",
+ "smart-wallet/guides/magicspend",
+ "smart-wallet/guides/batch-transactions",
+ "smart-wallet/guides/paymasters",
+ "smart-wallet/guides/erc20-paymasters",
+ {
+ "group": "Sub Accounts",
+ "pages": [
+ "smart-wallet/guides/sub-accounts/overview",
+ "smart-wallet/guides/sub-accounts/setup",
+ "smart-wallet/guides/sub-accounts/creating",
+ "smart-wallet/guides/sub-accounts/using"
+ ]
+ },
+ {
+ "group": "Spend Permissions",
+ "pages": [
+ "smart-wallet/guides/spend-permissions/overview",
+ "smart-wallet/guides/spend-permissions/quickstart",
+ "smart-wallet/guides/spend-permissions/api-reference"
+ ]
+ }
+ ]
+ }
+ ],
+ "global": {
+ "anchors": [
+ {
+ "anchor": "GitHub",
+ "href": "https://github.com/coinbase/onchainkit",
+ "icon": "github"
+ },
+ {
+ "anchor": "Support",
+ "href": "https://discord.com/invite/cdp",
+ "icon": "discord"
+ }
+ ]
+ }
+ },
+ {
+ "tab": "OnchainKit",
+ "groups": [
+ {
+ "group": "Get Started",
+ "pages": [
+ "onchainkit/quickstart",
+ "onchainkit/templates",
+ {
+ "group": "Installation",
+ "pages": ["onchainkit/nextjs", "onchainkit/vite"]
+ },
+ "onchainkit/troubleshoot",
+ "onchainkit/telemetry"
+ ]
+ },
+ {
+ "group": "Guides",
+ "pages": [
+ "onchainkit/guides/build-with-ai",
+ "onchainkit/guides/lifecycle-status",
+ "onchainkit/guides/reach-more-users-with-minikit",
+ "onchainkit/guides/tailwind-css-integration",
+ "onchainkit/guides/theme-customization",
+ "onchainkit/guides/use-basenames"
+ ]
+ },
+ {
+ "group": "Components",
+ "pages": [
+ "onchainkit/components/bridge",
+ "onchainkit/components/buy",
+ "onchainkit/components/checkout",
+ "onchainkit/components/earn",
+ "onchainkit/components/fund",
+ "onchainkit/components/identity",
+ "onchainkit/components/mint",
+ "onchainkit/components/swap",
+ "onchainkit/components/token",
+ "onchainkit/components/transaction",
+ "onchainkit/components/wallet"
+ ]
+ },
+ {
+ "group": "API",
+ "openapi": {
+ "source": "docs/openapi/onchainkit.yaml",
+ "directory": "api-reference"
+ }
+ },
+ {
+ "group": "Utilities",
+ "pages": ["onchainkit/utilities/is-base"]
+ },
+ {
+ "group": "Contribute",
+ "pages": ["onchainkit/contribute/report-a-bug"]
+ }
+ ],
+ "global": {
+ "anchors": [
+ {
+ "anchor": "GitHub",
+ "href": "https://github.com/coinbase/onchainkit",
+ "icon": "github"
+ },
+ {
+ "anchor": "Playground",
+ "href": "https://onchainkit.xyz/playground",
+ "icon": "gamepad"
+ },
+ {
+ "anchor": "Support",
+ "href": "https://discord.com/invite/cdp",
+ "icon": "discord"
+ }
+ ]
+ }
+ },
+ {
+ "tab": "Cookbook",
+ "groups": [
+ {
+ "group": "Use Cases",
+ "pages": [
+ "cookbook/onboard-any-user",
+ "cookbook/accept-crypto-payments",
+ "cookbook/launch-ai-agents",
+ "cookbook/launch-tokens",
+ "cookbook/deploy-a-chain",
+ "cookbook/decentralize-your-social-app",
+ "cookbook/defi-your-app",
+ "cookbook/go-gasless"
+ ]
+ },
+ {
+ "group": "Build with AI",
+ "pages": ["cookbook/ai-prompting", "cookbook/base-builder-mcp"]
+ }
+ ]
+ },
+ {
+ "tab": "Showcase",
+ "pages": ["showcase"]
+ },
+ {
+ "tab": "Learn",
+ "groups": [
+ {
+ "group": "Building Onchain",
+ "pages": [
+ "learn/welcome",
+ {
+ "group": "Onchain Concepts",
+ "pages": [
+ "learn/onchain-concepts/the-onchain-tech-stack",
+ "learn/onchain-concepts/unique-aspects-of-building-onchain",
+ "learn/onchain-concepts/onchain-development-flow",
+ "learn/onchain-concepts/offchain-to-onchain"
+ ]
+ }
+ ]
+ },
+ {
+ "group": "Ethereum 101",
+ "pages": [
+ "learn/introduction-to-ethereum",
+ "learn/ethereum-dev-overview",
+ "learn/ethereum-applications",
+ "learn/gas-use-in-eth-transactions",
+ "learn/evm-diagram",
+ "learn/guide-to-base"
+ ]
+ },
+ {
+ "group": "Onchain App Development",
+ "pages": [
+ "learn/deploy-with-fleek",
+ "learn/account-abstraction",
+ "learn/cross-chain-development",
+ "learn/client-side-development"
+ ]
+ },
+ {
+ "group": "Smart Contract Development",
+ "pages": [
+ "learn/solidity/introduction",
+ "learn/solidity/anatomy",
+ {
+ "group": "Introduction to Solidity",
+ "pages": [
+ "learn/solidity/video-tutorial",
+ "learn/solidity/overview",
+ "learn/solidity/introduction-to-remix",
+ "learn/solidity/remix-guide",
+ "learn/solidity/deployment-in-remix",
+ "learn/solidity/step-by-step"
+ ]
+ },
+ {
+ "group": "Contracts and Basic Functions",
+ "pages": [
+ "learn/solidity/introduction-to-contracts",
+ "learn/solidity/hello-world",
+ "learn/solidity/basic-types",
+ "learn/solidity/exercise-basics"
+ ]
+ },
+ {
+ "group": "Deploying to a Testnet",
+ "pages": [
+ "learn/solidity/test-networks-overview",
+ "learn/solidity/test-networks",
+ "learn/solidity/deploy-to-sepolia",
+ "learn/solidity/contract-verification",
+ "learn/solidity/exercise-deployment"
+ ]
+ },
+ {
+ "group": "Control Structures",
+ "pages": [
+ "learn/solidity/standard-control-structures",
+ "learn/solidity/loops",
+ "learn/solidity/require-revert-error",
+ "learn/solidity/control-overview",
+ "learn/solidity/exercise-control"
+ ]
+ }
+ ]
+ },
+ {
+ "group": "Development with Foundry",
+ "pages": [
+ "learn/foundry/introduction-to-foundry",
+ "learn/foundry/testing"
+ ]
+ },
+ {
+ "group": "Development with Hardhat",
+ "pages": [
+ {
+ "group": "Hardhat Setup and Overview",
+ "pages": [
+ "learn/hardhat/overview",
+ "learn/hardhat/creating-project",
+ "learn/hardhat/setup"
+ ]
+ },
+ {
+ "group": "Testing with Typescript",
+ "pages": [
+ "learn/hardhat/testing",
+ "learn/hardhat/writing-tests",
+ "learn/hardhat/contract-abi-testing",
+ "learn/hardhat/testing-guide"
+ ]
+ },
+ {
+ "group": "Etherscan",
+ "pages": [
+ "learn/hardhat/etherscan-guide",
+ "learn/hardhat/etherscan-video"
+ ]
+ },
+ {
+ "group": "Deploying Smart Contracts",
+ "pages": [
+ "learn/hardhat/installing-deploy",
+ "learn/hardhat/setup-deploy-script",
+ "learn/hardhat/testing-deployment",
+ "learn/hardhat/network-configuration",
+ "learn/hardhat/deployment",
+ "learn/hardhat/deployment-guide"
+ ]
+ },
+ {
+ "group": "Verifying Smart Contracts",
+ "pages": [
+ "learn/hardhat/verify-video",
+ "learn/hardhat/verify-guide"
+ ]
+ },
+ {
+ "group": "Mainnet Forking",
+ "pages": [
+ "learn/hardhat/fork-video",
+ "learn/hardhat/fork-guide"
+ ]
+ }
+ ]
+ },
+ {
+ "group": "Token Development",
+ "pages": []
+ },
+ {
+ "group": "Exercise Contracts",
+ "pages": ["learn/exercise-contracts"]
+ }
+ ]
+ }
+ ]
+ },
+ "logo": {
+ "light": "/logo/light.svg",
+ "dark": "/logo/dark.svg"
+ },
+ "navbar": {
+ "links": [
+ {
+ "label": "Blog",
+ "href": "https://blog.base.dev/"
+ },
+ {
+ "label": "GitHub",
+ "href": "https://github.com/base"
+ },
+ {
+ "label": "Support",
+ "href": "https://discord.com/invite/base"
+ }
+ ],
+ "primary": {
+ "type": "button",
+ "label": "Base.org",
+ "href": "https://base.org"
+ }
+ },
+ "footer": {
+ "socials": {
+ "x": "https://x.com/mintlify",
+ "github": "https://github.com/mintlify",
+ "linkedin": "https://linkedin.com/company/mintlify"
+ }
+ }
+}
diff --git a/docs/base-chain/flashblocks/apps.mdx b/docs/base-chain/flashblocks/apps.mdx
new file mode 100644
index 00000000..ac866eb2
--- /dev/null
+++ b/docs/base-chain/flashblocks/apps.mdx
@@ -0,0 +1,195 @@
+---
+title: Flashblocks
+sidebarTitle: Apps
+description: Experience lightning-fast transaction confirmations on Base by using Flashblocks. Preconfirmations happen in just 200 milliseconds—designed for real-time apps, games, and seamless UX.
+---
+
+## Overview
+
+Flashblocks enable up to 200 millisecond transaction confirmations on Base by leveraging preconfirmations, ultra-fast signals that arrive before the next block is sealed. Built for developers who demand instant UX, it's ideal for high-frequency apps, games, and real-time interactions where waiting even a few seconds is too long. By integrating directly within Base's infrastructure, Flashblocks enables, seamless, ultrafast and snappy user experiences without compromising security.
+
+## Integrating Flashblocks
+
+Flashblocks is enabled for developers on Base Sepolia with full support for mainnet coming very soon. There are two ways you can integrate with Flashblocks data. You can either use the WebSocket API to stream real-time block updates, or use the RPC API to query the Flashblocks-aware RPC endpoint.
+
+### WebSocket API
+
+Use our API to stream realtime block updates over a WebSocket.
+
+You can connect to the websocket endpoint with any WebSocket library of CLI tool. The endpoint is available at wss://sepolia.flashblocks.base.org/ws.
+
+Two recommended tools for connecting to the WebSocket endpoint are [Websocat](https://github.com/vi/websocat) and the [Javascript Websocket Client](https://developer.mozilla.org/en-US/docs/Web/API/WebSockets_API/Writing_WebSocket_client_applicationsjk).
+
+#### Websocat Example
+
+Firstly install websocat, [following these instructions](https://github.com/vi/websocat?tab=readme-ov-file#installation).
+
+From your terminal, you can then connect to the websocket stream by running:
+```
+websocat wss://sepolia.flashblocks.base.org/ws
+```
+
+In your terminal, you'll see a stream of all the Flashblocks being sent over the websocket connection.
+
+#### Interpreting the data
+
+To minimize the amount of data sent to clients, each Flashblock only includes the diff data from the previous block. The initial Flashblock (when index is zero) includes the block properties (e.g. number, gas limit) and the subsequent Flashblocks only include the diff data (e.g. transactions that are present in that Flashblock).
+
+**Example Initial Response**
+```
+{
+ "payload_id": "0x03997352d799c31a",
+ "index": 0,
+ "base": {
+ "parent_hash": "0x9edc29b8b0a1e31d28616e40c16132ad0d58faa8bb952595b557526bdb9a960a",
+ "fee_recipient": "0x4200000000000000000000000000000000000011",
+ "block_number": "0x158a0e9",
+ "gas_limit": "0x3938700",
+ "timestamp": "0x67bf8332",
+ "base_fee_per_gas": "0xfa"
+ // ... other base fields ...
+ },
+ "diff": {
+ "state_root": "0x208fd63edc0681161105f27d03daf9f8c726d8c94e584a3c0696c98291c24333",
+ "block_hash": "0x5c330e55a190f82ea486b61e5b12e27dfb4fb3cecfc5746886ef38ca1281bce8",
+ "gas_used": "0xab3f",
+ "transactions": [
+ "0x7ef8f8a0b4afc0b7ce10e150801bbaf08ac33fecb0f38311793abccb022120d321c6d276..."
+ ],
+ "withdrawals": []
+ // ... other diff fields ...
+ },
+ "metadata": {
+ "block_number": 22585577,
+ "new_account_balances": {
+ "0x000f3df6d732807ef1319fb7b8bb8522d0beac02": "0x0",
+ // ... other balances ...
+ },
+ "receipts": {
+ "0x07d7f06b06fea714c1d1d446efa2790c6970aa74ee006186a32b5b7dd8ca2d82": {
+ "Deposit": {
+ "status": "0x1",
+ "depositNonce": "0x158a0ea"
+ // ... other receipt fields ...
+ }
+ }
+ }
+ }
+}
+```
+
+**Example Diff Response**
+```
+{
+ "payload_id": "0x03e303378749418d",
+ "index": 4,
+ "diff": {
+ "state_root": "0x7a8f45038665072f382730e689f4a1561835c9987fca8942fa95872fb9367eaa",
+ "block_hash": "0x9b32f7a14cbd1efc8c2c5cad5eb718ec9e0c5da92c3ba7080f8d4c49d660c332",
+ "gas_used": "0x1234f",
+ "transactions": [
+ "0x7ef8f8a0b4afc0b7ce10e150801bbaf08ac33fecb0f38311793abccb022120d321c6d276..."
+ ],
+ "withdrawals": []
+ // ... other diff fields ...
+ },
+ "metadata": {
+ "block_number": 22585577,
+ "new_account_balances": {
+ "0x000f3df6d732807ef1319fb7b8bb8522d0beac02": "0x0",
+ "0x4200000000000000000000000000000000000015": "0x1234"
+ // ... other balances ...
+ },
+ "receipts": {
+ "0x07d7f06b06fea714c1d1d446efa2790c6970aa74ee006186a32b5b7dd8ca2d82": {
+ "status": "0x1",
+ "gasUsed": "0x1234f",
+ "logs": []
+ // ... other receipt fields ...
+ }
+ }
+ }
+}
+```
+
+### RPC API
+
+You can also utilize our Flashblock aware RPC endpoint at `https://sepolia-preconf.base.org`.
+
+In addition to these flashblock-specific methods, all standard Ethereum JSON-RPC methods are supported as usual.
+
+#### eth_getBlockByNumber
+
+Use the `pending` tag to retrieve the latest Flashblock:
+```
+curl https://sepolia-preconf.base.org -X POST -H "Content-Type: application/json" -d '{"jsonrpc":"2.0","method":"eth_getBlockByNumber","params":["pending",true],"id":1}'
+```
+
+**Example Response**
+```
+{
+ "jsonrpc": "2.0",
+ "id": 1,
+ "result": {
+ "number": "0x1234",
+ "hash": "0x...",
+ "transactions": [...]
+ }
+}
+```
+
+#### eth_getTransactionReceipt
+
+Use the existing receipt RPC to get preconfirmed receipts:
+```
+curl https://sepolia-preconf.base.org -X POST -H "Content-Type: application/json" -d '{"jsonrpc":"2.0","method":"eth_getTransactionReceipt","params":["0x..."],"id":1}'
+```
+
+**Example Response**
+```
+{
+ "jsonrpc": "2.0",
+ "id": 1,
+ "result": {
+ "transactionHash": "0x...",
+ "blockNumber": "0x1234",
+ "status": "0x1"
+ }
+}
+```
+
+#### eth_getBalance
+
+Use the `pending` tag to get the address balance in the latest Flashblock:
+```
+curl https://sepolia-preconf.base.org -X POST -H "Content-Type: application/json" -d '{"jsonrpc":"2.0","method":"eth_getBalance","params":["0x...","pending"],"id":1}'
+```
+
+**Example Response**
+```
+{
+ "jsonrpc": "2.0",
+ "id": 1,
+ "result": "0x0234"
+}
+```
+
+#### eth_getTransactionCount
+
+Use the `pending` tag to get the address nonce in the latest Flashblock:
+```
+curl https://sepolia-preconf.base.org -X POST -H "Content-Type: application/json" -d '{"jsonrpc":"2.0","method":"eth_getTransactionCount","params":["0x...","pending"],"id":1}'
+```
+
+**Example Response**
+```
+{
+ "jsonrpc": "2.0",
+ "id": 1,
+ "result": "0x1b" // 27 transactions
+}
+```
+
+## Support
+
+For feedback, support or questions about Flashblocks, please don't hesitate to contact us in the `#developer-chat` channel in the [Base Discord](https://base.org/discord).
diff --git a/docs/base-chain/flashblocks/node-providers.mdx b/docs/base-chain/flashblocks/node-providers.mdx
new file mode 100644
index 00000000..699e5c46
--- /dev/null
+++ b/docs/base-chain/flashblocks/node-providers.mdx
@@ -0,0 +1,48 @@
+---
+title: How to host Flashblocks-aware RPC nodes
+sidebarTitle: Node Providers
+---
+
+## Quick Start
+
+1. **Prerequisites**:
+ - Docker and Docker Compose
+ - Minimum hardware requirements (see [node README](https://github.com/base/node?tab=readme-ov-file#hardware-requirements))
+ - Access to a Flashblocks websocket endpoint, we provide public endpoints in the env files in the repo
+
+2. **Set Up Environment**:
+
+ ```sh
+ # Clone the repository
+ git clone https://github.com/base/node.git
+ cd node
+ ```
+
+3. **Start the Node with Flashblocks Support**:
+
+ ```sh
+ NODE_TYPE=base CLIENT=reth docker-compose up
+ ```
+
+## Configuration Options
+
+- Node Type: Use `NODE_TYPE=base` to enable base reth node withFlashblocks functionality
+- Network: Use `NETWORK_ENV=.env.mainnet` for mainnet or `NETWORK_ENV=.env.sepolia` for testnet
+
+## Verifying Flashblocks Functionality
+
+Test that your node is properly supporting Flashblocks by querying a pending block:
+
+```sh
+curl -X POST \
+ --data '{"jsonrpc":"2.0","method":"eth_getBlockByNumber","params":["pending", false],"id":1}' \
+ http://localhost:8545
+```
+
+## Available RPC Methods
+
+Flashblocks-aware nodes provide all standard Ethereum JSON-RPC methods plus specialized Flashblocks endpoints. For more details, see the [Flashblocks RPC API documentation](/base-chain/flashblocks/apps#rpc-api).
+
+## Further Resources
+
+For detailed information about node setup, including hardware requirements and additional configuration options, refer to the [Reth node README](https://github.com/base/node/tree/main/reth#readme).
\ No newline at end of file
diff --git a/docs/base-chain/network-information/base-contracts.mdx b/docs/base-chain/network-information/base-contracts.mdx
new file mode 100644
index 00000000..a8938937
--- /dev/null
+++ b/docs/base-chain/network-information/base-contracts.mdx
@@ -0,0 +1,131 @@
+---
+sidebarTitle: Base Contracts
+title: Contract Addresses
+description: A comprehensive list of L2 contract addresses for Base Mainnet and Base Testnet, including links to their respective blockchain explorers.
+---
+
+## L2 Contract Addresses
+
+### Base Mainnet
+
+| Name | Address |
+| :---------------------------- | :-------------------------------------------------------------------------------------------------------------------- |
+| WETH9 | [0x4200000000000000000000000000000000000006](https://basescan.org/address/0x4200000000000000000000000000000000000006) |
+| L2CrossDomainMessenger | [0x4200000000000000000000000000000000000007](https://basescan.org/address/0x4200000000000000000000000000000000000007) |
+| L2StandardBridge | [0x4200000000000000000000000000000000000010](https://basescan.org/address/0x4200000000000000000000000000000000000010) |
+| SequencerFeeVault | [0x4200000000000000000000000000000000000011](https://basescan.org/address/0x4200000000000000000000000000000000000011) |
+| OptimismMintableERC20Factory | [0xF10122D428B4bc8A9d050D06a2037259b4c4B83B](https://basescan.org/address/0xF10122D428B4bc8A9d050D06a2037259b4c4B83B) |
+| GasPriceOracle | [0x420000000000000000000000000000000000000F](https://basescan.org/address/0x420000000000000000000000000000000000000F) |
+| L1Block | [0x4200000000000000000000000000000000000015](https://basescan.org/address/0x4200000000000000000000000000000000000015) |
+| L2ToL1MessagePasser | [0x4200000000000000000000000000000000000016](https://basescan.org/address/0x4200000000000000000000000000000000000016) |
+| L2ERC721Bridge | [0x4200000000000000000000000000000000000014](https://basescan.org/address/0x4200000000000000000000000000000000000014) |
+| OptimismMintableERC721Factory | [0x4200000000000000000000000000000000000017](https://basescan.org/address/0x4200000000000000000000000000000000000017) |
+| ProxyAdmin | [0x4200000000000000000000000000000000000018](https://basescan.org/address/0x4200000000000000000000000000000000000018) |
+| BaseFeeVault | [0x4200000000000000000000000000000000000019](https://basescan.org/address/0x4200000000000000000000000000000000000019) |
+| L1FeeVault | [0x420000000000000000000000000000000000001a](https://basescan.org/address/0x420000000000000000000000000000000000001a) |
+| EAS | [0x4200000000000000000000000000000000000021](https://basescan.org/address/0x4200000000000000000000000000000000000021) |
+| EASSchemaRegistry | [0x4200000000000000000000000000000000000020](https://basescan.org/address/0x4200000000000000000000000000000000000020) |
+| LegacyERC20ETH | [0xDeadDeAddeAddEAddeadDEaDDEAdDeaDDeAD0000](https://basescan.org/address/0xDeadDeAddeAddEAddeadDEaDDEAdDeaDDeAD0000) |
+
+### Base Testnet (Sepolia)
+
+| Name | Address |
+| :---------------------------- | :---------------------------------------------------------------------------------------------------------------------------- |
+| WETH9 | [0x4200000000000000000000000000000000000006](https://sepolia.basescan.org/address/0x4200000000000000000000000000000000000006) |
+| L2CrossDomainMessenger | [0x4200000000000000000000000000000000000007](https://sepolia.basescan.org/address/0x4200000000000000000000000000000000000007) |
+| L2StandardBridge | [0x4200000000000000000000000000000000000010](https://sepolia.basescan.org/address/0x4200000000000000000000000000000000000010) |
+| SequencerFeeVault | [0x4200000000000000000000000000000000000011](https://sepolia.basescan.org/address/0x4200000000000000000000000000000000000011) |
+| OptimismMintableERC20Factory | [0x4200000000000000000000000000000000000012](https://sepolia.basescan.org/address/0x4200000000000000000000000000000000000012) |
+| GasPriceOracle | [0x420000000000000000000000000000000000000F](https://sepolia.basescan.org/address/0x420000000000000000000000000000000000000F) |
+| L1Block | [0x4200000000000000000000000000000000000015](https://sepolia.basescan.org/address/0x4200000000000000000000000000000000000015) |
+| L2ToL1MessagePasser | [0x4200000000000000000000000000000000000016](https://sepolia.basescan.org/address/0x4200000000000000000000000000000000000016) |
+| L2ERC721Bridge | [0x4200000000000000000000000000000000000014](https://sepolia.basescan.org/address/0x4200000000000000000000000000000000000014) |
+| OptimismMintableERC721Factory | [0x4200000000000000000000000000000000000017](https://sepolia.basescan.org/address/0x4200000000000000000000000000000000000017) |
+| ProxyAdmin | [0x4200000000000000000000000000000000000018](https://sepolia.basescan.org/address/0x4200000000000000000000000000000000000018) |
+| BaseFeeVault | [0x4200000000000000000000000000000000000019](https://sepolia.basescan.org/address/0x4200000000000000000000000000000000000019) |
+| L1FeeVault | [0x420000000000000000000000000000000000001a](https://sepolia.basescan.org/address/0x420000000000000000000000000000000000001a) |
+| EAS | [0x4200000000000000000000000000000000000021](https://sepolia.basescan.org/address/0x4200000000000000000000000000000000000021) |
+| EASSchemaRegistry | [0x4200000000000000000000000000000000000020](https://sepolia.basescan.org/address/0x4200000000000000000000000000000000000020) |
+| LegacyERC20ETH | [0xDeadDeAddeAddEAddeadDEaDDEAdDeaDDeAD0000](https://sepolia.basescan.org/address/0xDeadDeAddeAddEAddeadDEaDDEAdDeaDDeAD0000) |
+
+\*_L2 contract addresses are the same on both mainnet and testnet._
+
+## L1 Contract Addresses
+
+### Ethereum Mainnet
+
+| Name | Address |
+| :--------------------------- | :-------------------------------------------------------------------------------------------------------------------- |
+| AddressManager | [0x8EfB6B5c4767B09Dc9AA6Af4eAA89F749522BaE2](https://etherscan.io/address/0x8EfB6B5c4767B09Dc9AA6Af4eAA89F749522BaE2) |
+| AnchorStateRegistryProxy | [0x496286e5eE7758de84Dd17e6d2d97afC2ACE4cc7](https://etherscan.io/address/0x496286e5eE7758de84Dd17e6d2d97afC2ACE4cc7) |
+| DelayedWETHProxy (FDG) | [0xa2f2aC6F5aF72e494A227d79Db20473Cf7A1FFE8](https://etherscan.io/address/0xa2f2aC6F5aF72e494A227d79Db20473Cf7A1FFE8) |
+| DelayedWETHProxy (PDG) | [0x3E8a0B63f57e975c268d610ece93da5f78c01321](https://etherscan.io/address/0x3E8a0B63f57e975c268d610ece93da5f78c01321) |
+| DisputeGameFactoryProxy | [0x43edB88C4B80fDD2AdFF2412A7BebF9dF42cB40e](https://etherscan.io/address/0x43edB88C4B80fDD2AdFF2412A7BebF9dF42cB40e) |
+| FaultDisputeGame | [0xE17d670043c3cDd705a3223B3D89A228A1f07F0f](https://etherscan.io/address/0xE17d670043c3cDd705a3223B3D89A228A1f07F0f) |
+| L1CrossDomainMessenger | [0x866E82a600A1414e583f7F13623F1aC5d58b0Afa](https://etherscan.io/address/0x866E82a600A1414e583f7F13623F1aC5d58b0Afa) |
+| L1ERC721Bridge | [0x608d94945A64503E642E6370Ec598e519a2C1E53](https://etherscan.io/address/0x608d94945A64503E642E6370Ec598e519a2C1E53) |
+| L1StandardBridge | [0x3154Cf16ccdb4C6d922629664174b904d80F2C35](https://etherscan.io/address/0x3154Cf16ccdb4C6d922629664174b904d80F2C35) |
+| MIPS | [0xF027F4A985560fb13324e943edf55ad6F1d15Dc1](https://etherscan.io/address/0xF027F4A985560fb13324e943edf55ad6F1d15Dc1) |
+| OptimismMintableERC20Factory | [0x05cc379EBD9B30BbA19C6fA282AB29218EC61D84](https://etherscan.io/address/0x05cc379EBD9B30BbA19C6fA282AB29218EC61D84) |
+| OptimismPortal | [0x49048044D57e1C92A77f79988d21Fa8fAF74E97e](https://etherscan.io/address/0x49048044D57e1C92A77f79988d21Fa8fAF74E97e) |
+| PermissionedDisputeGame | [0xE749aA49c3eDAF1DCb997eA3DAC23dff72bcb826](https://etherscan.io/address/0xE749aA49c3eDAF1DCb997eA3DAC23dff72bcb826) |
+| PreimageOracle | [0x1fb8cdFc6831fc866Ed9C51aF8817Da5c287aDD3](https://etherscan.io/address/0x1fb8cdFc6831fc866Ed9C51aF8817Da5c287aDD3) |
+| ProxyAdmin | [0x0475cBCAebd9CE8AfA5025828d5b98DFb67E059E](https://etherscan.io/address/0x0475cBCAebd9CE8AfA5025828d5b98DFb67E059E) |
+| SystemConfig | [0x73a79Fab69143498Ed3712e519A88a918e1f4072](https://etherscan.io/address/0x73a79Fab69143498Ed3712e519A88a918e1f4072) |
+| SystemDictator | [0x1fE3fdd1F0193Dd657C0a9AAC37314D6B479E557](https://etherscan.io/address/0x1fE3fdd1F0193Dd657C0a9AAC37314D6B479E557) |
+
+**Unneeded contract addresses**
+
+Certain contracts are mandatory according to the [OP Stack SDK](https://stack.optimism.io/docs/build/sdk/#unneeded-contract-addresses), despite not being utilized. For such contracts, you can simply assign the zero address:
+
+- `StateCommitmentChain`
+- `CanonicalTransactionChain`
+- `BondManager`
+
+### Ethereum Testnet (Sepolia)
+
+| Name | Address |
+| :--------------------------- | :---------------------------------------------------------------------------------------------------------------------------- |
+| AddressManager | [0x709c2B8ef4A9feFc629A8a2C1AF424Dc5BD6ad1B](https://sepolia.etherscan.io/address/0x709c2B8ef4A9feFc629A8a2C1AF424Dc5BD6ad1B) |
+| AnchorStateRegistryProxy | [0x0729957c92A1F50590A84cb2D65D761093f3f8eB](https://sepolia.etherscan.io/address/0x0729957c92A1F50590A84cb2D65D761093f3f8eB) |
+| DelayedWETHProxy (FDG) | [0x489c2E5ebe0037bDb2DC039C5770757b8E54eA1F](https://sepolia.etherscan.io/address/0x489c2E5ebe0037bDb2DC039C5770757b8E54eA1F) |
+| DelayedWETHProxy (PDG) | [0x27A6128F707de3d99F89Bf09c35a4e0753E1B808](https://sepolia.etherscan.io/address/0x27A6128F707de3d99F89Bf09c35a4e0753E1B808) |
+| DisputeGameFactoryProxy | [0xd6E6dBf4F7EA0ac412fD8b65ED297e64BB7a06E1](https://sepolia.etherscan.io/address/0xd6E6dBf4F7EA0ac412fD8b65ED297e64BB7a06E1) |
+| FaultDisputeGame | [0xcfce7dd673fbbbffd16ab936b7245a2f2db31c9a](https://sepolia.etherscan.io/address/0xcfce7dd673fbbbffd16ab936b7245a2f2db31c9a) |
+| L1CrossDomainMessenger | [0xC34855F4De64F1840e5686e64278da901e261f20](https://sepolia.etherscan.io/address/0xC34855F4De64F1840e5686e64278da901e261f20) |
+| L1ERC721Bridge | [0x21eFD066e581FA55Ef105170Cc04d74386a09190](https://sepolia.etherscan.io/address/0x21eFD066e581FA55Ef105170Cc04d74386a09190) |
+| L1StandardBridge | [0xfd0Bf71F60660E2f608ed56e1659C450eB113120](https://sepolia.etherscan.io/address/0xfd0Bf71F60660E2f608ed56e1659C450eB113120) |
+| L2OutputOracle | [0x84457ca9D0163FbC4bbfe4Dfbb20ba46e48DF254](https://sepolia.etherscan.io/address/0x84457ca9D0163FbC4bbfe4Dfbb20ba46e48DF254) |
+| MIPS | [0xF027F4A985560fb13324e943edf55ad6F1d15Dc1](https://sepolia.etherscan.io/address/0xF027F4A985560fb13324e943edf55ad6F1d15Dc1) |
+| OptimismMintableERC20Factory | [0xb1efB9650aD6d0CC1ed3Ac4a0B7f1D5732696D37](https://sepolia.etherscan.io/address/0xb1efB9650aD6d0CC1ed3Ac4a0B7f1D5732696D37) |
+| OptimismPortal | [0x49f53e41452C74589E85cA1677426Ba426459e85](https://sepolia.etherscan.io/address/0x49f53e41452C74589E85cA1677426Ba426459e85) |
+| PermissionedDisputeGame | [0xf0102ffe22649a5421d53acc96e309660960cf44](https://sepolia.etherscan.io/address/0xf0102ffe22649a5421d53acc96e309660960cf44) |
+| PreimageOracle | [0x1fb8cdFc6831fc866Ed9C51aF8817Da5c287aDD3](https://sepolia.etherscan.io/address/0x1fb8cdFc6831fc866Ed9C51aF8817Da5c287aDD3) |
+| ProxyAdmin | [0x0389E59Aa0a41E4A413Ae70f0008e76CAA34b1F3](https://sepolia.etherscan.io/address/0x0389E59Aa0a41E4A413Ae70f0008e76CAA34b1F3) |
+| SystemConfig | [0xf272670eb55e895584501d564AfEB048bEd26194](https://sepolia.etherscan.io/address/0xf272670eb55e895584501d564AfEB048bEd26194) |
+
+## Base Admin Addresses
+
+### Base Mainnet
+
+| Admin Role | Address | Type of Key |
+| :------------------------------- | :-------------------------------------------------------------------------------------------------------------------- | :---------------------------------------- |
+| Batch Sender | [0x5050f69a9786f081509234f1a7f4684b5e5b76c9](https://etherscan.io/address/0x5050f69a9786f081509234f1a7f4684b5e5b76c9) | EOA managed by Coinbase Technologies |
+| Batch Inbox | [0xff00000000000000000000000000000000008453](https://etherscan.io/address/0xff00000000000000000000000000000000008453) | EOA (with no known private key) |
+| Output Proposer | [0x642229f238fb9de03374be34b0ed8d9de80752c5](https://etherscan.io/address/0x642229f238fb9de03374be34b0ed8d9de80752c5) | EOA managed by Coinbase Technologies |
+| Proxy Admin Owner (L1) | [0x7bB41C3008B3f03FE483B28b8DB90e19Cf07595c](https://etherscan.io/address/0x7bB41C3008B3f03FE483B28b8DB90e19Cf07595c) | Gnosis Safe |
+| Challenger | [0x8Ca1E12404d16373Aef756179B185F27b2994F3a](https://etherscan.io/address/0x8Ca1E12404d16373Aef756179B185F27b2994F3a) | EOA managed by Coinbase Technologies |
+| System config owner | [0x14536667Cd30e52C0b458BaACcB9faDA7046E056](https://etherscan.io/address/0x14536667Cd30e52C0b458BaACcB9faDA7046E056) | Gnosis Safe |
+| Guardian | [0x09f7150D8c019BeF34450d6920f6B3608ceFdAf2](https://etherscan.io/address/0x09f7150D8c019BeF34450d6920f6B3608ceFdAf2) | Gnosis Safe |
+
+### Base Testnet (Sepolia)
+
+| Admin Role | Address | Type of Key |
+| :--------------------- | :--------------------------------------------------------------------------------------------------------------------------------- | :----------------------------------- |
+| Batch Sender | [0x6CDEbe940BC0F26850285cacA097C11c33103E47](https://sepolia.etherscan.io/address/0x6CDEbe940BC0F26850285cacA097C11c33103E47) | EOA managed by Coinbase Technologies |
+| Batch Inbox | [0xff00000000000000000000000000000000084532](https://sepolia.etherscan.io/address/0xff00000000000000000000000000000000084532) | EOA (with no known private key) |
+| Output Proposer | [0x037637067c1DbE6d2430616d8f54Cb774Daa5999](https://sepolia.etherscan.io/address/0x037637067c1DbE6d2430616d8f54Cb774Daa5999) | EOA managed by Coinbase Technologies |
+| Proxy Admin Owner (L1) | [0x0fe884546476dDd290eC46318785046ef68a0BA9](https://sepolia.etherscan.io/address/0x0fe884546476dDd290eC46318785046ef68a0BA9) | Gnosis Safe |
+| Challenger | [0x8b8c52B04A38f10515C52670fcb23f3C4C44474F](https://sepolia.etherscan.io/address/0x8b8c52B04A38f10515C52670fcb23f3C4C44474F) | EOA managed by Coinbase Technologies |
+| System config owner | [0x0fe884546476dDd290eC46318785046ef68a0BA9](https://sepolia.etherscan.io/address/0x0fe884546476dDd290eC46318785046ef68a0BA9) | Gnosis Safe |
+| Guardian | [0xA9FF930151130fd19DA1F03E5077AFB7C78F8503](https://sepolia.etherscan.io/address/0xA9FF930151130fd19DA1F03E5077AFB7C78F8503) | EOA managed by Coinbase Technologies |
diff --git a/docs/base-chain/network-information/diffs-ethereum-base.mdx b/docs/base-chain/network-information/diffs-ethereum-base.mdx
new file mode 100644
index 00000000..7dd308d1
--- /dev/null
+++ b/docs/base-chain/network-information/diffs-ethereum-base.mdx
@@ -0,0 +1,16 @@
+---
+title: "Differences between Ethereum and Base"
+sidebarTitle: 'Differences: Ethereum & Base'
+---
+
+Base is built on the [Bedrock](https://stack.optimism.io/docs/releases/bedrock/explainer/) release of the [OP Stack](https://stack.optimism.io/), which is designed from the ground up to be as close to Ethereum as possible. Because of this, there are very few differences when it comes to building on Base and Ethereum.
+
+However, there are still some minor discrepancies between the behavior of Base and Ethereum that you should be aware of when building apps on top of Base.
+
+These minor differences include:
+
+- [Opcodes](https://stack.optimism.io/docs/releases/bedrock/differences/#opcode-differences)
+- [Blocks](https://stack.optimism.io/docs/releases/bedrock/differences/#blocks)
+- [Network specifications](https://stack.optimism.io/docs/releases/bedrock/differences/#network-specifications)
+- [Transaction costs](https://stack.optimism.io/docs/releases/bedrock/differences/#transaction-costs)
+
diff --git a/docs/base-chain/network-information/ecosystem-contracts.mdx b/docs/base-chain/network-information/ecosystem-contracts.mdx
new file mode 100644
index 00000000..752e42b0
--- /dev/null
+++ b/docs/base-chain/network-information/ecosystem-contracts.mdx
@@ -0,0 +1,81 @@
+---
+title: 'Ecosystem Contracts'
+---
+
+This page lists contract addresses for onchain apps that we have deployed.
+
+## Base Mainnet
+
+### Multicall3
+
+| Contract | Address |
+| :--------- | :-------------------------------------------------------------------------------------------------------------------- |
+| Multicall3 | [0xcA11bde05977b3631167028862bE2a173976CA11](https://basescan.org/address/0xcA11bde05977b3631167028862bE2a173976CA11) |
+
+### Uniswap v3
+
+| Contract | Address |
+| :----------------------------------- | :-------------------------------------------------------------------------------------------------------------------- |
+| `Permit2` | [0x000000000022D473030F116dDEE9F6B43aC78BA3](https://basescan.org/address/0x000000000022D473030F116dDEE9F6B43aC78BA3) |
+| `universal router` | [0x198EF79F1F515F02dFE9e3115eD9fC07183f02fC](https://basescan.org/address/0x198EF79F1F515F02dFE9e3115eD9fC07183f02fC) |
+| `v3CoreFactory` | [0x33128a8fC17869897dcE68Ed026d694621f6FDfD](https://basescan.org/address/0x33128a8fC17869897dcE68Ed026d694621f6FDfD) |
+| `multicall` | [0x091e99cb1C49331a94dD62755D168E941AbD0693](https://basescan.org/address/0x091e99cb1C49331a94dD62755D168E941AbD0693) |
+| `proxyAdmin` | [0x3334d83e224aF5ef9C2E7DDA7c7C98Efd9621fA9](https://basescan.org/address/0x3334d83e224aF5ef9C2E7DDA7c7C98Efd9621fA9) |
+| `tickLens` | [0x0CdeE061c75D43c82520eD998C23ac2991c9ac6d](https://basescan.org/address/0x0CdeE061c75D43c82520eD998C23ac2991c9ac6d) |
+| `nftDescriptor` | [0xF9d1077fd35670d4ACbD27af82652a8d84577d9F](https://basescan.org/address/0xF9d1077fd35670d4ACbD27af82652a8d84577d9F) |
+| `nonfungibleTokenPositionDescriptor` | [0x4f225937EDc33EFD6109c4ceF7b560B2D6401009](https://basescan.org/address/0x4f225937EDc33EFD6109c4ceF7b560B2D6401009) |
+| `descriptorProxy` | [0x4615C383F85D0a2BbED973d83ccecf5CB7121463](https://basescan.org/address/0x4615C383F85D0a2BbED973d83ccecf5CB7121463) |
+| `nonfungibleTokenPositionManager` | [0x03a520b32C04BF3bEEf7BEb72E919cf822Ed34f1](https://basescan.org/address/0x03a520b32C04BF3bEEf7BEb72E919cf822Ed34f1) |
+| `v3Migrator` | [0x23cF10b1ee3AdfCA73B0eF17C07F7577e7ACd2d7](https://basescan.org/address/0x23cF10b1ee3AdfCA73B0eF17C07F7577e7ACd2d7) |
+| `v3Staker` | [0x42bE4D6527829FeFA1493e1fb9F3676d2425C3C1](https://basescan.org/address/0x42bE4D6527829FeFA1493e1fb9F3676d2425C3C1) |
+| `quoterV2` | [0x3d4e44Eb1374240CE5F1B871ab261CD16335B76a](https://basescan.org/address/0x3d4e44Eb1374240CE5F1B871ab261CD16335B76a) |
+| `swapRouter` | [0x2626664c2603336E57B271c5C0b26F421741e481](https://basescan.org/address/0x2626664c2603336E57B271c5C0b26F421741e481) |
+
+### Uniswap v2
+
+| Contract | Address |
+| :-------- | :-------------------------------------------------------------------------------------------------------------------- |
+| `Factory` | [0x8909Dc15e40173Ff4699343b6eB8132c65e18eC6](https://basescan.org/address/0x8909Dc15e40173Ff4699343b6eB8132c65e18eC6) |
+| `Router` | [0x4752ba5dbc23f44d87826276bf6fd6b1c372ad24](https://basescan.org/address/0x4752ba5dbc23f44d87826276bf6fd6b1c372ad24) |
+
+## Base Testnet (Sepolia)
+
+### Multicall3
+
+| Contract | Address |
+| :--------- | :---------------------------------------------------------------------------------------------------------------------------- |
+| Multicall3 | [0xcA11bde05977b3631167028862bE2a173976CA11](https://sepolia.basescan.org/address/0xcA11bde05977b3631167028862bE2a173976CA11) |
+
+### Uniswap v3
+
+| Contract | Address |
+| :----------------------------------- | :---------------------------------------------------------------------------------------------------------------------------- |
+| `Permit2` | [0x000000000022d473030f116ddee9f6b43ac78ba3](https://sepolia.basescan.org/address/0x000000000022d473030f116ddee9f6b43ac78ba3) |
+| `universal router` | [0x050E797f3625EC8785265e1d9BDd4799b97528A1](https://sepolia.basescan.org/address/0x050E797f3625EC8785265e1d9BDd4799b97528A1) |
+| `v3CoreFactory` | [0x4752ba5DBc23f44D87826276BF6Fd6b1C372aD24](https://sepolia.basescan.org/address/0x4752ba5DBc23f44D87826276BF6Fd6b1C372aD24) |
+| `multicall` | [0xd867e273eAbD6c853fCd0Ca0bFB6a3aE6491d2C1](https://sepolia.basescan.org/address/0xd867e273eAbD6c853fCd0Ca0bFB6a3aE6491d2C1) |
+| `proxyAdmin` | [0xD7303474Baca835743B54D73799688990f24a79D](https://sepolia.basescan.org/address/0xD7303474Baca835743B54D73799688990f24a79D) |
+| `tickLens` | [0xedf6066a2b290C185783862C7F4776A2C8077AD1](https://sepolia.basescan.org/address/0xedf6066a2b290C185783862C7F4776A2C8077AD1) |
+| `nftDescriptor` | [0x4e0caFF1Df1cCd7CF782FDdeD77f020699B57f1a](https://sepolia.basescan.org/address/0x4e0caFF1Df1cCd7CF782FDdeD77f020699B57f1a) |
+| `nonfungibleTokenPositionDescriptor` | [0xd7c6e867591608D32Fe476d0DbDc95d0cf584c8F](https://sepolia.basescan.org/address/0xd7c6e867591608D32Fe476d0DbDc95d0cf584c8F) |
+| `nonfungibleTokenPositionManager` | [0x27F971cb582BF9E50F397e4d29a5C7A34f11faA2](https://sepolia.basescan.org/address/0x27F971cb582BF9E50F397e4d29a5C7A34f11faA2) |
+| `v3Migrator` | [0xCbf8b7f80800bd4888Fbc7bf1713B80FE4E23E10](https://sepolia.basescan.org/address/0xCbf8b7f80800bd4888Fbc7bf1713B80FE4E23E10) |
+| `v3Staker` | [0x62725F55f50bdE240aCa3e740D47298CAc8d57D5](https://sepolia.basescan.org/address/0x62725F55f50bdE240aCa3e740D47298CAc8d57D5) |
+| `quoterV2` | [0xC5290058841028F1614F3A6F0F5816cAd0df5E27](https://sepolia.basescan.org/address/0xC5290058841028F1614F3A6F0F5816cAd0df5E27) |
+| `swapRouter` | [0x94cC0AaC535CCDB3C01d6787D6413C739ae12bc4](https://sepolia.basescan.org/address/0x94cC0AaC535CCDB3C01d6787D6413C739ae12bc4) |
+
+#### Testnet interfaces
+
+:::info
+
+Two community projects, [BaseX](https://basex-test.vercel.app/swap?currencyA=ETH¤cyB=0x036CbD53842c5426634e7929541eC2318f3dCF7e&focus=source) and [DapDap](https://testnet.base.dapdap.net/uniswap/swap), provide testnet interfaces for Uniswap contracts if you prefer to interact in the browser instead of with the contracts directly.
+
+:::
+
+### Uniswap v2
+
+| Contract | Address |
+| :-------- | :---------------------------------------------------------------------------------------------------------------------------- |
+| `Factory` | [0x7Ae58f10f7849cA6F5fB71b7f45CB416c9204b1e](https://sepolia.basescan.org/address/0x7Ae58f10f7849cA6F5fB71b7f45CB416c9204b1e) |
+| `Router` | [0x1689E7B1F10000AE47eBfE339a4f69dECd19F602](https://sepolia.basescan.org/address/0x1689E7B1F10000AE47eBfE339a4f69dECd19F602) |
+
diff --git a/docs/base-chain/network-information/network-fees.mdx b/docs/base-chain/network-information/network-fees.mdx
new file mode 100644
index 00000000..f735b60d
--- /dev/null
+++ b/docs/base-chain/network-information/network-fees.mdx
@@ -0,0 +1,28 @@
+---
+title: Network Fees
+description: Documentation about network fees on Base. This page covers details of the two-component cost system involving L2 execution fees and L1 security fees, and offers insights on fee variations and cost-saving strategies.
+---
+
+# Fees
+
+## How do network fees on Base work?
+
+Every Base transaction consists of two costs: an L2 (execution) fee and an L1
+(security) fee. The L2 fee is the cost to execute your transaction on the L2,
+and the L1 fee is the estimated cost to publish the transaction on the L1.
+Typically the L1 security fee is higher than the L2 execution fee.
+
+The L1 fee will vary depending on the amount of transactions on the L1. If the
+timing of your transaction is flexible, you can save costs by submitting
+transactions during periods of lower gas on the L1 (for example, over the
+weekend)
+
+Similarly, the L2 fee can increase and decrease depending on how many
+transactions are being submitted to the L2. This adjustment mechanism has the
+same implementation as the L1; you can read more about it
+[here](https://help.coinbase.com/en/coinbase/getting-started/crypto-education/eip-1559).
+
+For additional details about fee calculation on Base, please refer to the
+[op-stack developer
+documentation](https://docs.optimism.io/stack/transactions/fees).
+
diff --git a/docs/base-chain/node-operators/performance-tuning.mdx b/docs/base-chain/node-operators/performance-tuning.mdx
new file mode 100644
index 00000000..3bb251e4
--- /dev/null
+++ b/docs/base-chain/node-operators/performance-tuning.mdx
@@ -0,0 +1,103 @@
+---
+title: Node Performance
+sidebarTitle: Performance Tuning
+---
+
+This guide provides recommendations for hardware, client software, and configuration settings to optimize the performance of your Base node.
+
+## Hardware
+
+Running a performant Base node requires adequate hardware. We recommend the following minimum specifications:
+
+1. A modern multi-core CPU with good single-core performance.
+2. At least 32 GB RAM (64 GB recommended).
+3. A locally attached NVMe SSD drive. RAID 0 configurations can improve performance.
+4. Sufficient storage capacity calculated as:
+
+ ```
+ (2 \* [current chain size](https://base.org/stats) + [snapshot size](https://basechaindata.vercel.app) + 20% buffer)
+ ```
+
+ This accounts for chain data growth and snapshot restoration space.
+
+
+If utilizing Amazon Elastic Block Store (EBS), io2 Block Express volumes are recommended to ensure sufficient disk read speeds, preventing latency issues during initial sync. However, **locally attached NVMe SSDs are strongly recommended over networked storage for optimal performance.**
+
+
+### Production Hardware Examples
+
+The following are the hardware specifications used for Base production nodes:
+
+- **Geth Full Node:**
+ - Instance: AWS `i4i.12xlarge`
+ - Storage: RAID 0 of all local NVMe drives (`/dev/nvme*`)
+ - Filesystem: ext4
+
+- **Reth Archive Node:**
+ - Instance: AWS `i4ie.6xlarge`
+ - Storage: RAID 0 of all local NVMe drives (`/dev/nvme*`)
+ - Filesystem: ext4
+
+## Initial Sync
+
+Using a recent [snapshot](/base-chain/node-operators/snapshots.mdx) can significantly reduce the time required for the initial node synchronization process.
+
+## Client Software
+
+The [Base Node](https://github.com/base/node) repository contains the current stable configurations and instructions for running different client implementations.
+
+### Supported Clients
+
+Reth is currently the most performant client for running Base nodes. Future optimizations will primarily focus on Reth. You can read more about the migration to Reth [here](https://blog.base.dev/scaling-base-with-reth).
+
+| Type | Supported Clients |
+| ------- | -------------------------------------------------------------------------------------------------- |
+| Full | [Reth](https://github.com/base/node/tree/main/reth), [Geth](https://github.com/base/node/tree/main/geth) |
+| Archive | [Reth](https://github.com/base/node/tree/main/reth) |
+
+### Geth Performance Tuning
+
+#### Geth Cache Settings
+
+For Geth nodes, tuning cache allocation via environment variables can improve performance. These settings are used in the standard Docker configuration:
+
+```bash
+# .env.mainnet / .env.sepolia
+GETH_CACHE="20480" # Total P2P cache memory allowance (MB) (default: 1024)
+GETH_CACHE_DATABASE="20" # Percentage of cache memory allowance for database IO (default: 75)
+GETH_CACHE_GC="12" # Percentage of cache memory allowance for garbage collection (default: 25)
+GETH_CACHE_SNAPSHOT="24" # Percentage of cache memory allowance for snapshot caching (default: 10)
+GETH_CACHE_TRIE="44" # Percentage of cache memory allowance for trie caching (default: 25)
+```
+
+#### Geth LevelDB Tuning
+
+For teams running Geth with LevelDB, the following patch allows setting LevelDB initialization parameters via environment variables:
+
+[https://github.com/0x00101010/goleveldb/commit/55ef3429673fb70d389d052a15a4423e13d8b43c](https://github.com/0x00101010/goleveldb/commit/55ef3429673fb70d389d052a15a4423e13d8b43c)
+
+This patch can be applied using a `replace` directive in `go.mod` when building `op-geth`. Here’s how to modify your Dockerfile:
+
+```dockerfile
+RUN git clone $REPO --branch $VERSION --single-branch . && \
+ git switch -c branch-$VERSION $COMMIT && \
+ bash -c '[ "$(git rev-parse HEAD)" = "$COMMIT" ]'
+
+RUN echo '' >> go.mod && \
+ echo 'replace github.com/syndtr/goleveldb => github.com/0x00101010/goleveldb v1.0.4-param-customization' >> go.mod && \
+ go mod tidy
+
+# Continue building op-geth
+COPY op-geth/ ./
+RUN go run build/ci.go install -static ./cmd/geth
+```
+
+Recommended LevelDB environment variable values with this patch:
+
+```bash
+# Recommended LevelDB Settings
+LDB_BLOCK_SIZE="524288" # 512 KiB block size (matches common RAID 0 chunk sizes)
+LDB_COMPACTION_TABLE_SIZE="8388608" # 8 MiB compaction table size (default: 2 MiB)
+LDB_COMPACTION_TOTAL_SIZE="41943040" # 40 MiB total compaction size (default: 8 MiB)
+LDB_DEBUG_OPTIONS="1" # Emit LevelDB debug logs
+```
diff --git a/docs/base-chain/node-operators/run-a-base-node.mdx b/docs/base-chain/node-operators/run-a-base-node.mdx
new file mode 100644
index 00000000..1f7d9bfe
--- /dev/null
+++ b/docs/base-chain/node-operators/run-a-base-node.mdx
@@ -0,0 +1,113 @@
+---
+title: 'Getting Started'
+description: A tutorial that teaches how to set up and run a Base Node.
+---
+
+This tutorial will walk you through setting up your own [Base Node](https://github.com/base-org/node).
+
+## Objectives
+
+By the end of this tutorial you should be able to:
+
+- Deploy and sync a Base node
+
+## Prerequisites
+
+
+Running a node is time consuming, resource expensive, and potentially costly. If you don't already know why you want to run your own node, you probably don't need to.
+
+If you're just getting started and need an RPC URL, you can use our free endpoints:
+
+- **Mainnet**: `https://mainnet.base.org`
+- **Testnet (Sepolia)**: `https://sepolia.base.org`
+
+**Note:** Our RPCs are rate-limited, they are not suitable for production apps.
+
+If you're looking to harden your app and avoid rate-limiting for your users, please check out one of our [partners](/base-chain/tools/node-providers).
+
+
+
+### Hardware requirements
+
+We recommend you have this configuration to run a node:
+
+- 8-Core CPU
+- at least 16 GB RAM
+- a locally attached NVMe SSD drive
+- adequate storage capacity to accommodate both the snapshot restoration process (if restoring from snapshot) and chain data, ensuring a minimum of (2 \* current_chain_size) + snapshot_size + 20%\_buffer
+
+
+If utilizing Amazon Elastic Block Store (EBS), ensure timing buffered disk reads are fast enough in order to avoid latency issues alongside the rate of new blocks added to Base during the initial synchronization process; `io2 block express` is recommended.
+
+
+
+### Docker
+
+This tutorial assumes you are familiar with [Docker](https://www.docker.com/) and have it running on your machine.
+
+### L1 RPC URL
+
+You'll need your own L1 RPC URL. This can be one that you run yourself, or via a third-party provider, such as our [partners].
+
+## Running a Node
+
+1. Clone the [repo](https://github.com/base-org/node).
+2. Ensure you have an Ethereum L1 full node RPC available (not Base), and set `OP_NODE_L1_ETH_RPC` & `OP_NODE_L1_BEACON` (in the `.env.*` file if using `docker-compose`). If running your own L1 node, it needs to be synced before Base will be able to fully sync.
+3. Uncomment the line relevant to your network (`.env.sepolia`, or `.env.mainnet`) under the 2 `env_file` keys in `docker-compose.yml`.
+4. Run `docker compose up`. Confirm you get a response from:
+
+```bash [Terminal]
+curl -d '{"id":0,"jsonrpc":"2.0","method":"eth_getBlockByNumber","params":["latest",false]}' \
+ -H "Content-Type: application/json" http://localhost:8545
+```
+
+
+Syncing your node may take **days** and will consume a vast amount of your requests quota. Be sure to monitor usage and up your plan if needed.
+
+
+
+### Snapshots
+
+
+Geth Archive Nodes are no longer supported. For Archive functionality, use Reth, which provides significantly better performance in Base’s high-throughput environment.
+
+
+
+If you're a prospective or current Base Node operator and would like to restore from a snapshot to save time on the initial sync, it's possible to always get the latest available snapshot of the Base chain on mainnet and/or testnet by using the following CLI commands. The snapshots are updated every week.
+
+#### Restoring from snapshot
+
+In the home directory of your Base Node, create a folder named `geth-data` or `reth-data`. If you already have this folder, remove it to clear the existing state and then recreate it. Next, run the following code and wait for the operation to complete.
+
+| Network | Client | Snapshot Type | Command |
+| ------- | ------ | ------------- | --------------------------------------------------------------------------------------------------------------------- |
+| Testnet | Geth | Full | `wget https://sepolia-full-snapshots.base.org/$(curl https://sepolia-full-snapshots.base.org/latest)` |
+| Testnet | Reth | Archive | `wget https://sepolia-reth-archive-snapshots.base.org/$(curl https://sepolia-reth-archive-snapshots.base.org/latest)` |
+| Mainnet | Geth | Full | `wget https://mainnet-full-snapshots.base.org/$(curl https://mainnet-full-snapshots.base.org/latest)` |
+| Mainnet | Reth | Archive | `wget https://mainnet-reth-archive-snapshots.base.org/$(curl https://mainnet-reth-archive-snapshots.base.org/latest)` |
+
+You'll then need to untar the downloaded snapshot and place the `geth` subfolder inside of it in the `geth-data` folder you created (unless you changed the location of your data directory).
+
+Return to the root of your Base node folder and start your node.
+
+```bash [Terminal]
+cd ..
+docker compose up --build
+```
+
+Your node should begin syncing from the last block in the snapshot.
+
+Check the latest block to make sure you're syncing from the snapshot and that it restored correctly. If so, you can remove the snapshot archive that you downloaded.
+
+### Syncing
+
+You can monitor the progress of your sync with:
+
+```bash [Terminal]
+echo Latest synced block behind by: $((($(date +%s)-$( \
+ curl -d '{"id":0,"jsonrpc":"2.0","method":"optimism_syncStatus"}' \
+ -H "Content-Type: application/json" http://localhost:7545 | \
+ jq -r .result.unsafe_l2.timestamp))/60)) minutes
+```
+
+You'll also know that the sync hasn't completed if you get `Error: nonce has already been used` if you try to deploy using your node.
diff --git a/docs/base-chain/node-operators/snapshots.mdx b/docs/base-chain/node-operators/snapshots.mdx
new file mode 100644
index 00000000..c172c10a
--- /dev/null
+++ b/docs/base-chain/node-operators/snapshots.mdx
@@ -0,0 +1,78 @@
+---
+title: Node Snapshots
+sidebarTitle: Snapshots
+---
+
+Using a snapshot significantly reduces the initial time required to sync a Base node. Snapshots are updated regularly.
+
+
+Geth Archive Nodes are no longer supported via snapshots due to performance limitations. For Archive functionality, please use Reth.
+
+
+If you're a prospective or current Base node operator, you can restore from a snapshot to speed up your initial sync. Follow the steps below carefully.
+
+## Restoring from Snapshot
+
+These steps assume you are in the cloned `node` directory (the one containing `docker-compose.yml`).
+
+1. **Prepare Data Directory**:
+ - **Before running Docker for the first time**, create the data directory on your host machine that will be mapped into the Docker container. This directory must match the `volumes` mapping in the `docker-compose.yml` file for the client you intend to use.
+ - For Geth:
+ ```bash
+ mkdir ./geth-data
+ ```
+ - For Reth:
+ ```bash
+ mkdir ./reth-data
+ ```
+ - If you have previously run the node and have an existing data directory, **stop the node** (`docker compose down`), remove the _contents_ of the existing directory (e.g. `rm -rf ./geth-data/*`), and proceed.
+
+2. **Download Snapshot**: Choose the appropriate snapshot for your network and client from the table below. Use `wget` (or similar) to download it into the `node` directory.
+
+ | Network | Client | Snapshot Type | Download Command (`wget …`) |
+ | -------- | ------ | ------------- | ----------------------------------------------------------------------------------------------------------------- |
+ | Testnet | Geth | Full | `wget https://sepolia-full-snapshots.base.org/$(curl https://sepolia-full-snapshots.base.org/latest)` |
+ | Testnet | Reth | Archive | `wget https://sepolia-reth-archive-snapshots.base.org/$(curl https://sepolia-reth-archive-snapshots.base.org/latest)` |
+ | Mainnet | Geth | Full | `wget https://mainnet-full-snapshots.base.org/$(curl https://mainnet-full-snapshots.base.org/latest)` |
+ | Mainnet | Reth | Archive | `wget https://mainnet-reth-archive-snapshots.base.org/$(curl https://mainnet-reth-archive-snapshots.base.org/latest)` |
+
+
+ Ensure you have enough free disk space to download the snapshot archive (`.tar.gz` file) _and_ extract its contents. The extracted data will be significantly larger than the archive.
+
+
+3. **Extract Snapshot**: Untar the downloaded snapshot archive. Replace `` with the actual downloaded filename:
+
+ ```bash
+ tar -xzvf
+ ```
+
+4. **Move Data**: The extraction process will likely create a directory (e.g., `geth` or `reth`).
+
+ * Move the *contents* of that directory into the data directory you created in Step 1.
+
+ * Example (if archive extracted to a geth folder):
+
+ ```bash
+ # For Geth
+ mv ./geth/* ./geth-data/
+ rm -rf ./geth # Clean up empty extracted folder
+ ```
+
+ * Example (if archive extracted to a reth folder - **verify actual folder name**):
+
+ ```bash
+ # For Reth
+ mv ./reth/* ./reth-data/
+ rm -rf ./reth # Clean up empty extracted folder
+ ```
+
+ * The goal is to have the chain data directories (e.g., `chaindata`, `nodes`, `segments`, etc.) directly inside `./geth-data` or `./reth-data`, not nested within another subfolder.
+
+5. **Start the Node**: Now that the snapshot data is in place, start the node using the appropriate command (see the [Running a Base Node](/base-chain/quickstart/run-base-node#setting-up-and-running-the-node) guide):
+
+ ```bash
+ # Example for Mainnet Geth
+ docker compose up --build -d
+ ```
+
+6. **Verify and Clean Up**: Monitor the node logs (`docker compose logs -f `) or use the [sync monitoring](/base-chain/quickstart/run-base-node#monitoring-sync-progress) command to ensure the node starts syncing from the snapshot's block height. Once confirmed, you can safely delete the downloaded snapshot archive (`.tar.gz` file) to free up disk space.
diff --git a/docs/base-chain/node-operators/troubleshooting.mdx b/docs/base-chain/node-operators/troubleshooting.mdx
new file mode 100644
index 00000000..dfd59c32
--- /dev/null
+++ b/docs/base-chain/node-operators/troubleshooting.mdx
@@ -0,0 +1,130 @@
+---
+sidebarTitle: Troubleshooting
+title: Node Troubleshooting
+---
+
+This guide covers common issues encountered when setting up and running a Base node using the official [Base Node Docker setup](https://github.com/base/node) and provides steps to diagnose and resolve them.
+
+## General Troubleshooting Steps
+
+Before diving into specific issues, here are some general steps that often help:
+
+1. **Check Container Logs**: This is usually the most informative step. Use `docker compose logs -f ` to view the real-time logs for a specific container.
+ - L2 Client (Geth): `docker compose logs -f op-geth`
+ - L2 Client (Reth): `docker compose logs -f op-reth`
+ - Rollup Node: `docker compose logs -f op-node`. Look for errors, warnings, or repeated messages.
+
+2. **Check Container Status**: Ensure the relevant Docker containers are running: `docker compose ps`. If a container is restarting frequently or exited, check its logs.
+
+3. **Check Resource Usage**: Monitor your server’s CPU, RAM, disk I/O, and network usage. Performance issues are often linked to insufficient resources. Tools like `htop`, `iostat`, and `iftop` can be helpful.
+
+4. **Verify RPC Endpoints**: Use `curl` to check if the L2 client’s RPC endpoint is responding (see [Running a Base Node > Verify Node is Running](/base-chain/quickstart/run-base-node.mdx#verify-node-is-running)). Also, verify your L1 endpoints are correct and accessible from the node server.
+
+5. **Check L1 Node**: Ensure your configured L1 node (Execution and Consensus) is fully synced, healthy, and accessible. Issues with the L1 node will prevent the L2 node from syncing correctly.
+
+---
+
+## Common Issues and Solutions
+
+### Setup & Configuration Issues
+
+- **Issue**: Docker command fails (`docker compose up ...`)
+ - **Check**: Is Docker and Docker Compose installed and the Docker daemon running?
+ - **Check**: Are you in the correct directory (the cloned `node` directory containing `docker-compose.yml`)?
+ - **Check**: Syntax errors in the command (e.g., misspelled `NETWORK_ENV` or `CLIENT`).
+
+- **Issue**: Container fails to start, logs show errors related to `.env` files or environment variables.
+ - **Check**: Did you correctly configure the L1 endpoints (`OP_NODE_L1_ETH_RPC`, `OP_NODE_L1_BEACON`) in the correct `.env` file (`.env.mainnet` or `.env.sepolia`)?
+ - **Check**: Is the `OP_NODE_L1_BEACON_ARCHIVER` endpoint set if required by your configuration or L1 node?
+ - **Check**: Is `OP_NODE_L1_RPC_KIND` set correctly for your L1 provider?
+ - **Check**: (Reth) Are `RETH_CHAIN` and `RETH_SEQUENCER_HTTP` correctly set in the `.env` file?
+
+- **Issue**: Errors related to JWT secret or authentication between `op-node` and L2 client.
+ - **Check**: Ensure you haven't manually modified the `OP_NODE_L2_ENGINE_AUTH` variable or the JWT file path (`$OP_NODE_L2_ENGINE_AUTH`) unless you know what you're doing. The `docker-compose` setup usually handles this automatically.
+
+- **Issue**: Permission errors related to data volumes (`./geth-data`, `./reth-data`).
+ - **Check**: Ensure the user running `docker compose` has write permissions to the directory where the `node` repository was cloned. Docker needs to be able to write to `./geth-data` or `./reth-data`. Sometimes running Docker commands with `sudo` can cause permission issues later; try running as a non-root user added to the `docker` group.
+
+### Syncing Problems
+
+- **Issue**: Node doesn't start syncing or appears stuck (block height not increasing).
+ - **Check**: `op-node` logs. Look for errors connecting to L1 endpoints or the L2 client.
+ - **Check**: L2 client (`op-geth`/`op-reth`) logs. Look for errors connecting to `op-node` via the Engine API (port `8551`) or P2P issues.
+ - **Check**: L1 node health and sync status. Is the L1 node accessible and fully synced?
+ - **Check**: System time. Ensure the server’s clock is accurately synchronized (use `ntp` or `chrony`). Significant time drift can cause P2P issues.
+
+- **Issue**: Syncing is extremely slow.
+ - **Check**: Hardware specifications. Are you meeting the recommended specs (especially RAM and **NVMe SSD**) outlined in the [Node Performance](/base-chain/node-operators/performance-tuning) guide? Disk I/O is often the bottleneck.
+ - **Check**: L1 node performance. Is your L1 RPC endpoint responsive? A slow L1 node will slow down L2 sync.
+ - **Check**: Network connection quality and bandwidth.
+ - **Check**: `op-node` and L2 client logs for any performance warnings or errors.
+
+- **Issue**: `optimism_syncStatus` (port `7545` on `op-node`) shows a large time difference or errors.
+ - **Action**: Check the logs for both `op-node` and the L2 client (`op-geth`/`op-reth`) around the time the status was checked to identify the root cause (e.g., L1 connection issues, L2 client issues).
+
+- **Issue**: `Error: nonce has already been used` when trying to send transactions.
+ - **Cause**: The node is not yet fully synced to the head of the chain.
+ - **Action**: Wait for the node to fully sync. Monitor progress using `optimism_syncStatus` or logs.
+
+### Performance Issues
+
+- **Issue**: High CPU, RAM, or Disk I/O usage.
+ - **Check**: Hardware specifications against recommendations in the [Node Performance](/base-chain/node-operators/performance-tuning). Upgrade if necessary. Local NVMe SSDs are critical.
+ - **Check**: (Geth) Review Geth cache settings and LevelDB tuning options mentioned in [Node Performance – Geth Performance Tuning](/base-chain/node-operators/performance-tuning#geth-performance-tuning) and [Advanced Configuration](/base-chain/quickstart/run-base-node#geth-configuration-via-environment-variables).
+ - **Check**: Review client logs for specific errors or bottlenecks.
+ - **Action**: Consider using Reth if running Geth, as it’s generally more performant for Base.
+
+### Snapshot Restoration Problems
+
+Refer to the [Snapshots](/base-chain/node-operators/snapshots) guide for the correct procedure.
+
+- **Issue**: `wget` command fails or snapshot download is corrupted.
+ - **Check**: Network connectivity.
+ - **Check**: Available disk space.
+ - **Action**: Retry the download. Verify the download URL is correct.
+
+- **Issue**: `tar` extraction fails.
+ - **Check**: Downloaded file integrity (is it corrupted?).
+ - **Check**: Available disk space (extraction requires much more space than the download).
+ - **Check**: `tar` command syntax.
+
+- **Issue**: Node fails to start after restoring snapshot; logs show database errors or missing files.
+ - **Check**: Did you stop the node (`docker compose down`) _before_ modifying the data directory?
+ - **Check**: Did you remove the _contents_ of the old data directory (`./geth-data/*` or `./reth-data/*`) before extracting/moving the snapshot data?
+ - **Check**: Was the snapshot data moved correctly? The chain data needs to be directly inside `./geth-data` or `./reth-data`, not in a nested subfolder (e.g., `./geth-data/geth/...`). Verify the folder structure.
+
+- **Issue**: Ran out of disk space during download or extraction.
+ - **Action**: Free up disk space or provision a larger volume. Remember the storage formula:
+ ```
+ (2 * chain_size + snapshot_size + 20% buffer)
+ ```
+
+### Networking / Connectivity Issues
+
+- **Issue**: RPC/WS connection refused (e.g., `curl` to `localhost:8545` fails).
+ - **Check**: Is the L2 client container (`op-geth`/`op-reth`) running (`docker compose ps`)?
+ - **Check**: Are you using the correct port (`8545` for HTTP, `8546` for WS by default)?
+ - **Check**: L2 client logs. Did it fail to start the RPC server?
+ - **Check**: Are the `--http.addr` and `--ws.addr` flags set to `0.0.0.0` in the client config/entrypoint to allow external connections (within the Docker network)?
+
+- **Issue**: Node has low peer count.
+ - **Check**: P2P port (default `30303`) accessibility. Is it blocked by a firewall on the host or network?
+ - **Check**: Node logs for P2P errors.
+ - **Action**: If behind NAT, configure the `--nat=extip:` flag via `ADDITIONAL_ARGS` in the `.env` file (see [Advanced Configuration](/base-chain/quickstart/run-base-node#improving-peer-connectivity)).
+
+- **Issue**: Port conflicts reported in logs or `docker compose up` fails.
+ - **Check**: Are other services running on the host using the default ports (`8545`, `8546`, `8551`, `6060`, `7545`, `30303`)? Use
+ ```bash
+ sudo lsof -i -P -n | grep LISTEN
+ sudo netstat -tulpn | grep LISTEN
+ ```
+ - **Action**: Stop the conflicting service or change the ports used by the Base node containers by modifying the `ports` section in `docker-compose.yml` and updating the relevant environment variables (`$RPC_PORT`, `$WS_PORT`, etc.) in the `.env` file if necessary.
+
+---
+
+## Getting Further Help
+
+If you’ve followed this guide and are still encountering issues, seek help from the community:
+
+- **Discord**: Join the [Base Discord](https://discord.gg/buildonbase) and post in the `🛠｜node-operators` channel, providing details about your setup, the issue, and relevant logs.
+- **GitHub**: Check the [Base Node repository issues](https://github.com/base-org/node/issues) or open a new one if you suspect a bug.
diff --git a/docs/base-chain/quickstart/bridge-token.mdx b/docs/base-chain/quickstart/bridge-token.mdx
new file mode 100644
index 00000000..60b5d27c
--- /dev/null
+++ b/docs/base-chain/quickstart/bridge-token.mdx
@@ -0,0 +1,27 @@
+---
+title: "Bridging an L1 token to Base"
+sidebarTitle: 'Bridge Tokens to Base'
+description: How to submit ERC-20 tokens for bridging between Ethereum and Base as a token issuer.
+---
+
+This page is intended for token issuers who already have an ERC-20 contract deployed on Ethereum and would like to submit their token for bridging between Ethereum and Base. Base uses the [Superchain token list](https://github.com/ethereum-optimism/ethereum-optimism.github.io) as a reference for tokens that have been deployed on Base.
+
+**_Disclaimer: Base does not endorse any of the tokens that are listed in the Github repository and has conducted only preliminary checks, which include automated checks listed_** [**_here_**](https://github.com/ethereum-optimism/ethereum-optimism.github.io)**_._**
+
+## Adding your token to the list
+
+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/protocol/bridges.md) contracts, and furthermore deploy your token using the [OptimismMintableERC20Factory](https://docs.optimism.io/app-developers/tutorials/bridging/standard-bridge-standard-token). You can find the list of contracts addresses [here](/base-chain/network-information/base-contracts).
+
+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 Superchain 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
+
+Reviews are regularly conducted by the Base team and you should receive a reply within 24-72 hours (depending on if the PR is opened on a weekday, weekend or holiday).
diff --git a/docs/base-chain/quickstart/connecting-to-base.mdx b/docs/base-chain/quickstart/connecting-to-base.mdx
new file mode 100644
index 00000000..304e186a
--- /dev/null
+++ b/docs/base-chain/quickstart/connecting-to-base.mdx
@@ -0,0 +1,35 @@
+---
+title: 'Connecting to Base'
+description: Documentation about Base Mainnet and Base Testnet. This page covers network information for the Base network, including network names, descriptions, RPC endpoints, chain IDs, currency symbols, and block explorers.
+---
+
+## Base Mainnet
+
+| Name | Value |
+| :-------------- | :------------------------------------------------------------------------------------------------------ |
+| Network Name | Base Mainnet |
+| Description | The public mainnet for Base. |
+| RPC Endpoint | [https://mainnet.base.org](https://mainnet.base.org)
_Rate limited and not for production systems._ | +| Chain ID | 8453 | +| Currency Symbol | ETH | +| Block Explorer | [https://base.blockscout.com/](https://base.blockscout.com/) | + +## Base Testnet (Sepolia) + +| Name | Value | +| :-------------- | :------------------------------------------------------------------------------------------------------ | +| Network Name | Base Sepolia | +| Description | A public testnet for Base. | +| RPC Endpoint | [https://sepolia.base.org](https://sepolia.base.org)
_Rate limited and not for production systems._ | +| Chain ID | 84532 | +| Currency Symbol | ETH | +| Block Explorer | [https://sepolia-explorer.base.org](https://sepolia-explorer.base.org) | + +
+L1 & L2 protocol and network-related smart contract deployments can be found on the [Base Contracts](/base-chain/network-information/base-contracts) page.
+
+
+
+
+For production systems, we recommend using a node from one of our [node partners](/base-chain/tools/node-providers), or [running your own Base node](/base-chain/quickstart/run-base-node).
+
diff --git a/docs/base-chain/quickstart/deploy-on-base.mdx b/docs/base-chain/quickstart/deploy-on-base.mdx
new file mode 100644
index 00000000..7c525e78
--- /dev/null
+++ b/docs/base-chain/quickstart/deploy-on-base.mdx
@@ -0,0 +1,143 @@
+---
+title: 'Deploy on Base'
+---
+
+Welcome to the Base deployment quickstart guide! This comprehensive walkthrough will help you set up your environment and deploy smart contracts on Base. Whether you're a seasoned developer or just starting out, this guide has got you covered.
+
+## What You'll Achieve
+
+By the end of this quickstart, you'll be able to:
+
+- Set up your development environment to deploy on Base
+- Deploy your smart contracts to Base
+- Connect your frontend to your smart contracts
+
+
+**Why Base?**
+
+Base is a fast, low-cost, builder-friendly Ethereum L2 built to bring the next billion users onchain. By following this guide, you'll join a vibrant ecosystem of developers, creators, and innovators who are building a global onchain economy.
+
+
+
+## Set Up Your Development Environment
+
+1. Create a new project directory
+
+```bash
+mkdir my-base-project && cd my-base-project
+```
+
+2. Install Foundry, a powerful framework for smart contract development
+
+```bash
+curl -L https://foundry.paradigm.xyz | bash
+foundryup
+```
+
+This installs Foundry and updates it to the latest version.
+
+3. Initialize a new Solidity project
+
+```bash
+forge init
+```
+
+Your Foundry project is now ready. You'll find an example contract in the `src` directory, which you can replace with your own contracts. For the purposes of this guide, we'll use the Counter contract provided in `/src/Counter.sol`
+
+
+Foundry provides a suite of tools for Ethereum application development, including Forge (for testing), Cast (for interacting with the chain), and Anvil (for setting up a local node). You can learn more about Foundry [here](https://book.getfoundry.sh/).
+
+
+
+## Configure Foundry with Base
+
+To deploy your smart contracts to Base, you need two key components:
+
+1. A node connection to interact with the Base network
+2. A funded private key to deploy the contract
+
+Let's set up both of these:
+
+### 1. Set up your node connection
+
+1. Create a `.env` file in your project's root directory
+2. Add the Base network RPC URL to your `.env` file
+
+```bash
+BASE_RPC_URL="https://mainnet.base.org"
+BASE_SEPOLIA_RPC_URL="https://sepolia.base.org"
+```
+
+3. Load your environment variables
+
+```bash
+source .env
+```
+
+
+Base Sepolia is the test network for Base, which we will use for the rest of this guide. You can obtain free Base Sepolia ETH from one of the [faucets listed here](/base-chain/tools/network-faucets).
+
+
+
+### 2. Secure your private key
+
+1. Store your private key in Foundry's secure keystore
+
+```bash
+cast wallet import deployer --interactive
+```
+
+2. When prompted enter your private key and a password.
+
+Your private key is stored in `~/.foundry/keystores` which is not tracked by git.
+
+
+Never share or commit your private key. Always keep it secure and handle with care.
+
+
+
+## Deploy Your Contracts
+
+Now that your environment is set up, let's deploy your contracts to Base Sepolia.
+
+1. Use the following command to compile and deploy your contract
+
+```bash
+forge create ./src/Counter.sol:Counter --rpc-url $BASE_SEPOLIA_RPC_URL --account deployer
+```
+
+Note the format of the contract being deployed is `:`.
+
+2. After successful deployment, the transaction hash will be printed to the console output
+
+3. Copy the deployed contract address and add it to your `.env` file
+
+```bash
+COUNTER_CONTRACT_ADDRESS="0x..."
+```
+
+4. Load the new environment variable
+
+```bash
+source .env
+```
+
+### Verify Your Deployment
+
+To ensure your contract was deployed successfully:
+
+1. Check the transaction on [Sepolia Basescan](https://sepolia.basescan.org/).
+2. Use the `cast` command to interact with your deployed contract from the command line
+
+```bash
+cast call $COUNTER_CONTRACT_ADDRESS "number()(uint256)" --rpc-url $BASE_SEPOLIA_RPC_URL
+```
+This will return the initial value of the Counter contract's `number` storage variable, which will be `0`.
+
+**Congratulations! You've deployed your smart contracts to Base Sepolia!**
+
+## Next Steps
+
+- Use [Onchainkit](https://onchainkit.com) to connect your frontend to your contracts! Onchainkit is a library of ready-to-use React components and Typescript utilities.
+- Learn more about interacting with your contracts in the command line using Foundry from our [Foundry tutorial](/cookbook/smart-contract-development/foundry/deploy-with-foundry).
+
diff --git a/docs/base-chain/quickstart/why-base.mdx b/docs/base-chain/quickstart/why-base.mdx
new file mode 100644
index 00000000..47867775
--- /dev/null
+++ b/docs/base-chain/quickstart/why-base.mdx
@@ -0,0 +1,79 @@
+---
+title: 'Why Base?'
+---
+
+## TL;DR
+
+- **Cheap, fast, and open platform:** Base is a globally available platform that provides 1-second and <1-cent transactions to anyone in the world.
+- **Access to high-quality tooling:** Builders have access to tools to build incredible onchain experiences for AI, social, media, and entertainment.
+- **A place to earn:** Base has delivered grants to more than 1,000 builders, with plans to continue supporting more.
+- **Reach more users:** Base is committed to helping developers grow their user base by distributing their apps through official Base channels.
+
+
+## A platform for building innovative apps
+
+Base is a global onchain economy of people, builders, and businesses creating the next generation of the open internet. It enables builders to:
+
+- Focus on solving real user problems
+- Scale apps globally by default
+- Onboard users with a click
+- Accept payments from anyone, easily
+
+It’s fast, cheap, and permissionless, meaning anyone can build and use applications on Base.
+
+Base has become the hub for innovative use cases in media, entertainment, social, and even artificial intelligence. [Clanker], an autonomous AI agent on Base, generated more than $13 million in revenue within three months of its inception. As a cultivator of innovation, Base enables developers to focus on improving their products while retaining more of the upside they generate.
+
+Traditional app distribution models often require developers to sacrifice 30% of their revenue to app marketplaces. These platforms may incentivize predatory practices—selling user data or requiring personal information—and can restrict or deny access at their discretion. For instance, someone in Nairobi might be unable to use many U.S.-based fintech services.
+
+In contrast, decentralized finance (DeFi) apps—an onchain development sector—like [Moonwell] allow people anywhere in the world to access financial services directly from their phones. This means someone in Nairobi has the same level of access as someone in the U.S., opening opportunities that were previously inaccessible.
+
+
+
+## Expansive developer tools
+
+Developers choose Base for its:
+
+- Always-on global payment rail operating at internet speed
+- Low transaction costs (often less than a cent)
+- Robust developer tooling
+
+But there’s more: Base apps can be launched in hours, not days or weeks, thanks to an extensive suite of tools—many of which are open source. We’re reviving the spirit of innovation where two builders in a garage can create a massively successful business.
+
+Some of the tooling that makes this possible:
+
+- **Smart Wallets:** Onboard your users quickly and securely. Users never have to worry about seed phrases again.
+- **Coinbase Developer Platform:** Access specialized developer services for onchain development, such as free node software, sponsored transactions, and other tools to help you fine-tune your application.
+- **OnchainKit:** A React component library (TypeScript) to help you build apps faster.
+- **Basenames:** More than just human-readable text to replace an address—Basenames are the front page to a builder’s onchain profile.
+- **Verifications:** Enable unique experiences for users with verified credentials.
+
+
+
+## Builder support
+
+More apps mean more compelling reasons for everyone to get onchain. Base is committed to expanding its developer and user community by creating opportunities for apps to go viral. To support this, Base actively distributes apps through its official channels, including Wallet, X, and Warpcast.
+
+Beyond growth, Base is also a place to earn. Since its launch, we have dedicated a portion of our revenue to the Optimism Collective, supporting initiatives like [Retroactive Public Goods Funding (RetroPGF)] and other ecosystem projects.
+
+We have also distributed builder grants to more than 1,000 builders. Here are a few ways you can earn on Base:
+
+- **[Builder Grants]:** Small, retroactive grants up to 2 ETH
+- **[/base-builds]:** Weekly grants by rounds to Warpcast builders
+- **[Optimism RPGF]:** Projects built on Base are eligible for Optimism RPGF
+- Other community-driven collaborations through based.management, [Bountycaster], and [Talent Protocol]
+
+Base offers builders access to a high-growth, high-signal community across multiple social platforms, including a Discord server with over 400,000 members, X, and Warpcast. We actively amplify impactful projects on these platforms, helping the community discover new innovations. We believe the developers behind these applications are the key to unlocking an onchain future for everyone.
+
+
+
+[Basenames]: https://www.base.org/names
+[planned]: https://ethereum.org/en/roadmap/
+[Solidity]: https://soliditylang.org/
+[Bountycaster]: https://www.bountycaster.xyz/
+[Builder Grants]: https://docs.google.com/forms/d/e/1FAIpQLSeiSAod4PAbXlvvDGtHWu-GqzGpvHYfaTQR2f77AawD7GYc4Q/viewform
+[/base-builds]: https://warpcast.com/base/0xb3f1428b?utm_source=dotorg&urm_medium=builderkit
+[Optimism RPGF]: https://round3.optimism.io/projects?after=undefined&display=grid&sort=mostAwarded&search=&seed=1738341430276&categories=
+[Talent Protocol]: https://www.talentprotocol.com/
+[Moonwell]: https://moonwell.fi/discover
+[Clanker]: https://www.clanker.world/
+[Retroactive Public Goods Funding (RetroPGF)]: https://round3.optimism.io/projects?after=undefined&display=grid&sort=mostAwarded&search=&seed=1738341430276&categories=
diff --git a/docs/base-chain/security/avoid-malicious-flags.mdx b/docs/base-chain/security/avoid-malicious-flags.mdx
new file mode 100644
index 00000000..fd00ccc2
--- /dev/null
+++ b/docs/base-chain/security/avoid-malicious-flags.mdx
@@ -0,0 +1,33 @@
+---
+sidebarTitle: 'Avoid Malicious Flags'
+title: How to avoid getting your app flagged as malicious
+description: The Base bug bounty program and procedures for reporting vulnerabilities.
+---
+
+Ensuring that your app is perceived as trustworthy and not flagged as malicious requires attention to best practices. Here’s a quick guide on how to build a secure and compliant app from day one.
+
+## 1. Verify and reduce the risk of your smart contract
+
+- **Verify Smart Contract**: Ensure that the source code of your contracts is verified and publicly available on [block explorers](/base-chain/tools/block-explorers). For example, this can be done on [Etherscan](https://basescan.org/verifyContract) and [Basescan](https://basescan.org/verifyContract) under “Verify Contract”.
+- **Limit Exposure of User Funds**: Design your contracts to minimize the exposure of user funds. Use efficient design to reduce any unnecessary risk. For example, request the minimum amount needed to fulfill the transaction.
+
+## 2. Submit a verification request
+
+After verifying your smart contract, consider [submitting a verification request](https://report.blockaid.io/). This step helps ensure that your app is recognized as safe and verified by trusted sources in the ecosystem.
+
+## 3. Follow app best practices
+
+- **Accessibility Across Regions**: Avoid geo-blocking or access restrictions that prevent certain regions or countries from accessing your app. Depending on legal or compliance reasons, this may be necessary which you can indicate in your verification request submission.
+- **Consistent Behavior**: Avoid rapid or unexplained changes in UI that can make users feel uncertain about the app’s reliability.
+- **Transparent Onchain Interactions**: Make sure your app’s onchain interactions are clear and match the UI actions. For example, a “Mint” button should clearly emit a mint transaction.
+- **Standard Sign-in Methods**: Provide all standard connection methods for users to sign in, such as WalletConnect / Coinbase Wallet SDK or popular browser extension wallets.
+- **Audit Your Contracts**: Have your contracts audited by a reputable firm. Publish the audit report and provide a reference link so users can easily find it. Audits show that you’ve taken extra steps to secure your smart contracts.
+
+By following these recommendations, you’ll significantly reduce the chances of your app being flagged as malicious and foster a secure and trustworthy environment for your users.
+
+---
+
+**Still having trouble?**
+Coinbase Wallet may report false positives when flagging apps. To avoid false positives, please make sure you have completed the recommended actions above. If your app is still flagged as suspicious or malicious, [report it to Blockaid](https://report.blockaid.io/mistake).
+
+---
diff --git a/docs/base-chain/security/bug-bounty.mdx b/docs/base-chain/security/bug-bounty.mdx
new file mode 100644
index 00000000..7cb267c7
--- /dev/null
+++ b/docs/base-chain/security/bug-bounty.mdx
@@ -0,0 +1,3 @@
+---
+title: 'Bug Bounty'
+---
diff --git a/docs/base-chain/security/report-vulnerability.mdx b/docs/base-chain/security/report-vulnerability.mdx
new file mode 100644
index 00000000..26f81a0c
--- /dev/null
+++ b/docs/base-chain/security/report-vulnerability.mdx
@@ -0,0 +1,19 @@
+---
+sidebarTitle: 'Report a Vulnerability'
+title: Reporting Vulnerabilities
+description: The Base procedures for reporting vulnerabilities.
+---
+
+All potential vulnerability reports can be submitted via the [HackerOne](https://hackerone.com/coinbase) platform.
+
+The HackerOne platform allows us to have a centralized and single reporting source for us to deliver optimized SLAs and results. All reports submitted to the platform are triaged around the clock by our team of Coinbase engineers with domain knowledge, assuring the best quality of review.
+
+## Bug bounty program
+
+In line with our strategy of being the safest way for users to access crypto:
+
+- Coinbase will be extending our [best-in-industry](https://www.coinbase.com/blog/celebrating-10-years-of-our-bug-bounty-program) million-dollar [HackerOne bug bounty program](https://hackerone.com/coinbase?type=team) to cover the Base network, the Base bridge contracts, and Base infrastructure.
+- Coinbase will be working in tandem with OP Labs to harden the security guarantees of Bedrock and accelerate the timeline for decentralized fault-proofs on the [OP Stack](https://stack.optimism.io/).
+- Coinbase's bug bounty program will run alongside Optimism's existing [Immunefi Bedrock bounty program](https://immunefi.com/bounty/optimism/) to support the open source [Bedrock](https://stack.optimism.io/docs/releases/bedrock/) OP Stack framework.
+
+For more information on reporting vulnerabilities and our HackerOne bug bounty program, view our [security program policies](https://hackerone.com/coinbase?view_policy=true).
diff --git a/docs/base-chain/security/security-council.mdx b/docs/base-chain/security/security-council.mdx
new file mode 100644
index 00000000..f1fee274
--- /dev/null
+++ b/docs/base-chain/security/security-council.mdx
@@ -0,0 +1,141 @@
+---
+title: Security Council for Base
+description: This page outlines the purpose, goals, structure, and responsibilities of the Security Council for Base.
+---
+
+This page outlines the purpose, goals, structure, and responsibilities of the
+Security Council for Base. The Council is composed of individuals and
+organizations who hold signing keys and help manage upgrades to keep the Base
+network secure.
+
+## Purpose
+
+Base’s mission is to build a global onchain economy that increases innovation,
+creativity, and freedom. We believe this is only possible on a decentralized
+platform. This is why Base is (1) built on Ethereum, the most secure and
+decentralized L1, (2) built on the open and permissionless OP Stack, and (3)
+upholds key [Neutrality Principles](https://www.coinbase.com/blog/coinbases-neutrality-principles-for-base).
+
+As part of our ongoing commitment to decentralization, Base launched
+[permissionless fault proofs](https://base.mirror.xyz/eOsedW4tm8MU5OhdGK107A9wsn-aU7MAb8f3edgX5Tk) in
+October 2024, [decentralized control of contract upgrades](https://base.mirror.xyz/tWDMlGp48fF0MeADcLQruUBq1Qxkou4O5x3ax8Rm3jA) via a Security Council
+in April 2025, and has now reached Stage 1 Decentralization.
+
+In reaching **Stage 1**, Base provides stronger security guarantees and fewer
+trust assumptions. Builders benefit from infrastructure certainty (no unexpected
+rule changes), and there’s no single point of failure—everyone can participate
+in verifying and securing the network.
+
+## Structure
+
+**Composition and quorum**
+
+Stage 1 Decentralization requirements say that the group which approves Base
+Chain contract upgrades must contain:
+
+- at least 8 participants
+- a ≥75% quorum
+- a quorum-blocking group outside the main rollup operator (Base)
+
+In addition to the current signing entities (Optimism and Coinbase), the
+Security Council adds 10 independent entities and individuals from
+geographically diverse regions. To satisfy the ≥75% quorum, 9 out of the 12
+entities (the 10 entities in the Security Council, Optimism, and Coinbase) are
+required to approve Base upgrades. Base upgrades cannot take effect until a
+quorum of these entities sign and approve the upgrade. This composition
+satisfies all requirements.
+
+**Member Selection criteria**
+
+- Representation across diverse geographic regions and international territories
+- Strong alignment with [Base’s mission and values](https://base.mirror.xyz/jjQnUq_UNTQOk7psnGBFOsShi7FlrRp8xevQUipG_Gk)
+- Diverse organizations - each member represents a separate entity
+- Proven track record in the Base and Ethereum ecosystem - in good standing in upholding professional and ethical standards in the community
+- Technical competency and good security practices - has completed screening processes, including background checks, and have shown ability to securely store and use sensitive key materials
+
+**Current Roster**
+
+This is a living list that will stay up to date with membership. As of April 2025, the Security Council currently contains members from the following entities and individuals, based in the listed geographical jurisdictions.
+
+- [Entity] Aerodrome – signer based in Japan
+ - [Aerodrome](https://aerodrome.finance/) is a decentralized exchange on Base where users can swap, earn rewards and actively participate in the onchain economy.
+ - `0xa5959a39cA67b9fb473E4A3A898C611EEAc9CB73`
+- [Entity] Moonwell – signer based in Brazil
+ - [Moonwell](https://moonwell.fi/) is a decentralized lending and borrowing platform built on Base.
+ - `0x21C7D1e6A81Daca071bA94839ab74C39A25f851F`
+- [Entity] Blackbird – signer based in USA
+ - [Blackbird](https://www.blackbird.xyz/) is a loyalty and payments platform built specifically for the restaurant industry, powered by Base.
+ - `0xA5657B88A0130a626fcDd6aAA59522373438CdFE`
+- [Entity] ChainSafe – signer based in Canada
+ - [ChainSafe](https://chainsafe.io/) is a blockchain R&D firm focused on decentralized infrastructure.
+ - `0x1C56A6d2A6Af643cea4E62e72B75B9bDe8d62e2B`
+- [Entity] Talent Protocol – signer based in Portugal
+ - [Talent Protocol](https://app.talentprotocol.com/) brings professional reputation onchain to help Base builders showcase their skills and get the recognition they deserve.
+ - `0x5ff5C78ff194acc24C22DAaDdE4D639ebF18ACC6`
+- [Entity] Moshicam – signer based in USA
+ - [Moshicam](https://moshi.cam/) is a community-based photo editing app built on Base.
+ - `0xa8ee754FD1d069fb4B5d652730A0ca5e07a3fb06`
+- [Individual] Seneca – based in USA
+ - Seneca is the co-founder of [Rounds](https://rounds.wtf/), a social platform which has [powered](https://x.com/jessepollak/status/1781069700652523725) grant distribution to Base builders.
+ - `0x82C80F34C4b5c153dB76122a11AaD2F77C99E766`
+- [Individual] Juan Suarez – based in USA
+ - Juan is an active member of the Base ecosystem and has advised a number of key Base projects. He is a former member of the Coinbase Legal Team.
+ - `0x99DB5BbA0db16e9aD05e3ff53310683CC3C971D2`
+- [Individual] Toady Hawk – based in Canada
+ - [Toady Hawk](https://warpcast.com/toadyhawk.eth) is the founder of [Zero Rights Media](https://warpcast.com/zerorightsmedia), an open source onchain media org on Base (producers of ZEROPOD), and [The Yellow Collective](https://warpcast.com/basedandyellow), an onchain culture club for artists and creators on Base.
+ - `0x0E8A99738a50D523871739c6d676554b0E34252f`
+- [Individual] Roberto Bayardo – based in USA
+ - [Roberto Bayardo](https://warpcast.com/bayardo.eth) is an engineer at Commonware, building a framework for high-performance blockchains. He is a former core Base contributor.
+ - `0x18e982274f8C5B548D5aAc7aBef44D61504e1b3E`
+
+Individuals representing each entity are not published to protect personal privacy and to enhance security.
+
+**Member Terms**
+
+The Security Council for Base operates on a staggered “cohort” model:
+
+- Cohort 1: 6-month term beginning April 2025
+- Cohort 2: 9-month term beginning April 2025
+
+## Roles & Responsibilities
+
+**Review and approve changes**
+
+- Council members are notified about proposed upgrades, and they must verify, approve, and sign these upgrades.
+- Council members must verify, approve and sign role changes (in case of key rotations for lost devices, member rotations, etc.). Any key rotations will not disrupt quorum or security.
+
+**Maintain availability and lines of communication**
+
+- Be accessible and reachable for scheduled signings, coordination calls, and emergencies.
+- Collaborate with other members to resolve urgent issues.
+
+**Preserve key security**
+
+- Generate and store key materials securely.
+- Keys should only be used for activities which directly relate to the Security Council member role (upgrades and ownership changes).
+- Report suspected loss of access or compromise immediately.
+- Undergo onchain safety and security training at the beginning of each term.
+- At regular intervals, participate in a liveness check by signing a message, to confirm ongoing control of the key.
+
+**Act in good faith**
+
+- Avoid conflicts of interest and disclose potential conflicts.
+- Participate in removing or replacing dysfunctional signers without compromising security.
+
+## The future
+
+The Security Council for Base is a critical step toward a more decentralized,
+resilient, and secure future for the Base network. By distributing key
+responsibilities across trusted, independent participants and implementing fault
+proofs, we’ve reduced reliance on any single entity while strengthening
+guarantees for users, builders, and the broader ecosystem.
+
+This is just the beginning. As Base continues to evolve, the role of the
+Security Council will be progressively minimized, paving the way for even more
+trustless infrastructure beyond Stage 1—Stage 2—and even greater community
+control.
+
+Our mission remains the same: to build a global onchain economy that empowers
+innovation, creativity, and freedom—on a foundation that everyone can rely on.
+
+Base is for everyone.
diff --git a/docs/base-chain/tools/account-abstraction.mdx b/docs/base-chain/tools/account-abstraction.mdx
new file mode 100644
index 00000000..4ef628c5
--- /dev/null
+++ b/docs/base-chain/tools/account-abstraction.mdx
@@ -0,0 +1,53 @@
+---
+title: Account Abstraction
+description: Documentation for Account Abstraction toolkits and solutions for apps built on Base.
+---
+
+## 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 app's onboarding experience. It also offers Gas Manager and Bundler APIs for sponsoring gas and batching transactions.
+
+## Biconomy
+
+[Biconomy](https://www.biconomy.io) is an Account Abstraction toolkit that enables you to provide the simplest UX for your dapp or wallet. It offers modular smart accounts, as well as paymasters and bundlers as a service for sponsoring gas and executing transactions at scale.
+
+## Coinbase Account Abstraction Kit
+
+The Coinbase Developer Platform [Account Abstraction Kit](https://www.coinbase.com/developer-platform/solutions/account-abstraction-kit) is an account abstraction toolkit for building simple onchain user experiences. Account Abstraction Kit provides a paymaster and bundler that allows you to sponsor gas fees and bundle user transactions, improving the user experience of your application.
+
+## Openfort
+
+[Openfort](https://openfort.xyz) is an infrastructure provider designed to simplify the development of games and gamified experiences across their suite of API endpoints. The platform vertically integrates the AA stack, so game developers can focus on game development without worrying about private key management, the account model or the onchain interactions with paymasters and bundlers. The Openfort platform is compatible with most EVM chains, including Base.
+
+## Pimlico
+
+[Pimlico](https://pimlico.io/) provides an infrastructure platform that makes building smart accounts simpler. If you are developing, an ERC-4337 smart account, they provide bundlers, verifying paymasters, ERC-20 paymasters, and much more.
+
+## Reown (prev. known as WalletConnect)
+
+**[Reown](https://reown.com/?utm_source=base&utm_medium=docs&utm_campaign=backlinks)** gives developers the tools to build user experiences that make digital ownership effortless, intuitive, and secure. One of Reown's offerings is the AppKit SDK.
+
+**AppKit** is a powerful, free, and fully open-source SDK for developers looking to integrate wallet connections and other Web3 functionalities into their apps on any EVM and non-EVM chain. In just a few simple steps, you can provide your users with seamless wallet access, one-click authentication, social logins, and notifications—streamlining their experience while enabling advanced features like on-ramp functionality, in-app token swaps and smart accounts. Check out the [docs](https://docs.reown.com/appkit/overview?utm_source=base&utm_medium=docs&utm_campaign=backlinks) to get started.
+
+## Safe
+
+[Safe](https://docs.safe.global/getting-started/readme) provides modular smart account infrastructure and account abstraction stack via their Safe{Core} [Account Abstraction SDK](https://docs.safe.global/safe-core-aa-sdk/safe-core-sdk), [API](https://docs.safe.global/safe-core-api/supported-networks), and [Protocol](https://docs.safe.global/safe-core-protocol/safe-core-protocol).
+
+## Stackup
+
+[Stackup](https://www.stackup.sh) provides smart account tooling for building account abstraction within your apps. They offer Paymaster and Bundler APIs for sponsoring gas and sending account abstraction transactions.
+
+## thirdweb
+[thirdweb](https://portal.thirdweb.com/typescript/v5/account-abstraction/get-started) offers the complete toolkit to leverage account abstraction technology to enable seamless user experiences for your users. This includes Account Factory contracts that let your users spin up Smart Accounts, Bundler for UserOps support, and Paymaster to enable gas sponsorships.
+
+## WalletKit
+
+[WalletKit](https://walletkit.com) is an all-in-one platform for adding smart, gasless wallets to your app. It has integrated support for ERC 4337 and comes with a paymaster and bundler included, requiring no extra setup.
+
+WalletKit also offers pre-built components for onboarding users with email and social logins, which can be integrated in under 15 minutes using their React SDK or the wagmi connector. Alternatively, build completely bespoke experiences for your users using WalletKit's Wallets API.
+
+WalletKit is compatible with most EVM chains, including Base. You can check out the [WalletKit documentation here](https://docs.walletkit.com). Start building for free on the Base testnet today.
+
+## 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 flows by batching and automating transactions.
diff --git a/docs/base-chain/tools/base-products.mdx b/docs/base-chain/tools/base-products.mdx
new file mode 100644
index 00000000..b2420788
--- /dev/null
+++ b/docs/base-chain/tools/base-products.mdx
@@ -0,0 +1,24 @@
+---
+title: 'Base Products'
+---
+
+
+
+ Neque porro quisquam est qui dolorem ipsum quia dolor sit amet
+
+
+ Lorem ipsum dolor sit amet, consectetur adipiscing elit
+
+
+ Ut enim ad minim veniam, quis nostrud exercitation ullamco
+
+
+ Excepteur sint occaecat cupidatat non proident
+
+
+ Excepteur sint occaecat cupidatat non proident
+
+
+ Excepteur sint occaecat cupidatat non proident
+
+
\ No newline at end of file
diff --git a/docs/base-chain/tools/block-explorers.mdx b/docs/base-chain/tools/block-explorers.mdx
new file mode 100644
index 00000000..3786139c
--- /dev/null
+++ b/docs/base-chain/tools/block-explorers.mdx
@@ -0,0 +1,59 @@
+---
+title: 'Block Explorers'
+description: Documentation for block explorers for the Base network.
+---
+
+## Arkham
+
+The Arkham [Platform](https://platform.arkhamintelligence.com/) supports Base.
+
+Arkham is a crypto intelligence platform that systematically analyzes blockchain transactions, showing users the people and companies behind blockchain activity, with a suite of advanced tools for analyzing their activity.
+
+## Blockscout
+
+A Blockscout explorer is available for [Base](https://base.blockscout.com/).
+
+Blockscout provides tools to help you debug smart contracts and transactions:
+
+- View, verify, and interact with smart contract source code.
+- View detailed transaction information
+
+A testnet explorer for [Base Sepolia](https://base-sepolia.blockscout.com/) is also available.
+
+## Etherscan
+
+An Etherscan block explorer is available for [Base](https://basescan.org).
+
+Etherscan provides tools to help you view transaction data and debug smart contracts:
+
+- Search by address, transaction hash, batch, or token
+- View, verify, and interact with smart contract source code
+- View detailed transaction information
+- View L1-to-L2 and L2-to-L1 transactions
+
+A testnet explorer for [Base Sepolia](https://sepolia.basescan.org/) is also available.
+
+## DexGuru
+
+[DexGuru](https://base.dex.guru) provides a familiar UI with data on transactions, blocks, account balances and more. Developers can use it to verify smart contracts and debug transactions with interactive traces and logs visualization.
+
+## L2scan Explorer
+
+[L2scan Explorer](https://base.l2scan.co/) is a web-based tool that allows users to analyze Base and other layer 2 networks. It provides a user-friendly interface for viewing transaction history, checking account balances, and tracking the status of network activity.
+
+## OKLink
+
+[OKLink](https://www.oklink.com/base) is a multi-chain blockchain explorer that supports Base and provides the following features for developers:
+
+- Search by address, transaction, block, or token
+- View, verify, and interact with smart contract source code
+- Access a comprehensive and real-time stream of on-chain data, including large transactions and significant fund movements
+- Address labels (i.e. project labels, contract labels, risk labels, black address labels, etc.)
+
+## Routescan
+
+[Routescan](https://routescan.io/) superchain explorer allows you to search for transactions, addresses, tokens, prices and other activities taking place across all Superchain blockchains, including Base.
+
+## Tenderly Explorer
+
+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/docs/base-chain/tools/cross-chain.mdx b/docs/base-chain/tools/cross-chain.mdx
new file mode 100644
index 00000000..371d8a94
--- /dev/null
+++ b/docs/base-chain/tools/cross-chain.mdx
@@ -0,0 +1,77 @@
+---
+title: Cross-chain
+description: Documentation for cross-chain communication and messaging on the Base network. This page covers integrating tools like LayerZero with Base for web3 transactions, cross-chain messaging, and secure blockchain communication.
+---
+
+import {HeaderNoToc} from "/snippets/headerNoToc.mdx";
+
+## Axelar
+
+[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 use cases please visit the available [code examples](https://github.com/axelarnetwork/axelar-examples).
+
+
+Requests to Coinbase Developer Platform's Faucet are limited to one claim per 24 hours.
+
+
+
+## thirdweb Faucet
+
+The [thirdweb Faucet](https://thirdweb.com/base-sepolia-testnet) provides free testnet ETH on Base Sepolia - one claim per 24 hours.
+
+
+The thirdweb faucet allows developers to connect their wallet through EOA or social logins and claim Base Sepolia testnet funds.
+
+
+
+## Superchain Faucet
+
+The [Superchain Faucet](https://app.optimism.io/faucet) provides testnet ETH for all OP Chains, including Base.
+
+
+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).
+
+
+
+## Alchemy Faucet
+
+The [Alchemy Faucet](https://basefaucet.com/) is a fast and reliable network faucet that allows users with a free Alchemy account to request testnet ETH on Base Sepolia.
+
+
+Requests to Alchemy's Base Sepolia Faucet are limited to one claim per 24 hours.
+
+
+
+## Bware Labs Faucet
+
+[Bware Labs Faucet](https://bwarelabs.com/faucets) is an easy to use faucet with no registration required. You can use Bware Labs Faucet to claim Base Sepolia testnet ETH for free - one claim per 24 hours.
+
+
+Requests to Bware Labs Faucet are limited to one claim per 24 hours.
+
+
+
+## QuickNode Faucet
+
+[QuickNode Faucet](https://faucet.quicknode.com/drip) is an easy to use Multi-Chain Faucet. You can use QuickNode Faucet to claim Base Sepolia testnet ETH for free - one drip per network every 12 hours.
+
+
+Requests to QuickNode Faucet are limited to one drip every 12 hours.
+
+
+
+## LearnWeb3 Faucet
+
+[LearnWeb3 Faucet](https://learnweb3.io/faucets/base_sepolia) is a multi-chain faucet by LearnWeb3. You can use the LearnWeb3 faucet to claim Base Sepolia testnet ETH for free - one claim every 24 hours.
+
+
+Requests to LearnWeb3 faucet are limited to one claim per 24 hours.
+
+
+
+## Ethereum Ecosystem Faucet
+
+The [Base Sepolia Faucet](https://www.ethereum-ecosystem.com/faucets/base-sepolia) is a free & easy to use testnet faucet for Base Sepolia with very generous drips that doesn't require users to log in. It's run by [Ethereum Ecosystem](https://www.ethereum-ecosystem.com).
+
+
+Each wallet is restricted to receiving 0.5 ETH from this faucet every 24 hours.
+
diff --git a/docs/base-chain/tools/node-providers.mdx b/docs/base-chain/tools/node-providers.mdx
new file mode 100644
index 00000000..86e65f29
--- /dev/null
+++ b/docs/base-chain/tools/node-providers.mdx
@@ -0,0 +1,197 @@
+---
+title: 'Node Providers'
+description: Documentation for Node Providers for the Base network. Including details on their services, supported networks, and pricing plans.
+---
+
+import {HeaderNoToc} from "/snippets/headerNoToc.mdx";
+
+## Coinbase Developer Platform (CDP)
+
+[CDP](https://portal.cdp.coinbase.com/) provides an RPC endpoint that runs on the same node infrastructure that powers Coinbase's retail exchange, meaning you get the rock solid reliability of our retail exchange as a developer. CDP gives you a free, rate limited RPC endpoint to begin building on Base.
+
+
+The base url for our API endpoints is [https://base.org/api/registry/](https://base.org/api/registry/). The use of Onchain Registry API is governed by the license terms outlined in our [Terms & Conditions](#terms--conditions).
+
+
+
+## Instructions
+
+1. Users of this API can use the `/entries` and `/featured` endpoints to display Onchain Registry entries on their own surfaces
+2. If your team would like to use referral codes to point your users to entries, we recommend appending your referral code to the link provided in the `target_url` field
+3. If your team would like to filter entries based on where they are hosted or by creator, we recommend implementing logic based on the `target_url` and `creator_name` fields
+
+## Endpoints
+
+### GET /entries
+
+This endpoint will display all Onchain Registry entries subject to any query parameters set below
+
+#### Query Parameters
+
+| Name | Type | Description |
+| :------- | :----- | :------------------------------------------------------------------------------------------------------------- |
+| page | number | The page number (default 1) |
+| limit | number | The number of entries per page (default 10) |
+| category | array | The category or categories of the entries of interest
(Options: Games, Social, Creators, Finance, Media) | +| curation | string | The entry's level of curation
(Options: Featured, Curated, Community) | + +#### Response + +```json [JSON] +{ + "data": [ + { + "id": "7AsRdN8uf601fCkH1e084F", + "category": "Creators", + "content": { + "title": "Based Project", + "short_description": "Short description of this based project with max char count of 30", + "full_description": "Full description of this based project with max char count of 200", + "image_url": "https://base.org/image.png", + "target_url": "https://base.org/target-page", + "cta_text": "Mint", + "function_signature": "mint(uint256)", + "contract_address": "0x1FC10ef15E041C5D3C54042e52EB0C54CB9b710c", + "token_id": "2", + "token_amount": "0.01", + "featured": true, + "creator_name": "Base", + "creator_image_url": "https://base.org/creator-image.png", + "curation": "featured", + "start_ts": "2024-06-25T04:00:00Z", + "expiration_ts": "2024-07-29T00:00:00Z" + }, + "updated_at": null, + "created_at": "2024-07-10T18:20:42.000Z" + }, + { + "id": "8fRbdN8uf601fCkH1e084F", + "category": "Games", + "content": { + "title": "Based Project II", + "short_description": "Short description of this second based project with max char count of 30", + "full_description": "Full description of this second based project with max char count of 200", + "image_url": "https://base.org/image2.png", + "target_url": "https://base.org/second-target-page", + "cta_text": "Mint", + "function_signature": "mint(uint256)", + "contract_address": "0x1FC10ef15E041C5D3C54042e52EB0C54CB9b710c", + "token_id": "1", + "token_amount": "0.005", + "featured": false, + "creator_name": "Base", + "creator_image_url": "https://base.org/creator-image2.png", + "curation": "community", + "start_ts": "2024-06-25T04:00:00Z", + "expiration_ts": "2024-07-29T00:00:00Z" + }, + "updated_at": "2024-07-11T18:20:42.000Z", + "created_at": "2024-07-10T18:20:42.000Z" + } + ], + "pagination": { + "total_records": 2, + "current_page": 1, + "total_pages": 1, + "limit": 10 + } +} +``` + +### GET /featured + +This endpoint will display a single Onchain Registry entry that is being actively featured + +#### Response + +```json [JSON] +{ + "data": { + "id": "7AsRdN8uf601fCkH1e084F", + "category": "Creators", + "content": { + "title": "Based Project", + "short_description": "Short description of this based project with max char count of 30", + "full_description": "Full description of this based project with max char count of 200", + "image_url": "https://base.org/image.png", + "target_url": "https://base.org/target-page", + "cta_text": "Mint", + "function_signature": "mint(uint256)", + "contract_address": "0x1FC10ef15E041C5D3C54042e52EB0C54CB9b710c", + "token_id": "2", + "token_amount": "0.01", + "featured": true, + "creator_name": "Base", + "creator_image_url": "https://base.org/creator-image.png", + "curation": "featured", + "start_ts": "2024-06-25T04:00:00Z", + "expiration_ts": "2024-07-29T00:00:00Z" + }, + "updated_at": null, + "created_at": "2024-07-10T18:20:42.000Z" + } +} +``` + +## Entry Schema + +| Name | Type | Description | +| :----------------- | :--------------- | :------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| id | string | Unique entry ID | +| category | string | The category of the entry
(Options: Games, Social, Creators, Finance, Media) | +| title | string | The title of the entry | +| short_description | string | Short version of the entry description (max 30 char) | +| full_description | string | Full version of the entry description (max 200 char) | +| image_url | string | URL of the entry's featured image | +| target_url | string | URL for the entry's desired user action | +| cta_text | string | This is the type of user action for the entry
(Options: Play, Mint, Buy, Trade, Explore) | +| function_signature | string | The function signature associated with the desired user action on the entry's contract | +| contract_address | string | The contract address associated with the entry | +| token_id | string | The token ID if this is an ERC-1155 | +| token_amount | string | The price of the entry's desired user action | +| featured | boolean | A true or false based on whether the entry is actively featured | +| creator_name | string | The name of the entry's creator | +| creator_image_url | string | The logo of the entry's creator | +| curation | string | The entry's level of curation
Options:
+To use Chainlink datafeeds, you may need [LINK](https://docs.chain.link/resources/link-token-contracts?parent=dataFeeds) token.
+
+
+
+
+
+[image2]:
+
+[image3]:
+
+[image4]:
diff --git a/docs/components/App.tsx b/docs/components/App.tsx
deleted file mode 100644
index 503f939d..00000000
--- a/docs/components/App.tsx
+++ /dev/null
@@ -1,75 +0,0 @@
-'use client';
-
-import { OnchainKitProvider } from '@coinbase/onchainkit';
-import '@coinbase/onchainkit/styles.css';
-import { QueryClient, QueryClientProvider } from '@tanstack/react-query';
-import type { ReactNode } from 'react';
-import { http, WagmiProvider, createConfig } from 'wagmi';
-import { base, baseSepolia } from 'wagmi/chains';
-import { coinbaseWallet } from 'wagmi/connectors';
-import { useTheme } from '../contexts/Theme.tsx';
-import { defineChain } from 'viem';
-
-const queryClient = new QueryClient();
-
-export const SANDBOX_CHAIN = defineChain({
- id: 8453200058,
- name: 'Sandbox Network',
- nativeCurrency: {
- name: 'Ethereum',
- symbol: 'ETH',
- decimals: 18,
- },
- rpcUrls: {
- default: {
- http: ['https://sandbox-rpc-testnet.appchain.base.org'],
- },
- },
-});
-
-const wagmiConfig = createConfig({
- chains: [base, baseSepolia, SANDBOX_CHAIN],
- connectors: [
- coinbaseWallet({
- appName: 'OnchainKit',
- }),
- ],
- ssr: true,
- transports: {
- [base.id]: http(),
- [baseSepolia.id]: http(),
- [SANDBOX_CHAIN.id]: http(),
- },
-});
-
-export default function App({ children }: { children: ReactNode }) {
- const isServer = typeof window === 'undefined';
- if (isServer) {
- return null;
- }
-
- const viteCdpApiKey = import.meta.env.VITE_CDP_API_KEY;
- const viteProjectId = import.meta.env.VITE_CDP_PROJECT_ID;
- const { theme } = useTheme();
-
- return (
-
-
-
-
-
-
- );
-}
diff --git a/docs/config/guides.ts b/docs/config/guides.ts
deleted file mode 100644
index af4bb35b..00000000
--- a/docs/config/guides.ts
+++ /dev/null
@@ -1,16 +0,0 @@
-export const topGuides = [
- {
- title: 'Build an E-commerce App',
- path: '/guides/use-case-guides/commerce/build-an-ecommerce-app'
- },
- {
- title: 'Add an In-App Onramp ',
- path: '/guides/use-case-guides/finance/build-a-smart-wallet-funding-app'
- },
- {
- title: 'Run a Base Node',
- path: '/docs/chain/run-a-base-node'
- }
-] as const
-
-export type Guide = typeof topGuides[number]
\ No newline at end of file
diff --git a/docs/constants.ts b/docs/constants.ts
deleted file mode 100644
index a9d39e81..00000000
--- a/docs/constants.ts
+++ /dev/null
@@ -1 +0,0 @@
-export const isDevelopment = import.meta.env.MODE === 'development';
diff --git a/docs/contexts/AppProviders.tsx b/docs/contexts/AppProviders.tsx
deleted file mode 100644
index a4f70a28..00000000
--- a/docs/contexts/AppProviders.tsx
+++ /dev/null
@@ -1,14 +0,0 @@
-import { lazy, Suspense } from 'react';
-
-const CookieBannerWrapper = lazy(async () => import('./CookieBannerWrapper'));
-
-export function AppProviders({ children }: { children: React.ReactNode }) {
- return (
- <>
- {children}
-
-
-
- );
-}
diff --git a/docs/contexts/CookieBannerWrapper.tsx b/docs/contexts/CookieBannerWrapper.tsx
deleted file mode 100644
index 62885ff4..00000000
--- a/docs/contexts/CookieBannerWrapper.tsx
+++ /dev/null
@@ -1,71 +0,0 @@
-import { CookieManagerProvider } from '@/components/CookieManager/CookieManagerProvider.tsx';
-import ClientAnalyticsScript from '@/components/ClientAnalyticsScript/ClientAnalyticsScript.tsx';
-import { isDevelopment } from '@/constants.ts';
-/*
- * CJS import
- * This import structure for CookieBanner is necessary because in prod, direct
- * destructuring from @coinbase/cookie-banner fails.
- * However in dev, the import fails because the pkg is not found.
- * This structure allows the import to work in prod, and disables the banner in dev.
- */
-import pkg from '@coinbase/cookie-banner';
-const { CookieBanner } = isDevelopment ? {} : pkg;
-
-export const cookieBannerTheme = {
- colors: {
- primary: '#1652F0',
- positive: '#05B169',
- negative: '#DF5F67',
- warning: '#F4C622',
- background: '#FFFFFF',
- backgroundMuted: '#EEF0F3',
- onBackground: '#050F1A',
- onBackgroundMuted: '#0A0B0D',
- onPrimary: '#FFFFFF',
- overlay: 'rgba(17,52,83,0.6)',
- },
- border: {
- border: '1px solid #D8D8D8',
- borderRadius: '4px',
- },
- fontSize: {
- sm: '14px',
- md: '16px',
- },
- fontWeight: {
- regular: '400',
- bold: '500',
- },
- size: {
- xs: '8px',
- sm: '16px',
- md: '24px',
- lg: '32px',
- },
- breakpoints: {
- phone: 560,
- desktop: 992,
- tablet: 768,
- },
- zIndex: {
- hidden: 0,
- normal: 1,
- elevated: 2,
- high: 2,
- extraHigh: 3,
- backdrop: 999,
- overlay: 1000,
- top: 1001,
- },
-};
-
-export default function CookieBannerWrapper() {
- if (isDevelopment || typeof window === 'undefined') return null;
-
- return (
-
-
- );
-}
diff --git a/docs/cookbook/accept-crypto-payments.mdx b/docs/cookbook/accept-crypto-payments.mdx
new file mode 100644
index 00000000..dd293311
--- /dev/null
+++ b/docs/cookbook/accept-crypto-payments.mdx
@@ -0,0 +1,394 @@
+---
+title: 'Accept Crypto Payments with Coinbase Commerce & OnchainKit'
+sidebarTitle: 'Accept Crypto Payments'
+description: 'Learn how to integrate Coinbase Commerce payments into your application using OnchainKit to eliminate traditional fees and expand your global reach.'
+---
+
+Accepting crypto payments can help you **eliminate traditional credit card fees** and **avoid costly chargebacks**, giving you a faster, more global payment experience. In this guide, you'll learn how to quickly integrate Coinbase Commerce and OnchainKit to accept crypto payments for products or services in your application.
+
+## What You'll Build
+
+By the end of this guide, you'll have a fully functional checkout flow that:
+
+- Displays your product with an attractive interface
+- Connects users' wallets securely
+- Processes crypto payments through Coinbase Commerce
+- Provides real-time payment status updates
+
+
+
+ Remove traditional credit card processing fees and chargebacks
+
+
+ Accept payments from crypto users worldwide, 24/7
+
+
+ Receive payments instantly with blockchain confirmation
+
+
+ Get started in minutes with OnchainKit components
+
+
+
+## Prerequisites
+
+Before you begin, ensure you have the following accounts and tools set up:
+
+
+
+ [Sign up for Coinbase Commerce](https://beta.commerce.coinbase.com/sign-up) to accept cryptocurrency payments globally.
+
+
+ You'll need this to create products and manage payments.
+
+
+
+
+ [Create a CDP account](https://www.coinbase.com/cloud) to access OnchainKit APIs and services.
+
+
+ CDP provides the infrastructure for seamless crypto integrations.
+
+
+
+
+ [Set up Reown](https://cloud.reown.com/) (formerly WalletConnect) for secure wallet connections across devices and platforms.
+
+
+
+## Implementation Guide
+
+
+
+
+ First, you'll create a product in Coinbase Commerce that represents what you're selling.
+
+ 1. **Log in** to your [Coinbase Commerce dashboard](https://beta.commerce.coinbase.com/)
+ 2. Navigate to the [product creation page](https://beta.commerce.coinbase.com/products)
+ 3. **Fill in your product details**:
+ - Product name (clear and descriptive)
+ - Description (what customers are buying)
+ - Price (in your preferred currency)
+ 4. Click **Create product**
+ 5. Once created, select **View product** and copy the **UUID** from the URL
+
+
+ 
+
+
+
+ Save the product UUID immediately - you'll need it as an environment variable. The UUID appears in the product URL after creation.
+
+
+
+
+
+ Clone the official OnchainKit app template to get started quickly with best practices already configured.
+
+
+ ```bash Bun
+ git clone https://github.com/coinbase/onchainkit-app-template.git
+ cd onchainkit-app-template
+ bun install
+ ```
+
+ ```bash npm
+ git clone https://github.com/coinbase/onchainkit-app-template.git
+ cd onchainkit-app-template
+ npm install
+ ```
+
+ ```bash Yarn
+ git clone https://github.com/coinbase/onchainkit-app-template.git
+ cd onchainkit-app-template
+ yarn install
+ ```
+
+
+
+ Verify the installation completed successfully by running `ls` to see the project files.
+
+
+
+
+
+ Create your environment configuration with the required API keys and identifiers.
+
+ In your project root, create or update your `.env.local` file:
+
+ ```bash .env.local
+ # Coinbase Commerce Product ID (from Step 1)
+ NEXT_PUBLIC_PRODUCT_ID=your_product_uuid_here
+
+ # Coinbase Developer Platform API Key
+ NEXT_PUBLIC_ONCHAINKIT_API_KEY=your_cdp_api_key_here
+
+ # Reown (WalletConnect) Project ID
+ NEXT_PUBLIC_WC_PROJECT_ID=your_walletconnect_project_id_here
+
+ # Disable Next.js telemetry (optional)
+ NEXT_TELEMETRY_DISABLED=1
+ ```
+
+
+ Never commit API keys to version control. Add `.env.local` to your `.gitignore` file.
+
+
+
+ Use descriptive variable names and keep them organized with comments for team members.
+
+
+
+
+
+ Set up Wagmi to prioritize smart wallets for better user experience.
+
+ Update your Wagmi configuration file (typically `src/app/wagmi.ts`):
+
+ ```typescript src/app/wagmi.ts
+ // ... existing Wagmi configuration
+
+ // After your useMemo() hook, add:
+ coinbaseWallet.preference = 'smartWalletOnly';
+ ```
+
+
+ This configuration ensures users connect with smart wallets, which provide enhanced security and better UX.
+
+
+
+
+
+ Configure the OnchainKit provider to connect with Base network and your CDP API key.
+
+ Update `src/app/components/OnchainProviders.tsx`:
+
+ ```typescript src/app/components/OnchainProviders.tsx
+ 'use client';
+ import { OnchainKitProvider } from '@coinbase/onchainkit';
+ import { RainbowKitProvider } from '@rainbow-me/rainbowkit';
+ import { QueryClient, QueryClientProvider } from '@tanstack/react-query';
+ import type { ReactNode } from 'react';
+ import { base } from 'viem/chains';
+ import { WagmiProvider } from 'wagmi';
+ import { useWagmiConfig } from '../wagmi';
+
+ type Props = { children: ReactNode };
+ const queryClient = new QueryClient();
+
+ function OnchainProviders({ children }: Props) {
+ const wagmiConfig = useWagmiConfig();
+
+ return (
+
+
+
+
+ {children}
+
+
+
+
+ );
+ }
+
+ export default OnchainProviders;
+ ```
+
+ Update your configuration file to handle environment variables properly:
+
+ ```typescript Config.ts
+ export const NEXT_PUBLIC_URL =
+ process.env.NODE_ENV === 'development'
+ ? 'http://localhost:3000'
+ : 'https://your-app-domain.vercel.app'; // Replace with your actual domain
+
+ export const NEXT_PUBLIC_CDP_API_KEY =
+ process.env.NEXT_PUBLIC_ONCHAINKIT_API_KEY;
+
+ export const NEXT_PUBLIC_WC_PROJECT_ID =
+ process.env.NEXT_PUBLIC_WC_PROJECT_ID;
+ ```
+
+
+ Using environment variables makes your app more secure and easier to deploy across different environments.
+
+
+
+
+
+ Create an attractive payment interface that showcases your product and handles the checkout flow.
+
+ Update your main page (`src/app/page.tsx`):
+
+ ```typescript src/app/page.tsx
+ import { Checkout, CheckoutButton, CheckoutStatus } from '@coinbase/onchainkit/checkout';
+ import Image from 'next/image';
+
+ const productId = process.env.NEXT_PUBLIC_PRODUCT_ID;
+
+ export default function PaymentPage() {
+ return (
+
+
+ );
+ }
+ ```
+
+
+ Make sure to add your product image to the `public` folder and update the image path accordingly.
+
+
+
+ The conditional rendering prevents errors when no wallet is connected, providing a smooth user experience.
+
+
+
+
+
+ Test your payment flow locally before deploying to production.
+
+ **Local Testing:**
+
+
+ ```bash Bun
+ bun run dev
+ ```
+
+ ```bash npm
+ npm run dev
+ ```
+
+ ```bash Yarn
+ yarn dev
+ ```
+
+
+ 1. **Visit** `http://localhost:3000`
+ 2. **Connect your wallet** using the wallet connection button
+ 3. **Test the checkout flow** with a small amount
+ 4. **Verify payment status** updates correctly
+
+
+ 
+
+
+ **Production Deployment:**
+
+ 1. **Update your configuration** with production URLs
+ 2. **Deploy to your preferred platform** (Vercel, Netlify, etc.)
+ 3. **Test the live application** with real transactions
+ 4. **Monitor payment confirmations** in your Coinbase Commerce dashboard
+
+
+ Start with testnet transactions to ensure everything works before going live with mainnet.
+
+
+
+
+## Troubleshooting
+
+
+
+ **Common solutions:**
+ - Ensure your WalletConnect project ID is correctly configured
+ - Check that your wallet extension is updated to the latest version
+ - Try connecting with a different wallet provider
+ - Clear your browser cache and cookies
+
+
+
+ **Check these items:**
+ - Verify your product ID matches exactly with Coinbase Commerce
+ - Ensure your CDP API key has the necessary permissions
+ - Confirm the user has sufficient funds for the transaction
+ - Check network connectivity and blockchain status
+
+
+
+ **Configuration checklist:**
+ - All required environment variables are set in `.env.local`
+ - No extra spaces or quotes around variable values
+ - File is in the project root directory
+ - Restart your development server after making changes
+
+
+
+## Next Steps
+
+Now that you have crypto payments working, consider these enhancements:
+
+
+
+ Scale your setup to handle multiple products and services
+
+
+ Set up payment confirmation webhooks for automated processing
+
+
+ Track payment metrics and customer behavior
+
+
+ Accept payments on multiple blockchain networks
+
+
+
+## Conclusion
+
+Congratulations! You've successfully integrated Coinbase Commerce and OnchainKit into your application. Your users can now make crypto payments, giving you access to:
+
+✅ **Zero traditional payment fees and chargebacks**
+✅ **Global customer reach with 24/7 payment processing**
+✅ **Instant settlement with blockchain confirmation**
+✅ **Enhanced security through smart wallet integration**
+
+**Ready to scale?** Consider expanding to multiple products, implementing automated fulfillment, or adding analytics to track your crypto payment performance.
+
+
+Your application now supports the future of global payments. Happy building on Base!
+
diff --git a/docs/cookbook/ai-prompting.mdx b/docs/cookbook/ai-prompting.mdx
new file mode 100644
index 00000000..4b3e5fcc
--- /dev/null
+++ b/docs/cookbook/ai-prompting.mdx
@@ -0,0 +1,10 @@
+---
+sidebarTitle: AI-powered IDEs
+title: Use AI-powered IDEs
+description: How to use AI-powered IDEs to generate code for OnchainKit.
+---
+
+import AiPowered from "/snippets/ai-powered.mdx";
+
+
+
+ Create a new OnchainKit app
+
+ ```bash Terminal
+ npm create onchain@latest
+ ```
+
+
+ ```typescript App.tsx
+ import { SwapDefault } from '@coinbase/onchainkit/swap'; // [!code focus]
+ import type { Token } from '@coinbase/onchainkit/token';
+
+ const eth: Token = {
+ name: 'ETH',
+ address: '',
+ symbol: 'ETH',
+ decimals: 18,
+ image:
+ 'https://wallet-api-production.s3.amazonaws.com/uploads/tokens/eth_288.png',
+ chainId: 8453,
+ };
+
+ const usdc: Token = {
+ name: 'USDC',
+ address: '0x833589fcd6edb6e08f4c7c32d4f71b54bda02913',
+ symbol: 'USDC',
+ decimals: 6,
+ image:
+ 'https://d3r81g40ycuhqg.cloudfront.net/wallet/wais/44/2b/442b80bd16af0c0d9b22e03a16753823fe826e5bfd457292b55fa0ba8c1ba213-ZWUzYjJmZGUtMDYxNy00NDcyLTg0NjQtMWI4OGEwYjBiODE2',
+ chainId: 8453,
+ };
+
+
+
+
+You should now see the following swap component in your app:
+
+
+
+{/*
+
+ {({ address, swappableTokens }) => {
+ if (address) {
+ return (
+
+
+
+
+ ;
+ }}
+
+ */}
+
+The Swap component uses **Uniswap V3** as the default router, but you can also use the **0x Aggregator** by setting the `experimental.useAggregator` prop to `true`.
+
+
+
+### Swap Settings
+The Swap component comes preconfigured but is highly customizable. Just a couple of the settings you can customize:
+- Swap settings
+- bidirectional or unidirectional swaps
+- Gasless swaps with paymasters
+
+To learn more about how to customize the Swap component, check out the [Swap docs](/onchainkit/swap/swap).
+
+
+## Earn Component Integration
+
+The `Earn` component enables users to deposit assets into yield-generating vaults and withdraw them later—all within your app. The `Earn` component currently supports Morpho vaults on Base.
+
+
+**Get a vault address**
+
+You can get a vault address from Morpho's [Vaults page](https://app.morpho.org/base/earn). You will use this address when setting up the `Earn` component.
+
+
+
+```tsx twoslash
+// @noErrors: 2307
+import { Earn } from '@coinbase/onchainkit/earn'; // [!code focus]
+
+
+```tsx index.tsx
+// @noErrors: 2307
+import { Earn, useEarnContext } from '@coinbase/onchainkit/earn';
+import { CustomDepositButtons } from '@/custom-deposit-buttons';
+
+
+
+
+```
+
+```tsx custom-deposit-buttons.tsx
+import {EarnDetails,
+ EarnDeposit,
+ useEarnContext,
+ DepositButton} from '@coinbase/onchainkit/earn';
+
+const predefinedAmounts = ['0.1', '1', '10'];
+
+function CustomDepositButtons() {
+ const { depositAmount, setDepositAmount } = useEarnContext();
+
+ return (
+
+
+ );
+}
+```
+
+
+
+
+{/*
+To use the `FundCard` component, you'll need to provide a Client API Key in `OnchainKitProvider`. You can get one following our [Getting Started](/onchainkit/installation/nextjs#get-your-client-api-key) steps.
+
+
+
+```tsx App.tsx
+import { FundCard } from '@coinbase/onchainkit/fund';
+
+
+
+ {({ address }) => {
+ if (address) {
+ return
+
+
+
+
+ );
+ }}
+
+ */}
+
+To learn more about the `FundCard` component and its features, check out the [FundCard docs](/onchainkit/fund/fund-card).
+
+## The `Buy` Component
+
+The `Buy` components provide a comprehensive interface for users to purchase [Tokens](/onchainkit/token/types#token).
+
+The `Buy` component supports token swaps from USDC and ETH by default with the option to provide an additional token of choice using the `fromToken` prop. Users are able to purchase tokens using their Coinbase account, Apple Pay, or debit card.
+
+
+This component requires a `projectId` to be set in the `OnchainKitProvider`. You can find your `projectId` on [Coinbase Developer Platform](https://portal.cdp.coinbase.com/products/onchainkit).
+
+
+
+```tsx twoslash
+import { Buy } from '@coinbase/onchainkit/buy'; // [!code focus]
+import type { Token } from '@coinbase/onchainkit/token';
+
+export default function BuyComponents() { // [!code focus]
+ const degenToken: Token = {
+ name: 'DEGEN',
+ address: '0x4ed4e862860bed51a9570b96d89af5e1b0efefed',
+ symbol: 'DEGEN',
+ decimals: 18,
+ image:
+ 'https://d3r81g40ycuhqg.cloudfront.net/wallet/wais/3b/bf/3bbf118b5e6dc2f9e7fc607a6e7526647b4ba8f0bea87125f971446d57b296d2-MDNmNjY0MmEtNGFiZi00N2I0LWIwMTItMDUyMzg2ZDZhMWNm',
+ chainId: 8453,
+ };
+
+ return ( // [!code focus]
+
+
+ {({ address, toToken }) => {
+ return (
+
+ */}
+
+
+**Note: This interface is for demonstration purposes only.**
+
+Swap and Onramp flows will execute and work out of the box when you implement the component in your own app.
+
+
+
+By combining Swap, Earn, Fund, and Buy with these additional tools, you can quickly build a robust in-app DeFi experience with minimal development overhead. This lets you focus on building your unique value proposition.
+
+
+## Next Steps
+
+If you're using these components, its likely you'll benefit from the following components:
+
+- [`
+
+Get early access to Base Appchains and transform your scaling strategy
+
+
+
+Jump to our step-by-step onboarding process
+
+
+
+## What Are Base Appchains?
+
+Base Appchains are **app-specific Layer 3 rollups** built on Base that provide dedicated blockspace for individual applications. Instead of competing with thousands of other apps for network resources, you get your own high-performance blockchain that rolls up to Base and inherits Ethereum's security.
+
+
+Layer 3 appchains roll up to Base (Layer 2), which settles on Ethereum, providing you with dedicated performance while maintaining the security guarantees of the Ethereum ecosystem.
+
+
+Think of it as the difference between **sharing a highway during rush hour** versus **having your own dedicated express lane**. With shared blockspace, your app's performance depends on network-wide activity. With an Appchain, you get consistent, predictable performance regardless of what's happening elsewhere.
+
+
+
+Compete with other apps for network resources, leading to variable performance, unpredictable costs, and user experience issues during peak times.
+
+
+
+Your own infrastructure with predictable performance, custom gas tokens, full control over throughput, and consistent user experience.
+
+
+
+## Why Choose Base Appchains?
+
+### High-Speed Performance Built for Scale
+
+Stop letting network congestion impact your user experience. Base Appchains deliver **1-second block times** and **sub-10 second withdrawals**, making them 10x faster than typical blockchain interactions.
+
+
+Gaming applications like Blocklords have processed over 80 million transactions across 1.8 million wallets using Base Appchains, achieving the scale needed for their gaming ecosystem without performance degradation.
+
+
+### Predictable, Cost-Effective Operations
+
+Replace unpredictable gas costs with **fixed monthly pricing**. Process transactions for fractions of cents while eliminating the need to sponsor gas costs for your users.
+
+
+
+Variable gas costs, expensive user onboarding, unpredictable operational expenses, and complex gas sponsorship management.
+
+
+
+Fixed monthly pricing, sub-cent transactions, predictable budgeting, and no gas sponsorship complexity.
+
+
+
+### Enterprise-Grade Infrastructure
+
+With Base Appchains, you get:
+
+
+Fully-managed sequencer and node infrastructure
+
+
+Automated maintenance and upgrades
+
+
+Real-time monitoring and performance alerts
+
+
+Dedicated block explorer for your chain
+
+
+### Seamless Base Ecosystem Integration
+
+Maintain access to Base's **users**, **liquidity**, and **developer tools** while getting dedicated performance. Your Appchain integrates seamlessly with Smart Wallet, Paymaster, OnchainKit, and other Base ecosystem tools.
+
+
+
+Enable seamless account abstraction across Base Mainnet and your Appchain with unified user experiences.
+
+
+
+Sponsor gas costs across multiple chains with unified billing and simplified user onboarding.
+
+
+
+Use the same familiar developer tools and components across the entire Base ecosystem.
+
+
+
+## Technical Architecture
+
+Base Appchains are built on the **OP Enclave framework**, providing fast withdrawals and seamless integration with Base Mainnet. This architecture enables near-instant bridging while maintaining security through innovative proving mechanisms.
+
+
+
+Built on Optimism's latest technology for **near-instant bridging** between your Appchain and Base Mainnet. Users can move funds in seconds rather than the typical 7-day withdrawal periods of traditional rollups.
+
+
+
+Uses **Amazon S3** for cost-efficient data storage while maintaining security through **AWS Nitro Enclave** verification. This approach significantly reduces costs while ensuring data integrity and availability.
+
+
+
+Control which contracts can be called on your chain, effectively managing blockspace allocation. Implement **custom gas tokens** and **permission systems** while protecting users from censorship through guaranteed deposit lanes.
+
+
+
+Unlike traditional rollups that rely on challenge periods, Base Appchains use **immediate state proving** through secure enclaves, enabling instant finality and faster user experiences.
+
+
+
+## Use Cases & Success Stories
+
+Base Appchains power applications across gaming, DeFi, and enterprise sectors that require high performance and predictable costs.
+
+
+
+Process millions of micro-transactions for in-game actions, NFT trades, and player interactions without network congestion affecting gameplay performance.
+
+**Success Story**: Super Champs chose Base Appchains for consistent throughput, comparing the experience to "gaming on iOS" - smooth, predictable, and reliable.
+
+
+
+Handle high-frequency trading, yield farming, and complex financial operations with consistent, low-cost transactions that don't fluctuate with network activity.
+
+**Success Story**: Applications processing high-volume trading data benefit from predictable costs and dedicated throughput for time-sensitive operations.
+
+
+
+Deploy compliance-ready solutions with dedicated infrastructure, custom permissions, and the ability to manage access controls while maintaining transparency.
+
+**Success Story**: Proof 8 uses blockchain technology for verifiable inventory ownership in warehouses and distilleries, where enterprise customers prioritize performance, security, and privacy.
+
+
+
+
+Base Appchains are designed for **mature projects** with significant transaction volumes. If you're just starting out or have low transaction volumes, consider building on Base Mainnet first to establish product-market fit.
+
+
+## When Should You Consider an Appchain?
+
+Base Appchains are ideal for applications that have outgrown shared blockspace limitations. Use this checklist to determine if an Appchain is right for your project:
+
+
+**High Transaction Volume**: Your app generates thousands of transactions daily and performance is affected by network congestion
+
+
+
+**Significant Gas Sponsorship**: You're spending substantial amounts sponsoring gas costs for users through Paymaster or similar solutions
+
+
+
+**Performance-Critical Operations**: User experience is negatively impacted by variable transaction times or network congestion
+
+
+
+**Custom Requirements**: You need custom gas tokens, specialized permissions, or governance mechanisms not available on shared chains
+
+
+
+**Predictable Costs**: Fixed operational costs are important for your business model and budgeting
+
+
+
+If you're considering launching your own L1 or L2 blockchain, Base Appchains offer a compelling alternative with faster time-to-market, proven infrastructure, and immediate access to Base's ecosystem.
+
+
+
+## Getting Started
+
+Base Appchains are currently in **beta with a waitlist**. We're working with select partners to refine the platform before broader availability.
+
+
+
+Complete our application form to be considered for early access to Base Appchains. We prioritize applications from mature projects with clear scaling needs.
+
+
+Join the Base Appchains beta program
+
+
+
+
+Our team will review your application and schedule a consultation to understand your specific scaling requirements, transaction patterns, and technical needs.
+
+
+During the consultation, we'll help you determine if an Appchain is the right solution and design the optimal configuration for your use case.
+
+
+
+
+Once approved, you'll receive access to both testnet and mainnet features. Start with the **$1/month testnet** to validate your architecture and integration.
+
+
+Use the testnet environment to test bridging, custom gas tokens, and permission systems before deploying to mainnet.
+
+
+
+
+Deploy to production with full enterprise support, monitoring, and maintenance included. Our team provides ongoing support for your Appchain infrastructure.
+
+
+Full technical support during launch and ongoing operations
+
+
+
+
+
+**Coming Soon**: Self-serve, one-click deployment will be available for approved projects, making it even easier to launch and manage your Appchain.
+
+
+## Frequently Asked Questions
+
+
+
+Base Appchains offer significant advantages over launching independent blockchain infrastructure:
+
+- **Faster time-to-market**: Deploy in weeks, not months or years
+- **Proven infrastructure**: Built on battle-tested Base and OP Stack technology
+- **Immediate ecosystem access**: Users and liquidity from Base Mainnet
+- **Lower operational overhead**: Fully managed infrastructure and maintenance
+- **Ethereum alignment**: Inherit security without custom validator sets or consensus mechanisms
+
+
+
+Base Appchains provide **seamless onboarding** similar to Base Mainnet applications:
+
+- Users can bridge funds between Base and your Appchain in **seconds**
+- Same wallet experience across Base ecosystem
+- Smart Wallet integration for account abstraction
+- Familiar transaction patterns and interfaces
+
+
+
+**Coinbase manages the core infrastructure** on your behalf, including:
+
+- Sequencer operation and maintenance
+- Node infrastructure and upgrades
+- Security key management
+- Monitoring and alerting systems
+
+You maintain control over **application-level configurations** like gas tokens, permissions, and governance while benefiting from enterprise-grade infrastructure management.
+
+
+
+Base Appchains use the **OP Enclave framework** for **near-instant bridging**:
+
+- Move funds between Base and your Appchain in seconds
+- No 7-day withdrawal periods like traditional rollups
+- Maintains security through cryptographic proofs
+- Seamless user experience across chains
+
+
+
+Base Appchains balance **operational efficiency** with **censorship resistance**:
+
+- Custom permissions control high-throughput operations
+- **Guaranteed deposit lanes** prevent censorship through direct Base deposits
+- Users always have recourse through the Base bridge
+- Inherits Ethereum's long-term decentralization roadmap
+
+
+
+## Ready to Scale?
+
+Base Appchains represent the next evolution in blockchain scaling, providing dedicated infrastructure without sacrificing ecosystem benefits. Whether you're processing millions of gaming transactions, handling high-frequency DeFi operations, or building enterprise solutions, Appchains deliver the performance and predictability your users expect.
+
+
+
+Apply for early access to Base Appchains beta program
+
+
+
+Discover the full ecosystem of Base developer tools and integrations
+
+
+
+
+**Next Steps**: After joining the waitlist, explore Base's developer documentation to understand how Appchains integrate with Smart Wallet, Paymaster, OnchainKit, and other ecosystem tools.
+
\ No newline at end of file
diff --git a/docs/cookbook/go-gasless.mdx b/docs/cookbook/go-gasless.mdx
new file mode 100644
index 00000000..9bd29ada
--- /dev/null
+++ b/docs/cookbook/go-gasless.mdx
@@ -0,0 +1,406 @@
+---
+sidebarTitle: Go Gasless
+title: 'Gasless Transactions on Base using a Paymaster'
+description: Learn how to leverage the Base Paymaster for seamless, gasless transactions on the Coinbase Cloud Developer Platform.
+---
+
+import { Danger } from "/snippets/danger.mdx";
+
+Base transaction fees are typically less than a penny, but the concept of gas can still be confusing for new users and lead to poor user experience when users don't have gas funds in their wallet. You can abstract this away and improve your UX by using the **Base Paymaster**. The Paymaster allows you to:
+
+- Batch multi-step transactions
+- Create custom gasless experiences
+- Sponsor up to $15k monthly on mainnet (unlimited on testnet)
+
+
+If you need an increase in your sponsorship limit, please [reach out on Discord][Discord]!
+
+
+
+## Objectives
+
+1. Configure security measures to ensure safe and reliable transactions.
+2. Manage and allocate resources for sponsored transactions.
+3. Subsidize transaction fees for users, enhancing the user experience by making transactions free.
+4. Set up and manage sponsored transactions on various schedules, including weekly, monthly, and daily cadences.
+
+## Prerequisites
+
+This tutorial assumes you have:
+
+1. **A Coinbase Cloud Developer Platform Account**
+ If not, sign up on the [CDP site]. Once you have your account, you can manage projects and utilize tools like the Paymaster.
+
+2. **Familiarity with Smart Accounts and ERC 4337**
+ Smart Accounts are the backbone of advanced transaction patterns (e.g., bundling, sponsorship). If you’re new to ERC 4337, check out external resources like the official [EIP-4337 explainer](https://eips.ethereum.org/EIPS/eip-4337) before starting.
+
+3. **Foundry**
+ Foundry is a development environment, testing framework, and smart contract toolkit for Ethereum. You’ll need it installed locally for generating key pairs and interacting with smart contracts.
+
+
+**Testnet vs. Mainnet**
+If you prefer not to spend real funds, you can switch to **Base Sepolia** (testnet). The steps below are conceptually the same. Just select _Base Sepolia_ in the Coinbase Developer Platform instead of _Base Mainnet_, and use a contract deployed on Base testnet for your allowlisted methods.
+
+
+
+## Set Up a Base Paymaster & Bundler
+
+In this section, you will configure a Paymaster to sponsor payments on behalf of a specific smart contract for a specified amount.
+
+1. **Navigate to the [Coinbase Developer Platform].**
+2. Create or select your project from the upper left corner of the screen.
+3. Click on the **Paymaster** tool from the left navigation.
+4. Go to the **Configuration** tab and copy the **RPC URL** to your clipboard — you’ll need this shortly in your code.
+
+### Screenshots
+
+- **Selecting your project**
+
+ 
+
+
+- **Navigating to the Paymaster tool**
+
+ 
+
+
+- **Configuration screen**
+
+ 
+
+
+### Allowlist a Sponsorable Contract
+
+1. From the Configuration page, ensure **Base Mainnet** (or **Base Sepolia** if you’re testing) is selected.
+2. Enable your paymaster by clicking the toggle button.
+3. Click **Add** to add an allowlisted contract.
+4. For this example, add [`0x83bd615eb93eE1336acA53e185b03B54fF4A17e8`][simple NFT contract], and add the function `mintTo(address)`.
+
+
+
+
+
+
+**Use your own contract**
+ We use a [simple NFT contract][simple NFT contract] on Base mainnet as an example. Feel free to substitute your own.
+
+
+
+### Global & Per User Limits
+
+Scroll down to the **Per User Limit** section. You can set:
+
+- **Dollar amount limit** or **number of UserOperations** per user
+- **Limit cycles** that reset daily, weekly, or monthly
+
+For example, you might set:
+
+- `max USD` to `$0.05`
+- `max UserOperation` to `1`
+
+This means **each user** can only have $0.05 in sponsored gas and **1** user operation before the cycle resets.
+
+
+**Limit Cycles**
+These reset based on the selected cadence (daily, weekly, monthly).
+
+
+
+Next, **set the Global Limit**. For example, set this to `$0.07` so that once the entire paymaster has sponsored \$0.07 worth of gas (across all users), no more sponsorship occurs unless you raise the limit.
+
+
+
+
+
+## Test Your Paymaster Policy
+
+Now let’s verify that these policies work. We’ll:
+
+1. Create two local key pairs (or use private keys you own).
+2. Generate two Smart Accounts.
+3. Attempt to sponsor multiple transactions to see your policy in action.
+
+### Installing Foundry
+
+1. Ensure you have **Rust** installed
+ ```bash
+ curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh
+ ```
+2. Install Foundry
+ ```bash
+ curl -L https://foundry.paradigm.xyz | bash
+ foundryup
+ ```
+3. Verify it works
+ ```bash
+ cast --help
+ ```
+ If you see Foundry usage info, you’re good to go!
+
+### Create Your Project & Generate Key Pairs
+
+1. Make a new folder and install dependencies, `viem` and `permissionless`:
+ ```bash
+ mkdir sponsored_transactions
+ cd sponsored_transactions
+ npm init es6
+ npm install permissionless
+ npm install viem
+ touch index.js
+ ```
+2. Generate two key pairs with Foundry:
+ ```bash
+ cast wallet new
+ cast wallet new
+ ```
+ You’ll see something like:
+ ```bash
+ Successfully created new keypair.
+ Address: 0xD440D746...
+ Private key: 0x01c9720c1dfa3c9...
+ ```
+ **Store these private keys somewhere safe**
+
+### Project Structure With Environment Variables
+
+Create a `.env` file in the `sponsored_transactions` directory. In the `.env`, you'll add the rpcURL for your paymaster and the private keys for your accounts:
+
+
+**Find your Paymaster & Bundler endpoint**
+
+The Paymaster & Bundler endpoint is the URL for your Coinbase Developer Platform (CDP) Paymaster.
+This was saved in the previous section and follows this format: `https://api.developer.coinbase.com/rpc/v1/base/`
+Navigate to the [Paymaster Tool] and select the `Configuration` tab at the top of the screen to obtain your RPC URL.
+
+
+
+
+**Secure your endpoints**
+
+You will create a constant for our Paymaster & Bundler endpoint obtained from cdp.portal.coinbase.com. The most secure way to do this is by using a proxy. For the purposes of this demo, hardcode it into our `index.js` file. For product, we highly recommend using a [proxy service].
+
+
+
+```bash
+PAYMASTER_RPC_URL=https://api.developer.coinbase.com/rpc/v1/base/
+PRIVATE_KEY_1=0x01c9720c1dfa3c9...
+PRIVATE_KEY_2=0xbcd6fbc1dfa3c9...
+```
+
+
+Never commit `.env` files to a public repo!
+
+
+
+## Example `index.js`
+
+Below is a full example of how you might structure `index.js`.
+
+```js index.js
+// --- index.js ---
+// @noErrors
+
+// 1. Import modules and environment variables
+import 'dotenv/config';
+import { http, createPublicClient, encodeFunctionData } from 'viem';
+import { base } from 'viem/chains';
+import { createSmartAccountClient } from 'permissionless';
+import { privateKeyToSimpleSmartAccount } from 'permissionless/accounts';
+import { createPimlicoPaymasterClient } from 'permissionless/clients/pimlico';
+
+// 2. Retrieve secrets from .env
+// Highlight: environment variables for paymaster, private keys
+const rpcUrl = process.env.PAYMASTER_RPC_URL; // highlight
+const firstPrivateKey = process.env.PRIVATE_KEY_1; // highlight
+const secondPrivateKey = process.env.PRIVATE_KEY_2; // highlight
+
+// 3. Declare Base addresses (entrypoint & factory)
+const baseEntryPoint = '0x5FF137D4b0FDCD49DcA30c7CF57E578a026d2789';
+const baseFactoryAddress = '0x15Ba39375ee2Ab563E8873C8390be6f2E2F50232';
+
+// 4. Create a public client for Base
+const publicClient = createPublicClient({
+ chain: base,
+ transport: http(rpcUrl),
+});
+
+// 5. Setup Paymaster client
+const cloudPaymaster = createPimlicoPaymasterClient({
+ chain: base,
+ transport: http(rpcUrl),
+ entryPoint: baseEntryPoint,
+});
+
+// 6. Create Smart Accounts from the private keys
+async function initSmartAccounts() {
+ const simpleAccount = await privateKeyToSimpleSmartAccount(publicClient, {
+ privateKey: firstPrivateKey,
+ factoryAddress: baseFactoryAddress,
+ entryPoint: baseEntryPoint,
+ });
+
+ const simpleAccount2 = await privateKeyToSimpleSmartAccount(publicClient, {
+ privateKey: secondPrivateKey,
+ factoryAddress: baseFactoryAddress,
+ entryPoint: baseEntryPoint,
+ });
+
+ // 7. Create SmartAccountClient for each
+ const smartAccountClient = createSmartAccountClient({
+ account: simpleAccount,
+ chain: base,
+ bundlerTransport: http(rpcUrl),
+ middleware: {
+ sponsorUserOperation: cloudPaymaster.sponsorUserOperation,
+ },
+ });
+
+ const smartAccountClient2 = createSmartAccountClient({
+ account: simpleAccount2,
+ chain: base,
+ bundlerTransport: http(rpcUrl),
+ middleware: {
+ sponsorUserOperation: cloudPaymaster.sponsorUserOperation,
+ },
+ });
+
+ return { smartAccountClient, smartAccountClient2 };
+}
+
+// 8. ABI for the NFT contract
+const nftAbi = [
+ // ...
+ // truncated for brevity
+];
+
+// 9. Example function to send a transaction from a given SmartAccountClient
+async function sendTransaction(client, recipientAddress) {
+ try {
+ // encode the "mintTo" function call
+ const callData = encodeFunctionData({
+ abi: nftAbi,
+ functionName: 'mintTo',
+ args: [recipientAddress], // highlight: specify who gets the minted NFT
+ });
+
+ const txHash = await client.sendTransaction({
+ account: client.account,
+ to: '0x83bd615eb93eE1336acA53e185b03B54fF4A17e8', // address of the NFT contract
+ data: callData,
+ value: 0n,
+ });
+
+ console.log(`✅ Transaction successfully sponsored for ${client.account.address}`);
+ console.log(`🔍 View on BaseScan: https://basescan.org/tx/${txHash}`);
+ } catch (error) {
+ console.error('Transaction failed:', error);
+ }
+}
+
+// 10. Main flow: init accounts, send transactions
+(async () => {
+ const { smartAccountClient, smartAccountClient2 } = await initSmartAccounts();
+
+ // Send a transaction from the first account
+ await sendTransaction(smartAccountClient, smartAccountClient.account.address);
+
+ // Send a transaction from the second account
+ // For variety, let’s also mint to the second account's own address
+ await sendTransaction(smartAccountClient2, smartAccountClient2.account.address);
+})();
+```
+
+Now that the code is implemented, lets run it:
+Run this via `node index.js` from your project root.
+
+```bash
+node index.js
+```
+
+You should see a "Transaction successfully sponsored" output.
+
+To confirm that your spend policies are correctly in place, try running the script again. If your Paymaster settings are strict (e.g., limit 1 transaction per user), the second time you run the script, you may get a “request denied” error, indicating the policy is working.
+
+## Hitting Policy Limits & Troubleshooting
+
+1. **Per-User Limit**
+ If you see an error like:
+
+ ```json
+ {
+ "code": -32001,
+ "message": "request denied - rejected due to maximum per address transaction count reached"
+ }
+ ```
+
+ That means you’ve hit your **UserOperation** limit for a single account. Return to the [Coinbase Developer Platform] UI to adjust the policy.
+
+2. **Global Limit**
+ If you repeatedly run transactions and eventually see:
+ ```json
+ {
+ "code": -32001,
+ "message": "request denied - rejected due to max global usd spend limit reached"
+ }
+ ```
+ You’ve hit the **global** limit of sponsored gas. Increase it in the CDP dashboard and wait a few minutes for changes to take effect.
+
+## Verifying Token Ownership (Optional)
+
+Want to confirm the token actually minted? You can read the NFT’s `balanceOf` function:
+
+```js
+import { readContract } from 'viem'; // highlight
+
+// example function
+async function checkNftBalance(publicClient, contractAddress, abi, ownerAddress) {
+ const balance = await publicClient.readContract({
+ address: contractAddress,
+ abi,
+ functionName: 'balanceOf',
+ args: [ownerAddress],
+ });
+ console.log(`NFT balance of ${ownerAddress} is now: ${balance}`);
+}
+```
+
+## Conclusion
+
+In this tutorial, you:
+
+- Set up and **configured** a Base Paymaster on the Coinbase Developer Platform.
+- **Allowlisted** a contract and specific function (`mintTo`) for sponsorship.
+- Established **per-user** and **global** sponsorship **limits** to control costs.
+- Demonstrated the **sponsorship flow** with Smart Accounts using `permissionless`, `viem`, and Foundry-generated private keys.
+
+This approach can greatly improve your dApp’s user experience by removing gas friction. For more complex sponsorship schemes (like daily or weekly cycles), simply tweak your per-user and global limit settings in the Coinbase Developer Platform.
+
+> **Next Steps**
+>
+> - Use a [proxy service][proxy service] for better endpoint security.
+> - Deploy your own contracts and allowlist them.
+> - Experiment with bundling multiple calls into a single sponsored transaction.
+
+## References
+
+- [list of factory addresses]
+- [Discord]
+- [CDP site]
+- [Coinbase Developer Platform]
+- [UI]
+- [proxy service]
+- [Paymaster Tool]
+- [Foundry Book installation guide]
+- [simple NFT contract]
+
+[list of factory addresses]: https://docs.alchemy.com/reference/factory-addresses
+[Discord]: https://discord.com/invite/cdp
+[CDP site]: https://portal.cdp.coinbase.com/
+[Coinbase Developer Platform]: https://portal.cdp.coinbase.com/
+[UI]: https://portal.cdp.coinbase.com/products/bundler-and-paymaster
+[proxy service]: https://www.smartwallet.dev/guides/paymasters
+[Paymaster Tool]: https://portal.cdp.coinbase.com/products/bundler-and-paymaster
+[Foundry Book installation guide]: https://book.getfoundry.sh/getting-started/installation
+[simple NFT contract]: https://basescan.org/token/0x83bd615eb93ee1336aca53e185b03b54ff4a17e8
+
+**Happy Building on Base!**
diff --git a/docs/cookbook/growth/cast-actions.mdx b/docs/cookbook/growth/cast-actions.mdx
new file mode 100644
index 00000000..a477eb2d
--- /dev/null
+++ b/docs/cookbook/growth/cast-actions.mdx
@@ -0,0 +1,6 @@
+---
+title: 'Cast Actions'
+description: 'Guide to implementing Cast Actions for growth'
+---
+
+[Guide for implementing and utilizing Cast Actions to grow your application]
\ No newline at end of file
diff --git a/docs/cookbook/growth/deploy-to-vercel.mdx b/docs/cookbook/growth/deploy-to-vercel.mdx
new file mode 100644
index 00000000..0e370596
--- /dev/null
+++ b/docs/cookbook/growth/deploy-to-vercel.mdx
@@ -0,0 +1,6 @@
+---
+title: 'Deploy to Vercel'
+description: 'Guide to deploying your application on Vercel'
+---
+
+[Step-by-step guide for deploying your Base application to Vercel]
\ No newline at end of file
diff --git a/docs/cookbook/growth/email-campaigns.mdx b/docs/cookbook/growth/email-campaigns.mdx
new file mode 100644
index 00000000..f3027cc6
--- /dev/null
+++ b/docs/cookbook/growth/email-campaigns.mdx
@@ -0,0 +1,6 @@
+---
+title: 'Email Campaigns'
+description: 'Set up and manage email campaigns'
+---
+
+[Guide for setting up and managing email campaigns for user engagement]
\ No newline at end of file
diff --git a/docs/cookbook/growth/gating-and-redirects.mdx b/docs/cookbook/growth/gating-and-redirects.mdx
new file mode 100644
index 00000000..10810c6f
--- /dev/null
+++ b/docs/cookbook/growth/gating-and-redirects.mdx
@@ -0,0 +1,6 @@
+---
+title: 'Gating and Redirects'
+description: 'Implement access control and redirects'
+---
+
+[Guide for implementing content gating and smart redirects in your application]
\ No newline at end of file
diff --git a/docs/cookbook/growth/hyperframes.mdx b/docs/cookbook/growth/hyperframes.mdx
new file mode 100644
index 00000000..54a83b21
--- /dev/null
+++ b/docs/cookbook/growth/hyperframes.mdx
@@ -0,0 +1,6 @@
+---
+title: 'Hyperframes'
+description: 'Implement Hyperframes for enhanced engagement'
+---
+
+[Guide for implementing Hyperframes to enhance user engagement and distribution]
\ No newline at end of file
diff --git a/docs/cookbook/growth/retaining-users.mdx b/docs/cookbook/growth/retaining-users.mdx
new file mode 100644
index 00000000..1a34fad4
--- /dev/null
+++ b/docs/cookbook/growth/retaining-users.mdx
@@ -0,0 +1,6 @@
+---
+title: 'Retaining Users'
+description: 'Strategies and implementations for user retention'
+---
+
+[Guide for implementing user retention strategies in your application]
\ No newline at end of file
diff --git a/docs/cookbook/launch-ai-agents.mdx b/docs/cookbook/launch-ai-agents.mdx
new file mode 100644
index 00000000..07a1cc93
--- /dev/null
+++ b/docs/cookbook/launch-ai-agents.mdx
@@ -0,0 +1,460 @@
+---
+title: 'Launch AI Agents on Base'
+description: 'Learn how to build and deploy autonomous AI agents on Base with access to stablecoins, tokens, NFTs, and onchain actions using CDP AgentKit.'
+---
+
+import LangChainReplitInstructions from '/snippets/ai-instructions/langchain-replit.mdx';
+import LangChainLocalInstructions from '/snippets/ai-instructions/langchain-local.mdx';
+import ElizaInstructions from '/snippets/ai-instructions/eliza.mdx';
+
+AI Agents become exponentially more powerful when they're onchain! By deploying AI agents on Base, you unlock access to **stablecoins**, **tokens**, **NFTs**, and a vast ecosystem of **DeFi protocols**. This significantly increases their autonomy and the universe of tasks they can perform, from automated trading to complex multi-step financial operations.
+
+## What You'll Build
+
+By the end of this guide, you'll have deployed a fully functional AI agent that can:
+
+- **Execute onchain transactions** autonomously
+- **Interact with DeFi protocols** for trading and liquidity
+- **Manage digital assets** including tokens and NFTs
+- **Respond to market conditions** with intelligent automation
+
+
+
+ Agents can execute transactions, trade tokens, and interact with smart contracts
+
+
+ Access to DEXs, lending protocols, and yield farming opportunities
+
+
+ Manage portfolios, NFT collections, and cross-chain assets
+
+
+ Real-time market analysis and automated trading strategies
+
+
+
+## Prerequisites
+
+Before launching your AI agent, ensure you have the following setup:
+
+
+
+ Choose your preferred development environment and ensure you have the necessary tools installed.
+
+ **For Local Development:**
+ - Node.js 18+ or Python 3.10+
+ - Git for repository management
+ - Code editor (VS Code recommended)
+
+ **For Replit (Browser-based):**
+ - Replit account for cloud development
+ - No local installation required
+
+
+ Replit is perfect for quick prototyping, while local development gives you more control and flexibility.
+
+
+
+
+ Gather the required API keys for your AI agent:
+
+ - **Coinbase Developer Platform (CDP) API Key**: [Get your CDP credentials](https://www.coinbase.com/cloud)
+ - **OpenAI API Key**: [Create an OpenAI account](https://platform.openai.com/api-keys) for AI capabilities
+ - **Base Network Access**: Your agent will operate on Base Sepolia testnet initially
+
+
+ Store all API keys securely and never commit them to version control. Use environment variables for all sensitive credentials.
+
+
+
+
+ Choose the framework that best fits your needs:
+
+ - **LangChain**: Full-featured framework with extensive integrations
+ - **Eliza**: Lightweight, fast setup for simple agents
+
+
+ Each framework has different strengths. LangChain offers more customization, while Eliza provides rapid deployment.
+
+
+
+
+## Choose Your Agent Framework
+
+Select the framework and environment that best matches your development preferences and project requirements:
+
+
+
+ **LangChain** provides a comprehensive framework for building sophisticated AI agents with extensive tooling and integrations.
+
+
+ **Best for:** Complex agents requiring custom tools, advanced reasoning, and extensive integrations with external services.
+
+
+ ### Development Environment
+
+
+
+ Perfect for getting started quickly without local setup requirements.
+
+
+ **Replit Advantages:**
+ - No local environment setup required
+ - Built-in collaboration features
+ - Automatic deployment and hosting
+ - Great for learning and prototyping
+
+
+
+
+ Recommended for production applications and advanced customization.
+
+
+ **Local Development Advantages:**
+ - Full control over your environment
+ - Better performance for intensive operations
+ - Easier integration with existing toolchains
+ - Enhanced security for production applications
+
+
+
+
+ ### Advanced LangChain Features
+
+ Once your basic agent is running, you can enhance it with:
+
+
+
+ ```python
+ # Example: Custom DeFi interaction tool
+ from cdp_langchain.tools import CdpTool
+
+ class CustomDeFiTool(CdpTool):
+ def __init__(self):
+ super().__init__(
+ name="defi_analyzer",
+ description="Analyze DeFi opportunities on Base"
+ )
+ ```
+
+
+
+ ```python
+ # Add memory to your agent
+ from langchain.memory import ConversationBufferWindowMemory
+
+ memory = ConversationBufferWindowMemory(
+ k=10, # Remember last 10 interactions
+ return_messages=True
+ )
+ ```
+
+
+
+ ```python
+ # Coordinate multiple specialized agents
+ trading_agent = create_trading_agent()
+ portfolio_agent = create_portfolio_agent()
+
+ # Orchestrate agents for complex strategies
+ coordinator = AgentCoordinator([trading_agent, portfolio_agent])
+ ```
+
+
+
+
+
+ **Eliza** offers the fastest path to deploying AI agents with minimal configuration and maximum speed.
+
+
+ **Best for:** Quick deployments, simple autonomous agents, and rapid prototyping with immediate results.
+
+
+
+
+ Get your agent running in under 5 minutes with the CLI tool
+
+
+ Pre-configured templates for common agent patterns
+
+
+ Native support for popular onchain actions and APIs
+
+
+ Access to pre-built agent templates from the community
+
+
+
+ ### Extending Your Eliza Agent
+
+
+
+ Extend your agent's capabilities by adding custom onchain actions:
+
+ ```typescript
+ // Add to your agent's action registry
+ export const customActions = [
+ {
+ name: "YIELD_FARM",
+ description: "Automatically farm yield on Base protocols",
+ handler: async (params) => {
+ // Your yield farming logic
+ }
+ }
+ ];
+ ```
+
+
+
+ Implement automated trading strategies:
+
+ ```typescript
+ export const tradingConfig = {
+ strategies: ["DCA", "MOMENTUM", "ARBITRAGE"],
+ riskLevel: "MODERATE",
+ maxSlippage: 0.01
+ };
+ ```
+
+
+
+ Add monitoring and alerts for your agent:
+
+ ```typescript
+ export const monitoringConfig = {
+ alerts: {
+ lowBalance: true,
+ failedTx: true,
+ profitTarget: 0.05
+ }
+ };
+ ```
+
+
+
+
+
+## Testing Your AI Agent
+
+Before deploying to mainnet, thoroughly test your agent's capabilities:
+
+
+
+ **Test all functions on Base Sepolia testnet:**
+
+ 1. **Wallet Operations**: Create wallets, check balances, transfer tokens
+ 2. **DeFi Interactions**: Test swaps, liquidity provision, lending
+ 3. **NFT Operations**: Mint, transfer, and trade NFTs
+ 4. **Error Handling**: Ensure graceful handling of failed transactions
+
+
+ Your agent should handle all basic operations without errors before proceeding.
+
+
+
+
+ **Evaluate agent performance under various conditions:**
+
+ - Response time to market changes
+ - Transaction success rates
+ - Gas optimization effectiveness
+ - Resource utilization
+
+
+ Monitor your agent's performance metrics to identify optimization opportunities.
+
+
+
+
+ **Verify security measures are in place:**
+
+ - API keys are properly secured
+ - Wallet private keys are encrypted
+ - Rate limiting is implemented
+ - Transaction limits are configured
+
+
+ Never deploy to mainnet without proper security auditing. Consider professional security reviews for high-value operations.
+
+
+
+
+## Deployment and Monitoring
+
+
+
+ **Deploy your agent to a production environment:**
+
+
+
+ ```bash
+ # Deploy to cloud provider
+ npm run build
+ npm run deploy:production
+
+ # Set production environment variables
+ export CDP_API_KEY_NAME="your_production_key"
+ export NETWORK_ID="base-mainnet"
+ ```
+
+
+
+ ```bash
+ # Set up production server
+ pm2 start ecosystem.config.js
+ pm2 startup
+ pm2 save
+
+ # Configure monitoring
+ pm2 install pm2-logrotate
+ ```
+
+
+
+
+ Ensure your deployment includes proper logging, monitoring, and backup systems.
+
+
+
+
+ **Set up comprehensive monitoring:**
+
+ - **Transaction Monitoring**: Track success rates and gas usage
+ - **Performance Metrics**: Monitor response times and throughput
+ - **Financial Tracking**: Watch portfolio performance and P&L
+ - **System Health**: Monitor server resources and uptime
+
+
+ Use tools like Grafana, DataDog, or custom dashboards to visualize your agent's performance.
+
+
+
+
+## Troubleshooting
+
+
+
+ **Common solutions:**
+ - Check API key validity and permissions
+ - Verify network connectivity to Base RPC endpoints
+ - Ensure sufficient gas funds in agent wallet
+ - Review agent logs for error messages
+ - Confirm OpenAI API quota and rate limits
+
+
+
+ **Debug transaction issues:**
+ - Verify sufficient token balance for operations
+ - Check gas price settings and network congestion
+ - Confirm smart contract addresses are correct
+ - Review transaction simulation results
+ - Validate slippage tolerance settings
+
+
+
+ **Optimize agent performance:**
+ - Implement request batching for multiple operations
+ - Use connection pooling for database operations
+ - Cache frequently accessed data
+ - Optimize trading frequency to reduce gas costs
+ - Review and tune AI model parameters
+
+
+
+ **Enhance security measures:**
+ - Rotate API keys regularly
+ - Implement transaction signing verification
+ - Set up multi-signature requirements for large transactions
+ - Enable wallet spending limits
+ - Monitor for unusual activity patterns
+
+
+
+## Advanced Use Cases
+
+Explore advanced patterns for sophisticated AI agents:
+
+
+
+ Build agents that identify and execute arbitrage opportunities across DEXs
+
+
+ Create agents that rebalance portfolios based on market conditions
+
+
+ Deploy agents that automatically find and compound the best yields
+
+
+ Develop agents that analyze and trade NFTs based on market trends
+
+
+
+## Next Steps
+
+Expand your AI agent's capabilities:
+
+
+
+ Connect your agent to more DeFi protocols:
+ - **Uniswap** for advanced trading strategies
+ - **Aave** for lending and borrowing
+ - **Compound** for yield generation
+ - **1inch** for optimal trade routing
+
+
+
+ Build sophisticated trading and management strategies:
+ - Dollar-cost averaging (DCA) algorithms
+ - Mean reversion trading
+ - Momentum-based strategies
+ - Risk-adjusted portfolio rebalancing
+
+
+
+ Extend your agent across multiple chains:
+ - **Ethereum** for additional DeFi access
+ - **Polygon** for low-cost operations
+ - **Arbitrum** for advanced trading
+ - Cross-chain bridging automation
+
+
+
+## Resources and Community
+
+
+
+ Complete documentation for building agents with CDP
+
+
+ Connect with other developers building AI agents on Base
+
+
+ Access source code, examples, and contribute to the project
+
+
+ Watch step-by-step tutorials for agent development
+
+
+
+## Conclusion
+
+Congratulations! You've successfully launched an AI agent on Base with full onchain capabilities. Your agent can now:
+
+✅ **Execute autonomous transactions** with real-world financial impact
+✅ **Interact with DeFi protocols** for advanced financial operations
+✅ **Manage digital assets** including tokens and NFTs
+✅ **Respond intelligently** to market conditions and opportunities
+
+**Ready for production?** Consider implementing advanced monitoring, security audits, and gradual scaling as your agent proves its effectiveness in live markets.
+
+
+Your AI agent is now part of the onchain economy, ready to operate 24/7 in the world of decentralized finance. Happy building on Base!
+
diff --git a/docs/cookbook/launch-tokens.mdx b/docs/cookbook/launch-tokens.mdx
new file mode 100644
index 00000000..aa3402cd
--- /dev/null
+++ b/docs/cookbook/launch-tokens.mdx
@@ -0,0 +1,423 @@
+---
+title: 'Launch a Token'
+---
+
+
+Launching a token on Base can be accomplished through multiple approaches, from no-code platforms to custom smart contract development. This guide helps you choose the right method and provides implementation details for both approaches.
+
+
+
+ Use existing platforms like Zora, Clanker, or Flaunch for quick deployment
+
+
+ Build custom ERC-20 tokens with Foundry for maximum control
+
+
+ Decision framework to help you pick the right method
+
+
+ Security, community building, and post-launch guidance
+
+
+
+
+**For most users:** Use existing token launch platforms like Zora, Clanker, or Flaunch. These tools handle the technical complexity while providing unique features for different use cases.
+
+**For developers:** Build custom ERC-20 tokens using Foundry and OpenZeppelin's battle-tested contracts for maximum control and customization.
+
+
+## Choosing Your Launch Approach
+
+### Platform-Based Launch (Recommended for Most Users)
+
+Choose a platform when you want:
+- Quick deployment without coding
+- Built-in community features
+- Automated liquidity management
+- Social integration capabilities
+
+### Custom Development (For Developers)
+
+Build your own smart contract when you need:
+- Custom tokenomics or functionality
+- Full control over contract behavior
+- Integration with existing systems
+- Advanced security requirements
+
+## Token Launch Platforms on Base
+
+### Zora
+**Best for:** Content creators and social tokens
+
+Zora transforms every post into a tradeable ERC-20 token with automatic Uniswap integration. Each post becomes a "coin" with 1 billion supply, creators receive 10 million tokens, and earn 1% of all trading fees.
+
+**Key Features:**
+- Social-first token creation
+- Automatic liquidity pools
+- Revenue sharing for creators
+- Built-in trading interface
+
+[Get started with Zora →](https://zora.co)
+
+### Clanker
+**Best for:** Quick memecoin launches via social media
+
+Clanker is an AI-driven token deployment tool that operates through Farcaster. Users can create ERC-20 tokens on Base by simply tagging @clanker with their token concept.
+
+**Key Features:**
+- AI-powered automation
+- Social media integration via Farcaster
+- Instant deployment
+- Community-driven discovery
+
+[Get started with Clanker →](https://warpcast.com) or visit [clanker.world](https://clanker.world)
+
+### Flaunch
+**Best for:** Advanced memecoin projects with sophisticated tokenomics
+
+Flaunch leverages Uniswap V4 to enable programmable revenue splits, automated buybacks, and Progressive Bid Walls for price support. Creators can customize fee distributions and treasury management.
+
+**Key Features:**
+- Programmable revenue sharing
+- Automated buyback mechanisms
+- Progressive Bid Wall technology
+- Treasury management tools
+
+[Get started with Flaunch →](https://flaunch.gg)
+
+## Technical Implementation with Foundry
+
+For developers who want full control over their token implementation, here's how to create and deploy a custom ERC-20 token on Base using Foundry.
+
+
+Before launching a custom developed token to production, always conduct security reviews by expert smart contract developers.
+
+
+### Prerequisites
+
+
+
+ Install Foundry on your system:
+ ```bash Terminal
+ curl -L https://foundry.paradigm.xyz | bash
+ foundryup
+ ```
+ For detailed installation instructions, see the [Foundry documentation](https://book.getfoundry.sh/getting-started/installation).
+
+
+ Obtain Base Sepolia ETH for testing from the [Base Faucet](https://docs.base.org/docs/tools/network-faucets)
+
+
+ Configure your wallet and development tools for Base testnet deployment
+
+
+
+### Project Setup
+
+Initialize a new Foundry project and clean up template files:
+
+```bash Terminal
+# Create new project
+forge init my-token-project
+cd my-token-project
+
+# Remove template files we don't need
+rm src/Counter.sol script/Counter.s.sol test/Counter.t.sol
+```
+
+Install OpenZeppelin contracts for secure, audited ERC-20 implementation:
+
+```bash Terminal
+# Install OpenZeppelin contracts library
+forge install OpenZeppelin/openzeppelin-contracts
+```
+
+### Smart Contract Development
+
+Create your token contract using OpenZeppelin's ERC-20 implementation:
+
+```solidity src/MyToken.sol
+// SPDX-License-Identifier: MIT
+pragma solidity ^0.8.19;
+
+import "@openzeppelin/contracts/token/ERC20/ERC20.sol";
+import "@openzeppelin/contracts/access/Ownable.sol";
+
+/**
+ * @title MyToken
+ * @dev ERC-20 token with minting capabilities and supply cap
+ */
+contract MyToken is ERC20, Ownable {
+ // Maximum number of tokens that can ever exist
+ uint256 public constant MAX_SUPPLY = 1_000_000_000 * 10**18; // 1 billion tokens
+
+ constructor(
+ string memory name,
+ string memory symbol,
+ uint256 initialSupply,
+ address initialOwner
+ ) ERC20(name, symbol) Ownable(initialOwner) {
+ require(initialSupply <= MAX_SUPPLY, "Initial supply exceeds max supply");
+ // Mint initial supply to the contract deployer
+ _mint(initialOwner, initialSupply);
+ }
+
+ /**
+ * @dev Mint new tokens (only contract owner can call this)
+ * @param to Address to mint tokens to
+ * @param amount Amount of tokens to mint
+ */
+ function mint(address to, uint256 amount) public onlyOwner {
+ require(totalSupply() + amount <= MAX_SUPPLY, "Minting would exceed max supply");
+ _mint(to, amount);
+ }
+
+ /**
+ * @dev Burn tokens from caller's balance
+ * @param amount Amount of tokens to burn
+ */
+ function burn(uint256 amount) public {
+ _burn(msg.sender, amount);
+ }
+}
+```
+
+### Deployment Script
+
+Create a deployment script following Foundry best practices:
+
+```solidity script/DeployToken.s.sol
+// SPDX-License-Identifier: MIT
+pragma solidity ^0.8.19;
+
+import {Script, console} from "forge-std/Script.sol";
+import {MyToken} from "../src/MyToken.sol";
+
+contract DeployToken is Script {
+ function run() external {
+ // Load deployer's private key from environment variables
+ uint256 deployerPrivateKey = vm.envUint("PRIVATE_KEY");
+ address deployerAddress = vm.addr(deployerPrivateKey);
+
+ // Token configuration parameters
+ string memory name = "My Token";
+ string memory symbol = "MTK";
+ uint256 initialSupply = 100_000_000 * 10**18; // 100 million tokens
+
+ // Start broadcasting transactions
+ vm.startBroadcast(deployerPrivateKey);
+
+ // Deploy the token contract
+ MyToken token = new MyToken(
+ name,
+ symbol,
+ initialSupply,
+ deployerAddress
+ );
+
+ // Stop broadcasting transactions
+ vm.stopBroadcast();
+
+ // Log deployment information
+ console.log("Token deployed to:", address(token));
+ console.log("Token name:", token.name());
+ console.log("Token symbol:", token.symbol());
+ console.log("Initial supply:", token.totalSupply());
+ console.log("Deployer balance:", token.balanceOf(deployerAddress));
+ }
+}
+```
+
+### Environment Configuration
+
+Create a `.env` file with your configuration:
+
+```bash .env
+PRIVATE_KEY=your_private_key_here
+BASE_SEPOLIA_RPC_URL=https://sepolia.base.org
+BASE_MAINNET_RPC_URL=https://mainnet.base.org
+BASESCAN_API_KEY=your_basescan_api_key_here
+```
+
+Update `foundry.toml` for Base network configuration:
+
+```toml foundry.toml
+[profile.default]
+src = "src"
+out = "out"
+libs = ["lib"]
+remappings = ["@openzeppelin/=lib/openzeppelin-contracts/"]
+
+[rpc_endpoints]
+base_sepolia = "${BASE_SEPOLIA_RPC_URL}"
+base_mainnet = "${BASE_MAINNET_RPC_URL}"
+
+[etherscan]
+base_sepolia = { key = "${BASESCAN_API_KEY}", url = "https://api-sepolia.basescan.org/api" }
+base = { key = "${BASESCAN_API_KEY}", url = "https://api.basescan.org/api" }
+```
+
+### Testing
+
+Create comprehensive tests for your token:
+
+```solidity test/MyToken.t.sol
+// SPDX-License-Identifier: MIT
+pragma solidity ^0.8.19;
+
+import {Test, console} from "forge-std/Test.sol";
+import {MyToken} from "../src/MyToken.sol";
+
+contract MyTokenTest is Test {
+ MyToken public token;
+ address public owner = address(0x1);
+ address public user = address(0x2);
+
+ uint256 constant INITIAL_SUPPLY = 100_000_000 * 10**18;
+
+ function setUp() public {
+ // Deploy token contract before each test
+ vm.prank(owner);
+ token = new MyToken("Test Token", "TEST", INITIAL_SUPPLY, owner);
+ }
+
+ function testInitialState() public {
+ // Verify token was deployed with correct parameters
+ assertEq(token.name(), "Test Token");
+ assertEq(token.symbol(), "TEST");
+ assertEq(token.totalSupply(), INITIAL_SUPPLY);
+ assertEq(token.balanceOf(owner), INITIAL_SUPPLY);
+ }
+
+ function testMinting() public {
+ uint256 mintAmount = 1000 * 10**18;
+
+ // Only owner should be able to mint
+ vm.prank(owner);
+ token.mint(user, mintAmount);
+
+ assertEq(token.balanceOf(user), mintAmount);
+ assertEq(token.totalSupply(), INITIAL_SUPPLY + mintAmount);
+ }
+
+ function testBurning() public {
+ uint256 burnAmount = 1000 * 10**18;
+
+ // Owner burns their own tokens
+ vm.prank(owner);
+ token.burn(burnAmount);
+
+ assertEq(token.balanceOf(owner), INITIAL_SUPPLY - burnAmount);
+ assertEq(token.totalSupply(), INITIAL_SUPPLY - burnAmount);
+ }
+
+ function testFailMintExceedsMaxSupply() public {
+ // This test should fail when trying to mint more than max supply
+ uint256 excessiveAmount = token.MAX_SUPPLY() + 1;
+
+ vm.prank(owner);
+ token.mint(user, excessiveAmount);
+ }
+
+ function testFailUnauthorizedMinting() public {
+ // This test should fail when non-owner tries to mint
+ vm.prank(user);
+ token.mint(user, 1000 * 10**18);
+ }
+}
+```
+
+Run your tests:
+
+```bash Terminal
+# Run all tests with verbose output
+forge test -vv
+```
+
+### Deployment and Verification
+
+Deploy to Base Sepolia testnet:
+
+```bash Terminal
+# Load environment variables
+source .env
+
+# Deploy to Base Sepolia with automatic verification
+forge script script/DeployToken.s.sol:DeployToken \
+ --rpc-url base_sepolia \
+ --broadcast \
+ --verify
+```
+
+
+The `--verify` flag automatically verifies your contract on BaseScan, making it easier for users to interact with your token.
+
+
+
+To deploy to Base Mainnet, simply change `base_sepolia` to `base_mainnet` in your deployment command. Ensure you have sufficient ETH on Base Mainnet for deployment and gas fees.
+
+
+## Post-Launch Considerations
+
+Once your token is deployed, here are the key next steps to consider:
+
+### Token Distribution and Economics
+
+Carefully consider your token's supply and distribution settings. Think through how tokens will be distributed to your community, team, and ecosystem participants. Consider factors like vesting schedules, allocation percentages, and long-term incentive alignment.
+
+### Community and Social Presence
+
+Establish a community and social presence around your token and project. This includes creating documentation, setting up social media accounts, engaging with the Base ecosystem, and building relationships with other projects and developers.
+
+### Liquidity and Trading
+
+Add liquidity to decentralized exchanges like Uniswap to enable trading. Note that token launchers will typically handle this for you automatically, but for custom deployments, you'll need to create trading pairs and provide initial liquidity.
+
+### Continued Development
+
+For comprehensive guidance on growing your project on Base, including marketing strategies, ecosystem integration, and growth tactics, visit the [Base Launch Playbook](https://www.launchonbase.xyz/).
+
+
+Remember to always prioritize security, transparency, and community value when developing and launching tokens. Consider conducting security audits and following best practices for token distribution.
+
+
+## Resources
+
+
+
+ Complete guide to getting started on Base
+
+
+ Technical specifications and network information
+
+
+ Comprehensive guide to using Foundry
+
+
+ Security-focused smart contract library
+
+
+ Explore transactions and contracts on Base
+
+
+ Get testnet ETH for development
+
+
+
+### Community
+
+
+
+ Join the Base community
+
+
+ Follow Base updates
+
+
+ Contribute to Base development
+
+
+
+---
+
+Whether you choose a platform-based approach for speed and convenience, or custom development for maximum control, Base provides a robust foundation for token launches. Start with the approach that best fits your technical expertise and project requirements, and leverage Base's growing ecosystem to build successful token projects.
\ No newline at end of file
diff --git a/docs/cookbook/nfts/complex-onchain-nfts.mdx b/docs/cookbook/nfts/complex-onchain-nfts.mdx
new file mode 100644
index 00000000..87e582e1
--- /dev/null
+++ b/docs/cookbook/nfts/complex-onchain-nfts.mdx
@@ -0,0 +1,6 @@
+---
+title: 'Complex Onchain NFTs'
+description: 'Create advanced onchain NFTs'
+---
+
+[Guide for creating complex onchain NFTs with advanced features]
\ No newline at end of file
diff --git a/docs/cookbook/nfts/dynamic-nfts.mdx b/docs/cookbook/nfts/dynamic-nfts.mdx
new file mode 100644
index 00000000..ae65005a
--- /dev/null
+++ b/docs/cookbook/nfts/dynamic-nfts.mdx
@@ -0,0 +1,6 @@
+---
+title: 'Dynamic NFTs'
+description: 'Create NFTs with dynamic properties'
+---
+
+[Guide for creating dynamic NFTs that can change over time]
\ No newline at end of file
diff --git a/docs/cookbook/nfts/nft-minting-zora.mdx b/docs/cookbook/nfts/nft-minting-zora.mdx
new file mode 100644
index 00000000..6d35f221
--- /dev/null
+++ b/docs/cookbook/nfts/nft-minting-zora.mdx
@@ -0,0 +1,6 @@
+---
+title: 'NFT Minting with Zora'
+description: 'Guide to minting NFTs using Zora protocol'
+---
+
+[Guide for minting NFTs using the Zora protocol on Base]
\ No newline at end of file
diff --git a/docs/cookbook/nfts/signature-mint.mdx b/docs/cookbook/nfts/signature-mint.mdx
new file mode 100644
index 00000000..c293c7ed
--- /dev/null
+++ b/docs/cookbook/nfts/signature-mint.mdx
@@ -0,0 +1,6 @@
+---
+title: 'Signature Mint'
+description: 'Implement signature-based NFT minting'
+---
+
+[Guide for implementing signature-based NFT minting]
\ No newline at end of file
diff --git a/docs/cookbook/nfts/simple-onchain-nfts.mdx b/docs/cookbook/nfts/simple-onchain-nfts.mdx
new file mode 100644
index 00000000..252a6b4f
--- /dev/null
+++ b/docs/cookbook/nfts/simple-onchain-nfts.mdx
@@ -0,0 +1,619 @@
+---
+title: Simple Onchain NFTs
+sidebarTitle: Simple NFTs
+description: 'Create basic NFT collections with metadata stored fully onchain for permanence and decentralization'
+---
+
+Build NFT collections where all metadata lives onchain for true decentralization and permanence. This approach ensures your NFTs remain accessible forever, regardless of external hosting or IPFS availability.
+
+
+
+ Understand the advantages of storing metadata onchain
+
+
+ Deploy your onchain NFT contract
+
+
+ Structure your onchain metadata properly
+
+
+ Create a user-friendly minting experience
+
+
+
+## Why Onchain Metadata?
+
+Traditional NFTs store metadata on centralized servers or IPFS, creating potential points of failure. Onchain metadata ensures true permanence and decentralization.
+
+
+**Onchain vs Offchain Comparison**
+
+- **Onchain**: Metadata stored in smart contract, permanent, higher gas costs
+- **Offchain**: Metadata on IPFS/servers, lower gas costs, potential availability issues
+- **Hybrid**: Critical data onchain, detailed media offchain
+
+
+### Benefits of Onchain NFTs
+
+
+**Permanent Access**: Metadata exists as long as the blockchain exists
+
+
+**True Decentralization**: No reliance on external hosting services
+
+
+**Composability**: Other contracts can easily read and use metadata
+
+
+**Transparency**: All data is publicly verifiable onchain
+
+
+## Prerequisites
+
+Before building your onchain NFT collection:
+
+
+Understanding of Solidity and smart contract development
+
+
+Foundry or Hardhat development environment
+
+
+Base testnet ETH for deployment testing
+
+
+Basic knowledge of JSON and Base64 encoding
+
+
+## Smart Contract Implementation
+
+### Basic Onchain NFT Contract
+
+Here's a foundational contract that stores all metadata onchain:
+
+```solidity contracts/SimpleOnchainNFT.sol
+// SPDX-License-Identifier: MIT
+pragma solidity ^0.8.19;
+
+import "@openzeppelin/contracts/token/ERC721/ERC721.sol";
+import "@openzeppelin/contracts/access/Ownable.sol";
+import "@openzeppelin/contracts/utils/Strings.sol";
+import "@openzeppelin/contracts/utils/Base64.sol";
+
+contract SimpleOnchainNFT is ERC721, Ownable {
+ using Strings for uint256;
+
+ uint256 private _tokenIdCounter;
+ mapping(uint256 => NFTMetadata) private _tokenMetadata;
+
+ struct NFTMetadata {
+ string name;
+ string description;
+ string image; // Can be SVG data or onchain-generated art
+ string[] attributes;
+ }
+
+ event NFTMinted(address indexed to, uint256 indexed tokenId, string name);
+
+ constructor(address initialOwner)
+ ERC721("Simple Onchain NFT", "SONFT")
+ Ownable(initialOwner)
+ {}
+
+ function mint(
+ address to,
+ string memory name,
+ string memory description,
+ string memory image,
+ string[] memory attributes
+ ) public onlyOwner {
+ uint256 tokenId = _tokenIdCounter++;
+
+ _tokenMetadata[tokenId] = NFTMetadata({
+ name: name,
+ description: description,
+ image: image,
+ attributes: attributes
+ });
+
+ _safeMint(to, tokenId);
+ emit NFTMinted(to, tokenId, name);
+ }
+
+ function tokenURI(uint256 tokenId)
+ public
+ view
+ override
+ returns (string memory)
+ {
+ require(_exists(tokenId), "Token does not exist");
+
+ NFTMetadata memory metadata = _tokenMetadata[tokenId];
+
+ // Build JSON metadata
+ bytes memory json = abi.encodePacked(
+ '{"name":"', metadata.name,
+ '","description":"', metadata.description,
+ '","image":"', metadata.image,
+ '","attributes":[', _buildAttributes(metadata.attributes),
+ ']}'
+ );
+
+ // Encode as base64 data URI
+ return string(
+ abi.encodePacked(
+ "data:application/json;base64,",
+ Base64.encode(json)
+ )
+ );
+ }
+
+ function _buildAttributes(string[] memory attributes)
+ private
+ pure
+ returns (string memory)
+ {
+ if (attributes.length == 0) return "";
+
+ bytes memory result;
+ for (uint256 i = 0; i < attributes.length; i += 2) {
+ if (i > 0) result = abi.encodePacked(result, ",");
+
+ if (i + 1 < attributes.length) {
+ result = abi.encodePacked(
+ result,
+ '{"trait_type":"', attributes[i],
+ '","value":"', attributes[i + 1], '"}'
+ );
+ }
+ }
+ return string(result);
+ }
+
+ function getMetadata(uint256 tokenId)
+ public
+ view
+ returns (NFTMetadata memory)
+ {
+ require(_exists(tokenId), "Token does not exist");
+ return _tokenMetadata[tokenId];
+ }
+
+ function totalSupply() public view returns (uint256) {
+ return _tokenIdCounter;
+ }
+}
+```
+
+### Generative Art Contract
+
+For purely generative onchain art:
+
+```solidity contracts/GenerativeOnchainNFT.sol
+// SPDX-License-Identifier: MIT
+pragma solidity ^0.8.19;
+
+import "@openzeppelin/contracts/token/ERC721/ERC721.sol";
+import "@openzeppelin/contracts/access/Ownable.sol";
+import "@openzeppelin/contracts/utils/Strings.sol";
+import "@openzeppelin/contracts/utils/Base64.sol";
+
+contract GenerativeOnchainNFT is ERC721, Ownable {
+ using Strings for uint256;
+
+ uint256 private _tokenIdCounter;
+ uint256 public constant MAX_SUPPLY = 1000;
+ uint256 public constant MINT_PRICE = 0.01 ether;
+
+ // Colors for generative art
+ string[] private colors = ["red", "blue", "green", "purple", "orange", "yellow"];
+ string[] private shapes = ["circle", "square", "triangle", "diamond"];
+
+ constructor(address initialOwner)
+ ERC721("Generative Onchain Art", "GOA")
+ Ownable(initialOwner)
+ {}
+
+ function mint() public payable {
+ require(_tokenIdCounter < MAX_SUPPLY, "Max supply reached");
+ require(msg.value >= MINT_PRICE, "Insufficient payment");
+
+ uint256 tokenId = _tokenIdCounter++;
+ _safeMint(msg.sender, tokenId);
+ }
+
+ function tokenURI(uint256 tokenId)
+ public
+ view
+ override
+ returns (string memory)
+ {
+ require(_exists(tokenId), "Token does not exist");
+
+ // Generate deterministic traits based on tokenId
+ uint256 seed = uint256(keccak256(abi.encodePacked(tokenId, block.timestamp)));
+
+ string memory color = colors[seed % colors.length];
+ string memory shape = shapes[(seed >> 8) % shapes.length];
+ uint256 size = (seed % 100) + 50; // Size between 50-149
+
+ // Generate SVG
+ string memory svg = generateSVG(tokenId, color, shape, size);
+
+ // Build metadata JSON
+ bytes memory json = abi.encodePacked(
+ '{"name":"Generative Art #', tokenId.toString(),
+ '","description":"Fully onchain generative art",',
+ '"image":"data:image/svg+xml;base64,', Base64.encode(bytes(svg)),
+ '","attributes":[',
+ '{"trait_type":"Color","value":"', color, '"},',
+ '{"trait_type":"Shape","value":"', shape, '"},',
+ '{"trait_type":"Size","value":', size.toString(), '}',
+ ']}'
+ );
+
+ return string(
+ abi.encodePacked(
+ "data:application/json;base64,",
+ Base64.encode(json)
+ )
+ );
+ }
+
+ function generateSVG(
+ uint256 tokenId,
+ string memory color,
+ string memory shape,
+ uint256 size
+ ) private pure returns (string memory) {
+ string memory shapeElement;
+
+ if (keccak256(bytes(shape)) == keccak256(bytes("circle"))) {
+ shapeElement = string(
+ abi.encodePacked(
+ '',
+ text,
+ ' '
+ )
+ );
+ }
+
+ function wrapSVG(string memory content)
+ internal
+ pure
+ returns (string memory)
+ {
+ return string(
+ abi.encodePacked(
+ ''
+ )
+ );
+ }
+}
+```
+
+## Building Mint Interface
+
+### Next.js Minting App
+
+Create a user-friendly interface for minting:
+
+```typescript app/mint/page.tsx
+'use client'
+
+import { useState } from 'react'
+import { useAccount, useWriteContract, useWaitForTransactionReceipt } from 'wagmi'
+import { parseEther } from 'viem'
+
+const CONTRACT_ADDRESS = '0x...' // Your deployed contract address
+const ABI = [...] // Your contract ABI
+
+export default function MintPage() {
+ const { address, isConnected } = useAccount()
+ const [isLoading, setIsLoading] = useState(false)
+
+ const { writeContract, data: hash } = useWriteContract()
+
+ const { isLoading: isConfirming, isSuccess } = useWaitForTransactionReceipt({
+ hash,
+ })
+
+ const handleMint = async () => {
+ if (!isConnected) return
+
+ setIsLoading(true)
+
+ try {
+ writeContract({
+ abi: ABI,
+ address: CONTRACT_ADDRESS,
+ functionName: 'mint',
+ value: parseEther('0.01'),
+ })
+ } catch (error) {
+ console.error('Mint failed:', error)
+ } finally {
+ setIsLoading(false)
+ }
+ }
+
+ return (
+ ([])
+
+ const { data: totalSupply } = useReadContract({
+ abi: ABI,
+ address: contractAddress,
+ functionName: 'totalSupply',
+ })
+
+ useEffect(() => {
+ if (totalSupply) {
+ loadNFTs(Number(totalSupply))
+ }
+ }, [totalSupply])
+
+ const loadNFTs = async (supply: number) => {
+ const nftPromises = []
+
+ for (let i = 0; i < supply; i++) {
+ // Load token URI and parse metadata
+ // Implementation depends on your setup
+ }
+
+ const loadedNFTs = await Promise.all(nftPromises)
+ setNfts(loadedNFTs)
+ }
+
+ return (
+
+**Optimize Storage**
+
+Store only essential data onchain. Use efficient data structures and consider gas costs when designing your metadata schema.
+
+
+1. **Pack Data Efficiently**: Use structs and pack data to minimize storage slots
+2. **Lazy Generation**: Generate images and metadata on-demand in `tokenURI()`
+3. **Batch Operations**: Allow batch minting to reduce per-NFT costs
+4. **Optimize SVG**: Keep SVG code minimal and efficient
+
+### Security Considerations
+
+
+**Immutable Data**
+
+Remember that onchain data is permanent and immutable. Thoroughly test your generation logic before deployment.
+
+
+1. **Access Controls**: Implement proper access controls for minting functions
+2. **Input Validation**: Validate all inputs to prevent malformed metadata
+3. **Reentrancy Protection**: Use OpenZeppelin's ReentrancyGuard for payable functions
+4. **Audit Code**: Have your contracts audited before mainnet deployment
+
+## Deployment
+
+### Deploy to Base
+
+```bash Terminal
+# Using Foundry
+forge create --rpc-url https://mainnet.base.org \
+ --private-key $PRIVATE_KEY \
+ --verify \
+ contracts/SimpleOnchainNFT.sol:SimpleOnchainNFT \
+ --constructor-args $OWNER_ADDRESS
+```
+
+### Verify Contract
+
+```bash Terminal
+forge verify-contract \
+ --chain base \
+ --compiler-version v0.8.19 \
+ $CONTRACT_ADDRESS \
+ contracts/SimpleOnchainNFT.sol:SimpleOnchainNFT
+```
+
+## Resources
+
+
+
+ Secure smart contract building blocks
+
+
+ Onchain Base64 encoding utilities
+
+
+ Learn SVG for onchain graphics
+
+
+ NFT metadata standards
+
+
+
+---
+
+Onchain NFTs provide true digital ownership and permanence that can't be achieved with traditional hosted metadata. While they require more careful planning and higher gas costs, they offer unmatched durability and composability for your digital assets.
\ No newline at end of file
diff --git a/docs/cookbook/nfts/thirdweb-unreal-nft-items.mdx b/docs/cookbook/nfts/thirdweb-unreal-nft-items.mdx
new file mode 100644
index 00000000..07124250
--- /dev/null
+++ b/docs/cookbook/nfts/thirdweb-unreal-nft-items.mdx
@@ -0,0 +1,6 @@
+---
+title: 'ThirdWeb Unreal NFT Items'
+description: 'Create NFT items using ThirdWeb and Unreal Engine'
+---
+
+[Guide for creating NFT items using ThirdWeb and Unreal Engine]
\ No newline at end of file
diff --git a/docs/cookbook/onboard-any-user.mdx b/docs/cookbook/onboard-any-user.mdx
new file mode 100644
index 00000000..01b28960
--- /dev/null
+++ b/docs/cookbook/onboard-any-user.mdx
@@ -0,0 +1,143 @@
+---
+title: Onboard Any User
+sidebarTitle: Onboard User
+description: Learn how to seamlessly integrate the WalletModal component from OnchainKit to rapidly onboard new users with a smart wallet experience.
+---
+
+In onchain apps, the wallet is at the center of your user model. Onboarding requires users to connect an existing wallet or sign up for a new wallet. The [`
+
+ ```bash Terminal
+ npm create onchain@latest
+ ```
+
+
+ ```tsx providers.tsx
+
+ {children}
+
+ ```
+
+
+ ```tsx App.tsx
+
+
+
+
+
+
+
+
+ ```
+
+
+ Ensure that the Wallet Modal is globally accessible by wrapping your key UI components:
+
+ ```tsx
+
+
+ ```
+
+
+
+
+{/*
+ */}
+
+You now have an interface to streamline user onboarding! The `WalletModal` component handles:
+
+- Smart wallet creation for new signups
+- Quick connection for existing wallets
+- Wallet connection states
+- Error handling
+- Mobile/desktop responsive behavior
+- Theme customization
+- Terms/privacy policy display
+
+## Why Smart Wallet for new signups?
+
+In addition to providing a secure and feature-rich wallet experience, Smart Wallets provide a streamlined onboarding experience through account creation with Passkeys. This allows anyone to securely create a new wallet and begin transacting without ever leaving your app.
+
+
+**More on Smart Wallets**
+
+Smart Wallet has advanced features such as sponsored transactions, spend permissions, and Magic Spend. [Learn more about Smart Wallet here](/smart-wallet/quickstart).
+
+
+
+## Conclusion
+
+By integrating `
+
+ Platform-owned identity and content with limited user control
+
+
+ User-owned identity, programmable feeds, and embedded applications
+
+
+
+### The Onchain Social Paradigm
+
+Onchain social represents a fundamental shift in how we think about digital identity and social interactions:
+
+**Traditional Model Problems:**
+- Your identity, content, and interactions are owned by the platform
+- Building requires working on top of platforms, never inside them
+- Users must leave conversations to access new experiences
+- Developers are limited by platform APIs and restrictions
+
+**Onchain Social Solutions:**
+- **Portable Identity**: Your Farcaster ID (FID) belongs to you, not locked to any single platform
+- **Embedded Experiences**: Rich, interactive apps run natively inside posts and conversations
+- **Developer Freedom**: Build as first-class citizens within the social graph
+- **User Ownership**: Control your data, content, and social connections
+
+
+This isn't about replacing existing platforms—it's about removing the walls between users, developers, and the experiences they create together.
+
+
+## What You'll Build
+
+By the end of this guide, you'll have created a fully functional Mini App with these capabilities:
+
+
+
+ Polls, games, and collaborative tools that run inside social feeds
+
+
+ Apps that know who opened them and adapt accordingly
+
+
+ Direct access to wallets, DeFi protocols, and blockchain transactions
+
+
+ User-owned identity through Farcaster without separate logins
+
+
+
+## Mini Apps: The Interface for Onchain Social
+
+Mini Apps are lightweight, expressive web applications that live directly inside social feeds. They launch instantly without installation and provide rich, interactive experiences that respond to your onchain identity.
+
+**What makes Mini Apps special:**
+- **Embedded experiences** that don't redirect users away from conversations
+- **Social context awareness** - they know who opened them and from where
+- **Onchain identity integration** with automatic personalization
+- **Native feel** within social platforms
+
+**Use cases include:**
+- Interactive polls and real-time voting
+- Social games and entertainment
+- E-commerce with instant checkout
+- DeFi interfaces and portfolio management
+- NFT showcases and trading
+- Collaborative decision-making tools
+
+
+Mini Apps offer developers direct access to social distribution - you're building inside the conversation, not trying to pull users away from it.
+
+
+## Build Your First Mini App
+
+
+
+ The fastest way to build a Mini App is with MiniKit, which handles authentication, social context, and onchain integrations automatically.
+
+ **Create a new Mini App:**
+ ```bash
+ npx create-onchain --mini
+ cd your-mini-app-name
+ npm install
+ ```
+
+ **Start the development server:**
+ ```bash
+ npm run dev
+ ```
+
+
+ Your Mini App should now be running at `http://localhost:3000` with a fully functional social interface.
+
+
+ **What you get out of the box:**
+ - Complete frontend and backend scaffold
+ - Built-in support for Farcaster identity and notifications
+ - Native integrations with Base blockchain and OnchainKit
+ - Responsive design optimized for mobile social feeds
+ - Development tools for testing and debugging
+
+
+ The MiniKit scaffold includes example components and pages to help you understand the architecture quickly.
+
+
+
+
+ Mini Apps have access to rich social context that traditional web apps lack. This context makes personalization effortless and enables intelligent interactions.
+
+ **Access user and social context:**
+ ```tsx
+ import { useMiniKit } from "@coinbase/onchainkit/minikit";
+
+ export default function App() {
+ const { context } = useMiniKit();
+
+ // Verified user information (always available)
+ const userFid = context?.user?.fid;
+
+ // Additional user data (when available)
+ const username = context?.user?.username;
+ const displayName = context?.user?.displayName;
+ const pfpUrl = context?.user?.pfpUrl;
+
+ // Client information
+ const isAdded = context?.client?.added; // Whether user has added this Mini App
+ const location = context?.location; // Where the Mini App was launched from
+
+ return (
+
+ Always handle cases where context might be undefined, especially during development and testing.
+
+
+
+
+ Create engaging social experiences that leverage the Mini App's embedded nature:
+
+ **Example: Social Voting App**
+ ```tsx
+ import { useState, useEffect } from 'react';
+ import { useMiniKit } from "@coinbase/onchainkit/minikit";
+
+ export default function VotingApp() {
+ const { context } = useMiniKit();
+ const [votes, setVotes] = useState({ option1: 0, option2: 0 });
+ const [userVote, setUserVote] = useState(null);
+
+ const handleVote = async (option) => {
+ if (userVote) return; // Prevent double voting
+
+ // Submit vote to your backend
+ const response = await fetch('/api/vote', {
+ method: 'POST',
+ headers: { 'Content-Type': 'application/json' },
+ body: JSON.stringify({
+ fid: context?.user?.fid,
+ option,
+ location: context?.location
+ })
+ });
+
+ if (response.ok) {
+ setUserVote(option);
+ // Update vote counts
+ setVotes(prev => ({
+ ...prev,
+ [option]: prev[option] + 1
+ }));
+ }
+ };
+
+ return (
+
+ Use the user's FID to prevent duplicate votes and create personalized experiences without requiring separate authentication.
+
+
+
+
+ Enhance your Mini App with blockchain functionality using OnchainKit:
+
+ ```tsx
+ import {
+ Transaction,
+ TransactionButton,
+ TransactionStatus
+ } from '@coinbase/onchainkit/transaction';
+
+ export default function OnchainMiniApp() {
+ const { context } = useMiniKit();
+
+ const handleTransaction = async () => {
+ // Create transaction based on social context
+ const txData = {
+ to: '0x...',
+ value: '1000000000000000000', // 1 ETH
+ data: '0x...'
+ };
+
+ return txData;
+ };
+
+ return (
+
+ Your Mini App can now trigger blockchain transactions directly from social interactions.
+
+
+
+
+ Deploy your Mini App to make it accessible within social feeds:
+
+ **Deploy to Vercel (recommended):**
+ ```bash
+ npm install -g vercel
+ vercel --prod
+ ```
+
+ **Test your Mini App:**
+ 1. **Local testing**: Use the MiniKit development tools
+ 2. **Frame testing**: Test as a Farcaster Frame
+ 3. **Social testing**: Deploy and test in actual social contexts
+ 4. **Performance testing**: Ensure fast loading in mobile environments
+
+
+ Always test your Mini App in actual social contexts before broad deployment, as the social environment can affect performance and user experience.
+
+
+
+
+## Convert Existing Apps to Mini Apps
+
+Transform your existing Next.js application into a Mini App without major restructuring. The process is straightforward and doesn't require rebuilding your entire application.
+
+
+Follow our comprehensive guide for integrating MiniKit into existing applications with step-by-step instructions, environment setup, and testing procedures.
+
+
+**Key integration steps:**
+- Install MiniKit as part of OnchainKit
+- Wrap your app with `MiniKitProvider`
+- Add social context integration to existing components
+- Configure environment variables and deployment
+
+
+For new projects, use the [MiniKit CLI](/builderkits/minikit/quickstart) for automatic setup with all features pre-configured.
+
+
+## Advanced MiniKit Features
+
+Once you have your basic Mini App running, explore advanced capabilities:
+
+
+
+ Send push notifications to users who have added your Mini App
+
+
+ Implement Farcaster authentication for secure, persistent sessions
+
+
+ Navigate users to Farcaster profiles and build social connections
+
+
+ Allow users to save your Mini App for easy access
+
+
+
+## Best Practices & Troubleshooting
+
+Building successful Mini Apps requires understanding social-specific patterns and common pitfalls:
+
+
+
+ Design patterns and best practices for building social Mini Apps
+
+
+ Common issues and solutions when developing Mini Apps
+
+
+ Optimize loading times and user experience for mobile social environments
+
+
+ Specific guidance for optimizing Mini Apps in Coinbase Wallet
+
+
+
+## Resources and Community
+
+
+
+ Complete documentation for building Mini Apps with MiniKit
+
+
+ Get started with MiniKit in under 10 minutes
+
+
+ Learn about the underlying Farcaster social protocol
+
+
+ Connect with other developers building onchain social apps
+
+
+
+
diff --git a/docs/cookbook/payments/build-ecommerce-app.mdx b/docs/cookbook/payments/build-ecommerce-app.mdx
new file mode 100644
index 00000000..eb365cd2
--- /dev/null
+++ b/docs/cookbook/payments/build-ecommerce-app.mdx
@@ -0,0 +1,6 @@
+---
+title: 'Build an E-commerce App'
+description: 'Learn how to build an e-commerce application on Base'
+---
+
+[Guide for building an e-commerce application on Base]
\ No newline at end of file
diff --git a/docs/cookbook/payments/deploy-shopify-storefront.mdx b/docs/cookbook/payments/deploy-shopify-storefront.mdx
new file mode 100644
index 00000000..405118a1
--- /dev/null
+++ b/docs/cookbook/payments/deploy-shopify-storefront.mdx
@@ -0,0 +1,6 @@
+---
+title: 'Deploy a Shopify Storefront'
+description: 'Guide to deploying a Shopify storefront on Base'
+---
+
+[Instructions for deploying a Shopify storefront on Base]
\ No newline at end of file
diff --git a/docs/cookbook/payments/transaction-guide.mdx b/docs/cookbook/payments/transaction-guide.mdx
new file mode 100644
index 00000000..885e2e80
--- /dev/null
+++ b/docs/cookbook/payments/transaction-guide.mdx
@@ -0,0 +1,6 @@
+---
+title: 'Transaction Guide'
+description: 'Comprehensive guide for handling transactions'
+---
+
+[Guide for handling transactions in payment applications]
\ No newline at end of file
diff --git a/docs/cookbook/social/convert-farcaster-frame.mdx b/docs/cookbook/social/convert-farcaster-frame.mdx
new file mode 100644
index 00000000..c4b7659e
--- /dev/null
+++ b/docs/cookbook/social/convert-farcaster-frame.mdx
@@ -0,0 +1,436 @@
+---
+title: Convert Farcaster Frame to Open Frame
+sidebarTitle: Convert to Open Frame
+description: 'Step-by-step guide for converting Farcaster Frames to Open Frames for broader platform support'
+---
+
+Expand your Frame's reach beyond Farcaster by converting it to an Open Frame. Open Frames are supported across multiple platforms including X (Twitter), making your interactive content accessible to a much wider audience.
+
+
+
+ Learn about the Open Frame standard and its benefits
+
+
+ Step-by-step conversion guide
+
+
+ Deploy your Frame across multiple platforms
+
+
+ Tips for optimal cross-platform compatibility
+
+
+
+## Understanding Open Frames
+
+Open Frames extend the Farcaster Frame standard to work across multiple platforms. They maintain the same interactive capabilities while adding broader platform compatibility.
+
+
+**Open Frame Benefits**
+
+- **Wider Reach**: Deploy to X (Twitter), Lens Protocol, and other platforms
+- **Standardized Format**: Use a single codebase for multiple platforms
+- **Future-Proof**: Built on open standards for broader adoption
+- **Enhanced Discovery**: Tap into larger social networks
+
+
+### Key Differences
+
+| Feature | Farcaster Frames | Open Frames |
+|---------|------------------|-------------|
+| Platform Support | Farcaster only | Multiple platforms |
+| Metadata Format | Farcaster-specific | Open Graph + extensions |
+| Button Actions | Limited to Farcaster | Cross-platform compatible |
+| Image Handling | Farcaster standards | Universal image formats |
+
+## Prerequisites
+
+Before converting your Frame, ensure you have:
+
+
+A working Farcaster Frame
+
+
+Understanding of Open Graph meta tags
+
+
+Access to Frame deployment infrastructure
+
+
+Test accounts on target platforms
+
+
+## Conversion Steps
+
+### Step 1: Update Meta Tags
+
+Convert your Farcaster-specific meta tags to Open Frame format:
+
+```html Before (Farcaster Frame)
+
+
+
+
+```
+
+```html After (Open Frame)
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+```
+
+### Step 2: Update Frame Handler
+
+Modify your Frame handler to support multiple platforms:
+
+```typescript api/frame/route.ts
+import { NextRequest, NextResponse } from 'next/server'
+
+export async function POST(req: NextRequest) {
+ const body = await req.json()
+
+ // Detect the platform
+ const platform = detectPlatform(body)
+
+ // Handle different platform formats
+ switch (platform) {
+ case 'farcaster':
+ return handleFarcasterFrame(body)
+ case 'xmtp':
+ return handleXMTPFrame(body)
+ case 'lens':
+ return handleLensFrame(body)
+ default:
+ return handleGenericFrame(body)
+ }
+}
+
+function detectPlatform(body: any): string {
+ // Check for platform-specific identifiers
+ if (body.untrustedData?.fid) return 'farcaster'
+ if (body.clientProtocol?.includes('xmtp')) return 'xmtp'
+ if (body.clientProtocol?.includes('lens')) return 'lens'
+ return 'generic'
+}
+
+function handleFarcasterFrame(body: any) {
+ const { buttonIndex, fid, castId } = body.untrustedData
+
+ // Your existing Farcaster logic
+ return NextResponse.json({
+ image: "https://example.com/response.jpg",
+ buttons: [
+ { label: "Next", action: "post" }
+ ]
+ })
+}
+
+function handleGenericFrame(body: any) {
+ // Generic handling for other platforms
+ return NextResponse.json({
+ image: "https://example.com/response.jpg",
+ buttons: [
+ { label: "Continue", action: "post" }
+ ]
+ })
+}
+```
+
+### Step 3: Add Platform Detection
+
+Create a utility to handle platform-specific logic:
+
+```typescript utils/platform.ts
+export interface FrameRequest {
+ platform: 'farcaster' | 'xmtp' | 'lens' | 'generic'
+ user?: {
+ id: string
+ username?: string
+ address?: string
+ }
+ interaction: {
+ buttonIndex: number
+ inputText?: string
+ state?: string
+ }
+}
+
+export function parseFrameRequest(body: any): FrameRequest {
+ // Farcaster format
+ if (body.untrustedData?.fid) {
+ return {
+ platform: 'farcaster',
+ user: {
+ id: body.untrustedData.fid.toString(),
+ address: body.untrustedData.address,
+ },
+ interaction: {
+ buttonIndex: body.untrustedData.buttonIndex,
+ inputText: body.untrustedData.inputText,
+ state: body.untrustedData.state,
+ }
+ }
+ }
+
+ // Generic format for other platforms
+ return {
+ platform: 'generic',
+ user: {
+ id: body.user?.id || 'anonymous',
+ },
+ interaction: {
+ buttonIndex: body.buttonIndex || 1,
+ inputText: body.inputText,
+ state: body.state,
+ }
+ }
+}
+```
+
+### Step 4: Update Response Format
+
+Ensure your responses work across platforms:
+
+```typescript utils/frameResponse.ts
+export interface FrameResponse {
+ image: string
+ imageAspectRatio?: '1.91:1' | '1:1'
+ buttons?: Array<{
+ label: string
+ action?: 'post' | 'post_redirect' | 'link' | 'mint'
+ target?: string
+ }>
+ input?: {
+ text: string
+ }
+ state?: string
+}
+
+export function createFrameResponse(response: FrameResponse) {
+ const html = `
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ ${response.buttons?.map((button, index) => `
+
+
+ ${button.action ? `` : ''}
+ ${button.action ? `` : ''}
+ ${button.target ? `` : ''}
+ ${button.target ? `` : ''}
+ `).join('') || ''}
+
+ ${response.input ? `
+
+
+ ` : ''}
+
+ ${response.state ? `
+
+
+ ` : ''}
+
+
+ 
+
+
+ `
+
+ return new Response(html, {
+ headers: { 'Content-Type': 'text/html' },
+ })
+}
+```
+
+## Platform Support
+
+### X (Twitter) Integration
+
+To make your Open Frame work on X:
+
+1. **Ensure proper Open Graph tags** are present
+2. **Test with X's card validator**: Use the Card Validator to verify your meta tags
+3. **Handle X-specific user interactions**: X may pass different user data
+
+```typescript utils/xIntegration.ts
+export function handleXFrame(body: any) {
+ // X-specific handling
+ return {
+ platform: 'x',
+ user: {
+ id: body.user?.id || 'x_user',
+ username: body.user?.username,
+ },
+ interaction: {
+ buttonIndex: body.buttonIndex || 1,
+ }
+ }
+}
+```
+
+### Lens Protocol Support
+
+For Lens Protocol integration:
+
+```typescript utils/lensIntegration.ts
+export function handleLensFrame(body: any) {
+ return {
+ platform: 'lens',
+ user: {
+ id: body.profileId,
+ address: body.address,
+ },
+ interaction: {
+ buttonIndex: body.buttonIndex,
+ state: body.state,
+ }
+ }
+}
+```
+
+## Best Practices
+
+### Cross-Platform Compatibility
+
+
+**Universal Design**
+
+Design your Frame content and interactions to work across all platforms. Avoid platform-specific features in your core experience.
+
+
+1. **Consistent Branding**: Use the same visual elements across platforms
+2. **Universal Button Labels**: Use clear, platform-agnostic button text
+3. **Responsive Images**: Ensure images work at different aspect ratios
+4. **Graceful Degradation**: Handle missing platform features gracefully
+
+### Testing Strategy
+
+
+
+Ensure your original Farcaster Frame still works perfectly.
+
+
+
+Use validation tools to check your Open Graph and Open Frame meta tags.
+
+
+
+Test your Frame on each target platform with real user accounts.
+
+
+
+Track engagement across platforms to optimize performance.
+
+
+
+### Performance Optimization
+
+```typescript utils/optimization.ts
+// Cache images across platforms
+export function getCachedImage(imageKey: string) {
+ // Implement caching logic
+ return `https://cdn.example.com/frames/${imageKey}.jpg`
+}
+
+// Optimize for different platform requirements
+export function optimizeImageForPlatform(
+ baseImage: string,
+ platform: string
+): string {
+ switch (platform) {
+ case 'farcaster':
+ return `${baseImage}?w=1200&h=630` // 1.91:1 aspect ratio
+ case 'x':
+ return `${baseImage}?w=1200&h=675` // X card format
+ default:
+ return baseImage
+ }
+}
+```
+
+## Deployment
+
+### Environment Configuration
+
+```bash .env
+# Platform-specific configurations
+FARCASTER_HUB_URL=https://neynar.com/v1/farcaster
+XMTP_ENV=production
+LENS_API_URL=https://api.lens.dev
+
+# Image optimization
+IMAGE_CDN_URL=https://cdn.example.com
+```
+
+### Monitoring and Analytics
+
+Track Frame performance across platforms:
+
+```typescript utils/analytics.ts
+export function trackFrameInteraction(
+ platform: string,
+ action: string,
+ userId?: string
+) {
+ // Send analytics to your preferred service
+ analytics.track('frame_interaction', {
+ platform,
+ action,
+ userId,
+ timestamp: new Date().toISOString(),
+ })
+}
+```
+
+## Resources
+
+
+
+ Official Open Frames specification
+
+
+ Tools for testing your Frames
+
+
+ Platform-specific Frame documentation
+
+
+ Cross-platform optimization tips
+
+
+
+---
+
+Converting your Farcaster Frame to an Open Frame significantly expands your reach while maintaining the interactive experience users love. Start with backward compatibility and gradually optimize for each platform's unique features and audience.
\ No newline at end of file
diff --git a/docs/cookbook/social/farcaster-nft-minting-guide.mdx b/docs/cookbook/social/farcaster-nft-minting-guide.mdx
new file mode 100644
index 00000000..c8180900
--- /dev/null
+++ b/docs/cookbook/social/farcaster-nft-minting-guide.mdx
@@ -0,0 +1,419 @@
+---
+title: Farcaster NFT Minting Guide
+sidebarTitle: Farcaster NFT Minting
+description: 'Comprehensive guide to NFT minting with Farcaster integration'
+---
+
+Build engaging NFT minting experiences by integrating Farcaster Frames with Base smart contracts. This guide shows you how to create seamless social-first minting flows that leverage Farcaster's social graph.
+
+
+
+ Configure Farcaster Frames for your NFT collection
+
+
+ Deploy and integrate your NFT contract with Frame actions
+
+
+ Add social proof and community features to your mint
+
+
+ Security and user experience considerations
+
+
+
+## Overview
+
+Farcaster Frames provide a powerful way to embed interactive NFT minting experiences directly in social feeds. Users can mint NFTs without leaving their Farcaster client, creating frictionless onboarding and viral distribution.
+
+
+**What are Farcaster Frames?**
+
+Frames are interactive components that can be embedded in Farcaster casts (posts). They support buttons, images, and actions that can trigger onchain transactions directly from the social feed.
+
+
+## Prerequisites
+
+Before starting, ensure you have:
+
+
+A deployed NFT contract on Base (or Base Sepolia for testing)
+
+
+Basic understanding of Farcaster and Frame development
+
+
+Next.js development environment set up
+
+
+Farcaster account for testing
+
+
+## Setting Up Farcaster Frames
+
+### Project Structure
+
+Create a new Frame project or add Frame functionality to your existing Next.js app:
+
+```bash Terminal
+npx create-next-app@latest farcaster-nft-mint
+cd farcaster-nft-mint
+npm install frog hono @coinbase/onchainkit
+```
+
+### Frame Metadata
+
+Create your Frame with proper metadata for NFT minting:
+
+```typescript app/frame/route.tsx
+import { Button, Frog } from 'frog'
+import { handle } from 'frog/next'
+import { neynar } from 'frog/hubs'
+
+const app = new Frog({
+ title: 'Base NFT Mint',
+ hub: neynar({ apiKey: process.env.NEYNAR_API_KEY! }),
+ assetsPath: '/',
+ basePath: '/frame',
+})
+
+app.frame('/', (c) => {
+ return c.res({
+ image: (
+ Learn More ,
+ ],
+ })
+})
+
+export const GET = handle(app)
+export const POST = handle(app)
+```
+
+## Smart Contract Integration
+
+### NFT Contract Setup
+
+Use OpenZeppelin's ERC-721 contracts for a secure foundation:
+
+```solidity contracts/BaseNFT.sol
+// SPDX-License-Identifier: MIT
+pragma solidity ^0.8.19;
+
+import "@openzeppelin/contracts/token/ERC721/ERC721.sol";
+import "@openzeppelin/contracts/access/Ownable.sol";
+import "@openzeppelin/contracts/security/ReentrancyGuard.sol";
+
+contract BaseNFT is ERC721, Ownable, ReentrancyGuard {
+ uint256 public constant MAX_SUPPLY = 1000;
+ uint256 public constant MINT_PRICE = 0.001 ether;
+ uint256 public totalSupply;
+
+ mapping(address => bool) public hasMinted;
+
+ event NFTMinted(address indexed to, uint256 tokenId);
+
+ constructor(address initialOwner)
+ ERC721("Base Social NFT", "BSN")
+ Ownable(initialOwner)
+ {}
+
+ function mint() external payable nonReentrant {
+ require(totalSupply < MAX_SUPPLY, "Max supply reached");
+ require(msg.value >= MINT_PRICE, "Insufficient payment");
+ require(!hasMinted[msg.sender], "Already minted");
+
+ uint256 tokenId = totalSupply + 1;
+ totalSupply++;
+ hasMinted[msg.sender] = true;
+
+ _safeMint(msg.sender, tokenId);
+
+ emit NFTMinted(msg.sender, tokenId);
+ }
+
+ function withdraw() external onlyOwner {
+ payable(owner()).transfer(address(this).balance);
+ }
+}
+```
+
+### Frame Action Handler
+
+Create the mint action handler that integrates with your smart contract:
+
+```typescript app/frame/mint/route.tsx
+import { Button, Frog, parseEther } from 'frog'
+import { handle } from 'frog/next'
+
+app.frame('/mint', async (c) => {
+ const { buttonValue, frameData } = c
+
+ // Get user's Farcaster ID and ETH address
+ const fid = frameData?.fid
+ const address = frameData?.address
+
+ if (!address) {
+ return c.res({
+ image: (
+
+ View on BaseScan
+ ,
+ ],
+ })
+ }
+
+ return c.res({
+ image: (
+
+ Mint NFT (0.001 ETH)
+ ,
+ ,
+ ],
+ })
+
+ } catch (error) {
+ console.error('Mint error:', error)
+ return c.error({ message: 'Failed to process mint' })
+ }
+})
+```
+
+### Transaction Handler
+
+Handle the actual NFT minting transaction:
+
+```typescript app/frame/mint-tx/route.tsx
+import { Frog, parseEther } from 'frog'
+import { erc721Abi } from 'viem'
+
+app.transaction('/mint-tx', (c) => {
+ return c.contract({
+ abi: [
+ {
+ "inputs": [],
+ "name": "mint",
+ "outputs": [],
+ "stateMutability": "payable",
+ "type": "function"
+ }
+ ],
+ chainId: 'eip155:8453', // Base mainnet
+ functionName: 'mint',
+ to: process.env.NFT_CONTRACT_ADDRESS as `0x${string}`,
+ value: parseEther('0.001'),
+ })
+})
+```
+
+## Social Integration
+
+### Add Social Proof
+
+Display minting activity and social proof in your Frame:
+
+```typescript utils/social.ts
+export async function getMintingActivity() {
+ // Fetch recent mints from your contract
+ const recentMints = await publicClient.getLogs({
+ address: NFT_CONTRACT_ADDRESS,
+ event: parseAbiItem('event NFTMinted(address indexed to, uint256 tokenId)'),
+ fromBlock: 'earliest',
+ })
+
+ return recentMints.slice(-5) // Last 5 mints
+}
+
+export async function getFarcasterProfile(fid: number) {
+ // Use Neynar API to get user profile
+ const response = await fetch(`https://api.neynar.com/v2/farcaster/user/bulk?fids=${fid}`, {
+ headers: {
+ 'api_key': process.env.NEYNAR_API_KEY!,
+ },
+ })
+
+ return response.json()
+}
+```
+
+### Display Community Activity
+
+```typescript app/frame/activity/route.tsx
+app.frame('/activity', async (c) => {
+ const recentMints = await getMintingActivity()
+
+ return c.res({
+ image: (
+
+**Smart Contract Security**
+
+Always audit your NFT contracts before mainnet deployment. Use OpenZeppelin's battle-tested contracts and follow security best practices.
+
+
+1. **Rate Limiting**: Implement proper rate limiting to prevent spam
+2. **Input Validation**: Validate all Frame inputs and user data
+3. **Error Handling**: Provide clear error messages for failed transactions
+4. **Access Controls**: Use proper access controls for admin functions
+
+### User Experience
+
+
+**Seamless Experience**
+
+Keep the minting flow simple - ideally just 1-2 clicks from seeing the Frame to completing the mint.
+
+
+1. **Clear Imagery**: Use high-quality images that represent your NFT collection
+2. **Progress Indicators**: Show users their progress through the minting flow
+3. **Error Recovery**: Provide clear paths for users to retry failed transactions
+4. **Social Sharing**: Encourage users to share their successful mints
+
+### Gas Optimization
+
+Consider using Base's low fees and fast confirmation times:
+
+```typescript utils/gasOptimization.ts
+// Use efficient batch minting for multiple NFTs
+export async function batchMint(recipients: string[], amounts: number[]) {
+ return await contract.write.batchMint(recipients, amounts)
+}
+
+// Consider using ERC-721A for efficient batch minting
+// if your collection supports it
+```
+
+## Testing Your Frame
+
+### Local Development
+
+1. **Frame Validator**: Use the [Frame Validator](https://warpcast.com/~/developers/frames) to test your Frame
+2. **Local Testing**: Test with ngrok or similar tools to expose your localhost
+3. **Testnet First**: Deploy to Base Sepolia before mainnet
+
+### Production Deployment
+
+
+
+Deploy your NFT contract to Base mainnet using Foundry or Hardhat.
+
+
+
+Set up your production environment variables:
+
+```bash .env.production
+NFT_CONTRACT_ADDRESS=0x...
+NEYNAR_API_KEY=your_api_key
+BASE_RPC_URL=https://mainnet.base.org
+```
+
+
+
+Deploy your Frame app to Vercel or your preferred hosting platform.
+
+
+
+Test the complete flow from Frame display to successful NFT mint.
+
+
+
+## Resources
+
+
+
+ Official documentation for building Farcaster Frames
+
+
+ Farcaster data and infrastructure
+
+
+ Secure smart contract templates
+
+
+ Deploy contracts on Base
+
+
+
+---
+
+Building NFT minting experiences with Farcaster Frames creates viral, social-first onboarding that can dramatically increase your collection's reach and engagement. Start with a simple implementation and iterate based on user feedback and community response.
\ No newline at end of file
diff --git a/docs/cookbook/social/farcaster-no-code-nft-minting.mdx b/docs/cookbook/social/farcaster-no-code-nft-minting.mdx
new file mode 100644
index 00000000..9ddbfbef
--- /dev/null
+++ b/docs/cookbook/social/farcaster-no-code-nft-minting.mdx
@@ -0,0 +1,6 @@
+---
+title: Farcaster No-Code NFT Minting
+description: 'Create NFT minting experiences without code using Farcaster'
+---
+
+[Guide for creating no-code NFT minting experiences using Farcaster]
\ No newline at end of file
diff --git a/docs/custom.css b/docs/custom.css
new file mode 100644
index 00000000..e11340b9
--- /dev/null
+++ b/docs/custom.css
@@ -0,0 +1,34 @@
+/* Danger admonition coloring */
+
+.danger-admonition {
+ border: 1px solid rgba(239, 68, 68, 0.2);
+ background-color: rgba(254, 242, 242, 0.5);
+}
+
+.dark\:danger-admonition:is(.dark *) {
+ border-color: rgba(239, 68, 68, 0.3);
+ background-color: rgba(239, 68, 68, 0.1);
+}
+
+.base_header_img {
+ margin: auto;
+}
+
+.homepage_wrapper {
+ width: 75%;
+ max-width: 1376px;
+ margin: auto;
+ margin-bottom: 50px;
+}
+
+.home_header {
+ padding-bottom: 0 !important;
+}
+
+.home_header h1 {
+ margin-bottom: 24px;
+}
+
+.home_header div p {
+ margin-top: 10px;
+}
diff --git a/docs/docs.json b/docs/docs.json
new file mode 100644
index 00000000..9fba3077
--- /dev/null
+++ b/docs/docs.json
@@ -0,0 +1,1028 @@
+{
+ "$schema": "https://mintlify.com/docs.json",
+ "theme": "mint",
+ "name": "Base Documentation",
+ "colors": {
+ "primary": "#578BFA",
+ "light": "#578BFA",
+ "dark": "#578BFA"
+ },
+ "favicon": "/logo/favicon.svg",
+ "contextual": {
+ "options": [
+ "copy",
+ "chatgpt",
+ "claude"
+ ]
+ },
+ "api": {
+ "playground": {
+ "display": "simple"
+ },
+ "examples": {
+ "languages": [
+ "javascript"
+ ]
+ }
+ },
+ "navigation": {
+ "tabs": [
+ {
+ "tab": "Get Started",
+ "groups": [
+ {
+ "group": "Introduction",
+ "pages": [
+ "get-started/base"
+ ]
+ },
+ {
+ "group": "Browse by",
+ "pages": [
+ "get-started/products",
+ "get-started/use-cases"
+ ]
+ },
+ {
+ "group": "Quickstart",
+ "pages": [
+ "get-started/build-app",
+ "get-started/launch-token",
+ "get-started/deploy-chain",
+ "get-started/deploy-smart-contracts",
+ "get-started/get-funded"
+ ]
+ },
+ {
+ "group": "Build with AI",
+ "pages": [
+ "get-started/ai-prompting",
+ "get-started/prompt-library"
+ ]
+ }
+ ],
+ "global": {
+ "anchors": [
+ {
+ "anchor": "Status",
+ "href": "https://status.base.org/",
+ "icon": "signal-bars"
+ },
+ {
+ "anchor": "Faucet",
+ "href": "https://test-184b3b57.mintlify.app/base-chain/tools/network-faucets",
+ "icon": "gas-pump"
+ },
+ {
+ "anchor": "Bridge",
+ "href": "https://test-184b3b57.mintlify.app/base-chain/quickstart/bridge-token",
+ "icon": "coin"
+ }
+ ]
+ }
+ },
+ {
+ "tab": "Base Chain",
+ "groups": [
+ {
+ "group": "Quickstart",
+ "pages": [
+
+ "base-chain/quickstart/why-base",
+ "base-chain/quickstart/deploy-on-base",
+ "base-chain/quickstart/connecting-to-base",
+ "base-chain/quickstart/bridge-token"
+ ]
+ },
+ {
+ "group": "Network Information",
+ "pages": [
+ "base-chain/network-information/base-contracts",
+ "base-chain/network-information/network-fees",
+ "base-chain/network-information/ecosystem-contracts",
+ "base-chain/network-information/diffs-ethereum-base"
+ ]
+ },
+ {
+ "group": "Flashblocks",
+ "pages": [
+ "base-chain/flashblocks/apps",
+ "base-chain/flashblocks/node-providers"
+ ]
+ },
+ {
+ "group": "Node Operators",
+ "pages": [
+ "base-chain/node-operators/run-a-base-node",
+ "base-chain/node-operators/performance-tuning",
+ "base-chain/node-operators/snapshots",
+ "base-chain/node-operators/troubleshooting"
+ ]
+ },
+ {
+ "group": "Tools",
+ "pages": [
+ "base-chain/tools/base-products",
+ "base-chain/tools/onchain-registry-api",
+ "base-chain/tools/node-providers",
+ "base-chain/tools/block-explorers",
+ "base-chain/tools/network-faucets",
+ "base-chain/tools/oracles",
+ "base-chain/tools/data-indexers",
+ "base-chain/tools/cross-chain",
+ "base-chain/tools/account-abstraction",
+ "base-chain/tools/onramps",
+ "base-chain/tools/tokens-in-wallet"
+ ]
+ },
+ {
+ "group": "Security",
+ "pages": [
+ "base-chain/security/security-council",
+ "base-chain/security/avoid-malicious-flags",
+ "base-chain/security/report-vulnerability"
+ ]
+ }
+ ],
+ "global": {
+ "anchors": [
+ {
+ "anchor": "GitHub",
+ "href": "https://github.com/base",
+ "icon": "github"
+ },
+ {
+ "anchor": "Status",
+ "href": "https://status.base.org/",
+ "icon": "signal-bars"
+ },
+ {
+ "anchor": "Chain Stats",
+ "href": "https://www.base.org/stats",
+ "icon": "chart-line"
+ },
+ {
+ "anchor": "Explorer",
+ "href": "https://basescan.com/",
+ "icon": "magnifying-glass"
+ },
+ {
+ "anchor": "Support",
+ "href": "https://discord.com/invite/base",
+ "icon": "discord"
+ }
+ ]
+ }
+ },
+ {
+ "tab": "Smart Wallet",
+ "groups": [
+ {
+ "group": "Quickstart",
+ "pages": [
+ "smart-wallet/quickstart",
+ "smart-wallet/quickstart/quick-demo",
+ "smart-wallet/quickstart/nextjs-project",
+ "smart-wallet/quickstart/react-native-project",
+ "smart-wallet/quickstart/ai-tools-available-for-devs"
+ ]
+ },
+ {
+ "group": "Concepts",
+ "pages": [
+ "smart-wallet/concepts/what-is-smart-wallet",
+ {
+ "group": "Features",
+ "pages": [
+ {
+ "group": "Built-in Features",
+ "pages": [
+ "smart-wallet/concepts/features/built-in/single-sign-on",
+ "smart-wallet/concepts/features/built-in/networks",
+ "smart-wallet/concepts/features/built-in/passkeys",
+ "smart-wallet/concepts/features/built-in/recovery-keys",
+ "smart-wallet/concepts/features/built-in/MagicSpend"
+ ]
+ },
+ {
+ "group": "Optional Features",
+ "pages": [
+ "smart-wallet/concepts/features/optional/gas-free-transactions",
+ "smart-wallet/concepts/features/optional/spend-limits",
+ "smart-wallet/concepts/features/optional/batch-operations",
+ "smart-wallet/concepts/features/optional/custom-gas-tokens",
+ "smart-wallet/concepts/features/optional/sub-accounts"
+ ]
+ }
+ ]
+ },
+ {
+ "group": "Usage Details",
+ "pages": [
+ "smart-wallet/concepts/usage-details/signature-verification",
+ "smart-wallet/concepts/usage-details/popups",
+ "smart-wallet/concepts/usage-details/gas-usage",
+ "smart-wallet/concepts/usage-details/unsupported-calls"
+ ]
+ },
+ "smart-wallet/concepts/base-gasless-campaign"
+ ]
+ },
+ {
+ "group": "Guides",
+ "pages": [
+ "smart-wallet/guides/siwe",
+ "smart-wallet/guides/signing-and-verifying-messages",
+ "smart-wallet/guides/magic-spend",
+ "smart-wallet/guides/batch-transactions",
+ "smart-wallet/guides/paymasters",
+ "smart-wallet/guides/erc20-paymasters",
+ {
+ "group": "Sub Accounts",
+ "pages": [
+ "smart-wallet/guides/sub-accounts",
+ "smart-wallet/guides/sub-accounts/setup",
+ "smart-wallet/guides/sub-accounts/using-sub-accounts"
+ ]
+ },
+ "smart-wallet/guides/spend-limits"
+ ]
+ },
+ {
+ "group": "Examples",
+ "pages": [
+ "smart-wallet/examples/coin-a-joke-app"
+ ]
+ },
+ {
+ "group": "Technical Reference",
+ "pages": [
+ {
+ "group": "Coinbase Wallet SDK",
+ "pages": [
+ "smart-wallet/technical-reference/sdk",
+ "smart-wallet/technical-reference/sdk/CoinbaseWalletProvider/eth_accounts",
+ "smart-wallet/technical-reference/sdk/CoinbaseWalletProvider/eth_blockNumber",
+ "smart-wallet/technical-reference/sdk/CoinbaseWalletProvider/eth_chainId",
+ "smart-wallet/technical-reference/sdk/CoinbaseWalletProvider/eth_coinbase",
+ "smart-wallet/technical-reference/sdk/CoinbaseWalletProvider/eth_estimateGas",
+ "smart-wallet/technical-reference/sdk/CoinbaseWalletProvider/eth_feeHistory",
+ "smart-wallet/technical-reference/sdk/CoinbaseWalletProvider/eth_gasPrice",
+ "smart-wallet/technical-reference/sdk/CoinbaseWalletProvider/eth_getBalance",
+ "smart-wallet/technical-reference/sdk/CoinbaseWalletProvider/eth_getBlockByHash",
+ "smart-wallet/technical-reference/sdk/CoinbaseWalletProvider/eth_getBlockByNumber",
+ "smart-wallet/technical-reference/sdk/CoinbaseWalletProvider/eth_getBlockTransactionCountByHash",
+ "smart-wallet/technical-reference/sdk/CoinbaseWalletProvider/eth_getBlockTransactionCountByNumber",
+ "smart-wallet/technical-reference/sdk/CoinbaseWalletProvider/eth_getCode",
+ "smart-wallet/technical-reference/sdk/CoinbaseWalletProvider/eth_getLogs",
+ "smart-wallet/technical-reference/sdk/CoinbaseWalletProvider/eth_getProof",
+ "smart-wallet/technical-reference/sdk/CoinbaseWalletProvider/eth_getStorageAt",
+ "smart-wallet/technical-reference/sdk/CoinbaseWalletProvider/eth_getTransactionByBlockHashAndIndex",
+ "smart-wallet/technical-reference/sdk/CoinbaseWalletProvider/eth_getTransactionByBlockNumberAndIndex",
+ "smart-wallet/technical-reference/sdk/CoinbaseWalletProvider/eth_getTransactionByHash",
+ "smart-wallet/technical-reference/sdk/CoinbaseWalletProvider/eth_getTransactionCount",
+ "smart-wallet/technical-reference/sdk/CoinbaseWalletProvider/eth_getTransactionReceipt",
+ "smart-wallet/technical-reference/sdk/CoinbaseWalletProvider/eth_getUncleCountByBlockHash",
+ "smart-wallet/technical-reference/sdk/CoinbaseWalletProvider/eth_getUncleCountByBlockNumber",
+ "smart-wallet/technical-reference/sdk/CoinbaseWalletProvider/eth_requestAccounts",
+ "smart-wallet/technical-reference/sdk/CoinbaseWalletProvider/eth_sendRawTransaction",
+ "smart-wallet/technical-reference/sdk/CoinbaseWalletProvider/eth_sendTransaction",
+ "smart-wallet/technical-reference/sdk/CoinbaseWalletProvider/eth_signTypedData_v4",
+ "smart-wallet/technical-reference/sdk/CoinbaseWalletProvider/personal_sign",
+ "smart-wallet/technical-reference/sdk/CoinbaseWalletProvider/wallet_addEthereumChain",
+ "smart-wallet/technical-reference/sdk/CoinbaseWalletProvider/wallet_addSubAccount",
+ "smart-wallet/technical-reference/sdk/CoinbaseWalletProvider/wallet_connect",
+ "smart-wallet/technical-reference/sdk/CoinbaseWalletProvider/wallet_switchEthereumChain",
+ "smart-wallet/technical-reference/sdk/CoinbaseWalletProvider/wallet_watchAsset",
+ "smart-wallet/technical-reference/sdk/CoinbaseWalletProvider/web3_clientVersion"
+ ]
+ },
+ {
+ "group": "Spend Limits",
+ "pages": [
+ "smart-wallet/technical-reference/spend-permissions/spendpermissionmanager",
+ "smart-wallet/technical-reference/spend-permissions/coinbase-fetchpermissions"
+ ]
+ },
+ "smart-wallet/technical-reference/sdk/sub-account-reference"
+ ]
+ },
+ {
+ "group": "Contribute",
+ "pages": [
+ "smart-wallet/contribute/contribute-to-smart-wallet-docs",
+ "smart-wallet/contribute/security-and-bug-bounty"
+ ]
+ }
+ ],
+ "global": {
+ "anchors": [
+ {
+ "anchor": "GitHub",
+ "href": "https://github.com/coinbase/onchainkit",
+ "icon": "github"
+ },
+ {
+ "anchor": "Support",
+ "href": "https://discord.com/invite/cdp",
+ "icon": "discord"
+ }
+ ]
+ }
+ },
+ {
+ "tab": "OnchainKit",
+ "groups": [
+ {
+ "group": "Introduction",
+ "pages": [
+ "onchainkit/getting-started",
+ "onchainkit/guides/telemetry",
+ "onchainkit/guides/troubleshooting"
+ ]
+ },
+ {
+ "group": "Installation",
+ "pages": [
+ "onchainkit/installation/nextjs",
+ "onchainkit/installation/vite",
+ "onchainkit/installation/remix",
+ "onchainkit/installation/astro"
+ ]
+ },
+ {
+ "group": "Config",
+ "pages": [
+ "onchainkit/config/onchainkit-provider",
+ "onchainkit/config/supplemental-providers"
+ ]
+ },
+ {
+ "group": "Guides",
+ "pages": [
+ "onchainkit/guides/lifecycle-status",
+ "onchainkit/guides/tailwind",
+ "onchainkit/guides/themes",
+ "onchainkit/guides/use-basename-in-onchain-app",
+ "onchainkit/guides/using-ai-powered-ides",
+ "onchainkit/guides/ai-prompting-guide"
+ ]
+ },
+ {
+ "group": "Templates",
+ "pages": [
+ "onchainkit/templates/onchain-nft-app",
+ "onchainkit/templates/onchain-commerce-app",
+ "onchainkit/templates/onchain-social-profile"
+ ]
+ },
+ {
+ "group": "Components",
+ "pages": [
+ {
+ "group": "Appchain",
+ "pages": [
+ "onchainkit/appchain/bridge"
+ ]
+ },
+ {
+ "group": "Buy",
+ "pages": [
+ "onchainkit/buy/buy"
+ ]
+ },
+ {
+ "group": "Checkout",
+ "pages": [
+ "onchainkit/checkout/checkout"
+ ]
+ },
+ {
+ "group": "Earn",
+ "pages": [
+ "onchainkit/earn/earn"
+ ]
+ },
+ {
+ "group": "Fund",
+ "pages": [
+ "onchainkit/fund/fund-button",
+ "onchainkit/fund/fund-card"
+ ]
+ },
+ {
+ "group": "Identity",
+ "pages": [
+ "onchainkit/identity/identity",
+ "onchainkit/identity/address",
+ "onchainkit/identity/avatar",
+ "onchainkit/identity/badge",
+ "onchainkit/identity/identity-card",
+ "onchainkit/identity/name",
+ "onchainkit/identity/socials"
+ ]
+ },
+ {
+ "group": "Mint",
+ "pages": [
+ "onchainkit/mint/nft-card",
+ "onchainkit/mint/nft-mint-card"
+ ]
+ },
+ "onchainkit/signature/signature",
+ {
+ "group": "Swap",
+ "pages": [
+ "onchainkit/swap/swap",
+ "onchainkit/swap/swap-settings"
+ ]
+ },
+ {
+ "group": "Token",
+ "pages": [
+ "onchainkit/token/token-chip",
+ "onchainkit/token/token-image",
+ "onchainkit/token/token-row",
+ "onchainkit/token/token-search",
+ "onchainkit/token/token-select-dropdown"
+ ]
+ },
+ "onchainkit/transaction/transaction",
+ {
+ "group": "Wallet",
+ "pages": [
+ "onchainkit/wallet/wallet",
+ "onchainkit/wallet/wallet-dropdown-basename",
+ "onchainkit/wallet/wallet-dropdown-disconnect",
+ "onchainkit/wallet/wallet-dropdown-fund-link",
+ "onchainkit/wallet/wallet-dropdown-link",
+ "onchainkit/wallet/wallet-island",
+ "onchainkit/wallet/wallet-modal"
+ ]
+ }
+ ]
+ },
+ {
+ "group": "API",
+ "pages": [
+ {
+ "group": "Mint",
+ "pages": [
+ "onchainkit/api/get-token-details",
+ "onchainkit/api/get-mint-details",
+ "onchainkit/api/build-mint-transaction"
+ ]
+ },
+ {
+ "group": "Swap",
+ "pages": [
+ "onchainkit/api/build-swap-transaction",
+ "onchainkit/api/get-swap-quote"
+ ]
+ },
+ {
+ "group": "Token",
+ "pages": [
+ "onchainkit/api/get-tokens"
+ ]
+ },
+ {
+ "group": "Wallet",
+ "pages": [
+ "onchainkit/api/get-portfolios"
+ ]
+ }
+ ]
+ },
+ {
+ "group": "Utilities",
+ "pages": [
+ {
+ "group": "Config",
+ "pages": [
+ "onchainkit/config/is-base",
+ "onchainkit/config/is-ethereum"
+ ]
+ },
+ {
+ "group": "Earn",
+ "pages": [
+ "onchainkit/api/build-deposit-to-morpho-tx",
+ "onchainkit/api/build-withdraw-from-morpho-tx",
+ "onchainkit/hooks/use-build-deposit-to-morpho-tx",
+ "onchainkit/hooks/use-build-withdraw-from-morpho-tx",
+ "onchainkit/hooks/use-earn-context"
+ ]
+ },
+ {
+ "group": "Fund",
+ "pages": [
+ "onchainkit/fund/get-onramp-buy-url",
+ "onchainkit/fund/fetch-onramp-config",
+ "onchainkit/fund/fetch-onramp-quote",
+ "onchainkit/fund/fetch-onramp-options",
+ "onchainkit/fund/fetch-onramp-transaction-status",
+ "onchainkit/fund/setup-onramp-event-listeners"
+ ]
+ },
+ {
+ "group": "Identity",
+ "pages": [
+ "onchainkit/identity/get-address",
+ "onchainkit/identity/get-attestations",
+ "onchainkit/identity/get-avatar",
+ "onchainkit/identity/get-avatars",
+ "onchainkit/identity/get-name",
+ "onchainkit/identity/get-names",
+ "onchainkit/identity/use-address",
+ "onchainkit/identity/use-avatar",
+ "onchainkit/identity/use-avatars",
+ "onchainkit/identity/use-name",
+ "onchainkit/identity/use-names"
+ ]
+ },
+ {
+ "group": "Mint",
+ "pages": [
+ "onchainkit/hooks/use-token-details",
+ "onchainkit/hooks/use-mint-details"
+ ]
+ },
+ {
+ "group": "Token",
+ "pages": [
+ "onchainkit/token/format-amount"
+ ]
+ },
+ {
+ "group": "Wallet",
+ "pages": [
+ "onchainkit/wallet/is-valid-aa-entrypoint",
+ "onchainkit/wallet/is-wallet-a-coinbase-smart-wallet"
+ ]
+ }
+ ]
+ },
+ {
+ "group": "Types",
+ "pages": [
+ "onchainkit/api/types",
+ "onchainkit/appchain/types",
+ "onchainkit/checkout/types",
+ "onchainkit/config/types",
+ "onchainkit/earn/types",
+ "onchainkit/fund/types",
+ "onchainkit/identity/types",
+ "onchainkit/mint/types",
+ "onchainkit/signature/types",
+ "onchainkit/swap/types",
+ "onchainkit/token/types",
+ "onchainkit/transaction/types",
+ "onchainkit/wallet/types"
+ ]
+ },
+ {
+ "group": "Contribution",
+ "pages": [
+ "onchainkit/guides/contribution",
+ "onchainkit/guides/reporting-bug"
+ ]
+ }
+ ],
+ "global": {
+ "anchors": [
+ {
+ "anchor": "GitHub",
+ "href": "https://github.com/coinbase/onchainkit",
+ "icon": "github"
+ },
+ {
+ "anchor": "Playground",
+ "href": "https://onchainkit.xyz/playground",
+ "icon": "gamepad"
+ },
+ {
+ "anchor": "Support",
+ "href": "https://discord.com/invite/cdp",
+ "icon": "discord"
+ }
+ ]
+ }
+ },
+ {
+ "tab": "Wallet App",
+ "groups": [
+ {
+ "group": "Introduction",
+ "pages": [
+ "wallet-app/introduction/getting-started",
+ "wallet-app/introduction/mini-apps",
+ "wallet-app/introduction/beta-faq"
+ ]
+ },
+ {
+ "group": "Build with MiniKit",
+ "pages": [
+
+ "wallet-app/build-with-minikit/overview",
+ "wallet-app/build-with-minikit/quickstart",
+ "wallet-app/build-with-minikit/existing-app-integration",
+ "wallet-app/build-with-minikit/debugging"
+ ]
+ },
+ {
+ "group": "Guides",
+ "pages": [
+ "wallet-app/guides/thinking-social"
+ ]
+ }
+ ]
+ },
+ {
+ "tab": "Cookbook",
+ "groups": [
+ {
+ "group": "Use Cases",
+ "pages": [
+ "cookbook/onboard-any-user",
+ "cookbook/accept-crypto-payments",
+ "cookbook/launch-ai-agents",
+ "cookbook/launch-tokens",
+ "cookbook/deploy-a-chain",
+ "cookbook/onchain-social",
+ "cookbook/defi-your-app",
+ "cookbook/go-gasless"
+ ]
+ },
+ {
+ "group": "Build with AI",
+ "pages": [
+ "cookbook/ai-prompting",
+ "cookbook/base-builder-mcp"
+ ]
+ }
+ ]
+ },
+ {
+ "tab": "Showcase",
+ "pages": [
+ "showcase"
+ ]
+ },
+ {
+ "tab": "Learn",
+ "groups": [
+ {
+ "group": "Building Onchain",
+ "pages": [
+ "learn/welcome"
+ ]
+ },
+ {
+ "group": "Onchain Concepts",
+ "pages": [
+ "learn/onchain-concepts/core-concepts",
+ "learn/onchain-concepts/understanding-the-onchain-tech-stack",
+ {
+ "group": "Web2 vs Building Onchain",
+ "pages": [
+ "learn/onchain-concepts/building-onchain-wallets",
+ "learn/onchain-concepts/building-onchain-identity",
+ "learn/onchain-concepts/building-onchain-gas",
+ "learn/onchain-concepts/building-onchain-nodes",
+ "learn/onchain-concepts/building-onchain-frontend-development",
+ "learn/onchain-concepts/building-onchain-onramps",
+ "learn/onchain-concepts/building-onchain-social-networks",
+ "learn/onchain-concepts/building-onchain-ai"
+ ]
+ },
+ "learn/onchain-concepts/development-flow"
+ ]
+ },
+ {
+ "group": "Ethereum 101",
+ "pages": [
+ "learn/introduction-to-ethereum",
+ "learn/ethereum-dev-overview",
+ "learn/ethereum-applications",
+ "learn/gas-use-in-eth-transactions",
+ "learn/evm-diagram",
+ "learn/guide-to-base"
+ ]
+ },
+ {
+ "group": "Onchain App Development",
+ "pages": [
+ "learn/deploy-with-fleek",
+ "learn/account-abstraction",
+ "learn/cross-chain-development",
+ "learn/client-side-development"
+ ]
+ },
+ {
+ "group": "Smart Contract Development",
+ "pages": [
+ {
+ "group": "Introduction to Solidity",
+ "pages": [
+ "learn/introduction-to-solidity/introduction-to-solidity-overview",
+ "learn/introduction-to-solidity/anatomy-of-a-smart-contract-vid",
+ {
+ "group": "Introduction to Solidity",
+ "pages": [
+ "learn/introduction-to-solidity/introduction-to-solidity-vid",
+ "learn/introduction-to-solidity/solidity-overview",
+ "learn/introduction-to-solidity/introduction-to-remix-vid",
+ "learn/introduction-to-solidity/introduction-to-remix",
+ "learn/introduction-to-solidity/deployment-in-remix-vid",
+ "learn/introduction-to-solidity/deployment-in-remix"
+ ]
+ }
+ ]
+ },
+ {
+ "group": "Contracts and Basic Functions",
+ "pages": [
+ "learn/contracts-and-basic-functions/intro-to-contracts-vid",
+ "learn/contracts-and-basic-functions/hello-world-step-by-step",
+ "learn/contracts-and-basic-functions/basic-types",
+ "learn/contracts-and-basic-functions/basic-functions-exercise"
+ ]
+ },
+ {
+ "group": "Deploying to a Testnet",
+ "pages": [
+ "learn/deployment-to-testnet/overview-of-test-networks-vid",
+ "learn/deployment-to-testnet/test-networks",
+ "learn/deployment-to-testnet/deployment-to-base-sepolia-sbs",
+ "learn/deployment-to-testnet/contract-verification-sbs",
+ "learn/deployment-to-testnet/deployment-to-testnet-exercise"
+ ]
+ },
+ {
+ "group": "Control Structures",
+ "pages": [
+ "learn/control-structures/standard-control-structures-vid",
+ "learn/control-structures/loops-vid",
+ "learn/control-structures/require-revert-error-vid",
+ "learn/control-structures/control-structures",
+ "learn/control-structures/control-structures-exercise"
+ ]
+ },
+ {
+ "group": "Storage in Solidity",
+ "pages": [
+ "learn/storage/simple-storage-video",
+ "learn/storage/simple-storage-sbs",
+ "learn/storage/how-storage-works-video",
+ "learn/storage/how-storage-works",
+ "learn/storage/storage-exercise"
+ ]
+ },
+ {
+ "group": "Arrays in Solidity",
+ "pages": [
+ "learn/arrays/arrays-in-solidity-vid",
+ "learn/arrays/writing-arrays-in-solidity-vid",
+ "learn/arrays/arrays-in-solidity",
+ "learn/arrays/filtering-an-array-sbs",
+ "learn/arrays/fixed-size-arrays-vid",
+ "learn/arrays/array-storage-layout-vid",
+ "learn/arrays/arrays-exercise"
+ ]
+ },
+ {
+ "group": "The Mapping Type",
+ "pages": [
+ "learn/mappings/mappings-vid",
+ "learn/mappings/using-msg-sender-vid",
+ "learn/mappings/mappings-sbs",
+ "learn/mappings/how-mappings-are-stored-vid",
+ "learn/mappings/mappings-exercise"
+ ]
+ },
+ {
+ "group": "Advanced Functions",
+ "pages": [
+ "learn/advanced-functions/function-visibility-vid",
+ "learn/advanced-functions/function-visibility",
+ "learn/advanced-functions/function-modifiers-vid",
+ "learn/advanced-functions/function-modifiers"
+ ]
+ },
+ {
+ "group": "Structs",
+ "pages": [
+ "learn/structs/structs-vid",
+ "learn/structs/structs-sbs",
+ "learn/structs/structs-exercise"
+ ]
+ },
+ {
+ "group": "Inheritance",
+ "pages": [
+ "learn/inheritance/inheritance-vid",
+ "learn/inheritance/inheritance-sbs",
+ "learn/inheritance/multiple-inheritance-vid",
+ "learn/inheritance/multiple-inheritance",
+ "learn/inheritance/abstract-contracts-vid",
+ "learn/inheritance/abstract-contracts-sbs",
+ "learn/inheritance/inheritance-exercise"
+ ]
+ },
+ {
+ "group": "Imports",
+ "pages": [
+ "learn/imports/imports-vid",
+ "learn/imports/imports-sbs",
+ "learn/imports/imports-exercise"
+ ]
+ },
+ {
+ "group": "Errors",
+ "pages": [
+ "learn/error-triage/error-triage-vid",
+ "learn/error-triage/error-triage",
+ "learn/error-triage/error-triage-exercise"
+ ]
+ },
+ {
+ "group": "The new Keyword",
+ "pages": [
+ "learn/new-keyword/creating-a-new-contract-vid",
+ "learn/new-keyword/new-keyword-sbs",
+ "learn/new-keyword/new-keyword-exercise"
+ ]
+ },
+ {
+ "group": "Contract to Contract Interactions",
+ "pages": [
+ "learn/interfaces/intro-to-interfaces-vid",
+ "learn/interfaces/calling-another-contract-vid",
+ "learn/interfaces/testing-the-interface-vid",
+ "learn/interfaces/contract-to-contract-interaction"
+ ]
+ },
+ {
+ "group": "Events",
+ "pages": [
+ "learn/events/hardhat-events-sbs"
+ ]
+ },
+ {
+ "group": "Address and Payable",
+ "pages": [
+ "learn/address-and-payable/address-and-payable"
+ ]
+ }
+ ]
+ },
+ {
+ "group": "Development with Foundry",
+ "pages": [
+ "learn/foundry/introduction-to-foundry",
+ "learn/foundry/testing"
+ ]
+ },
+ {
+ "group": "Development with Hardhat",
+ "pages": [
+ {
+ "group": "Hardhat Setup and Overview",
+ "pages": [
+ "learn/hardhat/overview",
+ "learn/hardhat/creating-project",
+ "learn/hardhat/setup"
+ ]
+ },
+ {
+ "group": "Testing with Typescript",
+ "pages": [
+ "learn/hardhat/testing",
+ "learn/hardhat/writing-tests",
+ "learn/hardhat/contract-abi-testing",
+ "learn/hardhat/testing-guide"
+ ]
+ },
+ {
+ "group": "Etherscan",
+ "pages": [
+ "learn/hardhat/etherscan-guide",
+ "learn/hardhat/etherscan-video"
+ ]
+ },
+ {
+ "group": "Deploying Smart Contracts",
+ "pages": [
+ "learn/hardhat/installing-deploy",
+ "learn/hardhat/setup-deploy-script",
+ "learn/hardhat/testing-deployment",
+ "learn/hardhat/network-configuration",
+ "learn/hardhat/deployment",
+ "learn/hardhat/deployment-guide"
+ ]
+ },
+ {
+ "group": "Verifying Smart Contracts",
+ "pages": [
+ "learn/hardhat/verify-video",
+ "learn/hardhat/verify-guide"
+ ]
+ },
+ {
+ "group": "Mainnet Forking",
+ "pages": [
+ "learn/hardhat/fork-video",
+ "learn/hardhat/fork-guide"
+ ]
+ }
+ ]
+ },
+ {
+ "group": "Token Development",
+ "pages": [
+ {
+ "group": "Introduction to Tokens",
+ "pages": [
+ "learn/intro-to-tokens/intro-to-tokens-vid",
+ "learn/intro-to-tokens/misconceptions-about-tokens-vid",
+ "learn/intro-to-tokens/tokens-overview"
+ ]
+ },
+ {
+ "group": "Minimal Tokens",
+ "pages": [
+ "learn/minimal-tokens/creating-a-minimal-token-vid",
+ "learn/minimal-tokens/transferring-a-minimal-token-vid",
+ "learn/minimal-tokens/minimal-token-sbs",
+ "learn/minimal-tokens/minimal-tokens-exercise"
+ ]
+ },
+ {
+ "group": "ERC-20 Tokens",
+ "pages": [
+ "learn/erc-20-token/analyzing-erc-20-vid",
+ "learn/erc-20-token/erc-20-standard",
+ "learn/erc-20-token/openzeppelin-erc-20-vid",
+ "learn/erc-20-token/erc-20-testing-vid",
+ "learn/erc-20-token/erc-20-token-sbs",
+ "learn/erc-20-token/erc-20-exercise"
+ ]
+ },
+ {
+ "group": "ERC-721 Tokens",
+ "pages": [
+ "learn/erc-721-token/erc-721-standard-video",
+ "learn/erc-721-token/erc-721-standard",
+ "learn/erc-721-token/erc-721-on-opensea-vid",
+ "learn/erc-721-token/openzeppelin-erc-721-vid",
+ "learn/erc-721-token/implementing-an-erc-721-vid",
+ "learn/erc-721-token/erc-721-sbs",
+ "learn/erc-721-token/erc-721-exercise"
+ ]
+ }
+ ]
+ },
+ {
+ "group": "Exercise Contracts",
+ "pages": [
+ "learn/exercise-contracts"
+ ]
+ }
+ ]
+ }
+ ]
+ },
+ "logo": {
+ "light": "/logo/logo_light.svg",
+ "dark": "/logo/logo_dark.svg"
+ },
+ "navbar": {
+ "links": [
+ {
+ "label": "Blog",
+ "href": "https://blog.base.dev/"
+ },
+ {
+ "label": "GitHub",
+ "href": "https://github.com/base"
+ },
+ {
+ "label": "Support",
+ "href": "https://discord.com/invite/base"
+ }
+ ],
+ "primary": {
+ "type": "button",
+ "label": "Base.org",
+ "href": "https://base.org"
+ }
+ },
+ "footer": {
+ "socials": {
+ "x": "https://x.com/mintlify",
+ "github": "https://github.com/mintlify",
+ "linkedin": "https://linkedin.com/company/mintlify"
+ }
+ }
+}
\ No newline at end of file
diff --git a/docs/footer.tsx b/docs/footer.tsx
deleted file mode 100644
index e679c1af..00000000
--- a/docs/footer.tsx
+++ /dev/null
@@ -1,26 +0,0 @@
-export default function Footer() {
- return (
-
- )
-}
diff --git a/docs/get-started/ai-prompting.mdx b/docs/get-started/ai-prompting.mdx
new file mode 100644
index 00000000..6c5725ec
--- /dev/null
+++ b/docs/get-started/ai-prompting.mdx
@@ -0,0 +1,9 @@
+---
+sidebarTitle: AI-powered IDEs
+title: Use AI-powered IDEs
+description: How to use AI-powered IDEs to generate code for OnchainKit.
+---
+
+import AiPowered from "/snippets/ai-powered.mdx";
+
+
+
+
+
+## Base Offers
+
+
+
+**Payments & Financial Services:** Move value globally with sub-second, sub-cent payments and build on existing financial services for trading, yield generation, and more.
+
+
+**Creator Monetization:** Creators of all kinds are exploring new ways to monetize their work. Innovate on the frontier of creator monetiziation with the creator economy on Base.
+
+
+**Comprehensive Builder Support:** Base provides developer tools, infrastructure, and support. Plus, Base has one of the largest onchain builder communities whith which you can collaborate and grow.
+
+
+**Launch to real users:** Tap Base activations, grants, and mini-app channels that surface your project to millions.
+
+
+
+
+### Start Building
+
+
+
+ Build and deploy your app in minutes.
+
+
+ Launch a new token.
+
+
+ Deploy your own chain on Base.
+
+
+
+Explore [all products](/get-started/products) and [use cases](/get-started/use-cases).
+
+### Get Funded
+
+
+
+ Get rewarded up to 2 ETH weekly through the Builder Rewards Program.
+
+
+ Apply for fast, retroactive, Base Builder Grants (~1-5 ETH).
+
+
+ A global program for builders creating the next wave of onchain apps.
+
+
+ Apply for OP Retro Funding for your contributions to the Base ecosystem.
+
+
+
+### Reach More Users
+
+
+
+ Mini Apps run directly inside the social feed: Make your existing app a Mini App or build a new one.
+
+
+ Showcase your project to the Base community and get discovered.
+
+
+
+
+
+
diff --git a/docs/get-started/build-app.mdx b/docs/get-started/build-app.mdx
new file mode 100644
index 00000000..a2f2ab91
--- /dev/null
+++ b/docs/get-started/build-app.mdx
@@ -0,0 +1,250 @@
+---
+title: Build an App
+description: A guide to building a next.js app on Base using OnchainKit
+---
+
+Welcome to the Base quickstart guide! In this walkthrough, we'll create a simple onchain app from start to finish. Whether you're a seasoned developer or just starting out, this guide has got you covered.
+
+## What You'll Achieve
+
+By the end of this quickstart, you'll have built an onchain app by:
+
+- Configuring your development environment
+- Deploying your smart contracts to Base
+- Interacting with your deployed contracts from the frontend
+
+Our simple app will be an onchain tally app which lets you add to a total tally, stored onchain, by pressing a button.
+
+
+**Why Base?**
+
+Base is a fast, low-cost, builder-friendly Ethereum L2 built to bring the next billion users onchain. By following this guide, you'll join a vibrant ecosystem of developers, creators, and innovators who are building a global onchain economy.
+
+
+
+## Set Up Your Development Environment
+
+
+
+ OnchainKit is a library of ready-to-use React components and Typescript utilities for building onchain apps. Run the following command in your terminal and follow the prompts to bootstrap your project.
+
+ ```bash [Terminal]
+ npm create onchain@latest
+ ```
+
+ The prompots will ask you for a CDP API Key which you can get [here](https://portal.cdp.coinbase.com/projects/api-keys/client-key).
+
+ Once you've gone through the prompts, you'll have a new project directory with a basic OnchainKit app. Run the following to see it live.
+
+ ```bash [Terminal]
+ cd my-onchainkit-app
+ npm install
+ npm run dev
+ ```
+
+ You should see the following screen.
+
+
+
+
+
+ Once we've deployed our contracts, we'll add a button that lets us interact with our contracts.
+
+
+
+ The total tally will be stored onchain in a smart contract. We'll use the Foundry framework to deploy our contract to the Base Sepolia testnet.
+
+ 1. Create a new "contracts" folder in the root of your project
+
+ ```bash [Terminal]
+ mkdir contracts && cd contracts
+ ```
+
+ 2. Install and initialize Foundry
+
+ ```bash [Terminal]
+ curl -L https://foundry.paradigm.xyz | bash
+ foundryup
+ forge init --no-git
+ ```
+
+ Open the project and find the `Counter.sol` contract file in the `/contracts/src` folder. You'll find the simple logic for our tally app.
+
+
+ **--no-git**
+
+ Because `contracts` is a folder in our project, we don't want to initialize a separate git repository for it, so we add the `--no-git` flag.
+
+
+
+ To deploy your smart contracts to Base, you need two key components:
+
+ 1. A node connection to interact with the Base network
+ 2. A funded private key to deploy the contract
+
+ Let's set up both of these:
+
+ - Create a `.env` file in your `contracts` directory and add the Base and Base Sepolia RPC URLs
+
+ ```bash [contracts/.env]
+ BASE_RPC_URL="https://mainnet.base.org"
+ BASE_SEPOLIA_RPC_URL="https://sepolia.base.org"
+ ```
+
+ -Load your environment variables
+
+ ```bash [Terminal]
+ source .env
+ ```
+
+
+ **Base Sepolia**
+
+ Base Sepolia is the test network for Base, which we will use for the rest of this guide. You can obtain free Base Sepolia ETH from one of the [faucets listed here](/base-chain/tools/network-faucets).
+
+
+
+ A private key with testnet funds is required to deploy the contract. You can generate a fresh private key [here](https://visualkey.link/).
+
+ 1. Store your private key in Foundry's secure keystore
+
+ ```bash [Terminal]
+ cast wallet import deployer --interactive
+ ```
+
+ 2. When prompted enter your private key and a password.
+
+ Your private key is stored in `~/.foundry/keystores` which is not tracked by git.
+
+
+ Never share or commit your private key. Always keep it secure and handle with care.
+
+
+
+
+## Deploy Your Contracts
+
+Now that your environment is set up, let's deploy your contracts to Base Sepolia. The foundry project provides a deploy script that will deploy the Counter.sol contract.
+
+
+
+ 1. Use the following command to compile and deploy your contract
+
+ ```bash [Terminal]
+ forge create ./src/Counter.sol:Counter --rpc-url $BASE_SEPOLIA_RPC_URL --account deployer
+ ```
+
+ Note the format of the contract being deployed is `:`.
+
+
+ After successful deployment, the transaction hash will be printed to the console output
+
+ Copy the deployed contract address and add it to your `.env` file
+
+ ```bash
+ COUNTER_CONTRACT_ADDRESS="0x..."
+ ```
+
+
+
+ ```bash [Terminal]
+ source .env
+ ```
+
+
+ To ensure your contract was deployed successfully:
+
+ 1. Check the transaction on [Sepolia Basescan](https://sepolia.basescan.org/).
+ 2. Use the `cast` command to interact with your deployed contract from the command line
+
+ ```bash
+ cast call $COUNTER_CONTRACT_ADDRESS "number()(uint256)" --rpc-url $BASE_SEPOLIA_RPC_URL
+ ```
+
+ This will return the initial value of the Counter contract's `number` storage variable, which will be `0`.
+
+
+
+**Congratulations! You've deployed your smart contract to Base Sepolia!**
+
+Now lets connect the frontend to interact with your recently deployed contract.
+
+## Interacting with your contract
+
+To interact with the smart contract logic, we need to submit an onchain transaction. We can do this easily with the `Transaction` component. This is a simplified version of the `Transaction` component, designed to streamline the integration process. Instead of manually defining each subcomponent and prop, we can use this shorthand version which renders our suggested implementation of the component and includes the `TransactionButton` and `TransactionToast` components.
+
+
+
+ Lets add the `Transaction` component to our `page.tsx` file. Delete the existing content in the `main` tag and replace it with the snippet below.
+
+ ```tsx twoslash [page.tsx]
+ // @noErrors: 2307 - Cannot find module '@/calls'
+ import { Transaction } from '@coinbase/onchainkit/transaction';
+ import { calls } from '@/calls';
+
+
+ ;
+ ```
+
+
+ In the previous code snippet, you'll see we imported `calls` from the `calls.ts` file. This file provides the details needed to interact with our contract and call the `increment` function. Create a new `calls.ts` file in the same folder as your `page.tsx` file and add the following code.
+
+ ```ts twoslash [calls.ts]
+ const counterContractAddress = '0x...'; // add your contract address here
+ const counterContractAbi = [
+ {
+ type: 'function',
+ name: 'increment',
+ inputs: [],
+ outputs: [],
+ stateMutability: 'nonpayable',
+ },
+ ] as const;
+
+ export const calls = [
+ {
+ address: counterContractAddress,
+ abi: counterContractAbi,
+ functionName: 'increment',
+ args: [],
+ },
+ ];
+ ```
+
+
+ **Contract Address**
+
+ The `calls.ts` file contains the details of the contract interaction, including the contract address, which we saved in the previous step.
+
+
+
+ Now, when you connect a wallet and click on the `Transact` button and approve the transaction, it will increment the tally onchain by one.
+
+ We can verify that the onchain count took place onchain by once again using `cast` to call the `number` function on our contract.
+
+ ```bash [Terminal]
+ cast call $COUNTER_CONTRACT_ADDRESS "number()(uint256)" --rpc-url $BASE_SEPOLIA_RPC_URL
+ ```
+
+ If the transaction was successful, the tally should have incremented by one!
+
+
+
+We now have a working onchain tally app! While the example is simple, it illustrates the end to end process of building on onchain app. We:
+
+- Configured a project with frontend and onchain infrastructure
+- Deployed a smart contract to Base Sepolia
+- Interacted with the contract from the frontend
+
+## Further Improvements
+
+This is just the beginning. There are many ways we can improve upon this app. For example, we could:
+
+- Make the `increment` transaction gasless by integrating with [Paymaster](/onchainkit/transaction/transaction#sponsor-with-paymaster-capabilities)
+- Improve the wallet connection and sign up flow with the [WalletModal](/onchainkit/wallet/wallet-modal) component
+- Add onchain [Identity](/onchainkit/identity/identity) so we know who added the most recent tally
diff --git a/docs/get-started/concepts.mdx b/docs/get-started/concepts.mdx
new file mode 100644
index 00000000..748c81ca
--- /dev/null
+++ b/docs/get-started/concepts.mdx
@@ -0,0 +1,13 @@
+---
+title: 'Core Concepts'
+---
+
+Key concept overview:
+- Gas & Faucets
+- Blocks
+- Transactions
+- Signatures
+- Smart Contracts
+- Wallets
+- Nodes
+...
\ No newline at end of file
diff --git a/docs/get-started/deploy-chain.mdx b/docs/get-started/deploy-chain.mdx
new file mode 100644
index 00000000..4f8ff591
--- /dev/null
+++ b/docs/get-started/deploy-chain.mdx
@@ -0,0 +1,286 @@
+---
+title: 'Deploy an Appchain'
+keywords: ['deploy a chain', 'deploy a base chain', 'deploy a base appchain', 'deploy a base l3', 'l3']
+---
+
+Transform your high-traffic application into a dedicated blockchain with **1-second block times**, **sub-cent transactions**, and **enterprise-grade infrastructure**. Base Appchains provide dedicated blockspace for mature applications that need to scale beyond shared network limitations.
+
+
+
+Get early access to Base Appchains and transform your scaling strategy
+
+
+
+Jump to our step-by-step onboarding process
+
+
+
+## What Are Base Appchains?
+
+Base Appchains are **app-specific Layer 3 rollups** built on Base that provide dedicated blockspace for individual applications. Instead of competing with thousands of other apps for network resources, you get your own high-performance blockchain that rolls up to Base and inherits Ethereum's security.
+
+
+Layer 3 appchains roll up to Base (Layer 2), which settles on Ethereum, providing you with dedicated performance while maintaining the security guarantees of the Ethereum ecosystem.
+
+
+Think of it as the difference between **sharing a highway during rush hour** versus **having your own dedicated express lane**. With shared blockspace, your app's performance depends on network-wide activity. With an Appchain, you get consistent, predictable performance regardless of what's happening elsewhere.
+
+
+
+Compete with other apps for network resources, leading to variable performance, unpredictable costs, and user experience issues during peak times.
+
+
+
+Your own infrastructure with predictable performance, custom gas tokens, full control over throughput, and consistent user experience.
+
+
+
+## Why Choose Base Appchains?
+
+### High-Speed Performance Built for Scale
+
+Stop letting network congestion impact your user experience. Base Appchains deliver **1-second block times** and **sub-10 second withdrawals**, making them 10x faster than typical blockchain interactions.
+
+
+Gaming applications like Blocklords have processed over 80 million transactions across 1.8 million wallets using Base Appchains, achieving the scale needed for their gaming ecosystem without performance degradation.
+
+
+### Predictable, Cost-Effective Operations
+
+Replace unpredictable gas costs with **fixed monthly pricing**. Process transactions for fractions of cents while eliminating the need to sponsor gas costs for your users.
+
+
+
+Variable gas costs, expensive user onboarding, unpredictable operational expenses, and complex gas sponsorship management.
+
+
+
+Fixed monthly pricing, sub-cent transactions, predictable budgeting, and no gas sponsorship complexity.
+
+
+
+### Enterprise-Grade Infrastructure
+
+With Base Appchains, you get:
+
+
+Fully-managed sequencer and node infrastructure
+
+
+Automated maintenance and upgrades
+
+
+Real-time monitoring and performance alerts
+
+
+Dedicated block explorer for your chain
+
+
+### Seamless Base Ecosystem Integration
+
+Maintain access to Base's **users**, **liquidity**, and **developer tools** while getting dedicated performance. Your Appchain integrates seamlessly with Smart Wallet, Paymaster, OnchainKit, and other Base ecosystem tools.
+
+
+
+Enable seamless account abstraction across Base Mainnet and your Appchain with unified user experiences.
+
+
+
+Sponsor gas costs across multiple chains with unified billing and simplified user onboarding.
+
+
+
+Use the same familiar developer tools and components across the entire Base ecosystem.
+
+
+
+## Technical Architecture
+
+Base Appchains are built on the **OP Enclave framework**, providing fast withdrawals and seamless integration with Base Mainnet. This architecture enables near-instant bridging while maintaining security through innovative proving mechanisms.
+
+
+
+Built on Optimism's latest technology for **near-instant bridging** between your Appchain and Base Mainnet. Users can move funds in seconds rather than the typical 7-day withdrawal periods of traditional rollups.
+
+
+
+Uses **Amazon S3** for cost-efficient data storage while maintaining security through **AWS Nitro Enclave** verification. This approach significantly reduces costs while ensuring data integrity and availability.
+
+
+
+Control which contracts can be called on your chain, effectively managing blockspace allocation. Implement **custom gas tokens** and **permission systems** while protecting users from censorship through guaranteed deposit lanes.
+
+
+
+Unlike traditional rollups that rely on challenge periods, Base Appchains use **immediate state proving** through secure enclaves, enabling instant finality and faster user experiences.
+
+
+
+## Use Cases & Success Stories
+
+Base Appchains power applications across gaming, DeFi, and enterprise sectors that require high performance and predictable costs.
+
+
+
+Process millions of micro-transactions for in-game actions, NFT trades, and player interactions without network congestion affecting gameplay performance.
+
+**Success Story**: Super Champs chose Base Appchains for consistent throughput, comparing the experience to "gaming on iOS" - smooth, predictable, and reliable.
+
+
+
+Handle high-frequency trading, yield farming, and complex financial operations with consistent, low-cost transactions that don't fluctuate with network activity.
+
+**Success Story**: Applications processing high-volume trading data benefit from predictable costs and dedicated throughput for time-sensitive operations.
+
+
+
+Deploy compliance-ready solutions with dedicated infrastructure, custom permissions, and the ability to manage access controls while maintaining transparency.
+
+**Success Story**: Proof 8 uses blockchain technology for verifiable inventory ownership in warehouses and distilleries, where enterprise customers prioritize performance, security, and privacy.
+
+
+
+
+Base Appchains are designed for **mature projects** with significant transaction volumes. If you're just starting out or have low transaction volumes, consider building on Base Mainnet first to establish product-market fit.
+
+
+## When Should You Consider an Appchain?
+
+Base Appchains are ideal for applications that have outgrown shared blockspace limitations. Use this checklist to determine if an Appchain is right for your project:
+
+
+**High Transaction Volume**: Your app generates thousands of transactions daily and performance is affected by network congestion
+
+
+
+**Significant Gas Sponsorship**: You're spending substantial amounts sponsoring gas costs for users through Paymaster or similar solutions
+
+
+
+**Performance-Critical Operations**: User experience is negatively impacted by variable transaction times or network congestion
+
+
+
+**Custom Requirements**: You need custom gas tokens, specialized permissions, or governance mechanisms not available on shared chains
+
+
+
+**Predictable Costs**: Fixed operational costs are important for your business model and budgeting
+
+
+
+If you're considering launching your own L1 or L2 blockchain, Base Appchains offer a compelling alternative with faster time-to-market, proven infrastructure, and immediate access to Base's ecosystem.
+
+
+
+## Getting Started
+
+Base Appchains are currently in **beta with a waitlist**. We're working with select partners to refine the platform before broader availability.
+
+
+
+Complete our application form to be considered for early access to Base Appchains. We prioritize applications from mature projects with clear scaling needs.
+
+
+Join the Base Appchains beta program
+
+
+
+
+Our team will review your application and schedule a consultation to understand your specific scaling requirements, transaction patterns, and technical needs.
+
+
+During the consultation, we'll help you determine if an Appchain is the right solution and design the optimal configuration for your use case.
+
+
+
+
+Once approved, you'll receive access to both testnet and mainnet features. Start with the **$1/month testnet** to validate your architecture and integration.
+
+
+Use the testnet environment to test bridging, custom gas tokens, and permission systems before deploying to mainnet.
+
+
+
+
+Deploy to production with full enterprise support, monitoring, and maintenance included. Our team provides ongoing support for your Appchain infrastructure.
+
+
+Full technical support during launch and ongoing operations
+
+
+
+
+
+**Coming Soon**: Self-serve, one-click deployment will be available for approved projects, making it even easier to launch and manage your Appchain.
+
+
+## Frequently Asked Questions
+
+
+
+Base Appchains offer significant advantages over launching independent blockchain infrastructure:
+
+- **Faster time-to-market**: Deploy in weeks, not months or years
+- **Proven infrastructure**: Built on battle-tested Base and OP Stack technology
+- **Immediate ecosystem access**: Users and liquidity from Base Mainnet
+- **Lower operational overhead**: Fully managed infrastructure and maintenance
+- **Ethereum alignment**: Inherit security without custom validator sets or consensus mechanisms
+
+
+
+Base Appchains provide **seamless onboarding** similar to Base Mainnet applications:
+
+- Users can bridge funds between Base and your Appchain in **seconds**
+- Same wallet experience across Base ecosystem
+- Smart Wallet integration for account abstraction
+- Familiar transaction patterns and interfaces
+
+
+
+**Coinbase manages the core infrastructure** on your behalf, including:
+
+- Sequencer operation and maintenance
+- Node infrastructure and upgrades
+- Security key management
+- Monitoring and alerting systems
+
+You maintain control over **application-level configurations** like gas tokens, permissions, and governance while benefiting from enterprise-grade infrastructure management.
+
+
+
+Base Appchains use the **OP Enclave framework** for **near-instant bridging**:
+
+- Move funds between Base and your Appchain in seconds
+- No 7-day withdrawal periods like traditional rollups
+- Maintains security through cryptographic proofs
+- Seamless user experience across chains
+
+
+
+Base Appchains balance **operational efficiency** with **censorship resistance**:
+
+- Custom permissions control high-throughput operations
+- **Guaranteed deposit lanes** prevent censorship through direct Base deposits
+- Users always have recourse through the Base bridge
+- Inherits Ethereum's long-term decentralization roadmap
+
+
+
+## Ready to Scale?
+
+Base Appchains represent the next evolution in blockchain scaling, providing dedicated infrastructure without sacrificing ecosystem benefits. Whether you're processing millions of gaming transactions, handling high-frequency DeFi operations, or building enterprise solutions, Appchains deliver the performance and predictability your users expect.
+
+
+
+Apply for early access to Base Appchains beta program
+
+
+
+Discover the full ecosystem of Base developer tools and integrations
+
+
+
+
+**Next Steps**: After joining the waitlist, explore Base's developer documentation to understand how Appchains integrate with Smart Wallet, Paymaster, OnchainKit, and other ecosystem tools.
+
\ No newline at end of file
diff --git a/docs/get-started/deploy-smart-contracts.mdx b/docs/get-started/deploy-smart-contracts.mdx
new file mode 100644
index 00000000..a40e43d5
--- /dev/null
+++ b/docs/get-started/deploy-smart-contracts.mdx
@@ -0,0 +1,144 @@
+---
+title: 'Deploy Smart Contracts'
+description: A guide to help you get started with deploying your smart contracts on Base.
+---
+
+Welcome to the Base deployment quickstart guide! This comprehensive walkthrough will help you set up your environment and deploy smart contracts on Base. Whether you're a seasoned developer or just starting out, this guide has got you covered.
+
+## What You'll Achieve
+
+By the end of this quickstart, you'll be able to:
+
+- Set up your development environment to deploy on Base
+- Deploy your smart contracts to Base
+- Connect your frontend to your smart contracts
+
+
+**Why Base?**
+
+Base is a fast, low-cost, builder-friendly Ethereum L2 built to bring the next billion users onchain. By following this guide, you'll join a vibrant ecosystem of developers, creators, and innovators who are building a global onchain economy.
+
+
+
+## Set Up Your Development Environment
+
+1. Create a new project directory
+
+```bash
+mkdir my-base-project && cd my-base-project
+```
+
+2. Install Foundry, a powerful framework for smart contract development
+
+```bash
+curl -L https://foundry.paradigm.xyz | bash
+foundryup
+```
+
+This installs Foundry and updates it to the latest version.
+
+3. Initialize a new Solidity project
+
+```bash
+forge init
+```
+
+Your Foundry project is now ready. You'll find an example contract in the `src` directory, which you can replace with your own contracts. For the purposes of this guide, we'll use the Counter contract provided in `/src/Counter.sol`
+
+
+Foundry provides a suite of tools for Ethereum application development, including Forge (for testing), Cast (for interacting with the chain), and Anvil (for setting up a local node). You can learn more about Foundry [here](https://book.getfoundry.sh/).
+
+
+
+## Configure Foundry with Base
+
+To deploy your smart contracts to Base, you need two key components:
+
+1. A node connection to interact with the Base network
+2. A funded private key to deploy the contract
+
+Let's set up both of these:
+
+### 1. Set up your node connection
+
+1. Create a `.env` file in your project's root directory
+2. Add the Base network RPC URL to your `.env` file
+
+```bash
+BASE_RPC_URL="https://mainnet.base.org"
+BASE_SEPOLIA_RPC_URL="https://sepolia.base.org"
+```
+
+3. Load your environment variables
+
+```bash
+source .env
+```
+
+
+Base Sepolia is the test network for Base, which we will use for the rest of this guide. You can obtain free Base Sepolia ETH from one of the [faucets listed here](/base-chain/tools/network-faucets).
+
+
+
+### 2. Secure your private key
+
+1. Store your private key in Foundry's secure keystore
+
+```bash
+cast wallet import deployer --interactive
+```
+
+2. When prompted enter your private key and a password.
+
+Your private key is stored in `~/.foundry/keystores` which is not tracked by git.
+
+
+Never share or commit your private key. Always keep it secure and handle with care.
+
+
+
+## Deploy Your Contracts
+
+Now that your environment is set up, let's deploy your contracts to Base Sepolia.
+
+1. Use the following command to compile and deploy your contract
+
+```bash
+forge create ./src/Counter.sol:Counter --rpc-url $BASE_SEPOLIA_RPC_URL --account deployer
+```
+
+Note the format of the contract being deployed is `:`.
+
+2. After successful deployment, the transaction hash will be printed to the console output
+
+3. Copy the deployed contract address and add it to your `.env` file
+
+```bash
+COUNTER_CONTRACT_ADDRESS="0x..."
+```
+
+4. Load the new environment variable
+
+```bash
+source .env
+```
+
+### Verify Your Deployment
+
+To ensure your contract was deployed successfully:
+
+1. Check the transaction on [Sepolia Basescan](https://sepolia.basescan.org/).
+2. Use the `cast` command to interact with your deployed contract from the command line
+
+```bash
+cast call $COUNTER_CONTRACT_ADDRESS "number()(uint256)" --rpc-url $BASE_SEPOLIA_RPC_URL
+```
+This will return the initial value of the Counter contract's `number` storage variable, which will be `0`.
+
+**Congratulations! You've deployed your smart contracts to Base Sepolia!**
+
+## Next Steps
+
+- Use [Onchainkit](https://onchainkit.com) to connect your frontend to your contracts! Onchainkit is a library of ready-to-use React components and Typescript utilities.
+- Learn more about interacting with your contracts in the command line using Foundry from our [Foundry tutorial](/cookbook/smart-contract-development/foundry/deploy-with-foundry).
+
diff --git a/docs/get-started/get-funded.mdx b/docs/get-started/get-funded.mdx
new file mode 100644
index 00000000..19dc73b0
--- /dev/null
+++ b/docs/get-started/get-funded.mdx
@@ -0,0 +1,205 @@
+---
+title: 'Get Funded'
+description: "The Base ecosystem offers multiple funding pathways designed specifically for builders at every stage—from weekend experiments to full-scale ventures."
+---
+
+## Funding Pathways
+
+Whether you're just starting to experiment or ready to become a full-time founder, Base provides structured funding opportunities that grow with your ambitions. Each pathway is designed for different stages of your builder journey, with clear progression paths between programs.
+
+
+
+ 2 ETH in weekly rewards for prototypes and experiments through Talent Protocol.
+
+
+
+ Fast, retroactive grants ranging from 1-5 ETH. Perfect for shipped projects ready to scale.
+
+
+
+ Get rewarded for creating public goods that benefit the entire Base ecosystem.
+
+
+
+ Comprehensive founder program with mentorship, resources, and significant funding opportunities.
+
+
+
+## Before You Apply
+
+
+
+ Deploy your project to Base mainnet. Some programs will consider early prototypes and testnet deployments but being deployed on Base mainnet gives you a leg up.
+
+
+ Verify your contract is deployed and functional on Base.
+
+
+
+
+ Create clear documentation including setup instructions, project goals, and demo materials.
+
+
+ Ensure your README includes installation steps and your project has a working demo.
+
+
+
+
+ Measure relevant metrics like user adoption, transaction volume, or community engagement.
+
+
+ Even small metrics matter. Early usage data strengthens your application significantly.
+
+
+
+
+## Weekly Rewards: Start Building Today
+
+The Builder Rewards Program distributes 2 ETH weekly to active builders—perfect for experimentation and learning.
+
+[Join Builder Rewards Program](https://www.builderscore.xyz/)
+
+### How It Works
+1. Build anything on Base (prototypes welcome)
+2. Share your progress on social media
+3. Earn weekly rewards based on activity
+4. No minimum project size required
+
+
+Prototyping counts! Early-stage projects and experiments are explicitly encouraged.
+
+
+### Perfect For
+- First-time Base builders learning the ecosystem
+- Developers experimenting with new ideas
+- Weekend projects and hackathon submissions
+- Educational content creation
+
+
+Most successful Base builders started with weekly rewards while learning. Use this as your entry point to the ecosystem.
+
+
+## Builder Grants: Live on Base
+
+Need funding for your shipped project? Base Builder Grants offer retroactive funding for projects that demonstrate real value to the ecosystem.
+
+[Apply for Builder Grants](https://paragraph.com/@grants.base.eth/calling-based-builders)
+
+### What You Get
+- **Grant Range:** 1-5 ETH
+- **Application Type:** Retroactive (for shipped projects)
+
+
+
+Already have a working prototype? You're ready to apply. Builder Grants reward shipped code over perfect pitches.
+
+
+## OP Retro Funding: Long-term Impact
+
+Creating tools, infrastructure, or resources that benefit everyone? OP Retro Funding recognizes and rewards public goods contributions to the Base ecosystem.
+
+[Track Your Impact on Atlas](https://atlas.optimism.io/)
+
+### Ideal Projects
+- Open-source libraries and development frameworks
+- Community tools and ecosystem infrastructure
+- Analytics dashboards and ecosystem insights
+
+### Funding Approach
+- **Focus:** Public goods and ecosystem-wide impact
+- **Recognition:** Both funding and ecosystem acknowledgment
+
+### Application Process
+
+
+
+ Create tools, content, or infrastructure that benefits the entire Base community.
+
+
+ Ensure your project is open-source and publicly accessible.
+
+
+
+
+ Track usage metrics, community adoption, and ecosystem benefits.
+
+
+ Include testimonials from other builders who've used your tools.
+
+
+
+
+ Use the Optimism Atlas platform to track contributions and apply for funding.
+
+
+ Complete your Atlas profile with detailed project information.
+
+
+
+
+## Base Batches: The Founder Track
+
+For builders ready to become founders, Base Batches provides the most comprehensive support system in the ecosystem. This recurring initiative combines structured development, mentorship, and significant funding opportunities.
+
+[Learn More About Base Batches](https://basebatches.xyz)
+
+### Program Structure
+
+
+
+ Rapid development sprint with direct access to mentorship and technical resources from the Base team.
+
+
+ Complete your MVP and receive detailed technical feedback from Base core team members.
+
+
+
+
+ 4-week structured support to refine your product, validate your market, and develop your business model.
+
+
+ Achieve product-market fit indicators and prepare comprehensive pitch materials.
+
+
+
+
+ Present to top-tier investors including Coinbase Ventures and other leading crypto VCs.
+
+
+ Secure follow-on funding commitments from investor network.
+
+
+
+
+### What Each Cohort Receives
+- **Direct mentorship** from Base team members and industry experts
+- **Access to exclusive resources** including technical infrastructure and partnerships
+- **Investor introductions** to Coinbase Ventures and leading crypto funds
+- **Deep ecosystem integration** with Base protocol and community
+
+
+Base Batches #001 is currently in progress. The next Base Batches will be announced in the second half of 2025.
+
+
+## Get Started Today
+
+Building something on Base? The ecosystem is ready to support you at every stage of your journey.
+
+
+The best builders in Base started exactly where you are now. Most successful applicants begin with smaller programs and progress to larger opportunities.
+
+
+### Your Next Steps
+
+1. **Choose your starting point** based on your current project stage
+2. **Join the Base community** on Discord and social media
+3. **Start building** and documenting your progress
+4. **Apply to your selected program** with confidence
+
+
+Don't wait for the "perfect" project. The Base ecosystem values builders at all stages. Start where you are and grow with the community's support.
+
+
+Remember: Whether you're tinkering with a weekend project or building the next breakthrough application, there's a funding path designed for your journey. The Base ecosystem has invested millions in builders who started with nothing more than an idea and the determination to build.
+
+**Take the first step today.**
\ No newline at end of file
diff --git a/docs/get-started/launch-token.mdx b/docs/get-started/launch-token.mdx
new file mode 100644
index 00000000..aa3402cd
--- /dev/null
+++ b/docs/get-started/launch-token.mdx
@@ -0,0 +1,423 @@
+---
+title: 'Launch a Token'
+---
+
+
+Launching a token on Base can be accomplished through multiple approaches, from no-code platforms to custom smart contract development. This guide helps you choose the right method and provides implementation details for both approaches.
+
+
+
+ Use existing platforms like Zora, Clanker, or Flaunch for quick deployment
+
+
+ Build custom ERC-20 tokens with Foundry for maximum control
+
+
+ Decision framework to help you pick the right method
+
+
+ Security, community building, and post-launch guidance
+
+
+
+
+**For most users:** Use existing token launch platforms like Zora, Clanker, or Flaunch. These tools handle the technical complexity while providing unique features for different use cases.
+
+**For developers:** Build custom ERC-20 tokens using Foundry and OpenZeppelin's battle-tested contracts for maximum control and customization.
+
+
+## Choosing Your Launch Approach
+
+### Platform-Based Launch (Recommended for Most Users)
+
+Choose a platform when you want:
+- Quick deployment without coding
+- Built-in community features
+- Automated liquidity management
+- Social integration capabilities
+
+### Custom Development (For Developers)
+
+Build your own smart contract when you need:
+- Custom tokenomics or functionality
+- Full control over contract behavior
+- Integration with existing systems
+- Advanced security requirements
+
+## Token Launch Platforms on Base
+
+### Zora
+**Best for:** Content creators and social tokens
+
+Zora transforms every post into a tradeable ERC-20 token with automatic Uniswap integration. Each post becomes a "coin" with 1 billion supply, creators receive 10 million tokens, and earn 1% of all trading fees.
+
+**Key Features:**
+- Social-first token creation
+- Automatic liquidity pools
+- Revenue sharing for creators
+- Built-in trading interface
+
+[Get started with Zora →](https://zora.co)
+
+### Clanker
+**Best for:** Quick memecoin launches via social media
+
+Clanker is an AI-driven token deployment tool that operates through Farcaster. Users can create ERC-20 tokens on Base by simply tagging @clanker with their token concept.
+
+**Key Features:**
+- AI-powered automation
+- Social media integration via Farcaster
+- Instant deployment
+- Community-driven discovery
+
+[Get started with Clanker →](https://warpcast.com) or visit [clanker.world](https://clanker.world)
+
+### Flaunch
+**Best for:** Advanced memecoin projects with sophisticated tokenomics
+
+Flaunch leverages Uniswap V4 to enable programmable revenue splits, automated buybacks, and Progressive Bid Walls for price support. Creators can customize fee distributions and treasury management.
+
+**Key Features:**
+- Programmable revenue sharing
+- Automated buyback mechanisms
+- Progressive Bid Wall technology
+- Treasury management tools
+
+[Get started with Flaunch →](https://flaunch.gg)
+
+## Technical Implementation with Foundry
+
+For developers who want full control over their token implementation, here's how to create and deploy a custom ERC-20 token on Base using Foundry.
+
+
+Before launching a custom developed token to production, always conduct security reviews by expert smart contract developers.
+
+
+### Prerequisites
+
+
+
+ Install Foundry on your system:
+ ```bash Terminal
+ curl -L https://foundry.paradigm.xyz | bash
+ foundryup
+ ```
+ For detailed installation instructions, see the [Foundry documentation](https://book.getfoundry.sh/getting-started/installation).
+
+
+ Obtain Base Sepolia ETH for testing from the [Base Faucet](https://docs.base.org/docs/tools/network-faucets)
+
+
+ Configure your wallet and development tools for Base testnet deployment
+
+
+
+### Project Setup
+
+Initialize a new Foundry project and clean up template files:
+
+```bash Terminal
+# Create new project
+forge init my-token-project
+cd my-token-project
+
+# Remove template files we don't need
+rm src/Counter.sol script/Counter.s.sol test/Counter.t.sol
+```
+
+Install OpenZeppelin contracts for secure, audited ERC-20 implementation:
+
+```bash Terminal
+# Install OpenZeppelin contracts library
+forge install OpenZeppelin/openzeppelin-contracts
+```
+
+### Smart Contract Development
+
+Create your token contract using OpenZeppelin's ERC-20 implementation:
+
+```solidity src/MyToken.sol
+// SPDX-License-Identifier: MIT
+pragma solidity ^0.8.19;
+
+import "@openzeppelin/contracts/token/ERC20/ERC20.sol";
+import "@openzeppelin/contracts/access/Ownable.sol";
+
+/**
+ * @title MyToken
+ * @dev ERC-20 token with minting capabilities and supply cap
+ */
+contract MyToken is ERC20, Ownable {
+ // Maximum number of tokens that can ever exist
+ uint256 public constant MAX_SUPPLY = 1_000_000_000 * 10**18; // 1 billion tokens
+
+ constructor(
+ string memory name,
+ string memory symbol,
+ uint256 initialSupply,
+ address initialOwner
+ ) ERC20(name, symbol) Ownable(initialOwner) {
+ require(initialSupply <= MAX_SUPPLY, "Initial supply exceeds max supply");
+ // Mint initial supply to the contract deployer
+ _mint(initialOwner, initialSupply);
+ }
+
+ /**
+ * @dev Mint new tokens (only contract owner can call this)
+ * @param to Address to mint tokens to
+ * @param amount Amount of tokens to mint
+ */
+ function mint(address to, uint256 amount) public onlyOwner {
+ require(totalSupply() + amount <= MAX_SUPPLY, "Minting would exceed max supply");
+ _mint(to, amount);
+ }
+
+ /**
+ * @dev Burn tokens from caller's balance
+ * @param amount Amount of tokens to burn
+ */
+ function burn(uint256 amount) public {
+ _burn(msg.sender, amount);
+ }
+}
+```
+
+### Deployment Script
+
+Create a deployment script following Foundry best practices:
+
+```solidity script/DeployToken.s.sol
+// SPDX-License-Identifier: MIT
+pragma solidity ^0.8.19;
+
+import {Script, console} from "forge-std/Script.sol";
+import {MyToken} from "../src/MyToken.sol";
+
+contract DeployToken is Script {
+ function run() external {
+ // Load deployer's private key from environment variables
+ uint256 deployerPrivateKey = vm.envUint("PRIVATE_KEY");
+ address deployerAddress = vm.addr(deployerPrivateKey);
+
+ // Token configuration parameters
+ string memory name = "My Token";
+ string memory symbol = "MTK";
+ uint256 initialSupply = 100_000_000 * 10**18; // 100 million tokens
+
+ // Start broadcasting transactions
+ vm.startBroadcast(deployerPrivateKey);
+
+ // Deploy the token contract
+ MyToken token = new MyToken(
+ name,
+ symbol,
+ initialSupply,
+ deployerAddress
+ );
+
+ // Stop broadcasting transactions
+ vm.stopBroadcast();
+
+ // Log deployment information
+ console.log("Token deployed to:", address(token));
+ console.log("Token name:", token.name());
+ console.log("Token symbol:", token.symbol());
+ console.log("Initial supply:", token.totalSupply());
+ console.log("Deployer balance:", token.balanceOf(deployerAddress));
+ }
+}
+```
+
+### Environment Configuration
+
+Create a `.env` file with your configuration:
+
+```bash .env
+PRIVATE_KEY=your_private_key_here
+BASE_SEPOLIA_RPC_URL=https://sepolia.base.org
+BASE_MAINNET_RPC_URL=https://mainnet.base.org
+BASESCAN_API_KEY=your_basescan_api_key_here
+```
+
+Update `foundry.toml` for Base network configuration:
+
+```toml foundry.toml
+[profile.default]
+src = "src"
+out = "out"
+libs = ["lib"]
+remappings = ["@openzeppelin/=lib/openzeppelin-contracts/"]
+
+[rpc_endpoints]
+base_sepolia = "${BASE_SEPOLIA_RPC_URL}"
+base_mainnet = "${BASE_MAINNET_RPC_URL}"
+
+[etherscan]
+base_sepolia = { key = "${BASESCAN_API_KEY}", url = "https://api-sepolia.basescan.org/api" }
+base = { key = "${BASESCAN_API_KEY}", url = "https://api.basescan.org/api" }
+```
+
+### Testing
+
+Create comprehensive tests for your token:
+
+```solidity test/MyToken.t.sol
+// SPDX-License-Identifier: MIT
+pragma solidity ^0.8.19;
+
+import {Test, console} from "forge-std/Test.sol";
+import {MyToken} from "../src/MyToken.sol";
+
+contract MyTokenTest is Test {
+ MyToken public token;
+ address public owner = address(0x1);
+ address public user = address(0x2);
+
+ uint256 constant INITIAL_SUPPLY = 100_000_000 * 10**18;
+
+ function setUp() public {
+ // Deploy token contract before each test
+ vm.prank(owner);
+ token = new MyToken("Test Token", "TEST", INITIAL_SUPPLY, owner);
+ }
+
+ function testInitialState() public {
+ // Verify token was deployed with correct parameters
+ assertEq(token.name(), "Test Token");
+ assertEq(token.symbol(), "TEST");
+ assertEq(token.totalSupply(), INITIAL_SUPPLY);
+ assertEq(token.balanceOf(owner), INITIAL_SUPPLY);
+ }
+
+ function testMinting() public {
+ uint256 mintAmount = 1000 * 10**18;
+
+ // Only owner should be able to mint
+ vm.prank(owner);
+ token.mint(user, mintAmount);
+
+ assertEq(token.balanceOf(user), mintAmount);
+ assertEq(token.totalSupply(), INITIAL_SUPPLY + mintAmount);
+ }
+
+ function testBurning() public {
+ uint256 burnAmount = 1000 * 10**18;
+
+ // Owner burns their own tokens
+ vm.prank(owner);
+ token.burn(burnAmount);
+
+ assertEq(token.balanceOf(owner), INITIAL_SUPPLY - burnAmount);
+ assertEq(token.totalSupply(), INITIAL_SUPPLY - burnAmount);
+ }
+
+ function testFailMintExceedsMaxSupply() public {
+ // This test should fail when trying to mint more than max supply
+ uint256 excessiveAmount = token.MAX_SUPPLY() + 1;
+
+ vm.prank(owner);
+ token.mint(user, excessiveAmount);
+ }
+
+ function testFailUnauthorizedMinting() public {
+ // This test should fail when non-owner tries to mint
+ vm.prank(user);
+ token.mint(user, 1000 * 10**18);
+ }
+}
+```
+
+Run your tests:
+
+```bash Terminal
+# Run all tests with verbose output
+forge test -vv
+```
+
+### Deployment and Verification
+
+Deploy to Base Sepolia testnet:
+
+```bash Terminal
+# Load environment variables
+source .env
+
+# Deploy to Base Sepolia with automatic verification
+forge script script/DeployToken.s.sol:DeployToken \
+ --rpc-url base_sepolia \
+ --broadcast \
+ --verify
+```
+
+
+The `--verify` flag automatically verifies your contract on BaseScan, making it easier for users to interact with your token.
+
+
+
+To deploy to Base Mainnet, simply change `base_sepolia` to `base_mainnet` in your deployment command. Ensure you have sufficient ETH on Base Mainnet for deployment and gas fees.
+
+
+## Post-Launch Considerations
+
+Once your token is deployed, here are the key next steps to consider:
+
+### Token Distribution and Economics
+
+Carefully consider your token's supply and distribution settings. Think through how tokens will be distributed to your community, team, and ecosystem participants. Consider factors like vesting schedules, allocation percentages, and long-term incentive alignment.
+
+### Community and Social Presence
+
+Establish a community and social presence around your token and project. This includes creating documentation, setting up social media accounts, engaging with the Base ecosystem, and building relationships with other projects and developers.
+
+### Liquidity and Trading
+
+Add liquidity to decentralized exchanges like Uniswap to enable trading. Note that token launchers will typically handle this for you automatically, but for custom deployments, you'll need to create trading pairs and provide initial liquidity.
+
+### Continued Development
+
+For comprehensive guidance on growing your project on Base, including marketing strategies, ecosystem integration, and growth tactics, visit the [Base Launch Playbook](https://www.launchonbase.xyz/).
+
+
+Remember to always prioritize security, transparency, and community value when developing and launching tokens. Consider conducting security audits and following best practices for token distribution.
+
+
+## Resources
+
+
+
+ Complete guide to getting started on Base
+
+
+ Technical specifications and network information
+
+
+ Comprehensive guide to using Foundry
+
+
+ Security-focused smart contract library
+
+
+ Explore transactions and contracts on Base
+
+
+ Get testnet ETH for development
+
+
+
+### Community
+
+
+
+ Join the Base community
+
+
+ Follow Base updates
+
+
+ Contribute to Base development
+
+
+
+---
+
+Whether you choose a platform-based approach for speed and convenience, or custom development for maximum control, Base provides a robust foundation for token launches. Start with the approach that best fits your technical expertise and project requirements, and leverage Base's growing ecosystem to build successful token projects.
\ No newline at end of file
diff --git a/docs/get-started/products.mdx b/docs/get-started/products.mdx
new file mode 100644
index 00000000..2c2ffa42
--- /dev/null
+++ b/docs/get-started/products.mdx
@@ -0,0 +1,19 @@
+---
+title: 'Products'
+keywords: ['onchainkit', 'minikit', 'agentkit', 'base account', 'appchains', 'paymaster','l3','deploy a chain','smart wallet']
+---
+
+
+
+ All-in-one toolkit and ready-to-use, full-stack components.
+
+
+ Feature your mini app on decentralized social platforms with a few lines of code.
+
+
+ A passkey-based universal account to connect with the onchain world.
+
+
+ Launch a chain with dedicated blockspace on Base, in minutes.
+
+
\ No newline at end of file
diff --git a/docs/get-started/prompt-library.mdx b/docs/get-started/prompt-library.mdx
new file mode 100644
index 00000000..32846ff9
--- /dev/null
+++ b/docs/get-started/prompt-library.mdx
@@ -0,0 +1,9 @@
+---
+sidebarTitle: 'Prompt Library'
+title: Developer's Guide to Effective AI Prompting
+description: Learn practical AI prompting techniques to enhance your coding workflow and get better results from AI coding assistants.
+---
+
+import AiPrompt from "/snippets/prompt-library.mdx";
+
+
+
+ Unlock the power of DeFi protocols and services directly in your app.
+
+
+ Deploy AI agents that can interact with onchain data and smart contracts.
+
+
+ Integrate secure and efficient crypto payment solutions for your apps.
+
+
+ Let users sign up and sign in with Smart Wallet — the universal account for the onchain world.
+
+
+ Use decentralized social graphs to grow your app and find users — wherever they are.
+
+
+ Enable gasless transactions and simplify user onboarding.
+
+
\ No newline at end of file
diff --git a/docs/get-started/use-cases/agents.mdx b/docs/get-started/use-cases/agents.mdx
new file mode 100644
index 00000000..c3fbbdd7
--- /dev/null
+++ b/docs/get-started/use-cases/agents.mdx
@@ -0,0 +1,3 @@
+---
+title: 'Agents'
+---
\ No newline at end of file
diff --git a/docs/get-started/use-cases/defi.mdx b/docs/get-started/use-cases/defi.mdx
new file mode 100644
index 00000000..2ae239cb
--- /dev/null
+++ b/docs/get-started/use-cases/defi.mdx
@@ -0,0 +1,3 @@
+---
+title: 'DeFi'
+---
\ No newline at end of file
diff --git a/docs/get-started/use-cases/gasless.mdx b/docs/get-started/use-cases/gasless.mdx
new file mode 100644
index 00000000..314ada32
--- /dev/null
+++ b/docs/get-started/use-cases/gasless.mdx
@@ -0,0 +1,3 @@
+---
+title: 'Gasless'
+---
\ No newline at end of file
diff --git a/docs/get-started/use-cases/onboarding.mdx b/docs/get-started/use-cases/onboarding.mdx
new file mode 100644
index 00000000..8e6bf157
--- /dev/null
+++ b/docs/get-started/use-cases/onboarding.mdx
@@ -0,0 +1,3 @@
+---
+title: 'Onboarding'
+---
\ No newline at end of file
diff --git a/docs/get-started/use-cases/payments.mdx b/docs/get-started/use-cases/payments.mdx
new file mode 100644
index 00000000..4240d030
--- /dev/null
+++ b/docs/get-started/use-cases/payments.mdx
@@ -0,0 +1,3 @@
+---
+title: 'Payments'
+---
\ No newline at end of file
diff --git a/docs/get-started/use-cases/social.mdx b/docs/get-started/use-cases/social.mdx
new file mode 100644
index 00000000..9243782a
--- /dev/null
+++ b/docs/get-started/use-cases/social.mdx
@@ -0,0 +1,3 @@
+---
+title: 'Social'
+---
\ No newline at end of file
diff --git a/docs/iframe-theme.js b/docs/iframe-theme.js
new file mode 100644
index 00000000..ab0046cd
--- /dev/null
+++ b/docs/iframe-theme.js
@@ -0,0 +1,62 @@
+(function () {
+ function updateIframesForDarkMode() {
+ const isDark = document.documentElement.classList.contains("dark");
+ console.log("Dark mode:", isDark);
+
+ document.querySelectorAll('iframe[src*="chromatic.com/iframe.html"]').forEach((iframe) => {
+ iframe.style.background = "transparent";
+ iframe.allowTransparency = true;
+ console.log("Found iframe:", iframe.src);
+
+ // Use postMessage to communicate with the iframe since we can't access contentDocument due to CORS
+ const sendThemeMessage = () => {
+ try {
+ const message = {
+ type: 'THEME_CHANGE',
+ isDark: isDark,
+ styles: {
+ background: isDark ? '#0b0d0f' : 'transparent' // transparent for light mode
+ }
+ };
+ console.log("Sending theme message to iframe:", message);
+ iframe.contentWindow.postMessage(message, '*');
+ } catch (e) {
+ console.warn("Could not send message to iframe:", e);
+ }
+ };
+
+ // Send message immediately if iframe might be loaded
+ sendThemeMessage();
+
+ // Also send message when iframe loads
+ iframe.addEventListener("load", () => {
+ console.log("iframe loaded, sending theme message");
+ // Add a small delay to ensure iframe is ready
+ setTimeout(sendThemeMessage, 100);
+ });
+ });
+ }
+
+ // Listen for theme changes on the parent document
+ const observer = new MutationObserver((mutations) => {
+ mutations.forEach((mutation) => {
+ if (mutation.type === 'attributes' &&
+ mutation.attributeName === 'class' &&
+ mutation.target === document.documentElement) {
+ console.log("Theme class changed, updating iframes");
+ updateIframesForDarkMode();
+ }
+ });
+ });
+
+ observer.observe(document.documentElement, {
+ attributes: true,
+ attributeFilter: ['class']
+ });
+
+ if (document.readyState === "loading") {
+ document.addEventListener("DOMContentLoaded", updateIframesForDarkMode);
+ } else {
+ updateIframesForDarkMode();
+ }
+})();
diff --git a/docs/public/images/account-abstraction/privy-console.png b/docs/images/account-abstraction/privy-console.png
similarity index 100%
rename from docs/public/images/account-abstraction/privy-console.png
rename to docs/images/account-abstraction/privy-console.png
diff --git a/docs/public/images/account-abstraction/privy-dashboard-page.png b/docs/images/account-abstraction/privy-dashboard-page.png
similarity index 100%
rename from docs/public/images/account-abstraction/privy-dashboard-page.png
rename to docs/images/account-abstraction/privy-dashboard-page.png
diff --git a/docs/public/images/account-abstraction/privy-login-methods.png b/docs/images/account-abstraction/privy-login-methods.png
similarity index 100%
rename from docs/public/images/account-abstraction/privy-login-methods.png
rename to docs/images/account-abstraction/privy-login-methods.png
diff --git a/docs/public/images/account-abstraction/privy-login-modal.png b/docs/images/account-abstraction/privy-login-modal.png
similarity index 100%
rename from docs/public/images/account-abstraction/privy-login-modal.png
rename to docs/images/account-abstraction/privy-login-modal.png
diff --git a/docs/public/images/account-abstraction/privy-login-page.png b/docs/images/account-abstraction/privy-login-page.png
similarity index 100%
rename from docs/public/images/account-abstraction/privy-login-page.png
rename to docs/images/account-abstraction/privy-login-page.png
diff --git a/docs/public/images/base-docs-og.png b/docs/images/base-docs-og.png
similarity index 100%
rename from docs/public/images/base-docs-og.png
rename to docs/images/base-docs-og.png
diff --git a/docs/public/images/basenames-tutorial/basename-profile-home.png b/docs/images/basenames-tutorial/basename-profile-home.png
similarity index 100%
rename from docs/public/images/basenames-tutorial/basename-profile-home.png
rename to docs/images/basenames-tutorial/basename-profile-home.png
diff --git a/docs/public/images/basenames-tutorial/basenames-frame-final.png b/docs/images/basenames-tutorial/basenames-frame-final.png
similarity index 100%
rename from docs/public/images/basenames-tutorial/basenames-frame-final.png
rename to docs/images/basenames-tutorial/basenames-frame-final.png
diff --git a/docs/public/images/basenames-tutorial/basenames-homepage.png b/docs/images/basenames-tutorial/basenames-homepage.png
similarity index 100%
rename from docs/public/images/basenames-tutorial/basenames-homepage.png
rename to docs/images/basenames-tutorial/basenames-homepage.png
diff --git a/docs/public/images/basenames-tutorial/confirm-textrecord-update.png b/docs/images/basenames-tutorial/confirm-textrecord-update.png
similarity index 100%
rename from docs/public/images/basenames-tutorial/confirm-textrecord-update.png
rename to docs/images/basenames-tutorial/confirm-textrecord-update.png
diff --git a/docs/public/images/basenames-tutorial/confirm-txn.png b/docs/images/basenames-tutorial/confirm-txn.png
similarity index 100%
rename from docs/public/images/basenames-tutorial/confirm-txn.png
rename to docs/images/basenames-tutorial/confirm-txn.png
diff --git a/docs/public/images/basenames-tutorial/edit-basename-profile.png b/docs/images/basenames-tutorial/edit-basename-profile.png
similarity index 100%
rename from docs/public/images/basenames-tutorial/edit-basename-profile.png
rename to docs/images/basenames-tutorial/edit-basename-profile.png
diff --git a/docs/public/images/basenames-tutorial/final-basename.png b/docs/images/basenames-tutorial/final-basename.png
similarity index 100%
rename from docs/public/images/basenames-tutorial/final-basename.png
rename to docs/images/basenames-tutorial/final-basename.png
diff --git a/docs/public/images/basenames-tutorial/frame-preview.png b/docs/images/basenames-tutorial/frame-preview.png
similarity index 100%
rename from docs/public/images/basenames-tutorial/frame-preview.png
rename to docs/images/basenames-tutorial/frame-preview.png
diff --git a/docs/public/images/basenames-tutorial/frames-selector.png b/docs/images/basenames-tutorial/frames-selector.png
similarity index 100%
rename from docs/public/images/basenames-tutorial/frames-selector.png
rename to docs/images/basenames-tutorial/frames-selector.png
diff --git a/docs/public/images/basenames-tutorial/preview-frame.png b/docs/images/basenames-tutorial/preview-frame.png
similarity index 100%
rename from docs/public/images/basenames-tutorial/preview-frame.png
rename to docs/images/basenames-tutorial/preview-frame.png
diff --git a/docs/public/images/basenames-tutorial/profile-component-dropdown.png b/docs/images/basenames-tutorial/profile-component-dropdown.png
similarity index 100%
rename from docs/public/images/basenames-tutorial/profile-component-dropdown.png
rename to docs/images/basenames-tutorial/profile-component-dropdown.png
diff --git a/docs/public/images/basenames-tutorial/show-preview.png b/docs/images/basenames-tutorial/show-preview.png
similarity index 100%
rename from docs/public/images/basenames-tutorial/show-preview.png
rename to docs/images/basenames-tutorial/show-preview.png
diff --git a/docs/public/images/basenames-tutorial/try-now.png b/docs/images/basenames-tutorial/try-now.png
similarity index 100%
rename from docs/public/images/basenames-tutorial/try-now.png
rename to docs/images/basenames-tutorial/try-now.png
diff --git a/docs/public/images/build-with-nouns/auction.png b/docs/images/build-with-nouns/auction.png
similarity index 100%
rename from docs/public/images/build-with-nouns/auction.png
rename to docs/images/build-with-nouns/auction.png
diff --git a/docs/public/images/build-with-nouns/create-dao.png b/docs/images/build-with-nouns/create-dao.png
similarity index 100%
rename from docs/public/images/build-with-nouns/create-dao.png
rename to docs/images/build-with-nouns/create-dao.png
diff --git a/docs/public/images/build-with-thirdweb/car-color-nft.gif b/docs/images/build-with-thirdweb/car-color-nft.gif
similarity index 100%
rename from docs/public/images/build-with-thirdweb/car-color-nft.gif
rename to docs/images/build-with-thirdweb/car-color-nft.gif
diff --git a/docs/public/images/build-with-thirdweb/deploy-contract.png b/docs/images/build-with-thirdweb/deploy-contract.png
similarity index 100%
rename from docs/public/images/build-with-thirdweb/deploy-contract.png
rename to docs/images/build-with-thirdweb/deploy-contract.png
diff --git a/docs/public/images/build-with-thirdweb/get-nft-colors.png b/docs/images/build-with-thirdweb/get-nft-colors.png
similarity index 100%
rename from docs/public/images/build-with-thirdweb/get-nft-colors.png
rename to docs/images/build-with-thirdweb/get-nft-colors.png
diff --git a/docs/public/images/build-with-thirdweb/hex-to-linear-color.png b/docs/images/build-with-thirdweb/hex-to-linear-color.png
similarity index 100%
rename from docs/public/images/build-with-thirdweb/hex-to-linear-color.png
rename to docs/images/build-with-thirdweb/hex-to-linear-color.png
diff --git a/docs/public/images/build-with-thirdweb/import-image-instance.png b/docs/images/build-with-thirdweb/import-image-instance.png
similarity index 100%
rename from docs/public/images/build-with-thirdweb/import-image-instance.png
rename to docs/images/build-with-thirdweb/import-image-instance.png
diff --git a/docs/public/images/build-with-thirdweb/mint-nft.png b/docs/images/build-with-thirdweb/mint-nft.png
similarity index 100%
rename from docs/public/images/build-with-thirdweb/mint-nft.png
rename to docs/images/build-with-thirdweb/mint-nft.png
diff --git a/docs/public/images/build-with-thirdweb/open-thirdweb-manager.png b/docs/images/build-with-thirdweb/open-thirdweb-manager.png
similarity index 100%
rename from docs/public/images/build-with-thirdweb/open-thirdweb-manager.png
rename to docs/images/build-with-thirdweb/open-thirdweb-manager.png
diff --git a/docs/public/images/build-with-thirdweb/open-unreal-project.png b/docs/images/build-with-thirdweb/open-unreal-project.png
similarity index 100%
rename from docs/public/images/build-with-thirdweb/open-unreal-project.png
rename to docs/images/build-with-thirdweb/open-unreal-project.png
diff --git a/docs/public/images/build-with-thirdweb/perform-nft-claim.png b/docs/images/build-with-thirdweb/perform-nft-claim.png
similarity index 100%
rename from docs/public/images/build-with-thirdweb/perform-nft-claim.png
rename to docs/images/build-with-thirdweb/perform-nft-claim.png
diff --git a/docs/public/images/build-with-thirdweb/play-button.png b/docs/images/build-with-thirdweb/play-button.png
similarity index 100%
rename from docs/public/images/build-with-thirdweb/play-button.png
rename to docs/images/build-with-thirdweb/play-button.png
diff --git a/docs/public/images/build-with-thirdweb/scene-game.png b/docs/images/build-with-thirdweb/scene-game.png
similarity index 100%
rename from docs/public/images/build-with-thirdweb/scene-game.png
rename to docs/images/build-with-thirdweb/scene-game.png
diff --git a/docs/public/images/build-with-thirdweb/token-airdrop-dashboard.png b/docs/images/build-with-thirdweb/token-airdrop-dashboard.png
similarity index 100%
rename from docs/public/images/build-with-thirdweb/token-airdrop-dashboard.png
rename to docs/images/build-with-thirdweb/token-airdrop-dashboard.png
diff --git a/docs/public/images/build-with-zora/cdp-pick-node.png b/docs/images/build-with-zora/cdp-pick-node.png
similarity index 100%
rename from docs/public/images/build-with-zora/cdp-pick-node.png
rename to docs/images/build-with-zora/cdp-pick-node.png
diff --git a/docs/public/images/build-with-zora/dashboard.png b/docs/images/build-with-zora/dashboard.png
similarity index 100%
rename from docs/public/images/build-with-zora/dashboard.png
rename to docs/images/build-with-zora/dashboard.png
diff --git a/docs/public/images/builder-anniversary-nft/builder-anniversary-nft-preview.webp b/docs/images/builder-anniversary-nft/builder-anniversary-nft-preview.webp
similarity index 100%
rename from docs/public/images/builder-anniversary-nft/builder-anniversary-nft-preview.webp
rename to docs/images/builder-anniversary-nft/builder-anniversary-nft-preview.webp
diff --git a/docs/public/images/connecting-to-the-blockchain/add-project-information.png b/docs/images/connecting-to-the-blockchain/add-project-information.png
similarity index 100%
rename from docs/public/images/connecting-to-the-blockchain/add-project-information.png
rename to docs/images/connecting-to-the-blockchain/add-project-information.png
diff --git a/docs/public/images/connecting-to-the-blockchain/alchemy-new-app.png b/docs/images/connecting-to-the-blockchain/alchemy-new-app.png
similarity index 100%
rename from docs/public/images/connecting-to-the-blockchain/alchemy-new-app.png
rename to docs/images/connecting-to-the-blockchain/alchemy-new-app.png
diff --git a/docs/public/images/connecting-to-the-blockchain/blockdaemon-create-key.png b/docs/images/connecting-to-the-blockchain/blockdaemon-create-key.png
similarity index 100%
rename from docs/public/images/connecting-to-the-blockchain/blockdaemon-create-key.png
rename to docs/images/connecting-to-the-blockchain/blockdaemon-create-key.png
diff --git a/docs/public/images/connecting-to-the-blockchain/connected.png b/docs/images/connecting-to-the-blockchain/connected.png
similarity index 100%
rename from docs/public/images/connecting-to-the-blockchain/connected.png
rename to docs/images/connecting-to-the-blockchain/connected.png
diff --git a/docs/public/images/connecting-to-the-blockchain/quicknode-select-chain.png b/docs/images/connecting-to-the-blockchain/quicknode-select-chain.png
similarity index 100%
rename from docs/public/images/connecting-to-the-blockchain/quicknode-select-chain.png
rename to docs/images/connecting-to-the-blockchain/quicknode-select-chain.png
diff --git a/docs/public/images/connecting-to-the-blockchain/rainbowkit-modal.png b/docs/images/connecting-to-the-blockchain/rainbowkit-modal.png
similarity index 100%
rename from docs/public/images/connecting-to-the-blockchain/rainbowkit-modal.png
rename to docs/images/connecting-to-the-blockchain/rainbowkit-modal.png
diff --git a/docs/public/images/connecting-to-the-blockchain/wallet-connect-create-button.png b/docs/images/connecting-to-the-blockchain/wallet-connect-create-button.png
similarity index 100%
rename from docs/public/images/connecting-to-the-blockchain/wallet-connect-create-button.png
rename to docs/images/connecting-to-the-blockchain/wallet-connect-create-button.png
diff --git a/docs/public/images/deployment-with-remix/base-confirm-transaction.png b/docs/images/deployment-with-remix/base-confirm-transaction.png
similarity index 100%
rename from docs/public/images/deployment-with-remix/base-confirm-transaction.png
rename to docs/images/deployment-with-remix/base-confirm-transaction.png
diff --git a/docs/public/images/deployment-with-remix/compiler-debug-log.png b/docs/images/deployment-with-remix/compiler-debug-log.png
similarity index 100%
rename from docs/public/images/deployment-with-remix/compiler-debug-log.png
rename to docs/images/deployment-with-remix/compiler-debug-log.png
diff --git a/docs/public/images/deployment-with-remix/editor-pane.png b/docs/images/deployment-with-remix/editor-pane.png
similarity index 100%
rename from docs/public/images/deployment-with-remix/editor-pane.png
rename to docs/images/deployment-with-remix/editor-pane.png
diff --git a/docs/public/images/deployment-with-remix/remix-base-goerli-connected.png b/docs/images/deployment-with-remix/remix-base-goerli-connected.png
similarity index 100%
rename from docs/public/images/deployment-with-remix/remix-base-goerli-connected.png
rename to docs/images/deployment-with-remix/remix-base-goerli-connected.png
diff --git a/docs/public/images/deployment-with-remix/remix-home.png b/docs/images/deployment-with-remix/remix-home.png
similarity index 100%
rename from docs/public/images/deployment-with-remix/remix-home.png
rename to docs/images/deployment-with-remix/remix-home.png
diff --git a/docs/public/images/deployment-with-remix/remix-terminal.png b/docs/images/deployment-with-remix/remix-terminal.png
similarity index 100%
rename from docs/public/images/deployment-with-remix/remix-terminal.png
rename to docs/images/deployment-with-remix/remix-terminal.png
diff --git a/docs/public/images/deployment-with-remix/select-provider.png b/docs/images/deployment-with-remix/select-provider.png
similarity index 100%
rename from docs/public/images/deployment-with-remix/select-provider.png
rename to docs/images/deployment-with-remix/select-provider.png
diff --git a/docs/public/images/deployment-with-remix/verify-and-publish.png b/docs/images/deployment-with-remix/verify-and-publish.png
similarity index 100%
rename from docs/public/images/deployment-with-remix/verify-and-publish.png
rename to docs/images/deployment-with-remix/verify-and-publish.png
diff --git a/docs/public/images/deployment-with-tenderly/configuration.png b/docs/images/deployment-with-tenderly/configuration.png
similarity index 100%
rename from docs/public/images/deployment-with-tenderly/configuration.png
rename to docs/images/deployment-with-tenderly/configuration.png
diff --git a/docs/public/images/deployment-with-tenderly/create-template.png b/docs/images/deployment-with-tenderly/create-template.png
similarity index 100%
rename from docs/public/images/deployment-with-tenderly/create-template.png
rename to docs/images/deployment-with-tenderly/create-template.png
diff --git a/docs/public/images/deployment-with-tenderly/debugger-button.png b/docs/images/deployment-with-tenderly/debugger-button.png
similarity index 100%
rename from docs/public/images/deployment-with-tenderly/debugger-button.png
rename to docs/images/deployment-with-tenderly/debugger-button.png
diff --git a/docs/public/images/deployment-with-tenderly/devnet-project-slug.png b/docs/images/deployment-with-tenderly/devnet-project-slug.png
similarity index 100%
rename from docs/public/images/deployment-with-tenderly/devnet-project-slug.png
rename to docs/images/deployment-with-tenderly/devnet-project-slug.png
diff --git a/docs/public/images/deployment-with-tenderly/github-actions.png b/docs/images/deployment-with-tenderly/github-actions.png
similarity index 100%
rename from docs/public/images/deployment-with-tenderly/github-actions.png
rename to docs/images/deployment-with-tenderly/github-actions.png
diff --git a/docs/public/images/deployment-with-tenderly/modifying-source.png b/docs/images/deployment-with-tenderly/modifying-source.png
similarity index 100%
rename from docs/public/images/deployment-with-tenderly/modifying-source.png
rename to docs/images/deployment-with-tenderly/modifying-source.png
diff --git a/docs/public/images/deployment-with-tenderly/output.png b/docs/images/deployment-with-tenderly/output.png
similarity index 100%
rename from docs/public/images/deployment-with-tenderly/output.png
rename to docs/images/deployment-with-tenderly/output.png
diff --git a/docs/public/images/deployment-with-tenderly/overrides.png b/docs/images/deployment-with-tenderly/overrides.png
similarity index 100%
rename from docs/public/images/deployment-with-tenderly/overrides.png
rename to docs/images/deployment-with-tenderly/overrides.png
diff --git a/docs/public/images/deployment-with-tenderly/result-of-expression.png b/docs/images/deployment-with-tenderly/result-of-expression.png
similarity index 100%
rename from docs/public/images/deployment-with-tenderly/result-of-expression.png
rename to docs/images/deployment-with-tenderly/result-of-expression.png
diff --git a/docs/public/images/deployment-with-tenderly/result-of-simulation.png b/docs/images/deployment-with-tenderly/result-of-simulation.png
similarity index 100%
rename from docs/public/images/deployment-with-tenderly/result-of-simulation.png
rename to docs/images/deployment-with-tenderly/result-of-simulation.png
diff --git a/docs/public/images/deployment-with-tenderly/setgreeting.png b/docs/images/deployment-with-tenderly/setgreeting.png
similarity index 100%
rename from docs/public/images/deployment-with-tenderly/setgreeting.png
rename to docs/images/deployment-with-tenderly/setgreeting.png
diff --git a/docs/public/images/deployment-with-tenderly/simulation.png b/docs/images/deployment-with-tenderly/simulation.png
similarity index 100%
rename from docs/public/images/deployment-with-tenderly/simulation.png
rename to docs/images/deployment-with-tenderly/simulation.png
diff --git a/docs/public/images/deployment-with-tenderly/simulator-button.png b/docs/images/deployment-with-tenderly/simulator-button.png
similarity index 100%
rename from docs/public/images/deployment-with-tenderly/simulator-button.png
rename to docs/images/deployment-with-tenderly/simulator-button.png
diff --git a/docs/public/images/dynamic-nfts/NFT_level_1.png b/docs/images/dynamic-nfts/NFT_level_1.png
similarity index 100%
rename from docs/public/images/dynamic-nfts/NFT_level_1.png
rename to docs/images/dynamic-nfts/NFT_level_1.png
diff --git a/docs/public/images/dynamic-nfts/NFT_level_2.png b/docs/images/dynamic-nfts/NFT_level_2.png
similarity index 100%
rename from docs/public/images/dynamic-nfts/NFT_level_2.png
rename to docs/images/dynamic-nfts/NFT_level_2.png
diff --git a/docs/public/images/dynamic-nfts/NFT_level_3.png b/docs/images/dynamic-nfts/NFT_level_3.png
similarity index 100%
rename from docs/public/images/dynamic-nfts/NFT_level_3.png
rename to docs/images/dynamic-nfts/NFT_level_3.png
diff --git a/docs/public/images/dynamic-nfts/all-characters.png b/docs/images/dynamic-nfts/all-characters.png
similarity index 100%
rename from docs/public/images/dynamic-nfts/all-characters.png
rename to docs/images/dynamic-nfts/all-characters.png
diff --git a/docs/public/images/dynamic-nfts/base-dynamic-nft.zip b/docs/images/dynamic-nfts/base-dynamic-nft.zip
similarity index 100%
rename from docs/public/images/dynamic-nfts/base-dynamic-nft.zip
rename to docs/images/dynamic-nfts/base-dynamic-nft.zip
diff --git a/docs/public/images/dynamic-nfts/image-level-1.png b/docs/images/dynamic-nfts/image-level-1.png
similarity index 100%
rename from docs/public/images/dynamic-nfts/image-level-1.png
rename to docs/images/dynamic-nfts/image-level-1.png
diff --git a/docs/public/images/dynamic-nfts/image-level-2.png b/docs/images/dynamic-nfts/image-level-2.png
similarity index 100%
rename from docs/public/images/dynamic-nfts/image-level-2.png
rename to docs/images/dynamic-nfts/image-level-2.png
diff --git a/docs/public/images/dynamic-nfts/image-level-3.png b/docs/images/dynamic-nfts/image-level-3.png
similarity index 100%
rename from docs/public/images/dynamic-nfts/image-level-3.png
rename to docs/images/dynamic-nfts/image-level-3.png
diff --git a/docs/public/images/dynamic-nfts/mutable-references.png b/docs/images/dynamic-nfts/mutable-references.png
similarity index 100%
rename from docs/public/images/dynamic-nfts/mutable-references.png
rename to docs/images/dynamic-nfts/mutable-references.png
diff --git a/docs/public/images/dynamic-nfts/open-sea-mockup.jpg b/docs/images/dynamic-nfts/open-sea-mockup.jpg
similarity index 100%
rename from docs/public/images/dynamic-nfts/open-sea-mockup.jpg
rename to docs/images/dynamic-nfts/open-sea-mockup.jpg
diff --git a/docs/public/images/dynamic-nfts/refresh-metadata.png b/docs/images/dynamic-nfts/refresh-metadata.png
similarity index 100%
rename from docs/public/images/dynamic-nfts/refresh-metadata.png
rename to docs/images/dynamic-nfts/refresh-metadata.png
diff --git a/docs/public/images/frames/100-lines-frame.png b/docs/images/frames/100-lines-frame.png
similarity index 100%
rename from docs/public/images/frames/100-lines-frame.png
rename to docs/images/frames/100-lines-frame.png
diff --git a/docs/public/images/frames/2024-a-base-odyssey.png b/docs/images/frames/2024-a-base-odyssey.png
similarity index 100%
rename from docs/public/images/frames/2024-a-base-odyssey.png
rename to docs/images/frames/2024-a-base-odyssey.png
diff --git a/docs/public/images/frames/first-frame.png b/docs/images/frames/first-frame.png
similarity index 100%
rename from docs/public/images/frames/first-frame.png
rename to docs/images/frames/first-frame.png
diff --git a/docs/public/images/frames/gave-me-away.png b/docs/images/frames/gave-me-away.png
similarity index 100%
rename from docs/public/images/frames/gave-me-away.png
rename to docs/images/frames/gave-me-away.png
diff --git a/docs/public/images/frames/install-action.png b/docs/images/frames/install-action.png
similarity index 100%
rename from docs/public/images/frames/install-action.png
rename to docs/images/frames/install-action.png
diff --git a/docs/public/images/frames/link-button-test.png b/docs/images/frames/link-button-test.png
similarity index 100%
rename from docs/public/images/frames/link-button-test.png
rename to docs/images/frames/link-button-test.png
diff --git a/docs/public/images/frames/real-nft.png b/docs/images/frames/real-nft.png
similarity index 100%
rename from docs/public/images/frames/real-nft.png
rename to docs/images/frames/real-nft.png
diff --git a/docs/public/images/frames/story-time.png b/docs/images/frames/story-time.png
similarity index 100%
rename from docs/public/images/frames/story-time.png
rename to docs/images/frames/story-time.png
diff --git a/docs/public/images/frames/updated-100-lines.png b/docs/images/frames/updated-100-lines.png
similarity index 100%
rename from docs/public/images/frames/updated-100-lines.png
rename to docs/images/frames/updated-100-lines.png
diff --git a/docs/public/images/frames/vercel-build.png b/docs/images/frames/vercel-build.png
similarity index 100%
rename from docs/public/images/frames/vercel-build.png
rename to docs/images/frames/vercel-build.png
diff --git a/docs/public/images/frames/vercel-import.png b/docs/images/frames/vercel-import.png
similarity index 100%
rename from docs/public/images/frames/vercel-import.png
rename to docs/images/frames/vercel-import.png
diff --git a/docs/public/images/frames/vercel-install.png b/docs/images/frames/vercel-install.png
similarity index 100%
rename from docs/public/images/frames/vercel-install.png
rename to docs/images/frames/vercel-install.png
diff --git a/docs/public/images/frames/vercel-projects.png b/docs/images/frames/vercel-projects.png
similarity index 100%
rename from docs/public/images/frames/vercel-projects.png
rename to docs/images/frames/vercel-projects.png
diff --git "a/docs/public/images/gasless-transaction-on-base/Screenshot 2024-07-11 at 3.10.17\342\200\257PM.png" "b/docs/images/gasless-transaction-on-base/Screenshot 2024-07-11 at 3.10.17\342\200\257PM.png"
similarity index 100%
rename from "docs/public/images/gasless-transaction-on-base/Screenshot 2024-07-11 at 3.10.17\342\200\257PM.png"
rename to "docs/images/gasless-transaction-on-base/Screenshot 2024-07-11 at 3.10.17\342\200\257PM.png"
diff --git "a/docs/public/images/gasless-transaction-on-base/Screenshot 2024-07-11 at 8.05.25\342\200\257AM.png" "b/docs/images/gasless-transaction-on-base/Screenshot 2024-07-11 at 8.05.25\342\200\257AM.png"
similarity index 100%
rename from "docs/public/images/gasless-transaction-on-base/Screenshot 2024-07-11 at 8.05.25\342\200\257AM.png"
rename to "docs/images/gasless-transaction-on-base/Screenshot 2024-07-11 at 8.05.25\342\200\257AM.png"
diff --git a/docs/public/images/gasless-transaction-on-base/cdp-allowlist-contract.png b/docs/images/gasless-transaction-on-base/cdp-allowlist-contract.png
similarity index 100%
rename from docs/public/images/gasless-transaction-on-base/cdp-allowlist-contract.png
rename to docs/images/gasless-transaction-on-base/cdp-allowlist-contract.png
diff --git a/docs/public/images/gasless-transaction-on-base/cdp-config.png b/docs/images/gasless-transaction-on-base/cdp-config.png
similarity index 100%
rename from docs/public/images/gasless-transaction-on-base/cdp-config.png
rename to docs/images/gasless-transaction-on-base/cdp-config.png
diff --git a/docs/public/images/gasless-transaction-on-base/cdp-global-user-limits.png b/docs/images/gasless-transaction-on-base/cdp-global-user-limits.png
similarity index 100%
rename from docs/public/images/gasless-transaction-on-base/cdp-global-user-limits.png
rename to docs/images/gasless-transaction-on-base/cdp-global-user-limits.png
diff --git a/docs/public/images/gasless-transaction-on-base/cdp-home.png b/docs/images/gasless-transaction-on-base/cdp-home.png
similarity index 100%
rename from docs/public/images/gasless-transaction-on-base/cdp-home.png
rename to docs/images/gasless-transaction-on-base/cdp-home.png
diff --git a/docs/public/images/gasless-transaction-on-base/cdp-paymaster.png b/docs/images/gasless-transaction-on-base/cdp-paymaster.png
similarity index 100%
rename from docs/public/images/gasless-transaction-on-base/cdp-paymaster.png
rename to docs/images/gasless-transaction-on-base/cdp-paymaster.png
diff --git a/docs/public/images/gasless-transaction-on-base/cdp-select-network.png b/docs/images/gasless-transaction-on-base/cdp-select-network.png
similarity index 100%
rename from docs/public/images/gasless-transaction-on-base/cdp-select-network.png
rename to docs/images/gasless-transaction-on-base/cdp-select-network.png
diff --git a/docs/public/images/gasless-transaction-on-base/cdp-select-project.png b/docs/images/gasless-transaction-on-base/cdp-select-project.png
similarity index 100%
rename from docs/public/images/gasless-transaction-on-base/cdp-select-project.png
rename to docs/images/gasless-transaction-on-base/cdp-select-project.png
diff --git a/docs/public/images/gasless-transaction-on-base/cdp-userops-10.png b/docs/images/gasless-transaction-on-base/cdp-userops-10.png
similarity index 100%
rename from docs/public/images/gasless-transaction-on-base/cdp-userops-10.png
rename to docs/images/gasless-transaction-on-base/cdp-userops-10.png
diff --git a/docs/public/images/hardhat-test-coverage/coverage-report.png b/docs/images/hardhat-test-coverage/coverage-report.png
similarity index 100%
rename from docs/public/images/hardhat-test-coverage/coverage-report.png
rename to docs/images/hardhat-test-coverage/coverage-report.png
diff --git a/docs/images/hero.png b/docs/images/hero.png
new file mode 100644
index 0000000000000000000000000000000000000000..f45b554f09e92631a834072c7af739f5a06adcf6
GIT binary patch
literal 870663
zcmV)iK%&2iP)Px#L}ge>W=%~1DgXcg2mk?xX#fNO00031000^Q000001E2u_0{{R30RRC20H6W@
z1ONa40RR98@}L6%1ONa40RR95i~s-t07psxumAu+07*naRCodGy;qYYOLis}GBZ+V
zY1yJ$-R{2KxBIFQzy(HJTflY=yWsB9jD~%o8DIE7KJlH8{105xj0?iJe4wpi0W7fu
z7T6sOMquWOxuUOb-PNV5QfG#a;CDPkMr1~+5-n!RD=WhN`0?Y%k9&AT96xcKUsyWN
zdBOG1@zW@%n~V@4(u+Xp7%Y~E6ikY;>c%b*N9;|-)4jFz<@N%4(;k5U8k~E{M$)52
z7bh7hIy6dEk5N6NF$`~5-cSaPn8_cpd~fmNrq@e9Aw6-G6BkIRbU5hbYZzGnNmd=B
z9ZL*k=a3mEN_-ekJa^ct`NI|*#?ImLj)jweNN^sLl?ZwyI%eS*+7XH$sV^q3mlYVV
zR4-OGufM%tmo+ORNQIO#rxY)7g3_*j#alb)
zmV_%8XEF-+zy9n0Eodbg!2bM(@Y6FZ3rkmurI~apl}@L?zbrXdE=cu;v%P1oZwnor
zlSE`@(n_vWn!R*s?Tt6YtJkDyk?QwCRdv_borjN{&F%e}shn-;U)=3He*C#<@|Gjm
zu4vo5X<4?z*|uq0nqze=v(34h$Z3Mx7Wigf(e6Ij1vNK#iVGuApjTb=q4nzJ)%~j5
z(vXwlgtRDSc|j57oFt_M&djFGVvd_C=jUfrj~+dK|AY7AgT(J@0$Xt?caTt*4gRa?Fk(
zrUXe5rJR^5$m!`!p_D7~xg3|~IoIG^U6uHzESjs!g{6g}k`)hX?w-UM6}Peepjm%h
zukRaLJD+nt{`jMMqsf?Yn1me`@8vKed^ep|78Wmvaz2+YLjZFsH
zj;->pF7j3}pWfVj7`6{rg(uH=B$TZ;6zK{=5f%h?CWwDQ@feRJd^)m=>)Pd|@BPm0
z-97c2M@F^oi0EY@?Fwnf6&*B)6T!KX;xC>p=%X8Aab8_6|JVQWA3xc!
zKD(>$S2`GbynxFm#qpw)%7f=z+PQJL^xNNAt2doHpT7TRfBGlv1;CdHD1QHY-=Cjf
z+SqPy?%9@`lT$@8RZe9WT?kog+GeAmIImsF+`cjYXoGvW;at3OZtjARyC&{#IA8zN
z-nv^Wr1oFGD&!PHPNhHi=<&b*)Bl}w(FEId@k4EBn?rL1CH#&~>Ta)zz-J5+KI^w2
zNvYsJzzGlnO#keGyT_1J2#O)HL;wlSVHFbQ9R(M%=rQ7P2|_+%NIQ)9m2?RKHIfK<
z2=IpFdEMQutha1$P77YbQUtRqOM-K6
zg8Am_&o-Vuj#ho-c)w7NOmbWThphUL#m3_5Wu+Z&+)1_~UQ=Hx7|MMa!vM*JlA*)s
zP+s)f8jd?A{XVolK=%S3Ug79mUK))v1mkf19xD|~45^B;Xl_cFR7aHZvL~r$41&qz
zlA(#@SX&Zvjs~27g`pK47oDM%Jey23CE*e}(Yl{Ql_%PsQ{tx*czGr8LR^h61QRcB
zA3k5sC+)mR@ekWNJVlKE{Mo$=;&$l$P%phLI?y5_fNM%~i_1c}Jl#y}EnYOM`@w`Do_vG+#r*~}FM4w`nLHCxc4nvQJ@U68c!XnM*uY_PpMVj>o9bV4%DeO7{{W8z}ry1rzPXw!+pq&i62A>
z8A&gKdc8gYkOdb>(DV|rG7DAY!)?pf3(%ae=2Fx-Ta}-WVfnvrqT)lJfa`J(tl
z5k
zH-Z-j0Q5{O8el}~_Vn~zAYz;$2MVrZ;p(P>0fa@oTvw76o^MMMAwUwcl!BPBYJibw
zsIFyT6zFNu0kgK_C<2e>6R$+gtI9iiya#cwUUrN|X_WQ`9};8)=Pp`5q?_l*dQp1Q
z0ju3}lmuqWEXIhR*R%XE0r_bkG*YY^ouDnFNOg&JW8;pkGj3Mq6@@Pr
zp)}>8jfHBGX&9*>72_Pde#+2J3!G&dre#7Q&hdsQ3QcC6?$!2mvobrEhl(7kTgNeB
z*H4D!Qr6-m&9Gow&9w7n#*eQ!pPpG=TDg+TPfI8Ry`U(Vre3R6=gm1OyFW3;D0Sz{%{OnIbKSIM
z>lPLaY{B866qX!I7v!wNDVo{gJGNL+Qz`MR82Yb>4`m6fLpFul4m|L*T)
zZ{3g-j%#z=f$QGia{l%Ia>sP_Y-#PFwx5#B>5@~-gQDJS)~nS@TBv{dC@sqxEjanZ
zOoC1vZDv;Oh?=%-@FHr}aorJ4q{}GnL70%RK4ln&B&8(6WHe|Rp*+yx#T1Qo%K=f_
zcFN^BG>lahNQmR^KB}KN%SJR2W`X#kkwzT3uE^s<83I8S1uefMgDQ_Y43)F6e&?8S
z$`N=>8fF?RV!OBoz8*(qSN$idGgY8_gIyJ^_Wk+IuS*iO^esdZ#~ljSk_7IDYQrHHKu566s;d
zOM;hfPaTE&GcOx$4z=QWhmfD=$V|6S40xD56!=Ug
zP}6xCl#?V|@BWSHjm@hxBYSanViPBc1*ZCp%&*6RTJ(a27m%exNa(q@0t_S#@kL`cF&f{h>($sW7(aKxkJMz~3i4ksQy
zTqYNeLr0N{V|%2>Ei({rU`B6kr|FkT0_fIBr?!`=d8fRdO5jui$032!iQ+hYIm1+S
z1KLGsxeIIOFFf7YoL{_9Dlg;q^0~b1dGSVkyy;q7U
zDs3nsJyU(CBgtByvlQ8Uw2l=8tN~DWfdR$_k%U^8-k>Rh(jJ74EKbNC{KHS4T)8;s
zIH`IIB7_74*Ab!Iw*`?GvX%qQzT0e@2UT-%F8iHtfBWbE@Jq-L#fcV$FcKy~nAOU9
zld9qQe7;mHEo3se#l?lW`E!}2Z0@G8@xa-*V^=mm=`EV~U4+9HxVT9xnRGhOiF{Lc_YT}vgKO6|Exl@)9V`!Uj+PQz8vGfF
z_$C4#jXJ)5A0A_t+NOJLRdh;
zU?ZKrU}tl=I=l@9!4n@+Bsx!q>_~Bfu%Slo5s>io`++teN_gMv4*Jfw&=;9nA1hF~
zeCfiaZ)LJmvvaer-ORqmbo!_z$8jBw&(8?odiVO>&zxpuJtefK3T7b(6}{1FL8pI^
zl@Gpth}9+d*by_?VjCZ%kT3&14Xzy*i*BZpl3lkYaP9StZhJ^N-LCT+iR((!bohG0
z0stGQr2PRNt*(JA3#8V!=&O`W7QUe{EZJoXEcS+b{c;Izxad;>A`V$FX%KnBz!i-v
zQI-YUv9XvT*YHga7H>FsvVyffW)(>k6xqf1Fj$QE@D9GTVXH?zqr{2ND8+(g2xF{z
z2rSpDwC5O-=oSlThL8Zze`c+UfP0Gs^+r$nGIpzD|NyraC!3+_k$2t20KSb^2
zkn($RLgYh55~%f7dMLWjs89m?18W}CF3|7-5W;u>3(k{N6qHFiADK?r3S#xh)RI`7
z02X6rf^x@(>N9{zJY;1wZ4Y&V0v<^eAeoO5k}=s61t@qwkfEml`@P)@3Kv}MkXgk*GmGS0kw~V
zd|WsKScrg!sP(}_LWn>k(FDWgfZFA`vSPON1qpp<#9`
zGA8brXd&rI@CV`!%m}MFjhss0R01!D1Tbw5c?^7}ZNS7b{ylOKXGbS;L<&bNKB!&C
z51)Y12~dxp&ruW)&)no=|L}E30-wSXHbD7uQ{NB=812)_6hz=z_
zrZIdT&}`J9J58sdKcyDX+~)G4h;Im>Y?fdGykBt^=HNshs(S-A`)!Rh`vNZ>?C*T>
z1sI!`-jyyaz~7A@V6)$7gCzrMeP*9e@BeTagKRR0_O118nCe5<2^LZ^yojLQs7~K&
z938`+jYdEUd;;PH&%pni`+MikOy?A(slr3L;MkCd;8>y~q{l9+m|tC<
zdgF~Z-h2OpR;%NaNIsE3SU?2!eTD0G(=h4UaTh)88
ztcP|RI(^RRXj+r$^wFE1QUJU%b_1s87B8hTbLinTLP~+Gps`ggx7y**dyQ(vAY1sh
zV`_+&AyNqL`O5K+k3jESy_At
zkk8NTxYz(dkn{3`+Y(H^xA|(LS}yRf-TvKAKmJLhzSmty3EIrg?&9KEhnKPEf|4m3
zhQ*6{%Py!Y-1JxBPv3QP3`j}94iMJX=KVlc=$)A8=;9y<9a$E}9^x2qI1$IBY@vW7
zRQZ&IZGJ?jFEh2ilrNOmF1?k_Oi#~D-M*Q>bz2I*6oEIK2fF+Dd)AZtPN%Ui@oKri
z74ulA(r|VB)_2}0b3m!TvVeNoctd%gN$=z*SO*bvvCxx_C1Z(Lscs^ustcJsHn<-6
z;Yp_lsMblwVO`x=2%-qXi6O?ay?lTM6pthKr-o4OM~*}M8jnCBPA^DdK#bWX$yFyq
z1M0_cj*8lgqe=wCy~r`taRMZwY=ivsWi@2xd9e}gxDylh1dU4^JbwA;yeo>FEa72;
z0^ng*81b^a34!KOx|Zm`qF&qs64)?}+RjgdBEQjRZ$P|!B6wN(KD4CK;0dm)q17CM
z6t1McOKoT!qcZz==mQ+forO&qAl(}hKrxijx8fuUNw65%p^33e4@aCZH-;WdBr!V*
zVYJ*ls-x)i)=l{MAFJ3vq=6Z|wVkF#}0i(YW{PE-cZ
zzwJlo0H*g)w?ezEYHdU3bi+-hxmR9&6aG4EDAQpo+{Ol;j;2vnu-S*2os@IT9SD2o
zfD({{dL6E}VXO+B9h^~c4m_BfsdQ>*mz;Ws!9)e{zyoCyl7oSU5~%uHpbN=hD1f_Qgh
zOD&i9rTNskWiF?1rm1NfJPFnJ4|ezV+8=&kJ*mQrcsKm)XWw9hTvP`$aB^49q{-fl
zk$|-_881WiB=U|3hwNPE;bSt@CzUQ8=|>9(^zctdmh_MGCQfkrd4bjHCugS%#e%HR
zhYR${0@;#d!vU*9?dQ{`t!Rd@yWiT{QDJ-a04(jC`onnoQ)
z<#4!xSClu#o_qfZAfwax%IpR2$a)hx_$fLvOot+iw1XP`WCYW?oxb
zx>6`iSL#@VXx+U1Zm~4QS{`dY#O%4>ktGFQP;^~`t-Q^Zn$4=NRk2O38@SZRn4FuA
z%FUyLBkL>VK#KGSk^r)vMK2R1)ae6=-uHC+SYd*88(w#y%}C`t|GQ
zR%bDya5cf{eZAhkytatZQ7)A*9DEuX1_rT(XdorI_a#E(o!1rW=1|3I7oUmMi=1kI$C&<$CWn)zBUjCt*KWYw%
z6Gmk{f!$()sRC0pJyT(RPm?n`gz%zevv;&Ck)qk0&F47yaqmQFZ?1PAJ-iz&b{apG
zz{?OAE_Jae@y$DyaxoWKm7eVA1hCbDYe&5sig9AjM(1#Y%5#S(4aFi50mOv#*zE(&x
zi61l8_T%*GjmPQk5wSqm@4b@~275Wjk^9xBPoP+b4|s?I-z$)2-_~JN4$VF!3(Y>%
zwb1NW>Q233zW&;^*%_!=gFplj*olbZ&jZmhlY!5c{bC`%yu4hVxsX01-PPFnRRmQf>~$^DKl2%5laj@4eASFWz5r}Bo(L%H83hwa!(*X&>c09*5R8c$mF
zj;eAh){tlu*?H`gteaxJWj|i8)T@nF&7IqIl@-4Dicp@vy0mh+T%N5r-IQ3lb^9GS
z`e#jN;tcd4)6?@VFJ-d1bfzGu@-9Es>cBj)ZJXE@7z+rrO)hlKnQZCa!@W>?Ol%}H
zKjI6M$(H1bEII{7`qb&9-zW2Y@~2M3?p2_MX$K!;elYD|bqHIH)mj>22>d(brJlV`GTRYia1v&z?OG
znqVG_VVbVj>TOuu*XnR6gpHS#La~_1Wa*ytix|l7`55f53DixW0t^YmbB7d+XHi9Q
zNH;Z3731J^DUKaGA+lrF-;d}CiewezZJ_Y_DfB{Obb2$#OAo8vV|Y9|Cy3>-F^tjU
ztvoK(J|Xl04p}>!#l|k%Z9coL_~jT4;ul|UVLCm#QVa=V+V$q{0OIrQDe!U4qO2e9
zMtxYP-QL`I5)?e%bGISKOZSx8sRWn=CLdsvmpBelk5g+OP9NatoJdKx?@{%Pp1hJM
zbYb1t(Hk&~LSH?7fMKO6FIFIy7*#SUf3)1ZQWI6=Bad4q87~={)P`pO12gfv@H43M
zw2Bjyz%%R6XI9Y(3hR{gsRVvQB!K&2{4M1u?LO&i|0L-5(CkTu(ij8}5#o`-=#;~9
zy$Do9-i>xDS25gG_}@@F9ZiSt6gMmIiz`C0P;4~!;fDv_^{ch^K}9JRUHIWSs8pcV
zhyKogc_i&M?Uo65Bm{;*FVyC)4Hr82dCWlxs$^h(U(Oe%3_G>3c;4Z#WiE82uAHu0
zi1VGTrlgzT0{TIy*Nv%CPJ+r5T6E@f2X)~L#X3GqhYN4oIu|DNF!;Bi64hGmPLo2X
z)uyny`Q+Un{MN!Oyz!WiH@Q|vqt{)Id;H{~B)?LxyVm!l^Yg;r{n&(cvSl+fb<&uj
zUgn3_g{u~zV~0T_-RA1LTd8pMO4WodJh{||`yCbQ1P~GLYM0K7
z+ne_UN64&rZkuJYr!WD_g(kFL+7*i;ikql4OQZ*g^VSO(Al>iK6Q0_
z4!(EhX6vP5c4it*@SQhazqz@&{?SM8>n1*9kyH&IqwGP~lTnmhE`tTFg@t*nV;xl0
zH{bepr_lhUjp`r*(77|~G#`lyd8ki_a_u!(Az2zfF-0_;Oo;mHj}Uy2a+
z@^feSIda106YA_^6#}mM!#vc2hwz6XM2_|0n2+o#f)G$ej>oVsI(AD%oXzGe5s6Y8
zy?OKL(?(yw&;|p7gqu=&1jo|(O%Tv^mFZvV`OGxQips;BY90+*AO9(
zPpb!$CBsGpnZY@%@!q`$XD=*3-HN?aHCR_0^k%AL_{FntZtwoJslyPy4TJre>EiTM
z3Tpj&t!67^4I
zPP|N$kvJ1n3qD=it;+UZp8WSVPN44@uZ7xt7=X9i&`qn&mZ#8%
zixIeq#~OrQ$cc_E{J;P4@BZ08{o%qa_7pW9ZMfuTU&BkXaPR)ts(SXbPx6&j_wWAp
zJx!zCf1#{|g*@}BPaLuzH2cIMto0F*1QSaP*en;O`cO-gg*&MOJWM(Q1pPF&zg=?Z(@%D5%%xD
z_1*9Ox>GTL+`yKhW$`ZxRS&qfnSxyZ9}pyp}zkJ`A)Wi?+d4s+`)k)YfL`
zen)h5QP82&$6gG-{9vQr(6)E>fB1vn#g2b>A9fBJszE;4;b#c}t0=bQI$C?nb>^IW
zNr7hHhGpWEX`-*dlH+bwmmIgCl$IS~OW`sr{G0%H`_OdUtyXu_DYDuB_~V~7>IXFN
z@#4k8TW^RfC8`4fBk6(bKH6|T
zf8VO^xiIM#ok}_9q*In@bg)EGYvm-#-mj{g+qK!5d?u5cDyN=q={H~d_AfvDMiT3~
ziH}931}>DgdQhp!vWO2TO2v$(mUj0lm74kPyZ`v_e)LyQH?~n7^&fRB1s10Wu3~u4
z!tNK?27`gw)dw_|#Hht3twXJE+wh5$&6cT55OUcx+#l6i`0xS*y$@F4q#t|3LS^5f
zr8g`Xq)2A>)(co=Ns+Za4@dl3-PKi^9P)~beJMI^Y^DvbLQQ;~KrDKr&#T2_xXU$T
z(oYhGH!Qsd#gD9w9*RdQ1au>jn2!^j0zrl8AQGMfCW3RA(HFt@O!%^gUE_Uu-eMmH
zghwWfBp?PjLDuMs157reCqZWgy9I`D6;?42Cz26~hUI?kBY_xk83fVi-sYhl5poHv
z=NmjuPLPdcIZ(C7T{Y;9+m0w|tPCEMFr}uk`8Esw9g1#CA;XkGw^KHUf>0#xMOhX@
z>U7#$o9k5I*D81&_iNRp)5Z*zK=fi6j1|pEE|Cn4mg|d;Uu1mDzDjxlhbPsq)(5Sj
zq4ybRC~}zDrP_^!nI{tItEUeTt#)W;6fqtTiUsF*ZX`7l!NVOBEhIb%ell({G_2q>
zaw>sS2?P?r#S(k=3g9pB8Pj$6NcaM?IW}vD?}DIYa2~tL<3v1s<%chMocs@@^@6iE
zknecL3)zZeWXdOnQ!J=z({bU5N7D=qdN)IdIW4rM+~R_eRp6_|g1eT3T5bQJc5pC@
zEGW+{80G3M|4ovE9lZ+|9PrNrZ99HstxvwTWy{IkyjHeM+q7D+W5rZNw)dVHw68*C
zZ`CfB&z2V#;9EZh58jxwpgqqh(8xpcNS^|r2rG*e6lVtf0zrviuVXLYMzaZZWrz6$
zH%bL)cloEA%>BI}{D=SWqd)kA?=Q~L4!Y2&wmNN0hgfrXY{RqAa_O6NN5$s>q|J03
zxCkdzE@pUA%Ha>z*rZ3qnS(-KaP)LqfesfQ_=yCWoa2YU6yo$$?Elz=i!`+UbnvzM
zpiE}u1SO&rVJI92&q5vD%A`cqz*i3V+(AdpwgFA4%*z?X4ZCqrZNpd3%2MuIZ@={q
zzj&|F47Sf@oO*qk$>eXm_S=;THsf7fSv`|0U*hvz&E_6|U_big=Xz_yG3#Vd4|;HO
z4>S7)qygq>=>oigBLrfOekA8hSKkrDoCqf~_~=4bBq=S(Mb+d`&NSgLebdtG*oqn7cRV>&Cg!EkbnD4>HM5;YYBlq
za^0*nQ0_ddWv8n%z-I1yXd;xhs0{imnO8EkY=&Z(MSt>J30zW2R%|Ly<%Z^JhBM4HVO
znuJ|#MUmFwsJs2HrqPHf#x=XLZQT%4=|Z&lrHgAAwrtT3EYKCn);Va23(lhiKIJVK
zKtdQTnXC-Q`a%vp>8cIvz5o|jok9W9vypr6F)rRV4YOdp1q07x2aFJ79&2ngvS^U@
zxr!x|5JK*K%vgaib7bTY#ju}8I-U0@)0NI*VZ^VoH$8-rUKWNI9iH2*#>eX=4uo+j
zbZI@)*bB>EmoXaH(SV!@LYK}2g^q|CGCUcpN36B4xW~o`^ANT*R(%LPdhM9J*sUW*
ze^3JT26r5Wg4+%zXUwqp{1J0COA6Dg0O^
z5RRf_rFu%tmjJt1CXz;SiDc+d!nn$MuD?O(;}Gw|=>rU+J`TKJt)E;9m9h|=ld%9z
zKu7=$EFRBbcgL}d4@VrH8?U#w9TS%ABbFqUexykuK38KgmyDDQos^H403QvF-w|H|
zo=;gkl|UeYiJlXKLND6+^ddx$JbNKL`x?g?c+Y~X@gKy-;rNBZ=}rg(8aY6|0T^$6
z^x}ymJ!8QIIn3l?cMC7w?M}+38%(P^a3mm8d=@pkbig92^jD3Bvfp4Qh3jIc-)oOKAO~VSq>~z{NU}BuUdw+)%
zj_{x3aO;}~zxc&R-~H~}@Wum;<>L*v)xlB(hwltvBi(9Gq1A8-f-Q5QV@B0XfeXj!
zq`<{e1!MpStfB=+g@2WY>s9D*!5{~RBkYR==s}s(&1CY|B;ZxKN1tQo`9rM
zMT$Y(J6~+Rb^F}ru4|EFa}%Ej;8O#h*KM-}V{j2};w|i@>+Bw=@V+uXTe^Pj+ArSw
zFnFM0k2O4>$xW@T-Q3;XTsyaN=FHi`)T{C`ug~+3{=vTY{s*1(*=F{O*IsPDSg`-U+bTcU)|)pn2;eu;91c>|Bbx
z@xTdvfmHo2^w-Yjb`#huOXcNk`r)Q4FTiI1BK!e~g1EoGEf|&8ZvW2H^#`WKV=v!q
zu8cl%_(Dr{bhTpY`&e>-`W!=2kIIw54Ar0>61=BpNCHWcCIjYW;OTb8{(xEU#Ab6>#n=+a$o$?-g)Xa>zt+5
z3+YZaZDQXFY?IrlSNEE8M{@mH@*0%ckt!wqYPfSa1sU}t@
z;EHE=ubNKL?!dX6f^DUz$|jbzV8x%yW-nd5bnkxD(U8}z)Y@tlpT)r65k?gaL=3{9
zyS5KI1R<4Kvf-S^f~P1M*9E@YfDo|eWx{bjEzDr6ST{p606$gE
z3ozAJI9}n^U3`-P$NG(|pd%Ng!Lq;`OA7@y-a_8`BSFRfxd*{Z`oJJBIMW5_g)kBT
z`p^Eb4>S6U^h1C=3lU!lR2Fg4IJ58Olf4I1qjgVUp%NXI7bXJRXi;RwRe8eFOX9SZc?BX8e!Q2zuD?
zgO5#j9RYR~;{05&I!JdV3c(o-p+F~Ulpi8df_Ozf`Mlbwc^=O^!0GW+0>dRR`XU)#
z{v>n3+ZY#Bl!N3F$_$CdV;S)twLS2OY#%gY4Cy)k@Id71c*@p_yC@i=J_lU;g!q9#=e
z0ilz#p%sLWZyS4zb~-Ixn`yRPB@1OS->iL;QO>BE0mb1#wN|N4!-a;g)+en#=+h78
z>`>rB2}|m3QuBc>NAACid3fG|e;crZ9OS0pGMq}$yC@(y!vvVN=_H^0Hl^XsBb`E~
zB!Cc9`{aln>j+Tj!^aME`n6i44jcU@whvVSoGL4}g)MU(n1^$GjVWY_K1|TzdjD6S
zJW$Q@_usj&G?(T%{ozyC?6*)ADnl#CH@^$^&<4`rVkolhaN+!0g0-B39dliHT7jY+
z-ovw!)F!ijKzV_7*u_T)RG#V~IgsT$u}>`vKwbtK&xSdB)An>&BoC(Ir!)7#$B$pR
zG;cXsr>*%;_HDfCgCEJJjac*WTVq&_&7CH^)nB@J?%-hO?){DM0YibymrLK$)PplC
z3un%pDNny5&GYs=zy7KH&CkAWRqxtnP2@VVh&2OzW`R|Z7L>@0TjIIvTOZ7TQ!`hBnN7#WHovOiXz&g%xSDA+zWC}X(Fj7L
zr9uAqXyeuES9q={NzKh&wXH*cox#!zx|sHmh4&-2ZLjOjx@mmxk%2QLcTzQ3`5zj)0E{dP*?ri8<18YBN1slg=D*~*?WZHJ#P&W+~I(@j`
zF?imR1uPqw(b04g+4jc#~!&7bozzq
zix+R@3iAu|${VkXubf9i{IKhC73lOour?k!&8lnZnj*Fe87$rCoi^b8nCB(dITVdshcgQ_IWVpr;7
zF^3CyXV=_2=)C>ycd+vH_zAvnpg>mw{nM${hJ$`M;X#L@z36Cca}7UNUN((eTz|B(
zWLkzPrQk*fFeqF(eqmt=pQ<32HkXF49tS#W^dMdysS{~fyEbjcOEUnJ`;sFw$NDm-
z)?KxQEwWom-o`ovx!q4GaKC@&n+L33s?=w|yLOObtom>Q`hmt}7$Q->c$n1_2?)kY
z^x%w{9Ge8@v22#6Jg)?c1cgH=t2CbK;Ug&017>B07NpS{kz7xCB0IczPk{-syQL?q
zrCaWq$DSRdJ$;Iblf$#)D7k(>LskbeIk4#QWOxi5XYGS8ihhodUOOm^$vn{Lb{{f<
z7#2uVcno2|yIIj~$%~VKMnv(dO37N5~WScZ0x@mQa*u*C#Vx3d}1VDK8{aJ
z6fY;?@vp4m?VFU&`1oUD_M!Cw*gV{w8HTqf%Z4hJ0W44SQc=mIBmeoG~+Hbp0or22PLqkH)uftKJ<09
zgFg-0eCRa6q;BZgiM3pW+j-~F;|kFZuF62E1qCQ7b4_jIzx-Hx_xrDs&Ay{Q-gH#M
zG4vLykYNk&z-S!GOG^}Ca}8VYl%iypmd>7CNu4{x?`*-n3H+PXSC$uE-Fy7euYU1#
z;|bVjpCe#F1XVCjNsN#HEf9DLQ?k;h7i)GT1AThY29NAS^^x4caS-|X-rm*A^CBpPgbkoq43(B-0mt1mW1e<*`CF|F(-Kf=?d%^a(%V%F#)#~cf?76dNr)JKJ
z<%~PSKl;pm@S#)N{nR$90;gilhR4!?rNI+Aw#f|^A=rur>qL5gAfD*|%Jp}!VQ*-v
zPm+=I*eSQAVmoC{>+G3Y1>58@)j7G;_uTL7@9(tRMsqo3b;>ov4D
zo9R5-Fq$fsYOodrw=>MaI^4K)_MjSeoEeN6NyuYButgx9mLGOH@EWtS;GA2@?(Dnb
zJU_)Rh|=3oN$+g0OLC`>FG8~~$wiZ2ZeeV+q0?`}%@1@MaKD4ST=9*^!zbZZ!!%HQ
z9>WOr1QP5>O-eb3k>=o9mCigxh;ucZQ8C!g;c>izO&UNzF``v4d{0n8npm#cl~2|L(iL
z|9||Of8%oyIpG4s)g;gYoF@eIHH}9$3MqnZEp#30XZV!G$rZvzaOc-9p=Jy}+6)_G
znWO=Of3o?fF^{b^T%OeWGCsj@H}|-+7dbJ*Sq|5!!2=IEJ(JB;@F@;f46w~LW{<5c
zTK)ktDy9E$EqsIV~h!Y2NAhEp#1avtNOTO82sVozq6o@O
zSSsuhlsnllA!AWyo*k3XT7!6a#RP!Eo_nwLvFIGR?I18o-_nFiE)98E7S5k7vwIOS
z%HaNyO`B}$1Zoi2G#Vt>*=ygIpMUH{PLD6W1j51i(zoR34Vdt{@sB}}Ubn=U
zv9SmzBPBz}toIb{gd~7oIfiNHgqVA2$ev2^rRl0?&uB0>g7dTI05t}c&(2?EkLBK@
zIUUJ2IdT(jSOi7D`~U?Rd#vy^PXHb4-Scvv_c3VL^X6k{{U^@k_|JXGe2!p{We>vf
z>khKLWRME00|0^DYbZ*JHIADp)G~!@&E_t)vQ*(Lo&4p{uDNoW-`@N*o4W*iee6#Q
z1L1O>nbwn~J<1UU`e5AKFV`dmJ@m5}r)1`xk`ML|V62S*mlU=|BfJf5F|@6oO5a!P
zlff_Oc?Ytiw=DR`uT2gH11l6*s-WG2p|Z#K1#FFg
ztxpgyXj4?bPdtJg?
zrE#`~J#szwJ9AU5hYuQo*kV%{l+=IoqfhaT#hY*3SXqMGb^gH7zZlj%3i&!O4R(TWMA3qSO(y|GaT#g#>OX+F1m;PNwk3A%mpJCY>U8Z9iukny;n
zbc~E;9vIp_c8S0Sx#$&gzvCGAv?F9J{!WIDUT+S)ZGJ6|d*uiX%D-juRIWd_C%w#nUhAARK>+lm>f_e
zBu`l^(BRb!rq(AvT0VSXVHuv{8%DC_B81U0Qd!y4&hb1T-OLPmwvxXqW
ziwsVUCK1CRSz)CVYaL#Ixan$-2bu=r5I^NZ2j(-hNpcga8D2b*tsdYw6vn~nAvY$_c-{s2+dvm+KlHis8L|V`o^kN1K4iW9SKj2@AC3W(qE&th19)faqqyfF+sB|g
z4RdM8?mh%$bG3iOLxUFp527@Uv;Pp_RY|iZ?lM&SX*iX@ubTwe#dXw19frtZ$_(VQ
zk60go-3JCt9|Oon)%pWad@yR8I7H^tLlqyZ!Z_u4YSf*v7n>^V!n&~mjEq8vw0{5v
z4?K!atnft0v63ut#Nzz~Pa&rg7%2gay2&P{krZPHCrmz8*GrecEaW{HK7Y=SrJs(4
z$TO0~+~PIp&zLTrEE#cgVb9;F-8Ep6%bv%H6>RMYM+}}amC~aE+5bYZLTJVEMMV6o
z%U4RdP)Swx?*~*~CW!?+AJ6&dV?RRSB*Zv`W-Kd~7%7{<*enMJ8jGX^C$%%Bo<4oN
z_R1A_yCMB~2j2Ec-Iq$ku?BbH#(&q?{ducxVqe-;yH(6G*E6(xCzXU+8gHR#Sh|zK
z4kI0A*bZFVL)%C`b2hh0r7ttjAD(t!qGwLvK?4}k>VpyA6%YLCz-@Q2lvTu$6l^D>!N4A(#ReU69GK1i^A0KD=f9Ds>C5;X}ra%7pl@jlfC
zY`tT5W)0A-8{4+gaXPj;wryJ-+qP}nwylnB=Z>A6Jo~)+oH6#;e_*XIYt@)FYt~g{
zS*uU&vZ}~jI3Kfv!|*+9NYd~#hsnxZh{L}=W(bwF3iNaNm0o6Axpe$P{x=I?dwX@W
zjODO6xSZK6rL+|D@RHLkqgG?{t#sxM^Lt$0)vc8-62k)m;?~?6+~;-;qFp~+Wjw8@
z<5oEDpuIVh%?ly?P=yfVwrQQjm{rNLBCBS(=_#jtMLYCkV6Yt7sTVZ$b3JvZk19?q
zNZ}4~EA#7}kayrF_hVb@r!O2Nnfn~IEH1~1%Zh7`Vv~??d6=R95adixSEi;6hw&n>
zcMzgM!p&?lwZE43sQ6`J)2b3=%1;`;6HMri^>SbZ@lV%s$yM`FOr2o&Cm0kxOzIV^
zNPo9vj*(UX_IsbYi@YH}FbQ%fU1;bQVOU~OsN~JMRD1O-QO*0Vlp$hb>e8~LPWcx#
zdo66MZTMaQ62&vTb>fBNGk^0ln|P_6#g&)jq(bA8X=9Em%uxWTZC@km6mxyhz!`=p
z(ny%ms$+G&jrG5h()(edr#nqkZzb+tm(RVe(ifgT?3<#vIF7CJ);3pR_J6^d-L-9}
z&|{(1cpz0CAKAA9G;`lb7bxR?s}ApK!@jw`v>3W?#{(E)`k++s)zN@fJ?e0j-d#O7pbMMX>=}+yGGuLyjEq^g&rBP0+|4EKJ%%inJB66`Vaw5j
z-Wm?e4LD*wO%AtU0h>hu7!g>hG!hzldr8MbYO&d@=yo@`i-1Vx5E)c3=4c&@Cf+>`
zoOWc6sLd$MRIqOyz`Fu>2F^Gh?NmVA-C8S8^m$6`#a>EKdij~N`#?u^we8DDi^_$J
zNQo*P9K^7Eww>@Gsn)6~}*1N%9`3b)*INjQZy4>kue;#!ybuj;*IKX9SZme_xRp+27sL(ozD
zxl$J97qRh`!f`nAUu2ryj+Ew
z-%iH~x=%ceAcMNfF!L$)a-(T`i=%{lt|BTs-=n`@*j;@A+_jggCZ~x~_}mZ7eBG1lEwz@GrlWtGzK;xF8@V5!dOmk&rFcu%
zJW22N4Tz-&L=rff+E=SjDMg?v{AqzW_a~R#jo2o{U?6{#?6nbXDm8i*a;Y#
zoa+>7HUsang&wb2%*;C4x??=s=6Uoidb=X)HT}V%-kpUVosd^oSLaj8wmv>E?<7;x
z(_gQ-H+sEHI#aM6{t86;?XWw#);D;4=(CrXXesPGYCItbg>MhVQnj1ikb$4J0%p6N
zsTKsLkLGERp>-BW4FZ^j28Oxt>uH!PzaF7R2P=J=$8&Wu)mXiZKt(k7h!kF0Ii1r<
z?b*1{fGfV8Q&Jnt0t3r?)`wjAqqB^S(O!g@>YMN1U9Fqv{iFyh(%`*SVIR9OZw(2A
z3DgAfpm>Rcg5r_#Vb4YerVhpV4S%Q(<3~^#eg=k|vJamCfj$C=KLa8R?S5kdL3w@R
zU?U6a>cHb)PE~HS^TRR_l)|0GF`O7-S83y-H^if|9v}gGed&2q%!2SoF<(9-2DIrf
zjgz;HA?uWuOoN0YOl9t178E0kXgR4V7!l%b%*>q<$U=-}3qxnapX%&?^p_2vXVjVm
z-)iju8Lt-`J&P&PT?iXd5IR{@4wFrx#wuvB?xq_HX#z*N9!@_f8MJ5|ac
z|H~~hMoH81N-pQ{=H)|kcu>E3uxwkMy1LwQ8UUvFE81{PQ>86_FKNGUz
z)$~CF=+b*(Ka^0SPOq*W@RLN#+_A&`)(H5V;~2Wo#i@k?%*-=3Q8bOup%1{u)*R&@
z1Ood|4-YPmO-WDl
zZtHGRl-gxWTYkRw2DQDJVXx#y%wP={&Rs^(6o&q0E;n)hpCY<;cJuwkuhVJ&UdsP@
zv9(2a%8uXRSl3MNevnU&2o?MR01~hC>dx@?pue(wI-3Ns1nqp&zCM^`tI^IgEF5?9?$XlzhUs`Jyowz+EAoi;Toj~gHV3CW&qGNn$QYJ8pPoMh_x%vEeT
zRpXpJ{Gt8YBZZuY$9=#15*=zt$ovi2pihbIGnPbFx6st^?`
zy}_%?1}%}*tOgTq!nQ*u{I#11{3|8B(i^k@?b$h}vX*uaG~O$Qoxtbuq|f2SVlcgR
zs?@^_w~}~ONB~8=GXFlz00gJA(!`E
z#jN(ZoKBZlr+P+@mqH&~yVRTsBrwdU_sZwF)%%%usn2c&ysYEJD;(A$ceZJvuFB!M
zvO8;{gh6j;v`rYo4n`j&Vk|6h^-#@J$i;Hz+l;P}L%s&}(XpvQ0ZlR>Q
zj=1pC!@wZ})rsY41DzJbadnb7vo$#hu2hPOGx}>-wao7M(D&WkXF%U}
zW5PkaaKnkQG6Ohs2%;nB3?hJAn};QxjpAmk#qv=M9oV258KGnX+30tVl6*j8VMoKL
zq8c<`dyhH5>>$5I}2cfQGps>{Qh6@asq<=$A)IYI5`5+_l@$%zByMf-V
zE&bJ$`sIHZNi)Tl4pmbRSisXAU6BW6Hh$-3Wd?vWePMhRu-q5tj}O%&gy2X^N9o2|(CpD8U%4oDCOy5DVk9s#Dy
z(CYx6ZFeIH}Nvx$>
zf6Il1!9DE-Lq^E0Ut?y)2jr^jGXO1_k1%w58tDYG`gQaV_Jv2iXmIzm_qrYpWYHE=
z|IM&So944CdnY14Rx4U!d1e0n^ic!{o{O7I&tRk)~mv;irX!lpL_F-M*X#Nuf~b1(KQlmCN(|JAZH;dPI@()WYX
z_eNc2dpLpGI}hlYTZz0Lf!hrSyWY>%RPi~6%*?ugPZj-J9F9;SLV68b?5aq
z_RG=6rZ^5&Wh-EsPkLADYG!#xkPTLiM^RMbfCk&zv+}~Q+Tt4!+WS2EeL{#Tr<*6^
zu$L1y7?eAG%(WXeQbI|9gVa)Ida&m3H*^XR)5+GBp!r%L_yA9&nWsKb`M*|B1+7=pg1#{Wy}tPef`&
zJ_fJ;eA}(){20{eLytFyAF6EkNSWnxs~+*h(3Z)Or5-6Xf-v}R
zX!;Zbs+O7%Z3b2+=^!?LL725MRl`0cyhRFTRxQm!N&TR>6q`TvXweAtmhztck@jFk%o}ds*`89o0o1!Zbe162s!zgZ!
z5z}I1ibxkGrT#Ye^Rejvj{qbRz7~Smol_wo0yj%Co*2Ul#v(CzTfOv-BbOI`f&6uM
zcA9;b{9C$i?BTR^+GujqC6asfFAZd8WhJHvFt=`ray4k_>(m&*
z3UK)&Y`b#30R5l=>E>BnyK{Td)QmK*51jAC+?&R#)e4IQFBCsN;Ck!2iPd_lvcUmG55T(;U?ctYnGkCpE12qo%$m^;_o;k%#0rOL!67KQ`~!3xRByS094L4bsI
z#O7)V!xUD{?o*+$r}(_)&+;3{mE9yB3>6a}MjkA-8Ymq#i@pb)DNL3&%5LE3;-#60
zF4f>T7vjk`zRG#i!_m?HniIQ=%W}S^$wCl)TF}&?bc}XdoCfvb2&j8j0|HcoH_`>i
zb>6y$#@O!b51i*|0AZlb&47D$asuzBtdA`!<{+$ck|urOFXgDsWv3ip>vHd#lGH{b
zI4}8NG2gN|(dzP-VBoZDUY`#OyxX_4NT!3jdPh*SfPN0*=TZ5rjjClN?9sn}=}l3eiS_&fuAmD*;FBEl_AscQM@*d+8fB6Y&K0{!bozF*V0pk=!^{X$@#wB!&*h!
zE8AsYjbQa6#F*nKEt?s8feBuRYJ2I$Pad&UxA!8Js%%$}>u9Ix>gZUzW@+N9RYFrr
zsjC}Yk*^8to}sa;C`JS~{i1TL@O#8r$4os)#VkdrSk)0`lU9>GIn(Svrgy$!BrZuZ
zr=6iB^2(^l7=u7ZgU>3mIATC)t7HTkn_VB**(Xhp(KMk5Z#$n84
zOv)5Tkxl9+zBGC&)KM><&oRd!TmWAf9{=BvE1V2VerO%iMrmH>PNMHIRRzV70!(I#
zU|QlJbi8gf|Khi_Fz--K5lU^IT7i_m4mWYPx-rUreL$!<&t!+8OpN3{k{6*_ycrE>
zM^&yvbfPNeZX+{=^*P5AJkf<<2l`%OskLaAy-$cW@oG|3CddWqCc4G?K>vRwF2Koe
zytb)-y?`$H{GG`&HfF@Xc?l}#{y|_biNyP
z0qd~~-GEh=Gbe)YmqQ%&jVetGs(
znki`pnOP{tuHb(*e`mLLHZa`_HP_1i;jF%>F2bAdgT@dW1wPLYla8uco9kU97$;=0bLBm$!D7jy%SU3xzbxU
zDu-OF_$-O>n8%a3+u`j{r7o`l09jp{L5|5Hw6AiDz1xA}R_5UQ$2Wq9d`2#Ui=mMklkPQr2wEYimoxk?gIl
zIZf+DmS)5io6l_px+L^xVhSVZf$~v)K9K`pvvgDFL_9BA&)S{}oJ{wjDF4ANMW_Og
zP*iN_Yjvl8h!hsri40qzxu4v^TNv(G^V|tQ*=;6R)1QGjo>iig;;aJBr$Zz@2}JC+
zpM86I6R8HJxzjS(6xI=q70K5>T(O1b8G4rq@WvSENHNmtYBsm+gJLn^0(4EuZ5axf6u-5Ng|NA^9%@6_dE&{iF%M~c+_
zi&d(X=8G%U!Dbi!mj`4Uj;WL&wbZ-D#^R(Y1LjCk;X-uqj4*c;kVix?0R*Qy@!$Mv
zLj)t$Eeh1fd>^}J4TnimTJI=+Xf~AKIt6oDs$0m04|lzYyN;a7ZpRoOt(s;kNDC=JwKw|&+A(O-N__0ekJyp%)^T5h>ALN^(
zEE%#-ur4aHD+`$+b_WsD&5^83QE1Ghp`p=Kgj;?Ykw!fqNiRK+ZQ4$B>~uFM#*Ik0
zjVN-Gt#R<{yg3d3On}Z%9}oHYUL$IMW&4A0>9|`Kl226s4=g#w#zE?KShnRLZ!d`J
z9?wTK5xhfRPRHVS6OIt|bg^mv+mS&$d`3i{N$IY0SW2cJ>q6+My_Zhn6J@I=TpyZA!U8
zw5Ychs@Ib8|EO!0#C214sszjP=#6$_9-{os$P`S!7>`d%{I%rdE3km%WOs
zJ~2g#>O+;S5G(I3*=ANXm5UC|LEEO7U^*og0`4OiYM-n{pNCW2{Zd?Yx~;>!v=ul6
z$@2-pzwQ>M?%*431M>6B=8dYf=}3XnCy}a!#7$8V%SJR{r+MRsxqK-BN(5!Sx11oo
zO@7seM}gfCp$5r0vi(K6j2U$3l?XIucK@t4Lh=*rsp6c^magziHlLa2#`|Mkg0C{p
zBUic9hZx|wy}fq4u0Ps)_y*5$Y
z;RAqdzE*a;q8*N^;R|&fVRo9t*Q{aSEn5KnAYLu{>W*!vM3Rhy9uq2xLghuf>*=3A
zY@kMp@n~8dIL}Kf(Q7Le6ZF<=)91J?-uLFtG-H=ke&X>5vPHtVopz78zz4_Lvk7a_
zj57@n58})%<9Z1UtJV~9i^r|%K1LeULF=i
zI%jy_GqV`D#Y>6MH_7};M62g$Cz`LkkoIIClpRumy`LUW#F|o$;x~*C0WADMGM{Lt
z=26w#PIZpdNoZx<#h`U_J|e4N3+0^4j_c!8@!lNgR2Vmq)i#T8h}c~WqC9buR%tgK
z#&RDYi|J@=%27$FiXU!ISvCCt?;aBMCap84LEyK&X?t!svXno~2V3E$lId@a4fcuv
zeOoOg4!B&)(N$R;5w{)TWlHut`_7hYWgllJ1&p$RL~6$(cOe(KlZrDWLAMxdUo%f5
zW9d+3oS!k`F6TaGJ&A0p2kdmAgu_x}OwGeH#>a`5tX5PJwJaqMZx3!se>l`+y;Lwu
zk`#%?nL@p=p--o`sVV%0COIjuw@-vsODpYHe!bI5vrIrv*|{zXmY~*5y--Z0<5%T}
z02)r2p%#BRO()+knXol}@DlPG529|s*|QAur4c_ebcehq!g4frGw17!9@&vPkU}|U
zjcnxax7W|W>-_S>&K5s
znMg+B`%9-sJD3?dR{?u+a&_B=NQrxOjRi#hI)xo=u=3q~^X+Wr`TkTr_}uedO6c{n
zhv@rIikoR?a^LLC)!o@`ipBc^WB}kr@_L&z20#*0$%54MB`?kV>10G%2EwecM5yce
zRZ80!$=K5V(55`6YSli=*D0sEnHc>xEE~@*nd2+F%?FV?N;^w+{$2JEc8dwQT
z(w^6zzRM{HRmz-?TLEsFQkoFgwKvdy7EK_Hhk&MBsK?RmS!`|K?YiYI5ivPh1v)3;
zMYS~;HE7)1mbcxmnf}ripZ*b2qZrce&q&_9wGNN>Q`_PdBe(b6cFN?j%OToV0H7tA_75){xBu`t%v_rwkF
zhs+BN!q6RvbP4pMtYI;7mT0E+&wJceB8UEIC7HpinBnS>euKNFXML~kSN*IFhy
z59$38oNnURwrM9s9{H%=g54BJ0=GIqd#~1$!JB>_^SRKobCI-PUzom8l$bBtwJS&?
z&v8)~@wY=v9|@)>iyaHA56hVi-&#tLLxfob;?DAbk!tf$5e60sPR^ISH<*6
zE}i@Bf<&~0We-L?UN{(;q2n<3)cu8sy-1vP{mz%skakbaf)o;`Tyb!wcH00Ce91)W
z&VX_vy}`JQ+>o52?IOFUcFTvljZPnB3ULe3YaylTkPQ0f*y(G~O9HftvlYkazv-L7
zMFc-)pkD&Nk<3u?P(*IokAj%Y8oV1@_tTb*#&pHpI6?hxC;JeY3+K@pD`CFl=ftgMn1(fRa6x)FEYRBJaT%&Ju@86>#8
zE(U#gwA?+LTOPY_K6igIx808|EiLpWOkp<}=a0pgyFF?q)-|epgpTmV$m^?a9wJk(KmF6Idr)T92&xlDzTY=|
zZRP{7UqE{?bO+dcMRRD()q9G=Ov0W~FI9oWtRgRvy-8F@o{KJF{9k9itwSKPf^1^B
z$9?V{lr#fw@L#kN^j~X$
zNlN*T74?E=3pJlUZ^l~@juJLtX>sJ!Hgi6AR}LbLI-RJZAP18+WoW$Hme`$l-_7Lo
zvikK2XHNYu3%Rv6T!{b=U7ZR_KLHiKDlUAk(JG}do5&cWJz(4(eET}UYj%Z*S-Phi5vWDuZP>wxMoe7ZC)O%
zQ^Q7+rcOY?uz@!dPO$^Vu2N(cK$#j!F0q1aW)k?D5JJGPmA%w*=a^3B@lK
z8i`hI1UygeZh1r#p^>GxrKCD?tLO8MrqZ1YMbs>;N1i$?WP8%|zQf=j!_PI9j{sFG
zbJ+#LGnww9Y&+6J%Y@=01}RR43v#T^L|7DF!QY4ONB0%(kJ&>(gnAGrOgJ-C3j9Tv+kp3u+`H)F!EUG%y;j2=
z@%Kq9XNB=Lc)%YMO{rrixS3@@yh=!q_mtvq0uf~qHM}hnZ``9m7E$66y^oI@2REG!
z!hx;byP9=GHKQqlqcvb4PEg`*zS@BV`6mfBVc)z%XklIXQQl80rLE)2-fYa8T1C>>4O
z8B|E5)*Y5m?o(2=o@MgVYxz{Qth^P+eaxe7d_|*eE}gy}z9dK}A6{N)-7uSRXBsUM
z!2cDX1FF@phBKNb6VfF`e7ODI5}AzTCtQ90dbk&o>USiZd5#o7EL7HTe!%+z`=26p
z$S7Awx~G^MWFKFwg^YVp
z1X|1q4!u#aguuw)XH>$x*8CW)87x9$8Y?3LLICj`E`(nEQeA>Pe{d
z*`)K1U)QLzVm;K>hHhRo>N;{tLnU-2UdKO1l_l+Fe*hT1D7$wSLP0h!`+9JDqYMtC
zME$WM3(CV>I*q!#DHA8D&yu#z0$}sCWtLbStQc8hE>GBYA#$vrZVT}+X3~?===N4P
zM4-ESynHy#J6m6Zkn_1D3
zT3)|7g2OKj(LcGhXf`
z@6H6+zFIZpkfim$T!@KfFm-raLB<@w<0Bi_uY%$_C&0a=rC*VT2OUI1LVS|GL?s=DV_Ixuv3P#5aH6Hb;HWs
z@SwjiwL>u1*I*vp7s^zNwwfhVMqsaP_o>CH04VTtUY~J55+tg#z7CjYi&Lk?Z?}@M
zU$6Wa3AJs$LI3jg%+A+g?G*2_+CU|oXLygF1bUGS)k#CU2Y?C2Nu2^+_hY^t!F4-%
zxU_UCadWJi)P0q0VWU*V`pp^F%^Hd&4wuPOm)T!e72o}!v;B~uUSyB22Af5#mad82
zoMZam$_nP*BBG%tBaAQp71ZfY60WGZTw?@Rta3EQ5^82oc9^cTt^_ri{&*j3D@Y;h
zZnu|{C$qV8RK?@trSMPr{CqX5o^YrzlaCB4CZc>x*pzov{1H2tI9tD+v-=oWa-FNnJ{k(gv^^Rzd;c
zcQ8HuLp<4fxt3~6#&2($+D9~Oyp8$8#tVy~DQ~CMK%SRqBEKYPp0E2_a{|u-Px-!1
zt26CH29ELEAnv0|)-Q%1%n(Len*kece|)q?&$(+>{-+xGsGmy8){!3=)()du%qJI=
zm!ZR7a5wrc|3T6@-gYXKqSOpgv~5P>q~_MTyIfeiGhNBnff@h6R8~d>Uf1R%cn)$(
zxPuW6XB6WgH2kJFHY&aRm#h~s<~~8Yc{qT6Y{96~^MO&4;S4Qh>+$0iJ7)H*9W)%x
zE-d@|o7N8{k$YVaE%hkeMZ@LEg)wld%{EUH9^PG`L8WqU?A6?7Te_7~JcGPY5hS5b
zyulnuc}eS{M9>#hs>Py2HXo{XYgThc?>&RL&VZi03zMR0xXvSReL(*-h2zN9N&}>B
zo5%;FjDi0nsyaV_4a0ug!U_?z-zcaj6V6N@0-mLPdx!iuYqg^5`SuNBGt+TxDk5>6aKotk;bg8PXqTBoQn?$|SlQxIz;NKt?1$MUe)iPP5W1^U6`s
z@8ov2r_Ig%Fxb@Ov5bDFYlHZrku>>U9&?@~`)d7o
zM6<2|v!`u43+W$N>SL8qqVikX`ozuLn3L^J*Jj
zinje|sJ>$O(XF>&eV(;lwN(W#i|C6z4D|urZ=^ud_p$gtTvnMqfVoHDI1{eIg6c8G
zzeRQM4dxTn+H+}Z)~fL`93AuUPDb9{|7_!!eOl^~M+6d^`6vkL&_YT$poJ>4`R_~v
zd%f~Id;z)?YTZtGJ?}MMX34%5#QOO_J+89WdtY`_sfbm}={7%qpKWnbj`<^8_qG+k
zr;Brl34ta~{!O1WN9Ee)Cgk=kj*2F}yHoOjxIUm$2Xqo$9!Z~TnMgfDd$rKDy-K_M
z&|szZqOf}l9_y0d_o->#+}5tvh~*a?oD&`R!B
zRThNntPIM{ohFxVJdHl)%lzJp92mXE7-l^;(&0JVj2l1)wc&(m^9XV;y&vZ+J=ZNf
zPpT?LZENtV3W#Xbj%#wZL19O7nn7LZDpQ1I$rf-{w0H@ND5^g}klH1e
zTtcglTcI{#SEs)o{ul}6&hM;0AsXqMZY*?d^>Tlp^-uUYlNi-UI1WYDO<=)6;zlao
z2sz{KnLCZPxT;)SzFZ0wFX_ZNU+42tIi-BTE(X;lA`+Qx2#xd$l?W_IBw5-#Q8^D~
za*F!C%`RpfbsY5`Jd|_bHLmYQoXrqJPwoEyDy=?BvN2M&<{FMVK{5VHe*n@dKCavo
zV?82d%ehl`xnX+_qbzZ?ZmiC5zxIh%9xQI+e;wYdjxqgL3U#=2070QdV%0M%{~7{ga^xa-4@F5PoHG
zvzTN0gl_C`?t99cevch_h#msOu)!Zf#o5r)U0mI3Kkv-Oj&j@!
z9H4-}r6sTL$2EA3*CW6hy_t(8U(ohGx_sO!!{osHmYzKTkb&SpyI%X(MtDrY(qtHbWRQhko`jFA4eEb+F`T+ufd|gB+a#Lz=%vk_R|AElSW<(iOxN
zxP+VT6O>{3AEkaeUb&5{nVDl4#!sQw8TIXpwSmUcr{UYr$;BN|oEg=g(lU30P1dLw
z6RPwmM>nhY{r#*s?{zG!0T-T&t8r!D0~;;LaVGuU0KOp&acm>-UoY}@nT6M@K~mmT
zHV;(_V!`kD$hU6DRL@lMjugh%GrUK@qRW3o(~HzG3~?V#*=Rs3WT{>*L0t`*G$@U8
zI|K=y-R)NCqNbi~a48WZX|dR?@(^+1vpoanjSJUkiWKX1LXUdF!2|tmYig^TH)Pxn
z3<9U+Aln7|uoh@t;(j>Xpq0llkN#(idVFf#o;QKcEiKLQ-vCgP=M=a}C+jp`OtwE0
zpLe$}^LEv5;W9f6(HR!)u?&=O-R0tMn20%vg=DK|o!71|t~UdpF$Qq{Py3aK9BnH<
z0r@RFzsG(chrqM5K=O$E@UXs94vg8;T-vo{#TNN7zLLMf;p78<=_nixL91?K(v
zxg-KXeGb3x_Bqi|a7UvKXD8k{sfwZ_2WCMKIbDc!KQ!VS5yFa<{b=swm|O#-r?3W(
zyRl9e(xpLR#!byi67n^rG9B8<)VX8BdSCA=7-|
z!`WsNW9mLZ=|x+TdCXXgL*cmbZVMF6uclj?EEL*IH}-$~0gtHcU?b%%D9W-0Gk7_i
z!}XH1nsy34EM5A^;A=*n$7q{%Z30e{N%-dGE~YU!@oLM~;o(vzEZOP^Sg7IqvACO+
z{joIghy-2-VJfSw2nH2$v7}zK5E>7T(@zf>(JcI6icw=V%X(jvvl#RD@Hd&rVR-(P
zo3Etc-rQl~HDZda8NV}dc35xL2xj+_$l`g1ng4_>a)T_p%3fC8lOxU@N`-|
z-1-V)0YNn_jd#(sa0mf5xwlahrTm{WI15=CEVu=#?dd%0!5aN@BSonveZ(L`#l0(
zNthvNv<{J6h;p5TCmx4MvhjAi927Ztq}fQir5Q+Sr}a}3YacGd&zaqEXVJ^$72Mab
zwa;`blC)#HIJ*!;qg?XK+1s)N_+~}%=BFh&mD2{U$?^cw^lGl7LLfc>ePKSus#U6F
ze^5h0=B&+yKk@h)_9Q@k`lO1bef0B2PmawkrP(7a}qaLWpG*gWjjdpjEi
zA>PHr^6uUL;9WyZSv9K;bKzXNk3Z-Mtxi`YP!FbAJg@2t6c6lm_g*)}=m#Mv89`itUKi=N11b7@MWECfwV?{`Dg-p*Mo$iMZ&*Zc
z!oWY&8-Of^deUFQJCQwll)D7Z&23WHB9U}N>Yey;Dq;UtLs3x~QXE}N|91t$|9abh
zwLz$zmFx1(yDES0Uz%^wd$K06TPQ1Gt?gdI!p$C#HjBCQxh=|fw#^?f9>h=GY=_txP=jjGzt
z`GdeQ3?
z1BH@>7Td1}!$3Q@(aYzOF5cY`H=@FAE~AbJ?bsyxfr7Yb`)QkZb%Y24Pq%AO!cEYm
z{lE5mbf`%hDivv9qhsKlIWwon@33x-AVHm)Th`B59E8?3^DN|uV5!}g-_WQqeS?k@
z<0i}SaiVd6$Qv(=R)L3gTiYV6WPQ-)a5vWLv4%MwK910!
zoBZ^FT+z2e$Ei81xJ-2o@$57Jw@}uDO=2qz
z;Fo7IiO6z1Yu_~?Cy^ohG9*EL&E>_;>cPj^L&mbP`bGS43_4-94JX?1+mDlS7rod0
z%Neo_&OT-e4C4JmH@RhSe$sP9A&OSvmZk
z>w6T__$`iK82xun>h-;++X)KP%nL~%7c**n1A(XB4^>7VQtldUc!|vfSvJ^DyOmB5
zKgKchBHdb3Uc~}R%WBYc>^E@+M32c_<5o?y_`s{q2N|U?Ve}w|n$q|`pNN1{#m%im
zCr>9OE}kyekMpjL!m>uN@CJX%zv%-XgWx#^6P~=tjcWtlt-hPKIkmMI&rdCrG_7E++UH}A{kpuXQu`+axo5xez{n;m^pu$*i
zkX$k)QJY!3`d%c&Vu`vkJG&*8w0iBJ5sGGhFc#!Oo*iwP@kDH$!tX9
z;;dP<>#cv++sUq~er>So7=5Kk47-YYNPJ(l$7@coX+4~$<%VMDod7Ae(^kDM9wA}-
zuEDE^J#{^mf7R8zF9m`$P$M)E>*lmVG{5w5x;G&IH0@lGqy$3yvR9Dcl44zUnjzNH
zDq9pM(4aLO6@Ywmaws7Z^7XY_vt)8>Rbs({t%Fa+1k*UvX3A8mXZpqWn(QCowq5r-
zZfy;2-C{xU3mqq*5<~%CUZ*QTNy|PRMbM%(OpI9SsyZ_0b$3;{TK>Z;K+|qvEN3nW
zXJrI{E{|gE8tea-mZmvg)`amlV6N1_+jIZHd4R
z&IFSvbsuGW9{m&c@xw{e4TV@iyc2Oz}9O6W4Cz|B)gY+nTc#Kra$v|+ED+$Onv$JROp_mcbI{3
zGQe(}RO|HE~y?^+*D
zT2a#25AaAq@=&#ZBWXgr?^mT{N7slhMm$RUn4Qwz>XqpAKUK#5X-8Ob{)57p@-RIs
zF;D)R8ah?eX7kbzOYLX#OX|i?K^(J3Z|%RZv}}`rPda1@i>waLFn>c&69fuM%BaaM
zQ!^pbFb2w9zKjGSKZ)4(`k+NyjCeRat?QXeRNcgiU1(y9>HK;Vk$Y)lG(}yq&G+N%
ztOv_UX~pR;4b45m>y}RQ*x5gW0Sy9UzpTj+N+&91VZ-u)hVEq!Oi^c3>qpKku>TFc
z`P7EX1TO+h?S?=$Ytcwv7oBm1;co$fE+MZ`8jxx3k#fTmN(RmE2q@ku~x~vg1Nk
zc)<}^lg9=y<-^+d0(Edc+&hkDaa8C-7Z=y;1z#fMe_G|)a!A~mYd0@)?(8_!AV*cD
zrnn$-H}lx6no;M6wt8KT-3>34>xV-}h6o3AHsrn1bSV#n`+o`{Kd8yKhKa(*{RWYr
z_kSI;k=oOsQuakp6uD%5Uqs$97jH$zi3g~Wn-B-8hXYvwMj9gVj2>p`;=sbX;|{{Y
zbwJ~~k|@?c5DVN!C>^XZz_RG#<2iDevLj^(Uo#Yy)UU6N1Mq_jO1i`s=DJ2TZ{W=m@A{cN>XSbcy$6
zFpyWxvB3Zs@BMAL3BE_Lxdy%(3-y29)YOn~A?L5;PA^*zJ6lcpaR8$REa|Tyr(Z(F
z`_yXnq%lxoHk_)k(Zrj2t(o6;P7hDJby4e!f!9Y5_a~H$=Y+JWS*#!p15j9jCYCj7
z>`UN>4sWPsSi}^LCqx#>u?Q4DIq5w(&)CoUky4Q|t)I`(&0B-m?BB^F6WhT^{({f4
zB}z;{Ma(o%7ATF$>5?6H2_?hU_`Hgnb>r{vi7Qw}6S`)`_dK4lCk@Klmx_4l6|DzW
zfomDQF-d?&kf+zi_xV$;+}x0IAdL;iFu)ZF>D>6;lrwe){U5HiJA3hHi`EvF`e2j!
z=BslhkNu@N3fzI7@pYVO8!*KU>l(N4@%d$XU
zSoxE&j@V>1Jn70r5O{RFD_`hO975?>b=!EPSP?f+Ub6q9W20|o_KsbS*UnT$K*u64
zloM4&Wz1BBx1#=`Ui(1myfY3bHS}Ja3r>iis;4S@t#<~1wZ<*4-ek9YgKt6PEazSb
z(NR0GB%#)j{|57G~na_UaX
zCo%WT-RAGkL%tC=n8IyJC6BVLn5&7z?-${}gcp-X#c=7{A}ZA}E&oMkR%+IY&_SEe$+c9UYMIW5<-po%5g(qx|l$iK-X
z9C0_l*z$#tGDkWg1?$8o!)r={()aj3|90`Z$mp|X+b!zHU4q!3&%6c*@$3hTjbV?M
z(Mn!^xPbT;B89@e%i3i
_Rate limited and not for production systems._ | +| Chain ID | 8453 | +| Currency Symbol | ETH | +| Block Explorer | [https://base.blockscout.com/](https://base.blockscout.com/) | + +## Base Testnet (Sepolia) + +| Name | Value | +| :-------------- | :------------------------------------------------------------------------------------------------------ | +| Network Name | Base Sepolia | +| Description | A public testnet for Base. | +| RPC Endpoint | [https://sepolia.base.org](https://sepolia.base.org)
_Rate limited and not for production systems._ | +| Chain ID | 84532 | +| Currency Symbol | ETH | +| Block Explorer | [https://sepolia-explorer.base.org](https://sepolia-explorer.base.org) | + +
(Options: Games, Social, Creators, Finance, Media) | +| curation | string | The entry's level of curation
(Options: Featured, Curated, Community) | + +#### Response + +```json [JSON] +{ + "data": [ + { + "id": "7AsRdN8uf601fCkH1e084F", + "category": "Creators", + "content": { + "title": "Based Project", + "short_description": "Short description of this based project with max char count of 30", + "full_description": "Full description of this based project with max char count of 200", + "image_url": "https://base.org/image.png", + "target_url": "https://base.org/target-page", + "cta_text": "Mint", + "function_signature": "mint(uint256)", + "contract_address": "0x1FC10ef15E041C5D3C54042e52EB0C54CB9b710c", + "token_id": "2", + "token_amount": "0.01", + "featured": true, + "creator_name": "Base", + "creator_image_url": "https://base.org/creator-image.png", + "curation": "featured", + "start_ts": "2024-06-25T04:00:00Z", + "expiration_ts": "2024-07-29T00:00:00Z" + }, + "updated_at": null, + "created_at": "2024-07-10T18:20:42.000Z" + }, + { + "id": "8fRbdN8uf601fCkH1e084F", + "category": "Games", + "content": { + "title": "Based Project II", + "short_description": "Short description of this second based project with max char count of 30", + "full_description": "Full description of this second based project with max char count of 200", + "image_url": "https://base.org/image2.png", + "target_url": "https://base.org/second-target-page", + "cta_text": "Mint", + "function_signature": "mint(uint256)", + "contract_address": "0x1FC10ef15E041C5D3C54042e52EB0C54CB9b710c", + "token_id": "1", + "token_amount": "0.005", + "featured": false, + "creator_name": "Base", + "creator_image_url": "https://base.org/creator-image2.png", + "curation": "community", + "start_ts": "2024-06-25T04:00:00Z", + "expiration_ts": "2024-07-29T00:00:00Z" + }, + "updated_at": "2024-07-11T18:20:42.000Z", + "created_at": "2024-07-10T18:20:42.000Z" + } + ], + "pagination": { + "total_records": 2, + "current_page": 1, + "total_pages": 1, + "limit": 10 + } +} +``` + +### GET /featured + +This endpoint will display a single Onchain Registry entry that is being actively featured + +#### Response + +```json [JSON] +{ + "data": { + "id": "7AsRdN8uf601fCkH1e084F", + "category": "Creators", + "content": { + "title": "Based Project", + "short_description": "Short description of this based project with max char count of 30", + "full_description": "Full description of this based project with max char count of 200", + "image_url": "https://base.org/image.png", + "target_url": "https://base.org/target-page", + "cta_text": "Mint", + "function_signature": "mint(uint256)", + "contract_address": "0x1FC10ef15E041C5D3C54042e52EB0C54CB9b710c", + "token_id": "2", + "token_amount": "0.01", + "featured": true, + "creator_name": "Base", + "creator_image_url": "https://base.org/creator-image.png", + "curation": "featured", + "start_ts": "2024-06-25T04:00:00Z", + "expiration_ts": "2024-07-29T00:00:00Z" + }, + "updated_at": null, + "created_at": "2024-07-10T18:20:42.000Z" + } +} +``` + +## Entry Schema + +| Name | Type | Description | +| :----------------- | :--------------- | :------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| id | string | Unique entry ID | +| category | string | The category of the entry
(Options: Games, Social, Creators, Finance, Media) | +| title | string | The title of the entry | +| short_description | string | Short version of the entry description (max 30 char) | +| full_description | string | Full version of the entry description (max 200 char) | +| image_url | string | URL of the entry's featured image | +| target_url | string | URL for the entry's desired user action | +| cta_text | string | This is the type of user action for the entry
(Options: Play, Mint, Buy, Trade, Explore) | +| function_signature | string | The function signature associated with the desired user action on the entry's contract | +| contract_address | string | The contract address associated with the entry | +| token_id | string | The token ID if this is an ERC-1155 | +| token_amount | string | The price of the entry's desired user action | +| featured | boolean | A true or false based on whether the entry is actively featured | +| creator_name | string | The name of the entry's creator | +| creator_image_url | string | The logo of the entry's creator | +| curation | string | The entry's level of curation
Options:
- Featured - one entry per day with top placement
- Curated - community entries being
- Community - all other community entries
{children}
-
+ {/* Product showcase section */}
+
+
+ {/* Product image container */}
+
+
+
+
+
+ {/* Product information */}
+
+
+
+
+
+ {/* Payment section */}
+ Your Amazing Product
+High-quality product with crypto payment support
+
+ {address ? (
+
+
+ ) : (
+
+
+ {predefinedAmounts.map((amount) => {
+ const selected = amount === depositAmount;
+ return (
+
+ );
+ })}
+
+
+
+ )
+}
+```
+
+### Display NFT Collection
+
+```typescript components/NFTGallery.tsx
+'use client'
+
+import { useState, useEffect } from 'react'
+import { useReadContract } from 'wagmi'
+
+interface NFT {
+ tokenId: number
+ name: string
+ image: string
+ attributes: Array<{ trait_type: string; value: string }>
+}
+
+export function NFTGallery({ contractAddress }: { contractAddress: string }) {
+ const [nfts, setNfts] = useStateMint Onchain NFT
+ +
+
+
+ {!isConnected ? (
+
+
+ Collection Details
++ Generative Onchain Art - Each NFT is unique and generated entirely onchain +
++ Price: 0.01 ETH +
++ Connect your wallet to mint +
+ ) : ( + + )} + + {isSuccess && ( +
+
+ )}
+ + NFT minted successfully! 🎉 +
+
+ {nfts.map((nft) => (
+
+ )
+}
+```
+
+## Best Practices
+
+### Gas Optimization
+
+
+ 
+
+ ))}
+
+
+ {nft.name}
+
+ {nft.attributes.map((attr, index) => (
+
+
+ {attr.trait_type}:
+ {attr.value}
+
+ ))}
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ );
+ }
+ ```
+
+ **Verified context properties:**
+ - **User identity**: FID (always available), username, display name, profile image URL
+ - **Client status**: Whether the user has added your Mini App to their favorites
+ - **Launch context**: General location information about where the Mini App was opened
+ - **Safe area insets**: For proper mobile layout within Farcaster clients
+
+ Welcome{displayName ? `, ${displayName}` : ''}!
+Your FID: {userFid}
+ {username &&Username: @{username}
} + {isAdded &&✅ You've added this Mini App
} + {location &&Launched from: {location}
} +
+
+ );
+ }
+ ```
+
+ What's your preference?
+ +
+
+
+
+
+
+ {userVote && (
+ Thanks for voting! Your choice: {userVote}
+ )} +
+ {
+ console.log('Transaction successful:', receipt);
+ }}
+ >
+
+
+ );
+ }
+ ```
+
+ Onchain Social Action
+Initiated by FID: {context?.user?.fid}
+ +
+
+ ),
+ intents: [
+ ,
+
+ Mint Your Base NFT
+
+
+ Limited Edition • 1000 Supply
+
+
+ Connect your wallet to mint
+
+ ),
+ intents: [
+ ,
+ ],
+ })
+ }
+
+ try {
+ // Check if user already minted
+ const hasMinted = await checkIfMinted(address)
+
+ if (hasMinted) {
+ return c.res({
+ image: (
+
+ Already minted! Check your wallet.
+
+ ),
+ intents: [
+
+ Ready to mint your NFT?
+
+ ),
+ intents: [
+
+
+ ),
+ intents: [
+ ,
+ ],
+ })
+})
+```
+
+## Best Practices
+
+### Security Considerations
+
+Recent Mints
+ {recentMints.map((mint, index) => (
+
+ #{mint.tokenId} minted by {mint.to.slice(0, 6)}...
+
+ ))}
+
+
+
+
+## Base Offers
+
+
+
+
+ Once we've deployed our contracts, we'll add a button that lets us interact with our contracts.
+
+
+
+
+
+