# Devnet wallet and rewards ## Current blockchain status Wingbits project is on Mainnet on the Solana blockchain.\ \ All rewards that were distributed on devnet were test tokens with zero value. All beta rewards are being redistributed on Mainnet, as explained below. ## Current Wingbits rewards claiming * Tokens claimed using the Wingbits dashboard claim functionality are distributed on mainnet cluster. * Token does not need to be added to the wallet prior to claiming. * New stations will not have a claimable balance until the rewards engine runs after midnight UTC the day the station starts contributing data. * Initial "owner" wallet additions will not show a claimable balance until after the next nightly rewards calculation. ## Mainnet transition Wingbits now runs all live token functionality on Mainnet only and devnet tokens are abandoned. This does not mean any previously rewarded tokens are lost. Instead, they are being distributed again on Mainnet under the schedule below. Think of devnet as a trial run with test tokens. You can see your account/rewards transition details if you are logged in by going to your [Beta Rewards Journey](https://wingbits.com/dashboard/tge) page. The concepts on that page are explained in more detail below as well. ## Beta (retroactive) rewards and potential bonus Seven days before Mainnet launched, we took a snapshot of all rewards earned on your account. These are referred to as "beta rewards." They include rewards from all stations under your account from the beginning of your participation, even if a station was later deleted. These are being reissued as claimable rewards on Mainnet at a 1:1 ratio over 365 days. All beta rewards receive a 20% bonus if you maintain at least one station online daily that generated rewards for the prior day. ### Day 1 mainnet unlock 5% of your total beta rewards were unlocked in a lump sum immediately after TGE launch and are claimable to your wallet. This 5% also includes a 1.2x multiplier so all beta rewards can benefit from the bonus. ### Days 1-365 of mainnet Remaining 95% of your total beta rewards will be claimable evenly over 365 days. For that your account will be checked for at least one online (generated rewards) station the previous day. * If a station was online the previous day, your beta rewards for the day will be multiplied by 1.2. * If no station was found to be online during the previous day, you will get the beta rewards without the bonus. #### Example: You earned 10,000 tokens before Mainnet... * Week 1 (mainnet): 600 tokens unlocked immediately (5% base = 500 tokens + 20% bonus = 100 tokens) * Days 1-365: 9,500 tokens claimable over 12 months (\~26 tokens/day) * Station online: \~26 tokens x 1.2 = \~31.23 tokens, * Station offline: \~26 tokens {% hint style="info" %} We may implement a station quality factor check, during the first 365 days of mainnet, which must be passed to qualify for the bonus to daily beta rewards. {% endhint %} ## **Why are my rewards called "beta" rewards and not "alpha" rewards?** We call them "beta" rewards because Wingbits entered its Beta phase in November 2023, and during that phase is when our current rewards system started. Even though some of you joined during our Alpha phase (June-November 2023), everyone now earns rewards under the system we launched during beta phase. That's why all rewards in your dashboard show as "beta" - it's just the name of our current rewards program. Don't worry - this is just a label. It doesn't change how much you earn or affect your retroactive rewards now that we're on Mainnet. Whether you joined in Alpha or Beta, all your data is being tracked and you'll be rewarded for everything you've contributed. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.wingbits.com/tge-mainnet/devnet-wallet-and-rewards.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.