> For the complete documentation index, see [llms.txt](https://selfient.gitbook.io/selfient-lite-paper-public-beta-launch/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://selfient.gitbook.io/selfient-lite-paper-public-beta-launch/selfient-on-polygon.md).

# Selfient on Polygon:

<figure><img src="/files/DjnjQrwiNvqq7QXANJzq" alt="" width="375"><figcaption></figcaption></figure>

### **1. EVM Compatibility:**&#x20;

* Selfient has chosen to remain within the Ethereum ecosystem rather than opting for an alternative Layer 1 (L1) network like Solana. This decision is rooted in our confidence in the reliability, performance, and security provided by Polygon, particularly as an Ethereum Layer 2 (L2) solution.&#x20;

### **2. Network Speed:**&#x20;

* Polygon PoS offers impressive transaction speeds, reaching up to 65,000 Transactions Per Second (TPS). This surpasses the transaction capabilities of Ethereum as a Layer 1 solution (approximately 15 TPS), Arbitrum (around 40,000 TPS), and Optimism (roughly 2,000 TPS) as Layer 2 solutions. The higher speed facilitates faster contract execution on the Polygon PoS network compared to its counterparts.

<figure><img src="/files/J6Sz7WmFrafzbEVUmVYh" alt=""><figcaption></figcaption></figure>

### **3. User Costs and Gas Fees on Polygon vs. Ethereum:**&#x20;

* User costs associated with interacting with a contract on Polygon are remarkably affordable compared to the Ethereum Main Network. Expenses for contract interactions on Polygon can range from a few cents to a few dollars. Lowering these costs has been a pivotal effort for Selfient, enabling users to focus directly on maximizing profits and minimizing gas expenses.

### **4. Layer 2 Market Activity:**&#x20;

* **Monthly Transactions:** (Graphs depicting network data highlight Polygon's significant advantage over Optimism and Arbitrum in terms of Monthly Transactions. This results in approximately 2 to 6 times more transactions than Arbitrum and roughly 4 to 13 times more transactions than Optimism in the year 2023.)

<figure><img src="/files/PnRNyghL9Uj8UM7po8uV" alt="" width="375"><figcaption></figcaption></figure>

* **Monthly Active Wallets:** (Graphs illustrating network data emphasize Polygon's substantial advantage over Optimism and Arbitrum in terms of Monthly Active Wallets. This translates to approximately 2 to 8 times more active wallets than Arbitrum and roughly 3 to 9 times more than Optimism in the year 2023.)

<figure><img src="/files/2xfU9kc3wKb70ol6JVSd" alt="" width="375"><figcaption></figcaption></figure>

### **5. Ecosystem Strength:**&#x20;

* Polygon boasts a robust ecosystem with approximately [53,000 dApps developed on their network](https://dailycoin.com/polygon-matic-witnesses-an-eightfold-increase-in-dapps-since-january/) as of June 2022. We are proud to be in esteemed company alongside prominent names such as Uniswap, OpenSea, Rainbow Wallet, Galaxe, Lens Protocol, and numerous other dApps seamlessly integrated with Polygon.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://selfient.gitbook.io/selfient-lite-paper-public-beta-launch/selfient-on-polygon.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
