Morici v. HashFast Technologies LLC

COMPLAINT - 1 Case No.
___________

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27

Venkat Balasubramani (SBN 189192)
FOCAL PLLC
800 Fifth Ave, Suite 4100
Seattle, WA 98104
Phone: (206) 529-4827
Fax: (206) 260-3966
Email: [email protected]
Attorneys for Plaintiff
PETE MORICI

UNITED STATES DISTRICT COURT
NORTHERN DISTRICT OF CALIFORNIA
SAN JOSE DIVISION

PETE MORICI, an individual,

Plaintiff,
v.

HASHFAST TECHNOLOGIES LLC, a
California limited liability company,
HASHFAST LLC, a Delaware limited liability
company, SIMON BARBER, an individual,
and EDUARDO deCASTRO, an individual,

Defendants.

Case No. ______________

COMPLAINT FOR DAMAGES,
RESTITUTION AND INJUNCTIVE RELIEF

(1) Breach of Contract
(2) Fraud
(3) Violation of Cal. Bus. & Prof. Code
17200, et seq.
(4) Declaratory Relief

JURY TRIAL DEMANDED

Plaintiff Pete Morici (Morici) alleges for his complaint against HashFast Technologies
LLC, HashFast LLC, and the principals of HashFast (collectively HashFast) as follows:
INTRODUCTION
This is a lawsuit seeking to enforce Moricis right to a refund for product ordered from
HashFast that was not delivered in a timely fashion. The product in questioncomputer
hardware configured specifically to mine Bitcoin digital currencyloses value daily, due to the
ever-increasing computing power necessary to mine the same amount of Bitcoin.
Consequently, the date of delivery was one of the most critical terms of the purchase. Although
HashFast represented at the time Morici placed his order, in August 2013, that delivery would
Case5:14-cv-00087 Document1 Filed01/07/14 Page1 of 15

COMPLAINT - 2 Case No. ___________

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27

occur between October 20, 2013 and October 30, 2013, and later assured Morici and other
customers on multiple occasions that delivery would occur within that time frame, HashFast
failed to make timely delivery. Instead, HashFast notified Morici on October 23, 2013, that
delivery would not occur until mid-November. However, on November 7, 2013, HashFast
again changed its delivery date, notifying Morici that delivery would not occur until mid-
December. Upon receiving HashFasts November notification, Morici cancelled his order and
requested a refund of the Bitcoin he paid to HashFast to purchase the product.
Despite repeated requests, HashFast has failed to offer Morici a full refund, likely due to
the fact that between the time Morici paid for the product and present day, the value of Bitcoin
has increased dramatically. HashFast should not be unjustly enriched as a result of its improper
actions and the change in value of the Bitcoin. Morici should be entitled to a refund, and this
refund should be tendered in Bitcoin (i.e., the number of Bitcoin that Morici tendered to
HashFast). This result is mandated both by the relevant legal principles and equity, and by the
understanding of the parties. HashFast has engaged in a systematic campaign of stringing along
its customers and making misleading statements and should not be allowed to profit from its
improper conduct. To the contrary, HashFast should be required to disgorge its ill-gotten gains.
THE PARTIES
1. Morici is a resident of, and domiciled in, the State of Maryland.
2. On information and belief, HashFast Technologies LLC is a limited liability
company organized and existing under the laws of the State of California, and HashFast LLC is
a limited liability company organized and existing under the laws of the State of Delaware. The
companies, which on information and belief are closely affiliated, or alter-egos for one another,
both have their principal places of business in San Jose, California.
3. On information and belief, Simon Barber and Eduardo deCastro are both
California residents, founders, members (owners) and officers of each of the HashFast limited
liability company entities.
4. At all times mentioned herein, defendants, and each of them, were an owner, a


1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27

co-owner, an agent, representative and/or alter ego of their co-defendants, or otherwise acting
on behalf of each and every remaining defendant and, in committing the acts hereinafter
alleged, were acting with the course and scope of their authorities as an owner, co-owner, agent,
representative and/or alter ego of its co-defendants, with the full knowledge, permission and
consent of each and every other defendant, each co-defendant having ratified the acts of the
other co-defendants.
5. Wherever appearing in this complaint, each and every reference to defendants, or
any of them, is intended to be and shall be a reference to all defendants hereto, and to each of
them, unless said reference is otherwise specifically qualified.
JURISDICTION AND VENUE
6. HashFast Technologies LLC is subject to personal jurisdiction in the State of
California because it is a California limited liability company having its principal place of
business in San Jose, California, and it is engaged in systematic and continuous contacts with
the State of California by virtue of its business activities here. HashFast LLC is also subject to
personal jurisdiction in the State of California because it has its principal place of business in
the State of California and is engaged in systematic and continuous contacts with the State of
California by virtue of its business activities here. The principals of HashFast are likewise
subject to jurisdiction in the State of California either by being residents of the State of
California, or by reason of their extensive contacts with the State of California, in the form of
HashFast-related activities. Alternatively, to the extent there is no general jurisdiction over the
principals of HashFast, they have purposefully aimed their conduct to the State of California,
through their activities with HashFast, and should reasonably expect to be sued in the State of
California.
7. The Court has jurisdiction over the subject matter of the dispute under 28 USC
1332. Morici and the HashFast entities and principals are citizens of different states and the
amount in controversy exceeds seventy five thousand dollars ($75,000.00).
8. Venue is proper in this judicial district under 28 USC 1391(b)(1) and (2)


1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27

because HashFast is based in this judicial district and, alternatively, because a substantial part of
the events or omissions giving rise to the Moricis claims occurred, or a substantial part of the
property that is the subject of the action is situated in this judicial district.
FACTS
BITCOINS BACKGROUND
9. Bitcoin is a peer-to-peer payment network that uses digital currency known as
Bitcoin (abbreviated as BTC). The Bitcoin network is decentralized, with no authority
overseeing its operation, and uses open-source encryption software for transactions. Every
Bitcoin transaction is permanently recorded and is maintained in a transparent public ledger.
The original technical paper describing Bitcoin can be found here: http://bitcoin.org/bitcoin.pdf.
10. Payment transactions are processed by a network of private computers
distributed throughout the world which, typically, have been specially configured for processing
Bitcoin transactions. These computers are commonly referred to as Bitcoin computers, and
the operators of such computers are known as miners. Miners are partially compensated for
the work they perform by receiving fees for the Bitcoin transactions that they process through
their Bitcoin computers.
11. The Bitcoin system also incentivizes miners to process transactions by allowing
miners to create new Bitcoins for themselves based on the number of blocks discovered.
Blocks are files containing data regarding Bitcoin transactions that have yet to be recorded in
the public ledger. The process of discovering a block involves calculating a SHA256 hash, an
algorithm that is very difficult to solve, over and over again until the miner finds an input that
matches an expected output. The chance that a miner will discover a given block, and thereby
claim its Bitcoin reward before another miner, are based on the miners hash rate relative to
the total hash rate of all Bitcoin miners on the network. This incentive creates an inherent
competitive environment in which miners seek to increase their rate of processing.
Consequently, miners are constantly looking to increase the processing power of their Bitcoin
computers. Thus, acquisition of the latest technology is crucial for miners, and to those who


1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27

purchase and sell Bitcoin mining equipment, the timing of shipment is inherently important.
12. The difficulty of Bitcoin mining is continually adjusted based on the rate at
which blocks are created. Thus, as competition increases, so does the difficulty in processing.
As a result, a Bitcoin mining computer continually becomes less valuable over time, as it
becomes relatively less efficient at processing Bitcoin blocks. Eventually, without upgrading
technology, the electricity required for processing will cost a miner more than the Bitcoin
computer is able to generate.
13. As the adoption of the Bitcoin system has increased, technology companies have
sprung up to serve the Bitcoin mining market, developing specialized computers to conduct
Bitcoin mining. Defendant HashFast is one such company.
14. Bitcoin value fluctuates based on supply and demand. Importantly, the Bitcoin
system includes a cap on the total number of Bitcoins that will be made available21,000,000
Bitcoins. Currently, the number of Bitcoins in circulation is approximately 12,185,000.
MORICIS ORDERS FROM HASHFAST
15. Like many members of the Bitcoin community, Mr. Morici was a participant in
the internet message board and community known as Bitcoin Talk. HashFast was also a
participant in this community, and starting in July 2013, made several posts about their soon-to-
be-launched Bitcoin mining computer.
16. HashFast engaged in a wide range of promotion via Bitcoin Talk, including
(1) inviting members to visit their offices, (2) announcing partnerships and supply
arrangements, and (3) stating that their order process would be fully transparent. For example,
in late August, HashFast purported to announce some specs for [HashFasts] mining chip,
going so far as to attach a letter from a third party partner. HashFast said that they would also
be open and transparent about their sales queue.
17. Most importantly, HashFast posted publicly statements that shipments would be
made in late October. On August 5, 2013, HashFast stated We will be shipping [the mining
product] in October. A screenshot of this post by HashFast is attached as Exhibit A hereto. A


1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27

screenshot of this post may also be viewed at:
https://bitcointalk.org/index.php?topic=262052.msg2869016#msg2869016. On August 8, 2013,
HashFast stated that HashFast is launching sales of the Baby Jet [mining product], and further
stated Shipments begin: October 20th-30th, in order of purchase. A screenshot of this post by
HashFast is attached as Exhibit B hereto. A screenshot of this post may also be viewed at:
https://bitcointalk.org/index.php?topic=270384.msg2894615#msg2894615.
18. HashFast operates a website located at http://www.hashfast.com (the Site).
HashFast describes itself on the Site as a leader in Bitcoin mining technology. See
http://hashfast.com/about-us/. The domain name <hashfast.com> is registered to Edward
Decastro.
19. On August 10, 2013, Mr. Morici visited the Site in the course of deciding
whether to order a Bitcoin mining computer from HashFast. After reviewing the product
information provided on the Site for HashFasts Baby Jet Bitcoin mining computer, including
the products technical specifications and HashFasts stated delivery dates, Mr. Morici decided
that the Baby Jet was the product he wished to purchase.
20. In choosing the Baby Jet, Mr. Morici relied on HashFasts representations and
warranties on the Site, including HashFasts claim that it had units of the Baby Jet in stock,
with shipments starting October 20-30. A screenshot of the webpage on the Site that was
substantially similar to what was viewed by Mr. Morici at the time of placing his order is
attached as Exhibit C hereto. Nothing on the product page indicated that there was any
uncertainty as to the current availability of the product or HashFasts ability to ship the product
in a timely fashion.
21. Although the Site contained functionality that allowed online ordering, on the
date Mr. Morici visited the Site (August 10, 2013), the Site was unavailable to process orders.
Therefore, Mr. Morici contacted Hashfast that day, and in response, John Skrodenis, Vice
President of HashFast, instructed Mr. Morici to place his order manually (by telephone and
email). In an email to Mr. Morici, Mr. Skrodenis offered free shipping.


1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27

22. In a subsequent telephone conversation with Mr. Skrodenis that same day, Mr.
Morici specifically raised the question of whether HashFasts advertised delivery dates of
October 20-30 were firm, and whether there was any possibility that HashFast would not meet
its advertised dates. Mr. Skrodenis was emphatic in assuring Mr. Morici, saying: that is not
going to happen.
23. Later that day, per Mr. Skrodenis instructions, Mr. Morici placed an order with
HashFast for two (2) Baby Jets at a total cost of $11,200 USD. Despite Mr. Skrodenis promise
of free shipping, HashFast also charged Mr. Morici $307.38 USD for shipping, making the total
transaction cost $11,507.38 USD. Payment on the transaction was to be made in Bitcoin, with
the cost amounting to 107.692308 BTC for the Baby Jets, 2.95557692 BTC for shipping, for a
total of 110.67773274 BTC.
24. HashFast stated in public posts on Bitcoin Talk that it would have credit card
processing available, but at the time Mr. Morici and numerous others placed their orders, the
only payment option made available by HashFast was in BTC. Had credit card processing been
made available by HashFast, Mr. Morici would have opted to pay using his credit card.
25. Neither the applicable terms of purchase, nor HashFasts public comments
indicated that refunds, if necessary, would be paid in U.S. Dollars. In fact, HashFast
represented that refunds would be paid in Bitcoin. In a public post on Bitcoin Talk made on
August 10, 2013, the day Mr. Morici placed his order, HashFast, through Mr. Barber, advised
that Orders are taken in BTC, in the unlikely event we get to refunds they will be given in
BTC. Attached as Exhibit D hereto is a true and correct copy of this post. The post may also
be viewed at: https://bitcointalk.org/index.php?topic=270384.msg2903338#msg2903338.
Another customer was also advised specifically that refunds would be paid in BTC. Attached as
Exhibit E hereto is a true and correct copy of this post. The post may also be viewed at:
26. Mr. Morici confirmed his order via email that day and paid a deposit in the
amount of 110.647885 BTC. On August 15, 2013, in response to a follow-up query from Mr.


1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27

Morici, HashFast advised that [the] transaction successfully went through, and your order has
been complete.
27. On August 19, 2013, nine days after Mr. Morici placed his order, HashFast sent
an order confirmation to Mr. Morici via email. The order confirmation contained additional
terms regarding the delivery date, and also contained an attachment, on a separate page, with
further terms and conditions. The email to Mr. Morici transmitting the order confirmation did
not reference the additional terms of the order confirmation, nor did the email indicate that
further terms and conditions were attached to the order confirmation. Mr. Morici did not
review any of these additional terms or agree to these terms.
28. Mr. Moricis order was order number M002, which, according to a list posted by
HashFast on the Site (at http://hashfast.com/order-chain/), placed him in Batch 1 of the
customers who ordered the Baby Jet (i.e., these customers would be the first to receive the Baby
Jet).
29. As HashFast is undoubtedly aware, Bitcoin mining computers lose their value at
a rapid rate due to the fact that more powerful computers are needed to effectively mine for
Bitcoins as time goes on. Cognizant of this, Mr. Morici placed his order with the expectation
and understanding that his computers would be delivered in October. Indeed, to Mr. Morici,
this was a critical term of the transaction.
THE MINER PROTECTION PROGRAM AND VAGUE SPECIFICATIONS
30. Mr. Moricis order was covered by what HashFast calls its Miner Protection
Program (MPP) (https://hashfast.com/miner-protection-program/), which HashFast announced
on August 13, 2013, and agreed to provide retroactively to all purchases of Batch 1 Baby Jets.
The MPP ostensibly provided that if a purchaser did not break even in Bitcoin terms (through
mining) within ninety (90) days after receiving their order, HashFast would automatically
supply the purchaser up to 400% more hashing power in the form of modules. A module, in
Hashfasts parlance, is one of Hashfasts chips on a printed circuit board, to be used in
connection with the Baby Jet mining computer.


1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27

31. HashFashts rollout of the Miner Protection Program is further evidence of its
understanding that the timing of shipment of the product was critically important.
32. In light of delays in fulfilling customer orders, HashFast modified the terms of
the MPP, representing that they would start the ninety day clock for the MPP as if they had
shipped their products by their originally advertised October 30, 2013 shipping date. In other
words, HashFast agreed to give all customers similarly situated to Mr. Morici four additional
modules some time after February 1, 2014, if the customers did not break even through their
mining activities.
33. In product specifications published on the Site prior to Mr. Morici placing his
order, HashFast stated that the Baby Jet contained a chip capable of processing at a speed of 400
Gh/s (400 billion hashes per second) while consuming 1 watt per Gh/s. Subsequently, after
testing, HashFast stated that the chip contained in the Baby Jet could run at up to 500 Gh/s.
However, it wasn't clear what the power consumption was at that speed, or if that speed was
sustainable without over heating during 24/7 operation.
34. While processing speed is obviously important, power consumption also matters
because at some point, as the Bitcoin computer produces less and less Bitcoin each month, the
USD value of the Bitcoin being produced is less than the cost of electricity required to operate
the Bitcoin computer. For example, at the current Bitcoin exchange rate, the Baby Jet computer
is likely to become unprofitable in late 2014.
35. To date, despite promises to do so, HashFast has yet to release the full
specifications for the product.
DELAYS AND CANCELLATION
36. Following placement of Mr. Moricis order, HashFast continued to reaffirm that
it would make deliveries in October. On August 11, 2013, HashFast stated in a post on Bitcoin
Talk: [w]e understand the importance of schedule . . . and we're confident we can deliver.
Attached as Exhibit F hereto is a true and correct copy of this post. The post can also be
viewed at: https://bitcointalk.org/index.php?topic=262052.msg2908364#msg2908364.


1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27

37. Also on August 11, 2013, in a post on Bitcoin Talk, a poster posited that if
HashFast ended up shipping in December, rather than October, HashFasts customers would
take a bath. In response, Mr. deCastro stated we wont, and also stated that HashFast would
protect its customers against hashrate increases. Attached as Exhibit G hereto is a true and
correct copy of this post. The post can also be viewed at:
38. On August 18, 2013, in response to a pointed question on Bitcoin Talk from a
customer as to whether the expected ship date of late October still look[ed] achievable? John
Skrodenis of HashFast responded Yes. We are exactly on track. Attached as Exhibit H
hereto is a true and correct copy of this post. The post may also be viewed at:
39. Nevertheless, on October 23, 2013, HashFast informed Mr. Morici via email that
his initial order would be delayed because one of HashFasts vendors allegedly had not supplied
it with certain components necessary to produce the products in question. This came as a
surprise to Mr. Morici, because HashFast represented at the time Mr. Morici placed his order
that it had a sufficient number of units of the Baby Jet mining computers in-stock, with
shipments starting October 20-30. Additionally, Mr. Morici had been advised during a phone
call with Mr. Skrodenis, HashFasts Vice President, and by HashFasts principals repeatedly on
Bitcoin Talk, that there would be no slippage in the delivery dates. Based on those
representations, Mr. Morici reasonably believed that the order would ship by no later than
October 30th.
40. Though HashFasts October 23, 2013 email to Mr. Morici goes on to admit that
time is money, HashFast informed Mr. Morici that his shipment would not be delivered by
late October, but instead would be delivered in mid-November.
41. HashFast failed to deliver to Mr. Morici his initial order in October as promised,
and incredibly, on November 7, 2013, HashFast sent Mr. Morici yet another email informing
him that his order would not be shipped until mid-December.


1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27

42. None of the email notices sent by HashFast contained any reference to Mr.
Moricis cancellation or refund rights.
43. As HashFast itself has admitted in its marketing material, in email
correspondence with Mr. Morici, and in posts at Bitcoin Talk, the value of a Bitcoin mining
computer decreases as time goes on. Realizing that the Baby Jet Bitcoin computers he ordered
would be of considerably less value in light of the new estimated delivery date (which
apparently was a moving target), and more troubling, having legitimate concerns that he had
been defrauded, at 3:42 PM on November 11, 2013, Mr. Morici sent an email to HashFast
canceling his order and requesting a full refund of his deposit (in BTC, as agreed to by
HashFast).
44. HashFast did not respond to Mr. Moricis refund request until over a month later.
45. On December 27, 2013, HashFast sent out an email to its customers, including
Mr. Morici, stating that they expected to be on track to ship . . . orders December 31.
However, on December 29, 2013, HashFast sent out a follow-up email stating that they were
kicking off . . . shipments in the next few days, but customers who were interested in refunds
could initiate refunds and be paid Bitcoin calculated at the exchange rate on the date of the
refund. The offer of refund in U.S. Dollars came as a surprise to Mr. Morici, given the
assurances and agreement of HashFast that refunds would be made in BTC.
46. On December 31, 2013, HashFast sent out another email to Mr. Morici, advising
that HashFast had hoped to resolve reliability issues sooner so that [HashFast] could begin
bulk production and be on track to ship Batch 1 customer orders on December 31.
Unfortunately, the email continued, stating that the issues have not been adequately resolved,
and therefore [HashFast is] unable to ship the remaining outstanding orders by December 31st.
47. Attached to HashFasts December 31st email was a detailed and onerous release
form purporting to require, as a condition of obtaining a refund, among other things, a promise
to not disparage, libel, or criticize [HashFast] or publish any statement concerning [HashFast]
this is critical.


1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27

48. HashFast purported to ship an item to Morici, but the shipment was partial, and
in any event, came too little too late. Given the more than two month delay in shipment, Mr.
Morici cancelled the order.
FIRST CLAIM FOR RELIEF
(Breach of Contract)
49. Morici realleges and incorporates by reference all preceding paragraphs of the
Complaint.
50. Moricis order placed via telephone on August 10, 2013, was an enforceable
agreement which required delivery of two Baby Jets by no later than October 30, 2013.
51. HashFast was aware of the time-sensitive nature of the delivery date for the
product and made specific assurances to Mr. Morici regarding the delivery deadline.
HashFasts failure to deliver the product by its advertised delivery date is a material breach of
the agreement.
52. Morici has been damaged by HashFasts actions and is entitled to be
compensated for any resulting damages, or alternatively, is entitled to a refund (in BTC) as per
the terms of the contract, or to rescind the contract and receive restitution.
SECOND CLAIM FOR RELIEF
(Fraud)
Complaint.
54. HashFast and its principals made false statements of material fact to Morici
regarding its product, including: (1) the delivery date for the product; (2) whether HashFast
actually had any product in stock; and (3) the computing power of the product and the efficacy
of the MPP.
55. Morici relied on the statements to his detriment and his reliance was reasonable.
56. Morici has been damaged as a result of such reliance and should be compensated
for any injury suffered by him.


1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27

THIRD CLAIM FOR RELIEF
(Violation of Cal. Bus. & Prof. Code 17200, et seq.)
Complaint.
58. The acts and practices of HashFast as alleged herein constitute unlawful business
acts and practices within the meaning of Cal. Bus. & Prof. Code 17200, et seq. HashFast has
engaged in unlawful business acts and practices as alleged above, but in particular by their
violation of Cal. Civ. Code 1723, which requires merchants to conspicuously display any
no-refund policies, and to provide refunds to customers who attempt to return goods within 30
days of purchase. HashFast has engaged in unfair business practices as alleged above, but in
particular by failing to provide Morici with the option to consent to a delayed shipping date or
cancel his order, in violation of 16 C.F.R. 435.2. Further, HashFast has engaged in unfair
business practices as alleged above, but in particular by inducing Mr. Morici to purchase
HashFasts products by making inaccurate representations regarding delivery times and failing
to follow the aforementioned laws governing Mr. Moricis cancellation and refund rights.
59. HashFasts actions have caused Morici damage.
60. HashFast has been unjustly enriched and should be required to make restitution
to Morici pursuant to Cal. Bus. & Prof. Code 1723.
FOURTH CLAIM FOR RELIEF
(Declaratory Relief)
Complaint.
62. Although HashFast and Morici are parties to a contract, HashFast has at several
turns attempted to impose onerous terms on Morici. Specifically, HashFast denied Moricis
right to cancel his order and receive a refund.
63. Specifically, although state and federal law require HashFast to provide Mr.
Morici with a full refund due to HashFasts failure to timely deliver the product, HashFast


1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27

attempted to condition Mr. Moricis request for a refund on numerous additional terms,
including a release of claims, a refund amount that calculates the amount of the refund in then-
current Bitcoin exchange rates, and a promise to not make any critical statements about
HashFast.
64. Mr. Morici is entitled to a declaration that these terms are unenforceable and
contrary to state and federal law.
PRAYER FOR RELIEF
Morici requests entry of judgment as follows:
a. Damages proximately flowing from HashFasts breach of the agreement;
b. At Mr. Moricis election, rescission of the agreement;
c. Damages and all other available remedies caused by HashFasts fraudulent and
misleading statements;
d. Restitution and other relief available under Cal. Bus. & Prof. Code 17200, et
seq.;
e. A declaration that the additional terms HashFast has attempted to impose on
Morici in order to obtain a refund are unlawful and unenforceable;
f. An order requiring HashFast to place Morici in the same position as he would
have been prior to placing the order;
g. Damages to be entered in BTC, as the operative currency for the transaction and
as per the parties understanding;
h. An order that the principals of HashFast are personally liable for any award
against HashFast; and
i. Other and further relief, in law or equity, that the Court may deem appropriate
and just.
//
//
//


1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27

Dated: January 7, 2014 Respectfully submitted,
FOCAL PLLC

By: s/Venkat Balasubramani
Venkat Balasubramani (SBN 189192)

800 Fifth Ave, Suite 4100
Seattle, WA 98104
Phone: (206) 529-4827
Fax: (206) 260-3966
Email: [email protected]

Attorneys for Plaintiff
PETE MORICI

Morici v. HashFast Technologies LLC

Uploaded by

Copyright:

Available Formats

Morici v. HashFast Technologies LLC

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Morici v. HashFast Technologies LLC

Uploaded by

Copyright:

Available Formats

COMPLAINT - 1 Case No.

You might also like