Scaling Clovers Network


I usually describe Clovers to non-crypto people as a kind of scavenger hunt game. Players search for Clovers in a Garden and with help from a Pig. Rare Clovers have payouts in Clover Coin which can be exchanged for Ether. Players can also search for Clovers that have fun or interesting shapes, like cloud watchers looking for recognizable images in the sky. To more crypto-native people it might make more sense to say that it’s a proof-of-work game where the hashing algorithm is replaced by generative images, the solution is an NFT and the block reward is a bonding-curve ERC-20.

A video about Clovers can be found here:

Some podcasts about Clovers can be found here:


Clovers has been an exercise in reducing gas costs and improving the user experience for decentralized apps. We’ve implemented improvements on the level of code efficiencies (link), using Oracles in multiple ways (link), counterfactual verification (link) as well as signed messages (link). Now we’re excited to utilize PoA/xDAI as a side chain to offload some of the computational expenses which are at an all time high on Ethereum. Furthermore we’re excited to implement meta transactions and a burnerwallet-like architecture to add support for users who have never owned crypto or used a wallet before. The Arbitrary Message Bridge is an essential element in this user flow as Ethereum is still the primary location for NFT activity. We plan to take advantage of the ability to tightly integrate our code on both chains.


We welcome feedback and comments on any level but especially in a technical capacity. The conversation in the post dedicated to the Arbitrary Message Bridge (link) has been especially helpful and we look forward to further communication with regard to meta-transactions on PoA.