Gjcb posting key password#

Never copy the master password into posts or transaction memos.

Gjcb posting key how to#

See CLI Wallet's get_private_key_from_password or Hive-python's () on how to derive the keys.Дon't use the master password to log into Hive.blog or any other Hive application. Having the master password enables to retrieve all private keys of an account. A hashing function calculates the corresponding private and public keys from the master password, the account name and the key type ('posting', 'active', 'owner' or 'memo').

The master password is used to derive all keys above. The owner key is not directly visible on the Hive.blog website but can be derived from the master password using the CLI Wallet or an API Library like Hive-python. Loss of this key severely limits the operation of the account. With this key your account can be completely taken over by a malicious party.

This is the key that should be most carefully safeguarded against loss or theft. It is the key required to change all the other keys. The owner key is the key with the highest privilege level. The memo key is the only key that can encrypt and decrypt private messages sent and received via your account. The Memo Key is used for handling private messages and encrypted transaction memos. The active key should ONLY need to be used to confirm transaction or trades or change user settings.Дo not use your active key to log in for posting and upvoting on a daily basis. The posting key offers the safest way to access your account on a regular basis and it is recommended that you develop the habit of using it as your primary way of logging into your account. It limits the privilege of the person using it to functions that do not have access to the wallet, thereby maintaining the safety and security of the tokens.

The posting key is the safest way to log into an account. The posting key is used exclusively for submitting posts, applying upvotes and downvotes, selecting and deselecting followers, muting accounts and claiming reward balances. Keys should be stored privately and safely. Loss of your keys will result in loss of access to your account. If you get hacked you are giving them access to every key you own on Hive. If you don't manage your keys correctly, you are putting your account at risk. He wrote a script and warned all steemians caught in the same mistake. In June 7th 2017 Krzysztof Szumny ( found a flaw in design that made his cousin accidentally pasted his own password into wrong field (a memo field), when he made a transfer.

Gjcb posting key generator#

Fabian Schuh post on a Hive Paperwallet Generator is an excellent resource. Use a safe deposit box for best redundancy.

Consider digital offline storage, such as an external disk or flash drive, as well as printed paper. It is also a strongly recommended that you store an offline copy of your password somewhere safe in case of a hard drive failure or other calamity. There is no way to recover your account if you lose your password or owner key! Because your account has real value, it is very important that you save your master password somewhere safe where you will not lose it. The Hive.blog FAQ explains why the password is long and random for maximum account security. If logging in with your post key, make sure you don't overwrite or misplace your original master password. The master password is used to derive all keys for your account, including the owner key. To keep your Hive account secure you must save your master password and keep it somewhere safe.