Ecosystem page update

public/locales/en/translation.json

@@ -90,6 +90,7 @@
       "theScrollMessenger": "The Scroll Messenger",
       "transactionFeesOnScroll": "Transaction Fees on Scroll",
       "toolingDeployedOnScroll": "Tooling deployed On Scroll",
+      "developerEcosystem": "Developer Ecosystem",
       "l2Fee": "L2 Fee",
       "l1Fee": "L1 Fee",
       "gasOracle": "Gas Oracle",

public/locales/es/translation.json

@@ -89,6 +89,7 @@
       "erc1155TokenBridge": "ERC1155 Token Bridge",
       "theScrollMessenger": "El Scroll Messenger",
       "transactionFeesOnScroll": "Comisiones de Transacciones en Scroll",
+      "developerEcosystem": "Ecosistema de Desarrollo",
       "l2Fee": "Comisión L2",
       "l1Fee": "Comisión L1",
       "gasOracle": "Gas Oracle",

src/config/sidebar.ts

@@ -141,6 +141,10 @@ export const getSidebar = () => {
             title: t("sidebar.developers.toolingDeployedOnScroll"),
             url: formatUrl("developers/tooling-deployed-on-scroll"),
           },
+          {
+            title: t("sidebar.developers.developerEcosystem"),
+            url: formatUrl("developers/developer-ecosystem"),
+          },
         ],
       },
       {

src/content/docs/en/developers/developer-ecosystem.mdx

@@ -0,0 +1,93 @@
+---
+section: developers
+date: Last Modified
+title: "Developer Ecosystem"
+lang: "en"
+permalink: "developers/developer-quickstart"
+excerpt: "Scroll Developer Quickstart helps you acquire testnet Ether, configure your network, and access all of your favorite tooling"
+whatsnext: { "Verify Your Smart Contracts": "/en/developers/verifying-smart-contracts" }
+---
+
+import Aside from "../../../../components/Aside.astro"
+import ClickToZoom from "../../../../components/ClickToZoom.astro"
+import networkSelection from "./_images/mmNetworkSelection.png"
+import injectedProviderMM from "./_images/injectedProviderMM.png"
+import ToggleElement from "../../../../components/ToggleElement.astro"
+import wagmiDemo from "../../../../assets/images/developers/getting-started/wagmi-demo.png"
+
+Explore Scroll’s most active ecosystem tooling and integrate it into your projects. For detailed data, see our [our Dune dashboard](https://dune.com/scroll/developer-ecosystem).
+
+# DEX Volume
+
+Higher DEX volume creates more yield for liquidity providers and brings more arbitrage opportunities. As a builder, you can permissionlessly integrate your application with DEXs to provide swaps or generate yield for your users.
+
+<iframe src="https://dune.com/embeds/5450198/8891807"/>
+
+| Dex | Contract | Docs |
+| - | - |- |
+| Ambient | [Vault](https://scrollscan.com/address/0xaaaaAAAACB71BF2C8CaE522EA5fa455571A74106), [Router](0xfB5f26851E03449A0403Ca945eBB4201415fd1fc) | [CrocSwap](https://docs.ambient.finance/developers/dex-contract-interface/usercmd-callpaths) |
+| Syncswap | [Scroll Deployments](https://docs.syncswap.xyz/syncswap/smart-contracts/smart-contracts#scroll) | [SyncSwap](https://docs.syncswap.xyz/api-documentation) |
+| HonneyPop | [Universal Router](https://scrollscan.com/address/0xc2730c06f3ec562d4e1ff63e04d4c75f417c3366) | [Uniswap Universal Router](https://docs.uniswap.org/contracts/universal-router/technical-reference) |
+| Uniswap V3 | [Scroll Deployments](https://gov.uniswap.org/t/rfc-deploy-uniswap-v3-on-scroll/21651/7) | [Uniswap v3](https://docs.uniswap.org/contracts/v3/overview) | 
+| iZUMi | [Scroll Deployments](https://developer.izumi.finance/iZiSwap/deployed_contracts/mainnet) | [iZiSwap](https://developer.izumi.finance/iZiSwap/contracts/)
+| SushiSwap | [RedSnwapper Router](https://scrollscan.com/address/0xac4c6e212a361c968f1725b4d055b47e63f80b75#code) | Uniswap V2-like contracts |
+
+# DEX Liquidity By Token
+
+DEXes with more liquidity will lead to less slippage when performing swaps.
+
+## WETH in DEXes
+
+<iframe src="https://dune.com/embeds/5515181/8982797"/>
+
+## USDC in DEXes
+
+<iframe src="https://dune.com/embeds/5480764/8932594"/>
+
+## SCR in DEXes
+
+<iframe src="https://dune.com/embeds/5495203/8952930"/>
+
+# Bridge Monthly Transactions
+
+Bridges provide not only ERC-20 token transfers but also are able to send arbitrary data cross-chains. A higher number of transactions signals user preference and trust in the bridge.
+
+<iframe src="https://dune.com/embeds/5328584/8734000"/>
+
+| Bridge | Contract | Docs |
+| - | - |- |
+| li.fi | [Diamond Entryway](https://docs.li.fi/introduction/lifi-architecture/smart-contract-addresses) | [Official docs](https://docs.li.fi/introduction/introduction) |
+| Across | [Scroll Deployment](https://docs.across.to/reference/contract-addresses/scroll-chain-id-534352) | [Official Docs](https://docs.across.to/) |
+| Stargate | [Scroll Deployment](https://docs.stargate.finance/resources/contracts/mainnet-contracts#scroll-endpointid-30214) | [Official Documentation](https://docs.stargate.finance/introduction/overview) |
+| Rhino | [Scroll Deployment](https://docs.rhino.fi/general/contract-addresses) | [Official Documentation](https://docs.rhino.fi/get-started/introduction) |
+| Squid | [Squid Router](https://scrollscan.com/address/0xce16f69375520ab01377ce7b88f5ba8c48f8d666#code) | [Official Docs](https://docs.squidrouter.com/) |
+
+# Borrowing & Lending Platforms
+
+Borrowing and lending platforms let users earn yield, leverage positions or protect against volatility. TVL data is available on [DeFiLlama](https://defillama.com/protocols/lending/Scroll), where the higher the more stable rates and yields. The chart below compares transaction counts across each platform indicating users pereference.
+
+<iframe src="https://dune.com/embeds/5514443/8981638"/>
+
+| Lending Platform | Contract | Docs |
+| - | - |- |
+| EtherFi Borrowing Market | [EtherFi Cash Vault](https://scrollscan.com/address/0x3a6A724595184dda4be69dB1Ce726F2Ac3D66B87) | [EtherFi Cash Docs](https://etherfi.gitbook.io/etherfi/cash/technical-documentation) |
+| Aave V3 | [Aave Contracts](https://aave.com/docs/resources/addresses) | [Aave Documentation](https://aave.com/docs) |
+| LayerBank | [LayerBank Contracts](https://github.com/layerbank-foundation/v2-contracts) | [Layer Bank V2 Documentation](https://docs.layerbank.finance/) |
+| Rho Markets | [Rho Markets Contracts](https://docs.rhomarkets.xyz/protocol/rho-markets-contract-overview#core-contracts) | [Rho Markets Documentation](https://docs.rhomarkets.xyz/) |
+| Morpho | [Morpho Contracts](https://docs.morpho.org/getting-started/resources/addresses#morpho-contracts) | [Morpho Documentation](https://docs.morpho.org/)  |
+| Compound | [Compund Contracts](https://docs.compound.finance/#protocol-contracts) | [Compund Documentation](https://docs.compound.finance/#compound-iii) |
+
+# ETH Liquid Staking & Rebase Tokens
+
+Liquid Staking Tokens produce yield by just holding them on the wallet by a process called Rebase. Higher market cap indicates more accesibility to users.
+
+<iframe src="https://dune.com/embeds/5515252/8983149"/>
+
+# Oracles on Scroll
+
+Oracles offer services that blockchains can't handle natively, by bringing in data from the outside world. In the Scroll ecosystem, Chainlink provides price feeds, while Anyrand supplies decentralized randomness.
+
+| VRF | Contract | Docs |
+| - | - |- |
+| Anyrand | [Anyrand Contract Address](https://docs.anyrand.com/using-anyrand/supported-networks) | [Anyrand Documentation](https://docs.anyrand.com/) |
+| Chainlink | [Chainlink Price Feeds](https://docs.chain.link/data-feeds/price-feeds/addresses?page=1&testnetPage=1&network=scroll) | [Price Feeds Documentation](https://docs.chain.link/data-feeds/using-data-feeds) |

src/content/docs/en/developers/guides/running-a-scroll-node.mdx

@@ -132,6 +132,10 @@ Insert your config in the yaml file and save it, recommended config would be :
             --l1.endpoint "${Your l1 endpoint}"
             --da.blob.blobscan "${Your blobscan endpoint}"
             --da.blob.beaconnode "${Your beaconnode endpoint}"
+            # Scroll provides aws s3 endpoints for both scroll-mainnet and scroll-sepolia
+            # scroll-mainnet : https://scroll-sepolia-blob-data.s3.us-west-2.amazonaws.com/
+            # scroll-sepolia: https://scroll-mainnet-blob-data.s3.us-west-2.amazonaws.com/
+            --da.blob.awss3 "${Your aws s3 endpoint}"
             --cache.snapshot=0
         logging:
             driver: "json-file"

src/content/docs/en/developers/l1-and-l2-bridging/the-scroll-messenger.mdx

@@ -10,99 +10,90 @@ excerpt: "The Scroll Messenger documentation for arbitrary message passing betwe
 
 import Aside from "../../../../../components/Aside.astro"
 
-The Scroll Messenger contracts allow for sending arbitrary messages from L1 to L2 or vice versa. This enables executing functions on another chain in a secure and permissionless way. To send a message from L1 to L2, use
-the messenger smart contract deployed on L1, `L1ScrollMessenger`. To send a message from L2 to L1, use the contract deployed on L2, `L2ScrollMessenger`.
-
-<Aside type="caution" title="">
-  When sending a transaction through the **Scroll Messenger** deployed on L1 and L2, the resulting transaction sender
-  (`CALLER` or `msg.sender`) will be the Messenger Contract address deployed on the receiving chain.
-  <br />
-  In future Scroll versions, enforced transactions from the L1 will allow setting the sender on L2 as the original EOA
-  on L1. It will also allow 3rd parties to relay signed transactions securely.
-</Aside>
+The Scroll Messenger contracts allow for sending arbitrary messages from L1 to L2 or vice versa. This enables executing functions on another chain in a secure and permissionless way. To send a message from L1 to L2, use the messenger smart contract deployed on L1, `L1ScrollMessenger`. To send a message from L2 to L1, use the contract deployed on L2, `L2ScrollMessenger`. You can find the smart contract addresses in the [Scroll Contracts](/developers/scroll-contracts) page.
+
+## Sending a Message
+
+Sending a cross-chain message through the `ScrollMessenger` is performed by calling the [`sendMessage`](#sendmessage) function. In this function you set the `target` address that will receive the message in the other chain, a `value` parameter for ETH transfers and `message` byte array to be sent as `CALLDATA` for smart contract execution. Notice the contract also expects a `gasLimit` parameter that you can safely set to `0` and a `refundAddress` which you can set as the sender EOA. These last two parameters are legacy since L1 to L2 transactions don't need to pay gas and L2 to L1 gas costs are handled differently, as we’ll cover in the next section.
 
-## Finalizing transactions on L1
+## Relaying Transactions on L1
 
-Any upcoming transactions from L2 need to be finalized using the `relayMessageWithProof` function on the Scroll Messenger
-contract. We call this process "submitting an Execute Withdrawal transaction," and it is required for both sending arbitrary messages and transferring assets through a gateway or the router. When you use `relayMessageWithProof`, you'll have to provide a Merkle inclusion proof showing your transaction is included in the trie of "withdrawal" messages, along with other parameters. Producing this proof and these values can be done locally and permissionlessly, but at the moment, the easiest way to retrieve these parameters is through our backend APIs:
+Unlike L1 to L2 transactions, L2 to L1 transactions need to be finalized using the [`relayMessageWithProof`](#relaymessagewithproof) function on the Scroll Messenger contract. We call this process "submitting an Execute Withdrawal transaction", and it is required for both sending arbitrary messages and transferring assets through a gateway or the router. When you use `relayMessageWithProof`, you'll have to provide a Merkle inclusion proof showing your transaction is included in the trie of "withdrawal" messages, along with other parameters. Producing this proof and these values can be done locally and permissionlessly, but at the moment, the easiest way to retrieve these parameters is through our backend APIs:
 
 - Scroll Sepolia API: https://sepolia-api-bridge-v2.scroll.io/api/
 - Scroll API: https://mainnet-api-bridge-v2.scroll.io/api/
 
-<Aside type="danger" title="Experimental API">
-  This API was made for our Bridge UI. It is not yet finalized and may change in the future. We will update this guide
-  when the API is finalized. Additionally, all examples below use the Sepolia API service -- the calls should be easily
-  adapted to work on mainnet.
-</Aside>
-
-Supply the address of the EOA or contract responsible for initiating the original transaction on L2 to the `/claimable`
-endpoint. The API backend will provide you with all the necessary information to successfully conclude the transaction on L1.
-Take a look at the following example:
+Supply the address of the EOA or contract responsible for initiating the original transaction on L2 to the `/unclaimed` endpoint. The API backend will provide you with all the necessary information to successfully conclude the transaction on L1. Take a look at the following example:
 
 ```bash
-https://sepolia-api-bridge.scroll.io/api/claimable?address=0x031407eaaffFB4f1EC2c999bE4477E52C81de3c5&page_size=10&page=1
+https://sepolia-api-bridge-v2.scroll.io/api/l2/unclaimed/withdrawals?address=0x031407eaaffFB4f1EC2c999bE4477E52C81de3c5&page=1&page_size=10
 ```
 
+<Aside type="caution" title="The address parameter">
+  The `address` parameter on the `/withdrawals` endpoint expects the sender EOA or contract address in the case sensitive [EIP-55 Mixed-cased Checksum](https://eips.ethereum.org/EIPS/eip-55) format.
+</Aside>
+
 The API should return your transaction data in the following format:
 
 ```json
 {
   "errcode": 0,
   "errmsg": "",
   "data": {
-    "result": [
+    "results": [
       {
-        "hash": "0xa476850306d6ee52b127628ded34dcf2343570873cce9c5383bd497db48d4f9b",
-        "amount": "",
-        "to": "",
-        "isL1": false,
-        "l1Token": "",
-        "l2Token": "",
-        "blockNumber": 748,
-        "blockTimestamp": null,
-        "finalizeTx": {
+        "hash": "0xd56f873c953e798521020d8b6885e7509069fcf0e12bdb1227b840c2d29c6645",
+        "replay_tx_hash": "",
+        "refund_tx_hash": "",
+        "message_hash": "0x65f7d787ff0a3fe7f42b603650afc9c0906f44cd913d52a9e37d1defbe526b6e",
+        "token_type": 1,
+        "token_ids": [],
+        "token_amounts": [
+          "0"
+        ],
+        "message_type": 2,
+        "l1_token_address": "",
+        "l2_token_address": "",
+        "block_number": 11517097,
+        "tx_status": 0,
+        "counterpart_chain_tx": {
           "hash": "",
-          "amount": "",
-          "to": "",
-          "isL1": false,
-          "blockNumber": 0,
-          "blockTimestamp": null
+          "block_number": 0
         },
-        "claimInfo": {
-          "from": "0x031407eaaffFB4f1EC2c999bE4477E52C81de3c5",
-          "to": "0x1039057185CFe192d16c03F5656225821A193FD5",
+        "claim_info": {
+          "from": "0x707e55a12557E89915D121932F83dEeEf09E5d70",
+          "to": "0xC96dde523FB7aB544DCe99F78C10272502452Ae7",
           "value": "0",
-          "nonce": "9",
-          "batch_hash": "0x49a18d72dbceeb957f918947b532db452c031f528e7e6bf329007066638c5e50",
-          "message": "0xa413686200000000000000000000000000000000000000000000000000000000000000200000000000000000000000000000000000000000000000000000000000000005686f6c6973000000000000000000000000000000000000000000000000000000",
-          "proof": "0x69b4ee6cf9a38bed79668ddd347fef2bdff44c3760c9309fa41decfd60202d22ad3228b676f7d3cd4284a5443f17f1962b36e491b30a40b2405849e597ba5fb5b4c11951957c6f8f642c4af61cd6b24640fec6dc7fc607ee8206a99e92410d3079f53171df5c0661d2afe86c4d97b6f34278daf6a0ea9baff5b4fc979d5629a5",
-          "batch_index": "93"
+          "nonce": "388896",
+          "message": "0x32e43a11",
+          "proof": {
+            "batch_index": "113627",
+            "merkle_proof": "0x595e51b1e616792354ed5337d73ab55e8cb62fec3d5b9254e0c5549a6359e07cad3228b676f7d3cd4284a5443f17f1962b36e491b30a40b2405849e597ba5fb5b4c11951957c6f8f642c4af61cd6b24640fec6dc7fc607ee8206a99e92410d3021ddb9a356815c3fac1026b6dec5df3124afbadb485c9ba5a3e3398a04b7ba85e58769b32a1beaf1ea27375a44095a0d1fb664ce2dd358e7fcbfb78c26a19344572901eb2c02c80041fe5b5524ab76baafbca7c7bcad9fcbd8a8f492f14ccfeb887c22bd8750d34016ac3c66b5ff102dacdd73f6b014e710b51e8022af9a1968ffd70157e48063fc33c97a050f7f640233bf646cc98d9524c6b92bcf3ab56f83936fdf2b4de30e14ed4e80b8ad6789e4da1c12dc0da39b4a0d87faf93f62b6843fb096223ed1df0ad0a5e4ad87b3bbeca3ec02bbd30b173a9e8bb06f6cdbdb0f5b57c8b6a31abc39d2ac02c6c49d65e06bd47bdc87a4c26f9e37d04aaa134438cb3e31fffb058537dac499fbd1fad3548af7ccc35028cebfb875e1541f37d5a53490c6ceeb450aecdc82e28293031d10c7d73bf85e57bf041a97360aa2c5d99c4c1bd797081f10d69a340d28e20e54bae159d5eddb976c97b3193a8bd5a38e8afc715bd0872994d0083b471117d24f5be50dd072551f0d41ffe8137346039d94d98dc6e569c87f338c68fa23139bafe238eb1308610d4a9b148fc1955128d4ce7874b09783cef2e7750f7ea24f6090c9ce47f33cf25ca5e16a1207b4a50fda2be1d3b5c807b281e4683cc6d6315cf95b9ade8641defcb32372f1c126e398ef7a1ef973d30ca636d922d10ae577c73bc4fe92699225f30c0c2e9d6727bceb256d"
+          },
+          "claimable": true
         },
-        "createdTime": null
+        "block_timestamp": 1755015985,
+        "batch_deposit_fee": ""
       }
     ],
     "total": 1
   }
 }
 ```
 
-The `claimInfo` object under the `result` json returned has all the information needed to execute your transaction on L1. The
-parameters needed by the `relayMessageWithProof` are: `from`, `to`, `value`, `nonce`, `message` and `proof`. Supply these to
-the `relayMessageWithProof` function on L1 to execute and finalize your transaction on L1.
+When the transaction finalizes on L1, `claim_info` object under the `result` json returned will have all the information needed to execute your transaction on L1. The
+parameters needed by the `relayMessageWithProof` are: `from`, `to`, `value`, `nonce`, `message` and `proof`. Supply these to the `relayMessageWithProof` function on L1 to execute and finalize your transaction on L1.
 
 <Aside type="tip" title="">
-  All L2 transactions are bundled into batches – you have to wait for the batch that includes your transaction to
-  finalize before calling `relayMessageWithProof`. Your transaction batch index is returned in the `batch_index` value
-  on the `/claimable` endpoint, and you can follow the progress on the [Scroll Rollup
-  Explorer](https://scroll.io/rollupscan?page=1&per_page=10).
+  All L2 transactions are bundled into batches, you have to wait for the batch that includes your transaction to finalize before calling `relayMessageWithProof`. Your transaction batch index is returned in the `batch_index` value on the `/unclaimed` endpoint, and you can follow the progress on the [Scroll Rollup Explorer](https://scroll.io/rollupscan?page=1&per_page=10).
 </Aside>
 
 ## Messenger API
 
-Please visit the [npm library](https://www.npmjs.com/package/@scroll-tech/contracts?activeTab=code) for the complete Scroll contract API documentation.
-
 ### sendMessage
 
+See implementation at [L2ScrollMessenger on Github](https://github.com/scroll-tech/scroll-contracts/blob/main/src/L2/L2ScrollMessenger.sol).
+
 ```solidity
 function sendMessage(
   address target,
@@ -125,6 +116,8 @@ Sends arbitrary data from one chain to another. It allows us to execute function
 
 ### relayMessageWithProof
 
+See implementation at [L1ScrollMessenger on Github](https://github.com/scroll-tech/scroll-contracts/blob/main/src/L1/L1ScrollMessenger.sol).
+
 ```solidity
 function relayMessageWithProof(
   address from,
@@ -136,7 +129,7 @@ function relayMessageWithProof(
 ) external;
 ```
 
-Relay a L2 => L1 message with message proof.
+Execute a L2 to L1 message with message proof.
 
 | Parameter | Description                                                  |
 | --------- | ------------------------------------------------------------ |