Skip to content

Latest commit

 

History

History
62 lines (42 loc) · 3.43 KB

GUIDELINES.md

File metadata and controls

62 lines (42 loc) · 3.43 KB

Stake Wars Guidelines

Format

Rules

This program is hard to create rules for, so we’re giving you guidelines and examples. Judges on our side will rate your submissions and assign points.

If you are acting in good faith, you’re almost assuredly good. If you’re acting in bad faith, moderators will ban you from the competition.

Here are some examples and we will trust you to follow the spirit of the law:

DO…

  • Check out the QA scenarios and run them on your system.
  • Run a node or as many nodes as you can figure out how to run.
  • Run any kind of benchmark you think is valuable
  • Try staking in all sorts of ways.
    • You will be rewarded for creativity, effort and magnitude of the submission. (For instance, if you get delegation to work for a bunch of small accounts)
  • Write reports on your experience and send them to us publicly
  • Complain about things that need fixing or cleanup!

DON’T…

  • Do anything illegal to hack our stuff.
  • Hack other peoples’ computers or use attack vectors that are outside of our control
  • For example, if you add a keylogger to someone’s computer, that is showing a flaw in their Operational Security not a flaw in the system we’re building
  • Harass people in any way. This includes community members and team members.
  • Be a jerk

Points Overview

In order to get points, you will need to submit an issue on GitHub for each test you run. (https://github.com/nearprotocol/stakewars)

GET STARTED: You can all get the basic points for running a node (or nodes) and running an interesting benchmark.

Since we hope all of you will do this, we’ve created an issue for this in the main repo: nearprotocol#4

Here’s how points work

  • Check for test scenarios scenarios
  • You submit issues based on what you run into while attempting to run nodes to the GitHub repo identified above.
  • We (a rotating panel of reviewers) assign points to whoever submitted based on the severity of bugs.
  • The identity of the submitter must be associated with the submission by the end of the comp to be valid. Otherwise no points.

Agreement and edge cases

  • In addition, you will have to sign a program and token agreement for the reward of tokens based on points. This will happen at some point during the competition.
  • You CAN get multiple rewards for running multiple nodes, BUT only for giving us valuable information about problems in our system. It’s still dependent on the severity of the bug or the value of the test you’ve created. For example…
    • If you create a bunch of nodes and then just leave them up. No points.
    • If you create a bunch of nodes to test a delegation contract you created, very valuable. Much points. Very wow.
  • We’re not making it public what the translation from points to tokens is. This is mainly because we don’t want to commit to specific numbers upfront and be wrong.
  • The point system allows us to create weights for bugs and tests. Our goal is to do this fairly and equitably. No funny business.

Our Goals for this

We want...

  • You to build things that solve your own problems as future validators on the network
  • To put the last year or so of hard work in front of our community to try it out
  • To find glaring flaws in our systems, designs and code
  • To learn what your needs are as part of the validator community