Vanar Chain doesn’t wait for a login screen.
A Virtua scene is already open. A VGN title loads right after. Same wallet. Same account. No reconnect, no prompt. The session is warm, carried across as-is. No forced refresh.
Something gets touched that matters. Not cosmetic. An access flag, an inventory edge, a gate that’s supposed to mean “not everyone.” The action settles and finality lands fast and complete.
The session keeps going. No wallet recheck. No entitlement refresh. The last snapshot is still sitting in the handoff path and it hasn’t been challenged yet. Recent enough to pass.
So the next action clears too. No new ask. Just movement.
A few seconds later the disagreement shows up. Not an error, just behavior that doesn’t line up. Virtua reflects the post-finalized state. VGN reflects what the warm session believed a moment earlier.
Users don’t send technical reports.
“I got in and then I got kicked.”
“My friend can still see it.”
“It worked earlier.”
Screenshots start landing in support. They show success and confidence. They don’t show the entitlement snapshot that got used on the Vanar's VGN handoff credential. They can’t.
Support doesn’t see a “failure.” They see two dashboards giving two answers. One says access active. One says expired. The Vanar indexer view is calm and correct, and still not enough.
On VGN, it doesn’t stay contained. One title refreshes entitlements on launch and starts kicking people out. Another only refreshes on a session reset, so the same account keeps moving like nothing changed. Now the reports sound fake: works in one game, blocked in another. Same wallet. Same Vanar session window. Different enforcement depending on where the handoff landed last.
Nothing new was signed. That’s what makes the partner thread ugly. You can’t point to “user did X” without it sounding like you’re blaming normal behavior.
Brands escalate because this isn’t UX noise. Early access is leakage. Late revocation is refunds. They don’t care which service refreshed first or which snapshot was “close enough.” They care that a gated surface behaves differently depending on which Vanar consumer surface the session came from.
A few fixes get floated. Re-auth on Vamar chain on every cross-title hop. Delay handoff until downstream views align. Those two die in the thread. Virtua traffic isn’t waiting and VGN can’t turn cross-title flow into checkpoints.
Traffic keeps coming.
Snapshots keep getting reused.
