Skip to content

Logic for relay gamification

What is the logic for the gamification? Which values we are going to give points?

Values could be bandwidth or anything else we want to encourage in relays.

General list of values we can work with (according to Hiro's review with Miko):

CONFIG VALUES
Parameter
IPv4 address
IPv4 address type
IPv6 connectivity
(neg) No nickname for the relay
(neg) Relay nickname violates Code of Conduct
Tor version stable or alpha
(neg) Tor version OUTDATED
Autonomous System (AS) rank (lower = better)
Operating System is BSD
(Only Exit Relays) Exit Policy
Operating System is Linux
Operating System is Windows or iOS
YIELD VALUES (very low priority)
Parameter
Speed (minimum)
Speed (measurement)
Advertised Bandwidth
Uptime (up to 1 year)
(neg) Uptime more than 1 year (implies neglected relay running an old Tor version)
MORE IMPORTANT VALUES
Parameter
Contact info is set and verified
(neg) Contact info is not set or not verified
MyFamily
Consensus Weight
Location
Uncommon AS
(neg) Overcrowded AS
Monthly participation

These values are all publicly available to track. They are essential in providing transparency to relay operators.

For the Gamification mockup components:

There are two components that will use the values above as basis:

1. Leaderboards:
The idea is to engage relay operators in healthy competition. Values chosen for leaderboards have to ideally:
i. Show some fluctuation (daily, weekly) so a large number of relay operators stand a chance to appear on the leaderboard
ii. Are transparently seen and open for everyone including other relay operators without using external testing / measuring applications.

**2. Relay Health Bar:**
Relays should be treated dearly and relay operators who invest in the "health and well being" of their relays should be shown some positive feedback (or positive reinforcement.)

Some challenges:

Uptime as a value should be considered carefully.

  1. Generally uptime can be regularly awarded with points upto 1 year.
  2. More than 1 year of uptime implies neglect towards the relay. This opens up risks that the relay may be running an old or unsupported Tor version. In this case, negative points should be awarded to the relay.

Important:

Metrics portal has a "Top Relays" page, currently using Consensus weight as value for ranking relays. This can be considered for leaderboards.
https://metrics.torproject.org/rs.html#toprelays
https://gitlab.torproject.org/tpo/network-health/team/-/wikis/metrics/website/relay-search#top-relays

Some gamification elements that are not completely values-dependent will be turned into badges

See #38 (closed) for Badge list

Excel sheet for logic with values plugged in:

https://docs.google.com/spreadsheets/d/1WU6ojWd-acpSXSj8JFJo1PMyB68d46ZK/edit?pli=1#gid=1400054447

As seen in subtotals, a gigantic difference in points is created on a daily basis so the values that are meant to be discouraged are GREATLY discouraged, enough to urge immediate action. Relays that do well will be awarded amplified points.

Edited by miko
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information