Skip to content
Nomicon game space for Cryptotech projects
HTML
Branch: master
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
Nomicon
Projects
Roles
_layouts
CODEOWNERS
README.md
_config.yml
cryptonomicon.png

README.md

Cryptonomicon

  1. The name of the game is Cryptonomicon
  2. The goal of the game is to Decentralize the Singularity
  3. The players of the game are the members of the players team
  4. All rules should be logically self-consistent
  5. The source for the rules are kept in the website repository
  6. The rules are published on the website

Jurisdiction

  1. Only Ulex 1.1 governs any claim or question arising under or related to this agreement, including the proper forum for resolving disputes, all rules applied therein, and the form and effect of any judgement.

Conventions

  1. The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in these rules are to be interpreted as described in RFC 2119.

Process

  1. All players must unanimously agree to all rule changes #virtual
  2. All changes to the game MUST be submitted through a pull request (PR)
  3. All changes to the game SHOULD be vetted by submitting a CIP or delta issue.
    1. A CIP is a Cryptonomicon Improvement Proposal (analogous to a BIP in Bitcoin Core).
    2. A delta is an inconsistency between a specification and an observation (analogous to a bug in software).
    3. If any player breaks the rules or witnesses another player breaking the rules, they SHOULD file a delta report.
    4. Deltas SHOULD be reviewed by the Operators to determine whether the rule should be changed or the player should be sanctioned.

Multi-votes

  1. If a proposal offers a choice between two or more options an Operator should call a multi-vote.
  2. Each option is voted on with a +1 (acceptable), a -1 (not acceptable) or 0 (neutral).
  3. Abstentions are counted as 0 (neutral).
  4. Each option is assigned a score equal to the sum of votes.
  5. If at least one option gets a positive score the multi-vote succeeds in choosing the one with the highest score, otherwise the proposal is defeated.
  6. If there is a tie for high score among the options, the sponsor of the proposal may choose a winner among them, otherwise the proposal is defeated.
  7. A multi-vote SHOULD have a single sponsor responsible for collecting and publishing options.
  8. A multi-vote SHOULD have a specified deadline.
  9. A multi-vote MAY be conducted on the game wiki.
  10. An option MAY be added to the multi-vote by the sponsor during the vote but options MAY NOT be removed once the vote starts.
  11. Voters MAY update their votes at any time before the vote ends but MUST NOT update anyone else's votes.
  12. A multi-vote MAY be resolved early only if all eligible voters have voted on all options.

Projects

  1. A project is a sub-game that inherits from the base rule set of Cryptonomicon.
  2. A project MUST have a unique name.
  3. A project MAY be located in a sub-folder of Cryptonomicon named after the project.
  4. A project MAY override a rule in the base game unless the rule is tagged as #final.
  5. A project MAY have its own set of players.
  6. A project SHOULD have a charter document that defines that goals of the project.
  7. A project SHOULD be a collaborative game played between two teams, typically the Gatekeepers and Keymasters
    1. The Gatekeepers (representing the project customers) SHOULD be responsible for acceptance criteria for project deliverables.
    2. The Keymasters (representing the project vendors) SHOULD be responsible for developing the project deliverables.
  8. A project MAY be funded with Bounties.

Roles

You can’t perform that action at this time.