Stackr Network

slide deck: https://drive.google.com/file/d/1GInZ-lnSZJ3H60azRclY5tXZXhHcegCI/view

reachout to us - @kautukkundan, shivam7vastava

Problems Identified

• It has been proven time and again that application specific rollups can be optimized to a great degree for the particular objective they fulfill. We have great examples like The Hubble Optimistic Rollup that has been optimized for ERC-20 transfers making it the cheapest solution for token transfers and is used by World Coin.

• We also have dYdX L2 which uses StarkWare’s StarkEx solution for optimizing trading, making it a really cheap option for self-custodial transactions. These application specific rollups can also be built to support other applications like on-chain games.

• However, there arent many applications doing it because it is not feasible for every application developer to build a rollup first and then build the application later. They would rather focus on building the application than building the infrastructure to support their application even if it means sacrificing optimizations.

• Moreover, aside from the building difficulty, running the sequencer in itself is a cumbersome task. And if the project which built the rollup runs the sequencer as well, it leads to several security red flags since it becomes centralized.

Solution

Stackr Network aims at bridging all these gaps as well as paving the path for future growth at scale by providing an SDK for building application-specific rollups. It also includes a network of decentralized independent sequencers to bundle the incoming transactions coming from applications and submit them on-chain which further improves data optimization.

Developers can leverage this SDK to quickly set up their own optimistic rollups by using the included APIs to build and connect to the stackr ecosystem.

How does it work?

Rollups are very simple. They are essentially State Machines that work on the principle of state and state transitions.

You have a state, which gets mutated via a tx based on a fixed state transition rule. The inputs and the final state are then stored on-chain

Using the SDK, the developers only need to worry about these 2 things -

1. How they define the state
2. How they define the state transition function

All the heavy lifting is done by the SDK itself and the developer is abstracted away from most of the EVM related overhead by providing interfaces in generic languages like TypeScript.

This is a huge added bonus for Web2 devs with little to no web3 experience so that they can use their existing skills to build on ethereum.

The SDK provides contracts written in Solidity and app nodes written in typescript. The sequencers themselves are written in typescript.

Developers can simply call "npx create-rollup <dir_name>" (not pushed on npm yet, please install locally) to spin up a rollup.

The sequencers are TS applications which can be configured and run like a simple nodeJS applicatio