HF28, scheduled for 19.11.2025, introduces strict authority checking, which may affect some Ledger users. This guide explains the change and outlines the steps required to update your account for full compatibility.
You may encounter the above error message if your account is configured in a way that does not derive all key roles from your Ledger device—for example, if only the owner key was replaced during the account association process.
Chierarchical key roles on Hive
Up until now, Hive blockchain used hierarchical keys that could have posting, active and owner roles. Posting may be used for social interactions, comments and some rewards' claiming actions, active could authorize monetary operations like transfers or staking, and owner could do anything including changing other keys.
While it has always been recommended to avoid using the owner key for daily operations—especially across various frontends—hiveledger.io relied on it to simplify account discovery. When signing via Ledger, the private key never leaves the device and every action requires physical confirmation, so this was considered safe.
Strict authority checking
Beginning with HF28, this is no longer possible. The blockchain now enforces the use of the correct key role when generating signatures for specific operations. For example, to vote for @engrave witness you need the active key, but to claim pending rewards - posting.
What should I do?
Upon logging in to hiveledger.io, you will see a colored dot next to your account name. This indicator shows whether your account is fully configured—with all three keys derived from your Ledger device.
If you see a green dot, no action is required. You shouldn't see the error message from the header image.
If you see a red dot, you must add missing authorities derived from Ledger device.
Manage authorities to add missing roles
Adding a missing role consists of two steps:
- Derive the new key from your Ledger device.
- Update the corresponding authorities to include this key.
Hive Ledger Wallet streamlines this process.
- Open
Advancedtab.
- Scroll to the appropriate form. It's recommended to begin with
Active Authorities. - Click
Add Public Key.
- Click
Get from Ledger. Make sure your device is connected and unlocked, otherwise you will see the error message.
- Once the key is retrieved from the device, click Add public key. The form will be updated with the new key.
- You should now see the new key marked with
[L]icon, indicating it is stored on the Ledger device. - Click
Save changes.
- Review and approve the transaction that will update your authorities.
- You should now be able to use your new key. Let's try voting for @engrave witness!
You can see proper
activerole being used now.
If needed, repeat the process for the
postingrole.