If people cannot put python code or golan code interacting with smart contracts, into a desktop software wallet, open source downloaded, without being indicted, then yeah the gov is telling what free code publishing is allowed, it sets the precedent for banning math/ai/everything
they're telling you which math, which encryption, which speech, which language of code, how you execute it, that you're allowed to publish, freely as FOSS, and indicting you for hosting it on *a central server somewhere or Github, plus they've forced Github to censor
This is what liberal dem voting OG FOSS people who hate crypto believe, they don't understand that the line between code publishing and markets/money as speech is that blurred, it will be used to censor, it is a violation of the 1st/4rth.
When they say they want regulations, councils, commissions, licensing, intensive identity verification, and geoblocking to publish FOSS math, encryption, finance swaps, arbitrarily based on central server hosting, or Github, or a particular execution format, yes its unlawful
They are using rent collection, fee collection, and central server hosting as the basis of the indictment of storm, but the swaps are only possible with the inclusion of smart contract. His case is the 4th & 1st amendment on trial unequivocally.
They are building his indictment on the work of the SEC and CFTC, if you're paying attention. They've chosen servers and frontends as the means to cripple this industry, because of servers and function calls to smart contract. It's a hyper "Facts and circumstance" case.
This is why the work of the SEC & CFTC is so dangerous, it helped build federal briefing to indict & beat Storm in court. Based on their 4 agency web of lies about what front end code is, and how they *claim* front end code isn't protected by the 1st/4rth, due to profit.
People who assume that a serverless frontend that doesn't give fees to a central LLC is some literal get out of jail free card, are being hyper naive, that won't be the case. Beating Storm is a stepping stone to active censorship of validator & Sequencer.
If you define one lie in federal court about front end code on a fact and circumstance case of an entity profiting, it will be used against Daos and governance regardless, we know the SEC was bad faith, so the Treasury will simply continue that interpretation of profit & entity.
Because they started with the conclusion and outcome they wanted, georestriction, censorship, and hard licensing of frontends by bad faith claims of profit & ownership, when the frontends are serverless & community owned, they will turn prosecution to sequencer & validator.
and in doing so they will continue to use OECD, Fatca, Fatf, aml-kyc, and Sanction Regime politics to do it, to enforce their point, and they will continue to expand or attempt to expand the Banking Secrecy act and patriot act. Do not trust them, do not trust their lies.
.@0xMakesy @lex_node @ChrisBlec @prestonjbyrne @pcfreak30
@0xMakesy @lex_node @ChrisBlec @prestonjbyrne @pcfreak30 @threadreaderapp unroll
• • •
Missing some Tweet in this thread? You can try to
force a refresh
