diff --git a/docs/04-resources/06-guides/eas-guide/_category_.yml b/docs/04-resources/06-guides/eas-guide/_category_.yml
new file mode 100644
index 00000000..8211f08d
--- /dev/null
+++ b/docs/04-resources/06-guides/eas-guide/_category_.yml
@@ -0,0 +1,6 @@
+label: Ethereum Attestation Service
+position: 2
+link:
+ type: generated-index
+ description: The PowPeg App fka 2 way peg app converts BTC to RBTC and vice versa. It is secured by the powpeg protocol, which is a unique PowPeg system that secures the locked bitcoins with the same Bitcoin hashrate that establishes consensus.
+ slug: /resources/guides/eas-guide/
\ No newline at end of file
diff --git a/docs/04-resources/06-guides/eas-guide/eas-userguide.md b/docs/04-resources/06-guides/eas-guide/eas-userguide.md
new file mode 100644
index 00000000..1f52898b
--- /dev/null
+++ b/docs/04-resources/06-guides/eas-guide/eas-userguide.md
@@ -0,0 +1,165 @@
+---
+sidebar_position: 2
+title: How to Navigate EAS Dashboard Guide
+sidebar_label: How to Navigate EAS Dashboard Guide
+tags: [rsk, rootstock, resources, mainnet, testnet, tutorials, Attestations, Indexing Service, EAS Devtool, Ethereum, dApps, smart contracts]
+description: "This guide explains how to navigate the provided interface, connect your wallet, create an EAS Schema, and explore attestations in detail."
+---
+
+
+
+ EAS Dashboard on DevTool (fig 1.)
+
+
+This guide explains how to navigate the provided interface, connect your wallet, create an EAS Schema, and explore attestations in detail.
+
+## Getting Started
+
+
+ 1. **Locate the "Connect Wallet" Button**:
+ * At the top-right corner of the page, you will see the **Connect Wallet** button.
+2. **Click the "Connect Wallet" Button**:
+ * A wallet connection modal will open, allowing you to choose your preferred cryptocurrency wallet (e.g., MetaMask, WalletConnect, etc.).
+3. **Authenticate**:
+ * Select your wallet and authorize the connection.
+ * Ensure your wallet is set to the correct blockchain network supported by the EAS platform.
+4. **Verify the Connection**:
+ * Once connected, your wallet address will replace the **Connect Wallet** button, confirming the link.
+
+
+
+ Connecting Your Wallet (fig 2.)
+
+
+> Adding your wallet only provides access to view your schema and attestations.
+
+
+
+ 1. **Click "Create EAS Schema"**:
+ * Located at the top-right corner of the interface.
+
+
+
+ Creating an EAS Schema (fig 3.)
+
+
+2. **Fill Out the Schema Details**:
+ * **Name**: Enter a descriptive name for the schema.
+ * **Type**: Select the type of data (e.g., `Address`, `string`, `bool`, `uint8`, etc.).
+ * If multiple fields are required, click **Add New Field** to define additional data points.
+ * **Resolver Address** (optional):
+ * Add a resolver smart contract address if you need custom verification or actions associated with this schema.
+ * **Is Revocable?**:
+ * Enable this option if attestations under this schema can be revoked later.
+3. **Submit the Schema**:
+ * Click the **Create Schema** button to deploy the schema on-chain.
+4. **Confirmation**:
+ * Upon successful submission, the schema appears in the list with a unique ID
+
+
+
+
+
+ Exploring the Schema List (fig 4.)
+
+
+1. **Schema Overview**
+ * **All Schemas**: Displays the total number of schemas created.
+ * **OnChain Attestation**: Number of attestations linked to schemas stored on-chain.
+ * **OffChain Attestation**: Number of attestations stored off-chain.
+2. **Schema Details**:
+ * Each row displays:
+ * **ID**: Unique identifier for the schema.
+ * **UID**: A unique on-chain reference for the schema.
+ * **Schema Fields**: Data structure of the schema (e.g., `bytes32 schemaId, string name`).
+ * **Attestations**: The number of attestations linked to this schema.
+3. **Clicking on a Schema**:
+ * Clicking on a schema opens detailed information about its attestations.
+
+
+
+
+
+ Viewing Attestation Details (fig 5.)
+
+
+:::info[When you select a schema:]
+
+1. **Header Details**:
+ * **Schema ID**: The unique identifier for the schema.
+ * **Total Attestations**: Total attestations associated with the schema (on-chain and off-chain).
+ * Includes growth percentage over the past week.
+ * **OnChain/OffChain Attestation Counts**: Breakdowns of attestations.
+2. **Schema Metadata**:
+ * **Created On**: The date the schema was created.
+ * **Creator**: Wallet address of the schema creator.
+ * **Transaction ID**: Blockchain transaction ID for the schema creation (clickable for blockchain explorer verification).
+ * **Resolver Contract**: Address of the custom resolver contract (if any).
+ * **Revocable Attestations**: Indicates whether attestations can be revoked.
+3. **Schema Structure**:
+ * Displays the fields defined in the schema (e.g., `bytes32 schemaId, string name`).
+4. **Attest Button**:
+ * **Attest this Schema**: Allows creating a new attestation under this schema.
+:::
+
+
+
+
+ Attesting to a schema allows you to associate specific data with an address based on the schema's structure.
+
+#### **Initiating the Attestation**
+
+1. **Click "Attest this Schema"**:
+ * Located at the bottom of the schema details page (visible in the first screenshot).
+2. **Modal Pop-Up**:
+ * A modal will appear with the following fields:
+ * **Recipient Address**:
+ * Enter the wallet address of the person or entity to whom the attestation is being made.
+ * **Schema Fields**:
+ * Each field defined in the schema is displayed with an appropriate input box.
+ * For example, if the schema has a `string` field labeled "Testu," you will see:
+ * `Testu (string):` followed by an input field to provide the corresponding value.
+
+
+
+ Attest To Schema (fig 6.)
+
+
+#### **Completing the Attestation**
+
+1. **Fill in the Details**:
+ * Enter the **Recipient Address** and all required values for the schema fields.
+ * Double-check that the data aligns with the schema's structure.
+2. **Submit or Close**:
+ * **Attest Button**:
+ * Click the **Attest** button to finalize and submit the attestation.
+ * **Close Button**:
+ * If you wish to cancel the process, click the **Close** button to exit the modal without submitting.
+
+#### **Processing the Attestation**
+
+1. **On Submission**:
+ * After clicking **Attest**, the attestation will be sent to the blockchain for processing.
+ * A transaction approval modal may appear via your connected wallet. Approve the transaction to proceed.
+2. **Confirmation**:
+ * After a few minutes, the attestation will be confirmed on the blockchain.
+
+#### **Viewing the Completed Attestation**
+
+
+
+ Viewing the Completed Attestation (fig 7.)
+
+
+ **Post-Attestation View**:
+ * Once confirmed, the attestation details will appear in the schema details page under its **Attestations** count.
+ * The attestation data can now be viewed as part of the schema's record.
+
+
+
+
+
+
+
+
+
diff --git a/docs/04-resources/06-guides/eas-guide/overview.md b/docs/04-resources/06-guides/eas-guide/overview.md
new file mode 100644
index 00000000..4842c763
--- /dev/null
+++ b/docs/04-resources/06-guides/eas-guide/overview.md
@@ -0,0 +1,321 @@
+---
+sidebar_position: 1
+title: How to Run EAS DevTool Locally
+sidebar_label: How to Run EAS DevTool Locally
+tags: [rsk, rootstock, resources, mainnet, testnet, tutorials, Attestations, Indexing Service, EAS Devtool, Ethereum, dApps, smart contracts]
+description: "Attestations are fundamental in blockchain technology, allowing entities to establish credibility and trust. However, traditional attestation methods face numerous challenges, including fragmentation, difficulty in managing schemas, and lack of intuitive tools for end-users. "
+---
+
+Attestations are fundamental in blockchain technology, allowing entities to establish credibility and trust. However, traditional attestation methods face numerous challenges, including fragmentation, difficulty in managing schemas, and lack of intuitive tools for end-users.
+
+The **Ethereum Attestation Service (EAS)** aims to solve these issues by providing a streamlined protocol for creating and managing attestations. On the Rootstock blockchain, the EAS Devtool enhances usability, making it easier for developers to interact with attestations.
+
+This guide explores the challenges of attestation, why EAS is a great choice for developers, and provides a step-by-step tutorial on using the EAS Devtool and Indexing Service.
+
+## What is EAS
+Ethereum Attestation Service (EAS) is a system that allows individuals and organizations to create verifiable claims or proofs about specific events, actions, or data, either on-chain (on the blockchain) or off-chain (outside the blockchain but linked to it).
+
+These claims can be about anything, like proving someone's identity, verifying ownership, or confirming that an agreement has been fulfilled.
+
+Making these claims or proofs publicly verifiable and tamper-proof helps build trust without relying on centralized entities. The attestations created through EAS can be used in decentralized applications (dApps), identity systems, or smart contracts to ensure certain facts are validated and transparent.
+
+:::info[Info]
+
+EAS is an open-source platform, meaning anyone can use it or contribute to its development. It operates as a public good for the Ethereum ecosystem.
+
+:::
+
+## Challenges in Attestation
+
+* **Trust and Credibility:**
+
+The fundamental challenge of attestation lies in establishing and maintaining trust. While blockchain technologies provide transparency, the credibility of an attestation depends on the reputation and reliability of the attestation source, the verification mechanism behind the attestation, and the potential for manipulation or false attestations.
+
+
+* **Privacy and Data Protection:**
+
+Attestations often involve sensitive personal or organizational information, creating critical privacy concerns such as balancing transparency with individual privacy rights, preventing unauthorized access to attestation data, implementing zero-knowledge proof technologies to validate information without exposing raw data, and ensuring compliance with evolving data protection regulations across different jurisdictions.
+
+
+* **Scalability and Performance:**
+
+As blockchain networks grow, attestation systems face significant technical challenges, including managing high volumes of attestations without compromising network performance, minimizing transaction costs and computational overhead, ensuring fast verification processes, and designing efficient storage and retrieval mechanisms for large-scale attestation networks.
+
+
+
+## Why Choose the EAS Tool on Rootstock?
+
+* **Centralized Management**
+
+EAS Devtool provides a unified platform to manage, view, and attest schemas, eliminating fragmentation. Developers can easily access all attestations for a project in one dashboard, reducing operational overhead.
+
+* **User-Friendly Interface**
+
+With tools like the EAS React SDK, developers and end-users can interact with attestations through an intuitive interface. A React-based dApp can integrate the EAS React SDK for seamless schema creation, allowing users to attest directly without technical knowledge.
+
+* **Enhanced Efficiency**
+
+The EAS Indexing Service enables fast and reliable data fetching using GraphQL, optimizing performance for high-volume use cases. An NFT marketplace can use the Indexing Service to verify authenticity attestations instantly.
+
+
+
+## Prerequisites
+
+Before you begin, ensure you have the following set up:
+
+1. **Docker**: Installed on your system with a basic understanding of how to use it. Docker is essential for running services like the EAS Indexing Service in a containerized environment.
+2. **Node.js**: Installed on your system. Ensure you have Node.js (version 14.x or later) to run the EAS React Tool and related scripts.
+3. **Rootstock RPC API Key**: Obtain a valid API key for Rootstock RPC to connect to the blockchain network. This is crucial for interacting with the EAS contracts deployed on Rootstock.
+
+## Setting Up the EAS Indexing Service
+
+The Indexing Service acts as the backbone of the EAS ecosystem, providing the data infrastructure required for the React Tool to function effectively. Without the Indexing Service, the React Tool cannot fetch, manage, or display attestation data.
+
+Let’s explore why this step is essential and understand what each component does.
+
+#### What is the EAS Indexing Service?
+
+The EAS Indexing Service is responsible for:
+
+1. **Indexing Blockchain Data**: It monitors the blockchain and indexes all the attestation-related events. This ensures that attestation data is organized and accessible in real time.
+2. **Providing a Queryable API**: The service exposes a GraphQL API that allows the EAS React Tool to fetch attestation data efficiently.
+3. **Handling Large Data Volumes**: It processes and stores data in a database (e.g., PostgreSQL), enabling rapid data retrieval even for applications with significant usage.
+
+
+:::warning[Warning]
+
+Before you start using the **EAS React Tool** (Devtool), it's crucial to set up and run the **EAS Indexing Service**.
+
+The EAS Indexing Service enables efficient data fetching for attestations. Here’s how to set it up:
+
+:::
+
+
+ ```
+git clone https://github.com/rsksmart/eas-indexing-service.git
+cd eas-indexing-service
+```
+
+
+
+Create a `.env` file in the root directory with the following content:
+
+```
+DATABASE_URL=postgresql://user:password@localhost:5432/eas-sepolia
+INFURA_API_KEY=
+INFURA_IPFS_USER=
+INFURA_IPFS_PASS=
+ALCHEMY_ARBITRUM_API_KEY=
+ALCHEMY_SEPOLIA_API_KEY=
+ALCHEMY_OPTIMISM_GOERLI_API_KEY=
+ROOTSTOCK_TESTNET_API_KEY=
+BATCH_SIZE= # How many blocks to fetch at once (some providers have limits)
+
+# Rootstock Tesnet
+CHAIN_ID=31
+
+```
+
+
+:::info[Explanation of Each Variable:]
+
+
+1. `DATABASE_URL`:
+ * Specifies the connection details for your PostgreSQL database.
+ * Example format: `postgresql://\:\@\:\/\`
+ * In this example:
+ * **Username**: user
+ * **Password**: password
+ * **Host**: localhost
+ * **Port**: 5432
+ * **Database Name**: eas-sepolia
+2. `INFURA_API_KEY`:
+ * API key for Infura, a blockchain infrastructure provider.
+ * Used for accessing Ethereum and IPFS (InterPlanetary File System) services.
+ * **Note:** Follow this guide to obtain your [API keys](https://docs.metamask.io/services/get-started/infura/#:~:text=View%20your%20API%20key%E2%80%8B&text=Infura%20automatically%20generates%20the%20My,can%20view%20your%20API%20key.).
+3. `INFURA_IPFS_USER and INFURA_IPFS_PASS`:
+ * Authentication credentials for accessing Infura’s IPFS gateway.
+ **Note**: Replace these values with your credentials to ensure secure access.
+4. `ALCHEMY_*_API_KEY`:
+ * API keys for Alchemy, another blockchain infrastructure provider.
+ * These keys allow you to interact with various Ethereum testnets (`Arbitrum, Sepolia, Optimism Goerli`).
+ * **Note:** Follow this guide to obtain your [API keys](https://www.alchemy.com/support/how-to-create-a-new-alchemy-api-key).
+5. `ROOTSTOCK_TESTNET_API_KEY`:
+ * API key for connecting to the Rootstock Testnet.
+ * This enables interactions with the Rootstock blockchain for testing and indexing.
+ * **Note:** Follow this guide to obtain your [API keys](https://dev.rootstock.io/developers/rpc-api/rootstock/setup/).
+6. `BATCH_SIZE`:
+ * Defines the number of blocks fetched in a single request when syncing data from the blockchain.
+ * Adjust this value based on your service provider's rate limits or API constraints.
+7. `CHAIN\_ID`:
+ * Identifies the blockchain network.
+ * In this case:
+ * `31` corresponds to the Rootstock Testnet.
+
+:::
+
+
+ The `yarn install` command is used to download and set up all the necessary packages and dependencies required for the EAS Indexing Service to function properly.
+
+These dependencies are listed in the project's package.json file and are essential for the service's operation.
+
+```
+yarn install
+```
+
+
+
+Prisma is used to define the database schema and generate client-side code that interacts with the database.
+
+The generated Prisma client is essential for the Indexing Service to communicate with the database. Without it:
+
+* The Indexing Service won't be able to store or retrieve indexed attestation data.
+* You may encounter runtime errors when the service tries to perform database operations.
+
+```
+SKIP_PRISMA_VERSION_CHECK=true npx prisma generate
+```
+
+:::info[Breakdown of the Command]
+
+1. `SKIP_PRISMA_VERSION_CHECK=true`:
+ * This environment variable is set to bypass Prisma's version compatibility check.
+ * **Why?**: The project uses the `typegraphql-prisma package`, which sometimes lags in supporting the latest Prisma versions. Without skipping the version check, you might encounter warnings or errors if there is a version mismatch between Prisma and its dependencies.
+2. `npx prisma generate`:
+ * This command generates the Prisma client based on the schema defined in the `prisma/schema.prisma` file.
+ * **What does it do?**
+ * Parses the database schema described in the `schema.prisma` file.
+ * Generates the client code for database interactions.
+ * The generated client provides methods for querying and modifying the database, enabling seamless integration with the EAS Indexing Service.
+
+:::
+
+:::warning[Warning]
+
+Start Docker Before Running `docker-compose`
+
+Before executing the `docker-compose up -d` command, make sure Docker is running on your system. You can do this by:
+
+1. **Using the Command Line**:
+ * Start Docker manually by running the appropriate command for your operating system:
+ * **Windows/Linux/macOS**:
+
+If Docker is installed as a service, you may need to start it using:
+
+```
+sudo systemctl start docker
+```
+
+Or simply run Docker Desktop.
+
+2. **Using Docker Desktop**:
+ * Open the Docker Desktop application if installed.
+ * Ensure that it is running and ready. The status should show that Docker is operational, and the engine is active.
+
+
+
+ Docker Engine Running" (fig 1.)
+
+
+You can find this at the bottom left of your screen
+:::
+
+
+ The `docker-compose up -d` command is used to start the Docker services required by the EAS Indexing Service. This step launches and runs all the containerized components defined in the `docker-compose.yml` file, setting up the necessary environment for the indexing service to function.
+
+```
+docker-compose up -d
+```
+:::info[Breakdown of the Command]
+
+1. `docker-compose`:
+ * This is a command-line tool for managing multi-container Docker applications.
+ * It uses the `docker-compose.yml` file to define and manage the services, networks, and volumes required by your application.
+2. `up`:
+ * This subcommand builds (if necessary) and starts all the containers specified in the `docker-compose.yml` file.
+ * It ensures all services, such as the database (`PostgreSQL`) and any related dependencies, are running.
+3. `-d`:
+ * This flag runs the services in detached mode, meaning they will continue running in the background.
+ * This allows you to close the terminal session or continue working on other tasks without stopping the containers.
+:::
+
+Expected output:
+
+```
+ ✔ Network eas-indexing-service_default Created 0.0s
+ ✔ Container eas-postgres Started 0.5s
+ ✔ Container eas_indexer_container Started
+```
+
+If you modify project files, rebuild Docker containers:
+
+```
+docker-compose build
+docker-compose up -d
+```
+
+Expected output:
+
+If everything is set up correctly, you should see a similar output when you check the logs of your `eas_indexer_container`
+
+
+
+ EAS Indexer Container Running Successfully (fig 2.)
+
+
+
+
+
+
+
+# Setting Up the EAS Devtool
+
+The EAS React Tool is a user-facing platform that leverages the data provided by the Indexing Service to:
+
+1. **Display Attestations**: It visualizes schemas and attestation data in an intuitive interface.
+2. **Allow User Interaction**: Users can create schemas and make attestations through this tool.
+3. **Streamline Workflow**: Developers can interact with attestation data without manually querying the blockchain or API.
+
+
+
+ ```
+git clone https://github.com/rsksmart/EAS-devtool.git
+cd EAS-devtool
+```
+
+
+ The `yarn install/npm install` command is used to download and set up all the necessary packages and dependencies required for the EAS Devtool to function properly.
+
+These dependencies are listed in the project's `package.json` file and are essential for the service's operation.
+
+```
+npm install
+# or
+yarn install
+```
+
+
+ ```
+npm run dev
+# or
+yarn dev
+```
+
+This launches the EAS Devtool, allowing you to manage and view attestations in a centralized platform.
+
+Expected output:
+
+
+
+ EAS Dashboard on DevTool (fig 3.)
+
+
+
+
+
+
+:::info[Info]
+
+Once you've set up and run the `EAS DevTool` locally, you can proceed to explore its **[dashboard](/resources/guides/eas-guide/eas-userguide/)** and functionality in detail. The following guide will walk you through navigating the `EAS Dashboard`, connecting your `wallet`, and managing `schemas` and `attestations`.
+
+:::
\ No newline at end of file
diff --git a/static/img/guides/EAS/EAS-devtool-dash.png b/static/img/guides/EAS/EAS-devtool-dash.png
new file mode 100644
index 00000000..10923cfa
Binary files /dev/null and b/static/img/guides/EAS/EAS-devtool-dash.png differ
diff --git a/static/img/guides/EAS/eas-indexer-contianer.png b/static/img/guides/EAS/eas-indexer-contianer.png
new file mode 100644
index 00000000..87c5f37e
Binary files /dev/null and b/static/img/guides/EAS/eas-indexer-contianer.png differ
diff --git a/static/img/guides/EAS/engine-running.png b/static/img/guides/EAS/engine-running.png
new file mode 100644
index 00000000..0c3f94c9
Binary files /dev/null and b/static/img/guides/EAS/engine-running.png differ
diff --git a/static/img/guides/EAS/frontend-guide/adding-wallet.png b/static/img/guides/EAS/frontend-guide/adding-wallet.png
new file mode 100644
index 00000000..d6737130
Binary files /dev/null and b/static/img/guides/EAS/frontend-guide/adding-wallet.png differ
diff --git a/static/img/guides/EAS/frontend-guide/attest-to-schema.png b/static/img/guides/EAS/frontend-guide/attest-to-schema.png
new file mode 100644
index 00000000..0f0713f5
Binary files /dev/null and b/static/img/guides/EAS/frontend-guide/attest-to-schema.png differ
diff --git a/static/img/guides/EAS/frontend-guide/completed-attestation.png b/static/img/guides/EAS/frontend-guide/completed-attestation.png
new file mode 100644
index 00000000..f55ba9b1
Binary files /dev/null and b/static/img/guides/EAS/frontend-guide/completed-attestation.png differ
diff --git a/static/img/guides/EAS/frontend-guide/eas-schema.png b/static/img/guides/EAS/frontend-guide/eas-schema.png
new file mode 100644
index 00000000..fd9b3183
Binary files /dev/null and b/static/img/guides/EAS/frontend-guide/eas-schema.png differ
diff --git a/static/img/guides/EAS/frontend-guide/shcema-list.png b/static/img/guides/EAS/frontend-guide/shcema-list.png
new file mode 100644
index 00000000..10923cfa
Binary files /dev/null and b/static/img/guides/EAS/frontend-guide/shcema-list.png differ
diff --git a/static/img/guides/EAS/frontend-guide/view-attestation.png b/static/img/guides/EAS/frontend-guide/view-attestation.png
new file mode 100644
index 00000000..c2dfdac0
Binary files /dev/null and b/static/img/guides/EAS/frontend-guide/view-attestation.png differ
+ 
+ 
+ 
+ 
+ 
+ 
+ 
+