(PDF) Bitcoin Transaction Malleability and MtGox

I Finally sold to Fortress, here is how and why

After receiving an email from Fortress with their new offer (1300$/GoxCoin), I decided to sell my claim:
Reasons of selling:
submitted by rirofriro88 to mtgoxinsolvency [link] [comments]

Founder of Bitcoin Builder, Josh Jones, and one of mtgox's largest creditors just lost $37 million in a sim hack.

In a now deleted post the user zhoujianfu pleads for help from miners/community after 59471 BCH (~$22 million) and 1547 BTC (~$15 million) vanished from his wallets.
To confirm the legitimacy of the address in question (1Edu4yBtfAKwGGsQSa45euTSAG6A2Zbone) from which the total sum of $37 million in crypto currency was stolen, he signed the address:
Text:
zhoujianfu owns me.
Signature:
HKo7vjjvoCbRZPx39rtf1dSjEmA8qigIR4+F85BGCpbpHzmdq1vm6D8bQ9KA6RzFrKdihT/QoOfENDzNPQzL85k=
I have verified the signature as valid. The post which confirms that zhoujianfu is indeed Josh Jones can be found here. According to the deleted post, this was a "sim hack". Which wallet service was used or how Josh was able to retrieve the private keys to sign that message remains unknown, however there has been speculation that he has used blockchain.info or blockchain.com.
This shouldn't have any impact on his claim with mtgox or his creditors in bitcoin builder, but it seems relevant here nonetheless.
submitted by warz to mtgoxinsolvency [link] [comments]

Did anyone else get very long email with the subject "【MTGOX】同意事項/Terms of Consent" today?

This was the full email. There were also 2 PDF attachments. The only part I have changed is where I've redacted my "creditor number". Please discuss what you think about it.
(English follows Japanese)
債権者様(債権者番号:XXXXXXXXXXX)
本メールは、株式会社MTGOX(以下「MTGOX」といいます。)の破産手続において破産債権の届出をしたものの、MTGOXの民事再生手続(以下「本民事再生手続」といいます。)において、再生債権の届出をしておらず、MTGOXのデータベースに存在した残高が自認債権として認められた債権者の方にお送りしています。
貴殿/貴社について認められた自認債権については、添付PDFファイルに記載しておりますのでご確認ください。
本民事再生手続において、届出債権者の方には、弁済を含めた諸手続を円滑に進めるため、本民事再生手続に関する同意事項に同意いただいております。しかし、貴殿/貴社は債権届出をしていないことから、未だ当該同意事項へ同意いただいておりません。弁済を含めた今後の手続を円滑に進めるためには、貴殿/貴社にも同様の同意事項に対して同意していただく必要があります。
そこで、本メールの末尾に記載しました「民事再生手続に関する同意事項」又は本メールに添付しました「民事再生手続に関する同意事項」(内容は同一です。)をご確認いただき、内容に同意いただける場合には、下記の文言を記載して、本メールに直接返信してください。
「私は、MTGOXの民事再生手続について、再生管財人から送付された「民事再生手続に関する同意事項」について同意及び表明いたします。」
再生管財人は、今後も、東京地方裁判所と協議しながら、適切な民事再生手続の遂行に努めてまいりますので、ご理解ご協力の程宜しくお願い申し上げます。
再生債務者株式会社MTGOX 再生管財人弁護士小林信明
To creditor (creditor number: XXXXXXXXXXX)
You have received this email because you are a creditor ofMtGox Co., Ltd. (“MtGox”) who filed a proof of bankruptcy claim(s) under the previous bankruptcy proceedings forMtGox but did not file a proof of rehabilitation claim(s) under the civil rehabilitation proceedings for MtGox (the “Civil Rehabilitation Proceedings”) and whose remaining balance on the MtGox database was approved by the Rehabilitation Trustee as a self-approved rehabilitation claim(s) (i.e., a rehabilitation claim that was not filed but accepted by the trustee voluntarily in accordance with the Civil Rehabilitation Act).
Your self-approved rehabilitation claim(s) are detailed in the attached PDF file for your review.
In the Civil Rehabilitation Proceeding, the rehabilitation creditors who filed their proofs of rehabilitation claim agreed to the terms of consent regarding the Civil Rehabilitation Proceedings to proceed smoothly with various procedures including repayment. However, since you have not filed a claim, you have not yet agreed to these terms of consent. In order to facilitate various proceedings, your consent to the terms is required.
Accordingly, we hereby stated the “Terms of Consent Regarding the Civil Rehabilitation Proceedings” at the end of this email, as well as attached the same to this email. Please carefully read the terms therein, and if you agree to the terms, please reply to this email and state the sentence below in the body of your reply.
“I/We hereby agree to and represent as set forth in the “Terms of Consent Regarding the Civil Rehabilitation Proceedings” sent by the rehabilitation trustee, in relation to the civil rehabilitation proceedings for MtGox Co., Ltd.”
The rehabilitation trustee will continue to make an effort to conduct the Civil Rehabilitation Proceeding appropriately and in consultation with the Tokyo District Court, and the rehabilitation trustee would appreciate the understanding and cooperation of all concerned parties.
Rehabilitation Debtor: MtGox Co., Ltd. Rehabilitation Trustee: Nobuaki Kobayashi, Attorney-at-law
事件番号 平成29年(再)第35号 / Case Number 2017 (sai) No. 35 再生債務者 株式会社MTGOX / Rehabilitation Debtor: MTGOX Co., Ltd.
民事再生手続に関する同意事項 Terms of Consent Regarding the Civil Rehabilitation Proceedings
1. 私/当社は、上記債権者番号の自認債権者本人であり、私/当社が届け出た情報は真実、正確かつ完全であること。その違反に起因又は関連して生じるあらゆる損害、損失、債務、コスト又は費用(以下「損害等」という。)について、株式会社MTGOX(以下「MTGOX」という。)及びMTGOXの民事再生手続(東京地方裁判所平成29年(再)第35号。以下「本民事再生手続」という。)における管財人(その代理及び補佐を含み、以下「再生管財人」という。)は一切の責任を負わず、私/当社はMTGOX及び再生管財人に対して当該損害等に関して損害賠償請求、補償請求その他一切の請求をしないこと。 I am/We are the creditor of self-approved rehabilitation claims that has the above creditor number, and I/we represent that the information that I/we have provided therein is true, accurate, and complete. MtGox Co., Ltd. (“MTGOX”) and the trustee (including deputy trustees and assistant trustees; the “Rehabilitation Trustee”) of the MTGOX civil rehabilitation proceedings (Tokyo District Court; 2017 (sai) Case No. 35; the “Civil Rehabilitation Proceedings”) are not liable in any respect for any damage, loss, liability, cost or expense (“Damages”) arising out of or in connection with any breach of such representation, and I/we will not make any claim for damages or compensation, or make any other claim with respect to such Damages against MTGOX or the Rehabilitation Trustee.
2. 再生管財人の故意によらず、ビットコイン及びビットコインから分岐した他の仮想通貨(以下「フォークコイン」といい、ビットコインと総称して「ビットコイン等」という。)の技術上の問題・障害等に起因又は関連して生じるあらゆる損害等(ビットコイン等又は金銭による弁済を受領できないことによる損害を含むが、これに限られない。)について、MTGOX及び再生管財人は一切の責任を負わず、私/当社はMTGOX及び再生管財人に対して当該損害等に関して損害賠償請求、補償請求その他一切の請求をしないこと。 MTGOX and the Rehabilitation Trustee are not liable in any respect for any Damages arising out of or in connection with any technical issue, impediment, or other ground, in the absence of without willful misconduct by the Rehabilitation Trustee, regarding Bitcoin or any other cryptocurrency split from Bitcoin (a “Fork Coin”; collectively with Bitcoin, “Bitcoin, Etc.”) (including, but not limited to, any damage related to payments in Bitcoin, Etc. or cash not being received), and I/we will not make any claim for damages or compensation, or make any other claim with respect to such Damages against MTGOX or the Rehabilitation Trustee.
3. 私/当社は、本書式のダウンロードその他のために必要なコンピュータ等の機器、ソフトウェアその他のアプリケーション、通信回線その他の通信環境等の準備(必要なアプリケーションのインストールを含む。)及び維持、並びに自らの利用環境に応じたコンピュータ・ウイルスの感染の防止、不正アクセス及び情報漏洩の防止等のセキュリティ対策を、自らの費用と責任において行うこと。本項に定める事項の違反に起因又は関連して生じるあらゆる損害等について、MTGOX及び再生管財人は一切の責任を負わず、私/当社はMTGOX及び再生管財人に対して当該損害等に関して損害賠償請求、補償請求その他一切の請求をしないこと。私/当社は、MTGOX及び再生管財人が利用環境を推奨した場合であっても動作保証は行わないことを認識し、これに同意していること。 I/We will, at my/our expense and responsibility, setup and maintain computers and other equipment, software and other applications, telecommunication lines and other telecommunication environments, among others, necessary to download this form (including installing necessary applications) and, in accordance with my/our use environment, take security measures, such as preventing infection by computer viruses, unauthorized access and information divulgence. MTGOX and the Rehabilitation Trustee are not liable in any respect for any Damages arising out of or in connection with any breach of any matter stipulated in this paragraph, and I/we will not make any claim for damages or compensation, or make any other claim with respect to such Damages against MTGOX or the Rehabilitation Trustee. I/We acknowledge and agree that notwithstanding that MTGOX and the Rehabilitation Trustee have recommended a use environment its operation is not guaranteed in any respect.
4. 私/当社は、自らの責任において、MTGOXのビットコイン取引所に登録していたユーザーネーム、メールアドレス及びパスワード、MTGOXの破産手続(東京地方裁判所平成26年(フ)第3830号。以下「本破産手続」という。)において債権者情報として登録した連絡先メールアドレス等私/当社であることの確認のために必要な情報及びこれに関連するもの(以下、総称して「パスワード等」という。)を管理、保管するものとし、パスワード等を第三者に利用させたり、貸与、譲渡、名義変更、売買その他処分をしたりしないこと。再生管財人は、私/当社のパスワード等により行われた一切の行為を、私/当社の行為とみなすことができ、パスワード等の管理不十分、使用上の過誤、漏洩、第三者の使用、盗用等に起因又は関連して生じるあらゆる損害等について、MTGOX及び再生管財人は一切の責任を負わず、私/当社はMTGOX及び再生管財人に対して当該損害等に関して損害賠償請求、補償請求その他一切の請求をしないこと。 I/We will, at my/our responsibility, manage and store user names, email address and passwords registered on the MTGOX Bitcoin exchange; the contact address registered as creditor information in the bankruptcy proceedings (Tokyo District Court; 2014 (fu) Case No. 3830; the “Bankruptcy Proceedings”); or any other information necessary for identity confirmation and anything related thereto (collectively, the “Passwords”) and will neither permit any third party to use the Passwords nor lend, assign, transfer ownership, trade, or handle the Passwords in any other manner. The Rehabilitation Trustee may deem all acts conducted with my/our Passwords as mine/our act; and MTGOX and the Rehabilitation Trustee are not liable in any respect for any Damages arising out of or in connection with insufficient management, erroneous use, divulgence, third party use, illegal use, or otherwise of the Passwords, and I/we will not make any claim for damages or compensation, or make any other claim with respect to such Damages against MTGOX or the Rehabilitation Trustee.
5. 私/当社は、再生管財人が定めている又は今後定める、再生管財人が用意した方式・方法による届出・通知及びこれに関連する事項を行う際のルール(今後の変更を含む。)を理解した上でこれに従うものとし、当該ルールに違反し、又は違反しようとしたことに起因又は関連して生じるあらゆる損害等について、MTGOX及び再生管財人は一切の責任を負わず、私/当社はMTGOX及び再生管財人に対して当該損害等に関して損害賠償請求、補償請求その他一切の請求をしないこと。 I/We will familiarize myself/ourselves with and follow current rules or future rules (as amended from time to time) for any filing/notifying with the form/method the Rehabilitation Trustee provided and anything related thereto stipulated, by the Rehabilitation Trustee; and MTGOX and the Rehabilitation Trustee are not liable in any respect for any Damages arising out of or in connection with any breach of or any attempted breach of the rules, and I/we will not make any claim for damages or compensation, or make any other claim with respect to such Damages against MTGOX or the Rehabilitation Trustee.
6. 他のウェブサイトからMTGOXのウェブサイトへのリンクが提供されている場合においても、MTGOXのウェブサイト以外のウェブサイト及びそこから得られる情報並びにそれに起因又は関連して生じる損害等について、MTGOX及び再生管財人は一切の責任を負わず、私/当社はMTGOX及び再生管財人に対して当該損害等に関して損害賠償請求、補償請求その他一切の請求をしないこと。 MTGOX and the Rehabilitation Trustee are not liable in any respect for any website other than MTGOX’s website, any information obtained therefrom, and any Damages arising out of or in connection with the same, notwithstanding that MTGOX’s website may be linked on another website, and I/we will not make any claim for damages or compensation, or make any other claim with respect to such Damages against MTGOX or the Rehabilitation Trustee.
7. 私/当社と他の再生債権者その他の者との間において生じた取引、連絡、紛争等については、私/当社の責任において処理及び解決するものとし、かかる事項及びそれに起因又は関連して生じるあらゆる損害等について、MTGOX及び再生管財人は一切の責任を負わず、私/当社はMTGOX及び再生管財人に対して当該損害等に関して損害賠償請求、補償請求その他一切の請求をしないこと。 I/we will, at my/our responsibility, handle and resolve any and all transactions, communication, disputes, among others, arising between me/us, another rehabilitation creditor, or any other person; and MTGOX and the Rehabilitation Trustee are not liable in any respect for any relevant matter and any Damages arising out thereof or in connection therewith, and I/we will not make any claim for damages or compensation, or make any other claim with respect to such Damages against MTGOX or the Rehabilitation Trustee.
8. 法律、政令、法令、命令、通達、条例、ガイドラインその他の規制(以下「法令等」という。)又は消費税を含む税制の将来の制定又は変更に起因又は関連して生じるあらゆる損害等について、MTGOX及び再生管財人は一切の責任を負わず、私/当社は、MTGOX及び再生管財人に対して当該損害等に関して損害賠償請求、補償請求その他一切の請求をしないこと。また、法令等又は消費税を含む税制の将来の制定又は変更が過去に遡及した場合に、これに起因又は関連して生じるあらゆる損害等について、MTGOX及び再生管財人は一切の責任を負わず、私/当社はMTGOX及び再生管財人に対して当該損害等に関して損害賠償請求、補償請求その他一切の請求をしないこと。 MTGOX and the Rehabilitation Trustee are not liable in any respect for any Damages arising out of or in connection with a future enactment or amendment to a law, cabinet order, ordinance, order, directive, bylaw, guideline, or any other regulation (“Laws”) or the tax system, including consumption tax; and I/we will not make any claim for damages or compensation, or make any other claim with respect to such Damages against MTGOX or the Rehabilitation Trustee. Further, MTGOX and the Rehabilitation Trustee are not liable in any respect for any Damages arising out of or in connection with any future enactment or amendment with a retroactive effect on Laws or the tax system including consumption tax, and I/we will not make any claim for damages or compensation, or make any other claim with respect to such Damages against MTGOX or the Rehabilitation Trustee.
9. 裁判所又は再生管財人が、再生管財人が私/当社のメールアドレスと認めるメールアドレス宛に電子メールにより通知を送信することによって、私/当社に対する適法な通知があったものとみなすこと。当該メールアドレスの不備等(メールアドレスの記載漏れを含む。)に起因又は関連して、当該メールアドレスに宛てた電子メールを送信することができず又は電子メールが到達しない場合(到達が確認できない場合を含む。)であっても同様とすること。 An appropriate notification is deemed to have been made to me/us if the court or the Rehabilitation Trustee sends a notification via email to the email address which is considered to be my/our email address by the Rehabilitation Trustee. The same applies notwithstanding that, due to, or in connection with, an inadequacy, inaccurateness or incompleteness, or any other issue (including omission of the email address), in or with that email address, an email addressed to that email address cannot be sent or the email is not delivered including where receipt is unconfirmed.
10.私/当社が本届出書を利用して行った再生債権の届出の内容について、再生管財人が裁判所その他必要な第三者に提出すること。 The Rehabilitation Trustee may submit the proof of rehabilitation claim filed by me/us using this form to the court and other third parties as necessary.
11.私/当社は、本民事再生手続においてパスワード等を用いて入手することができる一切の情報(他の再生債権者に関する情報を含むが、これに限られない。)を、本民事再生手続における権利行使の目的にのみ使用することとし、第三者に提供、開示又は漏洩しないこと。 I/We will use information (including, but not limited to, information related to any other rehabilitation creditors) acquired by using the Passwords in the Civil Rehabilitation Proceedings only for the purpose of exercising rights in the Civil Rehabilitation Proceedings and will not provide, disclose, or divulge such information to any third party.
12.私/当社の本民事再生手続における議決権の額は、再生管財人が提示する次の為替レートによって、円換算されて評価されること。 The amount of my/our voting rights in the Civil Rehabilitation Proceedings is computed through conversion to Japanese Yen (JPY) using the following exchange rates provided by the Rehabilitation Trustee:
(a) 外国通貨 平成30年6月21日(日本時間)の東京外国為替市場・電信為替売相場として三菱UFJリサーチ&コンサルティング株式会社が公表した相場 Foreign currency: the exchange rates publicly announced by Mitsubishi UFJ Research and Consulting Co., Ltd. as the Tokyo Foreign Exchange Market / Telegraphic Transfer Selling Rate on June 21, 2018 (Japan Time) (b) ビットコイン 平成30年6月21日23時59分(日本時間)時点のCoinDeskが発表する米国ドル建てのビットコイン相場を(a)の相場により日本円に換算した金額(1 BTC=6,724.57米国ドル=749,318.83円。1米国ドル=111.43円) Bitcoin: the amount obtained by converting the Bitcoin price denominated in USD announced by CoinDesk at 23:59 on June 21, 2018 (Japan Time) to JPY using the exchange rate referred to in the above (a). (1 BTC=6,724.57 USD = 749,318.83 JPY; 1 USD = 111.43 JPY) (c) ビットコインキャッシュ 平成30年6月21日23時59分(日本時間)時点のCoinDeskが発表する米国ドル建てのビットコインキャッシュ相場を(a)の相場により日本円に換算した金額(1 BCH=874.82米国ドル=97,481.19円。1米国ドル=111.43円) Bitcoin Cash: the amount obtained by converting the Bitcoin Cash Price denominated in USD announced by CoinDesk at 23:59 on June 21, 2018 (Japan time) to JPY using the exchange rate referred to in the above (a). (1 BCH = 874.82 USD = 97,481.19 JPY; 1 USD = 111.43 JPY) (d) その他の仮想通貨 金額は未定 Amounts for other cryptocurrencies: not determined
13.本民事再生手続においては、ビットコイン等の返還請求権は非金銭債権として取り扱われ、当該返還請求権に係る遅延損害金は生じないこととすること。 In the Civil Rehabilitation Proceedings, the right to claim for return of Bitcoin Etc. is treated as a non-monetary claim, and no delay damages pertaining to such right to claim for return will accrue.
14.再生管財人の私/当社への弁済(金銭及びビットコイン等の弁済を含む。)及びこれに関連する行為が、日本国の外国為替及び外国貿易法、米国財務省の金融制裁(OFAC規制)その他私/当社に関して適用のあるいかなる法令等にも抵触しないこと。再生管財人は、再生管財人の実施する私/当社への弁済及びこれに関連する行為が、日本国外の法令等に抵触しないことをいかなる意味においても保証しないこと。これらの法令等への抵触に起因又は関連して生じるあらゆる損害等について、MTGOX及び再生管財人は一切の責任を負わず、私/当社はMTGOX及び再生管財人に対して当該損害等に関して損害賠償請求、補償請求その他一切の請求をしないこと。再生管財人の私/当社への弁済に起因又は関連して私/当社に課される一切の公租公課(当該弁済の態様によって公租公課の額が増減する場合を含む。)は、私/当社が負担し、当該公租公課又はその増減に起因又は関連して生じるあらゆる損害等について、MTGOX及び再生管財人は一切の責任を負わず、私/当社はMTGOX及び再生管財人に対して当該損害等に関して損害賠償請求、補償請求その他一切の請求をしないこと。 Any payment (including payment of cash and Bitcoin Etc.) to me/us by the Rehabilitation Trustee and any act related thereto do not conflict with the Foreign Exchange and Foreign Trade Act of Japan, the United States Department of the Treasury’s financial sanctions (OFAC regulations) and any other applicable Laws. The Rehabilitation Trustee does not guarantee, in any respect, that payment to me/us by the Rehabilitation Trustee and any act related thereto do not conflict with Laws outside of Japan. MTGOX and the Rehabilitation Trustee are not liable in any respect for any Damages arising out of or in connection with any conflict with any applicable Laws, and I/we will not make any claim for damages or compensation, or make any other claim with respect to such Damages against MTGOX or the Rehabilitation Trustee. I/We will bear all taxes and other public charges (including any increases or decreases in the amount of taxes and other public charges due to the manner of the payment) levied on me/us arising out of or in connection with any payment to me/us by the Rehabilitation Trustee; and MTGOX and the Rehabilitation Trustee are not liable in any respect for any Damages arising out of or in connection with such taxes and other public charges and increase or decrease thereof, and I/we will not make any claim for damages or compensation, or make any other claim with respect to such Damages against MTGOX or the Rehabilitation Trustee.
15.再生管財人が、仮想通貨取引所(日本国内の仮想通貨交換業者を含むが、これに限られない。以下同じ。)又は金融機関(資金移動業者を含む。以下同じ。)に開設された再生債権者の口座に対して弁済金を振り込む場合、私/当社は、再生管財人の指定する方法により届け出た氏名・名称と同一名義の仮想通貨取引所又は金融機関の口座で受け取ること。 If the Rehabilitation Trustee transfers the money for distribution to an account of a rehabilitation creditor opened at a cryptocurrency exchange (including, but not limited to, cryptocurrency exchangers in Japan; the same applies below) or a financial institution (including fund transfer operators; the same applies below), I/we will receive the same in the account at the cryptocurrency exchange or the financial institution under the same name as that name I/we notified in the manner designated by the Rehabilitation Trustee.
16.私/当社が再生管財人の指定する仮想通貨取引所に開設した口座でビットコイン等及び/又は金銭で弁済を受ける場合には、次の各事項。 If I/we receive payment in Bitcoin Etc. and/or in cash in an account opened at the cryptocurrency exchange designated by the Rehabilitation Trustee, the following applies:
(a) 私/当社は、送付先等の必要情報を正確に提供しなければならず、その誤りから結果的にビットコイン等及び/又は金銭を受領できなかったとしても、それに起因又は関連して生じるあらゆる損害等について、MTGOX及び再生管財人は一切の責任を負わず、私/当社はMTGOX及び再生管財人に対して当該損害等に関して損害賠償請求、補償請求その他一切の請求をしないこと。 I/we must accurately provide necessary information about my/our accounts, among others, and, notwithstanding that an error therein results in my/our not receiving Bitcoin, Etc. or cash, MTGOX and the Rehabilitation Trustee are not liable in any respect for any Damages arising out of or in connection with such non-receipt, and I/we will not make any claim for damages or compensation, or make any other claim with respect to such Damages against MTGOX or the Rehabilitation Trustee.
(b) 再生管財人がビットコイン等及び/又は金銭を当該仮想通貨取引所に交付した時点で弁済が完了し、MTGOX及び再生管財人の弁済義務は消滅するものとし、再生管財人による当該仮想通貨取引所へのビットコイン等及び/又は金銭の交付後、私/当社が何らかの理由(仮想通貨のブロックチェーンの不具合、仮想通貨取引所のシステムの不具合を含むが、これらに限られない。)により仮想通貨取引所からのビットコイン等及び/又は金銭の適切な弁済を受けることができなかったとしても、それに起因又は関連して生じるあらゆる損害等について、MTGOX及び再生管財人は一切の責任を負わず、私/当社はMTGOX及び再生管財人に対して当該損害等に関して損害賠償請求、補償請求その他一切の請求をしないこと。 The instant the Rehabilitation Trustee sends Bitcoin, Etc. or cash to the cryptocurrency exchange, the payment by MTGOX and the Rehabilitation Trustee is deemed complete, and the payment obligation of MTGOX and the Rehabilitation Trustee is deemed to be discharged; and, after Bitcoin Etc. or cash has been sent to the cryptocurrency exchange by the Rehabilitation Trustee, notwithstanding that I/we fail to receive appropriate payment of Bitcoin Etc. or cash from the cryptocurrency exchange for any reason (including, but not limited to, a malfunction in the blockchain of the cryptocurrency or a system malfunction at the cryptocurrency exchange), MTGOX and the Rehabilitation Trustee are not liable in any respect for any Damages arising out of or in connection with such failure, and I/we will not make any claim for damages or compensation, or make any other claim with respect to such Damages against MTGOX or the Rehabilitation Trustee.
17.私/当社が金融機関の口座において金銭で弁済を受ける場合には、次の各事項。 If I/we receive cash in an account at a financial institution, the following applies:
(a) 私/当社は、送付先等の必要情報を正確に提供しなければならず、その誤りから結果的に金銭を受領できなかったとしても、それに起因又は関連して生じるあらゆる損害等について、MTGOX及び再生管財人は一切の責任を負わず、私/当社はMTGOX及び再生管財人に対して当該損害等に関して損害賠償請求、補償請求その他一切の請求をしないこと。 I/We must accurately provide necessary information about my/our accounts, among others, and, notwithstanding that an error therein results in my/our not receiving cash, MTGOX and the Rehabilitation Trustee are not liable in any respect for any Damages arising out of or in connection with that, and I/we will not make any claim for damages or compensation, or make any other claim with respect to such Damages against MTGOX or the Rehabilitation Trustee.
(b) 取扱通貨の種別や送金元銀行との取引の有無、日本国内外の法令等及び各金融機関の内部基準への抵触並びに諸手数料の発生その他要因に基づき弁済金を受領できなかったとしても、それに起因又は関連して生じるあらゆる損害等について、MTGOX及び再生管財人は一切の責任を負わず、私/当社はMTGOX及び再生管財人に対して当該損害等に関して損害賠償請求、補償請求その他一切の請求をしないこと。 Notwithstanding that I/we fail to receive cash for distribution due to unavailability of the designated currencies or transactions with the designated financial institutions, any conflict with Laws in or outside Japan or an internal standard of any relevant financial institution, various processing charges and fees, or any other causes, MTGOX and the Rehabilitation Trustee are not liable in any respect for any Damages arising out of or in connection with that, and I/we will not make any claim for damages or compensation, or make any other claim with respect to such Damages against MTGOX or the Rehabilitation Trustee.
(c) 諸手数料等を差し引いた金額の弁済金を受け取る場合であっても、当該諸手数料等に起因又は関連して生じるあらゆる損害等について、MTGOX及び再生管財人は一切の責任を負わず、私/当社はMTGOX及び再生管財人に対して当該損害等に関して損害賠償請求、補償請求その他一切の請求をしないこと。 Notwithstanding that I/we have received payment from which various processing charges and fees have been deducted, MTGOX and the Rehabilitation Trustee are not liable in any respect for any Damages arising out of or in connection with such processing charges and fees, and I/we will not make any claim for damages or compensation, or make any other claim with respect to such Damages against MTGOX or the Rehabilitation Trustee.
18.フォークコインに係る再生債権の届出については、ビットコインに関する再生債権の届出をもって、届け出たビットコインの数に応じて、フォークコインに係る再生債権についても届け出たものとみなし、再生債権者は独自にフォークコインに係る再生債権を届け出ないこと。再生債権の届出があるとみなされるフォークコインは、通常の方法により売却可能であり、かつ、財産的価値のあるものに限られ、それ以外のフォークコインについては、再生債権の届出があるとは認められないこと。なお、ビットコインキャッシュは再生債権の届出があるとみなされるフォークコインに含まれること。 The filing of a proof of rehabilitation claim for a Fork Coin is deemed to have been made in proportion to the number of the filed Bitcoin for which the proof of rehabilitation claim has been filed, and the rehabilitation creditor cannot file its own proof of rehabilitation claim for a Fork Coin. Fork Coins that are deemed to have been filed are limited to those that can be sold in an ordinary manner and that have property value, and no other Fork Coin will be recognized as being deemed to have been filed. Bitcoin Cash is included in Fork Coins that are deemed to have been filed.
19.私/当社が再生管財人により認められた債権を契約により第三者に譲渡する場合には、当該譲渡契約の準拠法は日本法にするものとし、MTGOX及び再生管財人に当該譲渡を対抗するためには、日本法に基づく債権譲渡の対抗要件その他再生管財人が指定する要件を備えることが必要であること。再生管財人は、各国の法令等の定め及び債権譲渡契約で定められた準拠法の定めにかかわらず、日本法のみに基づき債権譲渡契約の有効性及び対抗要件具備の有無を判断すること。再生管財人が日本法に基づき債権譲渡契約の有効性及び対抗要件具備の有無を判断することに起因又は関連して生じるあらゆる損害等について、MTGOX及び再生管財人は一切の責任を負わず、私/当社はMTGOX及び再生管財人に対して当該損害等に関して損害賠償請求、補償請求その他一切の請求をしないこと。 If I/we intend to transfer or assign any rehabilitation claim that was approved by the Rehabilitation Trustee to any third party pursuant to an agreement, the governing law for such agreement shall be Japanese law, and the perfection requirements in accordance with the relevant Japanese law and any other requirements specified by the Rehabilitation Trustee shall be fully satisfied to perfect such claim transfer or assignment against MTGOX and the Rehabilitation Trustee. The Rehabilitation Trustee will determine the validity of such claim transfer or assignment and perfection thereof pursuant only to Japanese law, irrespective of any statute in each country’s Laws and any governing law provided for in such agreement. MTGOX and the Rehabilitation Trustee are not liable in any respect for any Damages arising out of or in connection with the Rehabilitation Trustee determining the validity of such claim transfer or assignment and perfection thereof pursuant to Japanese law, and I/we will not make any claim for damages or compensation, or make any other claim with respect to such Damages against MTGOX or the Rehabilitation Trustee.
20.再生管財人による債権譲渡の承認が、債権譲渡の承認に必要な手続(譲渡人及び譲受人の本人確認、譲渡を証明する文書の検証を含むが、これらに限られない。)その他の理由により遅滞した場合であっても、これに起因又は関連して生じるあらゆる損害等について、MTGOX及び再生管財人は一切の責任を負わず、私/当社はMTGOX及び再生管財人に対して当該損害等に関して損害賠償請求、補償請求その他一切の請求をしないこと。 Notwithstanding that approval by the Rehabilitation Trustee of a claim transfer or assignment is delayed by the procedures necessary for approval of a claim transfer or assignment (including, but not limited to, identity check of the transferoassignor and transferee/assignee and verification of documents proving transfer or assignment) or any other reason, MTGOX and the Rehabilitation Trustee are not liable in any respect for any Damages arising out of or in connection with such delay, and I/we will not make any claim for damages or compensation, or make any other claim with respect to such Damages against MTGOX or the Rehabilitation Trustee.
21.ある再生債権を譲渡する場合、当該再生債権の全部を譲渡することとし、その一部のみを譲渡しないこと。 If a rehabilitation claim is transferred or assigned, all of such rehabilitation claim, not part thereof, shall be transferred or assigned.
22.ビットコイン等に係る再生債権を譲渡する場合には、対象となるビットコイン及び当該ビットコインから分岐したフォークコインを併せて譲渡するものとし、ビットコイン又はフォークコインに係る再生債権を個別に譲渡しないこと。 If a rehabilitation claim pertaining to Bitcoin, Etc. is transferred or assigned, the Bitcoin subject to such transfer or assignment and the Fork Coin split from such Bitcoin shall be transferred or assigned collectively, and a rehabilitation claim pertaining to Bitcoin or Fork Coin shall not be transferred or assigned individually.
23.情報の取扱いに関する同意事項 Matters of consent related to information management
(a) 再生管財人が、以下の情報(個人情報の保護に関する法律(平成15年法律第57号)第2条第1項により定義される個人情報その他識別された又は識別可能な自然人に関する一切の情報を含むが、これに限られない。以下同じ。)を収集すること。 The Rehabilitation Trustee may collect the information below (including, but not limited to, personal information defined under Article 2(1) of the Act on the Protection of Personal Information (Act No. 57 of 2003) and any other information relating to an identified or identifiable natural person; the same applies below)
i. 私/当社が再生管財人に提供する情報 information that I/we provided to the Rehabilitation Trustee;
ii. 私/当社以外の情報源(身元証明サービス機関を含むが、これに限られない。)から収集する私/当社の情報 information concerning me/us provided by an information source (including, but not limited to, organizations providing ID verification services) other than myself/ourselves;
iii. 本破産手続において、私/当社が本破産手続の破産管財人に提供した一切の情報 all information that I/we provided to the bankruptcy trustee of the Bankruptcy Proceedings;
iv. 私/当社が、MTGOXに提供した一切の情報 all information that I/we provided to MTGOX; and
v. その他再生管財人が適正な方法により取得し、又は今後取得する情報 any other information acquired, or to be acquired going forward, by the Rehabilitation Trustee using an appropriate method
(b) 再生管財人が、収集した上記(a)の情報を、以下の目的で日本国内外で管理及び利用すること。 The Rehabilitation Trustee may manage and use collected information stated in (a) above for the purposes below in and outside of Japan.
i. 再生債権の届出、調査、再生計画の立案、再生計画に基づく弁済その他の本民事再生手続の適切な遂行 filing proofs of rehabilitation claim, investigations of rehabilitation claims, drafting a rehabilitation plan, distribution in accordance with a rehabilitation plan, or any other appropriate execution of the Civil Rehabilitation Proceedings;
ii. 公益的な目的のためにする、日本国内外の行政官庁・捜査機関・司法機関への上記(a)の情報の開示又は提供 disclosing or providing information stated in (a) above to any government office, any investigation agency, or any judicial agency in or outside of Japan for the purpose of serving public interests; and
iii. その他上記目的に付随する目的 any other purposes incidental to the above purposes.
(c) 再生管財人が、上記(b)の目的のため、上記(a)の情報を、第三者(以下の者を含むが、これらに限られない。)に開示又は提供する場合があること。これらの第三者には、①米国、②カナダ、③イギリス、④私/当社が所在する国及び⑤私/当社が再生債権の弁済の受領のために利用する金融機関又は仮想通貨取引所が所在する国に、それぞれ所在する第三者が含まれること。 The Rehabilitation Trustee may disclose or provide information stated in (a) above for the purpose of (b) above to any third party (including, but not limited to, the persons below). The third parties hereunder include third parties located in (i) the United States of America, (ii) Canada, (iii) the United Kingdom, (iv) the country in which I am/we are located, and (v) the country in which the financial institution or cryptocurrency exchange that I/we use to receive payment for the rehabilitation claim is located.
東京地方裁判所その他裁判所(日本国外の裁判所を含む。)、本民事再生手続及び本破産手続(併せて以下「本民事再生手続等」という。)における調査委員(その代理及び補佐を含む。)その他の機関、日本国内外の行政官庁・捜査機関、管財人が本民事再生手続等の遂行のために依頼する法律事務所及びデロイトトーマツコンサルティング合同会社等の専門家、金融機関、仮想通貨取引所、他の再生債権者、Eメールサービスプロバイダー、及び詐欺行為検証サービスプロバイダー Tokyo District Court and other courts (including courts outside of Japan); the Examiner (chosa iin) (including deputy examiners and assistant examiners) and other officers or bodies in the Civil Rehabilitation Proceedings or the Bankruptcy Proceedings (collectively, the “Civil Rehabilitation Proceedings, Etc.”); government offices and investigation agencies in or outside of Japan; counsel and experts including the law firms and Deloitte Tohmatsu Consulting LLC. which the trustee has retained to proceed with the Civil Rehabilitation Proceedings, Etc.; financial institutions; cryptocurrency exchangers; other rehabilitation creditors; email service providers; and fraudulent act verification service providers
(d) 管財人は、本民事再生手続等に必要な限りで私/当社のブラウザ設定により影響されない特定の永続クッキーを使用する可能性があること。 The trustee might, to the extent necessary for the Civil Rehabilitation Proceedings, Etc., use a specific permanent cookies setting that will be unaffected by my/our browser setting.
24.私/当社の再生債権に関する事項が、オンライン上で他の再生債権者による閲覧の対象となり、また、東京地方裁判所において本民事再生手続の利害関係人の閲覧及び謄写の対象となる場合があること。 The information regarding my/our rehabilitation claim may be available online to other rehabilitation creditors, and may be subject to the inspection and copying thereof at the Tokyo District Court by an interested party in the Civil Rehabilitation Proceedings.
25.私が死亡した場合、本民事再生手続との関係では、再生管財人が、日本の法令等及び実務に従って、相続に関する各種関係資料の提出を求め、また、誰を再生債権者として取り扱うかについて判断すること、及び、当該判断に起因又は関連して生じるあらゆる損害等について、MTGOX及び再生管財人は一切の責任を負わず、私及び私の相続人はMTGOX及び再生管財人に対して当該損害等に関して損害賠償請求、補償請求その他一切の請求をしないこと。 For the purpose of the Civil Rehabilitation Proceedings, in the event that I died, the Rehabilitation Trustee may, in accordance with the Laws and practices of Japan, request for relevant evidence and explanation on the inheritance and determine who to be treated as the rehabilitation creditor; and MTGOX and the Rehabilitation Trustee are not liable in any respect for any Damages arising out of or in connection with such determination, and I and my heir(s)/successor(s) will not make any claim for damages or compensation, or make any other claim with respect to such Damages against MTGOX or the Rehabilitation Trustee.
26.本同意事項は日本語を正文とすること。本同意事項につき作成される英語の翻訳文は参考にすぎず、日本語と英語との間で相互に内容の相違、矛盾がある場合であっても、日本語のみが効力を有すること。 The governing language of these terms of consent shall be the Japanese language. The English-language translation thereof is merely for reference purposes only; and notwithstanding any discrepancy or contradiction in details between the Japanese-language original and the English-language translation the Japanese-language original shall prevail.
27. 本民事再生手続等及びこれに関連又は付随して生じる一切の請求又は紛争は日本法に準拠し、東京地方裁判所を専属的合意管轄裁判所とすること。 The Civil Rehabilitation Proceedings, Etc. and all claims and disputes arising out of, in connection with, or incidental to, the Civil Rehabilitation Proceedings, Etc. are governed by Japanese law, and the Tokyo District Court shall have exclusive jurisdiction.
28. 再生管財人が、本同意事項を必要に応じ変更すること。但し、再生管財人が変更についてwww.mtgox.comにおいて告知したものに限る。 The Rehabilitation Trustee will, as necessary, amend these terms of consent. However, amendments are limited to those that the Rehabilitation Trustee has notified on the website www.mtgox.com.
submitted by OculoDoc to mtgoxinsolvency [link] [comments]

You can call you a Bitcoiner if you know/can explain these terms...

03/Jan/2009
10 Minutes
10,000 BTC Pizza
2016 Blocks
21 Million
210,000 Blocks
51% Attack
Address
Altcoin
Antonopoulos
Asic
Asic Boost
Base58
Batching
Bech32
Bit
Bitcoin Cash
Bitcoin Improvement Proposal (BIP)
Bitcoin SV
Bitmain
Block
Block height
Block reward
Blockchain
Blockexplorer
Bloom Filter
Brain Wallet
Buidl
Change Address
Child pays for parent (CPFP)
Coinbase (not the exchange)
CoinJoin
Coinmarketcap (CMC)
Colored Coin
Confirmation
Consensus
Custodial Wallet
Craig Wright
David Kleinman
Difficulty
Difficulty adjustment
Difficulty Target
Dogecoin
Dorian Nakamoto
Double spend
Elliptic Curve Digital Signature Algorithm (ECDSA)
Ethereum
Faketoshi
Fork
Full Node
Gavin Andresen
Genesis Block
Getting goxed
Halving
Hard Fork
Hardware Wallet
Hash
Hashing
Hierarchical Deterministic (HD) Wallet
Hodl
Hot Wallet
Initial Coin Offering (ICO)
Initial Exchange Offering (IEO)
Ledger
Light Node
Lightning
Litecoin
Locktime
Mainnet
Malleability
Master Private Key
Master Public Key
Master Seed
mBTC
Mempool
Merkle Tree
Mining
Mining Farm
Mining Pool
Mixing
MtGox
Multisig
Nonce
Not your keys,...
Opcode
Orphan block
P2PKH
P2SH
Paper Wallet
Peers
Pieter Wuille
Premining
Private key
Proof of Stake (PoS)
Proof of Work (PoW)
Pruning
Public key
Pump'n'Dump
Replace by Fee (RBF)
Ripemd160
Roger Ver
sat
Satoshi Nakamoto
Schnorr Signatures
Script
Segregated Witness (Segwit)
Sha256
Shitcoin
Sidechain
Signature
Signing
Simplified Payment Verification (SPV)
Smart Contract
Soft Fork
Stratum
Syncing
Testnet
Transaction
Transaction Fees
TransactionId (Txid)
Trezor
User Activated Soft Fork (UASF)
Utxo
Wallet Import Format (WIF)
Watch-Only Address
Whitepaper
List obviously not complete. Suggestions appreciated.
Refs:
https://bitcoin.org/en/developer-glossary https://en.bitcoin.it/wiki/Main_Page https://www.youtube.com/channel/UCgo7FCCPuylVk4luP3JAgVw https://www.youtube.com/useaantonop
submitted by PolaT1x to Bitcoin [link] [comments]

Technical: A Brief History of Payment Channels: from Satoshi to Lightning Network

Who cares about political tweets from some random country's president when payment channels are a much more interesting and are actually capable of carrying value?
So let's have a short history of various payment channel techs!

Generation 0: Satoshi's Broken nSequence Channels

Because Satoshi's Vision included payment channels, except his implementation sucked so hard we had to go fix it and added RBF as a by-product.
Originally, the plan for nSequence was that mempools would replace any transaction spending certain inputs with another transaction spending the same inputs, but only if the nSequence field of the replacement was larger.
Since 0xFFFFFFFF was the highest value that nSequence could get, this would mark a transaction as "final" and not replaceable on the mempool anymore.
In fact, this "nSequence channel" I will describe is the reason why we have this weird rule about nLockTime and nSequence. nLockTime actually only works if nSequence is not 0xFFFFFFFF i.e. final. If nSequence is 0xFFFFFFFF then nLockTime is ignored, because this if the "final" version of the transaction.
So what you'd do would be something like this:
  1. You go to a bar and promise the bartender to pay by the time the bar closes. Because this is the Bitcoin universe, time is measured in blockheight, so the closing time of the bar is indicated as some future blockheight.
  2. For your first drink, you'd make a transaction paying to the bartender for that drink, paying from some coins you have. The transaction has an nLockTime equal to the closing time of the bar, and a starting nSequence of 0. You hand over the transaction and the bartender hands you your drink.
  3. For your succeeding drink, you'd remake the same transaction, adding the payment for that drink to the transaction output that goes to the bartender (so that output keeps getting larger, by the amount of payment), and having an nSequence that is one higher than the previous one.
  4. Eventually you have to stop drinking. It comes down to one of two possibilities:
    • You drink until the bar closes. Since it is now the nLockTime indicated in the transaction, the bartender is able to broadcast the latest transaction and tells the bouncers to kick you out of the bar.
    • You wisely consider the state of your liver. So you re-sign the last transaction with a "final" nSequence of 0xFFFFFFFF i.e. the maximum possible value it can have. This allows the bartender to get his or her funds immediately (nLockTime is ignored if nSequence is 0xFFFFFFFF), so he or she tells the bouncers to let you out of the bar.
Now that of course is a payment channel. Individual payments (purchases of alcohol, so I guess buying coffee is not in scope for payment channels). Closing is done by creating a "final" transaction that is the sum of the individual payments. Sure there's no routing and channels are unidirectional and channels have a maximum lifetime but give Satoshi a break, he was also busy inventing Bitcoin at the time.
Now if you noticed I called this kind of payment channel "broken". This is because the mempool rules are not consensus rules, and cannot be validated (nothing about the mempool can be validated onchain: I sigh every time somebody proposes "let's make block size dependent on mempool size", mempool state cannot be validated by onchain data). Fullnodes can't see all of the transactions you signed, and then validate that the final one with the maximum nSequence is the one that actually is used onchain. So you can do the below:
  1. Become friends with Jihan Wu, because he owns >51% of the mining hashrate (he totally reorged Bitcoin to reverse the Binance hack right?).
  2. Slip Jihan Wu some of the more interesting drinks you're ordering as an incentive to cooperate with you. So say you end up ordering 100 drinks, you split it with Jihan Wu and give him 50 of the drinks.
  3. When the bar closes, Jihan Wu quickly calls his mining rig and tells them to mine the version of your transaction with nSequence 0. You know, that first one where you pay for only one drink.
  4. Because fullnodes cannot validate nSequence, they'll accept even the nSequence=0 version and confirm it, immutably adding you paying for a single alcoholic drink to the blockchain.
  5. The bartender, pissed at being cheated, takes out a shotgun from under the bar and shoots at you and Jihan Wu.
  6. Jihan Wu uses his mystical chi powers (actually the combined exhaust from all of his mining rigs) to slow down the shotgun pellets, making them hit you as softly as petals drifting in the wind.
  7. The bartender mutters some words, clothes ripping apart as he or she (hard to believe it could be a she but hey) turns into a bear, ready to maul you for cheating him or her of the payment for all the 100 drinks you ordered from him or her.
  8. Steely-eyed, you stand in front of the bartender-turned-bear, daring him to touch you. You've watched Revenant, you know Leonardo di Caprio could survive a bear mauling, and if some posh actor can survive that, you know you can too. You make a pose. "Drunken troll logic attack!"
  9. I think I got sidetracked here.
Lessons learned?

Spilman Channels

Incentive-compatible time-limited unidirectional channel; or, Satoshi's Vision, Fixed (if transaction malleability hadn't been a problem, that is).
Now, we know the bartender will turn into a bear and maul you if you try to cheat the payment channel, and now that we've revealed you're good friends with Jihan Wu, the bartender will no longer accept a payment channel scheme that lets one you cooperate with a miner to cheat the bartender.
Fortunately, Jeremy Spilman proposed a better way that would not let you cheat the bartender.
First, you and the bartender perform this ritual:
  1. You get some funds and create a transaction that pays to a 2-of-2 multisig between you and the bartender. You don't broadcast this yet: you just sign it and get its txid.
  2. You create another transaction that spends the above transaction. This transaction (the "backoff") has an nLockTime equal to the closing time of the bar, plus one block. You sign it and give this backoff transaction (but not the above transaction) to the bartender.
  3. The bartender signs the backoff and gives it back to you. It is now valid since it's spending a 2-of-2 of you and the bartender, and both of you have signed the backoff transaction.
  4. Now you broadcast the first transaction onchain. You and the bartender wait for it to be deeply confirmed, then you can start ordering.
The above is probably vaguely familiar to LN users. It's the funding process of payment channels! The first transaction, the one that pays to a 2-of-2 multisig, is the funding transaction that backs the payment channel funds.
So now you start ordering in this way:
  1. For your first drink, you create a transaction spending the funding transaction output and sending the price of the drink to the bartender, with the rest returning to you.
  2. You sign the transaction and pass it to the bartender, who serves your first drink.
  3. For your succeeding drinks, you recreate the same transaction, adding the price of the new drink to the sum that goes to the bartender and reducing the money returned to you. You sign the transaction and give it to the bartender, who serves you your next drink.
  4. At the end:
    • If the bar closing time is reached, the bartender signs the latest transaction, completing the needed 2-of-2 signatures and broadcasting this to the Bitcoin network. Since the backoff transaction is the closing time + 1, it can't get used at closing time.
    • If you decide you want to leave early because your liver is crying, you just tell the bartender to go ahead and close the channel (which the bartender can do at any time by just signing and broadcasting the latest transaction: the bartender won't do that because he or she is hoping you'll stay and drink more).
    • If you ended up just hanging around the bar and never ordering, then at closing time + 1 you broadcast the backoff transaction and get your funds back in full.
Now, even if you pass 50 drinks to Jihan Wu, you can't give him the first transaction (the one which pays for only one drink) and ask him to mine it: it's spending a 2-of-2 and the copy you have only contains your own signature. You need the bartender's signature to make it valid, but he or she sure as hell isn't going to cooperate in something that would lose him or her money, so a signature from the bartender validating old state where he or she gets paid less isn't going to happen.
So, problem solved, right? Right? Okay, let's try it. So you get your funds, put them in a funding tx, get the backoff tx, confirm the funding tx...
Once the funding transaction confirms deeply, the bartender laughs uproariously. He or she summons the bouncers, who surround you menacingly.
"I'm refusing service to you," the bartender says.
"Fine," you say. "I was leaving anyway;" You smirk. "I'll get back my money with the backoff transaction, and posting about your poor service on reddit so you get negative karma, so there!"
"Not so fast," the bartender says. His or her voice chills your bones. It looks like your exploitation of the Satoshi nSequence payment channel is still fresh in his or her mind. "Look at the txid of the funding transaction that got confirmed."
"What about it?" you ask nonchalantly, as you flip open your desktop computer and open a reputable blockchain explorer.
What you see shocks you.
"What the --- the txid is different! You--- you changed my signature?? But how? I put the only copy of my private key in a sealed envelope in a cast-iron box inside a safe buried in the Gobi desert protected by a clan of nomads who have dedicated their lives and their childrens' lives to keeping my private key safe in perpetuity!"
"Didn't you know?" the bartender asks. "The components of the signature are just very large numbers. The sign of one of the signature components can be changed, from positive to negative, or negative to positive, and the signature will remain valid. Anyone can do that, even if they don't know the private key. But because Bitcoin includes the signatures in the transaction when it's generating the txid, this little change also changes the txid." He or she chuckles. "They say they'll fix it by separating the signatures from the transaction body. They're saying that these kinds of signature malleability won't affect transaction ids anymore after they do this, but I bet I can get my good friend Jihan Wu to delay this 'SepSig' plan for a good while yet. Friendly guy, this Jihan Wu, it turns out all I had to do was slip him 51 drinks and he was willing to mine a tx with the signature signs flipped." His or her grin widens. "I'm afraid your backoff transaction won't work anymore, since it spends a txid that is not existent and will never be confirmed. So here's the deal. You pay me 99% of the funds in the funding transaction, in exchange for me signing the transaction that spends with the txid that you see onchain. Refuse, and you lose 100% of the funds and every other HODLer, including me, benefits from the reduction in coin supply. Accept, and you get to keep 1%. I lose nothing if you refuse, so I won't care if you do, but consider the difference of getting zilch vs. getting 1% of your funds." His or her eyes glow. "GENUFLECT RIGHT NOW."
Lesson learned?

CLTV-protected Spilman Channels

Using CLTV for the backoff branch.
This variation is simply Spilman channels, but with the backoff transaction replaced with a backoff branch in the SCRIPT you pay to. It only became possible after OP_CHECKLOCKTIMEVERIFY (CLTV) was enabled in 2015.
Now as we saw in the Spilman Channels discussion, transaction malleability means that any pre-signed offchain transaction can easily be invalidated by flipping the sign of the signature of the funding transaction while the funding transaction is not yet confirmed.
This can be avoided by simply putting any special requirements into an explicit branch of the Bitcoin SCRIPT. Now, the backoff branch is supposed to create a maximum lifetime for the payment channel, and prior to the introduction of OP_CHECKLOCKTIMEVERIFY this could only be done by having a pre-signed nLockTime transaction.
With CLTV, however, we can now make the branches explicit in the SCRIPT that the funding transaction pays to.
Instead of paying to a 2-of-2 in order to set up the funding transaction, you pay to a SCRIPT which is basically "2-of-2, OR this singlesig after a specified lock time".
With this, there is no backoff transaction that is pre-signed and which refers to a specific txid. Instead, you can create the backoff transaction later, using whatever txid the funding transaction ends up being confirmed under. Since the funding transaction is immutable once confirmed, it is no longer possible to change the txid afterwards.

Todd Micropayment Networks

The old hub-spoke model (that isn't how LN today actually works).
One of the more direct predecessors of the Lightning Network was the hub-spoke model discussed by Peter Todd. In this model, instead of payers directly having channels to payees, payers and payees connect to a central hub server. This allows any payer to pay any payee, using the same channel for every payee on the hub. Similarly, this allows any payee to receive from any payer, using the same channel.
Remember from the above Spilman example? When you open a channel to the bartender, you have to wait around for the funding tx to confirm. This will take an hour at best. Now consider that you have to make channels for everyone you want to pay to. That's not very scalable.
So the Todd hub-spoke model has a central "clearing house" that transport money from payers to payees. The "Moonbeam" project takes this model. Of course, this reveals to the hub who the payer and payee are, and thus the hub can potentially censor transactions. Generally, though, it was considered that a hub would more efficiently censor by just not maintaining a channel with the payer or payee that it wants to censor (since the money it owned in the channel would just be locked uselessly if the hub won't process payments to/from the censored user).
In any case, the ability of the central hub to monitor payments means that it can surveill the payer and payee, and then sell this private transactional data to third parties. This loss of privacy would be intolerable today.
Peter Todd also proposed that there might be multiple hubs that could transport funds to each other on behalf of their users, providing somewhat better privacy.
Another point of note is that at the time such networks were proposed, only unidirectional (Spilman) channels were available. Thus, while one could be a payer, or payee, you would have to use separate channels for your income versus for your spending. Worse, if you wanted to transfer money from your income channel to your spending channel, you had to close both and reshuffle the money between them, both onchain activities.

Poon-Dryja Lightning Network

Bidirectional two-participant channels.
The Poon-Dryja channel mechanism has two important properties:
Both the original Satoshi and the two Spilman variants are unidirectional: there is a payer and a payee, and if the payee wants to do a refund, or wants to pay for a different service or product the payer is providing, then they can't use the same unidirectional channel.
The Poon-Dryjam mechanism allows channels, however, to be bidirectional instead: you are not a payer or a payee on the channel, you can receive or send at any time as long as both you and the channel counterparty are online.
Further, unlike either of the Spilman variants, there is no time limit for the lifetime of a channel. Instead, you can keep the channel open for as long as you want.
Both properties, together, form a very powerful scaling property that I believe most people have not appreciated. With unidirectional channels, as mentioned before, if you both earn and spend over the same network of payment channels, you would have separate channels for earning and spending. You would then need to perform onchain operations to "reverse" the directions of your channels periodically. Secondly, since Spilman channels have a fixed lifetime, even if you never used either channel, you would have to periodically "refresh" it by closing it and reopening.
With bidirectional, indefinite-lifetime channels, you may instead open some channels when you first begin managing your own money, then close them only after your lawyers have executed your last will and testament on how the money in your channels get divided up to your heirs: that's just two onchain transactions in your entire lifetime. That is the potentially very powerful scaling property that bidirectional, indefinite-lifetime channels allow.
I won't discuss the transaction structure needed for Poon-Dryja bidirectional channels --- it's complicated and you can easily get explanations with cute graphics elsewhere.
There is a weakness of Poon-Dryja that people tend to gloss over (because it was fixed very well by RustyReddit):
Another thing I want to emphasize is that while the Lightning Network paper and many of the earlier presentations developed from the old Peter Todd hub-and-spoke model, the modern Lightning Network takes the logical conclusion of removing a strict separation between "hubs" and "spokes". Any node on the Lightning Network can very well work as a hub for any other node. Thus, while you might operate as "mostly a payer", "mostly a forwarding node", "mostly a payee", you still end up being at least partially a forwarding node ("hub") on the network, at least part of the time. This greatly reduces the problems of privacy inherent in having only a few hub nodes: forwarding nodes cannot get significantly useful data from the payments passing through them, because the distance between the payer and the payee can be so large that it would be likely that the ultimate payer and the ultimate payee could be anyone on the Lightning Network.
Lessons learned?

Future

After LN, there's also the Decker-Wattenhofer Duplex Micropayment Channels (DMC). This post is long enough as-is, LOL. But for now, it uses a novel "decrementing nSequence channel", using the new relative-timelock semantics of nSequence (not the broken one originally by Satoshi). It actually uses multiple such "decrementing nSequence" constructs, terminating in a pair of Spilman channels, one in both directions (thus "duplex"). Maybe I'll discuss it some other time.
The realization that channel constructions could actually hold more channel constructions inside them (the way the Decker-Wattenhofer puts a pair of Spilman channels inside a series of "decrementing nSequence channels") lead to the further thought behind Burchert-Decker-Wattenhofer channel factories. Basically, you could host multiple two-participant channel constructs inside a larger multiparticipant "channel" construct (i.e. host multiple channels inside a factory).
Further, we have the Decker-Russell-Osuntokun or "eltoo" construction. I'd argue that this is "nSequence done right". I'll write more about this later, because this post is long enough.
Lessons learned?
submitted by almkglor to Bitcoin [link] [comments]

March 20th 2019 Creditors Meeting Q&A

As usual the documents distributed during the creditors meeting are available from the MtGox.com website.
Meeting started at 13:30, Q&A at 14:02. Next creditors meeting will be held October 1st 2019 at 13:30.
Apart from what is written on the report, the trustee mentioned that large claims in assessment could make it difficult for civil rehabilitation to continue moving forward, and also mentions that seeing how bitcoin price dropped it might be better to sell. He asked people in the room at the end who was for selling BTC (0% responded "for", ~20% responded "against") but mentioned he wouldn't be bound by this and would act in the interest of creditors with approval of the court.
submitted by MagicalTux to mtgoxinsolvency [link] [comments]

Binance Could Learn from 10 Years of Crypto

Binance's deposit problems on 2019 arise from an known, age-old, property of cryptocurrencies, generally known as "malleability".
On Feb 5, 2019, Binance was reported to credit, for a second time, some Nano user deposits that had already been credited months before. The presumed reason is that they were upgrading nodes and replaying the block chain, and didn't turn off the deposit engine for this replay. When the new blocks were replayed, they somehow generated new block identifiers on Binance's internal servers (that is, these blocks were not relayed to Binance from outside Binance).
These new block identifiers (for old blocks) triggered the deposit processor to create new internal deposits for user accounts, causing these accounts to get unduly credited with extra funds.
This general crypto issue has been known for ages and it is surprising that Binance was susceptible to it. For example, the standard bitcoin transaction ID can be changed in a variety of ways without invalidating the transaction. This is called transaction ID malleability. If an exchange considers transactions with new transaction IDs as new deposits, they are susceptible to double deposits.
The reason exchanges don't get caught by transaction malleability is that they judge new deposits by the transaction details and not the transaction ID, which can be changed. They also don't credit a user until the transaction has been confirmed a few times. While going down, MtGox famously blamed their problems on bitcoin transaction malleability (even though no one could ever verify these claims).
Even though exchanges have adopted workarounds, the general property is potentially problematic enough that bitcoin introduced a new type of transaction identifier with the segwit fork to address this general issue of malleability.
The nano protocol doesn't include the concept of confirmations, so counting confirmations to validate deposits can't apply. However, this dissimilarity doesn't mean that the basic problem of transaction malleability isn't known. And it underscores that the general practice of checking transaction details is much better than relying on protocol identifiers (like block or transaction IDs).
My understanding is that nano 17.1 fixed the underlying source of malleability that caught Binance, but in upgrading to the fix Binance's deposit processor was running the old protocol and processed a few second deposits.
submitted by coinoleum to nanocurrency [link] [comments]

r/Bitcoin recap - March 2018

Hi Bitcoiners!
I’m back with the fifteenth monthly Bitcoin news recap.
For those unfamiliar, each day I pick out the most popularelevant/interesting stories in Bitcoin and save them. At the end of the month I release them in one batch, to give you a quick (but not necessarily the best) overview of what happened in bitcoin over the past month.
And a lot has happened. It's easy to forget with so much focus on the price. Take a moment and scroll through the list below. You'll find an incredibly eventful month.
You can see recaps of the previous months on Bitcoinsnippets.com
A recap of Bitcoin in March 2018
submitted by SamWouters to Bitcoin [link] [comments]

MTGox still authoring invalid transactions

The MTGox transaction API (https://data.mtgox.com/api/0/bitcoin_tx.php) shows transactions MTGox authors.
Throughout the outage— e.g. as early as the 8th— they've been making a small number of what looks like dust sweeping transactions.
One shown right now is TXID ed7ffa58fef651adaf1281ad10e98a4399eb2be40950345c7ccb7c8f76f067e1 which spends 45d45286bac04311684ab7716ab170b50781cde6b094d9a644fb89ca07ae6888:31 which is the coinbase transaction of block 0000000000000000da75e32e941537e00bd2e752527adba6193f35ccaa6da293. At the moment it only has 62 confirmations.
Because the rules of the Bitcoin protocol prohibit spending coinbase txn with under 100 confirmations this transaction is currently invalid and will remain invalid for another 38 blocks.
So after all this outage time, MTGox has still not fixed their software to stop authoring invalid transactions.
submitted by nullc to Bitcoin [link] [comments]

Received Notice from Mt. Gox Regarding Bitcoin Rehabilitation

So Mt. Gox was a major bitcoin platform when it first got popular, however they were corrupt and there was a lot of fraud. I recently received the below notice and was hoping somebody could translate to help me determine if it is worth and if I am entitled to claims under this legal settlement:

To creditor (creditor number: xxxxxx)
You have received this email because you are a creditor of MtGox Co., Ltd. (“MtGox”) who did not file a proof of rehabilitation claim(s) under the civil rehabilitation proceedings for MtGox (the “Civil Rehabilitation Proceedings”) and whose remaining balance on the MtGox database was approved by the Rehabilitation Trustee as a self-approved rehabilitation claim(s) (i.e., a rehabilitation claim that was not filed but accepted by the trustee voluntarily in accordance with the Civil Rehabilitation Act).
As the rehabilitation trustee previously announced, the objection to your self-approved rehabilitation claim(s) filed by certain other creditors has been withdrawn.
In the Civil Rehabilitation Proceeding, the rehabilitation creditors who filed their proofs of rehabilitation claim agreed to the terms of consent regarding the Civil Rehabilitation Proceedings to seamlessly proceed with various procedures including repayment. However, since you have not filed a claim, you have not yet agreed to these terms of consent. In order to facilitate various proceedings, your consent to the terms is required.
Accordingly, we hereby stated the “Terms of Consent Regarding the Civil Rehabilitation Proceedings” at the end of this email, as well as attached the same to this email. Please carefully read the terms therein, and if you agree to the terms, please reply to this email and state the sentence below in the body of your reply.
“I/We hereby agree to and represent as set forth in the ‘Terms of Consent Regarding the Civil Rehabilitation Proceedings’ sent by the rehabilitation trustee, in relation to the civil rehabilitation proceedings for MtGox Co., Ltd.”
The rehabilitation trustee will continue to make an effort to conduct the Civil Rehabilitation Proceedings appropriately and in consultation with the Tokyo District Court, and the rehabilitation trustee would appreciate the understanding and cooperation of all concerned parties.
Rehabilitation Debtor: MtGox Co., Ltd. Rehabilitation Trustee: Nobuaki Kobayashi, Attorney-at-law
------------------------------------------------------------------------------------------------------------------------- 事件番号 平成29年(再)第35号 / Case Number 2017 (sai) No. 35 再生債務者 株式会社MTGOX / Rehabilitation Debtor: MTGOX Co., Ltd.
民事再生手続に関する同意事項 Terms of Consent Regarding the Civil Rehabilitation Proceedings
  1. 私/当社は、上記債権者番号の自認債権者本人であり、私/当社が届け出た情報は真実、正確かつ完全であること。その違反に起因又は関連して生じるあらゆる損害、損失、債務、コスト又は費用(以下「損害等」という。)について、株式会社MTGOX(以下「MTGOX」という。)及びMTGOXの民事再生手続(東京地方裁判所平成29年(再)第35号。以下「本民事再生手続」という。)における管財人(その代理及び補佐を含み、以下「再生管財人」という。)は一切の責任を負わず、私/当社はMTGOX及び再生管財人に対して当該損害等に関して損害賠償請求、補償請求その他一切の請求をしないこと。 I am/We are the creditor of self-approved rehabilitation claims that has the above creditor number, and I/we represent that the information that I/we have provided therein is true, accurate, and complete. MtGox Co., Ltd. (“MTGOX”) and the trustee (including deputy trustees and assistant trustees; the “Rehabilitation Trustee”) of the MTGOX civil rehabilitation proceedings (Tokyo District Court; 2017 (sai) Case No. 35; the “Civil Rehabilitation Proceedings”) are not liable in any respect for any damage, loss, liability, cost or expense (“Damages”) arising out of or in connection with any breach of such representation, and I/we will not make any claim for damages or compensation, or make any other claim with respect to such Damages against MTGOX or the Rehabilitation Trustee.
  2. 再生管財人の故意によらず、ビットコイン及びビットコインから分岐した他の仮想通貨(以下「フォークコイン」といい、ビットコインと総称して「ビットコイン等」という。)の技術上の問題・障害等に起因又は関連して生じるあらゆる損害等(ビットコイン等又は金銭による弁済を受領できないことによる損害を含むが、これに限られない。)について、MTGOX及び再生管財人は一切の責任を負わず、私/当社はMTGOX及び再生管財人に対して当該損害等に関して損害賠償請求、補償請求その他一切の請求をしないこと。 MTGOX and the Rehabilitation Trustee are not liable in any respect for any Damages arising out of or in connection with any technical issue, impediment, or other ground, in the absence of without willful misconduct by the Rehabilitation Trustee, regarding Bitcoin or any other cryptocurrency split from Bitcoin (a “Fork Coin”; collectively with Bitcoin, “Bitcoin, Etc.”) (including, but not limited to, any damage related to payments in Bitcoin, Etc. or cash not being received), and I/we will not make any claim for damages or compensation, or make any other claim with respect to such Damages against MTGOX or the Rehabilitation Trustee.
  3. 私/当社は、本書式のダウンロードその他のために必要なコンピュータ等の機器、ソフトウェアその他のアプリケーション、通信回線その他の通信環境等の準備(必要なアプリケーションのインストールを含む。)及び維持、並びに自らの利用環境に応じたコンピュータ・ウイルスの感染の防止、不正アクセス及び情報漏洩の防止等のセキュリティ対策を、自らの費用と責任において行うこと。本項に定める事項の違反に起因又は関連して生じるあらゆる損害等について、MTGOX及び再生管財人は一切の責任を負わず、私/当社はMTGOX及び再生管財人に対して当該損害等に関して損害賠償請求、補償請求その他一切の請求をしないこと。私/当社は、MTGOX及び再生管財人が利用環境を推奨した場合であっても動作保証は行わないことを認識し、これに同意していること。 I/We will, at my/our expense and responsibility, setup and maintain computers and other equipment, software and other applications, telecommunication lines and other telecommunication environments, among others, necessary to download this form (including installing necessary applications) and, in accordance with my/our use environment, take security measures, such as preventing infection by computer viruses, unauthorized access and information divulgence. MTGOX and the Rehabilitation Trustee are not liable in any respect for any Damages arising out of or in connection with any breach of any matter stipulated in this paragraph, and I/we will not make any claim for damages or compensation, or make any other claim with respect to such Damages against MTGOX or the Rehabilitation Trustee. I/We acknowledge and agree that notwithstanding that MTGOX and the Rehabilitation Trustee have recommended a use environment its operation is not guaranteed in any respect.
  4. 私/当社は、自らの責任において、MTGOXのビットコイン取引所に登録していたユーザーネーム、メールアドレス及びパスワード、MTGOXの破産手続(東京地方裁判所平成26年(フ)第3830号。以下「本破産手続」という。)において債権者情報として登録した連絡先メールアドレス等私/当社であることの確認のために必要な情報及びこれに関連するもの(以下、総称して「パスワード等」という。)を管理、保管するものとし、パスワード等を第三者に利用させたり、貸与、譲渡、名義変更、売買その他処分をしたりしないこと。再生管財人は、私/当社のパスワード等により行われた一切の行為を、私/当社の行為とみなすことができ、パスワード等の管理不十分、使用上の過誤、漏洩、第三者の使用、盗用等に起因又は関連して生じるあらゆる損害等について、MTGOX及び再生管財人は一切の責任を負わず、私/当社はMTGOX及び再生管財人に対して当該損害等に関して損害賠償請求、補償請求その他一切の請求をしないこと。 I/We will, at my/our responsibility, manage and store user names, email address and passwords registered on the MTGOX Bitcoin exchange; the contact address registered as creditor information in the bankruptcy proceedings (Tokyo District Court; 2014 (fu) Case No. 3830; the “Bankruptcy Proceedings”); or any other information necessary for identity confirmation and anything related thereto (collectively, the “Passwords”) and will neither permit any third party to use the Passwords nor lend, assign, transfer ownership, trade, or handle the Passwords in any other manner. The Rehabilitation Trustee may deem all acts conducted with my/our Passwords as mine/our act; and MTGOX and the Rehabilitation Trustee are not liable in any respect for any Damages arising out of or in connection with insufficient management, erroneous use, divulgence, third party use, illegal use, or otherwise of the Passwords, and I/we will not make any claim for damages or compensation, or make any other claim with respect to such Damages against MTGOX or the Rehabilitation Trustee.
  5. 私/当社は、再生管財人が定めている又は今後定める、再生管財人が用意した方式・方法による届出・通知及びこれに関連する事項を行う際のルール(今後の変更を含む。)を理解した上でこれに従うものとし、当該ルールに違反し、又は違反しようとしたことに起因又は関連して生じるあらゆる損害等について、MTGOX及び再生管財人は一切の責任を負わず、私/当社はMTGOX及び再生管財人に対して当該損害等に関して損害賠償請求、補償請求その他一切の請求をしないこと。 I/We will familiarize myself/ourselves with and follow current rules or future rules (as amended from time to time) for any filing/notifying with the form/method the Rehabilitation Trustee provided and anything related thereto stipulated, by the Rehabilitation Trustee; and MTGOX and the Rehabilitation Trustee are not liable in any respect for any Damages arising out of or in connection with any breach of or any attempted breach of the rules, and I/we will not make any claim for damages or compensation, or make any other claim with respect to such Damages against MTGOX or the Rehabilitation Trustee.
  6. 他のウェブサイトからMTGOXのウェブサイトへのリンクが提供されている場合においても、MTGOXのウェブサイト以外のウェブサイト及びそこから得られる情報並びにそれに起因又は関連して生じる損害等について、MTGOX及び再生管財人は一切の責任を負わず、私/当社はMTGOX及び再生管財人に対して当該損害等に関して損害賠償請求、補償請求その他一切の請求をしないこと。 MTGOX and the Rehabilitation Trustee are not liable in any respect for any website other than MTGOX’s website, any information obtained therefrom, and any Damages arising out of or in connection with the same, notwithstanding that MTGOX’s website may be linked on another website, and I/we will not make any claim for damages or compensation, or make any other claim with respect to such Damages against MTGOX or the Rehabilitation Trustee.
  7. 私/当社と他の再生債権者その他の者との間において生じた取引、連絡、紛争等については、私/当社の責任において処理及び解決するものとし、かかる事項及びそれに起因又は関連して生じるあらゆる損害等について、MTGOX及び再生管財人は一切の責任を負わず、私/当社はMTGOX及び再生管財人に対して当該損害等に関して損害賠償請求、補償請求その他一切の請求をしないこと。 I/we will, at my/our responsibility, handle and resolve any and all transactions, communication, disputes, among others, arising between me/us, another rehabilitation creditor, or any other person; and MTGOX and the Rehabilitation Trustee are not liable in any respect for any relevant matter and any Damages arising out thereof or in connection therewith, and I/we will not make any claim for damages or compensation, or make any other claim with respect to such Damages against MTGOX or the Rehabilitation Trustee.
  8. 法律、政令、法令、命令、通達、条例、ガイドラインその他の規制(以下「法令等」という。)又は消費税を含む税制の将来の制定又は変更に起因又は関連して生じるあらゆる損害等について、MTGOX及び再生管財人は一切の責任を負わず、私/当社は、MTGOX及び再生管財人に対して当該損害等に関して損害賠償請求、補償請求その他一切の請求をしないこと。また、法令等又は消費税を含む税制の将来の制定又は変更が過去に遡及した場合に、これに起因又は関連して生じるあらゆる損害等について、MTGOX及び再生管財人は一切の責任を負わず、私/当社はMTGOX及び再生管財人に対して当該損害等に関して損害賠償請求、補償請求その他一切の請求をしないこと。 MTGOX and the Rehabilitation Trustee are not liable in any respect for any Damages arising out of or in connection with a future enactment or amendment to a law, cabinet order, ordinance, order, directive, bylaw, guideline, or any other regulation (“Laws”) or the tax system, including consumption tax; and I/we will not make any claim for damages or compensation, or make any other claim with respect to such Damages against MTGOX or the Rehabilitation Trustee. Further, MTGOX and the Rehabilitation Trustee are not liable in any respect for any Damages arising out of or in connection with any future enactment or amendment with a retroactive effect on Laws or the tax system including consumption tax, and I/we will not make any claim for damages or compensation, or make any other claim with respect to such Damages against MTGOX or the Rehabilitation Trustee.
  9. 裁判所又は再生管財人が、再生管財人が私/当社のメールアドレスと認めるメールアドレス宛に電子メールにより通知を送信することによって、私/当社に対する適法な通知があったものとみなすこと。当該メールアドレスの不備等(メールアドレスの記載漏れを含む。)に起因又は関連して、当該メールアドレスに宛てた電子メールを送信することができず又は電子メールが到達しない場合(到達が確認できない場合を含む。)であっても同様とすること。 An appropriate notification is deemed to have been made to me/us if the court or the Rehabilitation Trustee sends a notification via email to the email address which is considered to be my/our email address by the Rehabilitation Trustee. The same applies notwithstanding that, due to, or in connection with, an inadequacy, inaccurateness or incompleteness, or any other issue (including omission of the email address), in or with that email address, an email addressed to that email address cannot be sent or the email is not delivered including where receipt is unconfirmed.
10.私/当社が本届出書を利用して行った再生債権の届出の内容について、再生管財人が裁判所その他必要な第三者に提出すること。 The Rehabilitation Trustee may submit the proof of rehabilitation claim filed by me/us using this form to the court and other third parties as necessary.
11.私/当社は、本民事再生手続においてパスワード等を用いて入手することができる一切の情報(他の再生債権者に関する情報を含むが、これに限られない。)を、本民事再生手続における権利行使の目的にのみ使用することとし、第三者に提供、開示又は漏洩しないこと。 I/We will use information (including, but not limited to, information related to any other rehabilitation creditors) acquired by using the Passwords in the Civil Rehabilitation Proceedings only for the purpose of exercising rights in the Civil Rehabilitation Proceedings and will not provide, disclose, or divulge such information to any third party.
12.私/当社の本民事再生手続における議決権の額は、再生管財人が提示する次の為替レートによって、円換算されて評価されること。 The amount of my/our voting rights in the Civil Rehabilitation Proceedings is computed through conversion to Japanese Yen (JPY) using the following exchange rates provided by the Rehabilitation Trustee:
(a) 外国通貨 平成30年6月21日(日本時間)の東京外国為替市場・電信為替売相場として三菱UFJリサーチ&コンサルティング株式会社が公表した相場 Foreign currency: the exchange rates publicly announced by Mitsubishi UFJ Research and Consulting Co., Ltd. as the Tokyo Foreign Exchange Market / Telegraphic Transfer Selling Rate on June 21, 2018 (Japan Time) (b) ビットコイン 平成30年6月21日23時59分(日本時間)時点のCoinDeskが発表する米国ドル建てのビットコイン相場を(a)の相場により日本円に換算した金額(1 BTC=6,724.57米国ドル=749,318.83円。1米国ドル=111.43円) Bitcoin: the amount obtained by converting the Bitcoin price denominated in USD announced by CoinDesk at 23:59 on June 21, 2018 (Japan Time) to JPY using the exchange rate referred to in the above (a). (1 BTC=6,724.57 USD = 749,318.83 JPY; 1 USD = 111.43 JPY) (c) ビットコインキャッシュ 平成30年6月21日23時59分(日本時間)時点のCoinDeskが発表する米国ドル建てのビットコインキャッシュ相場を(a)の相場により日本円に換算した金額(1 BCH=874.82米国ドル=97,481.19円。1米国ドル=111.43円) Bitcoin Cash: the amount obtained by converting the Bitcoin Cash Price denominated in USD announced by CoinDesk at 23:59 on June 21, 2018 (Japan time) to JPY using the exchange rate referred to in the above (a). (1 BCH = 874.82 USD = 97,481.19 JPY; 1 USD = 111.43 JPY) (d) その他の仮想通貨 金額は未定 Amounts for other cryptocurrencies: not determined
13.本民事再生手続においては、ビットコイン等の返還請求権は非金銭債権として取り扱われ、当該返還請求権に係る遅延損害金は生じないこととすること。 In the Civil Rehabilitation Proceedings, the right to claim for return of Bitcoin Etc. is treated as a non-monetary claim, and no delay damages pertaining to such right to claim for return will accrue.
14.再生管財人の私/当社への弁済(金銭及びビットコイン等の弁済を含む。)及びこれに関連する行為が、日本国の外国為替及び外国貿易法、米国財務省の金融制裁(OFAC規制)その他私/当社に関して適用のあるいかなる法令等にも抵触しないこと。再生管財人は、再生管財人の実施する私/当社への弁済及びこれに関連する行為が、日本国外の法令等に抵触しないことをいかなる意味においても保証しないこと。これらの法令等への抵触に起因又は関連して生じるあらゆる損害等について、MTGOX及び再生管財人は一切の責任を負わず、私/当社はMTGOX及び再生管財人に対して当該損害等に関して損害賠償請求、補償請求その他一切の請求をしないこと。再生管財人の私/当社への弁済に起因又は関連して私/当社に課される一切の公租公課(当該弁済の態様によって公租公課の額が増減する場合を含む。)は、私/当社が負担し、当該公租公課又はその増減に起因又は関連して生じるあらゆる損害等について、MTGOX及び再生管財人は一切の責任を負わず、私/当社はMTGOX及び再生管財人に対して当該損害等に関して損害賠償請求、補償請求その他一切の請求をしないこと。 Any payment (including payment of cash and Bitcoin Etc.) to me/us by the Rehabilitation Trustee and any act related thereto do not conflict with the Foreign Exchange and Foreign Trade Act of Japan, the United States Department of the Treasury’s financial sanctions (OFAC regulations) and any other applicable Laws. The Rehabilitation Trustee does not guarantee, in any respect, that payment to me/us by the Rehabilitation Trustee and any act related thereto do not conflict with Laws outside of Japan. MTGOX and the Rehabilitation Trustee are not liable in any respect for any Damages arising out of or in connection with any conflict with any applicable Laws, and I/we will not make any claim for damages or compensation, or make any other claim with respect to such Damages against MTGOX or the Rehabilitation Trustee. I/We will bear all taxes and other public charges (including any increases or decreases in the amount of taxes and other public charges due to the manner of the payment) levied on me/us arising out of or in connection with any payment to me/us by the Rehabilitation Trustee; and MTGOX and the Rehabilitation Trustee are not liable in any respect for any Damages arising out of or in connection with such taxes and other public charges and increase or decrease thereof, and I/we will not make any claim for damages or compensation, or make any other claim with respect to such Damages against MTGOX or the Rehabilitation Trustee.
15.再生管財人が、仮想通貨取引所(日本国内の仮想通貨交換業者を含むが、これに限られない。以下同じ。)又は金融機関(資金移動業者を含む。以下同じ。)に開設された再生債権者の口座に対して弁済金を振り込む場合、私/当社は、再生管財人の指定する方法により届け出た氏名・名称と同一名義の仮想通貨取引所又は金融機関の口座で受け取ること。 If the Rehabilitation Trustee transfers the money for distribution to an account of a rehabilitation creditor opened at a cryptocurrency exchange (including, but not limited to, cryptocurrency exchangers in Japan; the same applies below) or a financial institution (including fund transfer operators; the same applies below), I/we will receive the same in the account at the cryptocurrency exchange or the financial institution under the same name as that name I/we notified in the manner designated by the Rehabilitation Trustee.
16.私/当社が再生管財人の指定する仮想通貨取引所に開設した口座でビットコイン等及び/又は金銭で弁済を受ける場合には、次の各事項。 If I/we receive payment in Bitcoin Etc. and/or in cash in an account opened at the cryptocurrency exchange designated by the Rehabilitation Trustee, the following applies:
(a) 私/当社は、送付先等の必要情報を正確に提供しなければならず、その誤りから結果的にビットコイン等及び/又は金銭を受領できなかったとしても、それに起因又は関連して生じるあらゆる損害等について、MTGOX及び再生管財人は一切の責任を負わず、私/当社はMTGOX及び再生管財人に対して当該損害等に関して損害賠償請求、補償請求その他一切の請求をしないこと。 I/we must accurately provide necessary information about my/our accounts, among others, and, notwithstanding that an error therein results in my/our not receiving Bitcoin, Etc. or cash, MTGOX and the Rehabilitation Trustee are not liable in any respect for any Damages arising out of or in connection with such non-receipt, and I/we will not make any claim for damages or compensation, or make any other claim with respect to such Damages against MTGOX or the Rehabilitation Trustee.
(b) 再生管財人がビットコイン等及び/又は金銭を当該仮想通貨取引所に交付した時点で弁済が完了し、MTGOX及び再生管財人の弁済義務は消滅するものとし、再生管財人による当該仮想通貨取引所へのビットコイン等及び/又は金銭の交付後、私/当社が何らかの理由(仮想通貨のブロックチェーンの不具合、仮想通貨取引所のシステムの不具合を含むが、これらに限られない。)により仮想通貨取引所からのビットコイン等及び/又は金銭の適切な弁済を受けることができなかったとしても、それに起因又は関連して生じるあらゆる損害等について、MTGOX及び再生管財人は一切の責任を負わず、私/当社はMTGOX及び再生管財人に対して当該損害等に関して損害賠償請求、補償請求その他一切の請求をしないこと。 The instant the Rehabilitation Trustee sends Bitcoin, Etc. or cash to the cryptocurrency exchange, the payment by MTGOX and the Rehabilitation Trustee is deemed complete, and the payment obligation of MTGOX and the Rehabilitation Trustee is deemed to be discharged; and, after Bitcoin Etc. or cash has been sent to the cryptocurrency exchange by the Rehabilitation Trustee, notwithstanding that I/we fail to receive appropriate payment of Bitcoin Etc. or cash from the cryptocurrency exchange for any reason (including, but not limited to, a malfunction in the blockchain of the cryptocurrency or a system malfunction at the cryptocurrency exchange), MTGOX and the Rehabilitation Trustee are not liable in any respect for any Damages arising out of or in connection with such failure, and I/we will not make any claim for damages or compensation, or make any other claim with respect to such Damages against MTGOX or the Rehabilitation Trustee.
17.私/当社が金融機関の口座において金銭で弁済を受ける場合には、次の各事項。 If I/we receive cash in an account at a financial institution, the following applies:
(a) 私/当社は、送付先等の必要情報を正確に提供しなければならず、その誤りから結果的に金銭を受領できなかったとしても、それに起因又は関連して生じるあらゆる損害等について、MTGOX及び再生管財人は一切の責任を負わず、私/当社はMTGOX及び再生管財人に対して当該損害等に関して損害賠償請求、補償請求その他一切の請求をしないこと。 I/We must accurately provide necessary information about my/our accounts, among others, and, notwithstanding that an error therein results in my/our not receiving cash, MTGOX and the Rehabilitation Trustee are not liable in any respect for any Damages arising out of or in connection with that, and I/we will not make any claim for damages or compensation, or make any other claim with respect to such Damages against MTGOX or the Rehabilitation Trustee.
(b) 取扱通貨の種別や送金元銀行との取引の有無、日本国内外の法令等及び各金融機関の内部基準への抵触並びに諸手数料の発生その他要因に基づき弁済金を受領できなかったとしても、それに起因又は関連して生じるあらゆる損害等について、MTGOX及び再生管財人は一切の責任を負わず、私/当社はMTGOX及び再生管財人に対して当該損害等に関して損害賠償請求、補償請求その他一切の請求をしないこと。 Notwithstanding that I/we fail to receive cash for distribution due to unavailability of the designated currencies or transactions with the designated financial institutions, any conflict with Laws in or outside Japan or an internal standard of any relevant financial institution, various processing charges and fees, or any other causes, MTGOX and the Rehabilitation Trustee are not liable in any respect for any Damages arising out of or in connection with that, and I/we will not make any claim for damages or compensation, or make any other claim with respect to such Damages against MTGOX or the Rehabilitation Trustee.
(c) 諸手数料等を差し引いた金額の弁済金を受け取る場合であっても、当該諸手数料等に起因又は関連して生じるあらゆる損害等について、MTGOX及び再生管財人は一切の責任を負わず、私/当社はMTGOX及び再生管財人に対して当該損害等に関して損害賠償請求、補償請求その他一切の請求をしないこと。 Notwithstanding that I/we have received payment from which various processing charges and fees have been deducted, MTGOX and the Rehabilitation Trustee are not liable in any respect for any Damages arising out of or in connection with such processing charges and fees, and I/we will not make any claim for damages or compensation, or make any other claim with respect to such Damages against MTGOX or the Rehabilitation Trustee.
18.フォークコインに係る再生債権の届出については、ビットコインに関する再生債権の届出をもって、届け出たビットコインの数に応じて、フォークコインに係る再生債権についても届け出たものとみなし、再生債権者は独自にフォークコインに係る再生債権を届け出ないこと。再生債権の届出があるとみなされるフォークコインは、通常の方法により売却可能であり、かつ、財産的価値のあるものに限られ、それ以外のフォークコインについては、再生債権の届出があるとは認められないこと。なお、ビットコインキャッシュは再生債権の届出があるとみなされるフォークコインに含まれること。 The filing of a proof of rehabilitation claim for a Fork Coin is deemed to have been made in proportion to the number of the filed Bitcoin for which the proof of rehabilitation claim has been filed, and the rehabilitation creditor cannot file its own proof of rehabilitation claim for a Fork Coin. Fork Coins that are deemed to have been filed are limited to those that can be sold in an ordinary manner and that have property value, and no other Fork Coin will be recognized as being deemed to have been filed. Bitcoin Cash is included in Fork Coins that are deemed to have been filed.
19.私/当社が再生管財人により認められた債権を契約により第三者に譲渡する場合には、当該譲渡契約の準拠法は日本法にするものとし、MTGOX及び再生管財人に当該譲渡を対抗するためには、日本法に基づく債権譲渡の対抗要件その他再生管財人が指定する要件を備えることが必要であること。再生管財人は、各国の法令等の定め及び債権譲渡契約で定められた準拠法の定めにかかわらず、日本法のみに基づき債権譲渡契約の有効性及び対抗要件具備の有無を判断すること。再生管財人が日本法に基づき債権譲渡契約の有効性及び対抗要件具備の有無を判断することに起因又は関連して生じるあらゆる損害等について、MTGOX及び再生管財人は一切の責任を負わず、私/当社はMTGOX及び再生管財人に対して当該損害等に関して損害賠償請求、補償請求その他一切の請求をしないこと。 If I/we intend to transfer or assign any rehabilitation claim that was approved by the Rehabilitation Trustee to any third party pursuant to an agreement, the governing law for such agreement shall be Japanese law, and the perfection requirements in accordance with the relevant Japanese law and any other requirements specified by the Rehabilitation Trustee shall be fully satisfied to perfect such claim transfer or assignment against MTGOX and the Rehabilitation Trustee. The Rehabilitation Trustee will determine the validity of such claim transfer or assignment and perfection thereof pursuant only to Japanese law, irrespective of any statute in each country’s Laws and any governing law provided for in such agreement. MTGOX and the Rehabilitation Trustee are not liable in any respect for any Damages arising out of or in connection with the Rehabilitation Trustee determining the validity of such claim transfer or assignment and perfection thereof pursuant to Japanese law, and I/we will not make any claim for damages or compensation, or make any other claim with respect to such Damages against MTGOX or the Rehabilitation Trustee.
20.再生管財人による債権譲渡の承認が、債権譲渡の承認に必要な手続(譲渡人及び譲受人の本人確認、譲渡を証明する文書の検証を含むが、これらに限られない。)その他の理由により遅滞した場合であっても、これに起因又は関連して生じるあらゆる損害等について、MTGOX及び再生管財人は一切の責任を負わず、私/当社はMTGOX及び再生管財人に対して当該損害等に関して損害賠償請求、補償請求その他一切の請求をしないこと。 Notwithstanding that approval by the Rehabilitation Trustee of a claim transfer or assignment is delayed by the procedures necessary for approval of a claim transfer or assignment (including, but not limited to, identity check of the transferoassignor and transferee/assignee and verification of documents proving transfer or assignment) or any other reason, MTGOX and the Rehabilitation Trustee are not liable in any respect for any Damages arising out of or in connection with such delay, and I/we will not make any claim for damages or compensation, or make any other claim with respect to such Damages against MTGOX or the Rehabilitation Trustee.
21.ある再生債権を譲渡する場合、当該再生債権の全部を譲渡することとし、その一部のみを譲渡しないこと。 If a rehabilitation claim is transferred or assigned, all of such rehabilitation claim, not part thereof, shall be transferred or assigned.
22.ビットコイン等に係る再生債権を譲渡する場合には、対象となるビットコイン及び当該ビットコインから分岐したフォークコインを併せて譲渡するものとし、ビットコイン又はフォークコインに係る再生債権を個別に譲渡しないこと。 If a rehabilitation claim pertaining to Bitcoin, Etc. is transferred or assigned, the Bitcoin subject to such transfer or assignment and the Fork Coin split from such Bitcoin shall be transferred or assigned collectively, and a rehabilitation claim pertaining to Bitcoin or Fork Coin shall not be transferred or assigned individually.
23.情報の取扱いに関する同意事項 Matters of consent related to information management
(a) 再生管財人が、以下の情報(個人情報の保護に関する法律(平成15年法律第57号)第2条第1項により定義される個人情報その他識別された又は識別可能な自然人に関する一切の情報を含むが、これに限られない。以下同じ。)を収集すること。 The Rehabilitation Trustee may collect the information below (including, but not limited to, personal information defined under Article 2(1) of the Act on the Protection of Personal Information (Act No. 57 of 2003) and any other information relating to an identified or identifiable natural person; the same applies below)
i. 私/当社が再生管財人に提供する情報 information that I/we provided to the Rehabilitation Trustee;
ii. 私/当社以外の情報源(身元証明サービス機関を含むが、これに限られない。)から収集する私/当社の情報 information concerning me/us provided by an information source (including, but not limited to, organizations providing ID verification services) other than myself/ourselves;
iii. 本破産手続において、私/当社が本破産手続の破産管財人に提供した一切の情報 all information that I/we provided to the bankruptcy trustee of the Bankruptcy Proceedings;
iv. 私/当社が、MTGOXに提供した一切の情報 all information that I/we provided to MTGOX; and
v. その他再生管財人が適正な方法により取得し、又は今後取得する情報 any other information acquired, or to be acquired going forward, by the Rehabilitation Trustee using an appropriate method
(b) 再生管財人が、収集した上記(a)の情報を、以下の目的で日本国内外で管理及び利用すること。 The Rehabilitation Trustee may manage and use collected information stated in (a) above for the purposes below in and outside of Japan.
i. 再生債権の届出、調査、再生計画の立案、再生計画に基づく弁済その他の本民事再生手続の適切な遂行 filing proofs of rehabilitation claim, investigations of rehabilitation claims, drafting a rehabilitation plan, distribution in accordance with a rehabilitation plan, or any other appropriate execution of the Civil Rehabilitation Proceedings;
ii. 公益的な目的のためにする、日本国内外の行政官庁・捜査機関・司法機関への上記(a)の情報の開示又は提供 disclosing or providing information stated in (a) above to any government office, any investigation agency, or any judicial agency in or outside of Japan for the purpose of serving public interests; and
iii. その他上記目的に付随する目的 any other purposes incidental to the above purposes.
(c) 再生管財人が、上記(b)の目的のため、上記(a)の情報を、第三者(以下の者を含むが、これらに限られない。)に開示又は提供する場合があること。これらの第三者には、①米国、②カナダ、③イギリス、④私/当社が所在する国及び⑤私/当社が再生債権の弁済の受領のために利用する金融機関又は仮想通貨取引所が所在する国に、それぞれ所在する第三者が含まれること。 The Rehabilitation Trustee may disclose or provide information stated in (a) above for the purpose of (b) above to any third party (including, but not limited to, the persons below). The third parties hereunder include third parties located in (i) the United States of America, (ii) Canada, (iii) the United Kingdom, (iv) the country in which I am/we are located, and (v) the country in which the financial institution or cryptocurrency exchange that I/we use to receive payment for the rehabilitation claim is located.
東京地方裁判所その他裁判所(日本国外の裁判所を含む。)、本民事再生手続及び本破産手続(併せて以下「本民事再生手続等」という。)における調査委員(その代理及び補佐を含む。)その他の機関、日本国内外の行政官庁・捜査機関、管財人が本民事再生手続等の遂行のために依頼する法律事務所及びデロイトトーマツコンサルティング合同会社等の専門家、金融機関、仮想通貨取引所、他の再生債権者、Eメールサービスプロバイダー、及び詐欺行為検証サービスプロバイダー Tokyo District Court and other courts (including courts outside of Japan); the Examiner (chosa iin) (including deputy examiners and assistant examiners) and other officers or bodies in the Civil Rehabilitation Proceedings or the Bankruptcy Proceedings (collectively, the “Civil Rehabilitation Proceedings, Etc.”); government offices and investigation agencies in or outside of Japan; counsel and experts including the law firms and Deloitte Tohmatsu Consulting LLC. which the trustee has retained to proceed with the Civil Rehabilitation Proceedings, Etc.; financial institutions; cryptocurrency exchangers; other rehabilitation creditors; email service providers; and fraudulent act verification service providers
(d) 管財人は、本民事再生手続等に必要な限りで私/当社のブラウザ設定により影響されない特定の永続クッキーを使用する可能性があること。 The trustee might, to the extent necessary for the Civil Rehabilitation Proceedings, Etc., use a specific permanent cookies setting that will be unaffected by my/our browser setting.
24.私/当社の再生債権に関する事項が、オンライン上で他の再生債権者による閲覧の対象となり、また、東京地方裁判所において本民事再生手続の利害関係人の閲覧及び謄写の対象となる場合があること。 The information regarding my/our rehabilitation claim may be available online to other rehabilitation creditors, and may be subject to the inspection and copying thereof at the Tokyo District Court by an interested party in the Civil Rehabilitation Proceedings.
25.私が死亡した場合、本民事再生手続との関係では、再生管財人が、日本の法令等及び実務に従って、相続に関する各種関係資料の提出を求め、また、誰を再生債権者として取り扱うかについて判断すること、及び、当該判断に起因又は関連して生じるあらゆる損害等について、MTGOX及び再生管財人は一切の責任を負わず、私及び私の相続人はMTGOX及び再生管財人に対して当該損害等に関して損害賠償請求、補償請求その他一切の請求をしないこと。 For the purpose of the Civil Rehabilitation Proceedings, in the event that I died, the Rehabilitation Trustee may, in accordance with the Laws and practices of Japan, request for relevant evidence and explanation on the inheritance and determine who to be treated as the rehabilitation creditor; and MTGOX and the Rehabilitation Trustee are not liable in any respect for any Damages arising out of or in connection with such determination, and I and my heir(s)/successor(s) will not make any claim for damages or compensation, or make any other claim with respect to such Damages against MTGOX or the Rehabilitation Trustee.
26.本同意事項は日本語を正文とすること。本同意事項につき作成される英語の翻訳文は参考にすぎず、日本語と英語との間で相互に内容の相違、矛盾がある場合であっても、日本語のみが効力を有すること。 The governing language of these terms of consent shall be the Japanese language. The English-language translation thereof is merely for reference purposes only; and notwithstanding any discrepancy or contradiction in details between the Japanese-language original and the English-language translation the Japanese-language original shall prevail.
  1. 本民事再生手続等及びこれに関連又は付随して生じる一切の請求又は紛争は日本法に準拠し、東京地方裁判所を専属的合意管轄裁判所とすること。 The Civil Rehabilitation Proceedings, Etc. and all claims and disputes arising out of, in connection with, or incidental to, the Civil Rehabilitation Proceedings, Etc. are governed by Japanese law, and the Tokyo District Court shall have exclusive jurisdiction.
  2. 再生管財人が、本同意事項を必要に応じ変更すること。但し、再生管財人が変更についてwww.mtgox.comにおいて告知したものに限る。 The Rehabilitation Trustee will, as necessary, amend these terms of consent. However, amendments are limited to those that the Rehabilitation Trustee has notified on the website www.mtgox.com.
submitted by MadHatter8816 to legaladvice [link] [comments]

Proper Care & Feeding of your CryptoLocker Infection: A rundown on what we know.

This article is no longer being maintained, please see the new version here. Thanks.
tl;dr: I hope you have backups. It's legit, it really encrypts. It can jump across mapped network drives and encrypt anything with write access, and infection isn't dependent on being a local admin or UAC state. Most antiviruses do not catch it until the damage is done. The timer is real and your opportunity to pay them goes away when it lapses. You can pay them with a GreenDot MoneyPak or 2 Bitcoins, attempt to restore a previous version using ShadowExplorer, go to a backup, or be SOL.
Vectors: In order of likelihood, the vectors of infection have been:
  • Email attachments: A commonly reported subject is Payroll Report. The attachment, most of the time, is a zip with a PDF inside, which is actually an executable.
  • PCs that are unwitting members of the Zeus botnet have had the virus pushed to them directly.
  • There is currently one report of an infection through Java, using the .jnlp file as a dropper to load the executable.
Variants: The current variant demands $300 via GreenDot MoneyPak or 2 BTC. I will not attempt to thoroughly monitor the price of bitcoins for this thread, use Mt. Gox for the current exchange rate. Currently the MoneyPak is the cheaper option, but last week Bitcoins were. Two variants, including a $100 variant and a $300 that did not offer Bitcoin, are defunct.
Payload: The virus stores a public RSA 2048-bit key in the local registry, and goes to a C&C server for a private key which is never stored. The technical nuts and bolts have been covered by Fabian from Emsisoft here. It will use a mix of RSA 2048-bit and AES 256-bit encryption on files matching these masks:
*.odt, *.ods, *.odp, *.odm, *.odc, *.odb, *.doc, *.docx, *.docm, *.wps, *.xls, *.xlsx, *.xlsm, *.xlsb, *.xlk, *.ppt, *.pptx, *.pptm, *.mdb, *.accdb, *.pst, *.dwg, *.dxf, *.dxg, *.wpd, *.rtf, *.wb2, *.mdf, *.dbf, *.psd, *.pdd, *.eps, *.ai, *.indd, *.cdr, ????????.jpg, ????????.jpe, img_*.jpg, *.dng, *.3fr, *.arw, *.srf, *.sr2, *.bay, *.crw, *.cr2, *.dcr, *.kdc, *.erf, *.mef, *.mrw, *.nef, *.nrw, *.orf, *.raf, *.raw, *.rwl, *.rw2, *.r3d, *.ptx, *.pef, *.srw, *.x3f, *.der, *.cer, *.crt, *.pem, *.pfx, *.p12, *.p7b, *.p7c, *.pdf, *.tif
This list of file masks may be incomplete. Trust this list at your peril. When in doubt, CryptoLocker will show you what files it has encrypted by clicking the relevant link in the virus's message.
It will access mapped network drives that the current user has write access to and encrypt those. It will not attack server shares, only mapped drives. Current reports are unclear as to how much permission is needed for the virus to encrypt a mapped drive, and if you have clarification or can test in a VM please notify me via message.
By the time the notification pops up, it's already encrypted everything. It's silent until the job is done.
Many antiviruses have been reported as not catching the virus until it's too late, including MSE, Trend Micro WFBS, Eset, GFI Vipre, and Kaspersky. They can further complicate matters by reverting registry changes and removing the executables, leaving the files behind without a public or private key. Releasing the files from quarantine does work, as does releasing the registry keys added and downloading another sample of the virus.
Windows XP through 8 have all reported infections.
What's notable about this virus, and this is going to lead to a lot of tough decisions, is that paying them to decrypt the files actually does work, so long as their C&C server is up. They verify the money transfer manually and then push a notification for the infected machine to call home for the private key again, which it uses to decrypt. It takes a long time to decrypt, at the rate of roughly 5GB/hr based on forum reports. The virus uses the registry to maintain a list of files and paths, so not moving the files around is vital to decryption if you are paying them.
Also notable is that the timer it gives you to pay them does appear to be legitimate, as multiple users have reported that once the timer ran out, the program uninstalled itself. Reinfecting the machine does not bring a new timer. I was not able to verify the uninstallation of the program after the timer ran out, it appears to be dependent on internet access.
Due to the nature of the encryption, brute-forcing a decrypt is essentially impossible for now.
Removal: Removing the virus itself is trivial, but no antivirus product (or any product, for that matter), will be able to decrypt the files until the private key is found.
File Recovery: There are only a handful of options for recovering encrypted files, and they all rely on either having System Restore/VSS turned on or having a backup disconnected from the infected machine. Cloud backup solutions without versioning are no good against this as they will commit the encrypted files to the cloud.
I had a Carbonite employee message me regarding my earlier statement that Carbonite is no good against this virus. It turns out that versioning is included in all Carbonite plans and support all agent OSes except Mac OS X which is outside the scope of this thread anyway. They have the ability to do a mass reversion of files, but you must call tech support and upon mentioning CryptoLocker you will be escalated to a tier 3 tech. They do not mention this ability on the site due to the potential for damage a mass reversion could do if done inadvertently. These are my own findings, independent of what the employee told me. Crashplan and other versioning-based backup solutions such as SonicWALL CDP should also work fine provided the backups are running normally.
Using the "Previous Versions" tab of the file properties is a cheap test, and has had mixed results. Using ShadowExplorer on Vista-8 will give you a much easier graphical frontend for restoring large amounts of files at once (though this will not help with mapped drives, you'd need to run it on the server in that case). Undelete software doesn't work as it encrypts the files in place on the hard drive, there is no copying going on. The big takeaway is that cold-storage backups are good, and they will make this whole process laughably easy to resolve.
Prevention: As this post has attracted many home users, I'll put at the top that MalwareBytes Pro, Avast! Free and Avast! Pro (defs 131016-0 16.10.2013 or later) will prevent the virus from running.
For sysadmins in a domain environment, one way to prevent this and many other viruses is to set up software restriction policies (SRPs) to disallow the executing of .exe files from AppData/Roaming. Grinler explains how to set up the policy here.
Visual example. The rule covering %AppData%\*\*.exe is necessary for the current variant. The SRP will apply to domain admins after either the GP timer hits or a reboot, gpupdate /force does not enforce it immediately. There is almost no collateral damage to the SRP. Dropbox and Chrome are not effected. Spotify may be affected, not sure. I don't use it.
Making shares read-only will mitigate the risk of having sensitive data on the server encrypted.
Forecast: The reports of infections have risen from ~1,300 google results for cryptolocker to over 150,000 in a month. This virus is really ugly, really efficient, and really hard to stop until it's too late. It's also very successful in getting people to pay, which funds the creation of a new variant that plugs what few holes have been found. I don't like where this is headed.
Some edits below are now redundant, but many contain useful information.
9/17 EDIT: All 9/17 edits are now covered under Prevention.
10/10 EDIT: Google matches for CryptoLocker are up 40% in the last week, and I'm getting 5-10 new posts a day on this thread, so I thought I'd update it with some interesting finds from fellow Redditors.
  • soulscore reports that setting the BIOS clock back in time added time to his cryptolocker ransom. Confirmed that the timer extends with the machine offline, but that may be cosmetic and I don't like your chances of this actually helping if your timer runs out on the server side.
  • Spinal33 reports that AV companies are catching up with CryptoLocker and are blocking websites that are spawned in the virus's domain generation algorithm. This effectively means that some people are locked out of the ability to even pay the ransom. (Technically they could, but the virus couldn't call home.)
  • Malwarebytes is claiming that MBAM Pro will catch CryptoLocker. If someone wants to test them on it, be my guest. Confirmed
  • CANT_ARGUE_DAT_LOGIC gave some insight on the method the virus uses when choosing what to infect. It simply goes through folders alphabetically and encrypts all files that match the filemasks towards the top of this post. If you are lucky enough to catch it in the act of encrypting and pull the network connection, the CryptoLocker message will pop up immediately and the countdown will begin. Helpful in determining what will need to be taken into account for decryption.
EDIT 2: We had a customer that ignored our warning email get infected so I will have my hands on an infected PC today, hope to have some useful info to bring back.
10/10 MEGA EDIT: I now have an active CryptoLocker specimen on my bench. I want to run down some things I've found:
  • On WinXP at least, the nested SRP rule is necessary to prevent infection. The path rule needs to be %AppData%\*\*.exe
  • An alternate link to the virus sample is http://gktibioivpqbot.net/1002.exe
  • Once the program runs it spawns two more executables with random names in %userprofile%. Adding a SRP to cover %userprofile%\*.exe may be desired, though this will prevent GoToMyPC from running at a bare minimum.
  • This user was a local administrator, and CryptoLocker was able to encrypt files in other user's directories, though it did not spawn the executables anywhere but the user that triggered the infection. When logged in under a different account there is no indication that a timer is running.
  • The environment has server shares but no mapped drives and the shared data was not touched, even though a desktop shortcut would've taken the virus to a share. I suspect that will be covered in the next iteration.
  • The list of masks above does not appear to be totally complete. PDF files were encrypted and were not originally part of the set of file masks. That is the only exception I noticed, everything else follows the list. Conveniently (/s), CryptoLocker has a button you can click that shows the list of files it's encrypted.
  • The current ransom is $300 by MoneyPak or 2BTC, which at the time of writing would be $280 and change.
  • Fabian reported that registry data is stored at HKCU/Software/CryptoLocker. I cannot glean the meaning of the DWORD values on files but I do notice they are unique, likely salts for the individual files. I'm curious what purpose that would serve if the private key was revealed as the salts would be useless.
  • I have confirmed the message soulscore left that setting the BIOS timer back a few hours adds an equal amount of time. No telling whether that will work once it has a network connection and can see the C&C server, though.
  • The virus walked right through an up-to-date version of GFI Vipre. It appears AV companies either consider the risk too low to update definitions or, more likely, they're having trouble creating heuristic patterns that don't cause a lot of collateral damage.
10/11 EDIT: I ran Daphne on the infected PC to get a better idea of what might be going on. lsass.exe is running like crazy. Computer's had it's CPU pegged all day. I noticed the primary executable running from %AppData% has a switch on the end of the run command, which in my case is /w000000EC. No idea what that means.
10/15 EDIT: I just wanted to thank all the redditors that have submitted information on this. I have some interesting new developments that I'll be editing in full tomorrow.
10/18 EDIT: Hello arstechnica! Please read through comments before posting a question as there's a very good chance it's been answered.
New developments since 10/15:
  • We have confirmation that both Malwarebytes Antimalware Pro and Avast Free and Pro will stop CryptoLocker from running. My personal choice of the two is MBAM Pro but research on your own, AV Comparatives is a wonderful resource.
  • We have reports of a new vector of infection, Java. This is hardly surprising as Zeus was already being transmitted in this fashion, but Maybe_Forged reports contracting the virus with a honeypot VM in this manner.
  • zfs_balla made a hell of a first post on reddit, giving us a lot of insight to the behavior of the decryption process, and answered a frequently-asked question. I'm paraphrasing below.
A file encrypted twice and decrypted once is still garbage.
The waiting for payment confirmation screen stayed up for 16 days before a decryption began, so don't lose hope if it's been up a while.
The DWORD values in the registry have no bearing on decryption. Renaming an encrypted file to one on the list in the registry will decrypt it. However, I would presume this would only work for files that the virus encrypted on that machine as the public key is different with every infection.
Adding any new matching files to somewhere the virus has access will cause them to be encrypted, even at the "waiting for payment confirmation" screen. Be careful.
Hitting "Cancel" on a file that can't be found doesn't cancel the entire decryption, just that file.
EDIT 2: I've rewritten the bulk of this post so people don't have to slog through edits for important information.
10/21 EDIT: Two noteworthy edits. One is regarding Carbonite, which is apparently a viable backup option for this, it is covered under File Recovery. The other is regarding a piece of software called CryptoPrevent. I have not tried it, but according to the developer's website it blocks %localappdata%\*.exe and %localappdata%\*\*.exe which is not necessary for the current variant and will inflict quite a bit of collateral damage. I have no reason right now to doubt the legitimacy of the program, but be aware of the tradeoffs going in.
I'm now at the 15000 character limit. Wat do?
submitted by bluesoul to sysadmin [link] [comments]

History of MTGOX in one minute MtGox USD to BTC e Bitcoins in 1 minute #993 DeFi nicht Bitcoin, OKEx Auszahlungen gestoppt & Mt ... MtGox Bitcoins to BTC e Bitcoins in 50 seconds Roger Ver on MTGOX Bankruptcy and Bitcoin

I have sent 4 deposits totaling 10.88025073 BTC to my account on mtgox. As of right now. Mtgox Address 1: Deposit 1; 27 Confirmations Deposit 2; 11 r/Bitcoin. log in sign up. User account menu. 3. Mt.Gox bitcoins lost? Close. 3. Posted by. u/kungenikarlstad. 6 years ago. Archived. Mt.Gox bitcoins lost? Hi! I'm withdrawing 3.2 bitcoins from MtGox the withdraw is not showing up in blockchain.info. Should i be worried? It's been like 2 hours since i made the request. EDIT. Ok the bitcoins have shown up, 3-4 hours since i made the request ... optional parameters : description : a description for the address , a new description will generate a new address ipn : an URL that will be pinged when this new address receives a transaction, the ping is a POST request with txid, blockid, description . . . as parameters r/Bitcoin. log in sign up. User account menu. 5. How secure is Mt.Gox? Close. 5. Posted by. u/gmiwenht. 6 years ago. Archived. How secure is Mt.Gox? Apparently if I don't keep all my BTC in a cold paper wallet in safe somewhere, then I'm an idiot. But I trade daily, so how the fuck am I supposed to manage my funds? I have amassed a small fortune from trading and I cannot afford to wait for 6 ... The first, and for a long time largest, Bitcoin exchange was MtGox. Founded. in 2010 it was a first stop for many early adopters. With the creation of other. exchanges its monopoly slowly faded ...

[index] [31516] [28935] [11037] [25984] [7760] [6463] [18932] [31160] [48322] [15497]

History of MTGOX in one minute

http://bitcoin-informant.de/2020/10/16/993-defi-nicht-bitcoin-okex-auszahlungen-gestoppt-mt-gox-1-7-milliarden-bitcoin-rueckzahlung Hey Informanten, willkomm... MtGox USD to BTC-e Bitcoins in 1 minute This video shows the transfer of MtGox USD funds via the integrated Bitinstant functions of BTC-Trader to the BTC-e exchange and purchase of Bitcoins on BTC ... MtGox Bitcoins to BTC Bitcoins in 50 seconds BITCOIN PRICE , BITCOIN FUTURE in doubt http://youtu.be/eO-yrpQpIT8 What is NAMECOIN BITCOIN'S First Fork http:/... 6 March 2011 (bitcoin price $0.90) 8 June 2011 (bitcoin price $32) 19 June 2011 (bitcoin price $0.01) 19 Oct 2012 (bitcoin price $11.84) June 20, 2013 (bitcoin price=$111) 7 February 2014 (bitcoin ... 0:55:30 Adam B Levine joins 1:04:50 A Trader's perspective on MtGox and the people who have lost Coins 1:09:38 Keeping your Bitcoins safe with paper wallets 1:52:00 Personal responsibility of the ...

#