# Scaleswap Layer 2 Implementation

As of Spring 2021, the most logical way of building a layer 2 Ethereum solution for us was Polygon. We liked their solution-agnostic approach. Currently, we use Polygon’s [Plasma PoS Bridge](https://docs.matic.network/docs/develop/ethereum-matic/pos/getting-started/) (ok ok, that’s still from the “Matic times,” to be exact). It’s a sidechain, which is basically “*an independent EVM-compatible blockchain which runs in parallel to mainnet*” \[[Joshua](/scaleswap/list-of/references.md)].

However, where are the guarantees that say, in 10 years, Plasma PoS won’t reach the “motherland’s” Ethereum scale with gas fees adjusting as well? There is none. Nevertheless, the economics of Polygon’s Plasma PoS \[[Mittal](/scaleswap/list-of/references.md)] limits the number of validator nodes, offering instead the increasing [amount of transactions](https://research.binance.com/en/projects/matic-network) (and this is true as of May 2021). Therefore, instead of raising the transaction fees, validators are incentivized to keep the transaction growth trend.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://scaleswap.gitbook.io/scaleswap/layer-2-forget-that-expensive-gas/scaleswap-layer-2-implementation.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.