Clients on Solana
Connect to a Sentinel dVPN node with the sentinel-dvpn CLI and a client daemon. Payments are on Solana.
Draft
These pages come from the sentinel-dvpn and sentinel-dvpnd source in sentinel-solana and the binaries' --help output. The commands have not yet been run end to end on devnet. The source of devnet dVPN tokens is TBD.
What you need
- The
sentinel-dvpnCLI and thesentinel-dvpnddaemon, built for devnet with the program ID and mint set. See Build the binaries. A plaingo buildleaves them unset, and every chain call fails. - An owner wallet with SOL for fees and dVPN tokens for payment. On devnet, get SOL from the official Solana faucet.
- A client daemon with its own SOL balance. The daemon signs channel transactions and pays their fees with its operator key. Its public key is in the init output.
How a session works
- Your owner wallet holds the dVPN tokens and pays for on-chain actions.
- Your client daemon (
sentinel-dvpnd, instance tagc<N>) holds the session keys, signs channel transactions, and talks to nodes. - The CLI (
sentinel-dvpn) starts and stops sessions through the daemon, with--instance c<N>.
Ways to pay
| Route | Use it when | Command |
|---|---|---|
| New channel | You pay a node directly, per GB or per hour, by voucher or stream. | client start --instance c0 --node <NODE> --new-channel --mode voucher --escrow-base-units <N> |
| Existing channel | You already have a channel with this node. | client start --instance c0 --node <NODE> --channel <CHANNEL> |
| Provider ticket | You hold a subscription from a provider. | client start --instance c0 --node <NODE> --provider <PROVIDER> --subscription <SUB> --ticket |
Setup, then connection, are in the next two pages: