Skip to main content

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-dvpn CLI and the sentinel-dvpnd daemon, built for devnet with the program ID and mint set. See Build the binaries. A plain go build leaves 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​

  1. Your owner wallet holds the dVPN tokens and pays for on-chain actions.
  2. Your client daemon (sentinel-dvpnd, instance tag c<N>) holds the session keys, signs channel transactions, and talks to nodes.
  3. The CLI (sentinel-dvpn) starts and stops sessions through the daemon, with --instance c<N>.

Ways to pay​

RouteUse it whenCommand
New channelYou 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 channelYou already have a channel with this node.client start --instance c0 --node <NODE> --channel <CHANNEL>
Provider ticketYou 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:

  1. Set up the wallet and client daemon
  2. Connect to a node