AppAgent Owner
Last updated
Last updated
The AppAgent owner is a regular blockchain address granted full control over the AppAgent. As the owner, this address possesses the authority to initiate various actions and operations related to the AppAgent including its management, configuration, and utilisation. This control typically includes the ability to modify settings, trigger events such as pausing or destroying the AppAgent, and access any associated resources or assets owned by the AppAgent.
The initial owner of the AppAgent is the address that created it. This ownership can be transferred.
The best way to create and manage AppAgent Owner address is to use TRAIT Vault, an air-gapped wallet capable to sign the transactions to manage AppAgent. Read more about TRAIT Vault.
The recommended best practice is to use Owner address only for configuration of AppAgent and its admins. And use AppAgent' admins to perform most administrative tasks such as mint/burn/transfer tokens. Learn more about AppAgent Admins.
The owner address has full control over an AppAgent, hence this address and its private key should be treated with utmost care and only a limited set of key stakeholders of your organisation should have access to it.
It's crucial to understand that if the keys are lost and no backup exists, they cannot be recovered by any centralised authority or third party. This is a fundamental aspect of blockchain technology where users have full control over their assets and identities without reliance on intermediaries. As a result, users must take personal responsibility for securely managing and backing up their blockchain keys to prevent loss or unauthorised access to their assets.
You MUST backup private key of AppAgent owner.
Best practices for backing up blockchain keys include:
Use Secure Storage: Store backups in secure and reliable locations, such as hardware wallets, encrypted USB drives, or offline paper wallets. Avoid storing keys on easily accessible or compromised devices.
Multiple Copies: Create multiple copies of backups and store them in different secure locations.
Regular Updates: Update backups regularly, especially when generating new keys or making significant transactions. This ensures that backups are up-to-date and reflect the latest state of the blockchain keys.
Test Recovery: Periodically test the backup and recovery process to ensure that backups are accessible and functional. This helps identify any issues or discrepancies in the backup system before an emergency occurs.
Read Intro to blockchain addresses and keys for more information.