Human-readable.
Cryptographically grounded.
A unique username maps to a persistent identity. The technical blockchain address remains underneath.
VAYOS NETWORK / SOVEREIGN LAYER 1
Identity, assets and account history should outlast a single signing key. Vayos brings continuity into the foundation of a sovereign network.
Persistent identity.
Stable accounts. Controlled recovery.
One lost key should not mean a lost identity. Vayos separates the account from its current controller, with explicit rules for how access can change.
Protocol illustration only. No wallet connection or on-chain transaction.
The current controller signs. The identity remains independent.
A unique username maps to a persistent identity. The technical blockchain address remains underneath.
Signed credential status lives on-chain. Documents and biometric evidence belong in a separate, secured verification service.
Opt-in recovery uses explicit authorization, waiting periods and cancellation controls. KYC recovery requires at least 72 hours.
From settlement to the human experience, every plane has a clear responsibility. Together, they make continuity a property of the network.
CometBFT consensus, native VAY and modular execution form the network’s settlement base.
CONSENSUS · STAKING · FINAL SETTLEMENTStable accounts, multisignature roles and vesting make control and responsibility visible.
ACCOUNTS · MULTISIG · VESTINGPersistent identities, credential status and time-bound recovery remain linked to the account.
IDENTITY · CREDENTIALS · RECOVERYWallets, explorers and institutional applications connect through RPC, REST and gRPC interfaces.
EXPERIENCES · INTEGRATIONS · INTERFACESL1–L4 describe architectural planes within Vayos. They are not four separate blockchains or rollups.
People move. Teams evolve. Keys change. Financial infrastructure needs a deliberate way to keep identity, authority and assets connected.
Distinct fund responsibilities, multisignature authorization and explicit allocation rules create a foundation for controlled treasury operations.
ROLE SEPARATION / AUDITABILITYStable accounts and authorized controller changes support custody models that do not depend on one signing key forever.
STABLE ACCOUNTS / CONTINUITYHuman-readable usernames and credential status give application builders a more intuitive foundation for financial experiences.
IDENTITY / CREDENTIAL STATUSCosmos SDK modules and CometBFT consensus connect purpose-built Vayos capabilities with established developer tooling.
MODULAR EXECUTION / OPEN INTERFACESContinuity is not an add-on.
It is the starting point.
Network settlement, transaction fees and staking—within a fixed allocation framework.
| Allocation | VAY | Share |
|---|
Applies to transaction fees, not the amount transferred.
Allocations are not evidence of capital raised. No price, return, listing or liquidity is guaranteed.
Separating identity, control and settlement creates a path toward a broader class of institutional applications.
A future credential layer could let people share only the eligibility information an application needs.
Application-level approval flows could express purpose, permitted actions and settlement conditions.
Interoperable credential formats could connect identity-aware experiences across applications.
These are forward-looking application concepts, distinct from the current chain capabilities. Signed credentials are not zero-knowledge proofs.
No. Vayos is a sovereign Layer 1 built with Cosmos SDK and CometBFT. VAY is its native asset for transaction fees, staking and settlement.
No. The chain records signed credential status and commitments, not personal documents or biometric records. Document capture, liveness and private evidence custody require a separate verification service. Public identity IDs and credential status remain linkable.
No. Recovery is opt-in and requires the configured authorization, waiting period and cancellation rules. KYC recovery requires a valid issuer attestation and a minimum 72-hour delay. It is not an automatic reset or a bypass of ownership controls.
Persistent identities, stable accounts, multisignature roles, vesting and controlled recovery address long-lived operational needs. Institutional use still requires independent security review, appropriate custody and applicable compliance processes.
Explore the architecture, account model and economic framework behind the network.
Read the protocol paper