top of page

Cros: Crossing out Problems and Mitigating Ethereum’s Incessant Nuisances

Gas fees, slow speeds are just two of the key pain points on Ethereum’s blockchain that plague users on a daily basis. The good news is that these are all things that Cros is here to solve.

Ethereum’s upgrade, the “London Fork” launched back in August and was meant to alleviate the problems that keep accumulating on the blockchain, congesting the network, making it slower, and skyrocketing those transaction fees to the roof. However, four months later, the problem still persists - and is even encouraging regulators to breathe down DeFi’s neck.

The team behind Cros watched these tides rise, and knew that they had a fix with Cros - a brand new layer 2 protocol for MetaVerses, DeFi protocols, Gaming Platforms, dApps, and DAOs to collaborate with each other, and to ease out the scalability issues piled up on the Ethereum blockchain.

Cros combines the best of Ethereum and sovereign blockchains into a pioneering cross-org system. Cros solves pain points associated with blockchains - which in short means no more ludicrous fees and ebbing slow speeds - and this is all done without sacrificing on decentralization, and therefore security.

A scalable transaction layer infrastructure is designed to allow Cros to pay transaction gas fees on behalf of the user. That is in return for a monthly subscription fee in the form of fiat or stable tokens. Being also a scaling solution for Ethereum, Cros chose Polygon to be its playground to facilitate functionalities like checkpointing, consensus, layer 2 scaling, dispute resolution mechanism and interoperability with other chains.

The main vision bringing colour to Cros’ roadmap is building cross-org layer 2 scaling solutions, and so interoperability across different blockchain networks is a key area of focus in Cros’ roadmap. As any other design component, blockchain is just a design tool and with the right mix of side chains, rollups and other techniques, there will always be a solution for any scalability issues.

bottom of page