Frequently asked questions

Hive is the public blockchain behind the online part of 4th Street Bar. Your Hive account can hold balances and can also publish posts, comments, votes, and other account activity that compatible Hive apps can read.

No. Anyone can browse without signing in. If you want to participate, Hive-Bar shows the human-readable action first and Hive Keychain asks you to approve anything that needs your account authority.

Not for browsing, and a new account with the bar’s starter Hive Power delegation is intended to have enough Resource Credits for ordinary social actions such as posting, commenting, and voting. Features that actually send HBD—such as a paid Wall message or encrypted private message—require enough HBD to cover the amount shown before you approve it.

Hive Keychain is the wallet/signing tool that holds your private keys. Hive-Bar asks Keychain to sign or approve an action; Hive-Bar does not ask you to paste private keys into this site. Signing in verifies your account with a signed message and does not itself broadcast a Hive transaction.

Your Hive wallet is part of your Hive account, not money held by Hive-Bar. The wallet page here is a read-only view of public blockchain data. Hive-Bar cannot move those funds or recover your private keys from the wallet page.

HIVE is Hive’s liquid native token. Its market value can rise or fall. HIVE can be held or transferred, and it can also be powered up into Hive Power.

HBD means Hive Backed Dollar. It is Hive’s blockchain-native stablecoin, designed to track roughly one U.S. dollar. It is not a bank deposit or a guaranteed dollar peg, and its market price can move above or below $1.

Hive Power is the powered-up, or vested, form of HIVE. It helps determine an account’s Resource Credit capacity and its influence when voting. HP is different from liquid HIVE that you can immediately transfer.

Resource Credits, usually called RC, are an account’s capacity to perform actions on Hive. Posts, comments, votes, and transfers consume some RC. RC is tied to Hive Power, is not a spendable token, and regenerates over time.

Voting power is the renewable voting resource behind your upvotes and downvotes. A stronger vote uses more of that resource; it refills over time. Vote weight lets you choose how much voting strength to use on one vote.

Hive can assign rewards from eligible posting and voting activity. When rewards are ready, the wallet can show the claimable HIVE, HBD, or Hive Power. Claiming is an account action that you review before Keychain approves it.

The bar temporarily delegates Hive Power to the new account so it has Resource Credits to participate. That HP is not transferred to you as liquid HIVE, cannot be spent by you, and remains owned by the delegating account.

No. Your private credentials are generated in your browser and the bar receives only the public keys needed to create the account. The creating account becomes the initial Hive recovery account, but that recovery role does not give the bar your private keys.

It contains the private credentials generated for your new account. Store it somewhere private and protected. Do not give it to the bartender, post it, email it casually, or paste it into Hive-Bar.

Hive-Bar does not keep a copy. If you also lose every working copy of your account credentials, Hive-Bar cannot simply recreate those keys for you. Treat the recovery file as something you need before you leave account setup.

They are public Hive activity. Other Hive websites and blockchain tools can read them too. Think of a Hive post or comment as public publishing, not a private social-media draft.

Yes. The Wall message, sender, recipient, HBD payment, time, and transaction are public on Hive. The page shows the recipient’s minimum HBD amount before Keychain asks you to approve the transfer.

The message text is encrypted by Keychain in your browser and decrypted locally for the recipient. The blockchain still exposes transaction metadata such as who sent it, who received it, the HBD amount, time, and transaction. Do not treat that metadata as private.

That is the safety boundary. Hive-Bar prepares the requested operation and shows you a review step; Keychain holds the signing authority. If the action or account shown in Keychain is not what you expected, cancel it.