More From Eric Dixon at http://www.NYBusinessCounsel.com

Top 50 Twitter Rank of Worldwide Startup Advisors For Much of 2014. Go to my professional site for solutions to your legal, business and strategic problems. The only lawyer who is a co-inventor of multiple, allowed-for-grant patents on blockchain technology!!! Blockchain and Digital Currency Protocol Development --
Top Strategic Judgment -- When You Need A Fixer -- Explore Information Protection and Cryptographic Security -- MUST-WIN: JUST DON'T LOSE -- SURVIVE!: Under Investigation? Being Sued? Handling Extreme Stress -- Corporate Issues -- Startup Issues -- Investor Issues -- Contracts To Meet Your Needs -- Opposition Research -- Intellectual Property, Media and Reputation Issues -- Independent, top-notch legal, strategic and personal advice -- Extensive ghostwriting, speechwriting, book writing, issue research, press and crisis management services. Listed by American Bar Association's Law Bloggers (Blawgers). Contact EDixon@NYBusinessCounsel.com. European Union audiences: This site uses a third party site administrator which may use cookies but this site is intended for AMERICAN clients and prospective clients only!

Sunday, June 19, 2016

Idiots and Smart Contracts

[Author's Note: The author is a co-inventor of two patent pending innovations currently before the United States Patent and Trademark Office for improvements to blockchain technology which would facilitate smart contract applications.]

One of the major blockchain distributed asset organizations was disrupted this weekend, causing a temporary 30-50% decline (in 36 hours!) in the value of certain related "cryptocurrencies." (Note that I avoid the use of the word "hack.")

The cause was -- we think, because it's not certain yet -- a flaw in the blockchain code underlying one of these supposedly shiny, bright new things. Now, codes fail, because their creators are imperfect. Nothing new there. It's also possible the code worked as designed, in which case the code itself was bad, not in operation but in planning, and then the "contract" within the code was flawed. If the latter explanation holds true, then the problem is the bad contract. Which brings me to my point.

The contract is the issue, because we have been hearing more and more in the financial press about this supposedly wonderful new innovation called a "smart contract." I've heard supposedly brilliant innovators talk about "smart contracts" for at least three years. These are the two words that make you sound really smart, or hip. Just like putting "dot com" behind any rubbish made you money 20 years ago.

Beware!

Underlying all this is an anti-intellectual arrogance. It's the arrogance bred from a disdain for the law, the rule of law, and lawyers, and the idea that non-lawyers can do contracts much better than lawyers -- who've been doing this for decades -- can do and have been. Now, you see the result.

The tragic flaw in the DAO, the subject of the attack? It might be the uncorrected confidence of people who have never done, that they know better -- and are better -- than those who have.

If you want a smart contract, you need to start with a strong understanding of a contract, how it is constructed, how it works, and what you're actually trying to do.

Until then, you're just a dreamer with a laptop and lots of unearned confidence, but no record of achievement to match. Ignorance is no substitute for knowledge.

Some more reading on this. http://www.ericdixonlaw.com/2016/03/what-hell-is-blockchain-smart-contract.html

Eric Dixon has been a New York lawyer since graduating from Yale Law School in 1994. He works with and is a shareholder in several blockchain startups and seed-stage ventures.

Saturday, June 4, 2016

When Should Unindicted Co-Conspirators Be Identified?

Do unindicted co-conspirators have a privacy right to keep their names secret from the public?

Do reputational or financial issues warrant this?

Does the unindicted co-conspirator's public employment (or other status) change the analysis? And should it? What about the Equal Protection Clause? Aren't we all equally subject to the law, and equally protected?

And what about the Sixth Amendment's Confrontation Clause? (More on that later.)

These and other issues are going to be involved in. or affected by the Third Circuit Court of Appeals' consideration Monday of a motion by a "John Doe" to keep his name secret.

PREVIOUS COMMENTARY: Click here

Some other facts: first, John Doe is an unindicted co-conspirator as that term is used by the federal government. It means that prosecutors have labelled him as such.

Understandably, John Doe is upset over the characterization. And unless John Doe is indicted, and takes the case to a jury, John Doe will never get the chance to confront the government, its witnesses and its evidence to determine whether he has in fact committed a federal crime.

This means that John Doe could be impugned by the characterization AND have no way to "confront his accusers." John Doe is actually deprived of his Constitutional right, because he is not an "accused." He gets the right to confront, and clear his name, only if he is "accused," that is, charged with a crime.

For that, let's turn to the Sixth Amendment of the U.S. Constitution, which provides:
" . . . in all criminal prosecutions, the accused shall enjoy the right . . . to be confronted with the witnesses against him."
To be simple, this means that you need a prosecution to trigger the right. No prosecution, no right. So anything short of being charged, and it sort of means the government gets to go open season on your reputation. Particularly since John Doe is not specifically identified. The rationale may be that any government action short of charging someone is not sufficiently injurious enough to implicate Constitutional rights. (A fascinating sidebar that should be explored more by the federal appellate and even the Supreme Court.)

Except that...

Except that John Doe is listed in court documents in the ongoing criminal cases of two other people as being a potential witness. This means that if those other two cases go to trial, the public may find out who John Doe is -- and John Doe could be a witness and testify and be subject to cross examination. It also means the testimony might be John Doe's way to "exonerate" himself, but it might also be a danger by showing things he might wish had never occurred or he had never said. He might never be charged but the revelations might be very damaging to his reputation and career.

One can also see how the government can use these considerations to bargain for the cooperation of people whom it could charge, but would agree not to, in exchange for witness testimony.

There are Justice Department guidelines on the naming of unindicted co-conspirators. See the following, straight from the United States Attorneys' Manual (with my emphasis in bold text):
In the absence of some significant justification, federal prosecutors generally should not identify unindicted co-conspirators in conspiracy indictments. The practice of naming individuals as unindicted co-conspirators in an indictment charging a criminal conspiracy has been severely criticized in United States v. Briggs, 514 F.2d 794 (5th Cir. 1975). 
Ordinarily, there is no need to name a person as an unindicted co-conspirator in an indictment in order to fulfill any legitimate prosecutorial interest or duty. For purposes of indictment itself, it is sufficient, for example, to allege that the defendant conspired with "another person or persons known." In any indictment where an allegation that the defendant conspired with "another person or persons known" is insufficient, some other generic reference should be used, such as "Employee 1" or "Company 2". The use of non-generic descriptors, like a person's actual initials, is usually an unnecessarily-specific description and should not be used. 
If identification of the person is required, it can be supplied, upon request, in a bill of particulars. See USAM 9-27.760. With respect to the trial, the person's identity and status as a co-conspirator can be established, for evidentiary purposes, through the introduction of proof sufficient to invoke the co-conspirator hearsay exception without subjecting the person to the burden of a formal accusation by a grand jury. 
In the absence of some significant justification, federal prosecutors generally should not identify unindicted co-conspirators in conspiracy indictments. 

Perhaps the solution is to have the Department of Justice further revise its guidelines governing how its prosecutors refer to unindicted co-conspirators. One way is to standardize how they are identified so that their identities cannot be ascertained, not even by investigative lawyers like the author.

The above guideline is overtly critical of certain practices. (The same United States Attorney's Office in New Jersey handling the Bridgegate investigation and related criminal cases, when under the auspices of possible current co-conspirator Governor Chris Christie as U.S. Attorney, used to identify co-conspirators with initials and residence hometowns, for example.) Clearly, there are ways to identify the players. For instance, if an indictment referred to a certain white former basketball player with curly blonde hair, you'd be pretty certain we're talking about Larry Bird.

Sometimes the opaque "CC-1" is used (CC for co-conspirator). But other times an acronym or phrase is used, often in conjunction with additional narrative detail as to the person's job, title, age or residence (any of which might serve absolutely no purpose for the purposes of a charging document relating to someone else) and it allows for good educated guesses. The problem is that the descriptions can and do allow for the identification of uncharged persons, who never get a chance to clear their names. This is not only unfair to the unindicted co-conspirator, who may never be charged and thus may suffer permanent and irreparable harm (basically, this is the "John Doe" situation), but his very safety may be jeopardized.

And it is quite possible that this reputational damage is done, quite on purpose, whether to pressure the uncharged and unindicted into cooperation (an exchange of testimony for a promise not to reveal or damage the person's reputation). A cynic could argue that this is exactly the type of psychological coercion designed to induce an investigative target to "agree to cooperate," essentially to safeguard his own safety. But then again, anyone who testifies -- and in open court, it's all public -- loses any anonymity or secrecy hopes anyway.

This was the case years ago in a high profile public corruption case where the U.S. Attorney's Office wrote up a charging indictment that referred to an unindicted co-conspirator as "State Official 1." Everyone quickly figured out who the Governor was. And that Governor -- now out of public life -- was never charged.

And never able to exonerate himself either.  Indeed, the "cloud" still hovers over that ex-Governor (whom by now you've probably been able to identify).

Let's remember these important issues and the need for reasoned balancing of the considerations at stake here. Perhaps this is a judgment to eventually be made by Congress.

A good news source to follow this emerging saga is the Record of Hackensack, which will be updating this story over the next few days. A link to their current story is here:
http://www.northjersey.com/news/john-doe-s-privacy-gets-day-in-court-in-gwb-case-1.1610512