March 25th, 2026
We're migrating client data from json to a new encoding type called beast, which will reduce data transmission usage by approximately 30–50% in most cases. This will be particularly helpful for those using LTE services or other limited data plans.
The same data that is being received by your station will continue to flow through but it will be encoded in a more efficient format before being sent to the servers.
For the majority of participants there is nothing to do as it will happen in the background.
Here's what this means for you, depending on your setup:
✅ No action required
Hyfix device owners: your device will be updated automatically, nothing to do on your end.
Standard BYOD installs: (as per the official install guide/script) automatically handled, no changes needed.
⚠️ Action required:
Custom BYOD Installs: read the below as this applies to you
🔧 Container setups (byod-unofficial-tools) If you're running one of the container setups listed in byod-unofficial-tools, the respective authors have already been advised of this change. Please reach out to them directly for a timeline on when the updated version will be available for you to adopt.
🛠️ Custom container or other setups If you've built your own container setup, you can reference the standard BYOD install script or any of the tools listed in byod-unofficial-tools that have already implemented the change as a guide for updating your setup. Once the change is complete the client will verify and send our system a flag that it is beast-enabled. In batches we will then switch those newly flagged stations to beast mode only.
⏰ The deadline to complete this migration is 20 April 2026. After this date, the older endpoint will be removed and stations that have not been changed over will stop sending data.
If you're unsure which category applies to you, feel free to ask in our Support Chat on the site, or in discord, and the team will help point you in the right direction.
As always, thanks for your continued support in helping grow the network! 🙌
March 25th, 2026
1.10.15 - Prepares stations for beast mode. The client will now automatically attempt to update the readsb config at startup, saving the community from having to do it manually. 3rd party docker groups have been contacted.
Statistics page now shows beast status - You can now see on your statistics page whether your station is sending beast data. This also ensures beast-only stations no longer appear as offline.
Beast rollout underway - We have started rolling out beast to more stations. Most stations in Sweden and some in Australia are already running beast. Expect further expansion soon, potentially to Europe. As always, we will keep an eye on things before pushing further.
March 25th, 2026
1.10.13 - Improved monitoring to catch Tailscale health issues and missing beast config in readsb. Added support for true beast exclusive mode, which stops the JSON data flow and sends beast only. (Mar 19th)
1.10.14 - Added more metrics and logging to help the team identify BYOD stations running via Docker, failed readsb config updates, and other issues. (Mar 20th)
March 13th, 2026
1.10.9 - Sending additional metrics/logging. Tailscale client update. Tailscale re-auth bug squashed. Added Tailscale info to the local station's :8088 dashboard. (Mar 12th)
1.10.10 - Change in logging to help support and dev teams find information faster when investigating an issue. (Mar 13th)
GPS Accuracy on map - Some refer to this as GPS jamming. You can select it on the map toolbar and a popup will also show with more information on what this really represents.
Claimable/claimed reset (kinda) - In order to make a change to our ledger system, the ledger had to be emptied. This means the claimed went to 0. Instead of having 0 in claimable again and having a lot of support tickets opened, it was populated with your beta rewards balance at that moment. Please remember that claimed/claimable mean nothing until TGE and will reset to zeros then.
LAR fixes - We have now implemented the 7 day grace period for Low Altitude Rewards (LAR). A bug was also resolved where the most recent day's LAR were not showing for everyone in the Ledger or Reward Details data on the "Rewards & Wallets" page.
March 3rd, 2026
1.10.8 - Cleanup version with some minor upcoming change preparations (1.10.7 fell on the floor and was accidentally vacuumed up, never went out... or maybe we accidentally skipped a version number).
Account based Hosts - A host with their own account can now see station details for the station(s) they host. They can also see the planes the station is currently seeing and the rewards the station is collecting. Obviously, they can control when they claim their portion of rewards. We are looking to add even more transparency in the future, such as hosts getting alerts to a station being offline. If you have a host, we strongly encourage them to have their own account... not only for control on claiming but also so they can be more involved in the project.
Reward Breakdown/Earnings page - this has been removed and replaced by the next item
REWARDS & WALLETS page - The wallets page has a new name and been enhanced to include an Earnings overview, a Ledger section to show all transactions, and a Rewards Details section. All this together replaces and improves upon what previously existed on the above mentioned page. In the claim section we also added a "View Details ->" button to help you find this new location/page.
TGE rewards page - We have updated to fix some visual and calc issues. We have also added a csv download link on the page so you can grab an export of all the historical data. One known issue is that if you switch between accounts the page may cache data from the first account you used. You can SHIFT+CTRL+R to clear the cache and reload in order to stop this. We are working on a fix as well.
Rewards Charts - Both on the main dashboard page (Overview) and the individual station pages, we have been fixing minor issues such as the dates on the X axis being easier to read, clearer messaging on when rewards are calculated if you just onboarded, and other visual issues that were not behaving as expected.
Expired hex cleanup - Something had broken and the automated cleanup of expired hexes (from previous reservations or 100+ day offline stations) was not cleaning up. This has been resolved and the hex cleanup train is back on the tracks and going full steam ahead.
Pending value fix - The pending value on the Overview page was only showing/reflecting 6 days of rewards from the grace period and not 7 days. This has been resolved. Keep in mind that LAR are currently not subject to the grace period, but will be soon, so if you have any low altitude rewards the Pending value won't match your 7 day total.
The reservation system has been fully migrated now with existing reservations being ported over to the new flow. Reservations will no longer have hosts as they are not stations yet. IMPORTANT NOTE: If you had an existing reservation with host info setup, it was cleared and you will need to set that up again after you onboard the station.
February 23rd, 2026
During a recent TGE prep initiative, your All rewards on the chart (and a newly added Total Rewards Earned on the Overview page) showed inflated values. You probably also noticed that Beta rewards were showing on your chart while we tested 2 new fake TGE launch events (Jan 8th & Feb 16th) using our new ledger system. All this was to prepare the interface to show your rewards from a daily perspective for TGE/mainnet, so you would see your normal rewards and the Beta rewards (plus the 5% lump sum) being distributed on the timeline daily.
The unintended side effect of this change was that it initially showed all Beta rewards earned since March 2, 2025, and later only Beta rewards (plus lump sum) from the fake TGE launch events. This wouldn't be that much of an issue except that the chart's ALL and Total Rewards Earned values included all test distributed Beta rewards. This means that for some long term participants, their All value was initially inflated by 160%+ of their true earned rewards. The Feb 16th update did decrease those inflated values but still included the 5% (+20% bonus) lump sum and several days of beta rewards... which was misleading. We have removed these from the chart. The numbers reflected double dipping into your beta rewards, adding them first as normal rewards (Base+EPR+LAR) and then again as Beta rewards being distributed.
In our effort to be transparent with our UI changes and prep for TGE, we caused quite a bit of confusion between that and the resets of Claimable and Claimed tokens (in the Rewards panel on the Overview page). We apologize for the confusion that was created and have learned quite a bit over the last few weeks of what to show prior to TGE.
We haven't lost any of your contribution data, your total rewards earned should reflect the proper current value, and please keep in mind that devnet token claims are just for testing and only serve that purpose.
We have added a page at https://wingbits.com/dashboard/tge on the dashboard (linked under the rewards chart) to explain how your rewards will migrate from pre-TGE to post-TGE (mainnet). We did this with your specific data up to the point of an example TGE launch of Feb 9th, 2026. Obviously you will have earned more rewards between then and the real TGE, but we hope this make things more clear. At the end there is a FAQ with some common questions you may have after looking over all the stats.
3D Mode - map now has 3D mode available, allowing for visuals much cooler than before. We still have a few things to work out, but this is the initial release of the feature and we are very excited to release it to our community.
Mousing over craft now show altitude of the craft Above Mean Sea Level (AMSL).
February 12th, 2026
TGE Testing & Claiming Updates:
On Jan 8th a new testing phase for TGE preparation was started. This is basically a fake TGE date so we can test all the mechanisms like this is a real TGE. Part of that is the 5% lump sum distribution and while this is not claimable (none of the beta rewards are currently), it does now show in your rewards charts on the site. Along those lines, the remaining 95% would be distributed over 365 days and that is now also reflected on the rewards chart.
Another part of this effort is that we have migrated to a ledger system to support partial claims. This means your “Claimable” and "Total claimed" will have reset to zero. Pending will not include Beta rewards as they don't have a grace period. Claimable currently doesn’t reflect released beta rewards, although when you go to claim it will be included.
Remember, claims to Solana devnet cluster are only there for testing our systems and blockchain... those tokens have no utility. Your total on the Overview page chart, using ALL for time period, is going to be the source of truth for the post-TGE 1:1 conversion.
Client:
1.10.5 - Additional client changes to support new data transfer method, which is still only in testing phase. Previous versions since 1.10.0 would have the same description.
Site:
✨ New - Beta rewards are now visible on charts, including testing lump sum distribution, for this TGE test phase. You can click on the name in the chart legend to toggle them off/on, as you can any of the data series.
✨ New - Partial claims, including anonymous hosts (you entered host wallet instead of them setting up account and controlling their own claiming).
✨ New - Hosts can now view rewards and statistics for the station(s) they host.
🔄 Change - New reservations are now in their own area on the MY STATIONS page, existing reservations will be migrated over soon. This change is based on a restructure on the backend managing the flow of a reservation becoming an actual linked (onboarded) station.
🐛 Fixed - Rewards are now visible after daily calculation and not based on when your local time zone hits midnight for those that are in time zones earlier than UTC like PST, where they should be visible by 5pm now. UTC or later time zones should act as they did already.
🐛 Fixed - Rewards charts Y axis no longer rounding to show things like 2k twice when one should have been 1.5K
✨ New - Enabled vertical hover on rewards charts, especially useful on long time periods with very small bars. You can now just move the mouse around anywhere in the chart to see a day's tooltip.
Discord Bot:
🔄 Change - The Top 10% Performance roles given out, to eligible users who have linked, now include low altitude rewards in the calculations to determine the top 10%.
Docs:
Current docs on https://docs.wingbits.com/ do not yet reflect all these new and changed items but will be updated asap.
December 22nd, 2025
We’re excited to officially announce the launch of Low Altitude Rewards.
After completing final validation to ensure accurate altitude thresholds and fair reward distribution, Low Altitude Rewards are now active across the network. While low-altitude data has been visible in beta for some time, today (Dec 22nd) is the first day of low-altitude contributions that will be eligible for rewards.
🕛 Reward Timing
Along with other rewards, Low Altitude Rewards are calculated nightly (shortly after midnight UTC) and become visible on the site after all reward calculations are completed (within a few hours from now).
A big thank-you to everyone who participated in testing and helped validate this system along the way. Your feedback and real-world data were critical in getting this feature ready for launch.
👁️ Reviewing Rewards
At this time there will be no obvious visible component of the daily rewards charts, showing the breakdown of Base vs EPR vs Low Altitude.
Daily Low Altitude Rewards, along with data point counts, will be visible under the "Reward breakdown" button on the Dashboard's claim panel. Don't forget that you can filter to see just these by changing the Reward Type filter dropdown to "Low Altitude".
🗺️ Map Visualization
We will be implementing something in the future to help people visualize the areas that are eligible, but we didn't want to delay the release of the rewards. So for right now just picture the station sized hex that includes the airport and 6 hexes immediately surrounding it. Those are the eligible areas for airports that have an icon on the map.
📘 Documentation
For a breakdown of how Low Altitude Rewards are calculated and distributed, please refer to the documentation here:
👉 https://docs.wingbits.com/rewards/how-rewards-work#low-altitude-rewards-lar
Wingbits Team wishes you happy holidays and hope this makes up for a lack of the Santa Tracker this year!
December 18th, 2025
Client Updates (since Nov 25th):
1.8.1 - reverting library to investigate a hyfix issue, which turns out was not related
1.9.0 - Initial rollout of new functionality in prep for beta testing (it is a secret for the moment)
1.9.1 - Updates for beta testing new functionality
1.9.2 - Metrics additions for evaluating new functionality being tested
Site:
Generalize station's "Link Hyfix" button to "Link Device" as it can be used for Geosigners and potentially other hardware.
Released self-service api feature with multiple tiers, already being leveraged by many users - https://wingbits.com/pricing
Note: We didn't get the Santa tracker going this year due to other priorities... but we do have something coming that will be like a holiday present.
November 25th, 2025
Client Updates (Nov 18th - missed posting):
1.7.0 - a new local url has been made available for stations to see a TON of information about the device, including many things useful for debugging connectivity issues on your own or with support. Just go to http://<your_station_ip>:8088/ and start looking around!
Replace <your_station_ip> with the IP of the device on your network.
Client Updates (Nov 25th):
1.7.1 - Resolved being unable to use tar1090 via tailscale on @Hyfix devices and also resolved client update failure when tailscale was enabled. This was released on the 19th, including for transparency.
1.8.0 - Nothing visible, but aligning some housekeeping tasks with heartbeat timing.
Site:
Changelog link added to all Wingbits Dashboard site pages in footer, so you can review it if you aren't on discord. This also is helpful for when it pops up but you dismissed before reading.