Using graffiti-file flag
--graffiti-file
flag for the validator client enables the wonderful feature where validators
could use different graffiti for different validators running in the same running process.
Reasons may include:
- Privacy (same graffiti may link validators)
- Fun (graffiti wall, etc)
Usages
The validator flag: --graffiti-file=/path/to/graffitis.yaml
It supports yaml and the following scalar and collections. We will go through each of them in detail below.
- Specific
- Random
- Default
Specific usage
Specific chooses the graffiti based on the validator ID. When validator ID is not specified, a graffiti will be chosen from the random
list. This takes precedent over random and default.
Example:
Example output:
Random
Random chooses a random graffiti from the list. If random
is not specified, the default
graffiti will be used.
This takes precedent over default.
Example:
Example output:
Default
Default specifies the graffiti to be used by all the keys under validator client.
Example:
Example output: