Remove blocked.go from Osmosis

Proposal\n\n This proposal aims to come to consensus that we should delete the blocked.go file in the Osmosis Github Repository (https://github.com/osmosis-labs/osmosis/blob/main/app/blocked.go). My name is Anthony Rosa, and I am the project lead at Moultrie Audits. Centralized entities like Tether are holding firm to protect censorship resistance (https://twitter.com/Tether_to/status/1562468486886346753?s=20&t=R3Gc5J6rUnSfOzeYxNZyuw). There are many aspects to this conversation, and it is encouraged to read through the associated commonwealth threads (linked below) prior to voting. The blocked.go file prevents users from withdrawing to the contained blocked addresses, and the file comments state “we block all OFAC-blocked ETH addresses from receiving tokens.” If we accept as a community that we should censor addresses the government deems illegitimate, our entire purpose becomes questionable.\n\n # Reasons To Delete blocked.go\n\nWhy have a blockchain if the service retains the censorship restrictions of Web2? How can we claim to be decentralized while preventing users from accessing a service through a central repository subject to revision by the government? Why wouldn’t this set a censorship precedent? Are we here to make money or change the world? \n\nIt is my opinion that it’s better if we fail trying to democratize finance with a truly decentralized DEX than succeed as a TradFi proxy, touting disingenuous values. In the commonwealth discussion (linked below), one member stated, “If we do nothing about it now, you will see a slow but steady erosion of your right to trade freely...We need to come together and support our freedom to trade crypto in the spirit with which most of it has been developed – permissionlessly.”\n\n# Counterarguments\n\nThere are severe possible consequences for not complying with OFAC or any other government requirement to block specific addresses. Removing the functionality to block addresses at a protocol level opens up financial and legal risk to infrastructure providers, developers, users, investors, and the entire Osmosis community. Validator level censorship is still a possibility, but an additional burden.\n\n In the commonwealth discussion (linked below), one member stated “I don't think this is morally the right direction, by the US government, or by implementing these policies. However, I do think logically it is the best step forward to preserve and protect our validators.” \n\n# Vote Explanation\n\nYes: Developers should move to remove the blocked.go file from the Osmosis repo. We’ll start by deleting the addresses in the file.\n No: We should keep the blocked.go file and associated functionality.\nNo With Veto: You believe this proposal is spam or malicious to Osmosis and we should keep the blocked.go file and associated functionality. Moultrie Audits will lose the deposit.\n\n# Links\n\nCommonwealth Thread: https://commonwealth.im/osmosis/discussion/6591-blockedgo-ofac | https://gov.osmosis.zone/discussion/6734-remove-blockedgo-from-osmosis\n Longer Justification To Deleting blocked.go: https://ipfs.io/ipfs/QmeJ2g7ths2HpqqhnHYmGPr4RcJemWHSEQ6p8jpBQDq8gY/Osmosis%20Prop.pdf