Spire
Spire is a SDK lets you spin up an app-specific L3 on top of zkEVM rollups such as Polygon zkEVM or Scroll. We're also building a demo L3 app that monitors a set of contracts on the L2, indexes some data, and does some computing over it.
Project Description
This project aspires to hold an SDK which can be used to spin up app-specific L3 on top of a zkEVM rollup. It is called Spire because it scales up Ethereum L2 vertically or in a fractal fashion. We'd like the user experience and convenience of something like Cosmos SDK, but on top of zkEVM rollups like Polygon zkEVM, Scroll, and Taiko.
These are contract addresses deployed on Scroll:
- rollup_contract_address: "0xae32697367cfEAC4901D34BA689B56c6843a6e99"
- rollup_bridge_address: "0x7135711265EDF5019Abc5dcA6C5c8A5e4b1CA863"
These are contract addresses deployed on Polygon zkEVM:
- rollup_contract_address: "0x6f3055C11AE84b0ab06cc263c4A0fD56A5739C51"
- rollup_bridge_address: "0xfDa870ABD588E622d0a8529dbAAEf1E86C4Af1cc"
The next step is to build a sample L3 app to index data on Uniswap on Polygon zkEVM / Scroll, and list the volume/liquidity/price of tokens. Any contracts on L2s can refer to and use those indexed data provided by L3 built with Spire SDK.
The future vision is that all of the L3 spun up with Spire will be interoperable and also call contracts on underlying L2s, achieving flexible composability across L2/L3s.
How it's Made
The project is built using Rust to be very fast and to occupy very low memory. Using Rust we eliminate many of the problems that can appear unexpectedly at runtime. For the network interaction, we use ethers-rs rust library. In order to be very efficient and not waste a lot of network RPC calls the main network RPC uses a WebSocket connection. This will allow to if the rollup network reaches a very high number of blocks per second. For the Solidity contracts development, we use Foundry.
