Inspiration
Traditional water contracts are an intricate and time consuming application process (Texas). They are regulated and approved by a number of agencies (Eg. TCEQ, LCRA, TWDB...) that work interoperably to complete the task. A standard applicant must provide one original and six copies of the application and supporting materials so that the various agencies can coordinate.
What it does
H2Owners aims to streamline the application process for users, while also creating a frame work of interoperability for the regulatory agencies. We also aim to use Chainlink products to automate various functions of the Water contracts, using trigger-based automation with dynamic NFT's. This also includes other concept such as external adapter weather conditions being used within automation functions. CCIP is an ideal solution when there are multiple regulatory bodies involved who would need to have their own databases and stacks for their specific needs that go beyond water rights to aspects such as environmental regulation.
How we built it
I developed the concept in a Next.js/typescript app, with a traditional supabase db. From the App, the user authenticates with their web3 account and then has access to the owners page where they can submit their application data to the database and mint their initial NFT, in an unapproved state.
Challenges we ran into
I wasn't able to get testnet Avax / Avax-Link from any faucets, and had trouble with the final deployment of CCIP NFT. Was also experience issue with ENS resolve error during the final mint process. My team began as 3, but due to a lack of communication and work produce coming into the final week, I was forced into the decision to take on the whole project, which wasn't originally scoped for one person. This was a significant complication of course, but I was committed and it worked out well.
Accomplishments that we're proud of
I was able to complete the MVP to a point that shows the concept, and devoted significant time while working 45hr weeks throughout the duration of the hackathon, a difficult task that I am proud of. Using these bleeding edge technologies can be a difficult and time consuming to understand at points, but every time I do one of these hackathons I can tell my knowledge increases significantly, so I appreciate that for what it is and am happy to be a part of ChainLINK.
What we learned
I learned a lot about CCIP, dynamic NFT's, and also the intricacies of web3 auth and traditional database auth integrations.
What's next for H2Owners - Smart Water Contracts
I would like to improve and expand the number of smart contracts to cover the different types of permits and custom triggers that could be implemented. In reality the permitting process is quite complex and how a person applies would need to be improved upon. I think that this project would be well fitted for an Avax subnet, different agencies could develop their own dapps and be able to interact with the help of CCIP.
Built With
- accuweather
- avaxfuji
- chainlink
- ethsepolia
- mapbox
- nextjs
- openweather-(link-external-adapter)-data-sources:-tceq
- picket
- pinata/ipfs
- polygonmumbai
- quicknode/infura
- react
- supabase
- twdb
- typescript
Log in or sign up for Devpost to join the conversation.