What's new in HoneyGate — every feature, improvement, and fix in plain English.
HoneyGate now acknowledges quiz answer buttons immediately while it finishes saving the result. Players should no longer see Discord's ‘This interaction failed’ message after submitting an answer.
No prices, balances, rewards, permissions, or server settings changed.
HoneyGate now retries brief connection failures before reporting a service-check problem. If a page cannot be fully loaded, the check reports a connection problem instead of incorrectly claiming the page content is broken.
Checks in our testing environment are also clearly labelled, helping us distinguish test warnings from live-service problems.
This maintenance update changes monitoring only. Your server features, pricing and balances are unchanged.
Servers with a spending limit can keep all gates enabled while controlling routine usage. Priority checks receive reserved capacity. When capacity runs out, checks wait and resume automatically, preserving existing roles.
Manual refreshes, new verifications and wallet-change notifications now check the member’s linked wallets directly. They no longer wait for every gated collection to finish scanning. Large checks save their progress and resume before untouched checks in the same queue lane, while other servers still get turns.
Routine background checks now run daily. Background collection scans are used when completed measurements show a saving and the scan is small enough. Recent complete results are reused across role rules.
The portal shows the original confirmation date and next routine check time, including after older holdings details are cleared. Manual requests and supported wallet-change notifications still receive priority. If a notification is missed, the daily check may be what catches it.
Incomplete or outdated evidence cannot grant or remove roles. Provider limits still pause requests, and successful individual pages do not establish full recovery.
HoneyGate now follows the holdings provider's retry instructions and resumes temporary throttles with gradually longer pauses. Rate-limit errors returned inside an otherwise successful response are handled correctly.
Waiting requests keep usable saved batches without accumulating wallet failure penalties. The Holdings checks page shows when it is waiting for the provider, and existing roles stay protected until a complete check succeeds.
Provider warnings now distinguish temporary throttling, reported usage limits and unknown limits. A rejection alone no longer becomes a claim that credits are exhausted.
HoneyGate now checks NFT holdings in small batches and saves completed pages between runs. When a check is interrupted, it can continue from the next asset instead of fetching the same successful pages again.
Completed collection checks are reused across members in the same server. The Holdings checks page shows when a check is continuing in batches.
Roles and confirmation times update only after the full required check finishes. Saved work expires or restarts when newer ownership information makes it outdated.
HoneyGate could report that Helius checks had recovered after one successful page, even when a later page failed. Recovery now waits for completed holdings refreshes at least fifteen minutes apart without another recorded provider rejection.
A successful page alone no longer triggers a recovery notice. Other stale holdings keep their own warnings. A recovery notice confirms completed checks; the remaining Helius credit allowance still needs to be checked in the affected server’s project dashboard.
Holdings refresh warnings are now clearer and less repetitive, so server owners can tell when a problem needs attention.
Existing request limits and role protections remain in place.
HoneyGate now reuses complete holdings checks across a server's gates. Member refresh requests and ownership-change notifications receive priority, while rolling background checks also cover members who have not recently used Discord.
Open Holdings checks from the member portal to request a refresh for your linked wallets. You can see whether a check is pending, delayed or confirmed, along with the original confirmation time. Server administrators can see refresh progress on the Gates page.
Incomplete checks and provider interruptions preserve existing roles. HoneyGate retries delayed work, checks that the current gate rules still match before updating roles, and sends gate-state notifications after the role update is confirmed.
Background checks aim for hourly coverage. Provider availability and credit limits can delay them.
When several roles are created, renamed or deleted together, HoneyGate now combines the resulting refresh work and limits how much runs at once. This reduces the database connection spikes that could interrupt other server activity. Temporary failures are retried.
If Helius rejects a request because of a limit, HoneyGate pauses checks for the affected server and retries after a cooling-off period. Unavailable checks preserve the last confirmed holdings and their original check time. They do not add or remove gate roles based on incomplete information.
Approved integrations now receive background refreshes for eligible assets, with limits on request volume and runtime. NFT collection snapshots are kept separate for each server, so one server’s refresh cannot replace another’s. Incomplete checks are reported as unavailable instead of being presented as current holdings.
when a member enters a giveaway, the public Discord message now refreshes its entry total immediately after confirming the entry. Simultaneous entries are refreshed in order, so a slower update cannot make the displayed total move backward.
Server owners can now protect several legacy holder roles while moving them to HoneyGate. The new migration center tracks multiple roles together and only completes each takeover after HoneyGate verifies that its replacement gate is ready.
Authorized integrations can now award currency, read balances, spend currency, review transaction history, and reverse an exact earlier award. Every credential, balance, and transaction remains tied to one Discord server, spending cannot overdraw a member, and repeated requests cannot duplicate ledger changes.
Server owners can set their own base daily Coins reward from 0 to 100,000. Setting it to zero turns off the currency reward without disabling daily check-ins, and any configured earning multiplier still applies consistently in the portal and Discord.
A failed token distribution now rechecks the token's real precision before resuming and refuses to send if that information cannot be proven. Existing payout legs are never sent twice, and totals below one transferable unit fail safely without creating an empty payout plan.
HoneyGate now reuses a server's tier and feature-access result during the same page request. Pages that check several controls do less repeated database work while keeping the same permissions and plan limits.
The bot and module loader now distinguish harmless optional conditions from real runtime failures more accurately. Production smoke checks also recognize the complete landing-page feature grid, reducing repeat false alarms without hiding genuine errors.
authorized API clients can now request a current NFT holder snapshot for an approved asset in their own server. HoneyGate keeps those snapshots warm in the background so an integration can read dependable holder data without waiting for a fresh chain lookup.
verified HoneyGate updates can now be released when the owner needs them instead of depending on a maintenance window that may not exist. The release still verifies the exact staging build, notifies owners, waits for in-progress money operations, and checks production before marking the update complete.
HoneyGate's admin panel is safer when you work across several servers. Many ordinary settings and workflow actions now stay bound to the server shown on the page, so changing servers in another tab cannot redirect those stale forms to the wrong community.
The Economy panel now gives owners a recorded way to take back an accidental Coin grant without pushing a balance below zero. The Shop keeps complete item descriptions and pages larger catalogs instead of silently shortening what members see.
Revenue sharing now builds each payout plan atomically, preserves exact whole-unit totals, and refuses ambiguous retries. Wallet and payout safety checks gained stronger real-source regression coverage.
Developers can use HoneyGate's guild-scoped holdings endpoint with an exact asset allowlist. It reads existing HoneyGate cache evidence only: it never starts a wallet refresh or calls a blockchain provider on behalf of an API request, and missing evidence remains unknown instead of becoming a false zero.
We also made the public install message agree with the fact that installs are open, improved exact-word documentation search results, and reduced HoneyGate bot database connection pressure by sharing a small set of behavior-compatible pools.
No HoneyGate architecture foundation changed. This is a v2 feature release, so the correct platform version is 2.7.0.
when the bot's internal API does not answer, the gate sweep now skips that one member and carries on, instead of dying for everyone.
docs search can now find token gating, and the HoneyBot help widget reaches the seven public pages that had no way to ask anything.
an adversarial review of the entry above found four defects in the fix itself. All four are closed here, each measured before and after.
five defects that all shared one shape -- the number that decides who gets a role was either unenforced, invisible, or uneditable, and one banner described behaviour the code does not have. New tests: (runs the real, sliced out of the shipped file) and (runs the real summary and the real in-place update against a fake DB, and reads the real CSS).
Nothing about how HoneyGate works has changed, and nothing new started collecting data. We found a claim in our own privacy policy that was not true, and we would rather correct it out loud.
We do count page views, through Cloudflare. Cloudflare sits in front of our website to keep it fast and block attacks — that part was always the case. It also counts page views, so we can see how many people visit and which pages get read. Our policy said we used no third-party analytics at all. That was wrong, and it had been wrong since the policy was written.
What that counting does and does not do. It sets no cookies. It does not fingerprint your device. It does not follow you to other websites. The counts are anonymous — they cannot be tied back to your Discord account, your email, or your wallet. It runs on every page, including the member portal and the admin panel.
Cloudflare is now named in section 5 alongside Discord, Stripe, Hetzner, Google and Anthropic, with the same plain description of what it receives.
You are seeing this because our policy promises we tell you here when something like this changes, and naming a company that handles your data counts.
The updated policy is at [/privacy](/privacy).
Nothing about how HoneyGate works has changed. We told you two things that were not true, and we would rather fix them out loud than quietly.
Your data is in the United States, not Germany. The policy said Germany. Our hosting company is German, but the servers holding your data sit in Ashburn, Virginia. It now says so.
We use two AI providers, and we should have named them. The help assistant and the AI-assisted moderation send text to Google (Gemini) and Anthropic (Claude) to get an answer back. That was always true — we just never wrote it down. The policy now names them, and says what gets sent: the question you asked, or the message being checked. It also says what never gets sent — your Discord account details, your email, and your wallet address.
You are seeing this because our policy promises we tell you here when something like this changes, and adding a company that handles your data counts.
The updated policy is at [/privacy](/privacy).
external apps can now AWARD Coins, not just read them. write scope, backed by and.
read. Closes two of the gaps the ZombabieZ integration found on 2026-08-01: there was no way to ask about a SINGLE person (gap 4 — apps had to page through up to 1000 rows and filter client-side), and no way to ask whether somebody is staff (gap 1 — GET /members returned members and XP only, so an integrator could not decide who to let into its own admin screens).
both events are back in the subscription picker and now actually deliver. Closes the last of the four gaps the ZombabieZ integration found (gap 2), and it is the event an integrator most wanted — "tell me the moment somebody links a wallet".
gains a ninth check — any guild with for more than 14 days.
accepts --lane=fast|heavy|all, each lane taking its own lock. Default is all — byte-for-byte today's behaviour — so an unchanged crontab is unaffected.
added. CRACKR shipped on 2026-07-04 with no thumbnail, so its card on the games page fell back to a flat colour for a month.
now dedupes its alerts. It previously alerted on every failing run, and on a 15-minute cron that is roughly 96 identical messages a day for findings the owner already knew about.
new, run every 15 minutes. Everything else in the stack watches whether HoneyGate is RUNNING.
adding a tracked asset now looks the mint up on Solana first and refuses the save when the chain contradicts what was entered.
The Type dropdown on Tracked Assets used to open on "Fungible token" with nothing actually selected, and the server quietly fell back to "token" whenever the type was missing. Between them, an owner could add an NFT collection, never touch the dropdown, and get it saved as a fungible token -- which then put it in the wrong dropdowns when building gates and alerts.
HoneyGate now reports uncaught errors to Sentry, on both sides, with no Composer dependency and no bundler (ground rules 2 and 3).
When a blockchain lookup failed, HoneyGate treated it the same as "this member sold their NFT" and removed their role. It could not tell "they do not hold it" apart from "we could not find out".
Now it can. If a lookup is unreliable, HoneyGate leaves everyone's roles alone and checks again next time. Someone who genuinely sells still loses the role. A bad lookup no longer costs anyone theirs.
Two related cases are fixed too. A gate saved without a token address used to strip the role from everyone who had it. And a failed check used to get filed as "checked, holds nothing" and trusted for the next hour.
Moving over from Collab.Land, SolMate, Vibe or similar? Two bots managing the same role can disagree about who qualifies and take turns adding and removing it.
There is a new setting at Gates then Settings: Allow HoneyGate to remove roles. Turn it off during the changeover and HoneyGate will still give roles to people who qualify, but never take one away. Only the other bot removes, so there is nothing to argue about.
Turn it back on once the old bot is switched off, otherwise someone who sells keeps their role.
The key page showed a green "Connected" badge whenever a key was saved. It only ever checked the key at the moment you pasted it, so if the key was later revoked, expired or rate-limited, the page stayed green while gating quietly stopped working.
It now re-checks in the background and shows you the truth, including a third state: saved, but not working. If Helius is rejecting your key you will see what it said and what it is costing you.
If the alt-account check hit a problem, the draw quietly fell back to the full pool and picked a winner anyway, without telling anyone. The setting looked on and was not doing anything.
The check now knows the difference between "alt detection is not installed here" and "something broke", and a real failure is recorded so you can see that a draw did not get the filter you asked for.
If a query behind the economy dashboard failed, the page showed 0. "Coins in circulation: 0" looked exactly the same whether it was true or whether the number could not be loaded.
Failed figures now read "unavailable", and the platform dashboard warns you when any figure on it could not be loaded. A real zero still shows as zero.
Every endpoint on the v1 API was returning an error instead of data. Fixed. If you tried it before and gave up, it is worth another look.
Gates then Settings. The evaluation options that were previously only editable in the database now have a proper home, alongside the new switch above.
Nothing here changes what you see, but all of it shipped:
The NFT page in the member portal showed a grey placeholder instead of the artwork, for every single NFT.
The page was loading which NFTs a member holds, but not the pictures that go with them, so there was nothing to display. Fixed. The gallery shows the real artwork now.
Your server now has its own Coins: an economy your members earn, spend, and compete over, kept separately for each server.
Reward members for holding your NFTs, without them ever moving anything on-chain.
including compressed NFTs.
with no key can't gate by NFT — but it now fails safe (it never strips a role it couldn't verify) and simply prompts you to add a key.
We sorted out an issue where the roles people earn for holding your NFTs could briefly drop off and then come back across a whole server. If the blockchain check that confirms who holds a collection had a momentary hiccup, the old logic read it as "nobody holds this" and pulled everyone's role until the next good check. Now, if that check ever comes back empty, it quietly falls back to a reliable one-wallet-at-a-time check instead of removing anyone. Your roles stay put — nothing for you to do.
A member's best daily check-in streak now shows on their public profile, counted across all their HoneyGate servers — a little recognition for the people who show up every day.
You can now set a regular maintenance window — say, Sunday at 5am — and every admin sees the next one in the "Up next" panel on their dashboard. Owners can also switch on a friendly Discord heads-up about 30 minutes ahead, posted in a channel they pick. It's off unless you turn it on.
Your members can now check in from the member portal, not just with Discord commands. Each person sees their current streak, a 30-day calendar of the days they showed up, and a new Daily Streaks leaderboard that ranks your most consistent members. Still one check-in per day, same as always.
Admins can also switch on a daily "top streakers" post and optional check-in reminders. Both are off by default.
The old cap of 10 NFT gates is gone. Pro servers can now gate as many collections as they want. Free stays at two.
Some collections (older or delisted ones) can't be read through the free verification source, and a gate built on one used to award no one with no explanation. Now the gates page flags it plainly and gives you a one-click switch to verify that collection another way. You'll see exactly which collections need attention instead of guessing why a role isn't landing.
Here's what landed on your server today.
Tickets, faster to run (Pro)
/ticket canned <name> instead of retyping it for the tenth time.Roles that clean up after themselves (Free)
More control over giveaways (Free)
/giveaway list shows every giveaway running on your server at a glance./giveaway delete cancels a running one cleanly, with no winners drawn — for when you typo the prize or pick the wrong channel.Daily check-ins, upgraded (Free)
/streak lets members see their own stats any time, without using their daily claim.And this page. You're reading our new changelog. Updates show up here and in the "What's New" box on your dashboard, so you always know what changed.