Skip to main content

FAQ - Beta Test Program

info

Note: This FAQ is geared towards ZKN's Walletshield Beta Testing Program and will be replaced as the network client and deployments evolve.

General​

What is Network ID ?​

A Network ID is a unique identifier for a ZKN privacy network deployment. For the purpose of the beta testers program, it serves as your access token. As such, please protect the privacy of the Network ID to improve the quality of network testing. The Network ID is required to instruct client apps how to connect to the networks. Within the following instructions, replace <network_id> with the actual Network ID.

Where do I find the Network ID ?​

Join the waitlist for early access to ZKN's Walletshield app, now in a gated Beta Testing Program. Find the current Network ID in the pinned posts of the ZKN Beta Tester chat group on Telegram or Discord that you were invited to.

Why can't I connect to the network ?​

If your device is connected to the Internet, then likely you are using an expired or otherwise incorrect Network ID. Check your Beta Tester group for latest Network ID, and ensure it is typed correctly.

Network IDs will expire over the course of the testing program with a new Network ID being issued for each network upgrade. It is also advised to ensure the client (terminal or GUI) is the latest version as well.

Will the client run on MacOS, Windows, or some other platform ?​

As of network deployment v0.4.2, supported platforms include:

  • Windows (x64)
  • MacOS (both darwin-amd64 and darwin-arm64)
  • Linux (linux-x64 and linux-arm64)

Support for other platforms is under development as the mix network's cryptographic libraries become more cross-platform. Support is planned for all major platforms, including Android and iOS, with an initial focus on Desktop.

Why does the Beta Program work this way?​

To enable early testing of ZKN client applications while enhancing the quality of feedback from testing, some initial manual steps are required. These temporary processes will be replaced by integrated automation to seamlessly transition to concurrent network deployments as the system evolves.

What specifically is being tested within the beta testers program?​

Beta testers primarily assess the stability of the latest network deployments, which include continuous upgrades to client and server components. They offer usability feedback, insights into user interactions with the system, and test compatibility across various operating systems, browsers, wallets, and blockchains. This includes evaluating blockchain transactions such as token transfers, swaps, and smart contract interactions.

Is it useful for me to test running the client on multiple machines simultaneously?​

No. The ZKN network deployment lifecycle already includes lab tests to tune and establish theoretical and measured network capacity. After tuning, mix networks are deployed as testnets for beta program users. Capacity testing within the beta program is not useful and may reduce the quality of more valuable feedback.

Can I run the ZKN client on a remote server?​

No. Metadata privacy for your local device requires the client to run on the same machine as the wallets using it. Alternatively, if you trust your local network and understand its "observability," you could run the client on one computer within your network and connect to it from others. However, while it may function, running it remotely exposes the data to metadata surveillance and potentially cleartext transmission. For optimal privacy, run the client on the same device as your wallets.

Walletshield Application​

Do I need to spend crypto tokens or pay gas fees?​

The Walletshield works the same for both blockchain main and test networks. Networks will incur the same fees regularly associated with them, like gas fees. Using test networks is a great, and inexpensive way to test the Walletshield. Send many transactions! Send to yourself and others in the Testers program. While the process varies, most testnets have faucets providing free tokens. Refer to the following resources for more info:

Do I need to run a client for each wallet or network I want to use with it ?​

No. A single client and Walletshield app instance can serve multiple wallets configured to use it.

Are Walletshield RPC transactions slower than normal?​

At times RPC requests may be slower as small delay is an inherent characteristic of strong anonymity to conceal timing info. The mix network academic literature refers to this aspect as the Anonymity Trilema. While some delay is a "feature" for privacy, one of the ongoing missions of the private testnet is to continually tune the deployments for the applications. Response timing should be within the acceptable range for most crypto wallets. If, by chance, a transaction does fail as a result of the Walletshield and mix network delay, you can safely try again. The delay is variable each time. We want to collect feedback from testers within this area specifically.