Bitcoin at a Crossroads - Tackling the BitLicense

bitlicense draft
bitlicense draft

Folks, I’ll be honest.  No other news today really matters.  Today is all about the BitLicense and the necessity of assertive and compelling public comments - coordinated or individual - to the NYSDFS in the coming weeks.  Below is my breakdown and lengthy proposals for attacking the BitLicense’s deficiencies.

Bitcoin at a CrossRoads

- Ben Lawsky of NYSDFS

The BitLicense draft crafted by the NYSDFS and its superintendent, Ben Lawsky, is an important milestone for Bitcoin.  The proposals represent yet another step towards widespread adoption of virtual currencies, and the standardization they promote in consumer protection, financial transparency, and technical security across various service providers should lead to greater levels of trust from consumers and the broader business community. That trust, in turn, will help the industry’s exchanges, wallet services and payment processors attract customers and partners who had previously eyed virtual currencies with skepticism. 

An appropriate BitLicense, then, is undoubtedly a good thing for the future of Bitcoin as both a technology and a currency - the initial proposals’ current flaws notwithstanding.  And it is encouraging that we as a community now have the opportunity to respond to the NYSDFS’s proposals during a public comment period.

The bad news, of course, is that there appears to be a massive chasm that we still must cross to get from the proposals we have to the ones we need.  This makes it crucial that stakeholders across the industry rally to make their voices heard.  

Candidly, I am frustrated and disappointed with the first draft of the BitLicense for myriad reasons, as I’m sure many of you are as well.  But the reality is that we must work with the NYSDFS and need to forcefully convey the urgency of our concerns, while understanding the needs of these regulators tasked with promoting and abiding by existing laws related to money laundering, consumer protection and national security (regardless of personal opinions on the merits of those statutes).

As I see it, the only good option we have is to be assertive and convincing in our arguments against some of the most unpalatable provisions outlined by Lawsky and his colleagues, and then hope for the best.  You can’t fight city hall, and when it comes to New York financial authorities, we are dealing with people whose jurisdictional reach has proven to be global. 

It’s tough to effectively vote with your feet and simply set up shop outside of New York when the NYSDFS will likely set the standard for how Bitcoin should be treated in San Francisco, London and Berlin as well, especially if the outside world believes that most Bitcoiners embrace, or at least accept, this proposed regulation. 

As the first major regulatory body to consider blessing Bitcoin businesses and integrating them into the broader financial system, Lawsky and co will set legal precedents that matter regardless of where we ultimately do business.

I see no upside to simply telling off Lawsky and his colleagues, rather than waging a smart battle against some of the BitLicense’s ill-conceived provisions.  At the same time, I believe that our industry’s leaders should be more reserved in lauding - without qualifications - a flawed set of proposals.

Everyone in the community needs to step up in the next 45 days.  This applies to the largest funded Bitcoin ventures and leading advocates as well as to smaller entrepreneurs and general enthusiasts.  The larger ventures will have their legal teams draft up thorough responses to these proposals, but in many cases, they will not be deterred by the large compliance costs these new regulations assure. 

So while you can hope that the Bitcoin Foundation and/or Digital Asset Transfer Authority will address the concerns of the entrepreneur in their feedback, I can’t impress upon you enough how important it is for even the smallest ventures and future innovators to invest some time into smart and measured public comments that press the NYSDFS for less cumbersome and stifling requirements.

Please make the invaluable investment to voice your concerns.  There are no guarantees that the NYSDFS will pay attention to any particular comment, but with an abundance of pushback on some of the most egregious proposals, we should get some of the improvements we need.

In order to kickstart the discussion, we need to outline the good, the bad, and the ugly of the BitLicense regs.*  Below, I have attempted to address the largest errors and overreaches presented by the NYSDFS.  I hope this may serve as a springboard for others’ public comments.

*Please note, I am trying to sift through that which we can live with from that which is crippling.  I know crypto-anarchists would prefer that we defy the NYSDFS, but the BitLicense is real and inevitable, so I’m focusing on what absolutely needs modification.

The Good   

It’s important to recognize that these regulations are not all bad.  If you want to join the financial big leagues, you’d better get ready for the full regulatory proctological exam.  Background checks for key employees, shareholders and directors at BitLicensed companies make sense, and rigorous reviews of the companies’ financial and technical controls are hardly requirements that are unique to Bitcoin service providers.  When you are responsible for people’s money, you can and should be subject to personal reviews that others are not.

For similar reasons, the proposals for standardized cyber security programs, disaster recovery plans, and consumer protections, disclosures and marketing should be considered positive developments for the industry.  The final sections outline requirements that only stand to improve Bitcoin’s trustworthiness amongst consumers, merchants and investors, even if they do add some compliance costs.

In my opinion, there really aren’t many objections worth raising for a full 50% of the sections in the BitLicense (Sections 4-7, 16-21).  The notable exception being that a total lack of “tiering” means that a two person bootstrapped Bitcoin start-up would likely become a pipe dream. 

If the NYSDFS added an exemption for organizations processing less than a certain floor level of transaction volume, or at least radically streamlined the reporting processes for startups, they could capture the bulk of Bitcoin exchange volume without stifling new innovations.  Educated early adopters would likely test out the new, less-regulated ventures while the mainstream consumers could rely safely on their more thoroughly vetted counterparts.

The Bad

Aside from the lack of tiering, I believe that the true brutality of the BitLicense, can be quarantined to three primary oversights, which I have dubbed the Permission to Service, the Permission to Transact and the Permission to Innovate.  We must collectively fight tooth and nail against these provisions because their existence threatens the health and viability of Bitcoin as a technological revolution.

The Permission to Service

The NYSDFS’s definition of “Virtual Currency Business Activity” must either narrow or additional exemptions must be made for businesses who do not provide hosted storage or exchange services.  Currently, any firm providing currency exchange (Coinbase/Circle/itBit), payment processing (BitPay/Coinbase/Stripe), hosted wallets (Coinbase/Circle/Xapo), or investment management services (Pantera, BIT, Winklevii) must register for a BitLicense.  No surprise or problem there. 

But then the department overreaches by including under its purview many services that never actually access user funds.  These include wallets like Blockchain.info, tipping apps like Changetip, and mixing services like CoinJoin.  The inclusion of non-hosted wallets is especially troubling as it essentially outlaws the personal possession of Bitcoins for these users.  By imposing impossible reporting requirements on companies that in some cases literally cannot track user identity, the only solution for these services may be to restrict the IP addresses of users from certain locations.

We can argue that the onus should be on law enforcement to track illicit funds transferred to and from user controlled wallets, but given Ben Lawsky’s comments yesterday and apparent prioritization of the BitLicense’s anti-money laundering provisions, it appears the NYSDFS is going to great lengths to prevent this type of “leakage” regardless of the cost.  This shouldn’t be a surprise given his previously expressed willingness to sacrifice innovation for militant money laundering compliance, but it remains disheartening nonetheless. 

The department is banning people from owning their own digital cash privately.  Not only is this morally questionable, but it would make New York State the most restrictive regulatory environment in the world - and much more restrictive than even its federal counterparts.  Lawsky and the NYSDFS must understand that this is unacceptable if Bitcoin is to create jobs stimulate economic activity and foster much needed innovations in financial services.   

The Permission to Transact

The leakage concern spills over into the language that specifies that all parties in any Bitcoin transaction must be identified by name and physical address.  This is “CoinValidation” on steroids, and would create the equivalent of a closed loop Bitcoin network in which transactions would only be allowed by wallet providers if the counterpart to any one user’s transaction was also a known person.  Needless to say, this restriction would destroy much of Bitcoin’s utility as a payment network for those forced to comply.  Fungibility of the currency would be threatened.

Yet if we succeed in pressuring the NYSDFS to scrap its “Permission to Service” provision, then we also have an argument for limiting this “Permission to Transact” oversight as well.  In that scenario, regulators would still maintain the ability to monitor any suspicious activities from identified users at exchanges and hosted wallets, and authorities could track all inflows and outflows from unidentified addresses over time.  The BitLicense already allows for “enhanced due diligence” on suspicious transactions and could easily apply to those whose transactions appeared questionable. 

From a practical perspective, it strikes me as unlikely that many of the criminally inclines would attempt to launder money or evade taxes when using a BitLicensed exchange or wallet that carefully records and monitors 100% of their transaction history.  

However unpalatable, the NYSDFS must also recognize that it is impossible to prevent individuals from using open-source software to transact freely and privately.  It seems likely that the department’s crusade against anonymous Bitcoin users will fail at the same time it severely damages Bitcoin’s usability for honest actors.  The department would be better suited monitoring those who choose to utilize the services at Bitcoin’s licensed “banks” and exchanges. 

The Permission to Innovate

The most egregious restriction in the BitLicense seems to be the NYSDFS’s stranglehold on permissible innovation.  As a community, we should be aggressive in pushing back on the department’s claim to oversee and regulate new alt-currencies and similar decentralized tokens, as well as its insistence on reviewing new business plan proposals before they are ever even tested in the market. 

Under the BitLicense proposals, any party “controlling, administering or issuing a virtual currency” will require licensing.  This provision would have outlawed Satoshi Nakamoto’s original Bitcoin invention, and it certainly seems to ban any new alt-currencies and tokens that might be created in the future.  The detrimental effect this would have on innovation in New York and across the US cannot be understated. 

New currency innovators would be extremely unlikely to launch in the US, and would very likely follow the lead of Ethereum, Counterparty and other organizations in moving their legal operations overseas.  Once again, New York would pay a hefty price for no clear or likely benefit.

Finally, the BitLicense provisions in section 200.10 have the effect of banning all unapproved innovation, an entrepreneurial thought crime with no real legal precedent or positive effect.  The NYSDFS would be asking all entrepreneurs to submit their ideas for review to a regulatory body that appears unlikely to grasp many of the much simpler elements of Bitcoin’s technology.

The Ugly

That of course brings us to the ugly.  Advanced concepts like multi-signature transactions, decentralized autonomous organizations and applications, and other Bitcoin 2.0 concepts are not truly baked into this framework.  Rather, they are deemed guilty until proven innocent under the department’s broad umbrella of Virtual Currency Business Activity.

Other restrictions make some sense, but need further clarification to avoid unintended consequences.

For instance, mixing services appear to be banned under the BitLicense’s restriction on obfuscating Bitcoin transactions.  However, the NYSDFS would certainly agree that such mixing has positive use cases, such as offering the ability for users to hide their balance information from would be cyber-predators. 

Likewise, the department’s restriction on “permissible investments” makes sense for a Bitcoin bank or exchange that might be expected to separate its trading activity from its other business activities related to managing customer deposits (similar to Glass Steagall).  However, given the scope of entities who appear to require Bitlicenses, many businesses who do not receive deposits would be unfairly limited in their ability to hold virtual currency.

Finally, it is not unreasonable to question why Bitcoin businesses will be subjected to more rigorous anti-money laundering, know your customer and record-keeping standards than existing financial institutions who process many orders of magnitude more transactions (and have often been proven to fail in their charge to limit money laundering themselves).

***

Again, I hope this outline will prove a helpful starting point for those who wish to provide public comments.  The more challenging part - the part in which we should reasonably expect our industry’s top lawyers and regulatory experts to take the lead - will be to now craft compelling arguments that help the NYSDFS see the light and narrow the scope of their restrictions. 

The BitLicenses have transformative potential to legally integrate Bitcoin into the heavily regulated global financial system, but this potential will be squandered if some of the NYSDFS’s most cumbersome provisions are not modified or eliminated.

Community commentary

Manuel Heilmann:

"I think that regulations are better than no regulations although they may be inconvenient. It is the biggest hurdle for Bitcoin to reach mainstream. Therefore, all Bitcoin companies should embrace regulations and work with regulators. The requirements as proposed by the NYDFS are common and not shocking. However, the physical address will be a challenge for merchants that don't require it today for any sort of digital products, tickets, etc. I hope that other states will follow NY and copy the NY Bitlicense and make it easier for us to comply with regulations in every state."

Patrick Dugan:

"It is in no way surprising that the gatekeepers of the world's largest liquidity well would want to charge a toll in information, though the part dictating how a company invests its float was a bit much. I suspect the trillions in offshore wealth and the tens of trillions circulating through the City of London and Hong Kong may well compete with the approach taken by the State of New York.  There is a wide world out there."

 

Cointelegraph would like to thank author Ryan Selkis for this piece. Ryan is an entrepreneur, blogger and former venture capitalist. He has founded two separate Bitcoin ventures and writes a widely-followed daily blog under the moniker the "Two-Bit Idiot," where he discusses news, analysis and ideas for the Bitcoin industry. This article was originally published on Two-Bit Idiot’s blog.

Tips Are Always Appreciated

Financial tips: https://coinbase.com/twobitidiot

News tips: email [email protected]