As you know, the account recovery process is something I have worked on and written a lot about recently.
This allowed me to better understand the related transactions recorded in the blockchain. I also noticed that the related tables in HiveSQL were not that well organized (some early days errors)
So I took advantage of the HiveSQL reorganization work that I am currently carrying out to make some modifications.
TxAccountChangeRecovers has been renamed to TxAccountRecoveryChangesTxAccountRecovers has been split into TxAccountRecoveryRequests and TxAccountRecoveryConfirms.Therefore, we now have three new tables available:
TxAccountRecoveryChanges
This table contains operations broadcasted to the blockchain when users want to change their Recovery Account.
| Column | Description |
|---|---|
| account_to_recover | the account that wants to change its Recovery Account |
| new_recovery_account | the new Recovery Account |
TxAccountRecoveryRequests
This operation is broadcasted to the blockchain by the Account Recovery of an account that has been hacked to initiate the recovery process
| Column | Description |
|---|---|
| recovery_account | username of the Recovery Account |
| account_to_recover | username of the account to recover |
| new_owner_authority | new public owner key provided by the account to recover to the recovery account |
TxAccountRecoveryConfirms
This table contains operations broadcasted to the blockchain by the hacked account's owner to confirm the account recovery request sent by its Recovery Account.
| Column | Description |
|---|---|
| account_to_recover | username of the account to recover |
| new_owner_authority | new public owner key provided by the account to recover to the recovery account |
| recent_owner_authority | a public owner key of the account to recover before it was last changed |
This first change should make it easier to find information relating to the account recovery process.
As indicated at the beginning of this post, I have embarked on a work of reorganizing and improving the database. So expect to see more posts on this subject in the coming days.
If you have any questions or remarks, support is provided on the HiveSQL Discord Channel.
Thank you for reading.
Let's keep HiveSQL free to use - Support its proposals!