Unchained
February 11, 2026

Crypto’s Legal Lines, MegaETH Launched But Delayed TGE, and LayerZero's Bombshell

How Zero-Knowledge Proofs and Intentional Ecosystem Building Are Reshaping Crypto's Scalability and Regulatory Future

by Unchained

Date: October 2023

Quick Insight: This summary unpacks the cutting edge of blockchain scaling and the regulatory tightrope developers walk. It's for anyone building or investing in crypto's next generation, offering a clear view of the technical and legal battlegrounds.

  • 💡 How are new L1s and L2s: pushing the boundaries of transaction speed and decentralization simultaneously?
  • 💡 What are the critical legal distinctions: between software development and money transmission, and how do they impact developer liability?
  • 💡 How are projects like MegaETH and LayerZero's Zero: strategically building ecosystems for long-term adoption, beyond token launches?

The crypto world is a wild place, constantly pushing the boundaries of what's possible, both technically and legally. This conversation with Peter Van Valkenburgh of Coin Center, Namk Mudarolu and Amir Almmani of MegaETH, and Brian Pellegrino of LayerZero Labs, cuts through the noise, revealing the core tensions and opportunities defining the next wave of decentralized innovation.

The Developer's Legal Tightrope

"What we are against is attempts to license and permission software development or the operation of truly neutral infrastructure."
  • Speech Protection: Coin Center argues that publishing open-source software is a First Amendment protected right. This means developers of truly neutral, non-discretionary tools should not face licensing requirements.
  • Book Analogy: Imagine an author being forced to collect data on everyone who reads their book. This Orwellian scenario highlights the absurdity of applying money transmission laws to non-custodial software developers.
  • Resource Misallocation: Prosecuting software developers for others' misuse of their tools diverts law enforcement resources from actual criminals. This betrays victims and hinders effective crime fighting.

MegaETH's Long-Term Play

"The era of infrastructure for the sake of infrastructure is over and we need to have a proactive role in cultivating and facilitating a vibrant application ecosystem."
  • Performance First: MegaETH centralizes block production to achieve 10-millisecond block times and 55,000 transactions per second. This speed enables "10x" user experiences, like fully onchain social media or real-time games.
  • Strategic Delay: MegaETH postponed its token generation event, tying it to specific Key Performance Indicators (KPIs) like app fees and USDM liquidity. This prioritizes real economic activity and long-term ecosystem health over short-term token speculation.

LayerZero's Zero: Scaling with ZK

"The core problem with any blockchain today is that if you have a million nodes, every single one of those million nodes is reproducing the same exact compute. So you're paying effectively a million times the cost of doing the computation itself."
  • Compute Compression: Zero uses ZK-proofs to compress computation, allowing nodes to verify proofs rather than re-execute every transaction. This drastically reduces the computational burden on individual nodes.
  • Heterogeneous Architecture: Zero enables a system where powerful sequencers generate proofs, and small nodes (like Raspberry Pis) verify them. This maintains decentralization while achieving millions of transactions per second.

Key Takeaways:

  • 🌐 The Macro Shift: The industry is moving from a "build it and they will come" mentality to a highly intentional, ecosystem-first approach, recognizing that raw tech specs alone don't guarantee adoption. This is coupled with a critical legal battle to define developer liability, which will dictate the future of open-source crypto innovation.
  • The Tactical Edge: Investigate projects that prioritize real-world utility and long-term ecosystem health over short-term token hype. For builders, focus on creating "10x" user experiences that justify new infrastructure, while understanding the evolving legal framework for non-custodial software.
  • 🎯 The Bottom Line: The next 6-12 months will see a clearer delineation of regulatory boundaries for developers and a competitive race among high-performance chains to onboard institutional and consumer applications. Success hinges on a blend of technical superiority, strategic ecosystem cultivation, and legal clarity.

Podcast Link: Click here to listen

If crypto taxes feel overwhelming, you are not alone. That's why Cryptotax Girl, a team that's been helping crypto investors since 2017, is offering $100 off on one-on-one cryptotax help. To get $100 off your cryptotax services, go to cryptotaxgirl.com/unchained. Again, that's cryptotaxgirl.com/unchained.

Yeah, thanks V. And that was very kind of you. I've been working in this space for 11 years. So, Coin Center was founded in 2014. It's actually my first job out of law school. My first like big job out of law school.

And at the time, you know, there wasn't really a mature voice explaining and educating and representing these open source technologies in Washington DC. And Coin Center's mission was to fill that void was to be a voice for the technology, which at the time was, you know, primarily Bitcoin. That's really all we got questions about when we would go into a congressional office or into an agency. This was before the Ethereum ICO and before Ethereum launched. This was before ICO summer, NFT summer, DeFi summer, name your summer, you know.

So, we've been around for a long time. We're missiondriven. So, you know, there are now a number of mature and some of them quite successful trade associations in Washington DC that represent crypto interests, but Coin Center is not a trade association. We think of ourselves and we are a civil liberties firm that's focused simply on guaranteeing that people who want to develop the free and open source software that makes these technologies the open innovations that they are are protected from undue prosecution or regulatory treatment.

We're not nihilists to quote Senator Warner actually in a recent hearing who suggested that there are some people in the industry who are nihilists who don't want any regulation or that might have been Bessant actually it was in an exchange between the two of them it was really interesting exchange we do believe in common sense regulation of trusted persons in the space of companies like Coinbase and even of projects that claim to be decentralized and trust minimized but actually are still performing basically the roles of a centralized financial institution.

What we are against is attempts to license and permission software development or the operation of truly neutral infrastructure. And we sort of modeled ourselves after the Electronic Frontier Foundation, which for those of you who don't know is this amazing internet policy focused civil liberties organization that started in the '9s by great like John Perry Barlo that fought to say look you know aspects of the internet deserve regulation but just connecting computers together and making a global network possible and writing the software to do it is not something that we should police into the ground because otherwise we'll lose this beautiful new freedom that we have in a global communications network.

Good. He should he should come up on every podcast. I think it's hard to separate, you know, Coin Center, I think part of what's made Coin Center successful over the last 10 years is that we have this narrow mission. We're not here to represent, you know, a quasi centralized online casino for, you know, per or something like that. We're here to represent like an actual open source tool for privacy.

And we're also not here to opine on a whole bunch of other technologies. We're supposed to be cryptocurrency focused, blockchain focused, maybe you could call it decentralized computing focused. So, there are touch points there with AI. Like frankly, I would be more comfortable if the way AI was built out over the next few years was as much as possible through decentralized systems for both like who owns the compute resources and and how do we reward you know training data and things like that.

It'd be great if that was built on on on more decentralized protocols because I think that's a decent use case for blockchains. But on the question of just like AI and liability for developers who are building these models, I I think we would shy away from that. But it would also be hard to because the exact same precedents that will be set in the world of crypto like whether your smart contract for privacy is worthy of first amendment protections when you publish it or deploy it to the blockchain are going to be identical as far as legal standards that are developed under the first amendment as whether you can write the same code and publish it widely or distribute it widely for AI.

Right? So there's a lot of overlap, but we take as our mission defense of the crypto stuff specifically.

Well, so it's interesting. So, you know, back in 2017, I think we published a long form report arguing that the state money transmission licensing regime is a strange fit for crypto businesses. Like, it's odd that a Coinbase would be regulated exactly the same as a Moneygram or a Western Union, right? Because their risk profiles are different. consumer protection issues are different and it's inefficient to force these companies to go get 53 licenses from different states and territories that all independently regulate their activities.

Right? So the question back then was why don't we have a federal framework? And that's mostly what market structure is about. It's about can we establish and house at the SEC and the CFTC some unified national oversight for trusted companies that hold people's crypto that are deserving of regulation because people trust them with their crypto and they trust them with say best execution in a trade or something like that. And mostly that's something that Coin Center supports but doesn't get deeply involved in because if you walk like a duck and you quack like a duck, if you're kind of like a bank or other financial services provider, we just think there should be equal treatment.

You know, we don't think the banks should get special treatment. We don't think the companies in the crypto space should get special treatment. Where we get really involved though is on this developer liability question. So if you're not a traditional trusted entity, you know, someone who's taking custody of funds or someone who's making, you know, enforcable promises of things like best execution, if instead you're just providing software that allows people to transact on their own, you know, relying on your tools but not relying on your discretion or judgment.

Can you be regulated as a money transmitter and forced to get a license before you publish that software? Can you be regulated as a broker dealer under the SEC? Our argument is that when you're truly just publishing software or providing truly neutral, non-discretionary infrastructure that other people are using, you should not be forced to register or license. And there may even be actually pretty serious constitutional issues with forcing you to license or register before publishing your software because that would be a prior restraint on your constitutionally protected speech rights.

Additionally, those regulations setting aside the constitutional concerns are not usually fit for purpose. Broker dealer registration is about information asymmetries as is most of the SEC's you know statutory purpose. And in a world where your software is simply scraping publicly available information automatically and allowing a person to find say a trading partner somewhere online using that publicly available information. You are an information broker. You're not a stock broker in the traditional sense.

And so the information asymmetries that we would normally worry about in a broker registration context like are you going to find the best trading pair or are you actually going to prefer someone that is you know internal to your brokerage firm or your larger fund. Are you going to make public the information that you based your decision on how to route an order? Those questions start to fall away when we're talking about truly decentralized systems.

Similarly with money transmission and anti-moneyaundering rules. When you are in a position of trust visa v your customers your Moneygram, Western Union, PayPal, Coinbase, it is a fair bargain I think to then obligate you to know those customers and report some of their information to the government for crime fighting purposes. But when you are a stranger to those people, you are more like a person who wrote a really good book that a bunch of people are reading. the thought that we would force you to learn all the people who bought and read your book and report them to the government. it starts to look very Orwellian and it's problematic I think fundamentally so where we have truly decentralized activities truly softwarebased activities I think we need to avoid prior restraint and registration.

Now that's not to say that there's no regulations that apply as the last thing I'll add to this there are things like unfair and deceptive acts and practices so if you publish software and it turned out it it did things that you said it didn't do either because you were negligent And certainly if you were intentionally committing fraud or deceiving the users of your software, you should be prosecuted, right? And and there is jurisdiction to do that under unfair and deceptive acts and practices at the FTC and at other agencies. But registration and licensing is a is a step beyond that. It actually starts to get into the realm of prior restraint.

with is how do you maintain the non-custodial nature of of this kind of arrangement? Like what does it mean to have control? You know if if we can upgrade the vault, does that constitute control? What if we can pause withdrawals in order to respond to security instant incidents? Does that constitute control? What if you can pause withdrawal or sorry, what if you have something that is not 100% immutable because there are certain admin functions you need to have just to like be able to operate the thing.

So like do you do you read the provision the proposed language in in the market structure bill to mean that something really does have to be like 100% autonomous and immutable to constitute no control or if you have any at whatsoever, does that mean that you're subject to regulation?

So there's a couple different moving parts actually. It's a big bill and this is part of what's made it very difficult for it to move through the Senate because a lot of people have a lot of education to do before they can get comfortable with it. But there's a couple different provisions. The first provision to focus on for this question is the Blockchain Regulatory Certainty Act, which was a separate standalone piece of legislation that began in the House in 2018, I believe, when Representative Tom Emmer, now Majority Whip Tom Emmer, introduced this piece of legislation.

And it was intended with Darren Sto at the time. So it was bipartisan as a Democrat and a Republican. And it was intended to create a safe harbor from unlicensed money transmission prosecutions for people who are truly not doing money transmission as defined by Fininsen at the time, the relevant federal regulator for figuring out who is a money transmitter. Fininsson had issued guidance. At the time it was multiple letters to multiple companies who asked for for further information for administrative rulings and later it was official guidance in 2019 on all different kinds of entities in the crypto space.

And Fininsson said if you do not accept and transmit by which we understand at some point in between you'll have independent control over customer funds. If you don't do that, you're not in our jurisdiction, which I think was a very good and faithful reading of the underlying regs for the Bank Secrecy Act, which is our financial surveillance rules, and the Bank Secrecy Act itself. And so Tom Emmer's bill, the Blockchain Regulatory Certainty Act, simply took that Fininsen guidance and codified it and said, "We're going to make this a statutory rule so that it can't be ignored."

Because guidance is guidance and it's it's important. Companies sometimes rely upon it, but prosecutors can ignore it. They can say the underlying statute is different and the guidance shouldn't be followed. And in fact, that's exactly what the prosecutors said in the tornado cash prosecution when they went after Roman storm. They said, "Yeah, Fininsen said you're not a money transmitter if you don't have total independent control, but Fininsson's only defining only offering guidance on the statutory definition at 5330, the bank secrecy act, and we're talking about the criminal code where we think money transmission is basically whatever we want it to be."

to uncharitable reading of their That's an uncharitable reading, but we'll get hold on to to back up my unchar to back up my uncharitable reading though, they said a frying pan transfers heat even though it doesn't control heat, which is to me verging on chicainery. Like I understand a prosecutor for I'm not standing up for the DOJ in this prosecution or that brief, which I disagreed with a lot of it. I think that the bigger problem of that charging of tornado cash was the fact that they weren't specific enough with the facts because tornado cash obviously changed over time.

Agreed. And they should have charged it accordingly. But I know that your point here. I just I I want to make sure that um yes I'm challenging you in the ways that like that industry also. But so I guys what I think is like let me close the loop quickly on the market structure discussion because I know I go off on these tangents. So the BRCA ultimately got attached in the House to clarity the House's market structure legislation and that was important for Coin Center because we basically said look we want trusted companies to be regulated in a sensible way but part of the bargain for our support and for like what we care about is that you offer some clarity to software developers that they're not going to get unjustly prosecuted.

And the House passed that with the BRCA attached. Then it came to the Senate, which is why we're discussing it now, and it got subtly changed in ways that I'm generally comfortable with. But at now at this last moment where we're sort of dithering on the precipice of maybe getting a vote in Senate banking to get it out of committee to get it voted on in the larger Senate, there are renewed doubts by some folks who we're going to need the support of to get the vote count to actually pass this thing as to whether we're unduly restricting the ability of prosecutors to go after bad actors by providing this insulation from liability for software developers.

So yeah, hopefully that closes up on the question.

No, that's really helpful background. I think like the the frustration for like someone in my position right where I'm actually trying to advise like developers and builders around like you know if we have an admin key like what actual functionality can we retain or give up right in order to constitute no control and right now like and I get that it's the statute and so it's not necessarily going to drill down on what like the different factors are like that will come with rule making I assume but That's what I think is frustrating and and and it's it's hard, right? Because until we understand how control is actually defined, it's the language right now is not actually that helpful for us. Like we are still potentially at risk of being criminally prosecuted.

I think the BRCA's definition of non-controlling blockchain service or service provider or or software developer is much clearer than anything we've had in the past except maybe that 2019 Fininsen guidance and and or in line with that 2019 Fininsen guidance. And so this will hopefully cotify what has become a clear standard had it not been for some prosecutions from the Southern District of New York like the tornado cash prosecution that I think went off the rails or were prosecuted in the wrong way to be to be fair to Jess's excellent point which there there probably were good ways to prosecute this and this happened to not be one of them.

And then the other thing I'd say to answer your question on sufficially decentralized and admin keys and you know emergency security councils and things like this, I think the BRCA gives you a fair amount of clearance that if if what your admin key allows you to do is rewrite the smart contract in certain discrete ways. You don't have day-to-day ongoing control of customer funds. And so you're not a money transmitter. But there's more. You might be a broker dealer. you might be a digital commodities broker dealer which will be soon within the jurisdiction of the CFTC.

And so there's a secondary question. The BRCA gets you out from money transmission liability if you don't have control, but are you regulated at the federal level by these other competent authorities that will require registration and licensing? And so in the Senate banking amendment in the ANS draft, all this jargon, yeah, there's section 301, which is an interesting thing to look at if if you're a lawyer working in the space, which is about nondecentralized protocols.

And so that sets up effectively a rule making for determining what is a non- decentralized protocol with a number of important factors for what might be non- decentralized. If you are deemed non-deentralized after that rulemaking sets up those factors, you can then also be deemed obligated under existing securities laws or existing treasury rules like the bank secrecy act as an obligated entity either as a broker dealer for securities or as a money transmitter or not as a money transmitter or as a some some other BSA regulated entity under the bank secrecy act.

But if you are insulated by the BRCA, you can't be treated as a money transmitter. So this non-deentralized rulemaking is important and one thing that I you know the first time I saw this text from its drafters I was concerned because there's a lot in there and there's a lot you see technical terms in legislation you think well this probably won't age well or it won't create the clarity that you hope it should be more of a a principlesbased standard rather than a specific technical standard but once I dug through it I got comfortable with it there's things that I would potentially change if I was you know if I was the Senate to quote Star Wars.

But I'm not the Senate and the process of legislation is a process of compromise. And so I think where that ended up is pretty good. To your specific point, there is a section in 301 that deals with admin keys used for cyber security vulnerabilities, things like a pause function to address a known bug. And so they don't intend to they don't intend to call that non-deentralized. They intend to say like we don't want to disincentivize this good cyber security practice. We just want to go after the people who are calling themselves DeFi but are really just you know your traditional broker and dealer and security.

I think that's important to clarify right that like decentraliz sufficiently decentralized and like not having control does not mean you have to be 100% like immutable and autonomous. There actually is some room in there for some admin functionality. And I think like that, you know, that was kind of the right that was the feedback that I gave some of the staff on that which is that we should want to incentivize just kind of like ordinary responsible measures that honestly every DeFi protocol out there pretty much is already doing a lot of this stuff now, right? like like this might be a surprise to some people who talk about this in the abstract a lot, but there actually aren't that many DeFi protocols out there today that are 100% autonomous and immutable.

So like this would really protect no one if if control meant or no control meant that you really just have no admin functions at all.

B, you've said this before, but I think that part of the problem that the crypto industry and lawyers in the crypto industry, so we are to blame as well, have created is this binary conversation of control and not control. And that puts developers like the the place that you work and many other developers in this place of when I build this project, how do I build it to be secure from prosecution and ensure that I'm protecting myself? But it simultaneously I think puts policy makers in an odd situation because like when you talk to the Dems that really want to get this done like a Mark Warner who supposedly said this week that he's in crypto hell that is trying to figure out how to we're all in crypto hell like all of us.

How to ensure that he's in you know protecting national security and also like speaking for victims which I definitely want to touch on here as well. like he's trying to come up with rules that protect national security and ensure that you know billions of dollars don't continue to be stolen by you know DPRK just to name one aspect of this. And so the concept of binary doesn't really work for them either. And when you have conversations with, you know, Warner staff and other Democrats, they they seem to be really trying to find a solution that allows developers to succeed and protect first amendment rights, but simultaneously like ensure the proper protections are in place.

And what I struggle with is there are a lot of ideas out there and I know like Peter, you and I have talked about liability statutes before, like maybe it's using money laundering more than 1960. like maybe that solves a lot of it if you just take 1960 out which we can get to but you know just sort of saying like well if you're completely decentralized and you're you know not touching anything it's protected by first amendment and if you're not you're not like I think that sort of escapes addressing a lot of the intermediary side because you know the book analogy you talked about is like one that I think is really interesting and like strictly in the first amendment you can publish a book but if you publish a book with, you know, plans to build a bridge.

Maybe this isn't a great analogy, but like I'm I sort of came up with it a few minutes ago. Um, you know, to build a bridge and the bridge has all these problems with it and you set up a toll on it that automatically collects some sort of fees and the bridge collapses. Like where at what point in those steps do you become responsible? And I don't know if there's an answer. I don't know when. I mean, for that one, it's when you actually like reached into the physical world and built the bridge. Totally. It doesn't work. Um, so, but I I I take your point.

So, I'm not quite sure what to say back to, let's say, a Mark Warner. I'm I'm not meaning to pick on him, but he definitely No. One, he was my first job was interning for him. Oh, really? Yeah. Totally. I mean, I think I was in high school, but um uh I you know, he's really seems to be trying to get this done while simultaneously keeping the space safe, and he seems to be focused on the national security side. So, like, what do we say?

I'll say I'm I'm very grateful for Mark Warner's involvement in this. Actually, I I told I said at the beginning that to to Jesse and and V that I wasn't going to mention any members or staffers by name, but I will do it in the positive and that like Mark Warner has been a very honest broker on these topics and it it does feel like he's genuinely trying to get to a good place and it and the the what you teed up is exactly the difficulty and I you know Coin Center is even guilty of this in that we focus pretty narrowly on like truly open- source software. than doing things in the world and people being held liable for publishing the open source software and that I think is black and white that should be off the table for any kind of permissioned regulation but that makes me sound like an absolutist unless you realize that that's a very small segment of the crypto space that is actually a narrow carveout like that's like Bitcoin core developers Ethereum core developers probably some other L1 core developers, but I won't name names because this starts to get very, you know, uh, you know, dodgy.

It's a small number of people and it and and, you know, we also stand up for miners and validators who are truly not in a discretionary position visav like the users of their protocols that they are, you know, maintaining by mining and validating transactions. This is not a wide swath of people that we think are truly off the table. Then there's this giant intermediary gray area of people who are you know building DeFi tools h they retain some control they may make certain promises to their users this set of people there are very hard questions over and I think they may not be protected by the BRCA and I I want to like make that clear to if there's any staffers for any of the offices that are noodling on this text I don't think all of those people are protected by the BRCA the BRC TA is meant to be a very narrow piece of clarity for just people who are truly engaged in activities that don't engender trust from their users that don't trigger the normal regulatory obligations that we would expect because it's more like software development in a pure sense or infrastructure in a pure sense.

For the people who are actually in some position of quasi trust, they may not be excluded by the BRCA from anything and they're going to fall into or out of this three 301 rulemaking on non-deentralized protocols. If they if as Treasury and the SEC develop this 301 rulemaking, they develop it in a way that catches some of those people, those people will be treated as obligated entities for things like the Bank Secrecy Act. And then in general, there's also all of the truly centralized businesses out there who don't pretend to be decentralized, but previously have been regulated in a somewhat ad hoc manner by by squeezing them into existing regulatory structures like money transmission. This bill will create new categories of fally regulated financial institution that will have BSA AML obligations.

So this bill is not a deregulatory bill. It's actually a strongly regulatory bill that will create a lot of new data and data collection for law enforcement by the creation of these new BSA obligations for these new types of entities like digital commodity brokers and dealers. The part that we're now discussing that carves some people out from a licensing requirement and a surveillance requirement is really limited to carving out just those people who never should have been obligated to collect information on the users before because it would be like asking an author to collect information on the people who read their books.

I mean I think that's a great point. We obviously haven't solved anything yet, but we do need to take an ad break. So I'm going to jump in and let us do that and maybe when we're back we'll have all the answers. a chance to win $25,000 in Sorry, good job being crypto and access is running a $25,000 USDC sweepstakes tied to their democratized prime product. Here's how it works. Download the Figure Markets app using our link figurearkets.co/chained DP. deposit into a democratized prime lending pool and leave your funds there for 25 consecutive days. Every dollar equals one entry, so $1,000 equals 1,000 chances. While your funds stay in the pool, you're also earning around 9% APY paid out hourly. To learn more and enter, go to figurearkets.co/changed dp, which is also available in the show notes. If you're looking for help with crypto taxes, CryptoTax Girl is offering $100 off for Unchained listeners. They provide personalized cryptotax reports and returns and spots before April 15th are limited. Go to cryptotaxgirl.com/unchained to save $100. Once again, the link is cryptotaxgirl.com/unchained. We just have meaning. Sorry. True. Um, we were talking about the bill during break. Okay, we're back. Turning it over to V to talk a little bit about how money laundering fits into all of this.

So, we we mentioned um you know that there have been various charges in cases like tornado cash and Samurai Wallet, right? So, there's the the 1960 conspiracy to operate an unlicensed money transmitting business. But I I wanted to focus on the conspiracy to money launder charge. Because the reason I think it's important is because like you know even if we totally got rid of 1960, wouldn't developers still be exposed to criminal liability under in my view the very broad and incorrect way that the prosecutors have been applying the conspiracy to moneyaunder charge.

Right? So just for background like the developers you know they wrote and published non-custodial software the software I think you know this isn't in dispute right the software can be used to facilitate illicit finance and it was by bad actors the developers in some of these cases knew that that was happening and they didn't do anything to shut the protocol down block users um redesign it to to help like stop elicit activity, right? So, I think it's important to note that the DOJ here did not allege that the developers in any way actually coordinated with the illicit actors. Like they didn't come to an agreement with them to moneyaunder. They didn't direct moneyaundering activity. Um they didn't share any of the profits from the moneyaundering.

Right? So what they're basically saying is if you continue to maintain or publish software after learning that elicit activity is happening using the software, you've joined a conspiracy to moneyaunder. Right? So to me that was always really highly problematic a highly problematic reading of the federal conspiracy statutes which like if you guys don't know right just on a very basic level it requires an agreement between two or more people to commit a crime. It requires knowing and intentional participation in that in that agreement and it requires an overt act and furtherance of the conspiracy. Right? So, like if you went to law school, you probably remember covering this in criminal law. And I just I've never seen how we have all of those elements in these cases, right? Like where was the agreement between Roman Storm and Lazarus group? Where was the knowing and intentional participation?

So, like I I feel like we just haven't we haven't focused on that part of these cases enough as an industry. Especially because in my view I actually think that if this issue ever got to the Supreme Court that they would agree that this is a radical application of the federal conspiracy law and it has implications for like more than just how it's been applied to these crypto developers.

So I want to be very careful here because it is my hope that actually some you know staffers on the hill are actually listening to this and are thinking about the blockchain regulatory certainty act and whether it should stay in market structure or not and one thing that I will say is like when coin center has talked about these issues we emphasize how the BRCA doesn't change 18 USC 1956 which is is the moneyaundering statute. It only changes 18 USC 1960 and it doesn't get rid of 1960 to your earlier point V. It simply says look 1960 is something that can continue to be prosecuted for things like hala which is actually kind of what originated 1960 was fears over um these networks of quasi money transmitters in in communities to move money from person to person ultimately to a destination.

The BRCA doesn't touch Hala. It doesn't touch any kind of informal network where the people moving the money actually do move the money, actually have control of the money. It wouldn't limit those prosecutions. It wouldn't limit the state's ability to prosecute 1960 at all, except in the very narrow case where they try to prosecute someone under 1960 for creating tools that other people used to transfer money. And that's what I would describe the Tornado Cash developers do doing. They they didn't move any money for people. They did create tools that other people used to move money and some of those people turned out to be North Korea, you know, unfortunately.

That said, like the Linux operating system is definitely powering centrifuges that enrich uranium in Iran. But we're not going to say that like Linus Torvt is responsible for Iran's nuclear program. That's nonsense. like software and tools when they're good get used by a bunch of innocent people including tornado cash which people use to donate to Coin Center to support our mission which people use to support the defense of Ukraine our co-paints in our lawsuit challenging the sanctions on tornado cash a John Doe including people who just get paid their paycheck in crypto and don't want their the person in the cubicle next to them to know what their salary is and yes good software also get used by bad people but you shouldn't be found to be guilty of money transmission and unlicensed money transmission simply because other people used your software to transfer money.

Now money launder is a different actis. It's a different criminal or guilty act and it means that you conduct or attempt to conduct a financial transaction involving the proceeds of a from some spec from some specific unlawful activity. you transport, you transmit that, you know what it is and they have to actually like identify that when you started handling it in some way. Maybe you didn't have full control over it, by the way, but when you started handling it and facilitating it, you knew exactly what you were doing. You knew who you were helping and how you were helping them, right? And so there are hard questions there visav software developers who do more than just one-time deploy code to the blockchain.

Maybe they maintain servers that are frontends. Maybe they maintain some sort of advertising or technical support feature. Maybe somebody emailed them and said, "Hey, I'd like to use your software uh to launder these proceeds of crime. Will you help me?" And they foolishly said, "Yes." At some point, that factual pattern should probably lead to a a prosecution for money laundering. not for unlicensed money transmission because what you were doing was not money transmission in the traditional sense but based on the facts it may be money laundering and so my point in going through this is we didn't get a verdict on the moneyaunder charges in the Roman storm case in the tornado cash case we just got a hung jury that could be reprosecuted it probably should be reprosecuted and I you know I don't know enough about all the facts to make an educate a strongly educated guess on whether it could be successfully prosecuted or not because it's highly fact dependent.

As I said, if there are certain emails from North Korea to the developers, that could be the nail in the coffin. I don't know if those emails exist. The government should have to prove that knowledge on the board developers though. Those emails did not exist. Well, there was no communication between Roman group. Like that's fine. I'm speaking in the abstract though that what the law should demand is prove it. Right. And so if they have the ability still to reprosecute, they should go and find better evidence. And if that evidence doesn't exist, then they're going to fail again. And I'll be happy that they failed.

I mean, knowledge and intent. 18 USC 1960, the unlicensed money transmission prosecution. They don't have to prove intent. They don't have to prove knowledge. They don't have to prove crap. They basically say if you were doing money transmission, which we define as basically everything and you didn't have a license or registration, you're guilty. It's basically a strict liability federal felony. And that's a problem. That's the kind of liability that will stop even the most innocent, good-hearted, good-natured developer from publishing code because they're afraid they're going to get prosecuted for something that's effectively a strict liability felony.

So, actually, the last plug I'll put in is we have a lawsuit that we're helping support. We're paying the legal bills for. His name is Michael Llewellyn. He's a developer. He lives in Fort Worth, Texas. And he wants to write privacy software. And he's afraid to publish the results of his research and development because he thinks if he publishes it and deploys it to the blockchain like Roman Storm did, he'll get prosecuted for unlicensed money transmission. We're not arguing in that case that he should be free from 18 USC 1956 moneyaunderry prosecution. We're just asking for clarity on this narrow issue. And that's also the only thing the BRCA touches. It doesn't touch moneyaunderry. And frankly, I don't think it should. I think it'd be a very difficult political lift to reform the moneyaundering statutes and all I want from Coin Center's perspective is to get some clarity on this other statute 18 US 1960 that is so badly abused by prosecutors.

<

Others You May Like