atmofi
Secure Your Future, Whatever the Weather.
Demo
About
The problem it solves Of course. Here is a paragraph describing the problem AtmoFi solves and its value proposition, suitable for your project submission. AtmoFi addresses the significant financial risk that unpredictable weather poses to both businesses and individuals, offering a modern alternative to the slow and often opaque traditional insurance market. For businesses like agriculture, tourism, or event planning whose revenues are weather-dependent, it provides a powerful tool for hedging: a farmer can create a derivative that automatically pays out if rainfall is too low, or a ski resort can insure itself against a season with insufficient snowfall. For individuals and financial speculators, AtmoFi opens up a new, accessible market to capitalize on meteorological forecasts. What makes this process fundamentally easier and safer is its on-chain, autonomous nature. The entire agreement, from holding collateral in escrow to final payout, is governed by a transparent smart contract. By using Chainlink oracles for data and settlement triggers, AtmoFi removes the need for manual claims, adjusters, and intermediaries, replacing a subjective and lengthy process with instantaneous, trustless, and mathematically precise execution based on verifiable real-world outcomes.
How it's made
Challenges we ran into The development of AtmoFi presented a series of complex, real-world integration challenges, primarily centered on bridging off-chain services with our on-chain smart contract. Our initial goal to use a generative AI model via AWS Bedrock immediately highlighted the practical hurdles of cloud infrastructure, including navigating service availability across different AWS regions and debugging IAM permissions through CloudWatch logs. The most significant difficulties, however, arose when integrating the full suite of Chainlink services. We encountered considerable versioning conflicts within the official Chainlink contract libraries, which manifested as a cascade of file not found errors, undeclared identifier bugs, and deprecated function calls. The most difficult issue to resolve was a fundamental data type mismatch where the Chainlink VRF UI provided a uint256 subscription ID while its own smart contract interface strictly required a uint64, necessitating multiple contract refactors to finally solve. This volatility extended to the frontend, where initial attempts with various Web3 libraries led to compatibility and race condition errors, ultimately requiring a migration to the more stable wagmi and RainbowKit stack to build a reliable user interface.