# 9. Technical Considerations

## Blockchain (Polygon Network)

300FIT was initially developed as an ERC20, but switched its mainnet to the Polygon network on November 20, 2023 to build a web3 sports league ecosystem. Polygon Chain has established itself as a multi-chain powerhouse that provides developers and creators with the tools they need to build innovative, secure, and scalable blockchain solutions.

Polygon Chain supports the most popular Ethereum scaling ecosystem, providing EVM compatibility and the ultimate user experience with fast transactions at near-zero gas fees.

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

Polygon Chains provide the best scaling experience for developers and users.

1. &#x20;Low cost\
   \
   Scale your project by processing more transactions.\
   Spend \~$0.015 per transaction on average powered by Polygon's Proof of Stake architectureApproximately 10,000x lower cost per transaction than Ethereum<br>
2. Community support\
   \
   An active and engaged developer community\
   24/7 development support\
   Extensive developer documentation to make it easier to build<br>
3. EVM compatible\
   \
   Easily Deploy on Ethereum for Faster Development\
   Compatible with Ethereum developer tools<br>

Polygon is an enterprise-ready blockchain platform that has emerged as a solution available to a growing number of business and development teams. With its scalable architecture, fast and cheap transactions, and growing ecosystem, Polygon is an ideal platform for entrepreneurs, developers, and enterprises alike to build and launch blockchain solutions.


---

# 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://300fit.gitbook.io/300fit-white-paper/english/9.-technical-considerations.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.