Vanar Chain doesn’t assume sessions end.
A Virtua world stays open. A VGN title boots right after. Same wallet. Same account context. The handoff is fast on purpose. Nobody signs out. Nobody re-auths. The session stays warm and keeps moving.
Vanar's Virtua writes something that changes access. An inventory flag. A gate. An entitlement that isn’t cosmetic. It finalizes on-chain and the state is already settled.
VGN picks up the session before its side has absorbed that change. The session credential is still valid. The entitlement snapshot it’s holding hasn’t been challenged yet. Recent enough. Good enough.
So the next action goes through. No new ask to the chain. No pause. That’s the promise of the handoff.
A few seconds later, the views split.
Virtua reflects what finalized. VGN on Vanar cbain reflects what the warm session believed. Each log looks reasonable if you read it alone. Together they don’t line up.
Players don’t write “auth mismatch.” They write the ugly human versions.
“I entered, then I got kicked.”
“My friend can still use it.”
“It worked five minutes ago.”
Screenshots pile up. Screenshots don’t carry entitlement freshness. They don’t show which snapshot was used at the handoff. They just show success.
Support pulls two dashboards and gets two answers. One says access active. One says expired. The explorer is correct, but it doesn’t explain why the session behaved as if the update hadn’t landed yet.
VGN makes it spread because cross-title handoff is the product. Sessions move between titles. Assumptions come along for the ride. One game refreshes entitlements aggressively. Another holds state because onboarding drop-off hurts. Same wallet. Same session. Different enforcement depending on which title touched the account layer last.
Brands escalate because this isn’t UX. Early access is leakage. Late revocation is refunds. They don’t care which service was “supposed” to refresh first. They want a sentence they can quote when a gated surface behaves differently depending on where you entered.
Someone proposes forcing re-auth on every cross-title jump. Someone else asks how many users you’re willing to kick out mid-session. Another suggestion comes up—delay handoff until downstream views align—and dies immediately. Live Virtua traffic on Vanar isn’t waiting for alignment.
The system keeps accepting sessions.
What partners ask for is simpler than the debate... tell us which layer can block the action after finality, and when.
