July 17th, 2026
No client updates. The most recent client version remains 1.12.1.
Smoother, more reliable live map - We did a large performance pass on the live aircraft map to remove flickering, the brief freeze when clicking a plane, and a crash risk. Planes now update more smoothly as new data comes in. We also made the map more resilient when our backend is slow or briefly unavailable: it keeps the last-known planes on screen when it can, and shows a short "live data unavailable" message only when there is genuinely nothing to display (which clears itself automatically once data returns), instead of silently looking frozen.
Cleaner flight tracks (current flight only) - When you click an aircraft, the map track and the cockpit altitude profile now show just its current flight rather than stitching several separate flights together across long ground stops. Tracks and altitude graphs are much easier to read, and history loads faster.
Rebuilt flight replay - Live, historical, and collision-alert (ACAS/TCAS) replays now run on one unified engine with consistent controls and camera behavior. The camera smoothly follows the aircraft and releases when you pan or zoom. The altitude profile now shows gaps and uncertain data the same way the map does (grayed and dashed where coverage was lost) and can be expanded into a larger view. We also fixed a bug where closing a collision-alert replay left leftover info in the URL and could keep live planes hidden.
Clicking a flight now focuses the map on it - Selecting a flight anywhere in the app (for example a past departure or a live arrival from an airport's schedule list) now pans the map to that aircraft, instead of leaving you on the previous view with the plane off-screen. This also works for aircraft that have aged out of live tracking by falling back to their last-known position, and searching by hex or callsign now finds those aircraft too.
Light mode fixes - Fixed several places on the map that were still showing dark-mode styling while in light mode, which left unreadable dark boxes or low-contrast text. This covered the Reserved and Offline station info panels, the map filter chips, the aircraft info panel, and the selected-tab highlighting.
Rewards charts - The rewards chart hover popup now shows the daily total up front plus the top contributing stations, instead of a cut-off partial list, so people with many stations can actually read it. On the individual station rewards chart we also added a PageRank line, so you can see how your station's network importance tracks against its rewards over time.
Clearer reward claims & wallet ledger - Claims now show a per-station breakdown of Daily versus Beta rewards that make up the amount. The wallet ledger is ordered by timestamps, and clicking a claim amount opens a reconciliation breakdown of which stations and reward types it came from. (That breakdown is recorded at claim time, so it appears on claims made from this release onward.) Reward details also now show anonymous and account host splits correctly, and hide split percentages for Beta rewards since splits don't apply to them.
Host contract improvements - The host contract screen now shows when the contract was created, disables the update button when you haven't actually changed anything, and warns you before editing an anonymous host contract that changes take effect going forward (not retroactively).
Station notifications are now split into two independent controls: Station Offline and No Data Flow. The new No Data alert catches the case where a station is still online and sending heartbeats but has stopped producing aircraft data, so you find out about a quietly-broken station without waiting for it to go fully offline. Click on the Bell for a station on the MY STATIONS page to update the options.
May 8th, 2026
Announcing here on site instead of just in Discord server, where we run our AMAs…
Discussion about mainnet launch, new product offerings, the NFTs, buyback/burn, and other topics on participants' minds.
Hope to see everyone Wednesday May 20th, 11:00 AM EDT (3:00 PM UTC)
May 8th, 2026
1.10.25 - Improvements to NATS reconnect logic. Improved logs. (Apr 28th)
1.10.26 - Client will no longer attempt to connect to the now-shut-down legacy ingestors. (May 5th)
1.11.0 - Major cleanup of legacy code for connecting to ingestors at feed.wingbits.com and processing/sending JSON. Improved auth token retry logic when rate limited. Updated dependencies. (May 7th)
1.11.1 - FIX: Client panic happening on stations not authorized to connect for 4+ hours. FIX: Stations appearing as not connected for the first hour after restart even though data was flowing normally. (May 8th)
Legacy ingestors shut down - The legacy JSON ingestors (feed.wingbits.com) have been shut down. Stations still attempting to send JSON data or running outdated client versions will no longer be able to send data. Updating to the latest client is required.
April 30th, 2026
We’ve managed to decipher some of the strange signals that the network picked up.
It appears to be an urgent SOS for safe refuge, coming from a distant parallel universe.
A collective of 7,470 human-like species are imminently arriving. They have identified themselves as the Wingnauts, unique beings forged from static and signal by the psychedelic priest known only as Stalomir.
Captains. Navigators. Pilots. Explorers. Each one requests a beacon - a signal to be tethered too.
Will you answer their call? https://www.wingbits.com/wingnauts-omniverse
Laws of the Mint
Only active Wingbits stations can claim a Wingnaut.
Each station receives one free mint, to the current owner wallet.
Up to 3 additional mints allowed per wallet.
Each extra mint requires burning 747 unclaimed rewards.
Supply
7,470 Wingnauts exist in this First Era. This generation will never be repeated. The signal moves forward.
Rarity
There is no choosing NFTs or traits. Your allocation is based on pure cosmic luck and assigned at random.
Why wear one?
Wingnauts mark operators inside the network. Wearing one unlocks future rewards, access and status. The signal recognizes its own.
April 27th, 2026
We will get some warnings up on the site and docs, but be aware that Kraken has a 800 minimum WINGS deposit requirement (you can see this when trying to get the wallet address for receiving on their interface). This means you should not be using a Kraken wallet as your claim wallet directly unless you ensure every claim to a Kraken based wallet is over 800 rewards. The tokens will just disappear. Kraken will not provide support for recovery. Wingbits cannot help in this case either.
It is always a good idea in crypto to only send to wallets you completely control. From there you can make decisions on what to do with the tokens you hold. Remember, not your keys... not your wallet.
April 27th, 2026
1.10.22 - Improvements to logs and metrics. Remote config improvements. Auto-updater self cleanup. (Apr 23rd)
1.10.24 - NATS stability and observability improvements. Client self-update improvements to avoid getting stuck in an update state. (Note: v1.10.23 was built but never deployed to any station -- v1.10.24 carries the same changes.) (Apr 27th)
April 27th, 2026
1.10.16 - Added logs for easier debugging on missed heartbeats or config fetches. Failed certificate issuing requests now log the reason, including "no fresh heartbeat sent", so it's clearer why a data connection can't be established. Tailscale config fix so it doesn't lose state at restarts such as client version upgrades (please report if tailscale issues continue). (Mar 27th)
1.10.17 - Show beast stats instead of JSON on the :8088 dashboard when beast is enabled. Fixed an issue where some invalid config could cause the beast port to not be open, which should make more stations eligible for beast. (Apr 1st)
1.10.18 - Added support for sending BEAST data directly to NATS, bypassing legacy infrastructure. Attempted fix for a port conflict by closing the BEAST listener explicitly on shutdown. (Apr 16th)
1.10.19 - Beast first! Stations now start up in beast mode. If readsb isn't configured for beast but JSON is functioning, the station will fall back to sending JSON after a 90s grace period. The client will continue to monitor the beast connection and, once data is flowing on the beast port (30015), it will automatically switch to Beast mode and stay there. An extra heartbeat is sent once NATS Direct Connect is connected to signal a successful connection and limit early off-line status. The Station diagnostics page also has an added connectivity test toward the NATS Direct Connect endpoint (along with BYOD wingbits status command). (Apr 16th)
1.10.20 - Attempting to fix clients connecting directly with expired tokens by NTP compensating the clock so expiry calculation is more accurate. (Apr 17th)
TGE rewards page - Now shows data from the actual beta reward tables, and the language has been updated to reflect that it is final.
Dashboard graph cache - The cache on the Overview dashboard graph is now one hour instead of resetting at midnight each day. This should help reduce some of the confusion around when the graph updates.
Heartbeat requirement tightened - In addition to the existing checks (heartbeat count, satellite count, and geolocation within the station's hex), stations must now have sent a recent heartbeat for us to accept their data and award rewards. We're starting with a requirement of at least one heartbeat in the last 2 hours. Heartbeats are crucial for our processing of beast frames and for being able to review the state of the station fleet, so this change makes it more apparent when a station isn't reporting in.
BEAST data direct to NATS (rollout) - We have started gradually rolling out the new path where BEAST data goes directly to NATS, bypassing legacy infrastructure. Station owners shouldn't really notice much. The main observable change is that data is now going to ingest.wingbits.com instead of feed.wingbits.com.
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)