cashshuffle/spec

Issues

• Clarify: who should receive blame information and what information should they receive?

  #2 opened 5 years ago by emergent-reasons
  3

• Link to overview and white paper is broken

  #20 opened 5 years ago by BitLox
  2

• Broken Links

  #26 opened 5 years ago by DarrenTa
  1

• More Submappings

  #25 opened 5 years ago by nopara73
  0

• OP_RETURN without OP_RETURN

  #22 opened 5 years ago by nopara73
  9

• What's the difference between message 5b and 6?

  #24 opened 5 years ago by MaxHillebrand
  4

• Round Public Key is Shared too late

  #21 opened 5 years ago by nopara73
  6

• fusion idea: hiding number of players

  #15 opened 5 years ago by markblundeberg
  0

• Redirect standard protobuf definition to this repo

  #11 opened 6 years ago by emergent-reasons
  0

• Change proposal: add intent field to messages

  #9 opened 6 years ago by emergent-reasons
  0

• Multiple rounds

  #8 opened 6 years ago by emergent-reasons
  0

• Failed shuffle behavior

  #7 opened 6 years ago by emergent-reasons
  0

• Ban behavior: what should be in the spec and what should be implementation details?

  #6 opened 6 years ago by emergent-reasons
  0

• Be more strict about valid messages so that server and clients can identify a failed shuffle and minimize exposure to malicious clients

  #3 opened 6 years ago by emergent-reasons
  0

• Include version details, requirements (0, 100, 200, 300, ...)

  #4 opened 6 years ago by emergent-reasons
  1