Install Vela
The same wallet runs in several places, and they all open the same address with the same keys. Pick by what you need; you can use more than one. Downloads are on Get Vela.
| What it is | Cost | Status | |
|---|---|---|---|
| Web | wallet.getvela.app in any recent browser | Free | Live |
| Browser extension | The wallet in your toolbar; connects to dApps | Free | Download and load by hand; not yet on the Chrome Web Store |
| Desktop | Native app for macOS, Windows and Linux | Free | Download from Get Vela or GitHub |
| iPhone, Android | Native apps | One-time purchase in the stores | Not in the stores yet; you can build them from source |
Web
Nothing to install. Open wallet.getvela.app, create a wallet or sign in, and it is there. Your account list is kept in this browser; on another device you simply sign in again with one of your keys.
Browser extension
Chromium browsers: Chrome, Edge and Brave (Chrome 122 or later). It puts the wallet in the toolbar and lets dApps connect to it directly. Until it is on the Chrome Web Store:
- Download the extension from Get Vela and unzip it into a folder you will keep — the browser runs it from there.
- Open
chrome://extensionsand turn on Developer mode. - Click Load unpacked and choose that folder.
It is the same wallet: extension and web wallet use the same getvela.app passkeys, so the same keys open the same address.
Desktop
A native app, not a web page in a window: Windows 10 and 11 (x64 and ARM), macOS 11 or later, and Linux (.deb, .rpm or Flatpak, x64 and ARM).
- Windows will warn that it “protected your PC”, because the installer isn’t code-signed yet. Choose More info, then Run anyway.
- macOS builds are signed and notarized by Apple in a separate step, so they can lag behind the other platforms. When the Mac button says “coming shortly”, the most recent notarized Mac build is on the GitHub releases page.
- Linux: to use a USB security key, your system must give the app access to it — the .deb and .rpm packages install the rule for you.
On macOS and Windows the desktop app has a built-in browser for dApps. Checksums for every package are on the GitHub releases page — and you can check more than a checksum, see below.
iPhone and Android
Native apps for iOS 17.4 or later and Android 10 or later. They will be sold as a one-time purchase in the App Store and Google Play; they are not in the stores yet. The code is open, so you can build them yourself for free — with one difference: a build you sign yourself can’t use your phone’s own passkeys for getvela.app wallets, though scanning with another phone and USB security keys work. See build the apps yourself.
Verify what you downloaded
A checksum tells you that two files are identical. It cannot tell you who made
the file — and the list of checksums sits on the same page as the download. So
every package we attach to a release is also attested: the release workflow
signs a statement naming the file, the commit and the run, and GitHub keeps it.
Checking it takes one command with the GitHub CLI (sign in once with gh auth login; the
check is free):
gh attestation verify vela-wallet_0.9.4_amd64.deb --repo mondaylabsltd/vela-walletIt prints who built the file and from which commit, or it fails. Nothing on your machine has to trust us for that answer: the signature is GitHub’s, made when the release is published, and it cannot be produced by someone who merely re-uploads a file somewhere.
Mac images are the exception. They are built, signed with our Developer ID and
notarized by Apple by hand, so no workflow built them; a separate workflow attests
them afterwards, from the bytes as published (add --signer-workflow mondaylabsltd/vela-wallet/.github/workflows/macos-attest.yml to check that). Apple’s notarization, which macOS checks when you open one, is
their first proof. To ask for it yourself:
xcrun stapler validate VelaWallet-0.9.4-macos-arm64.dmg
spctl -a -t open --context context:primary-signature -v VelaWallet-0.9.4-macos-arm64.dmgPackages published before this was turned on carry their checksums only.
Using Vela with dApps
dApps connect to Vela the way they connect to any browser wallet (EIP-1193 and EIP-6963):
- in a desktop browser, through the Vela browser extension;
- inside the desktop app (macOS, Windows), the iPhone app and the Android app, through their built-in browser.
The web wallet at wallet.getvela.app doesn’t connect to dApps, and there is no WalletConnect. Every request a dApp makes is decoded and shown to you before you sign — see clear signing.
What your device needs
Vela signs with passkeys, which nearly every device from the last few years supports:
| Device | Supported |
|---|---|
| iPhone, iPad, Mac | iOS / iPadOS 16+, macOS with a recent Safari or Chrome |
| Android | A recent Android with Google Play services, or a USB security key |
| Windows | Windows Hello with Chrome or Edge, or a security key |
| Linux | A security key, or a phone nearby (scan the QR code) |
If your device can’t hold a passkey itself, use another phone or a hardware security key. Signers & security keys lists which kinds of key each app supports.
The only official addresses
- getvela.app — this site, and the downloads
- wallet.getvela.app — the web wallet
- github.com/mondaylabsltd — the code and release packages
Next: create your wallet.