How to avoid accidentally 𝐥𝐚𝐮𝐧𝐝𝐞𝐫𝐢𝐧𝐠 𝐦𝐨𝐧𝐞𝐲

Sounds silly, but surprisingly easy to do if you're not vigilant.

One small tweak in a seemingly unrelated module and suddenly kim jong is salivating.

To prevent this, we now ask two questions prior to shipping:

founder @seismic // product-focused cryptography // rookie years @ stanford, google

This is one of those cases where the expressivity of a turing-complete machine is so scary.

Even if what you're doing is far removed from the concept of anonymous money, any sufficiently motivated person can exploit tiny slip-ups.

Slip-up [1] typically happens when you want to hide the consumption of state.

Eg. You're building on-chain Minecraft and you want to let players anonymously steal plants from a garden.

Too bad same mechanism is used in Tornado Cash w/ plant == money and garden == mixing pool.

Slip-up [2] typically happens when you want to groups of users to own hidden state.

Eg. You're building on-chain baking and you want users to bring proprietary ingredients.

Too bad the same mechanism is used for Coin Join w/ ingredients == money and cake == mixed funds.

So yes, safe to say we've had many run-ins with these cases.

Which is why these two questions are so important for us. We don't think "it was an accident" holds well in court lol.

Not saying you shouldn't build tech that can do this. 

Saying that if you are, it should definitely be deliberate so you can fully think through all the implications!

1. Do you have ANY nullifier sets attached to your merkle trees?

2. Are there ANY cases where multiple users share hiding commitments?

If the answer to either is yes, then don't merge to main.