VersoVPN — the network and the VVPN token

Introduction

VersoVPN is a privacy-first VPN with an open token economy. It is built on a simple observation: a VPN does not remove the party who can watch you — it replaces one with another. The trade is only worth making if the new party keeps nothing worth taking.

Most providers answer this with a policy. A policy is a promise about future behaviour, and a promise is a setting someone can change — during a migration, after an acquisition, or when a new vendor turns logging back on by default. We would rather there be very little to keep in the first place, because of how the system is built rather than how the company feels about it.

VVPN, the network's utility token on Solana, exists for the same reason. Subscriptions are paid in VVPN and settled on-chain, so no banking record ties a person to an account. Paying operators in the same token lets capacity appear where users actually are, instead of where a hosting budget was approved a year ago.

This document describes what is decided, what is intended, and — explicitly — what is not decided yet. It is a working document, not a prospectus.

The problem

A commercial VPN asks for three things at once: your money, your traffic, and your trust. Each of them leaks something.

• Payment identifies you. A bank payment names the subscriber, the provider and the date. Even a provider who logs nothing is holding a billing record that ties a person to an account.
• Logs exist by default. Servers log unless someone deliberately makes them stop, and "deliberately" has to survive every future migration, vendor and on-call engineer.
• Trust is unverifiable. Audits are snapshots. Between two audits, the only thing standing between a user and a log file is the operator's word.
• Capacity is centrally planned. Coverage follows procurement, not demand. Users in the places that need a VPN most are frequently the ones served worst.

None of this is solved by promising harder.

What VersoVPN is

A VPN service designed so that there is little to hand over, and an economy that does not require users to identify themselves in order to pay.

No account to identify. Access is attached to a subscription, not to a profile about a person. There is no name field because nothing in the system would use it.

Payment separated from usage. How a subscription was paid and what was connected to are kept apart. Payment is settled in VVPN, so there is no banking record to separate in the first place.

Keep less rather than guard more. Data that exists gets copied, leaked, or sold with the company after an acquisition. The only version that survives all three is the version never kept. The concrete retention statement — what is kept, for how long, and how that can be checked — will be published before launch, as specifics rather than as a slogan.

Operator-run capacity. Anyone can run a node and be paid for the traffic it serves. Coverage grows where people connect from.

Modern, inspectable transport. WireGuard-based tunnelling: quick to connect, small enough to audit, undramatic on battery. Any client that shipped would come with public source and protocol details — a privacy claim nobody can inspect is a slogan.

Subscriptions and the VVPN token

The design uses a subscription model. Plans would be priced in USD as the reference unit and paid in VVPN, settled on-chain. Nothing below is running today.

When paying in VVPN, the amount of tokens is derived from the USD price using a moving average of the VVPN/USD rate over a trailing window, rather than the spot price at the moment of payment. This is a deliberate safeguard in both directions: a user does not overpay because of a five-minute spike, and the network does not lose a month of revenue because of a five-minute dip.

Payment in the token is how the design works, not an alternative rail: a bank payment would recreate the record the whole thing exists to avoid. The free tier would require no payment at all, so the service could be tried before holding any token.

Access tiers and staking

In the design, staking VVPN would unlock higher access tiers instead of a higher bill: access would follow the stake rather than a repeated charge, and the network would get a supply of tokens that is committed rather than circulating.

Staking parameters — thresholds, holding periods, and what each tier includes — are not decided, and no staking exists. If it is ever built, it is a mechanism for access, not a yield product: no return is promised, offered, or implied.

Node operators

Operators who provide capacity would be paid in VVPN for the traffic they serve, following measured traffic rather than declared capacity, so the cost of adding a node is borne by whoever benefits from it being there. No node software exists.

The measurement scheme, the reward formula and the anti-abuse rules are not written. They are the part of this design that fails most often in practice — a naive scheme pays the operator who fabricates traffic — and they would have to be published in detail before any reward was paid.

The token

VVPN is a classic SPL token on Solana with Metaplex metadata. Token-2022 extensions are deliberately not used: they cost compatibility with wallets, DEXes and aggregators, and nothing in this design needs them.

The mint address is already fixed and published here, even though the token has not been issued on mainnet yet. This is intentional: the address is derived from a key held by the project and will be the same one on every network. Any other address presented as VVPN — before or after launch — is not ours.

Distribution and emissions

Distribution is not published yet, and this document will not carry a placeholder chart for it. Percentages posted now would be numbers quietly changed later, which is worse than an acknowledged open question.

Three commitments constrain whatever is published:

1. Supply is fixed at 1,000,000,000 VVPN. There is no inflation mechanism in the design.
2. Allocations are announced with what is actually in force at the time. There is no vesting contract and no lock programme: writing one into this document before it exists would describe a guarantee nobody could check on-chain.
3. Anything the project holds will be visible on-chain, at addresses named in this document when distribution is announced.

Mint and freeze authority

Both authorities are currently held by the project. This is visible to anyone, and security scanners flag it — correctly, because an active mint authority means supply can change.

Revoking them is irreversible and therefore a decision taken once, deliberately, and announced with the transaction that does it. The current state will always be stated here honestly rather than quietly.

Security and trust

• The token is an ordinary SPL token issued through Metaplex Token Metadata. There is no custom token contract, so there is no bespoke code that could contain a bespoke bug.
• Everything about the token is publicly verifiable on Solana explorers: supply, holders, authorities, and every transfer.
• The service is being designed to be checkable, not merely trusted: published retention specifics, public client source, and inspectable protocol choices.
• Nothing to review yet. There are no contracts and no staking mechanism. If either is ever built, it would need external review before holding anyone's tokens.

Security here is not a feature list. It is the assumption that anything stored will eventually be seen by someone it was not meant for — so the design keeps as little as possible.

Status

At the time of writing:

• The token exists as a design and a fixed mint address; it has not been issued on mainnet.
• The issuance path has been rehearsed end-to-end against real mainnet programs on a local fork.
• The service is a design. There is no client, no node software, and no staking — and no commitment here that any of them will be built.
• Pricing, distribution, staking parameters and node reward rules are open questions, listed as such above.

This document will be updated as each of these becomes a fact. Changes that matter will be dated.

Legal notice

VVPN is a utility token intended for use inside a product. It is not a security, not a share, not a deposit, and not an investment product. Holding it does not entitle the holder to profit, dividends, revenue, or any claim on the assets of the project.

Nothing in this document is financial advice, an offer to sell, or a solicitation to buy any asset. Forward-looking statements describe intent and may change. The value of a token can fall to zero.