FORM 8453 // KEYCHAIN GETTIN'-STARTED INSTRUCTIONS

Hive & Hive Keychain

The followin' sections describe the Hive blockchain credential system, the Hive Keychain custody application, an' the procedures applicable to a Taxed-issued Hive account. Compliance is recommended.

This document is informational. The Tax Office don't warrant the third-party software described herein. Where third-party screenshots or links is referenced, they're provided as a public service.

TABLE OF CONTENTS

  1. 1. What is Hive?
  2. 2. What is Hive Keychain?
  3. 3. Installin' Keychain
  4. 4. The Four Keys — Deep Dive
  5. 5. Importin' yer Taxed-issued account
  6. 6. Account Recovery
  7. 7. Security Best Practices
  8. 8. Common Errors
  9. 9. Goin' Deeper

SUBSECTION 1

1. What is Hive?

Hive is a public, permissionless blockchain that records ledger state, signed messages, an' digital-asset transfers in publicly verifiable form. The protocol is run by a global network o' independent witnesses; no single feller owns it. Hive accounts is first-class citizens o' the protocol — they're referenced by name (handle), not by an opaque address. That's unusual fer public blockchains an' is the source o' the user-friendly account model Taxed builds on.

Each account on Hive carries an internal allowance o' Resource Credits, called RC fer short, which it spends to broadcast transactions. A new account is issued with zero RC an' has gotta accumulate Hive Power before it kin transact directly on chain. Until then, the account exists in the registry but kain't publish operations o' its own. Fer Taxed enrollees, this ain't no obstacle: every Taxed transaction touchin' Hive is signed an' broadcast by @taxed, not by yer account, an' Resource Credits is paid by @taxed in every case.

Accounts on Hive is permanent. There ain't no concept o' account deletion. The handle reserved by the registrar at the moment o' creation is the handle o' the account fer good. The keys kin rotate; the handle does not.

SUBSECTION 2

2. What is Hive Keychain?

Hive Keychain is a free, open-source custody application maintained by independent contributors. It's available as a browser extension fer desktop platforms an' as a standalone mobile app fer Android an' iOS. Its function is to store Hive private keys locally — never on a remote server — an' to sign transactions on yer behalf when authorized via a popup confirmation.

Keychain is the goin' standard custody tool in the Hive ecosystem. The Tax Office recommends, but don't require, its use. Alternative custody approaches include hardware-wallet rigs (Ledger), desktop wallet apps, an' self-managed cold storage. The rest o' this document presumes Keychain.

Keychain ain't affiliated with the Tax Office. The Tax Office don't develop, distribute, or warrant Keychain. Any defect, breach, or compromise o' Keychain is the responsibility o' its publisher.

SUBSECTION 3

3. Installin' Keychain

3.1 Desktop installation (Chrome / Brave / Edge / Firefox)

  1. Visit the Keychain website (hive-keychain.com) an' choose the right browser.
  2. Confirm the installation in yer browser's extension marketplace. Make sure the publisher field reads "Stoodkev" or the official mainteiner of record.
  3. Pin the extension to yer toolbar fer one-click access.
  4. Open the extension an' follow the on-screen instructions to set a local PIN. This PIN protects Keychain locally only; it don't protect yer account on chain.

3.2 Mobile installation (Android / iOS)

  1. Download Hive Keychain Mobile from the Apple App Store or Google Play Store. Verify the publisher.
  2. Open the app an' create a local PIN.
  3. The mobile app supports the same set o' import an' signin' operations as the desktop extension.

The Tax Office don't host installation media. Apply ordinary diligence in confirmin' the publisher o' the software ye install.

SUBSECTION 4

4. The Four Keys — Deep Dive

Every Hive account is governed by four cryptographically distinct private keys, each carryin' a different authority within the protocol. Loss o' the higher-authority keys is total an' permanent. The keys is issued in pairs o' public an' private; the public part is recorded on chain, the private part is held by the account holder.

Owner Key

The Owner key is the maximum authority. It kin rotate any o' the other three keys, transfer ownership o' the account, an' authorize the account-recovery procedure. It should never be loaded into a routine signin' tool. Use it only when initiatin' recovery or rotatin' other keys.

Threats: theft o' the Owner key results in total, irreversible compromise o' the account. The thirty-day recovery window described in Section 6 only mitigates this if the original Owner key was used to sign a transaction within the prior thirty days and a recovery account is designated.

Active Key

The Active key authorizes financial transactions: transfers, conversions, votin' fer witnesses, market actions, custom-JSON operations that move tokens. Fer a Taxed enrollee, the Active key is the key that authorizes deposits, withdrawals, an' WAGE exports.

Threats: theft o' the Active key allows the attacker to drain liquid funds. It does not allow rotation o' the Owner key, so account ownership is preserved if the Owner key remains intact. If the Active key is compromised, rotate it usin' the Owner key as soon as possible.

Posting Key

The Posting key authorizes social actions: posts, comments, votes on content, follows, custom-JSON operations classified as social. It kain't move funds. Many third-party Hive applications request only the Posting key.

Threats: theft o' the Posting key allows impersonation in social contexts but no financial loss.

Memo Key

The Memo key encrypts an' decrypts the optional memo field on Hive transfers. Encrypted memos use the recipient's public Memo key on the sender's side an' the recipient's private Memo key on the recipient's side. Memos themselves is stored on chain — only the contents is encrypted.

Threats: theft o' the Memo key allows decryption o' historical encrypted memos addressed to the account. It carries no other authority.

SUBSECTION 5

5. Importin' yer Taxed-issued account into Keychain

The reveal modal at the conclusion o' Form TAX-WHATEVER issuance includes a single-action OPEN IN HIVE KEYCHAIN button. On desktop browsers with the Keychain extension installed, the button triggers a native Keychain dialog that imports all four keys into the local keystore in one operation. On mobile, the equivalent action invokes the Keychain app via a URL handler; the user confirms the import inside the app.

If automatic import ain't available — fer example, if the extension ain't installed, the browser is in private-browsin' mode, or the URL handler is rejected — the reveal modal presents a COPY KEYS BLOCK action. The applicant copies the four-key block to the clipboard, opens Keychain manually, selects Add Account → Import using Keys, an' pastes the keys block into the input field. Keychain validates the block an' persists the account locally.

The Tax Office recommends the applicant verify successful import before closin' the reveal modal. The .txt file download is the canonical recovery artifact an' must be retained regardless o' whether Keychain import succeeded.

SUBSECTION 6

6. Account Recovery

Hive supports a protocol-level account recovery procedure. The procedure permits the account holder, with the cooperation o' a designated recovery account, to rotate the Owner key in the event o' compromise. The Taxed-issued account designates @taxed as the recovery account at the moment o' creation; this designation is recorded on chain.

The recovery procedure operates as follows. The account holder demonstrates control o' an Owner key that was active within the prior thirty days. The recovery account (@taxed) co-signs a recover_account operation that establishes a new Owner key. The protocol enforces the thirty-day window strictly; an Owner key older than thirty days ain't recoverable through this procedure.

To initiate recovery, the account holder files Form 1040-RECOVERY by contactin' Taxed support. The applicant must provide the previously valid Owner key, kept from the .txt download issued under Form TAX-WHATEVER, an' a new Owner public key. Taxed verifies the previous key matches the on-chain record within the thirty-day window an', if so, co-signs the recovery transaction.

The recovery procedure does not recover keys the applicant has lost without compromise. If the applicant has discarded the keys downloaded under Form TAX-WHATEVER, no recovery is possible. The keys ain't stored anywhere outside the applicant's possession.

SUBSECTION 7

7. Security Best Practices

  • Stash the .txt file in two locations. A local encrypted disk image plus a printed paper copy in a fireproof safe is a typical configuration. Cloud storage may be acceptable if the file is encrypted before upload. The Tax Office don't warrant any particular approach.
  • Never email the .txt file. Email ain't encrypted in transit by default an' is a frequent vector o' credential exposure.
  • Don't paste yer Owner key into any web form. The Owner key should never appear inside a routine signin' tool. Use Keychain or the Hive command-line tools when Owner-key operations is required.
  • Use the Active key fer routine financial operations. If the Active key is compromised, rotate it immediately usin' the Owner key. Account ownership is preserved.
  • Consider a hardware wallet fer high-value accounts. Ledger devices support Hive natively. The Owner key may be stored on the hardware device an' never exposed to the host computer.
  • Maintain backup copies o' the keys. Loss o' all copies is total. The Tax Office holds no copy.

SUBSECTION 8

8. Common Errors

"missing required posting authority"

The transaction requires a higher authority than the loaded key. Verify the Posting key (fer social) or Active key (fer financial) is loaded into Keychain.

"insufficient resource credits"

The account ain't got enough Resource Credits to broadcast. Fer Taxed-issued accounts, this is the expected state at issuance. Resource Credits accrue as the account stakes Hive Power, or transactions kin be sponsored by @taxed.

"invalid signature"

The key loaded into Keychain don't match the on-chain record. Verify the correct private key was imported an' that no characters got truncated durin' paste.

Keychain prompt don't appear

The browser extension may be disabled or not installed. Check the extensions settings o' yer browser. On Brave, additional shields may need to be lowered fer the Keychain popup.

SUBSECTION 9

9. Goin' Deeper

A game, buddy. Not financial advice. Not tax advice. Certainly not investment advice. No affiliation with any government agency, real or imagined.