Skip to main content

Account Model

Virae is best understood as one user account coordinating multiple product surfaces and wallet rails.

Virae account overview

The current Account page acts as a unified status surface: session state, proxy wallet, deploy status, and multi-step initialization or routing tasks are shown in one place instead of being scattered across product pages.

One account, multiple product capabilities​

Your account is the stable identity that ties together:

  • web access
  • Telegram access
  • wallet setup state
  • portfolio and activity views
  • rewards, referrals, and related account history

Why the account model matters​

Different products inside Virae can have different readiness rules. That means one account can be:

  • fully ready for one product
  • partially ready for another
  • missing funding or approvals for a third

This is normal in a multi-venue product.

What Virae tries to keep unified​

Even though venue behavior differs, Virae tries to keep these user-facing ideas unified:

  • one account identity
  • one place to understand portfolio and account state
  • one wallet setup model for supported product rails
  • one place to resolve account restrictions and recovery prompts

What Virae keeps explicit​

Virae does not pretend every venue uses the same execution model.

The docs and product UI separate:

  • identity and authentication
  • wallet existence and readiness
  • funding availability
  • trade execution and fee settlement

That separation makes the product less confusing when a specific rail needs attention.