Survivability

Velocity Network purposefully mitigates vendor lock-in risks and vulnerabilities associated with the discontinuation or usage restrictions of participating entities. The following network attributes ensure sustained credential utility, regardless of the actions of specific entities, without reliance on proprietary solutions. The subsequent list of network attributes explains the sustained utility of credentials within the project, even in the event of a particular entity's cessation of operations or discontinuation of its contract and how continuity is not contingent on any proprietary or vendor-specific solution that cannot be seamlessly substituted with another, ensuring minimal disruption to individuals benefiting from the demonstration.

Storage of Credentials: Wallets, used by individuals, provide a secure means of storing credentials. Users have the flexibility to transfer their credentials to other wallets within the Velocity Ecosystem, utilizing the same protocols without loss of utility. Wallet open-source SDKs used by ecosystem participants to develop wallets enable self-storage of credential data by default, allowing individuals to back up and recover their credentials independently, reducing reliance on a specific wallet vendor.

Verifiability of Credentials: Velocity Network maintains credential utility, even in cases where an issuer becomes unavailable. Relying parties directly verify credentials and claims by accessing the Velocity Ledger. This decentralized verification process ensures credentials remain verifiable, including source identity, revocation status, source authority, person binding, and data integrity.

The Trust Ledger: Velocity Network architecture is intentionally designed to be resilient and free from single-entity control. Dozens of independent organizations actively operating nodes on the decentralized ledger, and additional organizations are expected to join. This extensive network ensures redundancy and strengthens the foundational utility layer, enhancing reliability and robustness.

Issuers and Relying Parties: Issuers or relying parties aren't locked into any specific solution. They can operate their own credential agent using the open-source software developed by the community or opt for a 3rd party proprietary solution. Since all these technologies adhere to the same protocol and standards, this means Issuers and Relying Parties easily switch vendors without causing significant disruption.