SETUP_GUIDE.md

Setup guide

For specific configurations.

Local testing environment

This example uses the following:

• "machine-a" (headless Ubuntu)
  • Locally running Ethereum execution client
  • trin
  • glados-monitor
  • glados-audit
  • glados-web
• "machine-b" (with display)
  • Browser listening to glados-web

All commands are issued on machine-a unless otherwise stated.

Start trin (see docs)

~/trin$ RUST_LOG=debug cargo run -p trin -- --web3-transport http

Start glados-monitor, which uses chain data from the execution node and stores that in the glados database. For an empty database file, the --migration flag triggers database table creation.

~/glados$ RUST_LOG=glados_monitor=debug cargo run -p glados-monitor -- \
    --migrate \
    --database-url postgres://<user>:<password>@localhost:5432/<database> \
    follow-head \
    --provider-url https://mainnet.infura.io/v3/<api-key>

Start glados-audit, which takes monitoring data from the glados database, checks if trin has it, then records the outcome in the glados database.

~/glados$ RUST_LOG=debug cargo run -p glados-audit -- \
    --portal-client http://127.0.0.1:8545 \
    --database-url postgres://<user>:<password>@localhost:5432/<database>

Start glados-web, which takes audit data from the glados database and serves that for viewing.

~/glados$ RUST_LOG=debug cargo run -p glados-web -- \
    --database-url postgres://<user>:<password>@localhost:5432/<database>

Start glados-cartographer, which takes census of all the nodes on the network

~/glados$ RUST_LOG=debug cargo run -p glados-cartographer -- \
  --transport http  --http-url http://127.0.0.1:8545  \
  --database-url postgres://<user>:<password>@localhost:5432/<database>
  

On machine-b, listen for glados-web

$ ssh -N -L 3001:127.0.0.1:3001 <user>@<host>

On machine-b, navigate to http://127.0.0.1:3001 to view glados audit.