Vanar Chain assumes users won’t manage keys, fees or timing. Fine. Until subsidy is the thing that starts flinching.
Virtua drop. Real one. Timer running. Traffic comes in ugly. Bursts, not a curve.
Claim. Close app. Open. Claim again because “pending” looks like a lie when everyone else is posting screenshots.
Blocks keep landing. Explorer looks calm. If you stop there, you miss it.
The Vanar sponsor/relay side starts rationing and it doesn’t announce itself. It just… stretches. Requests that used to clear now hang. Not rejected. Not cleanly. Just long enough.
So users manufacture duplicates.
Two intents. Three. Same wallet. Same asset. Different outcomes depending on which path got subsidized and which one got parked in that half-alive state.
Your app log says “confirmed.” Your backend says “sent to relay.” The chain only has one finalized action. Support has a screenshot and a timestamp and zero context about why the other intent never became real.
$VANRY stays “invisible” right up until it’s deciding priority. Who gets gas covered. Who gets queued. Who gets silently pushed into waiting until they spam harder.
From the outside it looks random. From the inside it’s policy. Caps. Budget. Someone set it for a normal day.
Brands don’t care what you call it. They care that “confirmed” isn’t defensible during a public drop. They care that you can’t tell them, cleanly, which receipts are real without pulling internal relay traces and arguing about timing.
Then the requests start.
Freeze this collection. Reissue those claims. Make the UI stop saying confirmed until it’s final-final.
Ops checks the cap, checks the abuse patterns, checks the partner thread blowing up. Someone says “raise it.” Someone else says “don’t.” Another person asks how many manual reconciliations they’re willing to do tonight.