πŸ›‘οΈAbout Security

Q:What measures are in place to protect user data?

Access Control: ACL rules for access control management can be configured by setting the schema of a collection.

Encryption: Columns in a database can be encrypted

Data Redundancy: User data is persisted to Arweave through the data block, ensuring permanent storage. In any situation, users can recover their data directly from Arweave.

Consensus Algorithms: Aside from writing each data block to Arweave, GlacierDB generates a data proof for each block and writes it to the L1 contract to ensure the changes made are irreversible.

Q: What is the process for protecting a user's GID account and access keys if their wallet is compromised?

A Gid can be bound to multiple wallets, and users can set one of them as the controller wallet.With the controller wallet, users can revoke the permissions of other wallets. To maintain security, users can keep the controller wallet in a cold wallet and use other normal wallets for daily signing and interaction. In case the private key of a normal wallet is compromised, the user can utilize the controller wallet to revoke its permissions. However, if the private key of the controller wallet is compromised, it will result in the loss of data ownership. For users with higher security requirements, multisign can be utilized to manage their controller wallet.

Last updated