HF15: permanent key history + hourly limit on active/regular/memo - #168
Merged
Merged
Conversation
…tive/regular/memo changes Consensus keeps one row per member of every authority an account stops standing behind (role, key or account, weight, threshold, valid until block/time), written by account_update, recovery, direct sale and auction close. Rows are never removed, so a DLT node can prove which key an account held in the past. From HF15 a real change of active, regular or memo_key is limited to once an hour per role, like master. read API: database_api.get_key_history / get_key_history_by_key. Snapshot exports and imports the new index. Docs en+ru.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
A DLT node has no past blocks, so it cannot prove which key an account held when it signed something. From HF15 consensus keeps a permanent row for every member of every authority an account stops standing behind.
key_history_object: account, role (master/active/regular/memo), key or member account, weight, threshold,valid_until_block/valid_until_time(last block the key still held). Written by account_update, recovery, direct sale and auction close; only for roles that really changed. Never pruned.database_api.get_key_history(account, from, limit),get_key_history_by_key(key, limit).New object type → testnet redeploy from snapshot only.
🤖 Generated with Claude Code