Zen Protocol Documentation
WebsiteTelegramBlogForum
  • Zen Protocol Docs
  • Apps
    • Headless Full Node
      • Full Node NPM Package
      • Build from Source
      • CLI
      • API
        • Wallet
        • Contracts
        • General
        • Blockchain
        • AddressDB
      • Deploy
        • Systemd
        • Shell script
        • Docker
      • Technical Model
      • AddressDB
    • Wallet
      • Desktop Wallet
        • Installers
      • Web Wallet
        • Run Locally
      • Wallet User Guide
        • Connect a Wallet
          • Create a Wallet
          • Import a Wallet
          • Watch Mode
        • My Wallet
          • Navigation Bar
          • Portfolio
          • Receive
          • Send / Execute
          • Transaction History
        • Contracts
          • Active Contracts
          • Execute a Contract
            • Message Body Field
          • Extend a Contract
          • Activate a Contract
        • Voting
          • Common Goods Pool
            • Generating a Ballot ID
          • Governance
        • Signer
        • Settings
          • Account Settings
          • Node Connectivity
      • Deprecated Desktop Wallet
        • Executable Installers
        • Wallet Structure
          • Video Tutorials
    • Explorer
    • Zen.js
      • Payment Processing
    • Oracle
      • Oracle GUI
      • Oracle Service
      • Oracle's API
      • Deploy
        • Systemd
        • Docker
      • How the Oracle contract works
      • How to create an Attestation token
    • Dex
      • Dex User Guide
        • Traded Pairs
        • Search Pairs
        • Order Book
        • Operations
        • My Wallet
        • Settings
      • How DEX contract works
    • Fixed Payout
      • Fixed Payout Generator User Guide
        • Issue
        • Redeem
        • Cancel
        • Verify
        • Settings
      • How the FP Contract works
      • How are the asset named?
  • Smart Contracts
  • Contract Structure
  • Contract Cost
  • Contract Activation
  • Contract Examples
  • Smart Contracts SDK
  • Contracts Language ZF*
  • Named Token Tutorial
  • Consensus
  • Common Goods Pool
  • Block Validation
  • Transaction Validation
  • Serialization
  • Use Cases
    • Create Unsigned Transaction
    • Secure Sign Transaction
    • Cold Storage using Full Node
  • Troubleshooting
    • Responsible Disclosure
    • Bug Bounty
    • Known Bugs
  • For Miners
    • Pools
    • GPU Mining
    • GPU Bounties
  • Check Crowdsale Contribution
  • Alpha call option
Powered by GitBook
On this page
  • Desktop Wallet
  • Desktop Wallet Full Node
  • Web Wallet
  • Difference between the wallet versions
  1. Apps

Wallet

The Zen Protocol Wallet is designed to give users complete control over their financial assets by making ZP easy to use, creating and interacting with smart contracts and voting for the next upgrades.

PreviousAddressDBNextDesktop Wallet

Last updated 1 year ago

Please note that the use of the software is subject to the terms of its and .

Desktop Wallet

Using the Desktop Wallet is the most secure way to validate the network, make transaction and run smart contracts.

Desktop Wallet Full Node

This mode allow to connect to a local node using the addressdb module.

zen-node --connectwallet

Then in the Desktop wallet under Settings -> Node Connectivity you can choose one of the localhost node.

Web Wallet

Difference between the wallet versions

Web Wallet

Desktop Wallet

Chrome Desktop App (PWA)

Store Seed

Encrypted using a password of your choice and stored in local storage

Encrypted using a password of your choice and stored in local storage

Encrypted using a password of your choice and stored in local storage

Blockchain

Validation

Uses a "trusted" remote node to sync with the blockchain and validate the consensus rules, and relays signed transactions on its behalf

Uses a "trusted" remote node to sync with the blockchain and validate the consensus rules, and relays signed transactions on its behalf.

This is the only way for you to connect to a local node running in the localhost network

Uses a "trusted" remote node to sync with the blockchain and validate the consensus rules, and relays signed transactions on its behalf

Access

Is via a web browser, which can be compromised in multiple ways such as

* If the server that is serving the client gets hacked, the hacker could deliver a version of the website that steals your seed.

A desktop application to your computer once from a trusted source.

A PWA is a web application that can be “installed” on your system, which can be compromised in multiple ways such as

* If the server that is serving the client gets hacked, the hacker could deliver a version of the website that steals your seed.

* having a

* - someone could create a website with a domain that looks very similar to the real official wallet domain and serve a malicious version of the wallet.

* having a

* - someone could create a website with a domain that looks very similar to the real official wallet domain and serve a malicious version of the wallet.

licence
Authorized Protocol
Desktop Wallet
Web Wallet
malicious Chrome Extension
Phishing
malicious Chrome Extension
Phishing