What is the Next Bitcoin? 2020’s Most Promising ...
The Bitcoin Halving is Over: What's Next? Finance Magnates
Brian Tockey: Bitcoin, Regression Theorem, and Defining ...
Top Binance Trader Thinks This Comes Next for the Bitcoin ...
Top Binance Trader Thinks This Comes Next for the Bitcoin ...
Bob The Magic Custodian
Summary: Everyone knows that when you give your assets to someone else, they always keep them safe. If this is true for individuals, it is certainly true for businesses. Custodians always tell the truth and manage funds properly. They won't have any interest in taking the assets as an exchange operator would. Auditors tell the truth and can't be misled. That's because organizations that are regulated are incapable of lying and don't make mistakes. First, some background. Here is a summary of how custodians make us more secure: Previously, we might give Alice our crypto assets to hold. There were risks:
Alice might take the assets and disappear.
Alice might spend the assets and pretend that she still has them (fractional model).
Alice might store the assets insecurely and they'll get stolen.
Alice might give the assets to someone else by mistake or by force.
Alice might lose access to the assets.
But "no worries", Alice has a custodian named Bob. Bob is dressed in a nice suit. He knows some politicians. And he drives a Porsche. "So you have nothing to worry about!". And look at all the benefits we get:
Alice can't take the assets and disappear (unless she asks Bob or never gives them to Bob).
Alice can't spend the assets and pretend that she still has them. (Unless she didn't give them to Bob or asks him for them.)
Alice can't store the assets insecurely so they get stolen. (After all - she doesn't have any control over the withdrawal process from any of Bob's systems, right?)
Alice can't give the assets to someone else by mistake or by force. (Bob will stop her, right Bob?)
Alice can't lose access to the funds. (She'll always be present, sane, and remember all secrets, right?)
See - all problems are solved! All we have to worry about now is:
Bob might take the assets and disappear.
Bob might spend the assets and pretend that he still has them (fractional model).
Bob might store the assets insecurely and they'll get stolen.
Bob might give the assets to someone else by mistake or by force.
Bob might lose access to the assets.
It's pretty simple. Before we had to trust Alice. Now we only have to trust Alice, Bob, and all the ways in which they communicate. Just think of how much more secure we are! "On top of that", Bob assures us, "we're using a special wallet structure". Bob shows Alice a diagram. "We've broken the balance up and store it in lots of smaller wallets. That way", he assures her, "a thief can't take it all at once". And he points to a historic case where a large sum was taken "because it was stored in a single wallet... how stupid". "Very early on, we used to have all the crypto in one wallet", he said, "and then one Christmas a hacker came and took it all. We call him the Grinch. Now we individually wrap each crypto and stick it under a binary search tree. The Grinch has never been back since." "As well", Bob continues, "even if someone were to get in, we've got insurance. It covers all thefts and even coercion, collusion, and misplaced keys - only subject to the policy terms and conditions." And with that, he pulls out a phone-book sized contract and slams it on the desk with a thud. "Yep", he continues, "we're paying top dollar for one of the best policies in the country!" "Can I read it?' Alice asks. "Sure," Bob says, "just as soon as our legal team is done with it. They're almost through the first chapter." He pauses, then continues. "And can you believe that sales guy Mike? He has the same year Porsche as me. I mean, what are the odds?" "Do you use multi-sig?", Alice asks. "Absolutely!" Bob replies. "All our engineers are fully trained in multi-sig. Whenever we want to set up a new wallet, we generate 2 separate keys in an air-gapped process and store them in this proprietary system here. Look, it even requires the biometric signature from one of our team members to initiate any withdrawal." He demonstrates by pressing his thumb into the display. "We use a third-party cloud validation API to match the thumbprint and authorize each withdrawal. The keys are also backed up daily to an off-site third-party." "Wow that's really impressive," Alice says, "but what if we need access for a withdrawal outside of office hours?" "Well that's no issue", Bob says, "just send us an email, call, or text message and we always have someone on staff to help out. Just another part of our strong commitment to all our customers!" "What about Proof of Reserve?", Alice asks. "Of course", Bob replies, "though rather than publish any blockchain addresses or signed transaction, for privacy we just do a SHA256 refactoring of the inverse hash modulus for each UTXO nonce and combine the smart contract coefficient consensus in our hyperledger lightning node. But it's really simple to use." He pushes a button and a large green checkmark appears on a screen. "See - the algorithm ran through and reserves are proven." "Wow", Alice says, "you really know your stuff! And that is easy to use! What about fiat balances?" "Yeah, we have an auditor too", Bob replies, "Been using him for a long time so we have quite a strong relationship going! We have special books we give him every year and he's very efficient! Checks the fiat, crypto, and everything all at once!" "We used to have a nice offline multi-sig setup we've been using without issue for the past 5 years, but I think we'll move all our funds over to your facility," Alice says. "Awesome", Bob replies, "Thanks so much! This is perfect timing too - my Porsche got a dent on it this morning. We have the paperwork right over here." "Great!", Alice replies. And with that, Alice gets out her pen and Bob gets the contract. "Don't worry", he says, "you can take your crypto-assets back anytime you like - just subject to our cancellation policy. Our annual management fees are also super low and we don't adjust them often". How many holes have to exist for your funds to get stolen? Just one. Why are we taking a powerful offline multi-sig setup, widely used globally in hundreds of different/lacking regulatory environments with 0 breaches to date, and circumventing it by a demonstrably weak third party layer? And paying a great expense to do so? If you go through the list of breaches in the past 2 years to highly credible organizations, you go through the list of major corporate frauds (only the ones we know about), you go through the list of all the times platforms have lost funds, you go through the list of times and ways that people have lost their crypto from identity theft, hot wallet exploits, extortion, etc... and then you go through this custodian with a fine-tooth comb and truly believe they have value to add far beyond what you could, sticking your funds in a wallet (or set of wallets) they control exclusively is the absolute worst possible way to take advantage of that security. The best way to add security for crypto-assets is to make a stronger multi-sig. With one custodian, what you are doing is giving them your cryptocurrency and hoping they're honest, competent, and flawlessly secure. It's no different than storing it on a really secure exchange. Maybe the insurance will cover you. Didn't work for Bitpay in 2015. Didn't work for Yapizon in 2017. Insurance has never paid a claim in the entire history of cryptocurrency. But maybe you'll get lucky. Maybe your exact scenario will buck the trend and be what they're willing to cover. After the large deductible and hopefully without a long and expensive court battle. And you want to advertise this increase in risk, the lapse of judgement, an accident waiting to happen, as though it's some kind of benefit to customers ("Free institutional-grade storage for your digital assets.")? And then some people are writing to the OSC that custodians should be mandatory for all funds on every exchange platform? That this somehow will make Canadians as a whole more secure or better protected compared with standard air-gapped multi-sig? On what planet? Most of the problems in Canada stemmed from one thing - a lack of transparency. If Canadians had known what a joke Quadriga was - it wouldn't have grown to lose $400m from hard-working Canadians from coast to coast to coast. And Gerald Cotten would be in jail, not wherever he is now (at best, rotting peacefully). EZ-BTC and mister Dave Smilie would have been a tiny little scam to his friends, not a multi-million dollar fraud. Einstein would have got their act together or been shut down BEFORE losing millions and millions more in people's funds generously donated to criminals. MapleChange wouldn't have even been a thing. And maybe we'd know a little more about CoinTradeNewNote - like how much was lost in there. Almost all of the major losses with cryptocurrency exchanges involve deception with unbacked funds. So it's great to see transparency reports from BitBuy and ShakePay where someone independently verified the backing. The only thing we don't have is:
ANY CERTAINTY BALANCES WEREN'T EXCLUDED. Quadriga's largest account was $70m. 80% of funds are in 20% of accounts (Pareto principle). All it takes is excluding a few really large accounts - and nobody's the wiser. A fractional platform can easily pass any audit this way.
ANY VISIBILITY WHATSOEVER INTO THE CUSTODIANS. BitBuy put out their report before moving all the funds to their custodian and ShakePay apparently can't even tell us who the custodian is. That's pretty important considering that basically all of the funds are now stored there.
ANY IDEA ABOUT THE OTHER EXCHANGES. In order for this to be effective, it has to be the norm. It needs to be "unusual" not to know. If obscurity is the norm, then it's super easy for people like Gerald Cotten and Dave Smilie to blend right in.
It's not complicated to validate cryptocurrency assets. They need to exist, they need to be spendable, and they need to cover the total balances. There are plenty of credible people and firms across the country that have the capacity to reasonably perform this validation. Having more frequent checks by different, independent, parties who publish transparent reports is far more valuable than an annual check by a single "more credible/official" party who does the exact same basic checks and may or may not publish anything. Here's an example set of requirements that could be mandated:
First report within 1 month of launching, another within 3 months, and further reports at minimum every 6 months thereafter.
No auditor can be repeated within a 12 month period.
All reports must be public, identifying the auditor and the full methodology used.
All auditors must be independent of the firm being audited with no conflict of interest.
Reports must include the percentage of each asset backed, and how it's backed.
The auditor publishes a hash list, which lists a hash of each customer's information and balances that were included. Hash is one-way encryption so privacy is fully preserved. Every customer can use this to have 100% confidence they were included.
If we want more extensive requirements on audits, these should scale upward based on the total assets at risk on the platform, and whether the platform has loaned their assets out.
There are ways to structure audits such that neither crypto assets nor customer information are ever put at risk, and both can still be properly validated and publicly verifiable. There are also ways to structure audits such that they are completely reasonable for small platforms and don't inhibit innovation in any way. By making the process as reasonable as possible, we can completely eliminate any reason/excuse that an honest platform would have for not being audited. That is arguable far more important than any incremental improvement we might get from mandating "the best of the best" accountants. Right now we have nothing mandated and tons of Canadians using offshore exchanges with no oversight whatsoever. Transparency does not prove crypto assets are safe. CoinTradeNewNote, Flexcoin ($600k), and Canadian Bitcoins ($100k) are examples where crypto-assets were breached from platforms in Canada. All of them were online wallets and used no multi-sig as far as any records show. This is consistent with what we see globally - air-gapped multi-sig wallets have an impeccable record, while other schemes tend to suffer breach after breach. We don't actually know how much CoinTrader lost because there was no visibility. Rather than publishing details of what happened, the co-founder of CoinTrader silently moved on to found another platform - the "most trusted way to buy and sell crypto" - a site that has no information whatsoever (that I could find) on the storage practices and a FAQ advising that “[t]rading cryptocurrency is completely safe” and that having your own wallet is “entirely up to you! You can certainly keep cryptocurrency, or fiat, or both, on the app.” Doesn't sound like much was learned here, which is really sad to see. It's not that complicated or unreasonable to set up a proper hardware wallet. Multi-sig can be learned in a single course. Something the equivalent complexity of a driver's license test could prevent all the cold storage exploits we've seen to date - even globally. Platform operators have a key advantage in detecting and preventing fraud - they know their customers far better than any custodian ever would. The best job that custodians can do is to find high integrity individuals and train them to form even better wallet signatories. Rather than mandating that all platforms expose themselves to arbitrary third party risks, regulations should center around ensuring that all signatories are background-checked, properly trained, and using proper procedures. We also need to make sure that signatories are empowered with rights and responsibilities to reject and report fraud. They need to know that they can safely challenge and delay a transaction - even if it turns out they made a mistake. We need to have an environment where mistakes are brought to the surface and dealt with. Not one where firms and people feel the need to hide what happened. In addition to a knowledge-based test, an auditor can privately interview each signatory to make sure they're not in coercive situations, and we should make sure they can freely and anonymously report any issues without threat of retaliation. A proper multi-sig has each signature held by a separate person and is governed by policies and mutual decisions instead of a hierarchy. It includes at least one redundant signature. For best results, 3of4, 3of5, 3of6, 4of5, 4of6, 4of7, 5of6, or 5of7. History has demonstrated over and over again the risk of hot wallets even to highly credible organizations. Nonetheless, many platforms have hot wallets for convenience. While such losses are generally compensated by platforms without issue (for example Poloniex, Bitstamp, Bitfinex, Gatecoin, Coincheck, Bithumb, Zaif, CoinBene, Binance, Bitrue, Bitpoint, Upbit, VinDAX, and now KuCoin), the public tends to focus more on cases that didn't end well. Regardless of what systems are employed, there is always some level of risk. For that reason, most members of the public would prefer to see third party insurance. Rather than trying to convince third party profit-seekers to provide comprehensive insurance and then relying on an expensive and slow legal system to enforce against whatever legal loopholes they manage to find each and every time something goes wrong, insurance could be run through multiple exchange operators and regulators, with the shared interest of having a reputable industry, keeping costs down, and taking care of Canadians. For example, a 4 of 7 multi-sig insurance fund held between 5 independent exchange operators and 2 regulatory bodies. All Canadian exchanges could pay premiums at a set rate based on their needed coverage, with a higher price paid for hot wallet coverage (anything not an air-gapped multi-sig cold wallet). Such a model would be much cheaper to manage, offer better coverage, and be much more reliable to payout when needed. The kind of coverage you could have under this model is unheard of. You could even create something like the CDIC to protect Canadians who get their trading accounts hacked if they can sufficiently prove the loss is legitimate. In cases of fraud, gross negligence, or insolvency, the fund can be used to pay affected users directly (utilizing the last transparent balance report in the worst case), something which private insurance would never touch. While it's recommended to have official policies for coverage, a model where members vote would fully cover edge cases. (Could be similar to the Supreme Court where justices vote based on case law.) Such a model could fully protect all Canadians across all platforms. You can have a fiat coverage governed by legal agreements, and crypto-asset coverage governed by both multi-sig and legal agreements. It could be practical, affordable, and inclusive. Now, we are at a crossroads. We can happily give up our freedom, our innovation, and our money. We can pay hefty expenses to auditors, lawyers, and regulators year after year (and make no mistake - this cost will grow to many millions or even billions as the industry grows - and it will be borne by all Canadians on every platform because platforms are not going to eat up these costs at a loss). We can make it nearly impossible for any new platform to enter the marketplace, forcing Canadians to use the same stagnant platforms year after year. We can centralize and consolidate the entire industry into 2 or 3 big players and have everyone else fail (possibly to heavy losses of users of those platforms). And when a flawed security model doesn't work and gets breached, we can make it even more complicated with even more people in suits making big money doing the job that blockchain was supposed to do in the first place. We can build a system which is so intertwined and dependent on big government, traditional finance, and central bankers that it's future depends entirely on that of the fiat system, of fractional banking, and of government bail-outs. If we choose this path, as history has shown us over and over again, we can not go back, save for revolution. Our children and grandchildren will still be paying the consequences of what we decided today. Or, we can find solutions that work. We can maintain an open and innovative environment while making the adjustments we need to make to fully protect Canadian investors and cryptocurrency users, giving easy and affordable access to cryptocurrency for all Canadians on the platform of their choice, and creating an environment in which entrepreneurs and problem solvers can bring those solutions forward easily. None of the above precludes innovation in any way, or adds any unreasonable cost - and these three policies would demonstrably eliminate or resolve all 109 historic cases as studied here - that's every single case researched so far going back to 2011. It includes every loss that was studied so far not just in Canada but globally as well. Unfortunately, finding answers is the least challenging part. Far more challenging is to get platform operators and regulators to agree on anything. My last post got no response whatsoever, and while the OSC has told me they're happy for industry feedback, I believe my opinion alone is fairly meaningless. This takes the whole community working together to solve. So please let me know your thoughts. Please take the time to upvote and share this with people. Please - let's get this solved and not leave it up to other people to do. Facts/background/sources (skip if you like):
The inspiration for the paragraph about splitting wallets was an actual quote from a Canadian company providing custodial services in response to the OSC consultation paper: "We believe that it will be in the in best interests of investors to prohibit pooled crypto assets or ‘floats’. Most Platforms pool assets, citing reasons of practicality and expense. The recent hack of the world’s largest Platform – Binance – demonstrates the vulnerability of participants’ assets when such concessions are made. In this instance, the Platform’s entire hot wallet of Bitcoins, worth over $40 million, was stolen, facilitated in part by the pooling of client crypto assets." "the maintenance of participants (and Platform) crypto assets across multiple wallets distributes the related risk and responsibility of security - reducing the amount of insurance coverage required and making insurance coverage more readily obtainable". For the record, their reply also said nothing whatsoever about multi-sig or offline storage.
In addition to the fact that the $40m hack represented only one "hot wallet" of Binance, and they actually had the vast majority of assets in other wallets (including mostly cold wallets), multiple real cases have clearly demonstrated that risk is still present with multiple wallets. Bitfinex, VinDAX, Bithumb, Altsbit, BitPoint, Cryptopia, and just recently KuCoin all had multiple wallets breached all at the same time, and may represent a significantly larger impact on customers than the Binance breach which was fully covered by Binance. To represent that simply having multiple separate wallets under the same security scheme is a comprehensive way to reduce risk is just not true.
Private insurance has historically never covered a single loss in the cryptocurrency space (at least, not one that I was able to find), and there are notable cases where massive losses were not covered by insurance. Bitpay in 2015 and Yapizon in 2017 both had insurance policies that didn't pay out during the breach, even after a lengthly court process. The same insurance that ShakePay is presently using (and announced to much fanfare) was describe by their CEO himself as covering “physical theft of the media where the private keys are held,” which is something that has never historically happened. As was said with regard to the same policy in 2018 - “I don’t find it surprising that Lloyd’s is in this space,” said Johnson, adding that to his mind the challenge for everybody is figuring out how to structure these policies so that they are actually protective. “You can create an insurance policy that protects no one – you know there are so many caveats to the policy that it’s not super protective.”
The most profitable policy for a private insurance company is one with the most expensive premiums that they never have to pay a claim on. They have no inherent incentive to take care of people who lost funds. It's "cheaper" to take the reputational hit and fight the claim in court. The more money at stake, the more the insurance provider is incentivized to avoid payout. They're not going to insure the assets unless they have reasonable certainty to make a profit by doing so, and they're not going to pay out a massive sum unless it's legally forced. Private insurance is always structured to be maximally profitable to the insurance provider.
The circumvention of multi-sig was a key factor in the massive Bitfinex hack of over $60m of bitcoin, which today still sits being slowly used and is worth over $3b. While Bitfinex used a qualified custodian Bitgo, which was and still is active and one of the industry leaders of custodians, and they set up 2 of 3 multi-sig wallets, the entire system was routed through Bitfinex, such that Bitfinex customers could initiate the withdrawals in a "hot" fashion. This feature was also a hit with the hacker. The multi-sig was fully circumvented.
Bitpay in 2015 was another example of a breach that stole 5,000 bitcoins. This happened not through the exploit of any system in Bitpay, but because the CEO of a company they worked with got their computer hacked and the hackers were able to request multiple bitcoin purchases, which Bitpay honoured because they came from the customer's computer legitimately. Impersonation is a very common tactic used by fraudsters, and methods get more extreme all the time.
A notable case in Canada was the Canadian Bitcoins exploit. Funds were stored on a server in a Rogers Data Center, and the attendee was successfully convinced to reboot the server "in safe mode" with a simple phone call, thus bypassing the extensive security and enabling the theft.
The very nature of custodians circumvents multi-sig. This is because custodians are not just having to secure the assets against some sort of physical breach but against any form of social engineering, modification of orders, fraudulent withdrawal attempts, etc... If the security practices of signatories in a multi-sig arrangement are such that the breach risk of one signatory is 1 in 100, the requirement of 3 independent signatures makes the risk of theft 1 in 1,000,000. Since hackers tend to exploit the weakest link, a comparable custodian has to make the entry and exit points of their platform 10,000 times more secure than one of those signatories to provide equivalent protection. And if the signatories beef up their security by only 10x, the risk is now 1 in 1,000,000,000. The custodian has to be 1,000,000 times more secure. The larger and more complex a system is, the more potential vulnerabilities exist in it, and the fewer people can understand how the system works when performing upgrades. Even if a system is completely secure today, one has to also consider how that system might evolve over time or work with different members.
By contrast, offline multi-signature solutions have an extremely solid record, and in the entire history of cryptocurrency exchange incidents which I've studied (listed here), there has only been one incident (796 exchange in 2015) involving an offline multi-signature wallet. It happened because the customer's bitcoin address was modified by hackers, and the amount that was stolen ($230k) was immediately covered by the exchange operators. Basically, the platform operators were tricked into sending a legitimate withdrawal request to the wrong address because hackers exploited their platform to change that address. Such an issue would not be prevented in any way by the use of a custodian, as that custodian has no oversight whatsoever to the exchange platform. It's practical for all exchange operators to test large withdrawal transactions as a general policy, regardless of what model is used, and general best practice is to diagnose and fix such an exploit as soon as it occurs.
False promises on the backing of funds played a huge role in the downfall of Quadriga, and it's been exposed over and over again (MyCoin, PlusToken, Bitsane, Bitmarket, EZBTC, IDAX). Even today, customers have extremely limited certainty on whether their funds in exchanges are actually being backed or how they're being backed. While this issue is not unique to cryptocurrency exchanges, the complexity of the technology and the lack of any regulation or standards makes problems more widespread, and there is no "central bank" to come to the rescue as in the 2008 financial crisis or during the great depression when "9,000 banks failed".
In addition to fraudulent operations, the industry is full of cases where operators have suffered breaches and not reported them. Most recently, Einstein was the largest case in Canada, where ongoing breaches and fraud were perpetrated against the platform for multiple years and nobody found out until the platform collapsed completely. While fraud and breaches suck to deal with, they suck even more when not dealt with. Lack of visibility played a role in the largest downfalls of Mt. Gox, Cryptsy, and Bitgrail. In some cases, platforms are alleged to have suffered a hack and keep operating without admitting it at all, such as CoinBene.
It surprises some to learn that a cryptographic solution has already existed since 2013, and gained widespread support in 2014 after Mt. Gox. Proof of Reserves is a full cryptographic proof that allows any customer using an exchange to have complete certainty that their crypto-assets are fully backed by the platform in real-time. This is accomplished by proving that assets exist on the blockchain, are spendable, and fully cover customer deposits. It does not prove safety of assets or backing of fiat assets.
If we didn't care about privacy at all, a platform could publish their wallet addresses, sign a partial transaction, and put the full list of customer information and balances out publicly. Customers can each check that they are on the list, that the balances are accurate, that the total adds up, and that it's backed and spendable on the blockchain. Platforms who exclude any customer take a risk because that customer can easily check and see they were excluded. So together with all customers checking, this forms a full proof of backing of all crypto assets.
However, obviously customers care about their private information being published. Therefore, a hash of the information can be provided instead. Hash is one-way encryption. The hash allows the customer to validate inclusion (by hashing their own known information), while anyone looking at the list of hashes cannot determine the private information of any other user. All other parts of the scheme remain fully intact. A model like this is in use on the exchange CoinFloor in the UK.
A Merkle tree can provide even greater privacy. Instead of a list of balances, the balances are arranged into a binary tree. A customer starts from their node, and works their way to the top of the tree. For example, they know they have 5 BTC, they plus 1 other customer hold 7 BTC, they plus 2-3 other customers hold 17 BTC, etc... until they reach the root where all the BTC are represented. Thus, there is no way to find the balances of other individual customers aside from one unidentified customer in this case.
Proposals such as this had the backing of leaders in the community including Nic Carter, Greg Maxwell, and Zak Wilcox. Substantial and significant effort started back in 2013, with massive popularity in 2014. But what became of that effort? Very little. Exchange operators continue to refuse to give visibility. Despite the fact this information can often be obtained through trivial blockchain analysis, no Canadian platform has ever provided any wallet addresses publicly. As described by the CEO of Newton "For us to implement some kind of realtime Proof of Reserves solution, which I'm not opposed to, it would have to ... Preserve our users' privacy, as well as our own. Some kind of zero-knowledge proof". Kraken describes here in more detail why they haven't implemented such a scheme. According to professor Eli Ben-Sasson, when he spoke with exchanges, none were interested in implementing Proof of Reserves.
And yet, Kraken's places their reasoning on a page called "Proof of Reserves". More recently, both BitBuy and ShakePay have released reports titled "Proof of Reserves and Security Audit". Both reports contain disclaimers against being audits. Both reports trust the customer list provided by the platform, leaving the open possibility that multiple large accounts could have been excluded from the process. Proof of Reserves is a blockchain validation where customers see the wallets on the blockchain. The report from Kraken is 5 years old, but they leave it described as though it was just done a few weeks ago. And look at what they expect customers to do for validation. When firms represent something being "Proof of Reserve" when it's not, this is like a farmer growing fruit with pesticides and selling it in a farmers market as organic produce - except that these are people's hard-earned life savings at risk here. Platforms are misrepresenting the level of visibility in place and deceiving the public by their misuse of this term. They haven't proven anything.
Fraud isn't a problem that is unique to cryptocurrency. Fraud happens all the time. Enron, WorldCom, Nortel, Bear Stearns, Wells Fargo, Moser Baer, Wirecard, Bre-X, and Nicola are just some of the cases where frauds became large enough to become a big deal (and there are so many countless others). These all happened on 100% reversible assets despite regulations being in place. In many of these cases, the problems happened due to the over-complexity of the financial instruments. For example, Enron had "complex financial statements [which] were confusing to shareholders and analysts", creating "off-balance-sheet vehicles, complex financing structures, and deals so bewildering that few people could understand them". In cryptocurrency, we are often combining complex financial products with complex technologies and verification processes. We are naïve if we think problems like this won't happen. It is awkward and uncomfortable for many people to admit that they don't know how something works. If we want "money of the people" to work, the solutions have to be simple enough that "the people" can understand them, not so confusing that financial professionals and technology experts struggle to use or understand them.
For those who question the extent to which an organization can fool their way into a security consultancy role, HB Gary should be a great example to look at. Prior to trying to out anonymous, HB Gary was being actively hired by multiple US government agencies and others in the private sector (with glowing testimonials). The published articles and hosted professional security conferences. One should also look at this list of data breaches from the past 2 years. Many of them are large corporations, government entities, and technology companies. These are the ones we know about. Undoubtedly, there are many more that we do not know about. If HB Gary hadn't been "outted" by anonymous, would we have known they were insecure? If the same breach had happened outside of the public spotlight, would it even have been reported? Or would HB Gary have just deleted the Twitter posts, brought their site back up, done a couple patches, and kept on operating as though nothing had happened?
In the case of Quadriga, the facts are clear. Despite past experience with platforms such as MapleChange in Canada and others around the world, no guidance or even the most basic of a framework was put in place by regulators. By not clarifying any sort of legal framework, regulators enabled a situation where a platform could be run by former criminal Mike Dhanini/Omar Patryn, and where funds could be held fully unchecked by one person. At the same time, the lack of regulation deterred legitimate entities from running competing platforms and Quadriga was granted a money services business license for multiple years of operation, which gave the firm the appearance of legitimacy. Regulators did little to protect Canadians despite Quadriga failing to file taxes from 2016 onward. The entire administrative team had resigned and this was public knowledge. Many people had suspicions of what was going on, including Ryan Mueller, who forwarded complaints to the authorities. These were ignored, giving Gerald Cotten the opportunity to escape without justice.
There are multiple issues with the SOC II model including the prohibitive cost (you have to find a third party accounting firm and the prices are not even listed publicly on any sites), the requirement of operating for a year (impossible for new platforms), and lack of any public visibility (SOC II are private reports that aren't shared outside the people in suits).
Securities frameworks are expensive. Sarbanes-Oxley is estimated to cost $5.1 million USD/yr for the average Fortune 500 company in the United States. Since "Fortune 500" represents the top 500 companies, that means well over $2.55 billion USD (~$3.4 billion CAD) is going to people in suits. Isn't the problem of trust and verification the exact problem that the blockchain is supposed to solve?
To use Quadriga as justification for why custodians or SOC II or other advanced schemes are needed for platforms is rather silly, when any framework or visibility at all, or even the most basic of storage policies, would have prevented the whole thing. It's just an embarrassment.
We are now seeing regulators take strong action. CoinSquare in Canada with multi-million dollar fines. BitMex from the US, criminal charges and arrests. OkEx, with full disregard of withdrawals and no communication. Who's next?
We have a unique window today where we can solve these problems, and not permanently destroy innovation with unreasonable expectations, but we need to act quickly. This is a unique historic time that will never come again.
This is the problem with the crypto community. Many only get excited and interested when they see a major pump. OXTBETS seemed very active and interest peaked in late August. Then, the terrible month of September ensued (which I predicted btw, not to toot my own horn) and now Orchid's level of interest is back to the days of June and July. In the terrible words of scholarly rapper, Future: "Molly, Percocets, Rep the set, Gotta rep the set, Chase a check, Never chase a bitch." NEVER CHASE A CRYPTO or you will be doomed. (Btw Future was basically advertising street drugs which makes that a terrible song). Everyone should watch this video by Tommy World Power: (0:48) "imagining if someone put $100 in cryptocurrency or BTC in 2009, that in 2013, that $100 would become worth $100 million. Thinking about how people go to work everyday and they have these routines...and if they could put just $100 which is possible for most people in the Western world..." I can admit that I was sleeping on crypto throughout this decade. I first heard about Bitcoin in 2013 and dismissed it as some illegal black market money laundering scheme. And in a way with Mt. Gox, it was like that. Then came the more traditional exchanges like Binance and Coinbase which helped legitimize this asset class. (1:37) "I watched Bitcoin go from $10 to $1000 in 2013." Didn't we all? (1:50) "I actually made first major investments in Bitcoin and cryptocurrency at the end of 2013, at the end of that bubble...that next year is something we NEVER saw in cryptocurrency before.... My losses on some of them were 90%... Accumulate as much possible at those lows because I knew at some point, it would rebound." Basically, he was referring to how everyone forgot about crypto in 2015 including all his friends and how it came roaring back to reward the loyal crypto holders. Don't chase crypto gains but don't also sleep on crypto. https://www.youtube.com/watch?v=qhfbIGuSBxY
I applied price discovery algorithms to 5 Min OHLCV data from Bitmex and CME contracts and Bitstamp, Coinbase, HitBTC, Kraken, Poloniex, Binance, and OkEx BTCUSD/BTCUSDT markets from March 2016 to May 2020. Some exciting results I got was:
Before the 2017/18 bull run, Bitfinex dominated the price discovery process. They started the run. But as the price increased, trades on other exchanges, Binance and Bitstamp played a more dominant role in leading the price up.
Since then, CME Contracts and Bitmex contracts have had an increasing role in price discovery. Today Bitmex and CME Contracts play the most substantial role in determining the direction of Bitcoin price.
In 2020, market dominance by Bitmex has been negatively correlated with price. Dominance by Bitfinex, Huobi and OkCoin has had high positive correlation with price.
Price discovery is the overall process of setting the price of an asset. Price discovery algorithms identify the leader exchanges whose traders define the price. Two approaches are most famous for use in Price Discovery. Gonzalo and Granger (1995) and Hasbrouck (1995). But they assume random walk, and a common efficient price. I do not feel comfortable assuming random walk and common efficient price in Bitcoin Markets. So I used this little know method by De Blasis (2019) for this analysis. This work assumes that "the fastest price to reflect new information releases a price signal to the other slower price series." I thought this was valid in our market. It uses Markov Chains to measure Price Discovery. Without going into the mathematical details the summary steps used was:
Data is first grouped into a daily interval. Then inside each daily interval's 5-minute candles, the change in prices between the current time t and previous time t-1 is calculated. The difference across the same time t across all exchanges in a given day is juxtaposed to create an initial matrix.
The initial matrix is used to create a Transition Matrix, which measures the probability of price changing to something else at time t+1 for its state at t.
Then other Markov Chain based algorithms are used to measure the influence an exchange at time t had over all other exchanges' price movement at time t+1 individually.
Reduction and normalization is done to this data. In the end, each exchange receives a single number that sums to 1 for a given day.
De Blasis (2019) names this number Price Leadership Share (PLS). High PLS indicates a large role in price discovery. As the sum of the numbers is 1, they can be looked at as a percentage contribution. I recommend reading the original paper if you are interested to know more about the mathematical detail.
Andersen (2000) argues that 5 Minute window provides the best trade-off between getting enough data and avoiding noise. In one of the first work on Bitcoin's Price Discovery, Brandvold et al. 2015 had used 5M window. So I obtained 5M OHLCV data using the following sources:
Poloniex, Bitfinex, Binance and HitBTC: Exchange's API through CCXT.
CME: Okay, this was was supposed to be tricky and expensive. I broke a TOS and scraped the data for free, removing the expensive part from the equation. I will not go into detail about where I scraped this data.
Futures data are different from other data because multiple futures contract trades at the same time. I formed a single data from the multiple time series by selecting the nearest contract until it was three days from expiration. I used the next contract when the contract was three days from expiration. This approach was advocated by Booth et al ( 1999 )
I can't embed the chart on reddit so open this https://warproxxx.github.io/static/price_discovery.html In the figure above, each colored line shows the total influence the exchange had towards the discovery of Bitcoin Price on that day. Its axis is on the left. The black line shows a moving average of the bitcoin price at the close in Bitfinex for comparison. The chart was created by plotting the EMA of price and dominance with a smoothing factor of 0.1. This was done to eliminate the noise. Let's start looking from the beginning. We start with a slight Bitfinex dominance at the start. When the price starts going up, Bitfinex's influence does too. This was the time large Tether printing was attributed to the rise of price by many individuals. But Bitfinex's influence wanes down as the price starts rising (remember that the chart is an exponential moving average. Its a lagging indicator). Afterward, exchanges like Binance and Bitstamp increase their role, and there isn't any single leader in the run. So although Bitfinex may have been responsible for the initial pump trades on other exchanges were responsible for the later rally. CME contracts were added to our analysis in February 2018. Initially, they don't have much influence. On a similar work Alexandar and Heck (2019) noted that initially CBOE contracts had more influence. CBOE later delisted Bitcoin futures so I couldn't get that data. Overall, Bitmex and CME contracts have been averaging around 50% of the role in price discovery. To make the dominance clear, look at this chart where I add Bitmex Futures and Perp contract's dominance figure to create a single dominance index. There bitmex leads 936 of the total 1334 days (Bitfinex leads 298 days and coinbase and binance get 64 and 6 days). That is a lot. One possible reason for this might be Bitmex's low trading fee. Bitmex has a very generous -0.025% maker fee and price discovery tend to occur primarily in the market with smaller trading costs (Booth et al, 1999). It may also be because our market is mature. In mature markets, futures lead the price discovery.
Table 1: Days Lead
Out of 1334 days in the analysis, Bitmex futures leads the discovery in 571 days or nearly 43% of the duration. Bitfinex leads for 501 days. Bitfinex's high number is due to its extreme dominance in the early days.
Table 2: Correlation between the close price and Exchange's dominance index
Binance, Huobi, CME, and OkCoin had the most significant correlation with the close price. Bitmex, Coinbase, Bitfinex, and Bitstamp's dominance were negatively correlated. This was very interesting. To know more, I captured a yearwise correlation.
Table 3: Yearwise Correlation between the close price and Exchange's dominance index Price movement is pretty complicated. If one factor, like a dominant exchange, could explain it, everyone would be making money trading. With this disclaimer out of the way, let us try to make some conclusions. This year Bitfinex, Huobi, and OkEx, Tether based exchanges, discovery power have shown a high correlation with the close price. This means that when the traders there become successful, price rises. When the traders there are failing, Bitmex traders dominate and then the price is falling. I found this interesting as I have been seeing the OkEx whale who has been preceding price rises in this sub. I leave the interpretation of other past years to the reader.
My analysis does not include market data for other derivative exchanges like Huobi, OkEx, Binance, and Deribit. So, all future market's influence may be going to Bitmex. I did not add their data because they started having an impact recently. A more fair assessment may be to conclude this as the new power of derivative markets instead of attributing it as the power of Bitmex. But Bitmex has dominated futures volume most of the time (until recently). And they brought the concept of perpetual swaps.
There is a lot in this data. If you are making a trading algo think there is some edge here. Someday I will backtest some trading logic based on this data. Then I will have more info and might write more. But, this analysis was enough for to shift my focus from a Bitfinex based trading algorithm to a Bitmex based one. It has been giving me good results. If you have any good ideas that you want me to write about or discuss further please comment. If there is enough interest in this measurement, I can setup a live interface that provides the live value.
Crypto-Powered: Understanding Bitcoin, Ethereum, and DeFi
Until one understands the basics of this tech, they won’t be able to grasp or appreciate the impact it has on our digital bank, Genesis Block. https://reddit.com/link/ho4bif/video/n0euarkifu951/player This is the second post ofCrypto-Powered— a new series that examines what it means forGenesis Blockto be a digital bank that’s powered by crypto, blockchain, and decentralized protocols. --- Our previous post set the stage for this series. We discussed the state of consumer finance and how the success of today’s high-flying fintech unicorns will be short-lived as long as they’re building on legacy finance — a weak foundation that is ripe for massive disruption. Instead, the future of consumer finance belongs to those who are deeply familiar with blockchain tech & decentralized protocols, build on it as the foundation, and know how to take it to the world. Like Genesis Block. Today we begin our journey down the crypto rabbit hole. This post will be an important introduction for those still learning about Bitcoin, Ethereum, or DeFi (Decentralized Finance). This post (and the next few) will go into greater detail about how this technology gives Genesis Block an edge, a superpower, and an unfair advantage. Let’s dive in… https://preview.redd.it/1ugdxoqjfu951.jpg?width=650&format=pjpg&auto=webp&s=36edde1079c3cff5f6b15b8cd30e6c436626d5d8
Bitcoin: The First Cryptocurrency
There are plenty of online resources to learn about Bitcoin (Coinbase, Binance, Gemini, Naval, Alex Gladstein, Marc Andreessen, Chris Dixon). I don’t wanna spend a lot of time on that here, but let’s do a quick overview for those still getting ramped up. Cryptocurrency is the most popular use-case of blockchain technology today. And Bitcoin was the first cryptocurrency to be invented.
Bitcoin is the most decentralized of all crypto assets today — no government, company, or third party can control or censor it.
Bitcoin has two primary features (as do most other cryptocurrencies):
Send Value You can send value to anyone, anywhere in the world. Nobody can intercept, delay or stop it — not even governments or financial institutions. Unlike with traditional money transfers or bank wires, there are no layers of middlemen. This results in a process that is much more cost-efficient. Some popular use-cases include remittances and cross-border payments.
A few negative moments in Bitcoin’s history include the collapse of Mt. Gox — which resulted in hundreds of millions of customer funds being stolen — as well as Bitcoin’s role in dark markets like Silk Road — where Bitcoin arguably found its initial userbase. However, like most breakthrough technology, Bitcoin is neither good nor bad. It’s neutral. People can use it for good or they can use it for evil. Thankfully, it’s being used less and less for illicit activity. Criminals are starting to understand that transactions on a blockchain are public and traceable — it’s exactly the type of system they usually try to avoid. And it’s true, at this point “a lot more” crimes are actually committed with fiat than crypto. As a result, the perception of bitcoin and cryptocurrency has been changing over the years to a more positive light. Bitcoin has even started to enter the world of media & entertainment. It’s been mentioned in Hollywood films like Spiderman: Into the Spider-Verse and in songs from major artists like Eminem. It’s been mentioned in countless TV shows like Billions, The Simpsons, Big Bang Theory, Gray’s Anatomy, Family Guy, and more. As covid19 has ravaged economies and central banks have been printing money, Bitcoin has caught the attention of many legendary Wall Street investors like Paul Tudor Jones, saying that Bitcoin is a great bet against inflation (reminding him of Gold in the 1970s). Cash App already lets their 25M users buy Bitcoin. It’s rumored that PayPal and Venmo will soon let their 325M users start buying Bitcoin. Bitcoin is by far the most dominant cryptocurrency and is showing no signs of slowing down. For more than a decade it has delivered on its core use-cases — being able to send or store value.
At this point, Bitcoin has very much entered the zeitgeist of modern pop culture — at least in the West.
When Ethereum launched in 2015, it opened up a world of new possibilities and use-cases for crypto. With Ethereum Smart Contracts (i.e. applications), this exciting new digital money (cryptocurrency) became a lot less dumb. Developers could now build applications that go beyond the simple use-cases of “send value” & “store value.” They could program cryptocurrency to have rules, behavior, and logic to respond to different inputs. And always enforced by code. Additional reading on Ethereum fromLinda XieorVitalik Buterin.
Because these applications are built on blockchain technology (Ethereum), they preserve many of the same characteristics as Bitcoin: no one can stop, censor or shut down these apps because they are decentralized.
Just as tokens grew in popularity in 2017–2018, so did online marketplaces where these tokens could be bought, sold, and traded. This was a fledgling asset class — the merchants selling picks, axes, and shovels were finally starting to emerge.
I had a front-row seat — both as an investor and token creator. This was the Wild West with all the frontier drama & scandal that you’d expect.
Binance — now the world’s largest crypto exchange —was launched during this time. They along with many others (especially from Asia) made it really easy for speculators, traders, and degenerate gamblers to participate in these markets. Similar to other financial markets, the goal was straightforward: buy low and sell high. https://preview.redd.it/tytsu5jnfu951.jpg?width=600&format=pjpg&auto=webp&s=fe3425b7e4a71fa953b953f0c7f6eaff6504a0d1 That period left an embarrassing stain on our industry that we’ve still been trying to recover from. It was a period rampant with market manipulation, pump-and-dumps, and scams. To some extent, the crypto industry still suffers from that today, but it’s nothing compared to what it was then.
While the potential of getting filthy rich brought a lot of fly-by-nighters and charlatans into the industry, it also brought a lot of innovators, entrepreneurs, and builders.
The launch and growth of Ethereum has been an incredible technological breakthrough. As with past tech breakthroughs, it has led to a wave of innovation, experimentation, and development. The creativity around tokens, smart contracts, and decentralized applications has been fascinating to witness. Now a few years later, the fruits of those labors are starting to be realized.
I know that for the hardcore crypto people, what we covered today is nothing new. But for those who are still getting up to speed, welcome! I hope this was helpful and that it fuels your interest to learn more. Until you understand the basics of this technology, you won’t be able to fully appreciate the impact that it has on our new digital bank, Genesis Block. You won’t be able to understand the implications, how it relates, or how it helps. After today’s post, some of you probably have a lot more questions. What are specific examples or use-cases of DeFi? Why does it need to be on a blockchain? What benefits does it bring to Genesis Block and our users? In upcoming posts, we answer these questions. Today’s post was just Level 1. It set the foundation for where we’re headed next: even deeper down the crypto rabbit hole. --- Other Ways to Consume Today's Episode:
We have a lot more content coming. Be sure to follow our channels: https://genesisblock.com/follow/ Have you already downloaded the app? We're Genesis Block, a new digital bank that's powered by crypto & decentralized protocols. The app is live in the App Store (iOS & Android). Get the link to download at https://genesisblock.com/download
AMA Recap of CEO and Co-founder of Chromia, Henrik Hjelte in the @binancenigeria Telegram group on 03/05/2020.
Bitcoin (BTC) is a peer-to-peer cryptocurrency that aims to function as a means of exchange that is independent of any central authority. BTC can be transferred electronically in a secure, verifiable, and immutable way.
Launched in 2009, BTC is the first virtual currency to solve the double-spending issue by timestamping transactions before broadcasting them to all of the nodes in the Bitcoin network. The Bitcoin Protocol offered a solution to the Byzantine Generals’ Problem with ablockchainnetwork structure, a notion first created byStuart Haber and W. Scott Stornetta in 1991.
Bitcoin’s whitepaper was published pseudonymously in 2008 by an individual, or a group, with the pseudonym “Satoshi Nakamoto”, whose underlying identity has still not been verified.
The Bitcoin protocol uses an SHA-256d-based Proof-of-Work (PoW) algorithm to reach network consensus. Its network has a target block time of 10 minutes and a maximum supply of 21 million tokens, with a decaying token emission rate. To prevent fluctuation of the block time, the network’s block difficulty is re-adjusted through an algorithm based on the past 2016 block times.
With a block size limit capped at 1 megabyte, the Bitcoin Protocol has supported both the Lightning Network, a second-layer infrastructure for payment channels, and Segregated Witness, a soft-fork to increase the number of transactions on a block, as solutions to network scalability.
Bitcoin is a peer-to-peer cryptocurrency that aims to function as a means of exchange and is independent of any central authority. Bitcoins are transferred electronically in a secure, verifiable, and immutable way.
Network validators, whom are often referred to as miners, participate in the SHA-256d-based Proof-of-Work consensus mechanism to determine the next global state of the blockchain.
The Bitcoin protocol has a target block time of 10 minutes, and a maximum supply of 21 million tokens. The only way new bitcoins can be produced is when a block producer generates a new valid block.
The protocol has a token emission rate that halves every 210,000 blocks, or approximately every 4 years.
Unlike public blockchain infrastructures supporting the development of decentralized applications (Ethereum), the Bitcoin protocol is primarily used only for payments, and has only very limited support for smart contract-like functionalities (Bitcoin “Script” is mostly used to create certain conditions before bitcoins are used to be spent).
In the Bitcoin network, anyone can join the network and become a bookkeeping service provider i.e., a validator. All validators are allowed in the race to become the block producer for the next block, yet only the first to complete a computationally heavy task will win. This feature is called Proof of Work (PoW). The probability of any single validator to finish the task first is equal to the percentage of the total network computation power, or hash power, the validator has. For instance, a validator with 5% of the total network computation power will have a 5% chance of completing the task first, and therefore becoming the next block producer. Since anyone can join the race, competition is prone to increase. In the early days, Bitcoin mining was mostly done by personal computer CPUs. As of today, Bitcoin validators, or miners, have opted for dedicated and more powerful devices such as machines based on Application-Specific Integrated Circuit (“ASIC”). Proof of Work secures the network as block producers must have spent resources external to the network (i.e., money to pay electricity), and can provide proof to other participants that they did so. With various miners competing for block rewards, it becomes difficult for one single malicious party to gain network majority (defined as more than 51% of the network’s hash power in the Nakamoto consensus mechanism). The ability to rearrange transactions via 51% attacks indicates another feature of the Nakamoto consensus: the finality of transactions is only probabilistic. Once a block is produced, it is then propagated by the block producer to all other validators to check on the validity of all transactions in that block. The block producer will receive rewards in the network’s native currency (i.e., bitcoin) as all validators approve the block and update their ledgers.
The Bitcoin protocol utilizes the Merkle tree data structure in order to organize hashes of numerous individual transactions into each block. This concept is named after Ralph Merkle, who patented it in 1979. With the use of a Merkle tree, though each block might contain thousands of transactions, it will have the ability to combine all of their hashes and condense them into one, allowing efficient and secure verification of this group of transactions. This single hash called is a Merkle root, which is stored in the Block Header of a block. The Block Header also stores other meta information of a block, such as a hash of the previous Block Header, which enables blocks to be associated in a chain-like structure (hence the name “blockchain”). An illustration of block production in the Bitcoin Protocol is demonstrated below. https://preview.redd.it/m6texxicf3151.png?width=1591&format=png&auto=webp&s=f4253304912ed8370948b9c524e08fef28f1c78d
Block time and mining difficulty
Block time is the period required to create the next block in a network. As mentioned above, the node who solves the computationally intensive task will be allowed to produce the next block. Therefore, block time is directly correlated to the amount of time it takes for a node to find a solution to the task. The Bitcoin protocol sets a target block time of 10 minutes, and attempts to achieve this by introducing a variable named mining difficulty. Mining difficulty refers to how difficult it is for the node to solve the computationally intensive task. If the network sets a high difficulty for the task, while miners have low computational power, which is often referred to as “hashrate”, it would statistically take longer for the nodes to get an answer for the task. If the difficulty is low, but miners have rather strong computational power, statistically, some nodes will be able to solve the task quickly. Therefore, the 10 minute target block time is achieved by constantly and automatically adjusting the mining difficulty according to how much computational power there is amongst the nodes. The average block time of the network is evaluated after a certain number of blocks, and if it is greater than the expected block time, the difficulty level will decrease; if it is less than the expected block time, the difficulty level will increase.
What are orphan blocks?
In a PoW blockchain network, if the block time is too low, it would increase the likelihood of nodes producingorphan blocks, for which they would receive no reward. Orphan blocks are produced by nodes who solved the task but did not broadcast their results to the whole network the quickest due to network latency. It takes time for a message to travel through a network, and it is entirely possible for 2 nodes to complete the task and start to broadcast their results to the network at roughly the same time, while one’s messages are received by all other nodes earlier as the node has low latency. Imagine there is a network latency of 1 minute and a target block time of 2 minutes. A node could solve the task in around 1 minute but his message would take 1 minute to reach the rest of the nodes that are still working on the solution. While his message travels through the network, all the work done by all other nodes during that 1 minute, even if these nodes also complete the task, would go to waste. In this case, 50% of the computational power contributed to the network is wasted. The percentage of wasted computational power would proportionally decrease if the mining difficulty were higher, as it would statistically take longer for miners to complete the task. In other words, if the mining difficulty, and therefore targeted block time is low, miners with powerful and often centralized mining facilities would get a higher chance of becoming the block producer, while the participation of weaker miners would become in vain. This introduces possible centralization and weakens the overall security of the network. However, given a limited amount of transactions that can be stored in a block, making the block time too longwould decrease the number of transactions the network can process per second, negatively affecting network scalability.
3. Bitcoin’s additional features
Segregated Witness (SegWit)
Segregated Witness, often abbreviated as SegWit, is a protocol upgrade proposal that went live in August 2017. SegWit separates witness signatures from transaction-related data. Witness signatures in legacy Bitcoin blocks often take more than 50% of the block size. By removing witness signatures from the transaction block, this protocol upgrade effectively increases the number of transactions that can be stored in a single block, enabling the network to handle more transactions per second. As a result, SegWit increases the scalability of Nakamoto consensus-based blockchain networks like Bitcoin and Litecoin. SegWit also makes transactions cheaper. Since transaction fees are derived from how much data is being processed by the block producer, the more transactions that can be stored in a 1MB block, the cheaper individual transactions become. https://preview.redd.it/depya70mf3151.png?width=1601&format=png&auto=webp&s=a6499aa2131fbf347f8ffd812930b2f7d66be48e The legacy Bitcoin block has a block size limit of 1 megabyte, and any change on the block size would require a network hard-fork. On August 1st 2017, the first hard-fork occurred, leading to the creation of Bitcoin Cash (“BCH”), which introduced an 8 megabyte block size limit. Conversely, Segregated Witness was a soft-fork: it never changed the transaction block size limit of the network. Instead, it added an extended block with an upper limit of 3 megabytes, which contains solely witness signatures, to the 1 megabyte block that contains only transaction data. This new block type can be processed even by nodes that have not completed the SegWit protocol upgrade. Furthermore, the separation of witness signatures from transaction data solves the malleability issue with the original Bitcoin protocol. Without Segregated Witness, these signatures could be altered before the block is validated by miners. Indeed, alterations can be done in such a way that if the system does a mathematical check, the signature would still be valid. However, since the values in the signature are changed, the two signatures would create vastly different hash values. For instance, if a witness signature states “6,” it has a mathematical value of 6, and would create a hash value of 12345. However, if the witness signature were changed to “06”, it would maintain a mathematical value of 6 while creating a (faulty) hash value of 67890. Since the mathematical values are the same, the altered signature remains a valid signature. This would create a bookkeeping issue, as transactions in Nakamoto consensus-based blockchain networks are documented with these hash values, or transaction IDs. Effectively, one can alter a transaction ID to a new one, and the new ID can still be valid. This can create many issues, as illustrated in the below example:
Alice sends Bob 1 BTC, and Bob sends Merchant Carol this 1 BTC for some goods.
Bob sends Carols this 1 BTC, while the transaction from Alice to Bob is not yet validated. Carol sees this incoming transaction of 1 BTC to him, and immediately ships goods to B.
At the moment, the transaction from Alice to Bob is still not confirmed by the network, and Bob can change the witness signature, therefore changing this transaction ID from 12345 to 67890.
Now Carol will not receive his 1 BTC, as the network looks for transaction 12345 to ensure that Bob’s wallet balance is valid.
As this particular transaction ID changed from 12345 to 67890, the transaction from Bob to Carol will fail, and Bob will get his goods while still holding his BTC.
With the Segregated Witness upgrade, such instances can not happen again. This is because the witness signatures are moved outside of the transaction block into an extended block, and altering the witness signature won’t affect the transaction ID. Since the transaction malleability issue is fixed, Segregated Witness also enables the proper functioning of second-layer scalability solutions on the Bitcoin protocol, such as the Lightning Network.
Lightning Network is a second-layer micropayment solution for scalability. Specifically, Lightning Network aims to enable near-instant and low-cost payments between merchants and customers that wish to use bitcoins. Lightning Network was conceptualized in a whitepaper by Joseph Poon and Thaddeus Dryja in 2015. Since then, it has been implemented by multiple companies. The most prominent of them include Blockstream, Lightning Labs, and ACINQ. A list of curated resources relevant to Lightning Network can be found here. In the Lightning Network, if a customer wishes to transact with a merchant, both of them need to open a payment channel, which operates off the Bitcoin blockchain (i.e., off-chain vs. on-chain). None of the transaction details from this payment channel are recorded on the blockchain, and only when the channel is closed will the end result of both party’s wallet balances be updated to the blockchain. The blockchain only serves as a settlement layer for Lightning transactions. Since all transactions done via the payment channel are conducted independently of the Nakamoto consensus, both parties involved in transactions do not need to wait for network confirmation on transactions. Instead, transacting parties would pay transaction fees to Bitcoin miners only when they decide to close the channel. https://preview.redd.it/cy56icarf3151.png?width=1601&format=png&auto=webp&s=b239a63c6a87ec6cc1b18ce2cbd0355f8831c3a8 One limitation to the Lightning Network is that it requires a person to be online to receive transactions attributing towards him. Another limitation in user experience could be that one needs to lock up some funds every time he wishes to open a payment channel, and is only able to use that fund within the channel. However, this does not mean he needs to create new channels every time he wishes to transact with a different person on the Lightning Network. If Alice wants to send money to Carol, but they do not have a payment channel open, they can ask Bob, who has payment channels open to both Alice and Carol, to help make that transaction. Alice will be able to send funds to Bob, and Bob to Carol. Hence, the number of “payment hubs” (i.e., Bob in the previous example) correlates with both the convenience and the usability of the Lightning Network for real-world applications.
Schnorr Signature upgrade proposal
Elliptic Curve Digital Signature Algorithm (“ECDSA”) signatures are used to sign transactions on the Bitcoin blockchain. https://preview.redd.it/hjeqe4l7g3151.png?width=1601&format=png&auto=webp&s=8014fb08fe62ac4d91645499bc0c7e1c04c5d7c4 However, many developers now advocate for replacing ECDSA with Schnorr Signature. Once Schnorr Signatures are implemented, multiple parties can collaborate in producing a signature that is valid for the sum of their public keys. This would primarily be beneficial for network scalability. When multiple addresses were to conduct transactions to a single address, each transaction would require their own signature. With Schnorr Signature, all these signatures would be combined into one. As a result, the network would be able to store more transactions in a single block. https://preview.redd.it/axg3wayag3151.png?width=1601&format=png&auto=webp&s=93d958fa6b0e623caa82ca71fe457b4daa88c71e The reduced size in signatures implies a reduced cost on transaction fees. The group of senders can split the transaction fees for that one group signature, instead of paying for one personal signature individually. Schnorr Signature also improves network privacy and token fungibility. A third-party observer will not be able to detect if a user is sending a multi-signature transaction, since the signature will be in the same format as a single-signature transaction.
4. Economics and supply distribution
The Bitcoin protocol utilizes the Nakamoto consensus, and nodes validate blocks via Proof-of-Work mining. The bitcoin token was not pre-mined, and has a maximum supply of 21 million. The initial reward for a block was 50 BTC per block. Block mining rewards halve every 210,000 blocks. Since the average time for block production on the blockchain is 10 minutes, it implies that the block reward halving events will approximately take place every 4 years. As of May 12th 2020, the block mining rewards are 6.25 BTC per block. Transaction fees also represent a minor revenue stream for miners.
Huobi is a Singapore-based cryptocurrency exchange. Founded in China, the company now has offices in Hong Kong, Korea, Japan and the United States. In August 2018 it became a publicly listed Hong Kong company. Recently during early 2019, after crypto communities lost interest in ICOs (Initial Coin Offering) due to many unregistered STOs (Security Token Offering) and other projects whose aim was only to raise the funds. Exchanges adapted and gave a new dimension of the fund raising, IEO (Initial Exchange Offering). In this regard, exchanges helped the projects by providing them a platform to raise the funds and also helped the retail investors by doing due diligence on the project on behalf of the investors. Best part of this process is, such issued tokens are listed on the same platform and exchanges helped these start ups in the process. This gave a sense of security and helped to maintain integrity with the projects and public investors. All the top tier exchanges are participating in this movement and named such fund raising as Launchpad, Jumpstart, Spotlight, Startup etc. While Huobi came up with Huobi Prime. Unlike other exchanges, Huobi Prime has helped varieties of start-ups.
It all started with a DAG based blockchain platform, Top Network.
A project named after the greatest scientist who made a major impact on the human lives, Newton Project. It is aimed to deliver an infrastructure for the community economy.
It is followed by Thunder Core. A blockchain project dreamt of decentralized future and allows anyone to build dApps on their platform.
Then Reserve Rights continued the legacy. It’s a protocol for stable currencies with three kinds of tokens RSV, RSR and collateral tokens.
Akropolis - a protocol to explore the informal economy and help the people with DeFi. It was one of it’s kind which was competitive enough to seek the help from the Huobi.
Later a social digital currency, Emogi secured a place to be the next Prime project.
Recently, Whole Network - A consensus, co-creation, and win-win behavioral value network had the opportunity to feature as a 7th Prime project.
However, each of the Prime project is different from the other in the list. One must admit, it is a basket with mixed fruits. From DAG to Currency to dApp platform to stable coin protocol to DeFi protocol to digital currency to blockchain phone. Huobi has covered a rich list of projects in this journey. https://preview.redd.it/8z08lbq3qls41.png?width=800&format=png&auto=webp&s=34de122d950f32feb46df82cdce290221e1572be (This chart presents the information based on the price of the each token on 2nd October. However it may vary marginally as price of the cryptocurrencies are volatile in nature) Trading Options Many centralized exchanges serve as the sole, centralized market maker. In contrast, Huobi also allows you to trade over the counter (OTC). This means that you can buy and sell cryptocurrencies peer-to-peer on Huobi. Even though this option exists on the exchange, it has yet to gain adoption from traders. Various commenters have said that there is a lack of OTC offers. Still, this is still an innovative technical feature. If you are a margin trader, Houbi has a separate platform specifically for this. You can access this by going to the margin tab in the header. The amount of leverage you can have varies from coin-to-coin. For example, BTC is around 3x. Compared to other margin trading platforms, this is low. Nonetheless, it is an attractive option for potential users. In December 2018, Huobi Derivative Market issued BTC contracts and ETH contracts (including weekly, bi-weekly and quarterly, respectively), and flexible leverages, including 1x, 5x, 10x and 20x. In the future, more digital currencies will be issued to meet various investment demands. Meaning “currency” in Mandarin Chinese, Huobi consistently ranks as one of the world’s top ten largest exchanges by trade volume. In this article, we look at everything you need to know as a potential Huobi user. Let’s examine fees, fund security, customer experience and more. User Interface and Mobile App Available on iOS and Android, the Huobi mobile app features most of the functionalities available on the web platform. You can even complete tasks like account registration and verification directly via the app. In Google Play, the Huobi Global app has an average rating of 4.1 stars out of 3,730 reviews. However, in December 2018 and January 2019, some users have said that the Android app won’t let them login due to an error with Captcha. On the Apple App Store, Huobi boasts an average rating of 4.9 stars out of over 4,800 reviews. Trading Options Many centralized exchanges serve as the sole, centralized market maker. In contrast, Huobi also allows you to trade over the counter (OTC). This means that you can buy and sell cryptocurrencies peer-to-peer on Huobi. Even though this option exists on the exchange, it has yet to gain adoption from traders. Various commenters have said that there is a lack of OTC offers. Still, this is still an innovative technical feature. If you are a margin trader, Houbi has a separate platform specifically for this. You can access this by going to the margin tab in the header. The amount of leverage you can have varies from coin-to-coin. For example, BTC is around 3x. Compared to other margin trading platforms, this is low. Nonetheless, it is an attractive option for potential users. In December 2018, Huobi Derivative Market issued BTC contracts and ETH contracts (including weekly, bi-weekly and quarterly, respectively), and flexible leverages, including 1x, 5x, 10x and 20x. In the future, more digital currencies will be issued to meet various investment demands. Huobi offers a margin trading option. Security Compared to other exchanges, Huobi continues to excel from a security perspective. Many top exchanges suffer from large-scale hacks, with varying results in terms of trading volume afterward. In 2015, a Bitstamp hacker withdrew 12,000 BTC from Huobi. However, this issue did not relate to the security of Huobi. Huobi reported a DDOS attack in 2015 but this did not cause a security breach. According to one review, an individual user lost USDT and EOS on Huobi. This reviewer states that the problem was caused by a technical error with Huobi’s 2FA. One comment suggests that it was the result of a phishing scam. Huobi claims that its risk controls have been developed by the likes of Goldman Sachs. The exchange stores around 98 percent of funds in cold wallets. Moreover, Huobi now utilizes a decentralized exchange structure to prevent DDOS attacks. The exchange even has a User Protection Fund Initiative. Twenty percent of net revenue that the exchanges gains from trades will go to this fund, which it will use to buy back Huobi Token (HT). It also has a service called Huobi Security Reserve. As part of this, the exchange plans to store 20,000 BTC for insurance. This is a preventative measure that will help Huobi reimburse users in the case of any future hacks. Huobi Fees Huobi has a 0.2 percent fee that applies to both market makers and takers for amounts between $0 and $5,000,000 over the course of a 30-day period. In comparison, other top exchanges like Binance have 0.1 percent fees. Meanwhile, GDAX has 0.3 percent fees. In January 2019, Huobi Global launched a tiered fee structure that significantly reduces fees for higher volume traders. This is relatively competitive when compared to other exchanges. Users also have the option to reduce trading fees on Huobi by becoming a VIP member. This involves paying a monthly payment of HT, which varies depending on the membership level (1-5). Like most exchanges Huobi has no fees on deposits. However, Huobi does have withdrawal fees and minimums that vary from coin-to-coin. For example, withdrawing Bitcoin (BTC) costs 0.001 BTC, with a minimum withdrawal amount of 0.01 BTC. For Tether (USDT), the flat fee is 5 USDT and minimum withdrawal amount is 20 USDT. Overall, this means that Huobi fees are generally higher than most exchanges for lower withdrawal amounts. A few exceptions exist. For example, TUSD has a withdrawal minimum of $20 but a withdrawal fee of only $2. Withdrawal Limitations Similar to many exchanges on the market, Huobi has withdrawal limitations based on various levels of user verification. One thing you will notice is that withdrawal amounts vary greatly depending on your citizenship. For example, if you are a citizen of China, you can’t withdraw any funds as an unverified user or with level 1 verification. This option is only available at level 2 or above. In the United States, the exchange only requires level 1 verification. However, the amounts are relatively low: a daily limit of $2,000 and a monthly limit of $10,000. Customer Service Experience Compared to most exchanges, Huobi has above average customer service experience. Customer support is available 24/7, and response times only take two to three hours on average. Many consider this to be a rarity in the space. There are two main methods that you can use to reach customer support. First, you can utilize the chat app that is available directly on the Huobi trading platform. Second, you can contact the team at [[email protected]](mailto:[email protected]). If you choose this option, Huobi asks that you use the registered email address associated with your Huobi account and include your user ID. Huobi Website: https://www.huobi.vc/en-us/topic/invited/?invite_code=3afg5 UID: 134371568 Huobi Indian Community: https://t.me/huobiglobalindia Huobi Global Community: https://t.me/huobiglobalofficial
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.
Binance has the potential to become another major pool on the scene which would dent the decentralized mining space of Bitcoin, and this has been pointed out by certain members in the community. Twitter user ‘HsakaTrades’ tweeted a chart of Bitcoin’s hash rate distribution accompanied by the caption: “This hash distribution chart is soon going to be composed of just one colour.” It wasn’t until early November of 2015 (24 months after the $1,150 peak, and 36 months after the halving) that Bitcoin was able to break past the $300 point; by the end of 2015, BTC had climbed to $430. The second halving came in July of 2016. When the halving took place, Bitcoin was hovering around $660; by the end of the year (5 months later), Bitcoin had reached $957 (a price that still ... A 2015 study found a strong correlation between the Google Trends data and BTC price, while a May 2017 study concluded that when the U.S. Google "Bitcoin" searches increased dramatically, BTC ... Binance Coin Price; Monero Price; MimbleWimbleCoin Price ; How to; Trade Boasting a community of over eight million people, eToro is one of the leading global trading and investment platform – and it specialises in cryptocurrencies. Although there are more than 1,200 assets to trade on eToro, which was founded in 2007, it is in the crypto space that it is particularly popular. The innovative ... Top Trader on Binance Thinks Bitcoin Will Soon Recover . Digital asset manager Logan Han believes that Bitcoin is primed to recover as opposed to retracing lower. The top trader shared the chart below on September 10th with the caption, “my thoughts on how Bitcoin will play out in the coming weeks.” The chart indicates that BTC’s bearish retracement has already bottomed as the coin holds ... Binance Research simulated different Bitcoin allocation techniques in existing diversified multi-asset portfolios. All simulated portfolios which included Bitcoin exhibited overall better risk-return profiles than traditional multi-asset class portfolios. These results show that Bitcoin provides active diversification benefits for all investors worldwide, following multi-asset strategies. With ... This is in line with what happened at the start of the previous macro bull market in 2015-2016. After surging, Bitcoin consolidated in a pivotal trading range, then began a parabolic ascent months later. Logan Han is a prominent crypto trader that regularly posts profitable trades on his Twitter feed. Han has garnered over 4,000 followers after sharing a number of his tweets and ideas about ... 2017 was a massive year for cryptocurrency, with Bitcoin— the most valuable and widely-used cryptocurrency— experiencing a historic price run from just $900 to over $20,000 in value. While it may be the king of the crypto ecosystem, there are a number of issues with the network that has many investors asking: what is the next Bitcoin? Bitcoin: The Next Revolution in International Payment Processing? An Empirical Analysis of Potential Use Cases. 45 Pages Posted: 19 Jun 2015 Last revised: 26 Jan 2018. See all articles by Benedikt Eikmanns Benedikt Eikmanns. Technische Universität München (TUM) - TUM School of Management; Ludwig Maximilian University of Munich (LMU) Philipp G. Sandner. Frankfurt School of Finance ... “Bitcoin, Regression Theorem, and Defining Money” was published on January 2, 2015, and is reprinted here on Bitcoin.com for historical preservation. The opinions expressed in this article are ...
If we repeat 2015 the Bitcoin Bearmarket is over now!
Binance FIAT https: ... a suggested video will automatically play next. Up next The most bullish Bitcoin News in 2019 so far... - Duration: 7:42. sunny decree 28,471 views. 7:42. You Won't Believe ... #BINANCE #BITCOIN #BTC Today we are glad to announce the greatest crypto giveaway ever! It is happening just right now, during the live speech of Changpeng Zhao, CEO of Binance. Bitcoin 2018/2019 bear market compared to the Bitcoin 2014/2015 bear market and the Gold bear market from 1980 to 2000. These charts are very similar. If these similarities would continue for the ... Bloomberg Fidelity has been mining bitcoin since 2015 Finance and Crypto Do you believe they only have a couple hundred bitcoin? Please comment below! Don't forget to like an subscribe! BREAKING! JAPAN & USA COLLABORATION to BEAT China's E-Yuan! Ethereum to 10k minimum + SEC Securities - Duration: 29:09. Digital Asset News 31,107 views Autoplay When autoplay is enabled, a suggested video will automatically play next. Up next 3 Ways to Know When to Buy Bitcoin, Cryptos, Stocks and Forex - Duration: 10:38. In today's video, we take a look at the binance expected acquisition of coinmarketcap and whether or not this is good for crypto. If you would like to be highlighted on my channel please reach out ...