web3-DREAM11

web3-DREAM11

A platform where cricket teams and franchises can buy and sell players for their respective leagues or tournaments. The marketplace facilitates the bidding and trading process for cricket players.

The problem web3-DREAM11 solves

The rise of fantasy sports in India has been phenomenal in recent years, with millions of players participating in various fantasy sports platforms. The Indian fantasy sports market is projected to continue its upward trajectory, with more players and platforms entering the market and innovative features being introduced to attract new users. But this brings in numerous problems that exists in the current system:

  1. Data privacy: Fantasy sports platforms collect a lot of data about their users, which raises concerns over data privacy. There have been instances of data breaches in the past, which have led to the leakage of sensitive information.

  2. Insider trading: Insider trading is a major concern in fantasy sports, where employees of fantasy sports operators have access to inside information that could give them an unfair advantage in the games. This could lead to a situation where some players have an unfair advantage over others.

  3. Lack of transparency: There have been instances where fantasy sports operators have been accused of not disclosing enough information about their games, such as the rules and scoring systems. This lack of transparency makes it difficult for players to make informed decisions.

Challenges I ran into

  1. Building a Chainlink Adapter:
  • Chainlink adapters are essential components used to connect smart contracts with external data sources. Creating a Chainlink adapter requires a deep understanding of smart contract development, APIs, and the specific requirements of the external data source.
  • Debugging the adapter might be tricky, as errors or inconsistencies in the data retrieval process can have significant consequences on the smart contract's functionality and security.
  1. Using Chainlink Local Node to Fetch Data from an External API:
  • Setting up and configuring the Chainlink local node to interact with your smart contract and fetch data from an external API can be complex. It requires knowledge of blockchain infrastructure, networking, and smart contract development.
  • Synchronizing the local node with the blockchain and ensuring it stays updated can be challenging, especially if you encounter issues like syncing delays or network connectivity problems.
  1. Handling States in Your Next.js App to Properly Display Data:
  • Next.js is a popular framework for building server-side-rendered (SSR) React applications. Managing the application's state efficiently is crucial to ensure proper data display and user experience.
  • As data might be fetched asynchronously from the Chainlink adapter and the external API, handling loading, error states, and displaying the data correctly in the frontend can be challenging.
  1. Interacting Between Different Contracts:
  • When dealing with multiple smart contracts, coordinating interactions between them can be a daunting task. It requires a thorough understanding of the contract functions and their dependencies.
  • Ensuring atomicity and consistency when multiple smart contracts need to work together can be complex. You might face challenges related to transaction ordering, dependency resolution, and error handling.

Tracks Applied (3)

All Things Dev

Next.js Frontend Development: Building the frontend of our project using Next.js indicates expertise in modern frontend ...Read More

NFT, Art & Gaming

Ownership & Transferability: Users have true ownership of their selected players. They can transfer, sell, or trade thei...Read More

Blockchain & Cryptocurrencies

Our project fits into the blockchain and cryptocurrencies track by leveraging the power of blockchain technology and uti...Read More

Discussion