[ola]

> The first explanation was that the flaw was intentional—that it was meant to serve as a form of “copy protection.” If anyone used this code in their own work, he said, the IOTA developers would be able to exploit the flaw and damage other systems that were using the hash function.

Is this a common practice in the cryptocurrency community? Seems sort of pointless to put flaws and bugs in an open source project as copy protection instead of just keeping it closed source.

[tuxxy]

Be rest assured that this is NOT a common practice.

This is clearly someone trying to save face over a practically trivial break in their hashing function.

[xwvvvvwx]

Think about what kind of engineer would try to save face by claiming to have deliberately introduced a critical security vulnerability into their payment system.

[kruhft]

No, it's not. I assumed that it was 'like cartographers putting in fake streets into maps' and put that to them.

Not common practice in software, but something that other industries have been doing for a while.