Search results

More Submappings

Status: Open.

#25 In cashshuffle/spec;

· nopara73 opened on Feb 22, 2020

OP_RETURN without OP_RETURN

Status: Open.

#22 In cashshuffle/spec;

· nopara73 opened on Feb 14, 2020

Link to overview and white paper is broken

Status: Open.

#20 In cashshuffle/spec;

· BitLox opened on Jan 2, 2020

fusion idea: hiding number of players

Status: Open.

#15 In cashshuffle/spec;

· markblundeberg opened on Nov 6, 2019

Redirect standard protobuf definition to this repo

Status: Open.

#11 In cashshuffle/spec;

· emergent-reasons opened on May 9, 2019

Change proposal: add intent field to messages

Status: Open.

#9 In cashshuffle/spec;

· emergent-reasons opened on Apr 18, 2019

Multiple rounds

Status: Open.

#8 In cashshuffle/spec;

· emergent-reasons opened on Apr 18, 2019

Failed shuffle behavior

Status: Open.

#7 In cashshuffle/spec;

· emergent-reasons opened on Apr 18, 2019

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

Status: Open.

#6 In cashshuffle/spec;

· emergent-reasons opened on Apr 18, 2019

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

Status: Open.

#4 In cashshuffle/spec;

· emergent-reasons opened on Apr 9, 2019

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

Status: Open.

#3 In cashshuffle/spec;

· emergent-reasons opened on Apr 6, 2019