nym/clients/credential at 3e2009aa9d228b549da2c19e7e4de59e32c08d21 - nym

GRIN/nym

Files

T

Jon Häggblad dc5c765ecb Last set of crates to add the nym- prefix to (#3286 )

* Add nym- prefix to mixnode-common

* Add nym- prefix to mixnet-client

* Add nym-client- prefix to websocket-requests

* Makefile: add check target

* Rename to nym-credential-client

* rustfmt

* update to nym-credential-client in github workflow

2023-04-07 21:25:28 +02:00

src

Add more nym- crate prefixes (#3284 )

2023-04-06 09:04:49 +02:00

Cargo.toml

Last set of crates to add the nym- prefix to (#3286 )

2023-04-07 21:25:28 +02:00

README.md

Add sandbox.env and update credential readme

2023-03-27 13:49:14 +03:00

README.md

Credential binary

The credential binary is used to acquire coconut bandwidth credentials in exchange for nym tokens. Those credentials are stored in the client's data directory, so that they can be used as the client sees fit.

Warning

The credential binary is still experimental software. The infrastructure for using it is not yet deployed to mainnet and it's still in the process of being deployed to sandbox.

Building

From the project's root directory, run:

cargo build -p credential

which generates the credential binary in target/debug/credential.

Running

For example, you can get a credential worth 3 nym (3000000 unym) in a socks5 client that was already initialized like so:

./target/debug/credential --config-env-file envs/sandbox.env --client-home-directory  ~/.nym/socks5-clients/cred_client  --nyxd-url  https://sandbox-validator1.nymtech.net --mnemonic $MNEMONIC  --recovery-dir /tmp/recovery --amount 3000000

More information regarding how to run the binary can be found by running it with the --help argument.