lokinet/contrib/node-monitor
2019-06-19 15:29:23 -07:00
..
ini.js Minor warnings fixes in python/javascript code 2019-05-21 09:58:43 +01:00
lokinet.js Minor warnings fixes in python/javascript code 2019-05-21 09:58:43 +01:00
monitor_client.js Minor warnings fixes in python/javascript code 2019-05-21 09:58:43 +01:00
package-lock.json lokinet monitor 2019-05-03 15:11:08 -07:00
package.json lokinet monitor 2019-05-03 15:11:08 -07:00
README.md Update README.md 2019-06-19 15:29:23 -07:00

Building / Running

after building lokinet

cd contrib/node-monitor
npm install
sudo node monitor_client.js

and wait 30 minutes for final score

Scoring

Lokinet gets a point for everything it does correctly.

Currently:

  • succesful ping to snode (1 per second after a snode is discovered)
  • session with snode established
  • got a router from exploration
  • Handling DHT S or R message
  • a path is built
  • obtained an exit via
  • granted exit
  • IntroSet publish confirmed
  • utp.session.sendq. has a min zero count (no blocked buffers on routers)