Chronix
predict. profit. plant the future.
Demo
About
The problem it solves  # Chronix.Bet — Problem Solved _**predict.profit.plant the future**_ Chronix.Bet is a next-generation BTC prediction platform, designed to be user-focused, trustless, and climate-positive. Here’s how it addresses the real issues found in other web3 betting apps: --- ## **What Problems Does Chronix.Bet Solve?** ##### **1. Eliminates Repetitive Wallet Signing** _Most web3 betting platforms require users to sign every transaction, slowing down the experience._ - **Chronix.Bet** introduces a vault system: deposit once, then place bets without repeated wallet pop-ups to settle bet or getting back the winning price to the vault. - _Result: A seamless, frictionless betting experience._ ### **2. Removes Centralized, Untrustworthy Settlement** _Many platforms depend on centralized servers or manual processes, risking manipulation or downtime._ - **Chronix.Bet** automates every step—bet placement, settlement, and reward distribution—using Chainlink’s decentralized Automation and Data Streams. - _Result: Outcomes are trustless, tamper-proof, and fully on-chain._ ### **3. Ensures Transparent and Fair Results** - **Chainlink’s decentralized oracles** fetch real-time BTC/USD prices and trigger on-chain settlements. - _No human intervention, no single point of failure._ ### **4. Saves User Time** - **Bets resolve in a fixed 5-minute window.** - _Users don’t need to monitor the screen for long—just place a bet and return later._ ### **5. Adds Real-World Impact** - **A portion of winnings is automatically used to mint on-chain carbon credits.** - _Every win has a positive climate impact—something traditional platforms lack._ --- ## **Why Chronix.Bet is Unique (with Chainlink)** | Feature | **Chronix.Bet (with Chainlink)** | **Typical Web3 Betting App** | |----------------------------|--------------------------------------------|-------------------------------| | _Wallet Signing_ | Deposit and place bet once, no repeated pop-ups | Sign every action (bet settle/price claim) | | _Settlement_ | Fully automated, decentralized | Often manual or centralized | | _Data Integrity_ | Chainlink Data Streams (tamper-proof) | Centralized oracles/feeds | | _User Time Commitment_ | 5-minute rounds, minimal attention | Longer, less predictable | | _Transparency_ | On-chain, verifiable, trustless | Opaque, sometimes off-chain | | _Real-World Benefit_ | Carbon credits minted automatically | No external impact | --- ## **Technical Summary** **Chain**:AVAX (Avalanche Fuiji ) | **Chainlink Service** | **Usage in Chronix.bet** | |-----------------------------|----------------------------------------------------------------------------| | **Data Streams** | Provides real-time BTC/USD price for accurate prediction verification using DON | | **Functions** | Fetches real-time BTC/USD price form data streams api | | **Custom Logic Automation** | Triggers bet settlement in the contract | | **Time-Based Automation** | Schedules weekly lottery execution | | **VRF** | Selects lottery winners randomly and fairly | | **Price Feeds** | Fetches AVAX/USD and EMCH/USD prices to support deposits & carbon minting | ### **Smart Contracts Deployed** | **Contract** | **Address** | |---------------------|-----------------------------------------------------| | Vault | `0x622D987944c305b7e60A1C8D4ca6378617F8Ba2D` | | Carbon Credit | `0x3142A16a630a26bb4c7eC9ac175e9E4B418108A9` | | Betting | `0x4d2Fb695465c8fbbCFb2b9E424093BBdFC4E612B` | | Lottery | `0x75468b135Ba893fc1B7aD735349a1697f93950C9` | --- ## **Summary** _Chronix.Bet makes crypto prediction betting easier, safer, and more user-friendly by:_ - _Eliminating repetitive actions_ - _Ensuring trustless automation through Chainlink_ - _Adding climate-positive rewards_ - _Allowing users to participate in quick, 5-minute rounds without unnecessary screen time or risk of manipulation_
How it's made
Challenges we ran into While building **Chronix.Bet**, we encountered several technical and integration hurdles. Below are some of the key issues we faced and how we approached solving them: - **CCIP Integration Issues** We initially planned to use Chainlink CCIP for token transfers across supported chains. However, even with the official example contracts, we ran into deployment and configuration issues. Additionally, on the Avalanche Fuji testnet, token exchange support was very limited — with only a few tokens available — which made realistic token-swapping tests almost impossible. - **Data Streams API Key Access Delay** We were excited to integrate Chainlink Data Streams due to their real-time, low-latency capabilities. However, we soon learned that access to Data Streams requires coordination with the Chainlink team to obtain API keys. The approval and setup process took nearly a week. If there had been a quicker way to self-serve or request testnet credentials, it would have saved us significant development time. - **Chainlink VRF Subscription ID Format** With Chainlink VRF, we only faced one major issue — the new version of the VRF subscription ID is a much larger number. This caused compatibility issues during contract deployment as certain toolchains and libraries didn’t accept large integers in the expected format. We resolved this by adjusting how the ID was passed and encoded in our deployment scripts.