# DVeVPN 2.0 Stable Release Notes

**Version:** 2.0.0  
**Product:** DVeVPN 2.0 Stable  
**Protocol:** FROZEN (DVeProto / DVeNet 2.0)  
**Date:** 2026-08-03

## Highlights

- Production Linux VPN client and server (UDP Handshake → IP tunnel)
- Persistent client (`dve vpn enable`) with reconnect backoff 5→10→30→60
- Installer always tracks latest Stable: `curl -fsSL https://dveproto.serversys.ru/install.sh | sudo bash`
- `dve doctor` reports **READY** when the node is healthy
- `dve vpn remote-test HOST` for real-network validation
- `dve security check` production audit
- Update / apply with backup + rollback
- Release artifacts: amd64 / arm64 tarballs + checksums

## Install

```bash
curl -fsSL https://dveproto.serversys.ru/install.sh | sudo bash
sudo dve init
dve doctor          # expect READY
```

## Version display

```text
DVe:
2.0.0

DVeProto:
2.0

DVeNet:
2.0

DVeVPN:
2.0 Stable

Protocol:
FROZEN
```

## Downloads

| Platform | Artifact |
|----------|----------|
| Linux AMD64 | `release/dve-2.0-linux-amd64.tar.gz` |
| Linux ARM64 | `release/dve-2.0-linux-arm64.tar.gz` |
| Checksums | `release/checksums.txt` |
| Metadata | `release/release.json` |

API: `https://dveproto.serversys.ru/api/version`

## Frozen (do not change)

Wire · Handshake · Carrier · DVeNet · Routing · Multipath · packet format · crypto defaults · protocol compatibility

## Known limitations

- Windows / macOS clients still require Wintun / utun (stubs in 2.0)
- Real TUN needs root or `CAP_NET_ADMIN`
- Portal should stay on localhost in production

## Migration from RC

See [docs/migration-rc-to-stable.md](docs/migration-rc-to-stable.md).