Skip to main content

Zazen Snap FAQ

Overview​

Zazen is a MetaMask Snap that provides a secure, encrypted storage solution for your ZenChain validator node cloud access keys directly within MetaMask. By integrating key management into your wallet, Zazen simplifies the process of deploying and accessing your validator nodes without the need for external password managers or manual key handling.

Key Features:

  • Secure Storage: Zazen encrypts your cloud access keys, storing them securely within MetaMask's storage. This ensures that your sensitive information remains protected at all times.
  • Easy Access: Quickly deploy or log into your validator nodes without the hassle of managing keys externally. Zazen streamlines your workflow by keeping everything within MetaMask.
  • Future Expansion: Planned features include support for additional types of sensitive data and enhanced key management functionalities, providing greater flexibility and utility.

Technical and Security Considerations:

  • Encrypted Storage: Your keys are encrypted and stored securely within MetaMask's storage, accessible only when MetaMask is unlocked.
  • Permissions: Zazen requires the snap_manageState permission to manage the encrypted state within MetaMask.
  • Open-Source: Zazen is open-source, allowing transparency and community contributions to enhance security and functionality.
  • MetaMask Integration: Seamlessly integrates with MetaMask, ensuring a smooth and secure user experience without the need for additional software.

FAQ​

Q1: What is Zazen Snap?

A: Zazen is a MetaMask Snap that securely stores your ZenChain validator node cloud access keys within MetaMask, acting as a password manager for these keys. It allows you to easily deploy or log into your validator nodes without managing keys separately.

Q2: How does Zazen store my cloud access keys?

A: Zazen encrypts your cloud access keys and stores them securely within MetaMask's storage using the snap_manageState permission. The keys are stored in an encrypted format, ensuring they remain protected even if the storage is accessed externally.

Q3: Do I need to interact with Zazen directly to manage my keys?

A: No, once the Zazen Snap is installed, it works automatically in the background when you use the ZenChain Station dApp. When you submit your cloud access keys through the dApp, Zazen securely stores them within MetaMask, so you won't have to enter them again in the future.

Q4: How do I use Zazen to manage my keys?

A: Simply install the Zazen Snap when prompted by the ZenChain Station dApp. After installation, there's no need for further action. When you input your cloud access keys into the dApp, Zazen automatically encrypts and stores them securely within MetaMask. The next time you use the dApp, Zazen will retrieve your keys automatically, enhancing your user experience by eliminating the need to re-enter your keys.

Additional details on this can be found in our Knowledge Base.

Q5: Is my data secure with Zazen?

A: Yes, Zazen encrypts your cloud access keys before storing them, and the encrypted storage is only accessible when MetaMask is unlocked. This ensures that your sensitive information remains secure within your MetaMask wallet.

Q6: Can Zazen store other types of data?

A: Currently, Zazen focuses on storing cloud access keys for validator nodes. However, future versions may include support for additional types of sensitive data and expanded functionalities, providing greater flexibility.

Q7: Do I need any special permissions to use Zazen?

A: Zazen requires the snap_manageState permission to manage the encrypted state within MetaMask. When installing the Snap through the ZenChain Station dApp, you will be prompted to grant this permission. No additional configuration is required.

Q8: How do I install the Zazen Snap?

A: The ZenChain Station dApp will request to install the Zazen Snap when you connect your MetaMask wallet. Simply approve the installation and permission requests when prompted.

Q9: Is Zazen open-source?

A: Yes, Zazen is open-source and was forked from the MetaMask manage-state example snap at version 2.2.2. You can review the code and contribute via the GitHub repository.

Q10: Who can I contact for support?

A: For support, please refer to the Knowledge Base document or reach out to our support team.