From 24ce91d2cc679a9b950057333f25e8b6020a46f7 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Mona=20B=C3=A4renf=C3=A4nger?= <tschakki@posteo.de>
Date: Mon, 25 Nov 2024 09:59:11 +0100
Subject: [PATCH 1/3] [LISKDOCS-30] Add Velodrome (#253)

Add Velodrome
---
 docs/docs-user/exchanges.md | 24 +++++++++---------------
 1 file changed, 9 insertions(+), 15 deletions(-)

diff --git a/docs/docs-user/exchanges.md b/docs/docs-user/exchanges.md
index b35a514db..0184b384b 100644
--- a/docs/docs-user/exchanges.md
+++ b/docs/docs-user/exchanges.md
@@ -53,11 +53,19 @@ Lisk (LSK) is available for trading on various <!-- decentralized and centralize
 | **Zonda**                | 🟡 Ethereum        | [LSK/USDT](https://zondacrypto.com/en/exchange-rate/lisk-price-usdt)<br />[LSK/EUR](https://zondacrypto.com/en/exchange-rate/lisk-price-eur)<br />[LSK/BTC](https://zondacrypto.com/en/exchange-rate/lisk-price-btc)<br />[LSK/PLN](https://zondacrypto.com/en/exchange-rate/lisk-price-pln) |
 
 
+## Decentralized Exchanges (DEX)
+
+| Name                          | Supported network[^1]                       |
+| :---------------------------- | :------------------------------------------ |
+| [Oku.Trade](https://oku.trade/app/lisk/trade/0xac485391eb2d7d88253a7f1ef18c37f4242d1a24) | 🟢 Lisk |
+| [Velodrome](https://velodrome.finance/swap?from=0xac485391eb2d7d88253a7f1ef18c37f4242d1a24&to=0x05d032ac25d322df992303dca074ee7392c117b9&chain0=1135&chain1=1135) | 🟢 Lisk |
+| [Uniswap](https://app.uniswap.org/explore/tokens/ethereum/0x6033f7f88332b8db6ad452b7c6d5bb643990ae3f) | 🟡 Ethereum |
+
 [^1]: The LSK token is supported on both the Ethereum L1 and the Lisk L2 blockchains.
 The "supported network" field indicates the blockchain being used by the exchange for deposits & withdrawals of LSK. 
 Please note that using the wrong network/blockchain when depositing funds to an exchange could result in lost funds.
 
-### Coming soon
+## Coming soon
 
 | Name                     | Supported network |
 | :----------------------- |:----------------- |
@@ -67,17 +75,3 @@ Please note that using the wrong network/blockchain when depositing funds to an
 | **OkCoin** (OKX Japan)   | Lisk              |
 | **YellowCard** (Africa)  | Lisk              |
 
-## Decentralized Exchanges (DEX)
-
-| Name                          | Supported network[^1]                       |
-| :---------------------------- | :------------------------------------------ |
-| [Oku.Trade](https://oku.trade/app/lisk/trade/0xac485391eb2d7d88253a7f1ef18c37f4242d1a24) | 🟢 Lisk |
-| [Uniswap](https://app.uniswap.org/explore/tokens/ethereum/0x6033f7f88332b8db6ad452b7c6d5bb643990ae3f) | 🟡 Ethereum |
-
-### Coming soon
-
-| Name                          | 
-| :---------------------------- |
-| **Velodrome**                 | 
-
-

From 6999052a7ddc50a1c0491f0feb7618f1a352e17f Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Mona=20B=C3=A4renf=C3=A4nger?= <tschakki@posteo.de>
Date: Mon, 25 Nov 2024 09:59:33 +0100
Subject: [PATCH 2/3] [LISKDOCS-21] Fix not found bug (#254)

Fix not found bug
---
 plugins/generated-bridged-token-adresses-docs.js | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/plugins/generated-bridged-token-adresses-docs.js b/plugins/generated-bridged-token-adresses-docs.js
index 78839aeaf..5c2cae4e6 100644
--- a/plugins/generated-bridged-token-adresses-docs.js
+++ b/plugins/generated-bridged-token-adresses-docs.js
@@ -27,13 +27,13 @@ LiskAdresses.forEach(token => {
   // For Lisk Mainnet, add Ethereum Mainnet address
   if (token.chainId === chainIds[0]) {
     result = tokens.find(function(tkn) {
-        return tkn.symbol === token.symbol && tkn.chainId === 1;
+        return ((tkn.symbol === token.symbol) || (tkn.symbol + ".e" === token.symbol)) && tkn.chainId === 1;
     });
     ethAddress = result? result : {address: "Not Found"};
   // For Lisk Sepolia, add Ethereum Sepolia address
   } else if (token.chainId === chainIds[1]) {
     result = tokens.find(function(tkn) {
-      return tkn.symbol === token.symbol && tkn.chainId === 11155111;
+      return ((tkn.symbol === token.symbol) || (tkn.symbol + ".e" === token.symbol)) && tkn.chainId === 11155111;
     });
     ethAddress = result? result : {address: "Not Found"};
   } else {

From 359757dd3d4954afec5e8f08942be8f655b388c6 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Mona=20B=C3=A4renf=C3=A4nger?= <tschakki@posteo.de>
Date: Mon, 25 Nov 2024 14:33:35 +0100
Subject: [PATCH 3/3] [LISKDOCS-12] Add guide for redstone push (#252)

* Add new page

* Remove old page

* Add code example

* Update pages

* Add intro

* Add note about supported network

* Update note

* Remove duplicate title

* Update ind docs

* Apply suggestions from code review

Co-authored-by: Matjaz Verbole <verbole@gmail.com>

* Apply feedback

* Add link to new guide

* Apply suggestions from code review

Co-authored-by: Muhammad Talha <13951043+TalhaMaliktz@users.noreply.github.com>

* Apply feedback

* Caution to lower case

---------

Co-authored-by: Matjaz Verbole <verbole@gmail.com>
Co-authored-by: Muhammad Talha <13951043+TalhaMaliktz@users.noreply.github.com>
---
 .../using-oracle-data/redstone-pull.md        |  23 +-
 .../using-oracle-data/redstone-push.md        | 216 +++++++++++++++++
 .../using-oracle-data/tellor.md               |   4 +-
 docs/lisk-tools/oracles.md                    |   2 +-
 .../redstone-pull.md}                         |  29 +--
 .../using-oracle-data/redstone-push.md        | 218 ++++++++++++++++++
 .../using-oracle-data/tellor.md               | 207 +++++++++++++++++
 sidebars.js                                   |   1 +
 8 files changed, 673 insertions(+), 27 deletions(-)
 create mode 100644 docs/building-on-lisk/using-oracle-data/redstone-push.md
 rename i18n/ind/docusaurus-plugin-content-docs/current/building-on-lisk/{use-oracle-data.md => using-oracle-data/redstone-pull.md} (78%)
 create mode 100644 i18n/ind/docusaurus-plugin-content-docs/current/building-on-lisk/using-oracle-data/redstone-push.md
 create mode 100644 i18n/ind/docusaurus-plugin-content-docs/current/building-on-lisk/using-oracle-data/tellor.md

diff --git a/docs/building-on-lisk/using-oracle-data/redstone-pull.md b/docs/building-on-lisk/using-oracle-data/redstone-pull.md
index 2c24b7b9c..e1aba23ae 100644
--- a/docs/building-on-lisk/using-oracle-data/redstone-pull.md
+++ b/docs/building-on-lisk/using-oracle-data/redstone-pull.md
@@ -1,11 +1,11 @@
 ---
-title: ...with Redstone (Pull)
+title: ...with RedStone (Pull)
 slug: /building-on-lisk/using-oracle-data/redstone-pull
-description: A guide on using Redstone Data Feeds to access real-world data such as asset prices, directly from your smart contracts on the Lisk testnet.
+description: A guide on using RedStone Pull to access real-world data such as asset prices, directly from your smart contracts on the Lisk blockchain.
 keywords: [
     Oracle
     Oracles,
-    Redstone,
+    RedStone,
     price feeds,
     data feeds,
     smart contract,
@@ -17,25 +17,26 @@ keywords: [
     dapp development,
     build a dapp on Lisk,
     build on Lisk,
+    RedStone Pull,
   ]
 ---
 
-# Accessing real-world data using the Redstone Oracle
+# Accessing real-world data using the RedStone Oracle (Pull)
 
-This page will explain how you can access oracle data using Redstone.
+This page will explain how you can access oracle data using [RedStone Pull](https://docs.redstone.finance/docs/get-started/models/redstone-pull/).
 
 RedStone is a data ecosystem that delivers frequently updated, reliable, and diverse data for your dApp and smart contracts deployed on Lisk.
 
-## How to pull oracle data from Redstone
+## How to pull oracle data from RedStone
 
-To create a smart contract that directly fetches the latest data from the Redstone oracle, follow this guide.
+To create a smart contract that directly fetches the latest data from the RedStone oracle, follow this guide.
 
-This guide uses the [Redstone Pull model](https://docs.redstone.finance/docs/get-started/models/redstone-pull) to fetch the data.
+This guide uses the [RedStone Pull model](https://docs.redstone.finance/docs/get-started/models/redstone-pull) to fetch the data.
 
-For an overview of the different modules that Redstone offers to receive oracle data, go to [Oracles > Redstone](../../lisk-tools/oracles#redstone).
+For an overview of the different modules that RedStone offers to receive oracle data, go to [Oracles > RedStone](../../lisk-tools/oracles#redstone).
 
 [Hardhat](https://hardhat.org/) is used in this guide to create the smart contract.
-In case you want to use Foundry, check out the [Redstone docs](https://docs.redstone.finance/docs/get-started/models/redstone-pull#foundry) for instructions.
+In case you want to use Foundry, check out the [RedStone docs](https://docs.redstone.finance/docs/get-started/models/redstone-pull#foundry) for instructions.
 
 ### Dependencies
 
@@ -124,7 +125,7 @@ import { ethers } from "hardhat";
 import { WrapperBuilder } from "@redstone-finance/evm-connector";
 
 describe("YourContract", function () {
-    describe("Redstone", function () {
+    describe("RedStone", function () {
         it("Get ETH price securely", async function () {
         const YourContract = await ethers.getContractFactory("YourContract");
         const contract = await YourContract.deploy();
diff --git a/docs/building-on-lisk/using-oracle-data/redstone-push.md b/docs/building-on-lisk/using-oracle-data/redstone-push.md
new file mode 100644
index 000000000..c81374335
--- /dev/null
+++ b/docs/building-on-lisk/using-oracle-data/redstone-push.md
@@ -0,0 +1,216 @@
+---
+title: ...with RedStone (Push)
+slug: /building-on-lisk/using-oracle-data/redstone-push
+description: A guide on using RedStone Push to access real-world data such as asset prices, directly from your smart contracts on the Lisk blockchain.
+keywords: [
+    Oracle
+    Oracles,
+    RedStone,
+    price feeds,
+    data feeds,
+    smart contract,
+    Lisk blockchain,
+    Lisk network,
+    Lisk testnet,
+    Lisk test network,
+    app development,
+    dapp development,
+    build a dapp on Lisk,
+    build on Lisk,
+    RedStone Push,
+  ]
+---
+
+# Accessing real-world data using the RedStone Oracle (Push)
+
+This page will explain how you can access oracle data using [RedStone Push](https://docs.redstone.finance/docs/get-started/models/redstone-push).
+
+RedStone is a data ecosystem that delivers frequently updated, reliable, and diverse data for your dApp and smart contracts deployed on Lisk.
+
+RedStone data feeds are compatible with Chainlink's [AggregatorV3Interface](https://docs.chain.link/data-feeds/using-data-feeds#solidity) and include the following components:
+
+- **Aggregator contract**: An aggregator is a contract that receives periodic data updates from the oracle network.
+Aggregators store aggregated data onchain so that consumers can retrieve it and act upon it within the same transaction.
+These contracts have already been deployed on the Lisk network and can be directly used by consumers.
+- **Consumer**: A consumer is an onchain or offchain application that uses Data Feeds.
+Consumer contracts use the `AggregatorV3Interface` to call functions on the proxy contract[^1] of the Aggregator to retrieve oracle data.
+
+[^1]: Proxy contracts are onchain proxies that point to the aggregator for a particular data feed.
+Using proxies enables the underlying aggregator to be upgraded without any service interruption to consuming contracts.
+
+## Data feeds on Lisk
+The following Aggregators are available on Lisk Mainnet for RedStone Push:
+
+- [ETH/USD L2PriceFeedWithoutRounds](https://blockscout.lisk.com/address/0x6b7AB4213c77A671Fc7AEe8eB23C9961fDdaB3b2)
+  - address: `0x6b7AB4213c77A671Fc7AEe8eB23C9961fDdaB3b2`
+- [LSK/USD L2PriceFeedWithoutRounds](https://blockscout.lisk.com/address/0xa1EbA9E63ed7BA328fE0778cFD67699F05378a96)
+  - address: `0xa1EbA9E63ed7BA328fE0778cFD67699F05378a96`
+- [USDT/USD L2PriceFeedWithoutRounds](https://blockscout.lisk.com/address/0xd2176Dd57D1e200c0A8ec9e575A129b511DBD3AD)
+  - address: `0xd2176Dd57D1e200c0A8ec9e575A129b511DBD3AD`
+- [USDC/USD L2PriceFeedWithoutRounds](https://blockscout.lisk.com/address/0xb4e6A7861067674AC398a26DD73A3c524C602184)
+  - address: `0xb4e6A7861067674AC398a26DD73A3c524C602184`
+- [WBTC/USD L2PriceFeedWithoutRounds](https://blockscout.lisk.com/address/0x13da43eA89fB692bdB6666F053FeE70aC61A53cd)
+  - address: `0x13da43eA89fB692bdB6666F053FeE70aC61A53cd`
+
+In this guide, we will develop a Consumer contract that requests the latest spot prices from the ETH, LSK, and USDT data feeds.
+
+:::note
+RedStone Push is only fully available on Lisk Mainnet, so please make sure to deploy your Consumer contract on Lisk Mainnet as well.
+
+In case you wish to deploy on Lisk Sepolia Testnet, check the [Tellor](./tellor.md) guide, which is available for both networks.
+:::
+
+## Import
+
+To use the RedStone data inside your contract, import the [AggregatorV3Interface](https://docs.chain.link/data-feeds/using-data-feeds#solidity) from Chainlink, as shown in the example contract below.
+
+Create a new constant with the type `AggregatorV3Interface` for every data feed you want to store.
+
+In the constructor, set the above-defined constants to point to the respective data feeds.
+Use the `AggregatorV3Interface()` function and pass the address of the respective data feed contract as a parameter.
+
+```solidity title="Importing the AggregatorV3Interface"
+// SPDX-License-Identifier: MIT
+pragma solidity ^0.8.28;
+
+import {AggregatorV3Interface} from "@chainlink/contracts/src/v0.8/shared/interfaces/AggregatorV3Interface.sol";
+
+contract RedStoneDataConsumer {
+    AggregatorV3Interface internal dataFeedETH;
+    AggregatorV3Interface internal dataFeedLSK;
+    AggregatorV3Interface internal dataFeedUSDT;
+
+    /**
+     * Network: Lisk
+     * Aggregator: ETH/USD
+     * Address: 0x6b7AB4213c77A671Fc7AEe8eB23C9961fDdaB3b2
+     */
+     /**
+     * Network: Lisk
+     * Aggregator: LSK/USD
+     * Address: 0xa1EbA9E63ed7BA328fE0778cFD67699F05378a96
+     */
+      /**
+     * Network: Lisk
+     * Aggregator: USDT/USD
+     * Address: 0xd2176Dd57D1e200c0A8ec9e575A129b511DBD3AD
+     */
+    constructor() {
+        dataFeedETH = AggregatorV3Interface(
+            0x6b7AB4213c77A671Fc7AEe8eB23C9961fDdaB3b2
+        );
+        dataFeedLSK = AggregatorV3Interface(
+            0xa1EbA9E63ed7BA328fE0778cFD67699F05378a96
+        );
+        dataFeedUSDT = AggregatorV3Interface(
+            0xd2176Dd57D1e200c0A8ec9e575A129b511DBD3AD
+        );
+    }
+}
+```
+
+## Reading data
+To read the data of the price feeds, we define the following functions in the contract:
+
+- `getRedStoneETHDataFeedLatestAnswer()`
+- `getRedStoneLSKDataFeedLatestAnswer()`
+- `getRedStoneUSDTDataFeedLatestAnswer()`
+
+Inside the functions, call the [latestRoundData](https://docs.chain.link/data-feeds/api-reference#latestrounddata) on the respective data feeds to receive the latest spot prices for the respective token.
+
+The `latestRoundData()` function returns the following values:
+
+- `roundId`(uint80): The round ID.
+For all [data feeds](#data-feeds-on-lisk), the round is always `1`, because the contracts are without rounds, as the name suggests.
+- `answer`(int256): The data that this specific feed provides.
+Depending on the feed you selected, this answer provides asset prices, reserves, and other types of data.
+- `startedAt`(uint256): Timestamp of when the round started.
+- `updatedAt`(uint256): Timestamp of when the round was updated.
+- `answeredInRound`(uint80):  Deprecated - Previously used when answers could take multiple rounds to be computed.
+
+In this example, we will only use `answer` and `updatedAt`.
+The `updatedAt` value should be used to make sure that the `answer` is recent enough for your application to use it.
+You can compare `updatedAt` to the latest block time (`uint256 currentTime = block.timestamp;`) to ensure you are only using the latest oracle data in your application.
+
+:::caution
+This is an example contract that uses un-audited code.
+Do not use this code in production.
+:::
+
+```solidity title="Reading data feeds"
+// SPDX-License-Identifier: MIT
+pragma solidity ^0.8.28;
+
+import {AggregatorV3Interface} from "@chainlink/contracts/src/v0.8/shared/interfaces/AggregatorV3Interface.sol";
+
+contract RedStoneDataConsumer {
+  AggregatorV3Interface internal priceFeedETH;
+  AggregatorV3Interface internal priceFeedLSK;
+  AggregatorV3Interface internal priceFeedUSDT;
+
+  constructor() {
+      priceFeedETH = AggregatorV3Interface(
+          0x6b7AB4213c77A671Fc7AEe8eB23C9961fDdaB3b2
+      );
+      priceFeedLSK = AggregatorV3Interface(
+          0xa1EbA9E63ed7BA328fE0778cFD67699F05378a96
+      );
+      priceFeedUSDT = AggregatorV3Interface(
+          0xd2176Dd57D1e200c0A8ec9e575A129b511DBD3AD
+      );
+  }
+
+  /**
+    * Returns the latest ETH price, and when it was updated.
+    */
+  function getRedStoneETHDataFeedLatestAnswer() public view returns (int, uint) {
+      (
+        /* uint80 roundID */,
+        int answer,
+        uint updatedAt,
+        /*uint startedAt*/,
+        /*uint80 answeredInRound*/
+      ) = priceFeedETH.latestRoundData();
+      return (answer, updatedAt);
+  }
+  /**
+    * Returns the latest LSK price, and when it was updated.
+    */
+  function getRedStoneLSKDataFeedLatestAnswer() public view returns (int, uint) {
+      (
+        /* uint80 roundID */,
+        int answer,
+        uint updatedAt,
+        /*uint startedAt*/,
+        /*uint80 answeredInRound*/
+      ) = priceFeedLSK.latestRoundData();
+      return (answer, updatedAt);
+  }
+  /**
+    * Returns the latest USDT price, and when it was updated.
+    */
+  function getRedStoneUSDTDataFeedLatestAnswer() public view returns (int, uint) {
+      (
+        /* uint80 roundID */,
+        int answer,
+        uint updatedAt,
+        /*uint startedAt*/,
+        /*uint80 answeredInRound*/
+      ) = priceFeedUSDT.latestRoundData();
+      return (answer, updatedAt);
+  }
+}
+```
+
+## Deploying on Lisk
+
+To deploy the smart contract on Lisk, follow the guides 
+
+- [Deploying a smart contract with Hardhat](../deploying-smart-contract/with-Hardhat), or
+- [Deploying a smart contract with Foundry](../deploying-smart-contract/with-Foundry)
+
+:::note
+RedStone Push is only available on Lisk Mainnet, so please make sure to deploy your Consumer contract on Lisk Mainnet as well.
+
+In case you wish to deploy on Lisk Sepolia Testnet, check the [Tellor](./tellor.md) guide, which is available for both networks.
+:::
\ No newline at end of file
diff --git a/docs/building-on-lisk/using-oracle-data/tellor.md b/docs/building-on-lisk/using-oracle-data/tellor.md
index 99b7f1dbb..1fb3e8d2d 100644
--- a/docs/building-on-lisk/using-oracle-data/tellor.md
+++ b/docs/building-on-lisk/using-oracle-data/tellor.md
@@ -1,7 +1,7 @@
 ---
 title: ...with Tellor
 slug: /building-on-lisk/using-oracle-data/tellor
-description: A guide on using Redstone Data Feeds to access real-world data such as asset prices, directly from your smart contracts on the Lisk testnet.
+description: A guide on using Tellor Data Feeds to access real-world data such as asset prices, directly from your smart contracts on the Lisk blockchain.
 keywords: [
     Oracle
     Oracles,
@@ -21,6 +21,8 @@ keywords: [
 ---
 
 # Using oracle data with Tellor
+This page will explain how your application can access oracle data using Tellor.
+
 [Tellor](https://tellor.io/) is an immutable decentralized oracle protocol where parties can request the value of an offchain data point (e.g. ETH/USD, LSK/USD) and reporters compete to add this value to an onchain databank.
 The inputs to this databank are secured by a network of staked reporters.
 
diff --git a/docs/lisk-tools/oracles.md b/docs/lisk-tools/oracles.md
index 769e36dfd..7ddf9ab60 100644
--- a/docs/lisk-tools/oracles.md
+++ b/docs/lisk-tools/oracles.md
@@ -40,11 +40,11 @@ Interested in integration? [Get in contact](https://discord.com/invite/PVxBZKFr4
 #### Supported Networks
 
 - Lisk
-- Lisk Sepolia
 
 ### Guides
 
 - [Accessing oracle data with Redstone (Pull)](../building-on-lisk/using-oracle-data/redstone-pull.md)
+- [Accessing oracle data with Redstone (Push)](../building-on-lisk/using-oracle-data/redstone-push.md)
 
 ## Tellor
 
diff --git a/i18n/ind/docusaurus-plugin-content-docs/current/building-on-lisk/use-oracle-data.md b/i18n/ind/docusaurus-plugin-content-docs/current/building-on-lisk/using-oracle-data/redstone-pull.md
similarity index 78%
rename from i18n/ind/docusaurus-plugin-content-docs/current/building-on-lisk/use-oracle-data.md
rename to i18n/ind/docusaurus-plugin-content-docs/current/building-on-lisk/using-oracle-data/redstone-pull.md
index f682e1e88..e1aba23ae 100644
--- a/i18n/ind/docusaurus-plugin-content-docs/current/building-on-lisk/use-oracle-data.md
+++ b/i18n/ind/docusaurus-plugin-content-docs/current/building-on-lisk/using-oracle-data/redstone-pull.md
@@ -1,11 +1,11 @@
 ---
-title: Accessing real-world data with Oracles
-slug: /building-on-lisk/use-oracle-data
-description: A guide on using Redstone Data Feeds to access real-world data such as asset prices, directly from your smart contracts on the Lisk testnet.
+title: ...with RedStone (Pull)
+slug: /building-on-lisk/using-oracle-data/redstone-pull
+description: A guide on using RedStone Pull to access real-world data such as asset prices, directly from your smart contracts on the Lisk blockchain.
 keywords: [
     Oracle
     Oracles,
-    Redstone,
+    RedStone,
     price feeds,
     data feeds,
     smart contract,
@@ -17,25 +17,26 @@ keywords: [
     dapp development,
     build a dapp on Lisk,
     build on Lisk,
+    RedStone Pull,
   ]
 ---
 
-# Accessing real-world data using the Redstone Oracle
+# Accessing real-world data using the RedStone Oracle (Pull)
 
-This page will explain how you can access real world / off-chain data using Oracles such as Redstone.
+This page will explain how you can access oracle data using [RedStone Pull](https://docs.redstone.finance/docs/get-started/models/redstone-pull/).
 
 RedStone is a data ecosystem that delivers frequently updated, reliable, and diverse data for your dApp and smart contracts deployed on Lisk.
 
-## How to pull oracle data from Redstone
+## How to pull oracle data from RedStone
 
-To create a smart contract that directly fetches the latest data from the Redstone oracle, follow this guide.
+To create a smart contract that directly fetches the latest data from the RedStone oracle, follow this guide.
 
-This guide uses the [Redstone Pull model](https://docs.redstone.finance/docs/get-started/models/redstone-pull) to fetch the data.
+This guide uses the [RedStone Pull model](https://docs.redstone.finance/docs/get-started/models/redstone-pull) to fetch the data.
 
-For an overview of the different modules that Redstone offers to receive oracle data, go to [Oracles > Redstone](../lisk-tools/oracles#redstone).
+For an overview of the different modules that RedStone offers to receive oracle data, go to [Oracles > RedStone](../../lisk-tools/oracles#redstone).
 
 [Hardhat](https://hardhat.org/) is used in this guide to create the smart contract.
-In case you want to use Foundry, check out the [Redstone docs](https://docs.redstone.finance/docs/get-started/models/redstone-pull#foundry) for instructions.
+In case you want to use Foundry, check out the [RedStone docs](https://docs.redstone.finance/docs/get-started/models/redstone-pull#foundry) for instructions.
 
 ### Dependencies
 
@@ -124,7 +125,7 @@ import { ethers } from "hardhat";
 import { WrapperBuilder } from "@redstone-finance/evm-connector";
 
 describe("YourContract", function () {
-    describe("Redstone", function () {
+    describe("RedStone", function () {
         it("Get ETH price securely", async function () {
         const YourContract = await ethers.getContractFactory("YourContract");
         const contract = await YourContract.deploy();
@@ -158,5 +159,5 @@ Latest ETH price:
 
 To deploy the smart contract on Lisk Sepolia or Lisk Mainnet, follow the guides 
 
-- [Deploying a smart contract with Hardhat](deploying-smart-contract/with-Hardhat.md), or
-- [Deploying a smart contract with Foundry](deploying-smart-contract/with-Foundry.md)
\ No newline at end of file
+- [Deploying a smart contract with Hardhat](../deploying-smart-contract/with-Hardhat), or
+- [Deploying a smart contract with Foundry](../deploying-smart-contract/with-Foundry)
\ No newline at end of file
diff --git a/i18n/ind/docusaurus-plugin-content-docs/current/building-on-lisk/using-oracle-data/redstone-push.md b/i18n/ind/docusaurus-plugin-content-docs/current/building-on-lisk/using-oracle-data/redstone-push.md
new file mode 100644
index 000000000..e269c8c54
--- /dev/null
+++ b/i18n/ind/docusaurus-plugin-content-docs/current/building-on-lisk/using-oracle-data/redstone-push.md
@@ -0,0 +1,218 @@
+---
+title: ...with RedStone (Push)
+slug: /building-on-lisk/using-oracle-data/redstone-push
+description: A guide on using RedStone Push to access real-world data such as asset prices, directly from your smart contracts on the Lisk blockchain.
+keywords: [
+    Oracle
+    Oracles,
+    RedStone,
+    price feeds,
+    data feeds,
+    smart contract,
+    Lisk blockchain,
+    Lisk network,
+    Lisk testnet,
+    Lisk test network,
+    app development,
+    dapp development,
+    build a dapp on Lisk,
+    build on Lisk,
+    RedStone Push,
+  ]
+---
+
+# Accessing real-world data using the RedStone Oracle (Push)
+
+This page will explain how you can access oracle data using [RedStone Push](https://docs.redstone.finance/docs/get-started/models/redstone-push).
+
+RedStone is a data ecosystem that delivers frequently updated, reliable, and diverse data for your dApp and smart contracts deployed on Lisk.
+
+RedStone data feeds are compatible with Chainlink's [AggregatorV3Interface](https://docs.chain.link/data-feeds/using-data-feeds#solidity) and include the following components:
+
+- **Aggregator contract**: An aggregator is a contract that receives periodic data updates from the oracle network.
+Aggregators store aggregated data onchain so that consumers can retrieve it and act upon it within the same transaction.
+These contracts are already deployed on the Lisk network and can be directly used by Consumers.
+- **Consumer**: A consumer is an onchain or offchain application that uses Data Feeds.
+Consumer contracts use the `AggregatorV3Interface` to call functions on the proxy contract[^1] of the Aggregator to retrieve oracle data.
+
+[^1]: Proxy contracts are onchain proxies that point to the aggregator for a particular data feed.
+Using proxies enables the underlying aggregator to be upgraded without any service interruption to consuming contracts.
+
+## Data feeds on Lisk
+The following Aggregators are available on Lisk Mainnet for RedStone Push:
+
+- [ETH/USD L2PriceFeedWithoutRounds](https://blockscout.lisk.com/address/0x6b7AB4213c77A671Fc7AEe8eB23C9961fDdaB3b2)
+  - address: `0x6b7AB4213c77A671Fc7AEe8eB23C9961fDdaB3b2`
+- [LSK/USD L2PriceFeedWithoutRounds](https://blockscout.lisk.com/address/0xa1EbA9E63ed7BA328fE0778cFD67699F05378a96)
+  - address: `0xa1EbA9E63ed7BA328fE0778cFD67699F05378a96`
+- [USDT/USD L2PriceFeedWithoutRounds](https://blockscout.lisk.com/address/0xd2176Dd57D1e200c0A8ec9e575A129b511DBD3AD)
+  - address: `0xd2176Dd57D1e200c0A8ec9e575A129b511DBD3AD`
+- [USDC/USD L2PriceFeedWithoutRounds](https://blockscout.lisk.com/address/0xb4e6A7861067674AC398a26DD73A3c524C602184)
+  - address: `0xb4e6A7861067674AC398a26DD73A3c524C602184`
+- [WBTC/USD L2PriceFeedWithoutRounds](https://blockscout.lisk.com/address/0x13da43eA89fB692bdB6666F053FeE70aC61A53cd)
+  - address: `0x13da43eA89fB692bdB6666F053FeE70aC61A53cd`
+
+In this guide, we will develop a Consumer contract that will request the latest spot prices from the ETH, LSK and USDT data feeds.
+
+:::note
+RedStone Push is only fully available on Lisk Mainnet, so please make sure to deploy your Consumer contract on Lisk Mainnet as well.
+
+In case you wish to deploy on Lisk Sepolia Testnet, check the [Tellor](./tellor.md) guide, which is available for both networks.
+:::
+
+## Import
+
+To use the RedStone data inside your contract, import the [AggregatorV3Interface](https://docs.chain.link/data-feeds/using-data-feeds#solidity) from Chainlink like shown in the example contract below.
+
+For every data feed you like to store, create a new constant with type `AggregatorV3Interface`.
+
+In the constructor, set the above defined constants to point to the respective data feeds:
+Use the `AggregatorV3Interface()` function and pass the address of the respective data feed contract as parameter.
+
+```solidity
+// SPDX-License-Identifier: MIT
+pragma solidity ^0.8.28;
+
+import {AggregatorV3Interface} from "@chainlink/contracts/src/v0.8/shared/interfaces/AggregatorV3Interface.sol";
+
+contract RedStoneDataConsumer {
+    AggregatorV3Interface internal dataFeedETH;
+    AggregatorV3Interface internal dataFeedLSK;
+    AggregatorV3Interface internal dataFeedUSDT;
+
+    /**
+     * Network: Lisk
+     * Aggregator: ETH/USD
+     * Address: 0x6b7AB4213c77A671Fc7AEe8eB23C9961fDdaB3b2
+     */
+     /**
+     * Network: Lisk
+     * Aggregator: LSK/USD
+     * Address: 0xa1EbA9E63ed7BA328fE0778cFD67699F05378a96
+     */
+      /**
+     * Network: Lisk
+     * Aggregator: USDT/USD
+     * Address: 0xd2176Dd57D1e200c0A8ec9e575A129b511DBD3AD
+     */
+    constructor() {
+        dataFeedETH = AggregatorV3Interface(
+            0x6b7AB4213c77A671Fc7AEe8eB23C9961fDdaB3b2
+        );
+        dataFeedLSK = AggregatorV3Interface(
+            0xa1EbA9E63ed7BA328fE0778cFD67699F05378a96
+        );
+        dataFeedUSDT = AggregatorV3Interface(
+            0xd2176Dd57D1e200c0A8ec9e575A129b511DBD3AD
+        );
+    }
+}
+```
+
+## Reading data
+To read the data of the price feeds, we define the following functions in the contract:
+
+- `getRedStoneETHDataFeedLatestAnswer()`
+- `getRedStoneLSKDataFeedLatestAnswer()`
+- `getRedStoneUSDTDataFeedLatestAnswer()`
+
+Inside of the functions, call the [latestRoundData](https://docs.chain.link/data-feeds/api-reference#latestrounddata) on the respective data feeds to receive the latest spot prices for the respective token.
+
+The `latestRoundData()` function returns the following values:
+
+- `roundId`(uint80): The round ID.
+For all [data feeds](#data-feeds-on-lisk), the round is always `1`, because the contracts are without rounds, as the name suggests.
+- `answer`(int256): The data that this specific feed provides.
+Depending on the feed you selected, this answer provides asset prices, reserves, and other types of data.
+- `startedAt`(uint256): Timestamp of when the round started.
+- `updatedAt`(uint256): Timestamp of when the round was updated.
+- `answeredInRound`(uint80):  Deprecated - Previously used when answers could take multiple rounds to be computed.
+
+In this example, we will only use `answer` and `updatedAt`.
+The `updatedAt` value should be used to make sure that the `answer` is recent enough for your application to use it.
+You can compare `updatedAt` to the latest block time (`uint256 currentTime = block.timestamp;`) to ensure you are only using the latest oracle data in your application.
+
+```solidity
+// SPDX-License-Identifier: MIT
+pragma solidity ^0.8.28;
+
+/**
+ * THIS IS AN EXAMPLE CONTRACT THAT USES HARDCODED
+ * VALUES FOR CLARITY.
+ * THIS IS AN EXAMPLE CONTRACT THAT USES UN-AUDITED CODE.
+ * DO NOT USE THIS CODE IN PRODUCTION.
+ */
+
+import {AggregatorV3Interface} from "@chainlink/contracts/src/v0.8/shared/interfaces/AggregatorV3Interface.sol";
+
+contract RedStoneDataConsumer {
+  AggregatorV3Interface internal priceFeedETH;
+  AggregatorV3Interface internal priceFeedLSK;
+  AggregatorV3Interface internal priceFeedUSDT;
+
+  constructor() {
+      priceFeedETH = AggregatorV3Interface(
+          0x6b7AB4213c77A671Fc7AEe8eB23C9961fDdaB3b2
+      );
+      priceFeedLSK = AggregatorV3Interface(
+          0xa1EbA9E63ed7BA328fE0778cFD67699F05378a96
+      );
+      priceFeedUSDT = AggregatorV3Interface(
+          0xd2176Dd57D1e200c0A8ec9e575A129b511DBD3AD
+      );
+  }
+
+  /**
+    * Returns the latest ETH price, and when it was updated.
+    */
+  function getRedStoneETHDataFeedLatestAnswer() public view returns (int, uint) {
+      (
+        /* uint80 roundID */,
+        int answer,
+        uint updatedAt,
+        /*uint startedAt*/,
+        /*uint80 answeredInRound*/
+      ) = priceFeedETH.latestRoundData();
+      return (answer, updatedAt);
+  }
+  /**
+    * Returns the latest LSK price, and when it was updated.
+    */
+  function getRedStoneLSKDataFeedLatestAnswer() public view returns (int, uint) {
+      (
+        /* uint80 roundID */,
+        int answer,
+        uint updatedAt,
+        /*uint startedAt*/,
+        /*uint80 answeredInRound*/
+      ) = priceFeedLSK.latestRoundData();
+      return (answer, updatedAt);
+  }
+  /**
+    * Returns the latest USDT price, and when it was updated.
+    */
+  function getRedStoneUSDTDataFeedLatestAnswer() public view returns (int, uint) {
+      (
+        /* uint80 roundID */,
+        int answer,
+        uint updatedAt,
+        /*uint startedAt*/,
+        /*uint80 answeredInRound*/
+      ) = priceFeedUSDT.latestRoundData();
+      return (answer, updatedAt);
+  }
+}
+```
+
+## Deploying on Lisk
+
+To deploy the smart contract on Lisk, follow the guides 
+
+- [Deploying a smart contract with Hardhat](../deploying-smart-contract/with-Hardhat), or
+- [Deploying a smart contract with Foundry](../deploying-smart-contract/with-Foundry)
+
+:::note
+RedStone Push is only available on Lisk Mainnet, so please make sure to deploy your Consumer contract on Lisk Mainnet as well.
+
+In case you wish to deploy on Lisk Sepolia Testnet, check the [Tellor](./tellor.md) guide, which is available for both networks.
+:::
\ No newline at end of file
diff --git a/i18n/ind/docusaurus-plugin-content-docs/current/building-on-lisk/using-oracle-data/tellor.md b/i18n/ind/docusaurus-plugin-content-docs/current/building-on-lisk/using-oracle-data/tellor.md
new file mode 100644
index 000000000..1fb3e8d2d
--- /dev/null
+++ b/i18n/ind/docusaurus-plugin-content-docs/current/building-on-lisk/using-oracle-data/tellor.md
@@ -0,0 +1,207 @@
+---
+title: ...with Tellor
+slug: /building-on-lisk/using-oracle-data/tellor
+description: A guide on using Tellor Data Feeds to access real-world data such as asset prices, directly from your smart contracts on the Lisk blockchain.
+keywords: [
+    Oracle
+    Oracles,
+    Redstone,
+    price feeds,
+    data feeds,
+    smart contract,
+    Lisk blockchain,
+    Lisk network,
+    Lisk testnet,
+    Lisk test network,
+    app development,
+    dapp development,
+    build a dapp on Lisk,
+    build on Lisk,
+  ]
+---
+
+# Using oracle data with Tellor
+This page will explain how your application can access oracle data using Tellor.
+
+[Tellor](https://tellor.io/) is an immutable decentralized oracle protocol where parties can request the value of an offchain data point (e.g. ETH/USD, LSK/USD) and reporters compete to add this value to an onchain databank.
+The inputs to this databank are secured by a network of staked reporters.
+
+Tellor utilizes crypto-economic incentive mechanisms, rewarding honest data submissions by reporters and punishing bad actors through the issuance of Tellor’s token, Tributes (TRB) and a dispute mechanism.
+
+This incentivizes an open, permissionless network of data reporting and data validation, ensuring that data can be provided by anyone and checked by everyone.
+
+## Installation
+The first thing you'll want to do is install the basic tools necessary for using Tellor as your oracle.
+
+To install [usingtellor](https://github.com/tellor-io/usingtellor), run one the following commands:
+
+- Hardhat: `npm install usingtellor`
+- Foundry: `forge install tellor-io/usingtellor`
+
+Once installed, this will allow your contracts to inherit the functions from the 'UsingTellor' contract.
+
+Great! Now that you've got the tools ready, let's go through a simple exercise where we retrieve the `eth/usd` and `lsk/usd` prices from Tellor.
+
+## Import
+
+```solidity
+pragma solidity >=0.8.0;
+
+import "usingtellor/contracts/UsingTellor.sol";
+/**
+     * Network: Lisk Mainnet
+     * Address: 0x896419Ed2E0dC848a1f7d2814F4e5Df4b9B9bFcc
+*/
+contract MyContract is UsingTellor {
+
+  constructor(address payable _tellorOracle) UsingTellor(_tellorOracle) {
+
+  }
+
+  // ...
+
+}
+```
+
+To import the UsingTellor contract into your Solidity file, pass the desired Tellor Oracle address as a parameter. 
+For the Lisk Mainnet, the Tellor Oracle address is: [0x896419Ed2E0dC848a1f7d2814F4e5Df4b9B9bFcc](https://blockscout.lisk.com/address/0x896419Ed2E0dC848a1f7d2814F4e5Df4b9B9bFcc)
+
+## Reading data
+
+In the example below, we add two functions:
+
+- `getETHSpotPrice()` that reads the ETH/USD price feed and another function 
+- `getLSKSpotPrice()` that reads the LSK/USD price feed from the Oracle
+
+```solidity
+// SPDX-License-Identifier: MIT
+pragma solidity >=0.8.0;
+
+import { UsingTellor } from "usingtellor/contracts/UsingTellor.sol";
+
+contract MyContract is UsingTellor {
+
+    uint256 public ethLastStoredTimestamp;
+    uint256 public ethLastStoredPrice;
+    uint256 public lskLastStoredTimestamp;
+    uint256 public lskLastStoredPrice;
+    bytes32 public immutable ethQueryId;
+    bytes32 public immutable lskQueryId;
+    uint256 public constant DISPUTE_BUFFER = 20 minutes;
+    uint256 public constant STALENESS_AGE = 12 hours;
+
+    error StalePrice(uint256 price, uint256 timestamp);
+    error NoValueRetrieved(uint256 timestamp);
+
+    /** 
+     * @dev the constructor sets the Tellor address and the ETH and LSK queryIds
+     * @param _tellorOracle is the address of the Tellor oracle
+     */
+    constructor (address payable _tellorOracle) UsingTellor(_tellorOracle) {
+        // set the ETH queryId
+        bytes memory _ethQueryData = abi.encode("SpotPrice", abi.encode("eth", "usd"));
+        ethQueryId = keccak256(_ethQueryData);
+        // set the LSK queryId
+        bytes memory _lskQueryData = abi.encode("SpotPrice", abi.encode("lsk", "usd"));
+        lskQueryId = keccak256(_lskQueryData);
+    }
+
+    /** 
+     * @dev Allows a user contract to read the ETH price from Tellor and perform some 
+     * best practice checks on the retrieved data
+     * @return _value the ETH spot price from Tellor, with 18 decimal places
+     * @return timestamp the value's timestamp
+     */
+    function getETHSpotPrice()
+        public
+        returns (
+            uint256 _value,
+            uint256 timestamp
+        )
+    {
+        // retrieve the most recent 20+ minute old ETH price. 
+        // the buffer allows time for a bad value to be disputed
+        (bytes memory _data, uint256 _timestamp) = _getDataBefore(ethQueryId, block.timestamp - DISPUTE_BUFFER);
+
+        // check whether any value was retrieved
+        if (_timestamp == 0 || _data.length == 0) revert NoValueRetrieved(_timestamp);
+
+        // decode the value from bytes to uint256
+        _value = abi.decode(_data, (uint256));
+
+        // prevent a back-in-time dispute attack by caching the most recent value and timestamp.
+        // this stops an attacker from disputing tellor values to manupulate which price is used 
+        // by your protocol
+        if (_timestamp > ethLastStoredTimestamp) {
+            // if the new value is newer than the last stored value, update the cache
+            ethLastStoredTimestamp = _timestamp;
+            ethLastStoredPrice = _value;
+        } else {
+            // if the new value is older than the last stored value, use the cached value
+            _value = ethLastStoredPrice;
+            _timestamp = ethLastStoredTimestamp;
+        }
+
+        // check whether value is too old
+        if (block.timestamp - _timestamp > STALENESS_AGE) revert StalePrice(_value, _timestamp);
+
+        // return the value and timestamp
+        return (_value, _timestamp);
+    }
+
+    /** 
+     * @dev Allows a user contract to read the LSK price from Tellor and perform some 
+     * best practice checks on the retrieved data
+     * @return _value the LSK spot price from Tellor, with 18 decimal places
+     * @return timestamp the value's timestamp
+     */
+    function getLSKSpotPrice()
+        public
+        returns (
+            uint256 _value,
+            uint256 timestamp
+        )
+    {
+        (bytes memory _data, uint256 _timestamp) = _getDataBefore(lskQueryId, block.timestamp - DISPUTE_BUFFER);
+
+        if (_timestamp == 0 || _data.length == 0) revert NoValueRetrieved(_timestamp);
+
+        _value = abi.decode(_data, (uint256));
+
+        if (_timestamp > lskLastStoredTimestamp) {
+            lskLastStoredTimestamp = _timestamp;
+            lskLastStoredPrice = _value;
+        } else {
+            _value = lskLastStoredPrice;
+            _timestamp = lskLastStoredTimestamp;
+        }
+
+        if (block.timestamp - _timestamp > STALENESS_AGE) revert StalePrice(_value, _timestamp);
+
+        return (_value, _timestamp);
+    }
+}
+```
+
+You can adapt this contract to your needs.
+The example utilizes some best practices[^1] for using Tellor by implementing a dispute time buffer and a data staleness check.
+In addition, it also seeks to mitigate back-in-time dispute attacks by caching the most recent value and timestamp.
+
+[^1]: Based on examples in [Tellor's best practices repository](https://github.com/tellor-io/best-practices-user/tree/main)
+
+:::tip
+For a general overview of best practices using Tellor, go to the [User checklists](https://docs.tellor.io/tellor/getting-data/user-checklists) in the Tellor docs.
+:::
+
+## Deploying on Lisk
+
+To deploy the smart contract on Lisk Sepolia or Lisk Mainnet, follow the guides 
+
+- [Deploying a smart contract with Hardhat](../deploying-smart-contract/with-Hardhat), or
+- [Deploying a smart contract with Foundry](../deploying-smart-contract/with-Foundry)
+
+## Further resources
+
+- For a more robust implementation of the Tellor oracle, check out the full list of available functions [here](https://github.com/tellor-io/usingtellor/blob/master/README.md).
+- Have a specific Data Feed Request? [Fill out this form](https://github.com/tellor-io/dataSpecs/issues/new?assignees=&labels=&template=new_query_type.yaml&title=%5BNew+Data+Request+Form%5D%3A+).
+- Still have question? Reach out to the Tellor team on Discord [here](https://discord.gg/tellor).
\ No newline at end of file
diff --git a/sidebars.js b/sidebars.js
index 0a199518b..1ba87194b 100644
--- a/sidebars.js
+++ b/sidebars.js
@@ -116,6 +116,7 @@ const sidebars = {
           items: [
             'building-on-lisk/using-oracle-data/tellor',
             'building-on-lisk/using-oracle-data/redstone-pull',
+            'building-on-lisk/using-oracle-data/redstone-push',
           ],
         }
       ],