lokinet/contrib/node-monitor
Ryan Tharp dada2164ec
npm start doesn't work
why ask about an entry point...
2019-05-05 21:37:25 -07:00
..
ini.js lokinet monitor 2019-05-03 15:11:08 -07:00
lokinet.js lokinet monitor 2019-05-03 15:11:08 -07:00
monitor_client.js lokinet monitor 2019-05-03 15:11:08 -07: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 npm start doesn't work 2019-05-05 21:37:25 -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
  • Hanlding 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)