TIP <new>: Native Account Inheritance Mechanism #811
Conversation
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
Author
|
This Pull Request introduces the Native Account Inheritance mechanism: #810 Feedback, suggestions, and reviews from the community and maintainers are warmly welcome. |
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.
Summary:
This PR introduces a new feature to the TRON network allowing users to define a time-based inheritance key for their accounts. After a predefined period of owner inactivity, the inheritance key can manage account assets without exposing private keys, without requiring smart contracts, and without additional gas fees.
Motivation:
In current blockchain architectures, asset ownership is entirely dependent on the private key. In cases of death, cognitive illness, coma, or permanent loss of the seed phrase, digital assets become permanently inaccessible. This TIP adds a native account inheritance mechanism that prevents irreversible asset loss and provides a secure recovery path.
Backwards Compatibility:
Fully optional; does not change the behavior of existing accounts.
Requires no smart contracts and has no dependency on specific wallets.
Completely independent of TIP796 or any other TIP, ensuring no conflicts.
Important Note:
This PR is fully independent of TIP796 (Username addition to accounts). All commits are specific to the inheritance feature, and no changes are made to previous branches or PRs.