Skip to main content

Polygon

Let's start with a quick overview of Polygon, and then we will continue with comparing Polygon to Chromia and also discuss the benefits and challenges with the two solutions.

Polygon​

Tech and Architecture

  • Polygon, formerly known as Matic Network, is a platform that provides a suite of solutions for scaling Ethereum. It aims to address the challenges of Ethereum, such as its high transaction fees and low throughput, by providing various scaling options. Polygon's core component is Polygon SDK, a modular, flexible framework that supports building multiple types of applications.
  • Polygon's architecture consists of three main layers:
    • The Ethereum Layer: This layer is the foundation of Polygon and is responsible for securing transactions and maintaining the state of the network.
    • The Bor Layer: This layer processes transactions and produces blocks.
    • The Heimdall Layer: Handles consensus and validator coordination, overseeing block production in the Bor layer and managing checkpointing to the Ethereum main chain.

Scalability

  • Polygon employs a hybrid scaling approach, combining sidechains, ZK-Rollups, and optimistic rollups to achieve exceptional scalability.
  • Sidechains offload transactions, ZK-Rollups compress data, and optimistic rollups provide flexibility.
  • These techniques enables Polygon to handle massive transactions while maintaining cost-effectiveness and security.

Development tools

  • Developers on Polygon have the flexibility to use various programming languages, including Solidity, the primary language for Ethereum smart contracts. This compatibility allows Ethereum developers to port their applications to Polygon easily.
  • Polygon provides various development tools, including its software development kit (SDK), to make the creation of decentralized applications (dapps) simpler.
  • With a focus on Ethereum compatibility, developers can leverage existing Ethereum tools and libraries when building on Polygon.
  • Polygon offers libraries like Web3.js, Ethers.js, Alchemy, and InfStones, as well as extensive documentation, tutorials, and community forums to support developers.

Fee structure

  • Polygon dynamically adjusts transaction fees based on network congestion, ensuring affordability during low activity and discouraging excessive volume during peaks. This approach balances cost-effectiveness with network efficiency.

Comparison​

Development​

Polygon

  • Solidity is the primary programming language for Polygon development, as it is the native language of the Ethereum Virtual Machine (EVM). Solidity's familiarity and compatibility with Ethereum tools and resources make it a popular choice for Polygon developers.
  • Polygon offers a comprehensive suite of development tools and frameworks, including:
    • Polygon Chain Development Kit (CDK), a framework for building Ethereum Layer 2s using ZK technology.
    • Polygon Edge, a framework for developing private and permissioned blockchains.
    • Polygon ID, a decentralized identity solution.

Chromia

  • Chromia uses Rell, a relational blockchain programming language. Rell can be a more user-friendly language than Go or Rust, making it easier for developers to build dapps on Chromia.
  • Development on Chromia using Rell is very similar to Web2 development. For more insights on this, check out our guide here.
  • Chromia provides tools and libraries to simplify authentication, transaction signing, and asset management, and new features are added to support rapid dapp development.
  • Chromia's development environment has support for testing using its own test framework and simple deployment using developer-friendly tools.

Scalability​

Polygon

  • Polygon tackles Ethereum's scalability issues with a multi-layered architecture, combining sidechains, ZK-Rollups, and optimistic rollups. Each technology plays a specific role in boosting transaction throughput and reducing network congestion, enabling Polygon to support to a wide range of use cases and transaction volumes.
  • Sidechains are parallel blockchains linked to the Ethereum mainnet, offloading transactions and easing congestion.
  • ZK-Rollups use special cryptographic methods to combine many transactions into one compact proof. This cryptographic compression allows for the efficient submission of transactions to the Ethereum mainnet.
  • Polygon has an advanced architecture with many components. You can read more here.

Chromia

  • Chromia's approach is that every dapp on Chromia operates on a unique subchain. Each subchain can handle hundreds of transactions every second. If a dapp witnesses growth, it can with ease be expanded by adding more chains. This structure guarantees sustained high throughput and a predictable way of scaling your dapp, much like in a traditional cloud environment.

    Since every subchain is isolated from other subchains, this means that they can process transactions in parallel, in essence scaling horizontally and only your app architecture sets the limit for scalability.

    Chromias sidechain architecture is built into the platform, making it a low effort for developers to utilize this approach of side chains.

Operational Costs & Fees​

Polygon

  • Polygon has a flexible fee model that changes transaction costs depending on how busy the network is. This makes transactions affordable when the network is not busy and helps avoid too much traffic when it's busy. The fees are made up of:
    • Base Fee: This fee changes with network traffic. It goes up when the network is congested and down when it's not very busy.
    • Priority Fee (Tip): Users can pay an extra fee to get their transactions processed faster.
    • Transaction Complexity: Transactions that are more complex and use more computer power, like those with smart contracts, cost more.
    • Market Conditions: The price of MATIC also affects fees. Higher demand for MATIC can lead to higher fees.

Chromia

  • Chromia changes the game by allowing developers to host their decentralized app (dapp) in a container for a fixed, predictable fee.
  • This transparency means developers know how much their operational costs are each month, and they can create their end-user fee structures to cover these operating expenses. So, instead of being charged gas fees for every action, there's a single, more manageable cost to work with.
  • As a Chromia dapp grows in usage, the developer of the dapp can increase the resources of their container. It is very similar to how you manage resources in a Cloud environment.

Revenue models​

Polygon

  • On Polygon revenues are generated through transaction fees. These fees are paid by users when they execute transactions on the network.
  • Polygon offers other revenue-generating opportunities for developers, such as subscription fees, advertising, in-app purchases, and tokenization. These can be built into the dapp, but the end-user will always have to pay a transaction fee on top of the revenue-model choosen.

Chromia

  • Operational costs of dapps are fixed and predictable on Chromia; The dapp developer can choose which fee model they want to use for their end-users.
  • With Chromia, you are not locked in by transactions and gas fees. For your dapp, you can have a monthly subscription fee, charge for single features, or, if you want, per transaction. This opens up a more user-friendly experience since you can even let the user start for free and then open up for revenues later when the user has found the value of your dapp. This is a common practice in traditional web applications, and it should be no different for Web3.

Conclusion and comparison summary to Chromia​

Polygon and Chromia are well-architectured to handle common issues with traditional blockchain platforms.

Let's summarize and discuss the benefits and challenges.

Architecture​

Polygon features a multi-layered architecture with sidechains, ZK-Rollups, and optimistic rollups. This approach enables Polygon to achieve exceptional scalability, surpassing the limitations of Ethereum and positioning it as a viable solution for large-scale blockchain applications. However, the complexity of this architecture may pose challenges for new developers.

In contrast, Chromia stands out for its simplicity, accessibility, and decentralization. Chromia's consensus mechanism uses Proof of Authority, and becoming a Provider doesn't have Polygon's high hardware requirements, making the number of Providers higher on Chromia and more decentralized.

Chromia uses Rell, a relational blockchain programming language, deliberately similar to modern programming languages like JavaScript and Kotlin. This makes it a comfortable platform for developers and allows a broader range of developers to create dapps without the steep learning curve associated with more complex languages like Solidity, which is used in Polygon.

Scalability Considerations​

Polygon overcomes Ethereum's scalability limitations through a multi-layered architecture that combines sidechains, ZK-Rollups, and optimistic rollups. This approach enables Polygon to process massive transactions efficiently while maintaining low fees and fast confirmation times.

Sidechains are parallel blockchains connected to the Ethereum mainnet, offloading transactions and reducing congestion. ZK-Rollups compress multiple transactions into a single proof for efficient submission to the Ethereum mainnet. Optimistic rollups provide flexibility and reduce computational overhead.

Polygon's multi-layered architecture and integration of multiple scaling technologies can be complex for new developers to understand and implement. This complexity may hinder the adoption of Polygon by a broader range of developers.

Chromia, on the other hand, offers a straightforward scalability solution. Each dapp operates on its own subchain, capable of handling high transaction volumes.

Scalability can be easily managed through resource adjustments, which is very close to cloud services—making the development and resource management effort more straightforward. The ability to add subchains enables parallel execution of transactions, which gives the developer complete control of scaling.

Operational costs & fees​

Polygon's dynamic fee model can lead to unpredictable developer and end-user costs. During periods of high network congestion, transaction fees can surge, making it difficult for developers to budget and for end-users to estimate transaction costs accurately. This unpredictability can make it challenging for developers to plan their revenue models and can create friction for end-users.

High fees during periods of network congestion can lead to user frustration and discourage usage. While Polygon's dynamic fee model aims to balance affordability and efficiency, it may only sometimes provide the ideal user experience, especially for price-sensitive users. Developers may hesitate to build on Polygon if they cannot accurately predict operational costs or if their fee models create friction for users.

Chromia, however, offers a fixed, predictable fee for hosting dapps. This model not only simplifies budgeting for developers but also allows them to craft unique fee structures for end-users, enhancing the user experience.

Revenue models​

Developers relying on transaction fees as their primary revenue stream may face volatility due to the dynamic nature of Polygon's fee model. Fluctuating fees can make it difficult to predict revenue and plan for the future, potentially affecting the long-term sustainability of dapps.

Chromia allows developers to choose revenue models, from subscriptions to feature-based charges or transaction fees. This flexibility makes creative revenue strategies more aligned with today's web apps.

Final words​

In summary, while Polygon enhances Ethereum's scalability and compatibility with Ethereum developers, Chromia stands out with its user- and developer-friendly approach, straightforward scalability, and innovative cost and revenue models.

These features make Chromia appealing, especially for those seeking a seamless transition from web2 into the web3 domain.