DICEonCrack attacked?

[MPOE-PR]

Having said that, I think including users inputs in the payments is the only effective way you can protect against (this kind) of double-spend attacks.

MPEx sometimes allows 0conf from users. The rationale is that a double spend wouldn't help the attacker much as whatever missing funds can always be clawed back (say from the person's next withdrawal). So it's not exactly the only effective way, tho it may well be the only effective way in most cases.

[SRoulette]

I would not say that SDice and blockchain wallet "enabled" this attack.

Then you would be mistaken, No one is arguing that it is not a valid use of the blockchain, but it does directly enable the attack as I described.

We have our own method of protecting against double spends without creating chains that are easily double spent.
It has been successful thus far