What Happened to Mt. Gox? History of the Bitcoin Exchange ...
What Happened to Mt. Gox? History of the Bitcoin Exchange ...
Mt. Gox. Bitcoin Settlement Deadline Pushed to October 2020
Mt. Gox Trustee Transfers 16,000 BTC, BCH To Unknown ...
Who is Behind Historical 180,000 Bitcoin Transfer? MtGox ...
MtGox Trade History Recovery - Bitcoin Taxes
PSA: BitInstant's cash-to-bitcoin-address service is reliable, but they fudge the exchange rate; on top of the stated 3.99% fee (and unstated ZipZap fee), BitInstant has consistently marked up the exchange rate way above ($6 or so) the maximum that MtGox quotes around the time the transfer is made.
This includes any time at which the order was open.
This is a consistent markup from what I've experienced.
Everything that I've read both on and off BitInstant's web site suggests that they use MtGox directly. More to the point, BitInstant doesn't bother telling you what their exchange rate is going to be; it could be set at a markup of $200 for all you know.
UPDATE: Charlie Shrem (bitinstant) ultimately compensated me more than what I thought I was still owed, and for that I thank him; I feel that my personal matter has been satisfied amicably. I still believe that there are strange discrepancies in the data I've seen, which have not yet been accounted for, and I hope Charlie looks into it for the sake of his otherwise valuable company; I wouldn't want BitInstant to be blamed for the errors (or malice) of another party in the pipeline. In any case, I would currently still feel comfortable using BitInstant.
Help, please. Tried to transfer 1.2 Bitcoins to MtGox from BTC-e an hour ago -> worried
Still no confirmations anywhere on this MtGox page. I think they should be shown somewhere, right? I've done this between Bitstamp and BTC-e twice before but this time to Gox I'm really getting worried of what has happened. Last times it took only few minutes to see that my coins are coming ;__; Hopefully I didn't do something wrong!
Seems as though any transfer out request of more than 2 Btc is stuck in MtGox. The coins leave my account but don't enter the Blockchain. Transactions of 2 Btc or under seem to go just fine. As usual MtGox support takes 4 days just to assign someone to assist with my ticket.
What fees are associated with buying bitcoins from MtGox with a bank transfer?
I was looking on the site and it seemed like there were a substantial amount of fees involved with this method. I'm looking to buy about $150 or $200 worth of bitcoins. Is a bank transfer the best way to buy from there?
Last night I transferred all 9 of my Bitcoins out of MtGox to my Blockchain wallet while I decide on a new exchange. They're still not showing up.
Like many of us, I'm dropping MtGox. Their Facebook message just sealed the deal. 8 hours ago I transferred to my Blockchain wallet to keep them I'm a more-or-less lag free zone while I decide what exchange to move to. Even paid the 0.0005 transaction fee. They aren't showing up. You guys have any idea why? Also, I'm up for suggestions for exchanges. Leaning towards Bitfloor since they have moderate volume. Or maybe Bitstamp. Anyways, what do you use? USD by the way... EDIT: Finally was able to log back into MtGox. The funds are still there so the transaction just never occurred... Try again I guess. I would still appreciate exchange suggestions. Edit 2: Succesully transferred to Blockchain. Got all my funds in one easy place now. That being said, I would like to take my wallet offline eventually, perhaps copied to a few flash drives. I just like the liquidity of an online wallet.
Canadian Bitcoiners: Don't Forget About CaVirtex! They are accepting deposits (and have been for the whole while mtgox and tradehill have been down) via Email Money Transfer and will cash out the same way!
It's pretty insane how easy it is to buy bitcoin now.
Just about 4 or 5 years ago buying bitcoin or any crypto requires you to go a really round about ways of buying coins and you get then at least 1 to 2 days. Now all you need is a credit card and you get your coins within an hour
I am a first time buyer overwhelmed with methods of buying in. Any help is appreciated.
Sorry for the mobile formatting. I have been wanting to buy bitcoin for years and have been pushing it off while I procrastinate over where to actually start. I am overly averse to targeted advertising, and am overcautious in trusting random links I find on the general internets. A general indecision from what seems to be a wide range of possibilities in my research also has me trigger shy. Hoping to find some guidance on where to buy my first bit of bitcoin, and who I can trust. I am a Canadian and want to buy a relatively small amount to start (a few hundred CAD), but with periodic purchases to build up my holdings. Planning to hodl until I discover places where I can actually use it nearby. I primarily use apple products, but don’t really even know if I can use software to access or buy mobilly. And before you shit on me for “living under a rock” and being too lazy to research, please understand: it is very overwhelming to us noobs with all of the options, fees structures, regional restrictions, KYC, etc., and different sources come up with new options every time I look. It is pretty unheard of in my area so I don’t even have anyone savvy to talk about it with either. I just want a secure way to buy and hodl and get started. Even if you suggest how much time I should set aside and where I can look for the trusted information. Or a few recommendations that would work for me. I’m just a big mix of eager and cautious and busy but I want to get moving.
The Research States That Crypto Custodians Are Not Entirely Disintermediated And Hold Legal Risks Since its start in 2008, the crypto sector drew the attention of almost everyone in the financial industry – from crypto enthusiasts to legislators. In the context of research on digital assets, conducted as a collaboration between Leiden Law School and Oxford University, Prof. Dr. Matthias Haentjens, Dr. Tycho de Graaf & Ilya Kokorin LLM published a 42-page document. The research paper examines the possible risks behind crypto customers’ involvement with crypto custodians. The researchers noted that in recent years several crypto exchanges shut down operations, including Cryptopia (New Zealand), BitGrail (Italy), and QuadrigaCX (Canada). The team at Leiden Law School also analyzed the legal standpoint behind crypto custodians’ insolvency, like the ownership of Bitcoin, as well as the mechanisms behind transferring ownership, if such exists. Prof. Dr. Matthias Haentjens and his colleagues found out that a large portion of all Bitcoin in circulation is held by crypto custodians, which means the cryptosystem is not entirely disintermediated. Despite offering free-of-charge entry, crypto exchanges often store Bitcoin in a pool, rather than a segregated address. The pooling creates difficulties in tracing the exact path of a given Bitcoin, as well as not clarifying whether the funds are used by someone else. However, the team proposes the prohibition or limitation of such Bitcoin re-usage by eliminating the use of pooled Bitcoin addresses and use of segregated addresses. From a legal standpoint, there is no big difference in the way a crypto custodian stores Bitcoin, whether in pooled or in segregated addresses. Segregated crypto addresses mean the crypto custodian allocates unique wallet addresses and private keys for each user. The lawyers considered that from a property law perspective, Bitcoin ownership can be qualified either absolute or contract-related. The absolute ownership is often referred to as a physical Bitcoin carrier. However, the team proposes the prohibition or limitation of such Bitcoin re-usage. The researchers concluded that it’s hard from a legal point of view for users to put claims for revendication in case of crypto custodian insolvency. However, in the cases of MtGox and BitGrail, such claims were referred to as pari passu with other unsecured claims, as the courts ruled that Bitcoin can’t bear signs of ownership.
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:
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.
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.
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.
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:
Become friends with Jihan Wu, because he owns >51% of the mining hashrate (he totally reorged Bitcoin to reverse the Binance hack right?).
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.
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.
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.
The bartender, pissed at being cheated, takes out a shotgun from under the bar and shoots at you and Jihan Wu.
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.
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.
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!"
I think I got sidetracked here.
Bears are bad news.
You can't reasonably invoke "Satoshi's Vision" and simultaneously reject the Lightning Network because it's not onchain. Satoshi's Vision included a half-assed implementation of payment channels with nSequence, where the onchain transaction represented multiple logical payments, exactly what modern offchain techniques do (except modern offchain techniques actually work). nSequence (the field, but not its modern meaning) has been in Bitcoin since BitCoin For Windows Alpha 0.1.0. And its original intent was payment channels. You can't get nearer to Satoshi's Vision than being a field that Satoshi personally added to transactions on the very first public release of the BitCoin software, like srsly.
Miners can totally bypass mempool rules. In fact, the reason why nSequence has been repurposed to indicate "optional" replace-by-fee is because miners are already incentivized by the nSequence system to always follow replace-by-fee anyway. I mean, what do you think those drinks you passed to Jihan Wu are, other than the fee you pay him to mine a specific version of your transaction?
Satoshi made mistakes. The original design for nSequence is one of them. Today, we no longer use nSequence in this way. So diverging from Satoshi's original design is part and parcel of Bitcoin development, because over time, we learn new lessons that Satoshi never knew about. Satoshi was an important landmark in this technology. He will not be the last, or most important, that we will remember in the future: he will only be the first.
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:
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.
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.
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.
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:
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.
You sign the transaction and pass it to the bartender, who serves your first drink.
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.
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?
Payback's a bitch.
Transaction malleability is a bitchier bitch. It's why we needed to fix the bug in SegWit. Sure, MtGox claimed they were attacked this way because someone kept messing with their transaction signatures and thus they lost track of where their funds went, but really, the bigger impetus for fixing transaction malleability was to support payment channels.
Yes, including the signatures in the hash that ultimately defines the txid was a mistake. Satoshi made a lot of those. So we're just reiterating the lesson "Satoshi was not an infinite being of infinite wisdom" here. Satoshi just gets a pass because of how awesome Bitcoin is.
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:
No time limit.
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):
You have to store all the revocation keys of a channel. This implies you are storing 1 revocation key for every channel update, so if you perform millions of updates over your entire lifetime, you'd be storing several megabytes of keys, for only a single channel. RustyReddit fixed this by requiring that the revocation keys be generated from a "Seed" revocation key, and every key is just the application of SHA256 on that key, repeatedly. For example, suppose I tell you that my first revocation key is SHA256(SHA256(seed)). You can store that in O(1) space. Then for the next revocation, I tell you SHA256(seed). From SHA256(key), you yourself can compute SHA256(SHA256(seed)) (i.e. the previous revocation key). So you can remember just the most recent revocation key, and from there you'd be able to compute every previous revocation key. When you start a channel, you perform SHA256 on your seed for several million times, then use the result as the first revocation key, removing one layer of SHA256 for every revocation key you need to generate. RustyReddit not only came up with this, but also suggested an efficient O(log n) storage structure, the shachain, so that you can quickly look up any revocation key in the past in case of a breach. People no longer really talk about this O(n) revocation storage problem anymore because it was solved very very well by this mechanism.
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?
We can decentralize if we try hard enough!
"Hubs bad" can be made "hubs good" if everybody is a hub.
Smart people can solve problems. It's kinda why they're smart.
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?
Bitcoin offchain scaling is more powerful than you ever thought.
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 事件番号 平成２９年（再）第３５号 / 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.
The total amount of Bitcoins lost in the hack by customers is 850,000 bitcoins ($7.86 billion at the current price). Hence, there is a prolonging disagreement among the customers related to the amount and kind (bank transfer or BTC) of transfer of the approx $2 billion left in the hands of the Trustee. The Mt. Gox Trustee has consolidated over $150 million worth of Bitcoin and Bitcoin Cash to certain addresses. Now, there’s a bit of a panic in the cryptocurrency market that a massive selloff might be coming. Historically, whenever this has happened, it has led to a drop in Bitcoin price. With eyes of the world on Dorian Nakamoto and the uncovering of who is the real Satoshi Nakamoto behind bitcoin, a massive 180,000 bitcoin transfer (around $115 million) took place earlier today. The transfer was a combination of transactions from five different addresses to one single destination. While any large transaction will always draw interest, … An early breach in June 2011 occurred in which a hacker used a compromised Mt. Gox computer to transfer Bitcoin to himself, causing a flash crash of the price from $32 to one cent. A few months later, a number of suspicious transactions occurred, sending 2,609 BTC to invalid addresses, rendering them forever lost. Please be aware that due to errors in MtGox's own reporting, some of the trades in their report are corrupt. This is due to how they internally transferred Bitcoins between pools used for different fiat currencies. When a transfer happens, their internal system might purchase BTC from one pool and sell it to another. For example, if you were ...
In this video tutorial we'll create a new bitcoin wallet with Electrum and then send some bitcoins to it from MtGox. Investing in cryptocurrency 2018 and beyond is a sound investment, but what happens when the market is manipulated by those with large amounts of coins. Find out what happened what might happen to ... MtGox redeemable coupon codes no longer work! But Bitinstant developed a new method for transferring MtGox USD to other Bitcoin exchanges. Watch in this video how to transfer MtGox USD funds from ... 3. Transferring 23.23 USD from MtGox to BTC-e via Bitinstant (1.49% fee). 4. Receiving 22.89 USD on BTC-e Bitcoin exchange. 5. Buying new Bitcoins for a price of 11.40 USD/BTC getting 2.0037 BTC ... 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 ...