retrieve published mixnet configuration file

[xendarboh]

Implementation details are pending other developments that publish this information when a mixnet is deployed.

The idea is that client-side walletshield needs to know the mixnet configuration that has a dynamic nature for some settings when a mixnet is deployed.

When client starts, it retrieves a client.toml file served thru https://. If this file is unavailable (404) it also indicates the mixnet is unavailable.

Consider using a parm to configure multiple mixnet deployments (corresponding to different URL of files to retrieve). For example:

• ./walletshiled --deployment=test
• ./walletshiled --deployment=green (green vs blue deployments)
• ./walletshiled (use production by default)

Lifecycle

This feature supports compatibility with iterative testnets and may persist in some form in the context of testing deployments. This is expected to change in ways with deployment of the appchain-powered PKI.

[xendarboh]

a bash launcher script can provide an initial flexible solution while the implementation details for the deployment publication evolves

[xendarboh]

currently facilitated by this walletshield launcher script

https://github.com/0KnowledgeNetwork/apps/blob/main/walletshield.sh