Avatar
Sjors Provoost
8685ebef665338dd6931e2ccdf3c19d9f0e5a1067c918f22e7081c2558f8faf8
Physicist turned bitcoin developer aka "shadowy super-coder", author of Bitcoin: A Work In Progress

Ah whatever, looks safe… let's try

People can host their own Gitlab instance. The .com site is controlled by the company.

I haven't looked at it. I hope it's off by default. Private repos are ... private.

I haven't run into that. Is that their non-self-hosted instance?

Why does Github think it's a good idea to show this?

And it's worse. IIUC the money laundering charge is *conspiracy*. So they needed to have the intention of someone using the UI to launder money, and take one concrete step towards it (like writing the code). If such a charge survives, even if a license wasn't needed, that's a problem.

The Netherlands doesn't even have a license system for this, so it's really just about the question whether or not this was (actual, not conspiracy to) money laundering.

That said, the DAO didn't control the core contract. So to the extend that the core contract was used *without* any of the ancillary tools (website, DAO controlled smart contracts) then you COULD still maintain you had no control over that activity.

Unfortunately the DoJ probably just needs to prove *one* money launderer using the UI (based on CloudFlare records or something) for the money laundering charge to hold.

So then the defense in the US would have to fall back on the non-custodial side of things. At minimum they didn't need a license.

Not necessarily. You can specify which functions can be upgraded and which can't. For example some functions could be hard-code in the main smart contract, whereas others delegate to another smart contract, the address of which is stored in a variable. Ideally then those variables can only be changed by token vote, but my guess is that initially there was an admin who could do that.

However if "aspects of cryptography" could be changed, then most likely it would have been possible to brick the contract. But that would be destroying the company entirely, and so may not be an reasonable thing to demand. Plus it's rather pedantic, which itself doesn't always go well in court.

But imo the admin override doesn't matter. If it was a pure DAO then you just say "criminal conspiracy" and now all the token holders and developer are liable for the whole thing. Then all you need to do is *not* arrest the token holders (including the VC) and only arrest the developers and presto.

Hoekstra heeft de diplomatieke vaardigheden van een blok beton. Maar goed, ik zie 'm ook liever in Brussel dan hier. #NeverForgetWWFT

https://nos.nl/artikel/2487937-hoekstra-benadrukt-het-is-een-eer-maar-ik-ben-nog-slechts-kandidaat

En daarmee uiteindelijk van de Belastingbetaler, want die betaalt de volgende bailout.

I collected my brain dumps from last year and yesterday into a single massive blog post. It's totally unedited. Good luck :-)

https://sprovoost.nl/2023/08/24/tornado-cash-ofac-arrests/

Replying to Avatar Kieran

Just deployed a massive redesign of Snort.

Say hello to Snort V2 design, huge shoutout to nostr:npub1r0rs5q2gk0e3dk3nlc7gnu378ec6cnlenqp8a3cjhyzu6f8k5sgs4sq9ac as usual.

https://void.cat/d/RGhg4innbi5cTEfgV1DReP.webp

https://void.cat/d/JkpX5fmKyzGwMASB54sLSU.webp

As usual there are a few rough corners but we should get to them very soon, if you notice anything glaring please let me know.

This redesign has been in progress for over 2 months, the PR changed almost every file in the project.

Nice! Though I find the reply UX a bit confusing. Perhaps it's because the preview isn't working, but I also don't think it should be a modal. It makes more sense to have it directly below the post that you're replying to.

And maybe also the left-most button.