HIVE WalletHIVE
Get started
DESKTOP WALLET FOR THE HIVE NETWORK

Your Hive wallet.
Fast. Local. Yours.

Manage named Hive accounts, send and receive HIVE or HBD, scan payment details and approve each operation locally with the authority designed for the task.

Download walletExplore features
HIVE + HBD Self-custody Local signing
WALLET WORKSPACEPORTFOLIO
HIVE MAINNET
PORTFOLIONative liquid assets
DEMO PREVIEW
H
Liquid Hive balance1,248.520
HIVE
$
Hive Backed Dollar326.18
HBD
Recent activityReview operations

Received HIVEfrom @hiveuser · 3 sec ago

+24.000 HIVE

Sent HBDto @merchant · yesterday

-12.500 HBD
Local transaction signingSelected authority stays on this deviceACTIVE KEY
DISCOVER HIVE WALLET
2Direct liquid assetsHIVE and HBD
~3sHive block timeFast account operations
4Authority rolesOwner · Active · Posting · Memo
RPCLight-client modelRemote chain data, local signing
01 · CORE WALLET FEATURES

Everything you need
for everyday Hive.

A focused interface for checking balances, receiving to a readable account name, sending native assets and connecting to selected Hive applications without turning daily use into a protocol lesson.

01

Send and receive HIVE or HBD

View liquid balances, receive funds through your named Hive account and prepare native transfers with a clear recipient, amount, asset and memo review.

02

Follow multiple accounts

Add public Hive accounts for watch-only monitoring without storing their private signing keys. Switch accounts from one focused portfolio view.

03

Control authority by role

Use posting for social activity and active for financial actions while keeping owner control offline for recovery and critical changes.

04

Connect to the Hive ecosystem

Review and approve selected Keychain-compatible requests from Hive applications, including power, delegation and custom-JSON operations.

02 · ASSETS & ACCOUNT STATE

HIVE and HBD
at the center.

See the two native liquid assets first, then understand how Hive Power, Resource Credits and connected layer-two activity fit around your account.

A focused native-asset wallet. HIVE and HBD are first-class balances and transfers; vesting state and Hive Engine requests follow different operation paths.
ASSET OR ACCOUNT STATEWALLET ACCESS
HIVE

HIVE · liquid native asset

Monitor your liquid balance, receive to your named account and prepare native HIVE transfers.

NATIVE ASSET
HBD

Hive Backed Dollar · liquid native asset

Monitor, receive and transfer HBD from the same account view. HBD is not fiat USD or USDC.

NATIVE ASSET
HP

Hive Power / VESTS

See stake-related account state and use connected requests for supported power and delegation operations.

ACCOUNT STATE
RC

Resource Credits

Track the regenerating operation capacity associated with stake; RC is not a transferable cryptocurrency.

NETWORK CAPACITY
L2

Hive Engine tokens

Approve selected token-transfer requests from connected apps through Hive custom JSON after checking every field.

CONNECTED APP
—

BTC, ETH, SOL and other chains

HIVE Wallet is focused on the Hive account and network model, not unrelated blockchains.

OUTSIDE HIVE
03 · WALLET ACTIONS

One clear path
for every action.

Read your public account without a key, receive through your account name and approve value-moving actions with the correct Hive authority.

OPERATIONACCESS PATHTYPICAL AUTHORITY

Monitor a public account

Read balances and public account state through a Hive RPC endpoint without importing a signing key.

WATCH ONLYNO PRIVATE KEY

Receive HIVE or HBD

Share the readable Hive account name or a generated QR code as the receiving identifier.

NATIVE RECEIVEACCOUNT NAME

Transfer HIVE or HBD

Review recipient, amount, asset and memo, then sign locally before RPC broadcast.

NATIVE SENDACTIVE

Power up, power down or delegate

Approve supported Keychain-compatible requests after reviewing the effective vesting operation.

CONNECTED APPACTIVE

Post, vote or social custom JSON

Keep financial authority separate by using posting access when the requested operation permits it.

CONNECTED APPPOSTING

Savings, conversions and internal market

These Hive network functions require an interface that explicitly presents and confirms the complete operation.

VERIFY FLOWVARIES

Hive Engine token transfer

Inspect the custom-JSON contract, token symbol, quantity and recipient before authorization.

CONNECTED APPACTIVE / POSTING
04 · HOW IT WORKS

Chain data from RPC.
Authorization on your device.

HIVE Wallet stays lightweight by reading account state through a Hive RPC endpoint. The requested operation is assembled for review and signed locally when the required role key is available.

01

Review intent

Confirm account, recipient, amount, asset, memo and the exact requested operation.

02

Select authority

Use posting for social actions, active for transfers, and keep owner authority offline.

03

Sign locally

The applicable private key authorizes the serialized transaction on the user’s device.

04

Broadcast & verify

The signed transaction is sent through Hive RPC and checked independently on-chain.

Fast network access without downloading the chain. The wallet can use https://api.hive.blog for account data and broadcast. Private keys remain part of local signing; verify important balances and completed transfers independently when value matters.
05 · KEY CONTROL

One Hive account.
The right key for each task.

Hive separates recovery, financial, social and memo permissions. HIVE Wallet makes that authority model visible so daily actions do not require owner-level access.

RECOVERY CONTROL

Owner authority

Highest control level for critical account changes and recovery. Keep it offline and never import it for routine use.

FINANCIAL ACTIONS

Active authority

Authorizes transfers, power operations, delegations and many account-management actions.

SOCIAL ACTIONS

Posting authority

Lower-privilege role for posts, votes and selected social or custom operations.

PRIVATE MEMOS

Memo key

Encrypts and decrypts supported memos. It is not a spending authority by itself.

06 · CONNECTED HIVE APPS

Use Hive applications
with a visible signing path.

Selected Keychain-compatible requests move from a connected Hive application to the wallet for authority selection, review, local signing and broadcast.

HIVE WalletReviews and approves the requestKeychain-style bridgeTranslates selected dApp callsHive custom JSONBroadcasts application data

Understand the Hive Engine bridge. A connected application can request a token transfer through custom JSON. Always inspect the contract identifier, symbol, quantity and destination before signing.

07 · WALLET SECURITY

Your authority stays
under your control.

Local encrypted storage, role separation and device-assisted unlock reduce everyday exposure. Strong security still depends on a trusted package, protected device and independent recovery material.

Local encrypted storage

Selected role keys can be stored in an AES-based encrypted wallet file rather than on a custodial server.

Biometric convenience

Optional native keychain and biometric retrieval can reduce repeated password entry on supported devices.

Least-privilege account access

Choose posting or active authority according to the operation and keep the owner credential outside everyday wallet use.

Clear signing confirmation

Review the account, operation, asset, recipient, amount and memo before a locally signed transaction reaches RPC.

08 · RECOVERY & CONTINUITY

Keep access beyond
a single device.

Your Hive account lives on-chain, not inside one installation. Protect valid role credentials—especially owner control—and test a recovery path before the current device is lost or replaced.

01

Inventory before moving

Record every account and the relevant role keys, plus non-liquid states such as savings, pending rewards, conversions, delegations, orders and Hive Engine balances.

02

Test recovery before you need it

Restore only the minimum authority required in a trusted environment and confirm access with a low-value operation before relying on the setup.

03

Rotate after exposure

If a device or role key may be compromised, use protected owner authority to replace affected roles, verify authorities and only then retire the old installation.

Before installation

  • Verify the domain, repository, package ID and publisher
  • Match the signed binary to reviewed source and release evidence
  • Confirm supported OS and an independent recovery path

Before every signature

  • Identify the requested operation and effective authority
  • Verify account, recipient, amount, symbol and memo
  • Inspect custom JSON and never use owner for routine work

After broadcast & periodically

  • Record the transaction ID and verify it independently
  • Relock the wallet and clear unneeded dApp permissions
  • Audit authorities, recovery account, delegations, power-downs, savings and open operations
09 · PRIVACY BY DESIGN

Local keys do not make
public activity private.

Wallet keys can remain local, but Hive is a public blockchain. HIVE Wallet separates local signing from public account activity, RPC metadata and connected-application permissions.

01

Public account graph

Hive account names, balances, votes and operations are publicly observable and can be linked over time.

02

RPC metadata

A remote JSON-RPC operator may observe IP address, timing, queried accounts and request patterns even though private keys should remain local.

03

Embedded browser boundary

A dApp loaded inside the wallet has its own origin, scripts and trust assumptions. Review permissions and the exact operation before approval.

DESKTOP PACKAGES · VERSION 4.2.1.1

One wallet. Choose your platform.

Use the same Hive account, native assets and local-signing workflow on Windows, macOS or Linux. We highlight your current device; confirm its operating system and architecture, verify the SHA-256 digest, then install the matching package.

x64 installer

Windows

4.2.1.1
Version4.2.1.1Download size42.3 MB
hiveWalletInstaller-4.2.1.1-windows-x64.exe
SHA-256 digest0FB9BEF0416C9D870D27F56018CF26FCEDC098134939A3BFBDC3DEA53A2D7BDF
Download for Windows
Apple Silicon installer

macOS

4.2.1.1
Version4.2.1.1Download size32.1 MB
hiveWalletInstaller-4.2.1.1-macos-arm64.dmg
SHA-256 digest3C7673E5F9794DFF3BBE617CD836972DFF4AB4DD5F7CE44BA94F7A0F008E3B99
Download for macOS
AMD64 executable

Linux

4.2.1.1
Version4.2.1.1Download size71.6 MB
hiveWalletInstaller-4.2.1.1-linux-amd64
SHA-256 digestF7B5A71062F5B6E8F43F3E5A2ADBDD6CC8067A0ED71D45766392F6BDC005B0E4
Download for Linux

Verify before first launch. Compare the downloaded file with its published SHA-256 digest. A matching checksum confirms file integrity, not publisher identity; keep owner authority offline until the application and recovery path are independently verified.

11 · WALLET FAQ

Everything to know
before your first transfer.

Start with the verified desktop application for your operating system, complete account access, and only then authorize the web connection. Review native assets, role keys and every signing request before approval.

01How does desktop-to-web authentication work?+

First, open Downloads and choose the application that matches your operating system: Windows x64, macOS Apple Silicon or Linux AMD64. Verify the package, install it and open HIVE Wallet. Sign in with an existing Hive account, or complete the registration and account setup flow if you are a new user. After the application session is active, return to the web interface and request authentication. The web connection is then presented inside the desktop application for your review and approval. Never enter an owner key, master password or recovery material directly into a website.

02Which cryptocurrencies does HIVE Wallet support?+

HIVE and HBD are the two native liquid assets at the center of the wallet. Hive Power, VESTS, Resource Credits, savings and rewards are account states or network functions, while selected Hive Engine actions use connected custom-JSON requests.

03Is HBD the same as US dollars or USDC?+

No. HBD is a Hive-native dollar-oriented asset governed by blockchain feed, conversion and debt-ratio mechanics. It is not fiat in a bank and is not USDC or USDT.

04How do I access my Hive account?+

Hive uses a readable account name plus role-specific credentials: owner, active, posting and memo. The wallet flow is not based on a conventional BIP39 seed phrase. Keep owner or master recovery material offline.

05Should I import the owner key into the wallet?+

Not for daily activity. Owner authority is the highest recovery-sensitive permission. Keep it offline and use the least-privileged role that can authorize the intended operation.

06How does it work with Hive Engine?+

A connected Hive application can request selected token actions through custom JSON. Review the contract identifier, token symbol, quantity, destination and authority because a bridge request is different from a fully native token portfolio.

07Is this a full Hive node?+

No. It is a light client that reads chain data and broadcasts through remote JSON-RPC endpoints. Signing occurs locally when the relevant private key is available.

08Which desktop package should I choose?+

Use Windows x64 for 64-bit Windows, macOS ARM64 for Apple Silicon Macs, or Linux AMD64 for 64-bit Linux. Compare the downloaded file with the SHA-256 digest shown on this website before opening it.

YOUR HIVE ACCOUNT · YOUR AUTHORITY

A focused wallet
for everyday Hive.

Install the desktop package for your platform, add only the authority you need and keep owner recovery control offline.

Download HIVE Wallet