Evernode.Forum

Config is located at...
/etc/sashimono/mb-xrpl/mb-xrpl.cfg

Just do a npm i evernode-js-client Run the script with node scriptname.js (and wait an hour for it to load all nodes) const fs = require("fs"); const evernode = require("evernode-js-client"); async function main() { evernode.Defaults.set({ governorAddress: "rBvKgF3jSZWdJcwSs...

Each instance has built in ssl keys, they are located at following:
/contract/cfg/tlscert.pem
/contract/cfg/tlskey.pem

Additionally, it seems like using the UNL keypairs for client-side communication alert violations too. Not always, but sometimes.

Violations are different "metrics" HotPocket uses to identify bad network peers. Violation means that peer has displayed some undesired network activity like sending malformed messages, abruptly dropping connection etc... Multiple repeated violations within a short time period will cause t...

First, write
sed -i s/800000/1000000/ /etc/sashimono/sa.cfg

then reboot your node by writing reboot

in the file, /etc/systemd/journald.conf you can uncomment and set the following setting:
SystemMaxUse=50M

Afterwards roll a systemctl restart systemd-journald

This will make your evernode logs easier to be read.

Reputation logs: sudo -u sashireputationd bash -c 'journalctl --user -u sashimono-reputationd | tail -n 250' sudo -u sashimbxrpl bash -c 'journalctl -u sashimono-agent.service | tail -n 100' sudo -u sashimbxrpl bash -c 'journalctl --user -u sashimono-mb-xrpl | tail -n 100' Sometimes you need to run ...

A starting point here would be to have GPG encryption done on client side, that way the files are safely stored on evernode without risking getting compromised !

You can debug deployments on your own evernode node by doing following: Log into your node (ssh) #1: Write sudo sashi list to get a list of your tenants. #2: After that, write sudo -H -u <user> bash to log in as a tenant (remember to take the username from the list) #3: write docker logs <instance n...