- Just fixing the hash method at SHA-256, full-stop, dropped a bunch of
text.

- replacing "hashed communication" to "cable", and changing the terms-of-art
to go with the "sending a cable" metaphor, makes it shorter and seems to
read better (and avoids the overloaded term "communication").

Create the following Rule, "Cables", power-tbd:

      A person (the Transmitter) CAN transmit a Cable by publishing a
      text string (the cable's Hash) that is a SHA-256[*] output and
      labeling it as a cable, possibly associating the cable with
      other announcements in the same message.

      The transmitter CAN deliver a cable that e transmitted by
      publishing a clearly-delimited document (the plaintext), while in
      the same message clearly referencing the cable's transmission
      (including the hash and the context of the transmission).

      The delivery is SUCCESSFUL, and the cable is considered to be
      Received by Agora (or just 'received') if and only if all of the
      following are true:
      - it occurs while the Delivery Window for that cable is open;
      - that cable has not been previously delivered;
      - SHA-256 produces the cable's hash as its output if the alleged
        plaintext is the input.

      This process, from transmission to delivery, is known as "sending
      a cable".

      By default, the delivery window for a cable opens when the cable
      is transmitted, and closes 7 days later. The rules may set
      different delivery windows for specific types of cables.

      In delivering the cable, the necessary publication of the
      plaintext is considered quoted material (i.e. informational only)
      unless the transmitter, during delivery, specifies otherwise
      outside the plaintext.

      If a cable is transmitted in association with performing a
      regulated action (other than the sending of the cable itself),
      failure to deliver the cable within the delivery window is the
      Class-4 Crime of Losing the Codebook.[**]

[* I want to say "output of the SHA-256 algorithm" but that's kind of
like saying "the ATM Machine" - what's the right grammar here?]

[** we need to make "taking back a move by not revealing the plaintext"
expensive, so it's not seen as a legit gaming strategy.]


Amend Rule 2593 (Space Battles) to read in full:

      If the Rules enable a player (the attacker) to initiate a space
      battle (syn: attack) between eir spaceship and another spaceship,
      that player initiates it by an announcement specifying the owner
      of the other spaceship (the defender) in a message that also
      transmits a cable associated with that battle (the
      targeting command). These two players are the "combatants" of the
      Space Battle, and the two Spaceships are then "engaging" in the
      Space Battle until it is resolved.

      The plaintext of the targeting command MUST clearly specify a
      valid amount of energy to spend in the battle (the attack value) -
      failure to do so is the Class-4 Crime of Bad Targeting, committed
      when Agora receives the cable.  The delivery window
      for the targeting command opens either when the defender announces
      a defense value for the battle, as described below, or 4 days
      after the battle is initiated, whichever is sooner.  The delivery
      window closes 7 days after it opens.

      The attack value for the battle is set when the targeting command
      is delivered; if it is not
      completed when the delivery window closes, or the plaintext of
      the targeting command when delivered does not clearly specify a
      valid attack value, the attack value is set to 0.

      In the 7 days after the battle is initiated, the defender CAN,
      once, and SHOULD, set the defense value (a valid amount of energy
      to spend in the specified battle) by announcement.  If e does not
      do so within that 7 day period, the defense value for the battle
      is set to 0.

      After both the attack and defense values have been set for a
      battle, the Astronomor CAN, and SHALL in a timely fashion, resolve
      the Space Battle by announcing the changes in each Spaceship's
      Energy balance and Armour (described below), and the Winner (if
      any) of the Space Battle.

      When a Space Battle is resolved:

      1) N Energy is revoked from each Spaceship, where N is the lesser
         of the Spaceship's Energy balance and the amount of Energy
         decided on by the Spaceship's owner, or 0 if the Spaceship's
         owner failed to do so;
      2) each Spaceship's Armour is decreased by X, where X is the
         lesser of the Spaceship's Armour and the amount of Energy
         revoked from the other Spaceship;
      3) the Winner of the Space Battle is the combatant, if any, whose
         Spaceship's Armour was reduced by a smaller amount than the
         other Spaceship's.


Create the following Rule, "Terms of Engagement"

      Two players are "allied" if they agree to be allied or if one is
      the master of the other; otherwise they are "opponents". For the
      purposes of this rule, agreement includes both consent and
      agreement specified by contract.

      A player who owns a Pilotable Spaceship in the same Sector as one
      of eir opponents' Pilotable Spaceships CAN
      initiate a Space Battle between the two Spaceships.

      A Space Battle CANNOT be initiated if either of the two involved
      Spaceships has been engaging in a Space Battle within the last 24
      hours or if the prior Space Battle the spaceship initiating the
      Space Battle has been in was against the spaceship it is
      attacking.

------------------------------------------------------------------------

Reply via email to