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.
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.
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.
Regards!! I'm Jesús Zambrano, member of the Hispanic community of NANO for a long time. Last thursday, we had an interesting and enjoying Ask-me-anything at Binance Spanish community on telegram with the people behind NANO, Colin LeMahieu (Founder and Executive Director) and Zach Hyatt (Proyect Manager), where we take advantage of their kindness and willingness to ask them some questions and share opinions about de currency. I will share a compilation of some of the questions and answers. -(Admin) ¡Welcome Binancians to our following AMA! I will explain how AMA works; we will have three (3) segments. Segment #1: I am going to ask to our guests five (5) questions and then they will answer them. I will be explaining the rest of the segments as we conclude one of them. -(Admin) Today we have the great pleasure of having Colin (Founder and Executive Director) and Zach (Project Manager) with us in our chat room. Could you give us a little introduction about you? - (Zach) Hi everyone, I am Zach Hyatt, the Project Manager at the Nano Foundation and am excited to help answer questions about Nano. I live in Austin, TX where it is quite hot right now! -(Colin) I’m Colin LeMahieu, founder of Nano. I’m a computer engineer and I’ve worked at companies like Qualcomm, Dell, and AMD. I have been working on Nano for about 5 years now and I’m really excited to talk with people who are interested as well! -(Admin) It is a pleasure for us to have you here, I have to say that on a personal level, I have been a follower of the project for a long time now, so it is incredible for me to be able to count on you tonight, we will start with segment # 1, with the questions I have for you. Feeless transactions and in record time! What is NANO? Can you give us an introduction to the project? -(Colin) Nano’s goal is to solve problems with other cryptocurrencies and make sending value fast and fee-less. It has a unique design to allow us to accomplish this. We want people to have the option of using decentralized digital money instead of fiat money anywhere in the world. Nano is accessible and easy-to-use today and we plan on keeping it focused on these goals. -(Admin) Thank you for answering my first question, I am delighted with the features offered by the project, every week they are updating and making important changes that help to improve the ecosystem that surrounds the team. Here you can find all the weekly updates: https://nano.org/en Previously the project was called RaiBlocks, it appeared for the first time in an ad in Bitcoin Talk in 2015. Can you tell us why a name change came up later? -(Zach) Yeah, absolutely. Although the original RaiBlocks name has a special place in our history, it was difficult to pronounce in some areas of the world and caused confusion with certain users. We decided to move to a shorter name that not only was easy to pronounce but also reflected the fast, efficient nature of the protocol. -(Admin) A short and quick name to pronounce, definitely NANO is perfect to define it! My third question is the following; I had seen a very interesting gif early in the chat and it is just about the question that I came to ask. Currently, NANO has 100% of its tokens in circulation and these tokens were distributed through Faucets, so it meant that any user with a computer could get coins simply by completing some captchas, can you tell me which has been the experience of users when using this method? -(Colin) The faucet was a great way for us to distribute coins to people who have never used it before. Cryptocurrencies that use mining end up distributing only to people who have money to buy the mining hardware and this is unfair. We had a lot of people from Indonesia and Asia in the beginning of our distribution and at the end there were a lot of people from South America, Venezuela and Brasil that were getting most of the Nano from the faucet. We think this was a fairer way to do it and it got Nano into the hands of people in different locations, and it had a very positive impact on their lives. -(Admin) This is incredible! thanks for your answer! Can you tell us about what the Open Representative Vote is about and how it protects the network? -(Zach) Nano uses voting to get confirmation on the network instead of mining and the nodes on the network that create votes are called Representatives. Open Representative Voting allows people who have a Nano balance to pick whatever representative they want to vote on their behalf. This allows the people who hold Nano to decide who generates consensus instead of mining companies. The voting process is very efficient and is a big part of what allows Nano to be fee-less and use very little energy. -(Admin) Very good! The last question on my part: Nano PoW is your new approach, I have read a pretty interesting example with emails, can you explain what it is about? -(Colin) Nano PoW is a research project we’re doing in order to create a proof of work algorithm that uses less energy than other popular algorithms. Since Nano is fee-less, there must be a method to limit transactions going onto the network, which this PoW achieves. With the goal of using more memory in the process instead of CPU cycles in order to generate proofs, this new Nano PoW will help prevent ASICs from being able to cheaply send lots of transactions. It’s important for a cryptocurrency that’s used around the world to be energy efficient and green so continuing our research on this is important to us. -(Admin)https://medium.com/nanocurrency/nano-pow-the-details-ba22a9092d6f Thanks for your answers, Colin and Zach! I have a video, taken from your YouTube account that I would like to share with the community https://www.youtube.com/watch?v=eh9pA8UCUrI Can you tell me what we see in this video? -(Colin) This is a video of how fast our transactions send and receive. You can see it takes less than 1 second to finish which means you can use it as a currency. - (Zach) The wallet was made by developers in our amazing community, it is called Natrium. It really shows how fast Nano is and how it is easy-to-use! -(Colin) You can also see how simple it is to use. You just scan, enter an amount, and send. There are no complicated setting which is great for new users and great for adoption. - (Zach) And the best part is, there were no fees at all for that transaction. In fact there have never been any transaction fees on the Nano network ever! -(Admin) Great! That's why I wanted to share it with everyone, yesterday I could try the wallet and it is really spectacular to use, thank you very much for that excellent explanation, please stay with us, now comes the part in which our users participate Segment 3, community questions Q -First congratulations on your project, it is amazing. Now, does nano BlockChain have another use besides making transactions? A - (Zach) Thank you! Nano has always been focused on transfer of value and will continue to maintain that focus. The overall design is aimed at doing only this so it can remain fast, efficient and fee-less. Q -Good evening! I understand that thanks to its architecture called "Block-lattice", each individual provides the computing power necessary to verify their own transaction, thanks to this they do not use miners to confirm transactions and they do not apply commissions of any kind. My question is: How did this occur and how difficult was it? A - (Colin) It’s simila, transactions are validated by votes from the representatives, not by the PoW. The PoW is a way to slow down how fast people can create transactions so they can’t spam the network. Q - Do you have any short or long term projects so that transactions using $NANO were anonymous? A - (Colin) Long term we want to see what privacy options exist and are fast. Most privacy schemes make the transactions very big or slow to process and it’s important for things to remain quick and efficient so we can have fast transactions. Q - We are living in Venezuela many changes in the cryptocurrency sector, the integration of crypto for service payment and product purchases is already a reality. What agreements has NANO made with service stores to integrate it as a means of payment? I want to pay my movie ticket with NANOS A - (Zach) Thanks for your interest in Nano. We are always looking for ways to allow everyone to use Nano in as many places as possible. Although separate from our organization, we are aware of the efforts of the Nano Venezuela organization and try to support them when possible in bringing Nano to as many people and stores in Venezuela as possible. Q - (7 questions made from one persone at once)
How do you manage to make your transactions virtually instantaneous?
How do they create part of the company's livelihood if no fees are charged for transactions?
Why does $ NANO consume so little electricity?
Requirements for a medium-sized company to adopt nano correctly as a means of payment?
Since 100% of the $ NANOS are distributed, I have seen something in Medium that talked about `` Nano PoW '', could you tell me a little more about how it works? What profit will the person / institution get that puts hardware for their PoW? Will more $ NANO be created apart from those already in circulation?
What do the representatives earn for putting their vote and validating blocks if 100% of the $ NANOS are already created / issued?
7- Since your policy / slogan / commandment is to be a cryptocurrency without fees, shouldn't you force exchanges in which $ NANO is present that they don't charge withdrawal fees? A - (Colin)
Transactions are fast because they’re validated by voting. The votes get transmitted around the world in milliseconds and all people have to do is count votes to confirm the transaction.
We use the Dev fund to pay for developing the Nano protocol. The Nano protocol is a free tool that other people can build businesses on. We have ideas for businesses that can use fast, free money in order to help people send money to their family in other countries or pay microtransactions. It’s similar to Linux, it’s free but big companies use it because it saves them money.
Nano uses little electricity because we use voting for validating transactions. Voting is just sending data over the internet which is power efficient.
You can run a nano node with 40-60$/mo using cloud virtual machines
Nano pow is just a more efficient way to slow people down from sending transactions to the network
The most important thing is: why does a company want to use cryptocurrency? They want to use it because it saves them money on bank fees, etc. Since 40-60$/mo running a node is less expensive than their bank fees, they want to participate in the network to keep it going and save them money.
Q - Knowing all this about Nano, could you say that Nano is one of the most energy-efficient, Ecological friendly currencies in existence? A -(Zach) Absolutely. We care about making a positive change in the world and so pride ourselves on leaving as little energy trace possible in the world. It may just be the fastest, most efficient transfer of value available. Q - If the nano protocol had not passed the Red4Sec signature security test, would it have any vulnerability today? A - (Colin) The Red4Sec audit didn’t find any critiral vulnerabilities in Nano. In fact they did the audit twice because they couldn’t find anything wrong and that never happened before. It’s important for us to keep the code high quality and we will do audits again in the future because it’s important to make sure everything is secure. Q - I'd like to see more development of Nano by using SMS on our phones to avoid the problem of no Internet connection at the moment A -(Zach) As much as we like the idea of SMS, unfortunately it is not a secure network so managing Nano transactions over it brings some unique requirements. However we are always innovating and trying to make Nano as easy and accessible as possible so hope advances can help over time make it more accessible in this area. Q - What plans do you have to close this 2019 to increase adoption in Latin America? A -(Colin) We are very excited about the passion we see in the south american community. We would love to make it down to VE however in the mean time follow nanoVE for updates and meetups - there may be one near you soon! Q - How will you make the adoption and use of $ NANO continue to increase especially in markets where other cryptocurrencies are gaining more ground? A - (Colin) Our focus is to build tools people need to accept cryptocurrency. Right now it’s still difficulty and expensive. One thing we’re making is the device Appia which can accept cryptocurrency similar to a credit card. We made this device very inexpensive and can connect over wireless so it can be used in markets or resturaunts or other places cryptocurrency is not yet available. - (Admin) Thank you very much for your answers! You are the first guests that answer all the questions of our users, you are amazing guys! @AndyNano It was amazing to meet you, I learned a lot from you @FundacionNanoVE Thanks for making this happen! excellent work @nano_isam Thanks for everything buddy! -(Zach) Can we ask a question to the channel? What are the top things Nano can do to help you in your daily lives? -(Colin) My question: How do you store cryptocurrency safely? Where do you back up your seed so it isn’t lost or stolen? A - In Venezuela we currently have a problem with conventional payment processors, they are very slow, it would be great to be able to see people using NANO to make their purchases at any store in Venezuela, 0 commissions and instant transactions, is what we need A - Fast transactions are what can help society the most, and except that, the best thing is that it is very cheap ... from there it is addition, those are the main characteristics that we look for the most A - encrypted file in a pendrive A - Nano is a direct competition to the vast majority of Cryptos, in transaction speed and that it is literally free to send or receive, nothing to wait for 5 hours or the next day when you pay for items or services with Crypto, let's increase the adoption of nano! -(Colin) Question: Are there barriers to using Nano in your country right now? A - No barriers in Venezuela A - No barrier what is lacking is greater diffusion in means to give greater projection and that the adoption arrives. Here I am to support NANO! A - There should be no barriers to the payments we wish to make, freedom above all -(Colin) Fantastic! - (Zach) Thanks everyone, I have to go but I appreciate all the awesome questions and answers!
2019 in Review: Community, Crime, Courtcases, Craig & Consolidation
https://preview.redd.it/r7dmpveldia41.png?width=680&format=png&auto=webp&s=f7dc87d5b58c4391d3e04359c4dc111d771246a1 2019 has been a tumultuous but amazing year for the development and advancement of blockchain technology. Following the rally to the all-time-highs at the end of 2017 and the intense infrastructure development and ongoing Bear Market of 2018 it was clear things were changing quickly. We are about to enter a new decase and the team at Aelf wanted to look back at 2019 and reflect on some of the events that occurred over the last year to see where the industry might be headed in 2020. https://preview.redd.it/tccwloemdia41.png?width=384&format=png&auto=webp&s=3c9feac47c8e8accc602dee7e738df86facc3e2e Although the year has been considered a continuation of the 2018 bear market, it didn’t stop development, progression and a myriad of crazy events from occurring. This included the challenges associated with global regulations, the upcoming Bitcoin halving event in May 2020, announcement of the Facebook Libra and Telegram Open Network’s (TON) launch delay. This year also saw a myriad of debacles from self-proclaimed Bitcoin creator Craig Wright, the Justin Sun and Warren Buffet lunch situation, the recent claim of Twitter CEO Jack Dorsey’s goal to modify Twitter into a decentralized version of the platform, and President Trump’s Bitcoin statement, among others. Now let’s examine more of what took place during 2019 as we approach the start of the New Year in 2020. The SEC, Telegram, Facebook Libra, Kik and Blockchain’s Global Regulatory Environment Many of the world’s governments have been harsh towards blockchain technology in recent years. Particularly, the US Government and the Securities and Exchange Commission (SEC) have been very reluctant to ease the regulatory framework for blockchain development in the country. This has become more evident in 2019, with the SEC combatting many blockchain projects this year including the $1.7 billion-dollar token offering of the Telegram Open Network and the Facebook Libra project. As well the SEC created controversy in a gruesome battle with Kik over its alleged illegal token offering that Kik has sworn to fight to their last breath. https://preview.redd.it/6yngxxfndia41.png?width=614&format=png&auto=webp&s=dc363d1a2225f461bad20786e8439e7cc3896d7d Many proponents of blockchain technology accuse the SEC of unfair policies to put a stranglehold on the development on blockchain in order to prevent the devaluation of the American monetary system. The reluctance for crypto exchanges to set up shop in the US is also becoming more prevalent because of the supposedly biased and unfavourable approach of the SEC. Nevertheless, there are also several major countries including China that have for the most part embraced the advancement of blockchain technology in 2019. China has also nearly finalized the development of the digital Chinese Yuan and announced that that country is going all in on blockchain development despite its sometimes anti-Bitcoin approach. The Bitcoin Halving Event and its Ongoing Effect on Market Conditions With the end of 2019 nearly upon us and the upcoming Bitcoin halving event set to take place during May of 2020 the market could be overdue for a bull market of mass proportions. Remember, the last bull market that took place was 2 years ago during December 2017 and was followed by an incredible dump from the all-time-high price of 20 thousand US Dollars to just 3300 USD in December 2018. For the most part, 2018 was a blood-bath for crypto markets and 2019 has not been all that much better. The price did briefly rally up to 14 thousand US Dollars during mid 2019 but has since been reduce by half with the Bitcoin price presently at just over 7000 US Dollars. Bitcoin was designed by its original creators with code written to mitigate the negative effects of inflation. In order to curb inflation, once every 4 years (or 210,000 blocks) the mining rewards that the network automatically generates are reduced in half. https://preview.redd.it/xuthhfiodia41.png?width=819&format=png&auto=webp&s=2cc8cbc7452d4aadb5076530915acfd5e755735a 3 Additional Stories to Watch in 2020 In June, the CEO of Tron, Justin Sun purchased tickets through eBay for a charity auction to have lunch with Warren Buffet. Sun paid a record $4.56 million US Dollars in the process becoming the highest bid in the 20-year history of the event. The purpose of the lunch from Sun’s standpoint is to change Mr. Buffet’s viewpoint towards crypto and blockchain tech by inviting several blockchain industry leaders to help sway the famous investor’s perspective. Sun subsequently missed the lunch he scheduled in September because of a sudden bout with kidney stones. At this time, the community will have to wait and see when Sun and Buffet will meet in 2020. Stay tuned. Back in December of 2015, Craig Wright claimed publicly to be the creator of Bitcoin, Satoshi Nakamoto. Most believe Wright was lying to gain more fame and recognition in the industry. On November 18th, 2018 Bitcoin SV hard forked from the Bitcoin Cash Network to create it own chain. As noted above, the disgruntled CEO of Bitcoin SV, has for years maintained he led the initial development of Bitcoin. During February 2018, Wright was the subject of a 5.118-Billion-dollar lawsuit by Dave Kleiman claiming that Wright defrauded Kleiman of Bitcoin while working on the initial development of the Bitcoin Network between 2009 and 2013. In August 2019, Wright was ordered by a court of law to pay half the 5.11 Billion in Bitcoin back to Kleiman. Throughout 2019, Wright launched lawsuits against Ethereum founder Vitalik Buterin, Bitcoin Cash’s Roger Ver and others for calling him a fraud. It seems likely Wright will continue his ongoing Satoshi rhetoric in 2020. https://preview.redd.it/l977df8qdia41.png?width=547&format=png&auto=webp&s=f52d70a3c852b920ae665c8b5770a74cd8dadabe The CEO of Twitter, Jack Dorsey recently stated that he has hired 5 full-time employees to modify the Twitter platform and make it increasingly decentralized. This may seem like a small step initially, but this project could be expanded easily by someone of Dorsey’s reputation and wealth in the technology industry. Dorsey himself has been a long-term proponent of blockchain technology and an investor in Bitcoin. Binance CEO, Changpeng Zhao, recently offered to help Dorsey make this dream come to fruition. Additionally, Morgan Creek Capital founder Anthony Pompliano supported Dorsey’s statement noting that, “Jack Dorsey may understand the future better than any entrepreneur on the planet right now.” Conclusion This year we saw Kik, Telegram and Facebook Libra face fierce backlash from the most powerful regulatory body in the world, the SEC. We saw the Chinese government announce that they are all in on blockchain development and declare the upcoming launch of their own centralized digital Chinese Yuan. Justin Sun postponed his 4.56-million-dollar lunch with billionaire investor Warren Buffet because of health issues, while Jack Dorsey the CEO of Twitter proclaimed a more decentralized and open version of Twitter to prevent some of the abuse on the platform. In 2019, the 4-year long Craig Wright and Satoshi Nakamoto saga continued, and we finally are moving closer to the much-anticipated Bitcoin halving event of May 2020 that could change the trajectory of the Bitcoin price for much of 2020 and 2021. It is clear 2019 has been an incredible year for the blockchain industry. With no shortage of uncertainty and scepticism in the short-term, it is likely that 2019 will pale in comparison to the developments of 2020. As we approach 2020, the industry will continue to expand towards mass adoption and the mainstream evolution of blockchain technology. Nevertheless, with the global regulatory blockchain environment evolving in many areas across the world, the uncertainty in the United States remains stronger than ever. There is no telling what will happen in this regard and what will happen with Bitcoin and this amazing revolution in 2020 and beyond. Merry Christmas and Happy Holidays from the Aelf Blockchain team and a Happy 2020 to all our community members!! Thank You
Blockchain Jobs Continue To Grow Despite A 53% Yearly Drop In Blockchain Jobs` Interest
Blockchain Specialists Are Hard To Find Because Individuals Decreased Their Interest In The Blockchain Sector Since its introduction in 2009, the moving force behind every cryptocurrency – the blockchain, evolved from its origin to become a leading new technology. As the technology matures, so does the job sector, associated with it – companies are starting to seek professionals rather than enthusiasts. The companies providing blockchain-related job openings, however, have decreased their workforce expectations. The reason – decreased interest in job seekers. Indeed, one of the most popular employment websites did research, stating that although companies provide more and more blockchain-related job openings, the crypto enthusiasts with the required experience do not want to apply. “Blockchain-related jobs increased by over 26 percent. However, we see a 53 percent decrease of job searches over the past 12 months”, the report states. The interest decrease in 2019 made it the first year with a negative search in the blockchain sector, according to Indeed. In 2018, for example, there was a 214% growth in job openings from 2017, with a 14% increase in corresponding job searches. 2017 remains the best year in terms of blockchain job acquisition, with a 204% growth in job openings from 2016 and with a 326% increase in blockchain-related job searches. Bitcoin paved the way for further blockchain developments and new types of digital assets. Coins and tokens are scaling up from their initial purpose of payment methods. The number of crypto-related companies expanded, as well as the need for an increase of workforce behind every blockchain project. Indeed reports 1,457 percent growth in job offerings between September 2015 and September 2019. The job searches, however, gained “only” 469 percent. The main reason behind the explosion of crypto job offerings is the ICO boom in 2017, which created a large number of projects, aiming to raise funds in a new way. The increase, however, was followed by a massive drop, wiping 85% of the total market capitalization of the crypto sector. Over 1,000 crypto projects shut operations in 2018, according to TechCrunch. Regulators also managed to bring the trust in the crypto sector down, driving away potential workers, due to regulatory uncertainty, which drowned numerous projects. Despite the rough year for the entire crypto sector, some projects continued to grow and generate job opportunities. Binance, Coinbase, Amazon, JPMorgan Chase, and Wallmart are just some of the examples. Companies are mostly hiring full-stack developers, software engineers, front-enders, and software architects. Media and management comes second. Due to the high demand for specialists, there is not much of a supply.
Cardano is a 3rd generation open source blockchain platform that is expected to provide unprecedented support for dapps smart contracts and applications. But we have Ethereum for that, don't we? Well, Ethereum is not that good and has faced network congestion more than once. So we need something better designed from the ground up. Cardano is one of them. You may think of Cardano as Ethereum, but inside it is a robust, research-based approach that lays the groundwork for what should be achieved and how effective. And just like Ethereum, Cardano has its own cryptocurrency called Cardano(ADA), which serves as fuel for the Cardano network. Cardano is more than just a cryptocurrency. It is a technology platform that is capable of running financial applications that are used daily by individuals, organizations and governments around the world. The platform is built in modules, which provides flexibility in system maintenance and allows for upgrades using soft branches. Once the settlement layer at which Ada will operate is completed, a separate computing layer will be created to handle smart contracts, digital legal agreements that will underpin future trade and business. Cardano will also run decentralized applications or DApps, services not controlled by any one party but running on the blockchain.
2. How does Cardano cryptocurrency work?
Cardano has deliberately made it modular, so future updates and iterations can be easy. Cardano consists of two parts: the computational level and the computational level. The settlement level is for calculating cryptocurrency transactions (ADO transactions) and the calculation level is for calculating smart contracts and DApps code. For this reason, the team can change the agreed Protocol at the calculation level at any time without breaking the calculation level and Vice versa. The unique thing about Cardano is its long-term plans. Charles Hoskinson, CEO of Cardano, says they want to create something like a TCP / IP Protocol that can last for decades and eventually make the economy for 3 billion disadvantaged people comprehensive. That's why there's so much focus on research and peer review. https://preview.redd.it/ug51houkhnu31.png?width=1000&format=png&auto=webp&s=7150c6f81dfa5fd978bc65f88bd4837888a9d95b In fact, Charles says they chose their consensus Protocol, the so-called Ouroboros, very carefully. Through Ouroboros, the time in Cardano is divided into eras, which are further divided into slots, which are short time periods of about 20 seconds, and each slot has a designated leader. Slot leaders can create no more than one block in their assigned slot and are therefore rewarded with transaction fees collected in the era. But this slot leader is determined according to your Commission in the system. So if there are more ADA transactions in the system, the chances of you becoming a slot leader will be higher. Thus, Cardano provides security as well as proof of work Bitcoin, but cheaper and more efficient. This method also makes Cardano much faster when you don't have to wait 10 or more minutes for a transaction to complete. Cardano is developing more scalability capabilities, and we'll talk about that later in this article.
Cardano Foundation: an independent standards body based in Switzerland with primary responsibilities to support the Cardano user community and work with authorities on regulatory and commercial matters.
IOHK [Input Output HongKong]: IOHK is a blockchain technology company created by Charles Hoskinson in 2015 specifically to promote peer-to-peer innovation to provide financial services to the 3 billion people around the world who do not have them. IOHK has a contract to develop Cardano until 2020, and some of its other clients are Finance and Ethereum classic.
Emurg: invests in startups and helps businesses build the Cardano blockchain.
The Cardano project is steadily gaining popularity, and therefore the number of exchanges trading Cardano cryptocurrency is also growing. Here are some of the exchanges through which you can buy/sell cryptocurrency Cardano:
Binance: supported pairs: ADA / BT, ADA / ETO, DA / BOMB, DA / SDT
Huobi: Supported pairs: ADA / BTC, ADA / ETO, DA / SDT
Gate.io: supported pairs: ADA / BTC, ADA / USDT
Bitrix: supported pairs: ADA / BT, ADA / ETO, DA / SDT
Cardano is not an ERC 20 token. Instead, it has its own dedicated blockchain from the beginning and therefore has a completely different wallet designed by the Cardano team. The only viable and popular wallet for Cardano right now is the Daedalus wallet, which is the main client for storing, sending and receiving Cardano. The most popular Cardano wallets:
Desktop wallet: Daedalus Wallet (Windows & Mac)
Mobile wallet: Infinito Wallet (Android app | iOS app)
Hardware wallet: very soon you should expect Ledger Nano to support Cardano as it is under development.
7. Cardano's future and roadmap
Cardano is focused on solving 4 critical problems faced by the blockchain world today, all in one place:
You see how carefully Cardano's team is moving forward. But some might argue that it happens at a snail's pace. Given the fact that they follow the process of initial research and peer review, this speed is expected. Also, when you're focused on building a Protocol that can last decades, you need very careful planning. On the other hand, Cardano is written in Haskell, and there are very few developers around the world, and this is also one of the reasons for its slow development. But even when it is completed, smart contract and Apps development will require knowledge of the Plutus programming language. This can be a huge learning curve, and also to prevent the adoption of Cardano. It's too early to make a decision, as Cardano will need another year or more to fully develop it, and such things will only become clearer once development is complete. Source
Digital money that’s instant, private, and free from bank fees. Download our official wallet app and start using Bitcoin today. Read news, start mining, and buy BTC or BCH. Bitcoin Generator stellt grundsätzlich keinerlei Anlageberatung, Vermögensberatung, Kaufempfehlung oder Anlagempfehlung aus. Der Autor der Artikel kann in den unterschiedlichen Kryptowährungen selbst investiert sein. Im Rahmen von Partnerprogrammen (Affiliate) kann die Promotion von auf bitcoin-generator.de gelisteten Anbietern vergütet werden. In meinem Beitrag „Profit Trailer – Automatisch Kryptowährungen traden mit einem Bot“ habe ich ein wenig über das automatische Traden mit dem Profit Trailer Bot berichtet. Aber gerade bei der Börse Binance kommt es vor, dass der Bot nach längerer Laufzeit quasi eingefriert und sich aufhängt. Das Ergebnis ist, dass er nichts mehr tut, was […] Despite this serious security breach and theft, Bitcoin price is rallying and reached $7,000 this weekend establishing a fresh new high in 2019. Throughout the industry Binance has been known for its security and the fact hackers were able to breach one of exchanges hot wallets containing about two percent of the company’s holdings using advanced phishing techniques is concerning. Binance hacked, hackers, stolen 7,000 Bitcoin that worth more than $40 Million using a variety of attack methods that include phishing, viruses, and other attacks. By using the hacking methods, they obtain a large number of user API keys, 2FA codes, and potentially other info to withdraw BTC from the hot wallet. Hackers withdrew 7,074... Bitcoin Generator. Bitcoin network makes the hashing process challenging to limit the mining of numerous Bitcoin in minutes. The bitcoin network will make it more deliberate by introducing the feature called “proof of work.”This protocol demands the block’s hash to have a certain number of Zeroes at the start. If you put $1k in BTC in April 2015, you would have around $40,000 right now. And if you put $1k in BTC in December 2015, you would have more than $21,000 right now. As you can see, the Bitcoin news bring a lot of excitement and over time, the cryptocurrency can be seen as a great and very profitable long-term investment. The price of BTC this ... In my contribution “Profit Trailer – Automatically crypto currency trading with a bot” I have a little about the automated trading with the Profit Bot Trailer. But especially with the stock market Binance it happens, that after a long term of quasi Bot turned freezes and hangs. The result is, that he is doing nothing, was […] A new metric just emerged in the crypto news today, showing that the Bitcoin ROI since 2015 outperforms five major indices and puts the digital asset ahead of the traditional markets.. For those of you who don’t know, the dominant coin Bitcoin (BTC) had a nearly 3,500% return on investment since 2015 which is 70 times the one of five traditional stock markets. Automatisierte Investments mit Bitcoin. Wer schon ein wenig Startkapital hat und dieses nicht nutzlos auf seinem Wallet herumliegen haben möchte, für den kann es eine interessante Variante sein, die Bitcoins automatisiert in Fremdwährungen, Aktien oder ETFs anzulegen.Die Möglichkeit dazu bieten sogenannte Auto Trading Robots.
#kyc #binance #hacked. Category Science & Technology; Show more Show less. Loading... Advertisement Autoplay When autoplay is enabled, a suggested video will automatically play next. Up next Pomp ... Join Wazirx To Buy/Sell Bitcoin - https://bit.ly/2XLScra In this video we would like to talk about alt coins after bitcoin halving event gets over . As this can be very big opportunity for public ... How To Connect Two Routers On One Home Network Using A Lan Cable Stock Router Netgear/TP-Link - Duration: 33:19. Richard Lloyd Recommended for you Bigger Bitcoin, BTC Donations, Binance Trading Pairs & LTC Giveaway The Modern Investor. Loading... Unsubscribe from The Modern Investor? Cancel Unsubscribe. Working... Subscribe Subscribed ... 💙Phemex $112 Extra Bonus: https://phemex.com/web/user/register?group=74&referralCode=I4IEK 💛Binance Futures 10% Discount: https://www.binance.com/en/futures/... Amazon Affiliate Link - (If You Buy Something On Amazon, I Get A Small Commission As A Way To Support The Channel) - (There is NO extra cost for you) https://amzn.to/39MXp4q Computer I Use To ... #binance #binanceus #CZ #CZbinance #bitcoin #btc #binancebitcoin #Binanceexchange #Binanceappreview #Buyonbinance #binancebitcoinwallet #binance #bitcointrading #Bitcoin2020 # ... Users are rewarded for simply depositing and holding coins on Binance as they normally would. With staking on Binance, users can receive staking rewards all while just being a regular Binance user. This demo shows how you can connect your Binance US account to CryptoTrader.Tax to automate your cryptocurrency tax reporting. Simply import your trades and generate your tax reports with the ...