Global Feed Post Login
Replying to lucash.dev

Some cryptographic structures are so simple to implement — and so often implemented in very specialized ways — that you might not be worse off just writing one yourself.

I don’t recommend ever reusing a Merkle Tree implementation outside of its narrow original use case — unless you thoroughly review the implementation.

Most Merkle Tree implementations I’ve seen are either broken or one tiny change or assumption away from being completely broken.

Bitcoin’s implementation is a famous case.

But there are others.

Seen plenty of vulnerabilities in the wild.

Every novel use case for cryptography is dangerous.

Don’t assume yours is safe just because you copied it’s parts from someone else.

82
lucash.dev 2y ago

Bottom line is:

Don’t use a Merkle Tree implementation without reviewing it with your specific use case assumptions in mind.

Have knowledgeable people review it too.

Doesn’t matter if you wrote it or someone else, or if you got it from some place supposed to be battle-tested.

Reply to this note

Please Login to reply.

Discussion

No replies yet.