+ **Note**: if you are using a Mac, you may need an extra step to configure the security settings: + - Go to Apple menu > System Settings > Privacy & Security. + - Under security, add the `astar` binary file that you just downloaded to the whitelist. + - Continue with the following command. + + ```jsx + chmod +x zombienet-macos + ``` + +- Confirm if the binary is executable in your local environment. + + ```jsx + ./zombienet-macos --help + ``` + +- When the Zombienet CLI is installed correctly, you should see the following info: + + ```jsx + Usage: zombienet [options] [command] + + Options: + -c, --spawn-concurrency
+ **Note**: if you are using a Mac, you may need an extra step to configure the security settings: + - Go to Apple menu > System Settings > Privacy & Security. + - Under security, add the `astar` binary file that you just downloaded to the whitelist. + - Continue with the following command. + + ```jsx + chmod +x ./astar-collator + ``` + +--- + +### Download the configuration file for Zombienet + +In order to spawn the Zombienet, we need to add a configuration file to specify the configurations. We have a configuration file ready that is configured to two parachains named `shiden-dev` and `shibuya-dev`, and a relaychain named `rococo-local`: [here](https://github.com/AstarNetwork/Astar/tree/master/third-party/zombienet). + +- Download the configuration file from [here](https://github.com/AstarNetwork/Astar/blob/master/third-party/zombienet/multi_parachains.toml). + + ```jsx + curl -o multi_parachains.toml https://raw.githubusercontent.com/AstarNetwork/Astar/master/third-party/zombienet/multi_parachains.toml + ``` + +--- + +### Start the Zombienet with the configuration file + +- Start the Zombienet with the configuration file + + ```jsx + ./zombienet-macos -p native spawn multi_parachains.toml + ``` + +- After starting the Zombienet successfully, you will be able to see the local testnet endpoint and explorer link as shown below: + +  + +--- + +## Set up cross-chain assets on two parachains + +The HRMP channels between `shiden-dev` and `shibuya-dev` are opened as configured in the `multi_parachains.toml` configuration file. + +To proceed to the next step of XCM testing, we only need to register the native assets of `shiden-dev` and `shibuya-dev` on each other to pay for XCM execution on the remote chain. + +- Go to [Polkadot.JS Explorer](https://polkadot.js.org/apps/?rpc=ws://127.0.0.1:51931#/explorer) (or the link specified in `Direct Link` of `collator1` ) + - Click `Developer → Extrinsics → Decode` and input the following call data, to register `xcSDN` on `shibuya-dev`. Please make sure to submit the extrinsics via `Alice`'s account which have enough `SBY` balance. + + ```jsx + 0x63000b02102401910100d43593c715fdd31c61141abd04a99fd6822c8558854ccde39a5684e7a56da27d0102093d002410910114786353444e14786353444e12003600010101005d1f91013601010101005d1f02286bee + ``` + +- Go to [Polkadot.JS Explorer](https://polkadot.js.org/apps/?rpc=ws://127.0.0.1:51934#/explorer) (or the link specified in `Direct Link` of `collator2` ) + - Click `Developer → Extrinsics → Decode` and input the following call data, to register `xcSBY` on `shiden-dev`. Please make sure to submit the extrinsics via `Alice`'s account which have enough `SDN` balance. + + ```jsx + 0x63000b02102401210300d43593c715fdd31c61141abd04a99fd6822c8558854ccde39a5684e7a56da27d0102093d00241021031478635342591478635342591200360001010100411f2103360101010100411f02286bee + ``` + +--- + +## Execute a simple remote call from Shiden to Shibuya + +In this section, we will create an XCM remote call that will send an instruction from `shiden-dev` to execute `System::remark_with_event` on `shibuya-dev`. + +For more details on how to create a remote execution call and how the derived account works, we will explain in another guide. + +- Send some `SBY` to Alice’s derived account on **Shibuya** - `5Cvcv8RvSsp6go2pQ8FRXcGLAzNp5eyC8Je7KLHz5zFwuUyT` to pay for the gas fee of executing `System::remark_with_event`. + - The remote call won’t be executed via Alice's account on Shibuya directly, but with a new derived account. Thus, we need to send `SBY` to the derived account. + +  + +- Initiate the remote call by inputting the following call data in **Shiden’s** `Developer → Extrinsics → Decode`. + + ```jsx + 0x330001010100411f021400040000000013000064a7b3b6e00d130000000013000064a7b3b6e00d00060102286bee140a0808abba140d010004000101002611a3b92e2351f8b6c98b7b0654dc1daab45b2619ea357a848d4fe2b5ae1863 + ``` + +- After 2 blocks, you will be able to observe the executed `System::remark_with_event` in **Shibuya’s** explore under the recent blocks. + +  + +  + + +--- + +## FAQ + +Please join our [Discord](https://discord.com/invite/Z3nC9U4) for technical support. + +## Reference + +- [Zombienet](https://github.com/paritytech/zombienet) +- [Astar Documentation](https://docs.astar.network/docs/xcm/integration/zombienet-testing) +- [Bruno Galvao](https://hackmd.io/@brunopgalvao/S1Ilj5zA5) \ No newline at end of file diff --git a/docs/build/build-on-layer-1/builder-guides/xvm_wasm/_category_.json b/docs/build/build-on-layer-1/builder-guides/xvm_wasm/_category_.json new file mode 100644 index 0000000..9c43dcb --- /dev/null +++ b/docs/build/build-on-layer-1/builder-guides/xvm_wasm/_category_.json @@ -0,0 +1,4 @@ +{ + "label": "XVM and Wasm", + "position": 2 +} diff --git a/docs/build/build-on-layer-1/builder-guides/xvm_wasm/img/01.png b/docs/build/build-on-layer-1/builder-guides/xvm_wasm/img/01.png new file mode 100644 index 0000000..b60703f Binary files /dev/null and b/docs/build/build-on-layer-1/builder-guides/xvm_wasm/img/01.png differ diff --git a/docs/build/build-on-layer-1/builder-guides/xvm_wasm/img/02.png b/docs/build/build-on-layer-1/builder-guides/xvm_wasm/img/02.png new file mode 100644 index 0000000..546c24e Binary files /dev/null and b/docs/build/build-on-layer-1/builder-guides/xvm_wasm/img/02.png differ diff --git a/docs/build/build-on-layer-1/builder-guides/xvm_wasm/img/03.png b/docs/build/build-on-layer-1/builder-guides/xvm_wasm/img/03.png new file mode 100644 index 0000000..7f8e2fa Binary files /dev/null and b/docs/build/build-on-layer-1/builder-guides/xvm_wasm/img/03.png differ diff --git a/docs/build/build-on-layer-1/builder-guides/xvm_wasm/img/04.png b/docs/build/build-on-layer-1/builder-guides/xvm_wasm/img/04.png new file mode 100644 index 0000000..e5df9e2 Binary files /dev/null and b/docs/build/build-on-layer-1/builder-guides/xvm_wasm/img/04.png differ diff --git a/docs/build/build-on-layer-1/builder-guides/xvm_wasm/img/05.png b/docs/build/build-on-layer-1/builder-guides/xvm_wasm/img/05.png new file mode 100644 index 0000000..ed11ddf Binary files /dev/null and b/docs/build/build-on-layer-1/builder-guides/xvm_wasm/img/05.png differ diff --git a/docs/build/build-on-layer-1/builder-guides/xvm_wasm/img/06.png b/docs/build/build-on-layer-1/builder-guides/xvm_wasm/img/06.png new file mode 100644 index 0000000..94e9a0c Binary files /dev/null and b/docs/build/build-on-layer-1/builder-guides/xvm_wasm/img/06.png differ diff --git a/docs/build/build-on-layer-1/builder-guides/xvm_wasm/img/07.png b/docs/build/build-on-layer-1/builder-guides/xvm_wasm/img/07.png new file mode 100644 index 0000000..883de65 Binary files /dev/null and b/docs/build/build-on-layer-1/builder-guides/xvm_wasm/img/07.png differ diff --git a/docs/build/build-on-layer-1/builder-guides/xvm_wasm/manage_psp22_asset.md b/docs/build/build-on-layer-1/builder-guides/xvm_wasm/manage_psp22_asset.md new file mode 100644 index 0000000..18f5726 --- /dev/null +++ b/docs/build/build-on-layer-1/builder-guides/xvm_wasm/manage_psp22_asset.md @@ -0,0 +1,87 @@ +--- +sidebar_position: 2 +--- + +# Create and manage a PSP22 assets on Shibuya +## TL;DR +This guide will be help you in create and manage your PSP22 assets. + +--- + +## What is a PSP22 asset? +The PSP22 Fungible Token standard was inspired by ERC20. It targets every parachain that integrates with pallet contracts to enable WASM smart contracts. Defined at an ABI level, any language that compiles to WASM (and isn’t explicitly restricted to ink!) can use it. What PSP22 is on Polkadot is what ERC20 is on Ethereum. + +## Create a PSP22 contract +In this guide, we will use [OpenBrush](https://openbrush.io/) and their contract studio to build our PSP22 contract. OpenBrush contract studio is the fastest and easiest way to create your smart contract. It allows you to add extensions that will fit your needs for your asset. + + + +### Extensions: + +- **Metadata**: this allows you to enter the metadata of your asset during deployment. +- **Mintable**: allows you to create an `amount` of tokens and assign them to the `account`, increasing the total supply. +- **Burnable**: allows token holders to destroy both their own tokens and those they have an allowance for. +- **Wrapper**: allows you to wrap your PSP22 token in a PSP22Wrapper token which can be used, for example, in governance. +- **FlashMint**: allows the user to perform a flash loan on the token by minting the borrowed amount and then burning it along with fees for the loan. +- **Pausable**: allows you to pause all token operations. +- **Capped**: allows you to implement with a supply cap, analog to ERC20Capped. + +Not available in the contract studio, but another utility is the [TokenTimelock](https://docs.openbrush.io/smart-contracts/psp22/utils/token-timelock): a utility for locking PSP22 tokens for a specified time. [This contract](https://docs.openbrush.io/smart-contracts/psp22/utils/token-timelock) will lock user's `PSP22` tokens until the time specified when they can withdraw them. + +--- + +## Compile your PSP22 contract +When you decide on your PSP22 contract, you can download all files needed to compile by clicking on the ‘Download’ button on the top right. After downloading, unzip the files. +:::caution +Make sure your environment is set to compile ink! smart contract. If your environment is not set, follow the guide [here](https://docs.astar.network/docs/builder-guides/xvm_wasm/setup_your_ink_environment). +::: +### Step 1 +You can now open your Terminal and navigate to the folder with the downloaded files. + + + +### Step 2 +Next is to compile your smart contract by using this line: + +```rust +cargo +nightly contract build +``` +When compiling is finished, you should see the following screen where 3 files are created. The contract, wasm, and JSON file. + + +You can find the files in your folder under `target > ink`. + +--- + +### Deploy your PSP22 contract on Shibuya +Astar ecosystem has 3 networks: Astar, our mainnet, connected to Polkadot; Shiden, our canary network; and Shibuya, our testnet. Deploying and using your contract is the same on all our networks. + +### Step 1 +Go to our testnet [Shibuya](https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Frpc.shibuya.astar.network#/accounts). In this guide, we will use [Polkadot.JS](https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Frpc.shibuya.astar.network#/accounts), but you can also use the contract UI or our Swanky all-in-one tool. + +:::caution +Make sure you have an account on Shibuya with testnet tokens. You can get your testnet tokens through our faucet. +::: +Navigate to the contract dashboard `Developer > Contracts`: + + + +### Step 2 +We will now upload our contract and set the initial state. The PSP22 contract used in this guide has the metadata extension added to the contract. If you didn’t add this, you will not have the same screen. + + + +By adding the metadata extension, we can now set all the information for my asset. To finish, click on ‘Deploy’ and ‘Sign’ your message. + + + +When deployed, your new contract will be visible with your other contracts. + + + +--- + +## Reference + +- [Ink! official documentation](https://use.ink/) +- [OpenBrush](https://openbrush.io/) \ No newline at end of file diff --git a/docs/build/build-on-layer-1/builder-guides/xvm_wasm/pseudo_random.md b/docs/build/build-on-layer-1/builder-guides/xvm_wasm/pseudo_random.md new file mode 100644 index 0000000..4f88900 --- /dev/null +++ b/docs/build/build-on-layer-1/builder-guides/xvm_wasm/pseudo_random.md @@ -0,0 +1,70 @@ +--- +sidebar_position: 3 +--- + +# How to Generate Pseudo-Random Numbers in Ink! Smart Contract +Generating random numbers is an essential feature of many decentralized applications, but generating truly random numbers in a trustless, decentralized environment is a challenging problem. In this article, we will show you how to implement a simple pseudo-random function in your Ink! smart contract and generate pseudo-random numbers within a specified range. + +## **Implementation** + +First, create a new Ink! smart contract and modify the **`PseudoRandom`** struct to include the **`salt`** variable. The **`salt`** will be incremented by 1 each time the **`get_pseudo_random`** function is called. + +```rust +#[ink(storage)] +pub struct PseudoRandom { + salt: u64, +} +``` + +Then, update the **`get_pseudo_random`** function to take an input parameter for the maximum value in the range, and to return a number between 0 and the maximum value in the range using the following code: + +```rust +use ink::env::hash; + +#[ink(message)] +pub fn get_pseudo_random(&mut self, max_value: u8) -> u8 { + let seed = self.env().block_timestamp(); + let mut input: Vec
+To access the faucet visit the [chaindrop portal](https://chaindrop.org/?chainid=81&token=0xeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee), and select Shibuya from the token list. + + + +Paste your wallet address in the `beneficiary` field.
+Click the `I'm not a robot` checkbox, to validate the Captcha. + + + +Click `Send Me` to recieve SBY in your wallet; the amount recieved will be displayed.
+Click on the `success` link to view your transaction on explorer. \ No newline at end of file diff --git a/docs/build/build-on-layer-1/environment/img/1.png b/docs/build/build-on-layer-1/environment/img/1.png new file mode 100644 index 0000000..dfc2421 Binary files /dev/null and b/docs/build/build-on-layer-1/environment/img/1.png differ diff --git a/docs/build/build-on-layer-1/environment/img/1n.png b/docs/build/build-on-layer-1/environment/img/1n.png new file mode 100644 index 0000000..17d4ab6 Binary files /dev/null and b/docs/build/build-on-layer-1/environment/img/1n.png differ diff --git a/docs/build/build-on-layer-1/environment/img/2.png b/docs/build/build-on-layer-1/environment/img/2.png new file mode 100644 index 0000000..27d2aa1 Binary files /dev/null and b/docs/build/build-on-layer-1/environment/img/2.png differ diff --git a/docs/build/build-on-layer-1/environment/img/2n.png b/docs/build/build-on-layer-1/environment/img/2n.png new file mode 100644 index 0000000..500bd03 Binary files /dev/null and b/docs/build/build-on-layer-1/environment/img/2n.png differ diff --git a/docs/build/build-on-layer-1/environment/img/3.png b/docs/build/build-on-layer-1/environment/img/3.png new file mode 100644 index 0000000..1b92534 Binary files /dev/null and b/docs/build/build-on-layer-1/environment/img/3.png differ diff --git a/docs/build/build-on-layer-1/environment/img/3n.png b/docs/build/build-on-layer-1/environment/img/3n.png new file mode 100644 index 0000000..4902162 Binary files /dev/null and b/docs/build/build-on-layer-1/environment/img/3n.png differ diff --git a/docs/build/build-on-layer-1/environment/img/4.png b/docs/build/build-on-layer-1/environment/img/4.png new file mode 100644 index 0000000..31265df Binary files /dev/null and b/docs/build/build-on-layer-1/environment/img/4.png differ diff --git a/docs/build/build-on-layer-1/environment/img/5.png b/docs/build/build-on-layer-1/environment/img/5.png new file mode 100644 index 0000000..ff2a070 Binary files /dev/null and b/docs/build/build-on-layer-1/environment/img/5.png differ diff --git a/docs/build/build-on-layer-1/environment/img/6.png b/docs/build/build-on-layer-1/environment/img/6.png new file mode 100644 index 0000000..d18b670 Binary files /dev/null and b/docs/build/build-on-layer-1/environment/img/6.png differ diff --git a/docs/build/build-on-layer-1/environment/img/7.png b/docs/build/build-on-layer-1/environment/img/7.png new file mode 100644 index 0000000..c4a7678 Binary files /dev/null and b/docs/build/build-on-layer-1/environment/img/7.png differ diff --git a/docs/build/build-on-layer-1/environment/img/8.png b/docs/build/build-on-layer-1/environment/img/8.png new file mode 100644 index 0000000..7fcba7f Binary files /dev/null and b/docs/build/build-on-layer-1/environment/img/8.png differ diff --git a/docs/build/build-on-layer-1/environment/img/9.png b/docs/build/build-on-layer-1/environment/img/9.png new file mode 100644 index 0000000..17ec4df Binary files /dev/null and b/docs/build/build-on-layer-1/environment/img/9.png differ diff --git a/docs/build/build-on-layer-1/environment/img/chaindrop_1.png b/docs/build/build-on-layer-1/environment/img/chaindrop_1.png new file mode 100644 index 0000000..6d0eb30 Binary files /dev/null and b/docs/build/build-on-layer-1/environment/img/chaindrop_1.png differ diff --git a/docs/build/build-on-layer-1/environment/img/chaindrop_2.png b/docs/build/build-on-layer-1/environment/img/chaindrop_2.png new file mode 100644 index 0000000..fb96671 Binary files /dev/null and b/docs/build/build-on-layer-1/environment/img/chaindrop_2.png differ diff --git a/docs/build/build-on-layer-1/environment/index.md b/docs/build/build-on-layer-1/environment/index.md new file mode 100644 index 0000000..ecf2d61 --- /dev/null +++ b/docs/build/build-on-layer-1/environment/index.md @@ -0,0 +1,17 @@ +import Figure from "/src/components/figure" + +# Set up the Development Environment +
+
+
+
+
+## Overview
+
+Pinknode is a Polkadot-focused Infrastructure-as-a-Service platform offering RPC service through globally distributed node architecture coupled with Kubernetes clustering and geo-location routing for increased reliability and reduced latency. You will be able to integrate into the Astar ecosystem with Pinknode API services within minutes.
+
+## Public Endpoints
+
+Pinknode provides RPC and WSS endpoints for the Astar ecosystem. You will be able to connect via:
+
+- Public endpoints (May be subject to increased rate limits during high network load)
+- Custom API endpoints on:
+
+
+| Network | RPC Endpoint | WSS Endpoint|
+|----|----|---|
+| Astar | + `https://astar.public.blastapi.io/`
+ `https://astar-rpc.dwellir.com/`
+ `https://astar.api.onfinality.io/public` + 3. Chain ID: `592` + 4. Currency Symbol: `ASTR` + 5. Block Explorer URL(Optional): `https://astar.subscan.io/` +3. Click the “Save” button +4. Repeat steps 1-3 for Shiden network with following details: + 1. Network name: `Shiden Network Mainnet` + 2. New RPC URL:
+ `https://shiden.public.blastapi.io`
+ `https://shiden-rpc.dwellir.com`
+ `https://shiden.api.onfinality.io/public` + 3. Chain ID: `336` + 4. Currency Symbol: `SDN` + 5. Block Explorer URL(Optional): `https://shiden.subscan.io/` +5. Close the Settings menu and from the dropdown select the network you wish to interact with + +### Install apps to your Ledger device + +1. Open Ledger Live app and navigate to “Manager” +2. Connect your Ledger Device and unlock it + 1. If asked, confirm Ledger Manager on your device +3. Search for “Astar EVM” or “Shiden EVM” in the app catalog +4. Click install + +After this step, you should have one or both of these apps: + +
+.default})
+
+.default})
+
+
+
+
+
+
+.default})
+.default})
+.default})
+.default})
+.default})
+.default})
+.default})
+.default}){kind=spacer}
+.default})
+.default})
+.default})
+.default})
+
+.default})
+
+.default})
+
+
+
+
+
+
+
+ 
+
+
+- If prompted to update the device Firmware do so, as it will update the Astar app as well.
+
+
+ 
+
+
+- Once Ledger Live is up to date, ensure the latest Astar app (version 2.52.2 or higher) is installed.
+
+:::tip
+Ledger NanoS users should install the Astar XL version of the app, shown in the image below:
+:::
+
+
+ 
+
+
+### Import Ledger account to Polkadot.js
+
+- Open the Polkadot.js extension.
+- Click the + sign menu option.
+- Choose ‘Attach ledger account.’ Make sure your ledger is unlocked.
+
+
+ 
+
+
+- Follow through the process of Importing a Ledger Account by specifying a descriptive name. The default name and settings are shown in the image below:
+
+
+ 
+
+
+### Configure the Ledger device connection method
+
+- Once the Ledger account has been imported, visit the [Astar Network settings page on the Polkadot.js apps portal](https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Frpc.astar.network#/settings) and ensure **Attach Ledger via WebHID** is the preferred connection method listed under *account options* > *manage hardware connections*, as shown in the image below:
+
+
+ 
+
+
+### Visit the Astar Portal
+
+- Open a browser and visit the [Astar Portal](https://portal.astar.network).
+- Connect the Polkadot.js extension to the Portal.
+- Select the Ledger account that was imported during the last step. Check the toggle so Portal knows the device is a ledger. It can now be used to participate in dApp staking.
+
+
+ 
+
+
+For detailed information about dApp staking or how to stake on the EVM side of Astar Portal using a Ledger device, please refer to the [Astar official documentation] (/docs/build/dapp-staking/for-stakers/) [INSERT LINK] or [Ledger EVM staking guide](./ledger-evm.md)
+
+:::tip
+If you receive a **Ledger error: Failed to execute 'claimInterface' on 'USBDevice': Unable to claim interface** message during the dApp staking claim process, ensure you are performing the operation using a Chromium-based browser such as Chrome or Brave, and the Ledger device connection method is WebHID, as outlined in the previous step.
+:::
+
+
+ 
+
+
+## Ledger NanoS and S-plus/X device limitations
+
+Consider the following scenario: You stake on 2 dApps, and accumulate 2 eras worth of rewards each day. What happens if you do not claim the rewards for an entire month?
+
+- Ledger Nano-S - The Nano-S device supports claiming a maximum of **2 eras** at a time, so for as long as there are more eras to claim in the dApp staking dashboard, you should continue to claim. Based on a month's worth of accumulated rewards (30 eras), 30 claims would need to be initiated using a Nano-S.
+- Ledger Nano X - Based on a maximum of **6 eras per claim,** 10 claims would need to be initiated using a Nano X.
+
+Staking on multiple dApps using a Ledger device may substantially increase the amount of time and/or administrative overhead required to participate in dApp staking in order to maximize benefits. However, although multiple claims may be required to retrieve all rewards from the Portal using a Ledger device, the fees remain the same per era claimed whether they occur in batches, or as individual transactions.
diff --git a/docs/build/build-on-layer-1/integrations/wallets/subwallet.md b/docs/build/build-on-layer-1/integrations/wallets/subwallet.md
new file mode 100644
index 0000000..a99a8d6
--- /dev/null
+++ b/docs/build/build-on-layer-1/integrations/wallets/subwallet.md
@@ -0,0 +1,50 @@
+---
+sidebar_position: 2
+---
+
+# SubWallet
+
+## Overview
+
+SubWallet, Polkadot{.js}, and Talisman extensions allow dApps to connect to them via public interaction with the `injectedWeb3` object of the window browser.
+
+- SubWallet (public with properties `subwallet-js`)
+- Polkadot{.js} (public with properties `polkadot-js`)
+- Talisman (public with properties `talisman`)
+
+
+
+You can open the `injectedWeb3` object in your browser's devtools.
+
+
+
+## How to integrate with a dApp
+
+:::info
+Refer to these examples:
+
+- Github Repository +
-
+
- Bond: 3,200,000 ASTR tokens (3.2M $ASTR) +
- Meet hardware requirements +
If your node stops producing blocks for 1 session, your node will be kicked out of the active set and 1% of the bonded funds will be slashed. Running a node with low performance can lead to skipping blocks which may result in being kicked out of the active set.
+ ++
-
+
- Bond: 32,000 SDN tokens (32k $SDN) +
- Meet hardware requirements +
If your node stops producing blocks for 1 session, your node will be kicked out of the active set and 1% of the bonded funds will be slashed. Running a node with low performance can lead to skipping blocks which can lead to being kicked out of the active set.
+ +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+```
+
+## Troubleshooting
+
+If you are facing a webpack 5 polyfill issue please try using `react-app-rewired`.
+
+```
+npm install react-app-rewired
+
+npm install stream-browserify constants-browserify crypto-browserify os-browserify path-browserify process stream-browserify buffer ethers@^5.7.2
+```
+
+create a file name `config-overrides.js` using the content below.
+```
+const { ProvidePlugin }= require("webpack")
+
+module.exports = {
+ webpack: function (config, env) {
+ config.module.rules = config.module.rules.map(rule => {
+ if (rule.oneOf instanceof Array) {
+ rule.oneOf[rule.oneOf.length - 1].exclude = [/\.(js|mjs|jsx|cjs|ts|tsx)$/, /\.html$/, /\.json$/];
+ }
+ return rule;
+ });
+ config.resolve.fallback = {
+ ...config.resolve.fallback,
+ stream: require.resolve("stream-browserify"),
+ buffer: require.resolve("buffer"),
+ crypto: require.resolve("crypto-browserify"),
+ process: require.resolve("process"),
+ os: require.resolve("os-browserify"),
+ path: require.resolve("path-browserify"),
+ constants: require.resolve("constants-browserify"),
+ fs: false
+ }
+ config.resolve.extensions = [...config.resolve.extensions, ".ts", ".js"]
+ config.ignoreWarnings = [/Failed to parse source map/];
+ config.plugins = [
+ ...config.plugins,
+ new ProvidePlugin({
+ Buffer: ["buffer", "Buffer"],
+ }),
+ new ProvidePlugin({
+ process: ["process"]
+ }),
+ ]
+ return config;
+ },
+}
+```
+Change package.json to start using `react-app-rewired` instead of `react-scripts`.
+
+```
+react-scripts start -> react-app-rewired start
+react-scripts build -> react-app-rewired build
+react-scripts test -> react-app-rewired test
+```
+
+If you are still unable to resolve the issue please post your query to Banana Discord [here](https://discord.gg/3fJajWBT3N)
+
+
+## Learn more
+
+To learn more about Banana Wallet head over to [banana docs](https://banana-wallet-docs.rizelabs.io/)
+
+Full tutorial code is available [here](https://github.com/Banana-Wallet/banana-tutorial/tree/feat/shibuya-tutorial)
+
+If your dApp already uses Rainbowkit then you can use Banana Wallet directly on Shibuya testnet. Please refer [here](https://docs.bananahq.io/integration/wallet-connectors/using-rainbowkit) for more information.
diff --git a/docs/build/build-on-layer-1/smart-contracts/EVM/developer-tooling/hardhat.md b/docs/build/build-on-layer-1/smart-contracts/EVM/developer-tooling/hardhat.md
new file mode 100644
index 0000000..e07708a
--- /dev/null
+++ b/docs/build/build-on-layer-1/smart-contracts/EVM/developer-tooling/hardhat.md
@@ -0,0 +1,115 @@
+---
+sidebar_position: 1
+---
+# Hardhat
+
+### Initialize Your Project
+
+If you're starting your Hardhat project from scratch, we recommend you read the [Hardhat Quick Start](https://hardhat.org/getting-started/#quick-start#overview) page.
+
+### Setting up Your Account
+
+The quickest way to get Hardhat to deploy contracts to a non-local testnet, is to export and use an existing MetaMask account.
+
+To get an account's private key from MetaMask:
+
+1. Open MetaMask.
+2. Select the account you want to export.
+3. Click the three dots on the right side.
+4. Select "Account Details".
+5. Select "Export Private Key".
+6. Enter your password and select "Confirm".
+
+You should see a 64-character hex string similar to the following:
+
+`60ed0dd24087f00faea4e2b556c74ebfa2f0e705f8169733b01530ce4c619883`
+
+Create a new file in your root folder called `private.json` with your private key in it:
+
+```json
+{
+ "privateKey": "60ed0dd24087f00faea4e2b556c74ebfa2f0e705f8169733b01530ce4c619883"
+}
+```
+
+Modify your `hardhat.config.js` file to include:
+
+```js
+// hardhat.config.js
+
+// ...
+
+const { privateKey } = require("./private.json");
+
+// ...
+
+module.exports = {
+ // ...
+
+ networks: {
+ // Shibuya faucet: use #shibuya-faucet room in https://discord.gg/astarnetwork
+ shibuya: {
+ url: "https://evm.shibuya.astar.network",
+ chainId: 81,
+ accounts: [privateKey],
+ },
+
+ // Astar community faucet (please don't abuse): https://as-faucet.xyz/en/astar#
+ astar: {
+ url: "https://evm.astar.network",
+ chainId: 592,
+ accounts: [privateKey],
+ },
+
+ // Shiden community faucet (please don't abuse): https://as-faucet.xyz/en/shiden#
+ shiden: {
+ url: "https://evm.shiden.astar.network",
+ chainId: 336,
+ accounts: [privateKey],
+ },
+ },
+};
+```
+
+Once your accounts are funded, you can deploy the sample contract to Shibuya with `npx hardhat run --network shibuya scripts/deploy.js`.
+
+## Truffle
+
+### Create an Ethereum Account
+
+We recommend using the `@truffle/hdwallet-provider` package for key management. Instructions can be found [here](https://github.com/trufflesuite/truffle/blob/develop/packages/hdwallet-provider/README.md).
+
+### Add Networks to `truffle-config.js`
+
+To deploy and interact with Astar, modify `networks` in `truffle-config.js` to include Astar's networks:
+
+```js
+// truffle-config.js
+module.exports = {
+ networks: {
+ // ... any existing networks (development, test, etc.)
+
+ // Shibuya faucet: use #shibuya-faucet room in https://discord.gg/astarnetwork
+ shibuya: {
+ url: "https://evm.shibuya.astar.network",
+ network_id: 81,
+ },
+
+ // Astar community faucet (please don't abuse): https://as-faucet.xyz/en/astar#
+ astar: {
+ url: "https://evm.astar.network",
+ network_id: 592,
+ },
+
+ // Shiden community faucet (please don't abuse): https://as-faucet.xyz/en/shiden#
+ shiden: {
+ url: "https://evm.shiden.astar.network",
+ network_id: 336,
+ },
+ },
+
+ // ...
+};
+```
+
+Deploy/Migrate by running `truffle migrate --network shibuya`, replacing `shibuya` with your chosen network. If `--network` is not specified, the network values under`development` will be used.
\ No newline at end of file
diff --git a/docs/build/build-on-layer-1/smart-contracts/EVM/developer-tooling/img/thirdweb-explore.png b/docs/build/build-on-layer-1/smart-contracts/EVM/developer-tooling/img/thirdweb-explore.png
new file mode 100644
index 0000000..5c189ee
Binary files /dev/null and b/docs/build/build-on-layer-1/smart-contracts/EVM/developer-tooling/img/thirdweb-explore.png differ
diff --git a/docs/build/build-on-layer-1/smart-contracts/EVM/developer-tooling/index.md b/docs/build/build-on-layer-1/smart-contracts/EVM/developer-tooling/index.md
new file mode 100644
index 0000000..165ab7a
--- /dev/null
+++ b/docs/build/build-on-layer-1/smart-contracts/EVM/developer-tooling/index.md
@@ -0,0 +1,10 @@
+# Developer Tooling
+
+Deploying and interacting with EVM-based smart contracts on Astar is as easy as any other EVM-compatible network. Getting started requires just two steps:
+
+1. Configuring (and funding) your Ethereum account on the respective network.
+2. Adding Astar networks to your Ethereum client.
+
+:::caution
+For Astar and Shiden applications, we _highly_ recommend running your own network node and not relying on our RPC endpoints. This further decentralizes the network, and puts you in control of your uptime requirements.
+:::
\ No newline at end of file
diff --git a/docs/build/build-on-layer-1/smart-contracts/EVM/developer-tooling/own-RPC.md b/docs/build/build-on-layer-1/smart-contracts/EVM/developer-tooling/own-RPC.md
new file mode 100644
index 0000000..e493150
--- /dev/null
+++ b/docs/build/build-on-layer-1/smart-contracts/EVM/developer-tooling/own-RPC.md
@@ -0,0 +1,24 @@
+---
+sidebar_position: 4
+---
+# Your Own RPC Server
+
+For EVM developers and projects, it is not an unreasonable expectation that they should have their own managed EVM endpoints. Relying on public endpoints can introduce additional risk due to centralizaion or improper maintenance, and make them single points of failure.
+
+:::note
+Astar team highly recommends that projects use and maintain their own EVM endpoints.
+:::
+
+Launching an Astar Network endpoint is easy.
+
+:::note
+The EVM RPC server is disabled by default. To enable it, append the `--enable-evm-rpc` flag to the launch string.
+:::
+
+```
+astar-collator --chain=shiden --enable-evm-rpc --unsafe-rpc-external
+```
+
+The launch string above will start an Astar Collator on Shiden network, open up an WS/HTTP endpoint on port `9944`.
+
+We also recommend paying attention to the `--rpc-max-connections` parameter. By default this value is relatively small, so it may be beneficial to increase it to a few thousand.
\ No newline at end of file
diff --git a/docs/build/build-on-layer-1/smart-contracts/EVM/developer-tooling/privy.mdx b/docs/build/build-on-layer-1/smart-contracts/EVM/developer-tooling/privy.mdx
new file mode 100644
index 0000000..ae10a0b
--- /dev/null
+++ b/docs/build/build-on-layer-1/smart-contracts/EVM/developer-tooling/privy.mdx
@@ -0,0 +1,151 @@
+import Tabs from '@theme/Tabs';
+import TabItem from '@theme/TabItem';
+
+# Privy
+
+## Introduction
+
+Privy is the easiest way for web3 developers to onboard their users, regardless of whether they already have wallets, across mobile and desktop. Privy offers [embedded wallets](https://www.privy.io/features/wallets) so you can seamlessly provision self-custodial wallets for users who sign in via email or social login, as well as [powerful connectors](https://www.privy.io/features/connectors) for web3 native users who prefer to sign in with their existing wallets. It’s one library to onboard all users, regardless of where they are in their web3 journey.
+
+Developers building end-user facing applications in the Astar ecosystem can leverage Privy to expand their addressable market, improve onboarding funnel conversion and better understand their users. **For a limited time, Astar developers can get free unlimited access to Privy’s features for their first three months using the product, by reaching out to us at astar@privy.io**. For more information on Privy, check out the [website](http://privy.io), [API docs](http://docs.privy.io), [product demo](http://demo.privy.io), and sample customer integrations ([Lighthouse](http://lighthouse.world/), [Courtyard](http://courtyard.io/), and [Shibuya](http://shibuya.xyz/)).
+
+## Prerequisites
+
+To use Privy in your app, you'll need to:
+
+- Have basic knowledge of JavaScript and React
+- Use React 18 in your app
+- Use only EVM-compatible networks for any on-chain actions
+
+## Getting started
+
+### Step 1
+
+Request API keys by reaching out to our team at astar@privy.io to ensure you’re able to access Privy’s special offer of three free months of unlimited software use. We'll set you up with a [Privy app ID](https://docs.privy.io/guide/console/api-keys#app-id) that you can use to initialize the SDK.
+
+### Step 2
+
+Install the **[Privy React Auth SDK](https://www.npmjs.com/package/@privy-io/react-auth)** using `npm`:
+
+`npm install @privy-io/react-auth@latest`
+
+### Step 3
+
+Once you have your app ID and have installed the SDK, **in your React project, wrap your components with a [PrivyProvider](https://docs.privy.io/reference/react-auth/modules#privyprovider)**. The [PrivyProvider](https://docs.privy.io/reference/react-auth/modules#privyprovider) should wrap any component that will use the Privy SDK.
+
+For example, in a [NextJS](https://nextjs.org/) or [Create React App](https://create-react-app.dev/) project, you may wrap your components like so:
+
+Banana SDK Demo
+ {walletAddress &&Wallet Address: {walletAddress}
} + + + + + + +Output Panel
+
+
+{isLoading ? "Loading.." : output}
+Subscan is the most used explorer in the Polkadot ecosystem. With Subscan you can search the complete Astar Network. Subscan support Substrate and Ethereum API. BlockScout is the best explorer for developers who are building in our EVM environment, it has all the features as EtherScan.
+Subscan: https://astar.subscan.io
+BlockScout: https://blockscout.com/astar
+Polkadot JS: https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Fastar.api.onfinality.io%2Fpublic-ws#/explorer
+ +Subscan is the most used explorer in the Polkadot ecosystem. With Subscan you can search the complete Astar Network. Subscan support Substrate and Ethereum API. BlockScout is the best explorer for developers who are building in our EVM environment, it has all the features as EtherScan.
+Subscan: https://shiden.subscan.io
+BlockScout: https://blockscout.com/shiden
+Polkadot JS: https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Fshiden.api.onfinality.io%2Fpublic-ws#/explorer
+ +Subscan is the most used explorer in the Polkadot ecosystem. With Subscan you can search the complete Astar Network. Subscan support Substrate and Ethereum API. BlockScout is the best explorer for developers who are building in our EVM environment, it has all the features as EtherScan.
+Subscan: https://shibuya.subscan.io
+BlockScout: https://blockscout.com/shibuya
+Polkadot JS: https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Frpc.shibuya.astar.network#/explorer
+ +
+
\ No newline at end of file
diff --git a/docs/build/build-on-layer-1/smart-contracts/_category_.json b/docs/build/build-on-layer-1/smart-contracts/_category_.json
new file mode 100644
index 0000000..669e062
--- /dev/null
+++ b/docs/build/build-on-layer-1/smart-contracts/_category_.json
@@ -0,0 +1,4 @@
+{
+ "label": "Smart Contracts",
+ "position": 1
+}
diff --git a/docs/build/build-on-layer-1/smart-contracts/index.md b/docs/build/build-on-layer-1/smart-contracts/index.md
new file mode 100644
index 0000000..2dd1d50
--- /dev/null
+++ b/docs/build/build-on-layer-1/smart-contracts/index.md
@@ -0,0 +1,22 @@
+---
+title: Smart Contracts
+---
+
+# Overview
+
+This section contains all the information required to start building, testing, and deploying Substrate-native or EVM-based smart contracts on Astar's Substrate-based networks. Substrate is a modular blockchain framework using pallets to support granular features, such as execution environments for both Wasm and EVM smart contracts.
+
+## Wasm (ink!)
+
+Wasm smart contracts are powered by the `pallet-contracts` pallet for Substrate. For information about how to build and deploy ink! and Rust-based smart contracts on the Substrate-native virtual machine, otherwise known as the Wasm VM or **Astar Substrate Native Network**, see the Wasm section.
+
+## EVM
+
+For information about how to build and deploy Solidity-based smart contracts on the Frontier-based `EVM` pallet for Substrate, otherwise known as the **Astar Substrate EVM Network**, see the EVM section.
+
+```mdx-code-block
+import DocCardList from '@theme/DocCardList';
+import {useCurrentSidebarCategory} from '@docusaurus/theme-common';
+
+Astar Discord server
+ +1. Join the **Astar Discord** server [here](https://discord.gg/astarnetwork). +2. Accept the invite. +3. Take the **Developer** role under **#roles**. +4. Navigate to the **Builder/#-astar-polkadot** channel. + +Subscan is the most widely used explorer in the Polkadot ecosystem. Subscan has indexed Astar Network in its entirety, and supports both Substrate and Ethereum APIs. BlockScout is the best explorer for developers who are building on Astar EVM, as it has all the features of EtherScan.
+Under certain circumstances, the Polkadot.js apps portal may also be used to explore blocks.
+Subscan: https://astar.subscan.io
+Polkadot JS: https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Fastar.api.onfinality.io%2Fpublic-ws#/explorer
+ +Subscan is the most used explorer in the Polkadot ecosystem. With Subscan you can search the complete Astar Network. Subscan support Substrate and Ethereum API. BlockScout is the best explorer for developers who are building on Astar EVM, as it has all the features of EtherScan.
+Under certain circumstances, the Polkadot.js apps portal may also be used to explore blocks.
+Subscan: https://shiden.subscan.io
+Polkadot JS: https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Fshiden.api.onfinality.io%2Fpublic-ws#/explorer
+ +Subscan is the most used explorer in the Polkadot ecosystem. With Subscan you can search the complete Astar Network. Subscan support Substrate and Ethereum API. BlockScout is the best explorer for developers who are building on Astar EVM, as it has all the features of EtherScan.
+Sirato is a contract explorer for ink! smart contracts. Sirato provides a contract verification service enabling users to decode information about contract code and instances that have been deployed using the Contracts Pallet. The service allows users to upload source code and metadata to the service which will verify it matches the on-chain. For instructions on how to use the service you can refer here.
+Under certain circumstances, the Polkadot.js apps portal may also be used to explore blocks.
+Subscan: https://shibuya.subscan.io
+Sirato: https://shibuya.sirato.xyz/
+Polkadot JS: https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Frpc.shibuya.astar.network#/explorer
+ +
+
\ No newline at end of file
diff --git a/docs/build/build-on-layer-1/smart-contracts/wasm/smart-contract-wasm.md b/docs/build/build-on-layer-1/smart-contracts/wasm/smart-contract-wasm.md
new file mode 100644
index 0000000..c1f9d16
--- /dev/null
+++ b/docs/build/build-on-layer-1/smart-contracts/wasm/smart-contract-wasm.md
@@ -0,0 +1,72 @@
+---
+sidebar_position: 1
+---
+
+# Smart Contract Stack
+
+## Smart Contract Runtime Environment
+
+Astar & Shiden runtimes are based on Substrate, and both networks incorporate `pallet-contracts`, a sandboxed environment used to deploy and execute WebAssembly smart contracts. Any language that compiles to Wasm may be deployed and run on this Wasm Virtual Machine, however, the code should be compatible with the `pallet-contracts` [API](https://docs.rs/pallet-contracts/latest/pallet_contracts/api_doc/trait.Current.html).
+
+To avoid unnecessary complexity, and writing boilerplate code, the most appropriate method of building will involve the use of an eDSL specifically targeting `pallet-contracts`, such as [ink!] (based on Rust), or [ask!] (based on AssemblyScript), or possibly others as the ecosystem grows.
+
+After compilation, a Wasm blob can then be deployed and stored on-chain.
+
+### Execution Engine
+
+Pallet-contracts uses [wasmi](https://github.com/paritytech/wasmi) as a Wasm interpreter to execute Wasm smart contract blobs. Although there is a faster JIT interpreter such as [wasmtime](https://github.com/bytecodealliance/wasmtime) available in the native runtime, smart contracts are an untrusted environment which require a higher degree of correctness of interpretation, which makes wasmi a more suitable option.
+
+### Two-step Deployment of Contracts
+
+The contract code (Wasm blob), and contract address and storage are decoupled from one another other, so require two steps to deploy a new contract on-chain:
+
+1. First, upload the Wasm contract on-chain (every contract Wasm code has a `code_hash` as an identifier).
+2. Second, instantiate the contract - it will create an address and storage for that contract.
+3. Anyone can instantiate a contract based on its `code_hash`.
+
+There are several benefits of decoupling the contract code from the address/storage:
+
+- To save space on-chain. Since a contract can have several constructors and instantiations, a redeployment will create a new instance based on the same underlying code. Think about standardized tokens, like [PSP22][PSP22] & [PSP34][PSP34], that will have one `code_hash` & `blob` living on-chain, and as many instantiations as are needed, rather than having to upload code with each new instantiation (for example, on Ethereum).
+- To instantiate a new contract using code within an existing smart contract (see the delegator example), `code_hash` is all that is needed.
+- Some standard contracts such as ([PSP22][PSP22] and [PSP34][PSP34]) will only be uploaded on-chain once, preventing users from having to pay gas costs for uploading new code.
+- Update contract code for an address: replace the contract code at the specified address with new code (see [set_code_hash][set_code_hash]). Storage and balances will be preserved.
+
+### For More Information About `pallet-contracts`
+
+- [`pallet-contracts` in Rust docs](https://docs.rs/pallet-contracts/14.0.0/pallet_contracts/index.html)
+- [`pallet-contracts` on Github](https://github.com/paritytech/substrate/tree/master/frame/contracts)
+
+## Client APIs
+
+The only library available to communicate with smart contracts is [Polkadot.js API](https://github.com/polkadot-js/api).
+
+:::info
+This API provides application developers the ability to query a node and interact with the Polkadot or Substrate chains using Javascript.
+:::
+
+Parity also developed a web application to interact with contracts called [contracts-ui](https://github.com/paritytech/contracts-ui).
+
+## The Wasm Stack vs. Ethereum
+
+| | Ethereum | Astar |
+| --- | --- | --- |
+| L1 Architecture | [Ethereum clients](https://ethereum.org/en/developers/docs/nodes-and-clients/) | [Substrate](https://substrate.io/)
+Smart Contract Runtime Environment | [EVM] | Wasm [pallet-contract] + EVM [frontier]
+Gas Model | [fixed price per instruction] | [weight] + [storage fees][storage] + [loading fees]
+Smart Contract DSLs | Solidity and Vyper | [ink!] (Rust) and [ask!] (AssemblyScript)
+Standards | [EIPs] | [PSPs]
+
+[weight]: https://docs.substrate.io/reference/how-to-guides/weights/
+[PSP22]: https://github.com/w3f/PSPs/blob/master/PSPs/psp-22.md
+[PSP34]: https://github.com/w3f/PSPs/blob/master/PSPs/psp-34.md
+[set_code_hash]: https://docs.rs/ink_env/4.0.0-rc/ink_env/fn.set_code_hash.html
+[ink!]: https://github.com/paritytech/ink
+[ask!]: https://github.com/ask-lang/ask
+[EVM]: https://ethereum.org/en/developers/docs/evm/
+[pallet-contract]: https://github.com/paritytech/substrate/tree/master/frame/contracts
+[fixed price per instruction]: https://ethereum.github.io/yellowpaper/paper.pdf
+[frontier]: https://github.com/paritytech/frontier
+[storage]: https://github.com/paritytech/substrate/blob/c00ed052e7cd72cfc4bc0e00e38722081b789ff5/frame/contracts/src/lib.rs#L351
+[loading fees]: https://github.com/paritytech/substrate/blob/97ae6be11b0132224a05634c508417f048894670/frame/contracts/src/lib.rs#L331-L350
+[EIPs]: https://eips.ethereum.org/
+[PSPs]: https://github.com/w3f/PSPs
diff --git a/docs/build/build-on-layer-1/smart-contracts/wasm/swanky-suite/_category_.json b/docs/build/build-on-layer-1/smart-contracts/wasm/swanky-suite/_category_.json
new file mode 100644
index 0000000..fd4ba0d
--- /dev/null
+++ b/docs/build/build-on-layer-1/smart-contracts/wasm/swanky-suite/_category_.json
@@ -0,0 +1,4 @@
+{
+ "label": "Swanky Suite",
+ "position": 7
+}
diff --git a/docs/build/build-on-layer-1/smart-contracts/wasm/swanky-suite/cli.md b/docs/build/build-on-layer-1/smart-contracts/wasm/swanky-suite/cli.md
new file mode 100644
index 0000000..a9ffcb4
--- /dev/null
+++ b/docs/build/build-on-layer-1/smart-contracts/wasm/swanky-suite/cli.md
@@ -0,0 +1,371 @@
+---
+sidebar_position: 1
+# Display h2 to h5 headings
+toc_min_heading_level: 2
+toc_max_heading_level: 4
+---
+
+import Figure from '/src/components/figure'
+import Tabs from '@theme/Tabs'
+import TabItem from '@theme/TabItem'
+
+# Swanky CLI
+
+Swanky CLI is a Node.js based CLI application that abstracts away and extends the functionality of Polkadot.js, `cargo contract`, and other ink! based smart contract developer tools.
+It aims to ease development of and interaction with ink! smart contracts and provides simple tools to bootstrap contract environment (project) with contract and integration tests templates, local node and accounts management, smart contracts interaction on both local and remote networks, compatibility checks between the contract pallet and compiler...
+
+It also comes with a preconfigured Docker image and .codespaces configuration for easy dev environment setup.
+
+With all of the features mentioned above, even more is in active or planned development. The whole project is public, and everyone is welcome to contribute or suggest features:
+
+- [Swanky CLI repo](https://github.com/AstarNetwork/swanky-cli)
+- [Swanky CLI project](https://github.com/orgs/AstarNetwork/projects/3)
+
+:::info
+Templates provided in the current version of swanky-cli, as well as environment in the swanky-base image, and supported tools target ink! v4, and use `cargo contract` v2.
+
+Cargo contract v3 introduced breaking changes to how artifacts are stored and you'll have to move them manually if you wish to use it.
+:::
+
+## Installing
+
+The CLI can be installed and used in different ways:
+
+- using a preconfigured environment of a dev-container locally with VS Code
+- using the dev-container in a cloud-based environment such as GitHub Codespaces or Gitpod
+- using the swanky-base container image locally (same is used in the dev-container)
+- downloading a precompiled binary
+- as an npm package (installed globally, or via the `npx` command)
+
+:::caution
+Note that using the precompiled binaries, NPM, or compiling it yourself requires you to have the [local environment set up](/docs/build/build-on-layer-1/environment/ink_environment.md) correctly
+:::
+
+### Dev container
+
+Using [dev container](/docs/build/build-on-layer-1/environment/dev-container.md) is the easiest way to use `swanky-cli`, it includes all the environment setup and will support auto-updates in the future.
+
+To run your project in the dev container follow the steps on [swanky-dev-container Github](https://github.com/AstarNetwork/swanky-dev-container).
+
+### Cloud based environments
+
+Similar to using the dev container locally, GitHub will detect the `.devcontainer` config in your project and let you run the project in a cloud-based IDE.
+
+You'll have to sign up for an account to use [Gitpod](https://www.gitpod.io/), but the process is the same.
+
+:::caution
+Currently it is not possible to forward ws:// ports from GitHub Codespaces, so if you'd like to interact with the swanky-node from contracts-ui or a similar service, use Gitpod or one of the other methods.
+:::
+
+### Download the precompiled binaries
+
+1. Download the correct archive for your platform from the [releases section of swanky-cli github page](https://github.com/AstarNetwork/swanky-cli/releases).
+
+2. Extract the archive to the appropriate location, for example the `software` directory.
+
+3. Add the `swanky` executable to your path variable by creating a symbolic link to it from a common `bin` directory or somewhere similar.
+
+Astar Discord server
+ +1. Join the **Astar Discord** server [here](https://discord.gg/astarnetwork). +2. Accept the invite. +3. Take the **Developer** role under **#roles**. +4. Navigate to the **Builder/#-astar-polkadot** channel. + +
+ 
+
+
+
+Use the network selector and switch to zKatana network, or allow MetaMask to switch to zKatana network for you.
+
+
+
+ 
+
+
+
+Click on the Bridge tab on the left-hand side. Ensure Sepolia is selected as Bridge source, and zKatana is selected as destination. After you have entered the amount of ETH to transfer, press the Confirm button.
+
+
+
+ 
+
+
+
+Sign the MetaMask transaction.
+
+:::note
+Once the transaction shows as confirmed on the MetaMask Activity tab, it will take approximately 5-10 minutes for the Astar Portal and MetaMask to update your balance on the zKatana network side.
+:::
+
+
+
+ 
+
+
+ 
+
+
+
+ You should now see the bridged ETH within MetaMask for use on Astar zkEVM.
diff --git a/docs/build/build-on-layer-2/faq/_category_.json b/docs/build/build-on-layer-2/faq/_category_.json
new file mode 100644
index 0000000..3c3fb1c
--- /dev/null
+++ b/docs/build/build-on-layer-2/faq/_category_.json
@@ -0,0 +1,4 @@
+{
+ "label": "FAQ",
+ "position": 9
+}
\ No newline at end of file
diff --git a/docs/build/build-on-layer-2/faq/zkevm-eth-faq.md b/docs/build/build-on-layer-2/faq/zkevm-eth-faq.md
new file mode 100644
index 0000000..be34444
--- /dev/null
+++ b/docs/build/build-on-layer-2/faq/zkevm-eth-faq.md
@@ -0,0 +1,65 @@
+---
+sidebar_position: 2
+title: zkEVM and EVM Equivalence FAQs
+sidebar_label: EVM Equivalence
+---
+
+This document compiles some of the frequently asked questions related to the Astar zkEVM's equivalence with EVM. For more details, check out [Polygon zkEVM documentation](https://wiki.polygon.technology/docs/category/zkevm-protocol/).
+
+---
+
+### What is the difference between EVM Compatibility and EVM Equivalence?
+
+The ultimate goal is not **compatibility**. The ultimate goal is **equivalence**. **Solutions that are compatible enable most existing apps to work, but sometimes with code changes**. Additionally, compatibility may lead to the breaking of developer toolings.
+
+**zkEVM strives for EVM Equivalence because it means that most applications, tools, and infrastructure built on Ethereum can immediately port over to Astar zkEVM with limited to no changes needed**. Things are designed to work 100% on day one. This is critical because:
+
+1. **Development teams don't have to make changes to their code**, which could introduce security vulnerabilities.
+2. **No code changes are needed**. You don't need additional audits, which saves time and money.
+3. **zkEVM ultimately benefits from the security and decentralization of Ethereum**, since transactions are finalized on Ethereum.
+4. Astar zkEVM **benefits from the already vibrant and active Ethereum community**.
+5. Allows for **fast user onboarding**, since dApps built on Ethereum are already compatible.
+
+### Why is EVM Equivalence needed?
+
+Ethereum isn’t just a blockchain. It’s a rich ecosystem of smart contracts, developer tools, infrastructure, and wallets. It’s a vibrant community of developers, auditors, and users.
+
+The best way to scale Ethereum is to strive to maintain equivalence with this ecosystem. Astar zkEVM will give users and developers an almost identical experience to Ethereum L1 with significant scalability and user experience improvements.
+
+### What EVM opcodes are different on Astar zkEVM?
+
+The following EVM opcodes are different in Astar zkEVM: **SELFDESTRUCT**, **EXTCODEHASH**, **DIFFICULTY**, **BLOCKHASH**, and **NUMBER**.
+
+### What precompiled smart contract functions does Astar zkEVM support?
+
+The following precompiled contracts are supported in the zkEVM: **ecRecover** and **identity**.
+
+Other precompiled contracts have no effect on the zkEVM state tree and are treated as a `revert`, returning all gas to the previous context and setting the `success` flag to "0".
+
+### Which precompiled contracts are missing in the current zkEVM version?
+
+Astar zkEVM supports all precompiled contracts except **SHA256**, **BLAKE**, and **PAIRINGS**.
+
+### When will we get Type 2 EVM Equivalence?
+
+Currently, Astar zkEVM has Type 3 equivalence with EVM. It will reach Type 2 and full equivalence when all pre-compiled contracts are supported.
+
+### Can you explain the process of rollbacks and reverts in Astar zkEVM? Are they similar to EVM?
+
+The process of rollbacks and reverts is similar to regular EVMs. Whenever there is an error or a condition that triggers a revert, it uses the `REVERT` instruction to stop the execution and then returns an error message.
+
+Rollbacks can also happen sometimes because of an invalid zk-proof (this triggers something new to Astar zkEVM) which would cause the transaction to be aborted and all the state changes to be undone.
+
+### How does the Astar zkEVM handle events and logging?
+
+Astar zkEVM handles events and logging in a similar way to other EVMs, by emitting events and logging them on the blockchain for future reference.
+
+### How similar are Astar zkEVM error messages with Ethereum?
+
+Astar zkEVM has a high level of compatibility with Ethereum errors. You need to bear in mind that Astar zkEVM has more constraints than Ethereum and also uses different concepts (for example, batches instead of blocks). Therefore, it will give more types of errors with more precision (for example, the concept of gas in Astar zkEVM is more broken down).
+
+### Can Chainlink use their token (ERC677) in Astar zkEVM?
+
+You can deploy any smart contract on Astar zkEVM, just like you would on Ethereum, so you can deploy any token. If you want to send the token to Ethereum, the bridge will convert it to an ERC20 token (bi-directional bridge).
+
+The bridge also has **low-level message passing functionality** that can be used to bridge any type of value, including NFTs and other token standards.
diff --git a/docs/build/build-on-layer-2/faq/zkevm-general-faq.md b/docs/build/build-on-layer-2/faq/zkevm-general-faq.md
new file mode 100644
index 0000000..6c0f718
--- /dev/null
+++ b/docs/build/build-on-layer-2/faq/zkevm-general-faq.md
@@ -0,0 +1,93 @@
+---
+sidebar_position: 1
+title: General FAQs related to zkEVM
+sidebar_label: General FAQs
+---
+
+# General FAQ
+
+## Overview
+
+This document compiles some of the frequently asked questions related to the Astar zkEVM. For more details, check out [Polygon zkEVM documentation](https://wiki.polygon.technology/docs/category/zkevm-protocol/).
+
+
+### What is Astar zkEVM?
+
+Astar zkEVM is a layer 2 scaling solution for Ethereum that offers an EVM-equivalent smart contract environment. This means that most of the existing smart contracts, developer tools, and wallets for Ethereum also work with the Astar zkEVM.
+
+Astar zkEVM harnesses the power of Zero-Knowledge proofs to reduce transaction costs and increase throughput on L2, all while inheriting the security of Ethereum L1.
+
+### What are the main features of Astar zkEVM?
+
+- **EVM-equivalence**: Most Ethereum smart contracts, wallets, and tools work seamlessly on Astar zkEVM.
+- Inherits its **security from Ethereum.**
+- Lower cost compared to L1 and **faster finality compared to other L2 solutions** such as Optimistic Rollups
+- **Zero-Knowledge Proof-powered scalability** aiming for similar throughput to PoS.
+
+### What kind of gas fee reduction can users expect from Astar zkEVM?
+
+Compared to Ethereum Layer 1, users can expect a significant reduction in gas fees. Astar's layer 2 scaling solution batches transactions together, effectively spreading the cost of a single layer 1 transaction across multiple layer 2 transactions.
+
+### How do zk Rollups work?
+
+zk Rollups aggregate large batches of transactions and finalize them on the Ethereum network using zero-knowledge validity proofs.
+
+### What is so unique about zkEVMs?
+
+ZkEVMs were thought to be years away; not practical or competitive with other ZK L2s as there seemed to loom an unavoidable tradeoff - Full EVM equivalence or high performance, but not both.
+
+However, given the proving system breakthroughs pioneered by Polygon Labs, full EVM equivalence is now possible while at the same time offering higher performance and lower costs than alternative L1s, optimistic rollups, and other kinds of zk Rollups.
+
+### How do I connect Astar zkEVM to a Metamask Wallet?
+
+In order to add the Astar zkEVM network to your wallet, please check out the zkEVM quickstart guide [INSERT LINK] which contains the latest RPC details and videos demonstrating useful functionalities.
+
+### How does Astar zkEVM compare to other zkEVMs in terms of technology and performance? What are the technical advantages there?
+
+The best reference is Vitalik Buterin's comprehensive analysis of zkEVMs [published in his blog](https://vitalik.ca/general/2022/08/04/zkevm.html).
+
+However, the major difference between Astar zkEVM and others is the zkEVM's efficient prover and high Ethereum equivalence. Regarding the design of the prover/verification component: other projects use an arithmetic circuit approach while the Astar zkEVM zkProver uses the State Machine approach.
+
+### Is Astar zkEVM open source?
+
+Yes, [Astar zkEVM is fully open-source](https://polygon.technology/blog/polygon-zkevm-is-now-fully-open-source) and uses Polygon zkEVM solution with an AGPL v3 open-source license.
+
+### Does Astar zkEVM have a separate token?
+
+No. **ETH will be used for gas fees**. It is expected that ASTR will be used for staking and governance in Astar zkEVM in the future.
+
+It is also important to note that Astar zkEVM **natively supports Account Abstraction via ERC-4337**, which will allow users to pay fees with any token (bring your own gas).
+
+### What types of dApps can be deployed on Astar zkEVM?
+
+Any dApp that is compatible with EVM can be deployed, except for those which require a specific precompiled contract that is currently not supported by zkEVM. For more details related to supported precompiled contracts, check out the [Polygon zkEVM documentation](https://wiki.polygon.technology/docs/category/zkevm-protocol/).
+
+### Can this Layer 2 zkEVM work with other chains?
+
+**At the moment, the answer is No**. Aspirationally, the goal in the future is to build one of many chains that allow users' assets to move from layer 2 (L2) to layer 2. With that being said, users will not be able to utilize this functionality at launch, but L2 to L2 movement is included in our future roadmap.
+
+### What are some of the main use cases for Astar zkEVM?
+
+**DeFi Applications**: Because of Astar zkEVM’s high security and censorship resistance nature, it's a good fit for DeFi applications. zkRollups don’t have to wait for long periods for deposits and withdrawals; Astar zkEVM offers better capital efficiency for DeFi dApps/users.
+
+**NFT, Gamefi, and Enterprise Applications**: Low gas cost, high transaction speed, and a greater level of security coupled with Ethereum composability are attractive to blue chip NFTs, GameFi, and Enterprise applications.
+
+**Payments**: Users interested in transacting with each other in real-time within a near-instantaneous and low-fee environment will appreciate the value Astar zkEVM provides.
+
+### When Astar zkEVM publishes a proof on L1, how can someone trust that that proof is accurate and includes all the transactions it claims it does?
+
+Our zkRollup smart contract warranties it. It's trustworthy due to data availability and the fact that the published validity proofs are quick and easily verifiable SNARK proofs.
+
+### Does Astar zkEVM have support for both Solidity and Vyper?
+
+Yes, any language that gets compiled to EVM opcode should work with Astar zkEVM. In other words, if it can run on Ethereum, it can run on the Astar zkEVM.
+
+### What is an RPC node?
+
+**RPC (Remote Procedure Call)** is a JSON-RPC interface compatible with Ethereum. It enables the integration of Astar zkEVM with existing tools, such as Metamask, Etherscan, and Infura. It adds transactions to the pool and interacts with the state using read-only methods.
+
+Additionally, for a software application to interact with the Ethereum blockchain (by reading blockchain data and/or sending transactions to the network), it must connect to an Ethereum node. It works the same way as other nodes such as geth.
+
+### Do you support the JSON-RPC EVM query spec? What are the unsupported queries?
+
+All official queries are supported (`eth_*` endpoints). We are working on support from some "extra official endpoints" such as `debug_*`.
diff --git a/docs/build/build-on-layer-2/faq/zkevm-protocol-faq.md b/docs/build/build-on-layer-2/faq/zkevm-protocol-faq.md
new file mode 100644
index 0000000..d204d4d
--- /dev/null
+++ b/docs/build/build-on-layer-2/faq/zkevm-protocol-faq.md
@@ -0,0 +1,83 @@
+---
+sidebar_position: 3
+title: zkEVM Protocol FAQs
+sidebar_label: Protocol FAQs
+---
+This document compiles some of the frequently asked questions related to the Astar zkEVM protocol. For more details, check out [Polygon zkEVM documentation](https://wiki.polygon.technology/docs/category/zkevm-protocol/).
+
+---
+
+### How are transactions collected and ordered?
+
+- Transactions on the Astar zkEVM network are **created in users' wallets and signed with their private keys**.
+- Once generated and signed, the **transactions are sent to the Trusted Sequencer's node** via their JSON-RPC interface.
+- The transactions are then **stored in the pending transactions pool, where they await the Sequencer's selection**.
+- The **Trusted Sequencer reads transactions** from the pool and decides whether to discard them or order and execute them.
+- Lastly, the **Sequencer organizes the transactions into batches**, followed by the sequencing of the batches.
+
+### Are there any time or transaction intervals for a sequencer to wait before moving forward to make a Rollup batch?
+
+The sequencer always has an open batch. Transactions are added to this batch until this batch is full or a big timeout happens. Those batches are also accumulated until it reaches 128K of batches (or a big timeout) and then a sequencing transaction to L1 is sent.
+
+From the L2 user perspective, a new L2 block (different from the L2 batch) is closed and sent to the user. The user perceives the transaction finality even if the L2 batch is not closed. **One L2 Transaction is one L2 Block**.
+
+### What are the stages that a transaction goes through in order to be finalized on L1?
+
+The process of validating a specific transaction within the batch typically involves three steps:
+
+1. **Trusted State:** This state is given by the trusted sequencer almost instantaneously. No L1 transactions are required.
+
+2. **Virtual State:** Transactions are in L1. These transactions and their order cannot be modified as the state is final and anybody could calculate.
+
+3. **Verified State:** When the virtual state is verified by the smart contract, the funds can be withdrawn.
+
+### How does a Sequencer validate a specific transaction in order to generate proof?
+
+The Sequencer retrieves the transaction from the transaction pool and verifies that it is properly formatted and contains all the necessary information. The Sequencer does the following checks:
+
+- Checks that the transaction is valid by checking that the Sender has enough funds to cover the gas costs of the transaction and that the smart contract called, if any, is valid and has the correct bytecode.
+
+- Checks that the transaction is not a duplicate by checking the transaction nonce of the Sender to ensure that it is one greater than the last nonce used.
+
+- Checks that the transaction is not a double-spend by checking that the Sender's account balance has not been already spent in another transaction.
+
+Once the transaction is deemed valid, the Sequencer applies the transaction to the current state of the Astar zkEVM, updating the state of the smart contract and the account balances as necessary. Duration and cost vary depending on traffic and prevailing gas prices.
+
+### When do transactions achieve finality in Astar zkEVM?
+
+**If the user trusts the Sequencer**, transactions are considered final once the Sequencer sequences it (or Trusted State).
+
+**If the user trusts only the L1 state**, then the transaction will be final at the moment it reaches **Virtual State**. This means, once the data is available and the transaction is already on L1.
+
+**In case the user needs to withdraw funds**, he/she needs to wait for the Prover to convert the implicit state to an explicit state. We call this last state the **Consolidated or Verified State**.
+
+### Are Sequencers and Provers in-house or external? How do you ensure that your Sequencers and Provers maintain decentralization?
+
+Astar zkEVM's **Sequencer will be centralized during early stages**. We have a roadmap to decentralize the sequencer in future releases.
+
+Likewise, the **Prover is also centralized at the beginning** but the vision is to enable a Provers market. Provers cannot do much but generate proofs. To have a decentralized system of Provers is much more critical (and difficult) than the Sequencer.
+
+### Can a zkNode serve as both Sequencer and Aggregator? If not, how is it determined what role a node can play?
+
+A zkNode can potentially serve as both a sequencer and an aggregator, depending on the specific implementation of the zero-knowledge proof protocol.
+
+In some implementations, a node may only be able to perform one function or the other. The role a node can play is determined by the specific implementation of the protocol and the requirements of the network. For example, some protocols may require a certain number of nodes to perform the role of sequencer and a certain number to perform the role of aggregator in order to ensure the security and efficiency of the network.
+
+### How exactly do the state sync components do the syncing in L2 after a transaction batch and its validity proof is mined on L1?
+
+An easy way to summarize is that for each batch, one hash named `globalExitRoot` is transferred from **L1 → L2** and another hash is transferred from **L2 → L1** named `localExitRoot`.
+
+`globalExitRoot` mainly includes all the deposits and `localExitRoot` includes all the withdrawals.
+
+### What is Forced Batches?
+
+A Forced Batch is an L2 batch included in an L1 transaction. Trusted Sequencer is forced to include those batches. This is how a user guarantees that they can withdraw funds even if they are censored by Trusted Sequencer.
+
+This property is what memes the system censorship resistance.
+
+### What is an Emergency State, and when is it triggered?
+
+Emergency State halts the functionalities such as the sequencing of batches, verifying of batches, and forced batches.
+
+It can be triggered by the owner of a smart contract or, in the case of Astar zkEVM, by a Security Council multisig. This means that the Security Council can invoke the Emergency State if the pending state timeout is reached or a threatening vulnerability occurs.
+
diff --git a/docs/build/build-on-layer-2/fee.md b/docs/build/build-on-layer-2/fee.md
new file mode 100644
index 0000000..8440f44
--- /dev/null
+++ b/docs/build/build-on-layer-2/fee.md
@@ -0,0 +1,16 @@
+---
+sidebar_position: 7
+title: Astar zkEVM Fee Calculation
+sidebar_label: Fee Calculation
+---
+
+## How do network fees on Astar zkEVM work?
+In Astar zkEVM the gas fee is calculated by applying a fixed factor over L1 gas fee. That price factor is a fixed value and doesn't change often and it's value is based the rollup's cost to publish tx to L1. To Simply put, gas prices in L2 will linearly follow gas prices in L1.
+
+$$
+L2_{gas\_fee} = L1_{gas\_fee} * Factor
+$$
+
+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)
+
+The support for congestion mechanism based EIP-1559 [here](https://eips.ethereum.org/EIPS/eip-1559) is planned for future and will make the L2 gas fee dynamic.
\ No newline at end of file
diff --git a/docs/build/build-on-layer-2/img/add_zkEVM_network1.jpg b/docs/build/build-on-layer-2/img/add_zkEVM_network1.jpg
new file mode 100644
index 0000000..18f92e9
Binary files /dev/null and b/docs/build/build-on-layer-2/img/add_zkEVM_network1.jpg differ
diff --git a/docs/build/build-on-layer-2/img/add_zkEVM_network2.jpg b/docs/build/build-on-layer-2/img/add_zkEVM_network2.jpg
new file mode 100644
index 0000000..0cc033a
Binary files /dev/null and b/docs/build/build-on-layer-2/img/add_zkEVM_network2.jpg differ
diff --git a/docs/build/build-on-layer-2/img/astar-bridge-zKatana-Shibuya1.jpg b/docs/build/build-on-layer-2/img/astar-bridge-zKatana-Shibuya1.jpg
new file mode 100644
index 0000000..4b0b73b
Binary files /dev/null and b/docs/build/build-on-layer-2/img/astar-bridge-zKatana-Shibuya1.jpg differ
diff --git a/docs/build/build-on-layer-2/img/astar-bridge-zKatana-Shibuya2.jpg b/docs/build/build-on-layer-2/img/astar-bridge-zKatana-Shibuya2.jpg
new file mode 100644
index 0000000..07405c2
Binary files /dev/null and b/docs/build/build-on-layer-2/img/astar-bridge-zKatana-Shibuya2.jpg differ
diff --git a/docs/build/build-on-layer-2/img/astar-bridge-zKatana-Shibuya3.jpg b/docs/build/build-on-layer-2/img/astar-bridge-zKatana-Shibuya3.jpg
new file mode 100644
index 0000000..f91a7aa
Binary files /dev/null and b/docs/build/build-on-layer-2/img/astar-bridge-zKatana-Shibuya3.jpg differ
diff --git a/docs/build/build-on-layer-2/img/astar-bridge-zKatana-Shibuya4.jpg b/docs/build/build-on-layer-2/img/astar-bridge-zKatana-Shibuya4.jpg
new file mode 100644
index 0000000..749d82a
Binary files /dev/null and b/docs/build/build-on-layer-2/img/astar-bridge-zKatana-Shibuya4.jpg differ
diff --git a/docs/build/build-on-layer-2/img/metamask-network.png b/docs/build/build-on-layer-2/img/metamask-network.png
new file mode 100644
index 0000000..8e1e348
Binary files /dev/null and b/docs/build/build-on-layer-2/img/metamask-network.png differ
diff --git a/docs/build/build-on-layer-2/img/metamask-sepolia-select.png b/docs/build/build-on-layer-2/img/metamask-sepolia-select.png
new file mode 100644
index 0000000..7ec74d6
Binary files /dev/null and b/docs/build/build-on-layer-2/img/metamask-sepolia-select.png differ
diff --git a/docs/build/build-on-layer-2/img/wallet-select.jpg b/docs/build/build-on-layer-2/img/wallet-select.jpg
new file mode 100644
index 0000000..8fce1c6
Binary files /dev/null and b/docs/build/build-on-layer-2/img/wallet-select.jpg differ
diff --git a/docs/build/build-on-layer-2/img/zKatana-network1.jpg b/docs/build/build-on-layer-2/img/zKatana-network1.jpg
new file mode 100644
index 0000000..2deb382
Binary files /dev/null and b/docs/build/build-on-layer-2/img/zKatana-network1.jpg differ
diff --git a/docs/build/build-on-layer-2/index.md b/docs/build/build-on-layer-2/index.md
index 4bb4fba..09f18d4 100644
--- a/docs/build/build-on-layer-2/index.md
+++ b/docs/build/build-on-layer-2/index.md
@@ -1,7 +1,33 @@
---
-title: Build on Astar zkEVM
+title: Build on Layer 2
---
import Figure from '/src/components/figure'
-# Why build on Astar zkEVM?
\ No newline at end of file
+# Build on Astar zkEVM, a Layer 2 scaling solution for Ethereum
+
+
+
+
+
+
+2. Use the network selector and switch to zKatana network, or allow MetaMask to switch to zKatana network for you.
+
+
+
+
+
+
+
+3. Click on the Bridge tab on the left-hand side. Ensure Sepolia is selected as Bridge source, and zKatana is selected as destination. After you have entered the amount of ETH to transfer, press the Confirm button.
+
+
+
+
+
+
+
+4. Sign the MetaMask transaction.
+
+
+
+
+
+
+:::note
+Once the transaction shows as confirmed on the MetaMask Activity tab, it will take approximately 5-10 minutes for the Astar Portal and MetaMask to update your balance on the zKatana network side.
+:::
+
+
+
+
+
+
+ You should now see the bridged ETH within MetaMask for use on Astar zkEVM. Visit the [smart contracts section](/docs/build/build-on-layer-2/smart-contracts/index.md) to start building!
+
+
+
diff --git a/docs/build/build-on-layer-2/integrations/bridges-relays/index.md b/docs/build/build-on-layer-2/integrations/bridges-relays/index.md
new file mode 100644
index 0000000..7d4e5da
--- /dev/null
+++ b/docs/build/build-on-layer-2/integrations/bridges-relays/index.md
@@ -0,0 +1,4 @@
+# Asset Bridges
+
+## Overview
+Here you will find all the information required to bridge assets to the Astar zkEVM, and set up simple cross-chain contracts using our supported partner solutions.
\ No newline at end of file
diff --git a/docs/build/build-on-layer-2/integrations/index.md b/docs/build/build-on-layer-2/integrations/index.md
new file mode 100644
index 0000000..4bd359a
--- /dev/null
+++ b/docs/build/build-on-layer-2/integrations/index.md
@@ -0,0 +1,10 @@
+# Integrations
+
+Here you will find common services and tools available to developers building dApps on the Astar zkEVM, including sample configurations, and guides for many important elements of our infrastructure, including:
+
+```mdx-code-block
+import DocCardList from '@theme/DocCardList';
+import {useCurrentSidebarCategory} from '@docusaurus/theme-common';
+
+
+
+Ethereum StackExchange
+ +1. Join the **Ethereum StackExchange** [here](https://ethereum.stackexchange.com/). + +2. Create a new issue. +3. Make a detailed explanation of your issue. +4. At the end add a tag `Astar` to trigger Astar team. + +
+
diff --git a/docs/build/build-on-layer-2/smart-contracts/_category_.json b/docs/build/build-on-layer-2/smart-contracts/_category_.json
new file mode 100644
index 0000000..9a362c6
--- /dev/null
+++ b/docs/build/build-on-layer-2/smart-contracts/_category_.json
@@ -0,0 +1,4 @@
+{
+ "label": "Smart Contracts",
+ "position": 5
+}
\ No newline at end of file
diff --git a/docs/build/build-on-layer-2/smart-contracts/figures/end-product-nft-code.png b/docs/build/build-on-layer-2/smart-contracts/figures/end-product-nft-code.png
new file mode 100644
index 0000000..0edd6b3
Binary files /dev/null and b/docs/build/build-on-layer-2/smart-contracts/figures/end-product-nft-code.png differ
diff --git a/docs/build/build-on-layer-2/smart-contracts/figures/flatten-code-remix.png b/docs/build/build-on-layer-2/smart-contracts/figures/flatten-code-remix.png
new file mode 100644
index 0000000..ffde411
Binary files /dev/null and b/docs/build/build-on-layer-2/smart-contracts/figures/flatten-code-remix.png differ
diff --git a/docs/build/build-on-layer-2/smart-contracts/figures/hardhat-init.png b/docs/build/build-on-layer-2/smart-contracts/figures/hardhat-init.png
new file mode 100644
index 0000000..3dfed44
Binary files /dev/null and b/docs/build/build-on-layer-2/smart-contracts/figures/hardhat-init.png differ
diff --git a/docs/build/build-on-layer-2/smart-contracts/figures/input-object.png b/docs/build/build-on-layer-2/smart-contracts/figures/input-object.png
new file mode 100644
index 0000000..93f9020
Binary files /dev/null and b/docs/build/build-on-layer-2/smart-contracts/figures/input-object.png differ
diff --git a/docs/build/build-on-layer-2/smart-contracts/figures/json.png b/docs/build/build-on-layer-2/smart-contracts/figures/json.png
new file mode 100644
index 0000000..f87f66d
Binary files /dev/null and b/docs/build/build-on-layer-2/smart-contracts/figures/json.png differ
diff --git a/docs/build/build-on-layer-2/smart-contracts/figures/proj-created-outcome.png b/docs/build/build-on-layer-2/smart-contracts/figures/proj-created-outcome.png
new file mode 100644
index 0000000..05e1fbb
Binary files /dev/null and b/docs/build/build-on-layer-2/smart-contracts/figures/proj-created-outcome.png differ
diff --git a/docs/build/build-on-layer-2/smart-contracts/index.md b/docs/build/build-on-layer-2/smart-contracts/index.md
new file mode 100644
index 0000000..c5fc811
--- /dev/null
+++ b/docs/build/build-on-layer-2/smart-contracts/index.md
@@ -0,0 +1,8 @@
+# Smart Contracts
+
+```mdx-code-block
+import DocCardList from '@theme/DocCardList';
+import {useCurrentSidebarCategory} from '@docusaurus/theme-common';
+
+