Automating cancellation and completion of pools

• We wanted a way to automate the process of pool cancellation and rewards distribution because otherwise we would have to monitor each pool and do a transaction manually every time.
• First, we thought of a backend that constantly keeps track of the pools and executes transactions when needed. But this would make the platform partially centralized.
• Also, if the backend was inactive due to some reason, the pools wouldn't end on time and as the scores of the users depend on prices at the end time, it would result in incorrect winners.
• This was when we found out about the hyper-reliable ChainLink Keeper network and how if we make our contract keeper compatible, the keeper network would do the automation for us.
• It required a lot of brainstorming to adapt the contract to make it function as intended.

Querying blockchain data efficiently

• Initially, we used web3 functions to fetch the list of pools and the data for each pool. But as the number of pools started to increase, there was a large increase in the loading time as well. This would be unpleasant for the end-user. So we researched ways to fetch blockchain data.
• The Graph protocol seemed to provide exactly what we needed and after a few tries, we were able to build our very own subgraph for the contract.
• Fetching data using GraphQl queries from the indexed subgraph data dramatically reduced the loading time and allowed us to easily filter data as well.

Building a notification system

• We wanted to improve user experience and create a notification system that updates active users about platform events.
• We got to know that we use WSS providers to listen for events and then added listeners in the frontend to implement it.