Velas history and team: what we can verify

According to the official site, the Velas mainnet launched in 2019 as a fork of Solana with an integrated EVM. The project later added products such as Velas Wallet, Vault and Account.

What we could confirm

• The project's own description of its architecture.
• The existence of public explorers and documentation.

What we could not

We did not find a verifiable, current team page we could cite, so we do not name individuals. Check velas.com for current information and treat anonymous profiles with scepticism.

For technology, see how Velas works, and for latest updates roadmap and news.

The idea behind the project

Velas describes itself as a blockchain that combines the speed design of Solana with compatibility with Ethereum's virtual machine. The aim, in the project's own words, is to let developers use familiar Solidity tools while getting fast confirmations and low fees. That positioning explains the shape of the product line: a native network, an embedded EVM, a consumer wallet, and a set of tools for storing and managing assets. We can describe this because it appears in the official materials; we cannot independently measure how far each goal has been met, and you should be careful with any page that claims to do so without data.

Launch and early phase

The official site states that the mainnet launched in 2019. Before that, projects of this kind generally went through a period of code development, testnets and a token distribution. For Velas, we could not find a primary source we could cite that sets out a full, dated chain of events from the earliest design work to mainnet, the token sale or the listings that followed, so we do not retell one. Third-party timelines exist, but they are often copied from one another and may contain errors. If a date matters to you, check it against the project's own announcements or an archived copy of its site.

Why the Solana fork matters

A fork means the project started from Solana's open-source code and then changed it. This has two effects. On the positive side, it inherits a design built for high throughput. On the other, the fork does not automatically receive later improvements made by the original project, and its maintainers have to merge, adapt or leave out each change themselves. How much of that work is happening is a question about development activity, which you can partly judge by looking at the public code repositories and the documentation. Our Velas vs Solana page covers the technical differences in more detail.

Products and what they do

The official site lists Velas Wallet for holding and staking, Velas Vault for managing assets in a more structured way, and Velas Account as an access method. The roles of these products can change as the team revises them, so check the descriptions on velas.com instead of relying on summaries. We review the wallet separately in the wallet review.

Judging the team without names

Many readers want to know who is behind a project. We did not find a current team page we could verify and cite, so we do not list individuals. This is a limitation of our research, not a finding about the people. When you evaluate any project, useful questions include whether team members are publicly identifiable, whether their work history can be checked independently, whether there are published audits, and whether the project responds to questions in public. Be careful with sites that present detailed biographies and photos without sources, because such profiles are easy to fabricate.

What history cannot tell you

A long history is not a safety guarantee, and a short one is not a red flag by itself. What matters for a holder is current activity: whether the network runs, whether there are users and developers, and whether you can buy, sell and use the coin when you need to. For where to find the latest official information, see roadmap and news; for risk, see the safety guide.

Reading project history carefully

History pages can create the impression of certainty. A launch, a rename or a product release is easy to date, yet the reasons behind them are usually not documented in a way that outsiders can check. Where this site states something, it relies on the project's own channels: the mainnet launched in 2019 according to velas.com, and the product line, such as Velas Wallet, Vault and Account, is described on the official pages. Beyond that, we avoid filling gaps with guesses.

When you read about a team, separate three things: who is named, what they have done, and what can be confirmed independently. A confident biography on a single site is a claim, not a verification. Independent confirmation might be a public repository with a visible commit history, a conference recording or a documented audit. If it is missing, keep your confidence modest and say so in your own notes.

Finally, remember that a long operating record is useful but limited. It shows that a project survived for a while, not that it will keep doing so. Revisit the official documentation from time to time, and treat any claim about growth, partners or adoption as something to check against data you can open yourself, such as the explorers.