mule1
Joined 5 years ago
Joined 5 years ago
I am not against that set of rules, especially for the legacy system, but it's not on blockchain devs to comply.
We will have to let our legislators decide. Starting to see a good amount of bipartisan support for reasonable regulations (in the eyes someone who is pro crypto). And whatever they decide it will prove the true strength of a blockchain if it can resist censorship. For example, if they choose to make Coinbase comply with OFAC on an attestation level the system should be able to deal with that through social slashing etc.
It gets muddy where with Ethereum where there are public companies like Coinbase who have to comply with certain laws as they are a financial entity running their own validators with coins from their depositors. Don't get me wrong there is an urgent need for regulatory clarity and not all regulations are bad.
If censorship ever came to the blockchain itself i.e. Coinbase (who holds a large stake and needs to comply with OFAC) not attesting non-compliant blocks, there are censorship resistant ways the chain can employ to prevent this - like social slashing, this is a great read on it:
https://ercwl.medium.com/the-case-for-social-slashing-59277f...
Go compiles so fast and reads cleaner imo, that I never saw the benefit of python. I always thought debugging python was clunky, could be unfamiliarity with interpreted languages. Also a few times I needed to use an ODBC driver with python left a bad taste in my mouth. But overall I get what you're saying, my new team writes all of their lambdas in python so I'm going to have to learn.