├── .gitignore
├── LICENSE
├── README.md
├── cli
├── bcash-broadcast.js
├── bcash-instadump.js
├── bcash-tx.js
├── bcash-utxo.js
└── common.js
├── electrum-servers.json
├── lib
├── electrum.js
├── make-tx.js
├── patch-bcoin-bcash.js
├── shapeshift.js
├── socket.js
└── utxo.js
├── npm-shrinkwrap.json
├── package.json
├── screenshot.png
└── utility
└── tor-newnym.sh
/.gitignore:
--------------------------------------------------------------------------------
1 | node_modules
2 |
--------------------------------------------------------------------------------
/LICENSE:
--------------------------------------------------------------------------------
1 | GNU GENERAL PUBLIC LICENSE
2 | Version 3, 29 June 2007
3 |
4 | Copyright (C) 2007 Free Software Foundation, Inc.
5 | Everyone is permitted to copy and distribute verbatim copies
6 | of this license document, but changing it is not allowed.
7 |
8 | Preamble
9 |
10 | The GNU General Public License is a free, copyleft license for
11 | software and other kinds of works.
12 |
13 | The licenses for most software and other practical works are designed
14 | to take away your freedom to share and change the works. By contrast,
15 | the GNU General Public License is intended to guarantee your freedom to
16 | share and change all versions of a program--to make sure it remains free
17 | software for all its users. We, the Free Software Foundation, use the
18 | GNU General Public License for most of our software; it applies also to
19 | any other work released this way by its authors. You can apply it to
20 | your programs, too.
21 |
22 | When we speak of free software, we are referring to freedom, not
23 | price. Our General Public Licenses are designed to make sure that you
24 | have the freedom to distribute copies of free software (and charge for
25 | them if you wish), that you receive source code or can get it if you
26 | want it, that you can change the software or use pieces of it in new
27 | free programs, and that you know you can do these things.
28 |
29 | To protect your rights, we need to prevent others from denying you
30 | these rights or asking you to surrender the rights. Therefore, you have
31 | certain responsibilities if you distribute copies of the software, or if
32 | you modify it: responsibilities to respect the freedom of others.
33 |
34 | For example, if you distribute copies of such a program, whether
35 | gratis or for a fee, you must pass on to the recipients the same
36 | freedoms that you received. You must make sure that they, too, receive
37 | or can get the source code. And you must show them these terms so they
38 | know their rights.
39 |
40 | Developers that use the GNU GPL protect your rights with two steps:
41 | (1) assert copyright on the software, and (2) offer you this License
42 | giving you legal permission to copy, distribute and/or modify it.
43 |
44 | For the developers' and authors' protection, the GPL clearly explains
45 | that there is no warranty for this free software. For both users' and
46 | authors' sake, the GPL requires that modified versions be marked as
47 | changed, so that their problems will not be attributed erroneously to
48 | authors of previous versions.
49 |
50 | Some devices are designed to deny users access to install or run
51 | modified versions of the software inside them, although the manufacturer
52 | can do so. This is fundamentally incompatible with the aim of
53 | protecting users' freedom to change the software. The systematic
54 | pattern of such abuse occurs in the area of products for individuals to
55 | use, which is precisely where it is most unacceptable. Therefore, we
56 | have designed this version of the GPL to prohibit the practice for those
57 | products. If such problems arise substantially in other domains, we
58 | stand ready to extend this provision to those domains in future versions
59 | of the GPL, as needed to protect the freedom of users.
60 |
61 | Finally, every program is threatened constantly by software patents.
62 | States should not allow patents to restrict development and use of
63 | software on general-purpose computers, but in those that do, we wish to
64 | avoid the special danger that patents applied to a free program could
65 | make it effectively proprietary. To prevent this, the GPL assures that
66 | patents cannot be used to render the program non-free.
67 |
68 | The precise terms and conditions for copying, distribution and
69 | modification follow.
70 |
71 | TERMS AND CONDITIONS
72 |
73 | 0. Definitions.
74 |
75 | "This License" refers to version 3 of the GNU General Public License.
76 |
77 | "Copyright" also means copyright-like laws that apply to other kinds of
78 | works, such as semiconductor masks.
79 |
80 | "The Program" refers to any copyrightable work licensed under this
81 | License. Each licensee is addressed as "you". "Licensees" and
82 | "recipients" may be individuals or organizations.
83 |
84 | To "modify" a work means to copy from or adapt all or part of the work
85 | in a fashion requiring copyright permission, other than the making of an
86 | exact copy. The resulting work is called a "modified version" of the
87 | earlier work or a work "based on" the earlier work.
88 |
89 | A "covered work" means either the unmodified Program or a work based
90 | on the Program.
91 |
92 | To "propagate" a work means to do anything with it that, without
93 | permission, would make you directly or secondarily liable for
94 | infringement under applicable copyright law, except executing it on a
95 | computer or modifying a private copy. Propagation includes copying,
96 | distribution (with or without modification), making available to the
97 | public, and in some countries other activities as well.
98 |
99 | To "convey" a work means any kind of propagation that enables other
100 | parties to make or receive copies. Mere interaction with a user through
101 | a computer network, with no transfer of a copy, is not conveying.
102 |
103 | An interactive user interface displays "Appropriate Legal Notices"
104 | to the extent that it includes a convenient and prominently visible
105 | feature that (1) displays an appropriate copyright notice, and (2)
106 | tells the user that there is no warranty for the work (except to the
107 | extent that warranties are provided), that licensees may convey the
108 | work under this License, and how to view a copy of this License. If
109 | the interface presents a list of user commands or options, such as a
110 | menu, a prominent item in the list meets this criterion.
111 |
112 | 1. Source Code.
113 |
114 | The "source code" for a work means the preferred form of the work
115 | for making modifications to it. "Object code" means any non-source
116 | form of a work.
117 |
118 | A "Standard Interface" means an interface that either is an official
119 | standard defined by a recognized standards body, or, in the case of
120 | interfaces specified for a particular programming language, one that
121 | is widely used among developers working in that language.
122 |
123 | The "System Libraries" of an executable work include anything, other
124 | than the work as a whole, that (a) is included in the normal form of
125 | packaging a Major Component, but which is not part of that Major
126 | Component, and (b) serves only to enable use of the work with that
127 | Major Component, or to implement a Standard Interface for which an
128 | implementation is available to the public in source code form. A
129 | "Major Component", in this context, means a major essential component
130 | (kernel, window system, and so on) of the specific operating system
131 | (if any) on which the executable work runs, or a compiler used to
132 | produce the work, or an object code interpreter used to run it.
133 |
134 | The "Corresponding Source" for a work in object code form means all
135 | the source code needed to generate, install, and (for an executable
136 | work) run the object code and to modify the work, including scripts to
137 | control those activities. However, it does not include the work's
138 | System Libraries, or general-purpose tools or generally available free
139 | programs which are used unmodified in performing those activities but
140 | which are not part of the work. For example, Corresponding Source
141 | includes interface definition files associated with source files for
142 | the work, and the source code for shared libraries and dynamically
143 | linked subprograms that the work is specifically designed to require,
144 | such as by intimate data communication or control flow between those
145 | subprograms and other parts of the work.
146 |
147 | The Corresponding Source need not include anything that users
148 | can regenerate automatically from other parts of the Corresponding
149 | Source.
150 |
151 | The Corresponding Source for a work in source code form is that
152 | same work.
153 |
154 | 2. Basic Permissions.
155 |
156 | All rights granted under this License are granted for the term of
157 | copyright on the Program, and are irrevocable provided the stated
158 | conditions are met. This License explicitly affirms your unlimited
159 | permission to run the unmodified Program. The output from running a
160 | covered work is covered by this License only if the output, given its
161 | content, constitutes a covered work. This License acknowledges your
162 | rights of fair use or other equivalent, as provided by copyright law.
163 |
164 | You may make, run and propagate covered works that you do not
165 | convey, without conditions so long as your license otherwise remains
166 | in force. You may convey covered works to others for the sole purpose
167 | of having them make modifications exclusively for you, or provide you
168 | with facilities for running those works, provided that you comply with
169 | the terms of this License in conveying all material for which you do
170 | not control copyright. Those thus making or running the covered works
171 | for you must do so exclusively on your behalf, under your direction
172 | and control, on terms that prohibit them from making any copies of
173 | your copyrighted material outside their relationship with you.
174 |
175 | Conveying under any other circumstances is permitted solely under
176 | the conditions stated below. Sublicensing is not allowed; section 10
177 | makes it unnecessary.
178 |
179 | 3. Protecting Users' Legal Rights From Anti-Circumvention Law.
180 |
181 | No covered work shall be deemed part of an effective technological
182 | measure under any applicable law fulfilling obligations under article
183 | 11 of the WIPO copyright treaty adopted on 20 December 1996, or
184 | similar laws prohibiting or restricting circumvention of such
185 | measures.
186 |
187 | When you convey a covered work, you waive any legal power to forbid
188 | circumvention of technological measures to the extent such circumvention
189 | is effected by exercising rights under this License with respect to
190 | the covered work, and you disclaim any intention to limit operation or
191 | modification of the work as a means of enforcing, against the work's
192 | users, your or third parties' legal rights to forbid circumvention of
193 | technological measures.
194 |
195 | 4. Conveying Verbatim Copies.
196 |
197 | You may convey verbatim copies of the Program's source code as you
198 | receive it, in any medium, provided that you conspicuously and
199 | appropriately publish on each copy an appropriate copyright notice;
200 | keep intact all notices stating that this License and any
201 | non-permissive terms added in accord with section 7 apply to the code;
202 | keep intact all notices of the absence of any warranty; and give all
203 | recipients a copy of this License along with the Program.
204 |
205 | You may charge any price or no price for each copy that you convey,
206 | and you may offer support or warranty protection for a fee.
207 |
208 | 5. Conveying Modified Source Versions.
209 |
210 | You may convey a work based on the Program, or the modifications to
211 | produce it from the Program, in the form of source code under the
212 | terms of section 4, provided that you also meet all of these conditions:
213 |
214 | a) The work must carry prominent notices stating that you modified
215 | it, and giving a relevant date.
216 |
217 | b) The work must carry prominent notices stating that it is
218 | released under this License and any conditions added under section
219 | 7. This requirement modifies the requirement in section 4 to
220 | "keep intact all notices".
221 |
222 | c) You must license the entire work, as a whole, under this
223 | License to anyone who comes into possession of a copy. This
224 | License will therefore apply, along with any applicable section 7
225 | additional terms, to the whole of the work, and all its parts,
226 | regardless of how they are packaged. This License gives no
227 | permission to license the work in any other way, but it does not
228 | invalidate such permission if you have separately received it.
229 |
230 | d) If the work has interactive user interfaces, each must display
231 | Appropriate Legal Notices; however, if the Program has interactive
232 | interfaces that do not display Appropriate Legal Notices, your
233 | work need not make them do so.
234 |
235 | A compilation of a covered work with other separate and independent
236 | works, which are not by their nature extensions of the covered work,
237 | and which are not combined with it such as to form a larger program,
238 | in or on a volume of a storage or distribution medium, is called an
239 | "aggregate" if the compilation and its resulting copyright are not
240 | used to limit the access or legal rights of the compilation's users
241 | beyond what the individual works permit. Inclusion of a covered work
242 | in an aggregate does not cause this License to apply to the other
243 | parts of the aggregate.
244 |
245 | 6. Conveying Non-Source Forms.
246 |
247 | You may convey a covered work in object code form under the terms
248 | of sections 4 and 5, provided that you also convey the
249 | machine-readable Corresponding Source under the terms of this License,
250 | in one of these ways:
251 |
252 | a) Convey the object code in, or embodied in, a physical product
253 | (including a physical distribution medium), accompanied by the
254 | Corresponding Source fixed on a durable physical medium
255 | customarily used for software interchange.
256 |
257 | b) Convey the object code in, or embodied in, a physical product
258 | (including a physical distribution medium), accompanied by a
259 | written offer, valid for at least three years and valid for as
260 | long as you offer spare parts or customer support for that product
261 | model, to give anyone who possesses the object code either (1) a
262 | copy of the Corresponding Source for all the software in the
263 | product that is covered by this License, on a durable physical
264 | medium customarily used for software interchange, for a price no
265 | more than your reasonable cost of physically performing this
266 | conveying of source, or (2) access to copy the
267 | Corresponding Source from a network server at no charge.
268 |
269 | c) Convey individual copies of the object code with a copy of the
270 | written offer to provide the Corresponding Source. This
271 | alternative is allowed only occasionally and noncommercially, and
272 | only if you received the object code with such an offer, in accord
273 | with subsection 6b.
274 |
275 | d) Convey the object code by offering access from a designated
276 | place (gratis or for a charge), and offer equivalent access to the
277 | Corresponding Source in the same way through the same place at no
278 | further charge. You need not require recipients to copy the
279 | Corresponding Source along with the object code. If the place to
280 | copy the object code is a network server, the Corresponding Source
281 | may be on a different server (operated by you or a third party)
282 | that supports equivalent copying facilities, provided you maintain
283 | clear directions next to the object code saying where to find the
284 | Corresponding Source. Regardless of what server hosts the
285 | Corresponding Source, you remain obligated to ensure that it is
286 | available for as long as needed to satisfy these requirements.
287 |
288 | e) Convey the object code using peer-to-peer transmission, provided
289 | you inform other peers where the object code and Corresponding
290 | Source of the work are being offered to the general public at no
291 | charge under subsection 6d.
292 |
293 | A separable portion of the object code, whose source code is excluded
294 | from the Corresponding Source as a System Library, need not be
295 | included in conveying the object code work.
296 |
297 | A "User Product" is either (1) a "consumer product", which means any
298 | tangible personal property which is normally used for personal, family,
299 | or household purposes, or (2) anything designed or sold for incorporation
300 | into a dwelling. In determining whether a product is a consumer product,
301 | doubtful cases shall be resolved in favor of coverage. For a particular
302 | product received by a particular user, "normally used" refers to a
303 | typical or common use of that class of product, regardless of the status
304 | of the particular user or of the way in which the particular user
305 | actually uses, or expects or is expected to use, the product. A product
306 | is a consumer product regardless of whether the product has substantial
307 | commercial, industrial or non-consumer uses, unless such uses represent
308 | the only significant mode of use of the product.
309 |
310 | "Installation Information" for a User Product means any methods,
311 | procedures, authorization keys, or other information required to install
312 | and execute modified versions of a covered work in that User Product from
313 | a modified version of its Corresponding Source. The information must
314 | suffice to ensure that the continued functioning of the modified object
315 | code is in no case prevented or interfered with solely because
316 | modification has been made.
317 |
318 | If you convey an object code work under this section in, or with, or
319 | specifically for use in, a User Product, and the conveying occurs as
320 | part of a transaction in which the right of possession and use of the
321 | User Product is transferred to the recipient in perpetuity or for a
322 | fixed term (regardless of how the transaction is characterized), the
323 | Corresponding Source conveyed under this section must be accompanied
324 | by the Installation Information. But this requirement does not apply
325 | if neither you nor any third party retains the ability to install
326 | modified object code on the User Product (for example, the work has
327 | been installed in ROM).
328 |
329 | The requirement to provide Installation Information does not include a
330 | requirement to continue to provide support service, warranty, or updates
331 | for a work that has been modified or installed by the recipient, or for
332 | the User Product in which it has been modified or installed. Access to a
333 | network may be denied when the modification itself materially and
334 | adversely affects the operation of the network or violates the rules and
335 | protocols for communication across the network.
336 |
337 | Corresponding Source conveyed, and Installation Information provided,
338 | in accord with this section must be in a format that is publicly
339 | documented (and with an implementation available to the public in
340 | source code form), and must require no special password or key for
341 | unpacking, reading or copying.
342 |
343 | 7. Additional Terms.
344 |
345 | "Additional permissions" are terms that supplement the terms of this
346 | License by making exceptions from one or more of its conditions.
347 | Additional permissions that are applicable to the entire Program shall
348 | be treated as though they were included in this License, to the extent
349 | that they are valid under applicable law. If additional permissions
350 | apply only to part of the Program, that part may be used separately
351 | under those permissions, but the entire Program remains governed by
352 | this License without regard to the additional permissions.
353 |
354 | When you convey a copy of a covered work, you may at your option
355 | remove any additional permissions from that copy, or from any part of
356 | it. (Additional permissions may be written to require their own
357 | removal in certain cases when you modify the work.) You may place
358 | additional permissions on material, added by you to a covered work,
359 | for which you have or can give appropriate copyright permission.
360 |
361 | Notwithstanding any other provision of this License, for material you
362 | add to a covered work, you may (if authorized by the copyright holders of
363 | that material) supplement the terms of this License with terms:
364 |
365 | a) Disclaiming warranty or limiting liability differently from the
366 | terms of sections 15 and 16 of this License; or
367 |
368 | b) Requiring preservation of specified reasonable legal notices or
369 | author attributions in that material or in the Appropriate Legal
370 | Notices displayed by works containing it; or
371 |
372 | c) Prohibiting misrepresentation of the origin of that material, or
373 | requiring that modified versions of such material be marked in
374 | reasonable ways as different from the original version; or
375 |
376 | d) Limiting the use for publicity purposes of names of licensors or
377 | authors of the material; or
378 |
379 | e) Declining to grant rights under trademark law for use of some
380 | trade names, trademarks, or service marks; or
381 |
382 | f) Requiring indemnification of licensors and authors of that
383 | material by anyone who conveys the material (or modified versions of
384 | it) with contractual assumptions of liability to the recipient, for
385 | any liability that these contractual assumptions directly impose on
386 | those licensors and authors.
387 |
388 | All other non-permissive additional terms are considered "further
389 | restrictions" within the meaning of section 10. If the Program as you
390 | received it, or any part of it, contains a notice stating that it is
391 | governed by this License along with a term that is a further
392 | restriction, you may remove that term. If a license document contains
393 | a further restriction but permits relicensing or conveying under this
394 | License, you may add to a covered work material governed by the terms
395 | of that license document, provided that the further restriction does
396 | not survive such relicensing or conveying.
397 |
398 | If you add terms to a covered work in accord with this section, you
399 | must place, in the relevant source files, a statement of the
400 | additional terms that apply to those files, or a notice indicating
401 | where to find the applicable terms.
402 |
403 | Additional terms, permissive or non-permissive, may be stated in the
404 | form of a separately written license, or stated as exceptions;
405 | the above requirements apply either way.
406 |
407 | 8. Termination.
408 |
409 | You may not propagate or modify a covered work except as expressly
410 | provided under this License. Any attempt otherwise to propagate or
411 | modify it is void, and will automatically terminate your rights under
412 | this License (including any patent licenses granted under the third
413 | paragraph of section 11).
414 |
415 | However, if you cease all violation of this License, then your
416 | license from a particular copyright holder is reinstated (a)
417 | provisionally, unless and until the copyright holder explicitly and
418 | finally terminates your license, and (b) permanently, if the copyright
419 | holder fails to notify you of the violation by some reasonable means
420 | prior to 60 days after the cessation.
421 |
422 | Moreover, your license from a particular copyright holder is
423 | reinstated permanently if the copyright holder notifies you of the
424 | violation by some reasonable means, this is the first time you have
425 | received notice of violation of this License (for any work) from that
426 | copyright holder, and you cure the violation prior to 30 days after
427 | your receipt of the notice.
428 |
429 | Termination of your rights under this section does not terminate the
430 | licenses of parties who have received copies or rights from you under
431 | this License. If your rights have been terminated and not permanently
432 | reinstated, you do not qualify to receive new licenses for the same
433 | material under section 10.
434 |
435 | 9. Acceptance Not Required for Having Copies.
436 |
437 | You are not required to accept this License in order to receive or
438 | run a copy of the Program. Ancillary propagation of a covered work
439 | occurring solely as a consequence of using peer-to-peer transmission
440 | to receive a copy likewise does not require acceptance. However,
441 | nothing other than this License grants you permission to propagate or
442 | modify any covered work. These actions infringe copyright if you do
443 | not accept this License. Therefore, by modifying or propagating a
444 | covered work, you indicate your acceptance of this License to do so.
445 |
446 | 10. Automatic Licensing of Downstream Recipients.
447 |
448 | Each time you convey a covered work, the recipient automatically
449 | receives a license from the original licensors, to run, modify and
450 | propagate that work, subject to this License. You are not responsible
451 | for enforcing compliance by third parties with this License.
452 |
453 | An "entity transaction" is a transaction transferring control of an
454 | organization, or substantially all assets of one, or subdividing an
455 | organization, or merging organizations. If propagation of a covered
456 | work results from an entity transaction, each party to that
457 | transaction who receives a copy of the work also receives whatever
458 | licenses to the work the party's predecessor in interest had or could
459 | give under the previous paragraph, plus a right to possession of the
460 | Corresponding Source of the work from the predecessor in interest, if
461 | the predecessor has it or can get it with reasonable efforts.
462 |
463 | You may not impose any further restrictions on the exercise of the
464 | rights granted or affirmed under this License. For example, you may
465 | not impose a license fee, royalty, or other charge for exercise of
466 | rights granted under this License, and you may not initiate litigation
467 | (including a cross-claim or counterclaim in a lawsuit) alleging that
468 | any patent claim is infringed by making, using, selling, offering for
469 | sale, or importing the Program or any portion of it.
470 |
471 | 11. Patents.
472 |
473 | A "contributor" is a copyright holder who authorizes use under this
474 | License of the Program or a work on which the Program is based. The
475 | work thus licensed is called the contributor's "contributor version".
476 |
477 | A contributor's "essential patent claims" are all patent claims
478 | owned or controlled by the contributor, whether already acquired or
479 | hereafter acquired, that would be infringed by some manner, permitted
480 | by this License, of making, using, or selling its contributor version,
481 | but do not include claims that would be infringed only as a
482 | consequence of further modification of the contributor version. For
483 | purposes of this definition, "control" includes the right to grant
484 | patent sublicenses in a manner consistent with the requirements of
485 | this License.
486 |
487 | Each contributor grants you a non-exclusive, worldwide, royalty-free
488 | patent license under the contributor's essential patent claims, to
489 | make, use, sell, offer for sale, import and otherwise run, modify and
490 | propagate the contents of its contributor version.
491 |
492 | In the following three paragraphs, a "patent license" is any express
493 | agreement or commitment, however denominated, not to enforce a patent
494 | (such as an express permission to practice a patent or covenant not to
495 | sue for patent infringement). To "grant" such a patent license to a
496 | party means to make such an agreement or commitment not to enforce a
497 | patent against the party.
498 |
499 | If you convey a covered work, knowingly relying on a patent license,
500 | and the Corresponding Source of the work is not available for anyone
501 | to copy, free of charge and under the terms of this License, through a
502 | publicly available network server or other readily accessible means,
503 | then you must either (1) cause the Corresponding Source to be so
504 | available, or (2) arrange to deprive yourself of the benefit of the
505 | patent license for this particular work, or (3) arrange, in a manner
506 | consistent with the requirements of this License, to extend the patent
507 | license to downstream recipients. "Knowingly relying" means you have
508 | actual knowledge that, but for the patent license, your conveying the
509 | covered work in a country, or your recipient's use of the covered work
510 | in a country, would infringe one or more identifiable patents in that
511 | country that you have reason to believe are valid.
512 |
513 | If, pursuant to or in connection with a single transaction or
514 | arrangement, you convey, or propagate by procuring conveyance of, a
515 | covered work, and grant a patent license to some of the parties
516 | receiving the covered work authorizing them to use, propagate, modify
517 | or convey a specific copy of the covered work, then the patent license
518 | you grant is automatically extended to all recipients of the covered
519 | work and works based on it.
520 |
521 | A patent license is "discriminatory" if it does not include within
522 | the scope of its coverage, prohibits the exercise of, or is
523 | conditioned on the non-exercise of one or more of the rights that are
524 | specifically granted under this License. You may not convey a covered
525 | work if you are a party to an arrangement with a third party that is
526 | in the business of distributing software, under which you make payment
527 | to the third party based on the extent of your activity of conveying
528 | the work, and under which the third party grants, to any of the
529 | parties who would receive the covered work from you, a discriminatory
530 | patent license (a) in connection with copies of the covered work
531 | conveyed by you (or copies made from those copies), or (b) primarily
532 | for and in connection with specific products or compilations that
533 | contain the covered work, unless you entered into that arrangement,
534 | or that patent license was granted, prior to 28 March 2007.
535 |
536 | Nothing in this License shall be construed as excluding or limiting
537 | any implied license or other defenses to infringement that may
538 | otherwise be available to you under applicable patent law.
539 |
540 | 12. No Surrender of Others' Freedom.
541 |
542 | If conditions are imposed on you (whether by court order, agreement or
543 | otherwise) that contradict the conditions of this License, they do not
544 | excuse you from the conditions of this License. If you cannot convey a
545 | covered work so as to satisfy simultaneously your obligations under this
546 | License and any other pertinent obligations, then as a consequence you may
547 | not convey it at all. For example, if you agree to terms that obligate you
548 | to collect a royalty for further conveying from those to whom you convey
549 | the Program, the only way you could satisfy both those terms and this
550 | License would be to refrain entirely from conveying the Program.
551 |
552 | 13. Use with the GNU Affero General Public License.
553 |
554 | Notwithstanding any other provision of this License, you have
555 | permission to link or combine any covered work with a work licensed
556 | under version 3 of the GNU Affero General Public License into a single
557 | combined work, and to convey the resulting work. The terms of this
558 | License will continue to apply to the part which is the covered work,
559 | but the special requirements of the GNU Affero General Public License,
560 | section 13, concerning interaction through a network will apply to the
561 | combination as such.
562 |
563 | 14. Revised Versions of this License.
564 |
565 | The Free Software Foundation may publish revised and/or new versions of
566 | the GNU General Public License from time to time. Such new versions will
567 | be similar in spirit to the present version, but may differ in detail to
568 | address new problems or concerns.
569 |
570 | Each version is given a distinguishing version number. If the
571 | Program specifies that a certain numbered version of the GNU General
572 | Public License "or any later version" applies to it, you have the
573 | option of following the terms and conditions either of that numbered
574 | version or of any later version published by the Free Software
575 | Foundation. If the Program does not specify a version number of the
576 | GNU General Public License, you may choose any version ever published
577 | by the Free Software Foundation.
578 |
579 | If the Program specifies that a proxy can decide which future
580 | versions of the GNU General Public License can be used, that proxy's
581 | public statement of acceptance of a version permanently authorizes you
582 | to choose that version for the Program.
583 |
584 | Later license versions may give you additional or different
585 | permissions. However, no additional obligations are imposed on any
586 | author or copyright holder as a result of your choosing to follow a
587 | later version.
588 |
589 | 15. Disclaimer of Warranty.
590 |
591 | THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY
592 | APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT
593 | HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY
594 | OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO,
595 | THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
596 | PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM
597 | IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF
598 | ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
599 |
600 | 16. Limitation of Liability.
601 |
602 | IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
603 | WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS
604 | THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY
605 | GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE
606 | USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF
607 | DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD
608 | PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS),
609 | EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF
610 | SUCH DAMAGES.
611 |
612 | 17. Interpretation of Sections 15 and 16.
613 |
614 | If the disclaimer of warranty and limitation of liability provided
615 | above cannot be given local legal effect according to their terms,
616 | reviewing courts shall apply local law that most closely approximates
617 | an absolute waiver of all civil liability in connection with the
618 | Program, unless a warranty or assumption of liability accompanies a
619 | copy of the Program in return for a fee.
620 |
621 | END OF TERMS AND CONDITIONS
622 |
623 | How to Apply These Terms to Your New Programs
624 |
625 | If you develop a new program, and you want it to be of the greatest
626 | possible use to the public, the best way to achieve this is to make it
627 | free software which everyone can redistribute and change under these terms.
628 |
629 | To do so, attach the following notices to the program. It is safest
630 | to attach them to the start of each source file to most effectively
631 | state the exclusion of warranty; and each file should have at least
632 | the "copyright" line and a pointer to where the full notice is found.
633 |
634 | {one line to give the program's name and a brief idea of what it does.}
635 | Copyright (C) {year} {name of author}
636 |
637 | This program is free software: you can redistribute it and/or modify
638 | it under the terms of the GNU General Public License as published by
639 | the Free Software Foundation, either version 3 of the License, or
640 | (at your option) any later version.
641 |
642 | This program is distributed in the hope that it will be useful,
643 | but WITHOUT ANY WARRANTY; without even the implied warranty of
644 | MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
645 | GNU General Public License for more details.
646 |
647 | You should have received a copy of the GNU General Public License
648 | along with this program. If not, see .
649 |
650 | Also add information on how to contact you by electronic and paper mail.
651 |
652 | If the program does terminal interaction, make it output a short
653 | notice like this when it starts in an interactive mode:
654 |
655 | {project} Copyright (C) {year} {fullname}
656 | This program comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
657 | This is free software, and you are welcome to redistribute it
658 | under certain conditions; type `show c' for details.
659 |
660 | The hypothetical commands `show w' and `show c' should show the appropriate
661 | parts of the General Public License. Of course, your program's commands
662 | might be different; for a GUI interface, you would use an "about box".
663 |
664 | You should also get your employer (if you work as a programmer) or school,
665 | if any, to sign a "copyright disclaimer" for the program, if necessary.
666 | For more information on this, and how to apply and follow the GNU GPL, see
667 | .
668 |
669 | The GNU General Public License does not permit incorporating your program
670 | into proprietary programs. If your program is a subroutine library, you
671 | may consider it more useful to permit linking proprietary applications with
672 | the library. If this is what you want to do, use the GNU Lesser General
673 | Public License instead of this License. But first, please read
674 | .
675 |
--------------------------------------------------------------------------------
/README.md:
--------------------------------------------------------------------------------
1 | # bcash-instadump
2 |
3 | CLI tools for insta-dumping bcash in exchange for bitcoins (`bcash-instadump`),
4 | creating bcash-compatible transactions (`bcash-tx`),
5 | listing unspent bcash outputs (`bcash-utxo`)
6 | and broadcasting raw bcash transactions (`bcash-broadcast`).
7 |
8 | No bcash wallet or exchange account necessary.
9 |
10 | Developed by [Nadav Ivgi](https://www.bitrated.com/nadav) ([@shesek](https://twitter.com/shesek))
11 | of [Bitrated](https://www.bitrated.com/).
12 | *1HNDUy34hrqoTEChCZZjb6vWAU9APAKG78*
13 |
14 | **TL;DR**
15 |
16 | $ bcash-instadump --tor --key LmyBcashKeyWIF --payout 1myBtcAddr
17 | # confirm the details and press Y to sell your bcash and get your bitcoins
18 |
19 | (yes, that's it! but do read the whole thing to fully understand the risks involved.)
20 |
21 | **Warning! This software could put your bitcoins, bcash and privacy at risk.**
22 |
23 | These tools are meant for technically advanced users.
24 | Using them incorrectly (or even correctly!) could result in loss of funds and privacy.
25 | If you don't consider yourself a technical user, please seek advice from someone who is.
26 |
27 | Make sure to read *all* the instructions *carefully* before doing anything.
28 | You can use these tools in a way that doesn't risk your bitcoins,
29 | by moving them out first. There are also instructions for signing offline.
30 | See "*Instructions*" below.
31 |
32 | THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND. USE AT YOUR OWK RISK.
33 |
34 | ## Install
35 |
36 | *Requires nodejs 6.0.0 or newer.*
37 |
38 | The quick, less safe way:
39 |
40 | $ npm install -g bcash-instadump
41 |
42 | The safer way: find a Git commit reference published by a third-party security auditor that you trust, then:
43 |
44 | $ npm install -g git://github.com/shesek/bcash-instadump#[GIT-COMMIT-SHA256-HERE]
45 |
46 | There are currently no security audits that I'm aware of,
47 | but the code is < 500 SLOC if you want to review it yourself.
48 | If you do, you should publicly announce the hash for the Git commit you reviewed
49 | (and [tell me!](https://github.com/shesek/bcash-instadump/issues/new)).
50 |
51 | ## CLI tools
52 |
53 | ### `bcash-instadump` - dump bcash on ShapeShift
54 |
55 | $ bcash-instadump --key LmyBcashKeyWIF --payout 1myBtcAddr
56 |
57 | Insta-dump the bcash held in the provided `--key` (in base58 WIF)
58 | on [ShapeShift](https://shapeshift.io/)
59 | and send the purchased BTC to the bitcoin address provided in `--payout`.
60 | Shows details and asks for a confirmation before actually dumping.
61 |
62 | Using `--key ` will load all of the unspent outputs belonging to ``.
63 | To add specific inputs instead, you can use `--input txid,vout,amount,key`.
64 | Loading unspent outputs is done using the
65 | [Electrum bcash servers](https://github.com/shesek/bcash-instadump/blob/master/electrum-servers.json)
66 | (see "*Privacy considerations*" below).
67 |
68 | You can specify both `--key` and `--input` multiple times,
69 | or specify a file with `--keys keys.txt` and `--inputs utxos.csv`.
70 | All the inputs will be joined together in a single transaction (see "*Privacy considerations*" below).
71 | Only `p2pkh` scripts are currently supported.
72 |
73 | You can set your bcash refund address with `--refund `
74 | (used by ShapeShift in case anything goes wrong with the exchange).
75 | Defaults to the address associated with the first key provided.
76 |
77 | Specify `--feerate` to control the transaction fee (in `satoshis/byte`).
78 | Defaults to `rand(50,100)`.
79 |
80 | Use `--whateverjustdump` to skip all confirmations (for exchange rates, miner fees, etc) and just dump.
81 | This is probably a terrible idea.
82 |
83 | ShapeShift is used with a referrer code that tips the author of this tool.
84 | This can be disabled with `--noreferral`.
85 |
86 | The `--(no)proxy`, `--tor` and `--electrum` options are the same as for `bcash-tx` (below).
87 |
88 | See `bcash-instadump --help` for the full list of options.
89 |
90 | **The author of this tool is not affiliated with ShapeShift.**
91 | There are reports of orders failing with ShapeShift
92 | despite the funds being sent. Reaching out to ShapeShift's
93 | customer support should usually resolve that.
94 |
95 | ----
96 |
97 | Screenshot of `bcash-instadump` in action (dummy details, of course):
98 |
99 | 
100 |
101 | ----
102 |
103 | ### `bcash-tx`- make bcash-compatible transactions
104 |
105 | $ bcash-tx --input txid:vout:amount:key --output 1BcashAddr:ALL --feerate 250
106 |
107 | Create and sign a bcash-compatible transaction with the provided inputs and outputs.
108 | The transaction will be invalid on the Bitcoin network.
109 |
110 | `--output addr:amount` can be used multiple times.
111 | Use `ALL` as the `amount` to send the maximum available amount minus tx fees, or specify the amount in whole bitcoins.
112 | `--feerate` is only relevant if `ALL` is used.
113 |
114 | Specify `--inspect` to print the decoded transaction instead of its raw hex representation.
115 |
116 | Use `--broadcast` to broadcast the transaction via an Electrum bcash server
117 | (also see `bcash-broadcast` if you already have a raw transaction ready).
118 |
119 | Use `--proxy [socks4a|socks5h]://user:pass@host:port` or `--tor` to connect to the Electrum server over a proxy,
120 | or `--noproxy` to connect without one (see "*Privacy considerations*" below).
121 |
122 | You can configure a custom Electrum bcash server using `--electrum [tls|tcp]://host:port`.
123 | If not provided, one is chosen at random (from `electrum-servers.json`).
124 |
125 | See `bcash-tx --help` for the full list of options.
126 |
127 | ----
128 |
129 | ### `bcash-utxo` - list unspent bcash outputs
130 |
131 | $ bcash-utxo 1myFirstAddr 1myOtherAddr ...
132 |
133 | Get the unspent bcash outputs for the provided address(es) from the Electrum bcash servers,
134 | and print them as CSV (`txid,vout,amount,address` format).
135 |
136 | You may also provide keys instead of addresses.
137 | In this case, the CSV format would be `txid,vout,amount,key`
138 | (same as the format expected by `bcash-instadump` and `bcash-tx`).
139 |
140 | Specify `--file ` to read the list of addresses/keys from `` (one per line) instead of from arguments.
141 |
142 | This will leak information to the Electrum bcash servers (see "*Privacy considerations*" below).
143 |
144 | The `--(no)proxy`, `--tor` and `--electrum` options are the same as for `bcash-tx`.
145 |
146 | See `bcash-utxo --help` for the full list of options.
147 |
148 | ----
149 |
150 | ### `bcash-broadcast` - broadcast raw bcash transactions
151 |
152 | $ bcash-broadcast
153 |
154 | Broadcasts the provided `rawtx` (in hex) to the bcash network via an Electrum bcash server.
155 |
156 | The `--(no)proxy`, `--tor` and `--electrum` options are the same as for `bcash-tx`.
157 |
158 | See `bcash-broadcast --help` for the full list of options.
159 |
160 | ----
161 |
162 | ## Instructions & gotchas
163 |
164 | ### Protect your BTC
165 |
166 | **Move your bitcoins first!** To avoid risking your BTC, keys with a BTC balance should never be exposed to this tool.
167 | Make sure the keys provided to this software are *entirely emptied of BTC* and hold BCH only.
168 |
169 | ### Extracting unspent outputs and keys
170 |
171 | #### From Bitcoin Core:
172 |
173 | ```bash
174 | $ bitcoin-cli listunspent | jq -c '.[] | [.txid,.vout,.amount,.address]' | tr -d '[]"' \
175 | | awk -F, '{"bitcoin-cli dumpprivkey "$4 | getline key; print $1 FS $2 FS $3 FS key }' \
176 | > utxos.csv
177 | ```
178 |
179 | #### From Electrum:
180 |
181 | ```bash
182 | $ electrum listunspent | jq -c '.[] | [.prevout_hash,.prevout_n,.value,.address]' | tr -d '[]"' \
183 | | awk -F, '{"electrum getprivatekeys "$4"|jq -r .[0]" | getline key; print $1 FS $2 FS $3 FS key }' \
184 | > utxos.csv
185 |
186 | # @TODO assumes p2pkh outputs, will break with multisig
187 | ```
188 |
189 | #### From a list of keys:
190 |
191 | Prepare `keys.txt` with a list of base58 WIF keys (one per line), then:
192 |
193 | ```bash
194 | $ bcash-utxo -f keys.txt > utxos.csv
195 | ```
196 |
197 | WARNING: looking up the unspent outputs associated with your addresses
198 | will leak information to the Electrum bcash servers.
199 | See "*Privacy considerations*" below for suggestions to improve privacy.
200 |
201 | #### Dumping from the UTXO CSV file
202 |
203 | ```bash
204 | $ bcash-instadump --inputs utxos.csv --payout 1myBtcAddr
205 | ```
206 |
207 | ### Signing offline
208 |
209 | To sign offline, you can use [browserify](http://browserify.org/) to create a portable version
210 | of `bcash-tx` with all of its dependencies bundled in a single `.js` file,
211 | and run that from the offline machine (requires nodejs >=6.0.0).
212 |
213 | ```bash
214 | # Online machine - prepare portable bundle
215 | satoshi@hot:~$ npm install -g browserify
216 | satoshi@hot:~$ git clone https://github.com/shesek/bcash-instadump#[COMMIT-SHA256] && cd bcash-instadump
217 | satoshi@hot:~$ npm install
218 | satoshi@hot:~$ browserify --bare cli/bcash-tx.js > /media/usb/bcash-tx.js
219 |
220 | # Online machine - prepare list of outputs
221 | satoshi@hot:~$ bcash-utxo --tor 1myFirstAddr 1myOtherAddr > /media/usb/utxos.csv
222 | # WARNING: will leak information to the Electrum bcash servers, see "Privacy considerations"
223 |
224 | # Offline machine - sign bcash transaction
225 | satoshi@cold:~$ edit utxos.csv # change 4th column from address to key
226 | satoshi@cold:~$ node /media/usb/bcash-tx.js --inputs utxos.csv --output 1myBcashAddr:ALL --inspect
227 | satoshi@cold:~$ node /media/usb/bcash-tx.js --inputs utxos.csv --output 1myBcashAddr:ALL > /media/usb/signed.tx
228 |
229 | # Online machine - broadcast to the bcash network
230 | satoshi@hot:~$ bcash-broadcast --tor `cat /media/usb/signed.tx`
231 | ```
232 |
233 | ### Splitting coins
234 |
235 | If your coins are too big to be sold with one order (due to ShapeShift's limits),
236 | you can split them up with `bcash-tx` and make several orders.
237 |
238 | For example, to split a 10 BCH output into two 4.995 BCH orders
239 | (leaving some for mining fees),
240 | use something like:
241 |
242 | ```bash
243 | $ bcash-tx --tor --broadcast --key LmyBcashKeyWithLargeOutput \
244 | --output 1myBcashAddr1:4.995 --output 1myBcashAddr2:4.995
245 | # take note of the resulting
246 | $ bcash-instadump --tor --input ,0,4.995,LkeyForAddr1 --payout 1myBtcAddr1
247 | $ bcash-instadump --tor --input ,1,4.995,LkeyForAddr2 --payout 1myBtcAddr2
248 | ```
249 |
250 | ### Dump specific UTXOs
251 |
252 | `bcash-instadump --key ` will by default dump all of the
253 | unspent outputs available to ``.
254 | To select specific ones, use:
255 |
256 | ```bash
257 | $ bcash-utxo --tor LmyBcashKey > utxos.csv
258 | $ edit utxos.csv # leave just the ones you want to dump
259 | $ bcash-instadump --tor --inputs utxos.csv --payout 1btcAddr
260 | ```
261 |
262 | ### Privacy considerations
263 |
264 | #### Leaking data to the public blockchain
265 |
266 | Merging your unspent outputs together (in a single multi-input transaction)
267 | will reveal the link between them (and their associated addresses)
268 | on the public bitcoin/bcash blockchains, *to the entire world*.
269 |
270 | It is recommended to invoke `bcash-instadump` multiple times,
271 | once for each unspent output being sold (creating a separate 1-in,1-out tx each time)
272 | and with a different `--payout` address. Ideally, this should also be spread out over time.
273 | This could be accomplished using a bash script along the lines of:
274 |
275 | ```bash
276 | $ cat utxos.csv | xargs -L 1 bash -c 'sleep $[ ( $RANDOM % 3600 ) ]s &&
277 | bcash-instadump --input $0 --payout `bitcoin-cli getnewaddress` --whateverjustdump'
278 | ```
279 |
280 | #### Leaking data to ShapeShift
281 |
282 | Selling all of your unspent outputs from the same IP address
283 | will reveal the link between your outputs (and their associated addresses) to ShapeShift
284 | and to anyone gaining access to their systems (via hacking, a legal warrant, or otherwise).
285 |
286 | It is recommended to sell one output at a time and use `--proxy` or `--tor` to connect over a proxy.
287 | Preferably, use a proxy with a different public IP address for each request
288 | (otherwise the transactions would not be linked to your real IP address, but still linked to each-other. see more on that below.)
289 |
290 | #### Leaking data to the Electrum bcash servers
291 |
292 | The Electrum bcash servers are used for two purposes:
293 | *(1)* Broadcasting raw transactions to the bcash network
294 | (for `bcash-instadump` and `bcash-tx --broadcast`),
295 | and *(2)* Fetching the unspent bcash outputs associated with your addresses
296 | (for `bcash-utxo` and `bcash-instadump --key).
297 |
298 | This gives the Electrum servers the ability to link your transactions/addresses/outputs
299 | to each-other and to your IP address.
300 |
301 | To completely mitigate this leakage, you should ideally broadcast transactions and
302 | fetch unspent outputs using a bcash full node under your full control, connected over Tor.
303 |
304 | However, if running a full node is not possible or desirable,
305 | you can also retain better privacy by using a proxy -
306 | with the same caveat mentioned above regarding different public IP addresses.
307 | To switch public IP addresses between address lookups,
308 | you can use Tor, the [tor-newnym](https://raw.githubusercontent.com/shesek/bcash-instadump/master/utility/tor-newnym.sh)
309 | script available in `utility/`, and something like:
310 |
311 | ```bash
312 | $ cat addresses-or-keys.txt | xargs -L 1 bash -c '
313 | ./tor-newnym.sh && sleep $[ ( $RANDOM % 180) ]s &&
314 | bcash-utxo --tor $0' \
315 | > utxos.csv
316 | ```
317 |
318 | Under the default Tor configuration, the control port is 9151 and authentication is done using the cookie file.
319 | This should work: ```./tor-newnym.sh 9151 "`cat /path/to/tor/control_auth_cookie`"```.
320 | See the [Tor manual](https://www.torproject.org/docs/tor-manual.html.en#ControlPort) for
321 | more information about control port configuration and authentication.
322 |
323 | (`tor-newnym` will hopefully soon be integrated into the tool itself. PRs welcome!)
324 |
325 | In addition, it is also recommended that you use a random Electrum bcash server for each lookup.
326 | This is the default behaviour if you don't provide a specific server via `--electrum`.
327 |
328 | ## Contributing
329 |
330 | Pull requests are welcome! Some interesting next steps are:
331 |
332 | - A tool to prepare the list of unspent outputs based on the HD master seed.
333 |
334 | - Creating a GUI frontend (packaged as a browser extension, an [Electron](https://electron.atom.io/) app, or something else?)
335 |
336 | - Optimize input-merging behavior to improve privacy.
337 |
338 | - Multi-signature support (currently only `p2pkh` scripts are supported)
339 |
340 | - Connect to the Tor control port to change circuits (`NEWNYM` signal) between
341 | address lookups in `bcash-utxo`.
342 |
343 | - Tests (there aren't any! :scream::scream:)
344 |
345 | - Have any other cool ideas? [Let me know!](https://github.com/shesek/bcash-instadump/issues/new)
346 |
347 | ## License
348 |
349 | This software is released under the GPL v3 license.
350 | See LICENSE for more details.
351 |
--------------------------------------------------------------------------------
/cli/bcash-broadcast.js:
--------------------------------------------------------------------------------
1 | #!/usr/bin/env node
2 |
3 | const
4 | C = require('chalk')
5 | , Electrum = require('../lib/electrum')
6 | , { formatSat, initArgs, printErr } = require('./common')
7 |
8 | const args = require('commander')
9 | .version(require('../package.json').version)
10 | .description('Broadcast raw transactions to the bcash network.')
11 | .usage('[options] ')
12 |
13 | .option('-e, --electrum ', 'electrum server, must be bcash-compatible [default: random server]')
14 | .option('-p, --proxy ', 'proxy for connecting to electrum server')
15 | .option('-t, --tor', 'shortcut for --proxy socks5h://127.0.0.1:9150')
16 | .option('-N, --noproxy', 'set if you\'re sure you don\'t want to use a proxy')
17 |
18 | .on('--help', _ => console.log('\n README:', C.underline('https://github.com/shesek/bcash-instadump'), '(really, do!)\n'))
19 |
20 | .parse(process.argv)
21 |
22 | if (!args.args.length) args.help()
23 | initArgs(args)
24 |
25 | Electrum(args.electrum, args.proxy).broadcast(args.args[0])
26 | .then(txid => console.log(C.green('(success)'), 'transaction broadcast to the bcash network:', C.yellowBright(txid)))
27 | .catch(printErr)
28 |
--------------------------------------------------------------------------------
/cli/bcash-instadump.js:
--------------------------------------------------------------------------------
1 | #!/usr/bin/env node
2 | const
3 | C = require('chalk')
4 | , util = require('util')
5 | , inquirer = require('inquirer')
6 | , Electrum = require('../lib/electrum')
7 | , ShapeShift = require('../lib/shapeshift')
8 | , makeTx = require('../lib/make-tx')
9 | , {keysUtxo} = require('../lib/utxo')
10 |
11 | , { collector, parseInput, toSat, formatSat, initArgs, checkFee, printErr, info } = require('./common')
12 |
13 | const dummyOut = { address: '1BitcoinEaterAddressDontSendf59kuE', value: 'ALL' }
14 | , pair = 'BCH_BTC'
15 |
16 | const formatNum = (num, asStr) => asStr ? (+num).toFixed(8) : +(+num).toFixed(8)
17 | , formatDate = ts => new Date(ts).toLocaleString()
18 |
19 | const args = require('commander')
20 | .version(require('../package.json').version)
21 | .description(`${C.red('DUMP bcash')} 💩 ${C.green('HODL bitcoin')} 🚀:🌔`)
22 |
23 | .option('-i, --input ', 'add input in txid:vout:amount:key format (amount in whole bitcoins, key in base58)', collector(parseInput), [])
24 | .option('-I, --inputs ', 'read inputs from CSV file')
25 | .option('-k, --key ', 'load unspent outputs for and add them', collector(x => x), [])
26 | .option('-K, --keys ', 'read keys from file (one per line)')
27 | .option('-P, --payout ', 'bitcoin address for receiving the converted bitcoins (required)')
28 | .option('-r, --refund ', 'bcash address for refunds if anything goes wrong with the exchange [default: the address of the first key]')
29 | .option('-f, --feerate ', 'set the feerate in satoshis/byte [default: rand(50,100)]', x => parseInt(x))
30 |
31 | .option('-e, --electrum ', 'electrum server, must be bcash-compatible [default: random server]')
32 | .option('-p, --proxy ', 'proxy for connecting to electrum server and shapeshift')
33 | .option('-t, --tor', 'shortcut for --proxy socks5://127.0.0.1:9050')
34 | .option('-N, --noproxy', 'set if you\'re sure you don\'t want to use a proxy')
35 |
36 | .option('--crazyfee', 'disable the crazy fee sanity check (allow feerate>2000)')
37 | .option('--noreferral', 'don\'t use referrer code to tip the author of this software')
38 | .option('--whateverjustdump', 'skip all confirmations (for exchange rates, miner fees, etc) and just dump. this is probably a terrible idea.')
39 |
40 | .on('--help', _ => console.log('\n Example:\n\n $ bcash-instadump --input txid,vout,amount,key --payout 1BtcAddrGimmeRogersCoins'
41 | + '\n\n README:', C.underline('https://github.com/shesek/bcash-instadump'), '(really, do!)\n'))
42 |
43 | .parse(process.argv)
44 |
45 | initArgs(args)
46 | if (!(args.input.length || args.key.length) || !args.payout) args.help()
47 |
48 | if (args.key.length) info('loading unspent outputs for', C.yellowBright(args.key.length), 'keys')
49 |
50 | keysUtxo(args.key, args).then(inputs => args.input.concat(inputs)).then(inputs => {
51 | if (!inputs.length) return Promise.reject('no unspent outputs found for the provided key(s)')
52 |
53 | const shift = ShapeShift({ proxy: args.proxy, noreferral: args.noreferral })
54 | , txTmp = makeTx(inputs, [ dummyOut ], args.feerate) // @XXX builds and discards a dummy tx to estimate size/fee/amounts, somewhat wasteful
55 | , txVal = txTmp.getOutputValue()
56 | , refund = args.refund || txTmp.view.getCoin(txTmp.inputs[0]).getAddress().toString()
57 |
58 | info('fetching market info')
59 | return shift.marketinfo(pair)
60 | .then(market => (info('ShapeShift market info:', util.inspect(market, { colors: true }).replace(/\n /g,'')), market))
61 | .then(market => verifyLimits(market, formatSat(txVal)))
62 |
63 | .then(_ => info('creating order to dump', C.yellowBright(formatSat(txVal), 'BCH')))
64 | .then(_ => shift.openOrder(pair, formatSat(txVal), refund, args.payout))
65 | .then(order => makeVerifyTx(order, inputs, txVal)
66 | .then(tx => Electrum(args.electrum, args.proxy).broadcast(tx.toRaw().toString('hex')))
67 | .then(txid => printSuccess(order, txid)))
68 | }).catch(printErr)
69 |
70 | const verifyLimits = (market, amount) =>
71 | !market.minimum || !market.limit ? Promise.reject('missing market limits, probably a temporary ShapeShift issue. try again in a few minutes.')
72 | : toSat(amount) < toSat(''+market.minimum) ? Promise.reject('cannot sell '+amount+' BCH, minimum is '+market.minimum+' BCH')
73 | : toSat(amount) > toSat(''+market.limit) ? Promise.reject('cannot sell '+amount+' BCH, maximum is '+market.limit+' BCH')
74 | : info('within limits', C.yellowBright(market.minimum, '<=', amount, '<=', market.limit))
75 |
76 | const makeVerifyTx = (order, inputs, txVal) => {
77 | const tx = makeTx(inputs, [ { address: order.deposit, value: txVal } ])
78 | , btcs = order.withdrawalAmount
79 | , rateE = (toSat(btcs)/tx.getOutputValue()).toFixed(8)
80 | , rateF = (toSat(btcs)/tx.getInputValue()).toFixed(8)
81 |
82 | if (!args.crazyfee) checkFee(tx)
83 |
84 | console.log('\nShapeShift order', C.yellowBright(order.orderId)+':\n')
85 | console.log(' Payout address (BTC):', C.yellowBright(order.withdrawal))
86 | console.log(' Deposit address (BCH):', C.yellowBright(order.deposit))
87 | console.log(' Refund address (BCH):', C.yellowBright(order.returnAddress), C.yellow(!args.refund ? '(none provided, defaulted to the address of the first key)' : ''))
88 | console.log('\n Fixed fee:', C.yellowBright(order.minerFee, 'BTC'), C.yellow('(charged by ShapeShift)'))
89 | console.log('\n '+C.red(C.bold('DUMP'), formatSat(txVal), C.bold('BCH'))+',', C.green(C.bold('GET'), btcs, C.bold('BTC'))+'\n')
90 | console.log(' Quoted rate: 1 BCH =', C.yellowBright(order.quotedRate), 'BTC', C.yellow('(before ShapeShift\'s fixed fee and mining fees)'))
91 | console.log(' Actual rate: 1 BCH =', C.yellowBright(rateE), 'BTC', C.yellow('(including ShapeShift\'s fixed fee)'))
92 | console.log(' Total rate: 1 BCH =', C.yellowBright(rateF), 'BTC', C.yellow('(including your bcash miner fees, too)'))
93 | console.log('\n ' + C.cyan.underline(order.url), args.noproxy ? '' : '\n '+C.red('(warn)'), C.gray('don\'t forget your proxy when opening links in browser'))
94 | console.log('\n ' + C.underline('order expires'), 'in', C.yellowBright(Math.ceil((order.expiration-Date.now())/60000)), 'minutes'
95 | , '('+C.yellowBright(formatDate(order.expiration))+')')
96 |
97 | console.log('\nTransaction', C.yellowBright(tx.txid())+':\n')
98 | console.log(' Inputs:', C.yellowBright(formatSat(tx.getInputValue()), 'BCH'), 'from', C.yellowBright(tx.inputs.length+' outpoints')
99 | , C.yellow('('+tx.inputs.map(inv => [inv.prevout.txid().substr(0, 7), inv.prevout.index].join(':')).join(', ')+')'))
100 | console.log(' Output:', C.yellowBright(formatSat(tx.getOutputValue()), 'BCH'), 'to', C.yellowBright(tx.outputs[0].getAddress()), C.yellow('(ShapeShift\'s deposit address)'))
101 | console.log(' Tx size:', C.yellowBright(tx.getVirtualSize()+'b')+',', 'fee:', C.yellowBright(formatSat(tx.getFee()), 'BCH'), '(rate:', C.yellowBright(Math.round(tx.getRate(tx.view)/1000,2)), 'satoshis/byte)')
102 | if (tx.inputs.length > 1) console.log(' ', C.red('(warn)'), C.gray('merging multiple inputs together could harm your privacy. See README.md for more details.'))
103 |
104 | console.log('\nPlease make sure everything checks out. Once confirmed, this cannot be undone.')
105 | console.log('Press Y to confirm and dump or N to abort and print the bcash transaction without broadcasting it.\n')
106 |
107 | return confirm('DUMP bcash, HODL bitcoin?')
108 | .catch(_ => {
109 | console.log('\n'+C.red('(canceled)'), 'not sending transaction:\n')
110 | console.log(util.inspect(tx.inspect(), { depth: 5, colors: true })+'\n')
111 | console.log(C.yellow('(rawtx)'), tx.toRaw().toString('hex')+'\n')
112 | info('you can send this transaction manually using:\n $ bcash-broadcast \n')
113 | return Promise.reject('user aborted')
114 | })
115 | .then(_ => !nearExpiry(order) ? tx : Promise.reject('ShapeShift order expired, aborting transaction. be quicker next time!'))
116 | }
117 |
118 | const confirm = message => args.whateverjustdump
119 | ? (console.log(C.green('?'), C.bold(message), C.gray('--whateverjustdump, skipping')), Promise.resolve(true))
120 | : inquirer.prompt([ { name: 'ok', type: 'confirm', message, default: false } ])
121 | .then(r => r.ok || Promise.reject('user aborted'))
122 |
123 | const nearExpiry = order => Date.now() > order.expiration - 60000 // safety margin of 1 minute
124 |
125 | const printSuccess = (order, txid) => {
126 | console.log('\n'+C.green.bold('(success)'), 'bcash dumped in tx', C.yellowBright(txid)+'\n')
127 | console.log(' Order status:', C.cyan.underline(order.url))
128 | console.log(' Transaction: ', C.cyan.underline(txUrl(txid)))
129 | args.noproxy || console.log(' ' + C.red('(warn)'), C.gray('don\'t forget your proxy when opening links in browser'))
130 | console.log('\n '+C.yellowBright(order.withdrawalAmount, 'BTC'), 'are coming your way (after 3 bcash confirmations).', C.bold('HODL strong!')+'\n')
131 | console.log('Make sure to keep a copy of the order and transaction details for future reference.\n')
132 | }
133 | const txUrl = txid => 'https://blockchair.com/bitcoin-cash/transaction/' + txid
134 |
--------------------------------------------------------------------------------
/cli/bcash-tx.js:
--------------------------------------------------------------------------------
1 | #!/usr/bin/env node
2 |
3 | const
4 | C = require('chalk')
5 | , util = require('util')
6 | , Electrum = require('../lib/electrum')
7 | , makeTx = require('../lib/make-tx')
8 | , {keysUtxo} = require('../lib/utxo')
9 |
10 | , { parseInput, parseOutput, collector, initArgs, checkFee, printErr, info } = require('./common')
11 |
12 | const args = require('commander')
13 | .version(require('../package.json').version)
14 | .description('Create and sign a bcash-compatible transaction with the provided inputs and outputs.\n The transaction will be invalid on the Bitcoin network.')
15 |
16 | .option('-i, --input ', 'add input in txid:vout:amount:key) format (amount in whole bitcoins, key in base58)', collector(parseInput), [])
17 | .option('-I, --inputs ', 'read inputs from CSV file')
18 | .option('-k, --key ', 'load unspent outputs for and add them', collector(x => x), [])
19 | .option('-K, --keys ', 'read keys from file (one per line)')
20 | .option('-o, --output