Binance Coin, Tron, Cosmos Price Analysis: 09 September ...
The Top 511 Bitcoin Open Source Projects
Can I Mine Bitcoin With A Laptop? [2020 Guide]
Steps to Buy NEO Crypto on Binance (2020) Free Bitcoin Life
Running Bitcoin: Tools, Apps and Guides SourceCrypto
GitHub - SpiralDevelopment/Awesome-Crypto-Trading: An ...
The Top 496 Bitcoin Open Source Projects
Binance hack Bitcoin News
BTC/USDT Perpetual Binance Live Price Chart
Bob The Magic Custodian
Summary: Everyone knows that when you give your assets to someone else, they always keep them safe. If this is true for individuals, it is certainly true for businesses. Custodians always tell the truth and manage funds properly. They won't have any interest in taking the assets as an exchange operator would. Auditors tell the truth and can't be misled. That's because organizations that are regulated are incapable of lying and don't make mistakes. First, some background. Here is a summary of how custodians make us more secure: Previously, we might give Alice our crypto assets to hold. There were risks:
Alice might take the assets and disappear.
Alice might spend the assets and pretend that she still has them (fractional model).
Alice might store the assets insecurely and they'll get stolen.
Alice might give the assets to someone else by mistake or by force.
Alice might lose access to the assets.
But "no worries", Alice has a custodian named Bob. Bob is dressed in a nice suit. He knows some politicians. And he drives a Porsche. "So you have nothing to worry about!". And look at all the benefits we get:
Alice can't take the assets and disappear (unless she asks Bob or never gives them to Bob).
Alice can't spend the assets and pretend that she still has them. (Unless she didn't give them to Bob or asks him for them.)
Alice can't store the assets insecurely so they get stolen. (After all - she doesn't have any control over the withdrawal process from any of Bob's systems, right?)
Alice can't give the assets to someone else by mistake or by force. (Bob will stop her, right Bob?)
Alice can't lose access to the funds. (She'll always be present, sane, and remember all secrets, right?)
See - all problems are solved! All we have to worry about now is:
Bob might take the assets and disappear.
Bob might spend the assets and pretend that he still has them (fractional model).
Bob might store the assets insecurely and they'll get stolen.
Bob might give the assets to someone else by mistake or by force.
Bob might lose access to the assets.
It's pretty simple. Before we had to trust Alice. Now we only have to trust Alice, Bob, and all the ways in which they communicate. Just think of how much more secure we are! "On top of that", Bob assures us, "we're using a special wallet structure". Bob shows Alice a diagram. "We've broken the balance up and store it in lots of smaller wallets. That way", he assures her, "a thief can't take it all at once". And he points to a historic case where a large sum was taken "because it was stored in a single wallet... how stupid". "Very early on, we used to have all the crypto in one wallet", he said, "and then one Christmas a hacker came and took it all. We call him the Grinch. Now we individually wrap each crypto and stick it under a binary search tree. The Grinch has never been back since." "As well", Bob continues, "even if someone were to get in, we've got insurance. It covers all thefts and even coercion, collusion, and misplaced keys - only subject to the policy terms and conditions." And with that, he pulls out a phone-book sized contract and slams it on the desk with a thud. "Yep", he continues, "we're paying top dollar for one of the best policies in the country!" "Can I read it?' Alice asks. "Sure," Bob says, "just as soon as our legal team is done with it. They're almost through the first chapter." He pauses, then continues. "And can you believe that sales guy Mike? He has the same year Porsche as me. I mean, what are the odds?" "Do you use multi-sig?", Alice asks. "Absolutely!" Bob replies. "All our engineers are fully trained in multi-sig. Whenever we want to set up a new wallet, we generate 2 separate keys in an air-gapped process and store them in this proprietary system here. Look, it even requires the biometric signature from one of our team members to initiate any withdrawal." He demonstrates by pressing his thumb into the display. "We use a third-party cloud validation API to match the thumbprint and authorize each withdrawal. The keys are also backed up daily to an off-site third-party." "Wow that's really impressive," Alice says, "but what if we need access for a withdrawal outside of office hours?" "Well that's no issue", Bob says, "just send us an email, call, or text message and we always have someone on staff to help out. Just another part of our strong commitment to all our customers!" "What about Proof of Reserve?", Alice asks. "Of course", Bob replies, "though rather than publish any blockchain addresses or signed transaction, for privacy we just do a SHA256 refactoring of the inverse hash modulus for each UTXO nonce and combine the smart contract coefficient consensus in our hyperledger lightning node. But it's really simple to use." He pushes a button and a large green checkmark appears on a screen. "See - the algorithm ran through and reserves are proven." "Wow", Alice says, "you really know your stuff! And that is easy to use! What about fiat balances?" "Yeah, we have an auditor too", Bob replies, "Been using him for a long time so we have quite a strong relationship going! We have special books we give him every year and he's very efficient! Checks the fiat, crypto, and everything all at once!" "We used to have a nice offline multi-sig setup we've been using without issue for the past 5 years, but I think we'll move all our funds over to your facility," Alice says. "Awesome", Bob replies, "Thanks so much! This is perfect timing too - my Porsche got a dent on it this morning. We have the paperwork right over here." "Great!", Alice replies. And with that, Alice gets out her pen and Bob gets the contract. "Don't worry", he says, "you can take your crypto-assets back anytime you like - just subject to our cancellation policy. Our annual management fees are also super low and we don't adjust them often". How many holes have to exist for your funds to get stolen? Just one. Why are we taking a powerful offline multi-sig setup, widely used globally in hundreds of different/lacking regulatory environments with 0 breaches to date, and circumventing it by a demonstrably weak third party layer? And paying a great expense to do so? If you go through the list of breaches in the past 2 years to highly credible organizations, you go through the list of major corporate frauds (only the ones we know about), you go through the list of all the times platforms have lost funds, you go through the list of times and ways that people have lost their crypto from identity theft, hot wallet exploits, extortion, etc... and then you go through this custodian with a fine-tooth comb and truly believe they have value to add far beyond what you could, sticking your funds in a wallet (or set of wallets) they control exclusively is the absolute worst possible way to take advantage of that security. The best way to add security for crypto-assets is to make a stronger multi-sig. With one custodian, what you are doing is giving them your cryptocurrency and hoping they're honest, competent, and flawlessly secure. It's no different than storing it on a really secure exchange. Maybe the insurance will cover you. Didn't work for Bitpay in 2015. Didn't work for Yapizon in 2017. Insurance has never paid a claim in the entire history of cryptocurrency. But maybe you'll get lucky. Maybe your exact scenario will buck the trend and be what they're willing to cover. After the large deductible and hopefully without a long and expensive court battle. And you want to advertise this increase in risk, the lapse of judgement, an accident waiting to happen, as though it's some kind of benefit to customers ("Free institutional-grade storage for your digital assets.")? And then some people are writing to the OSC that custodians should be mandatory for all funds on every exchange platform? That this somehow will make Canadians as a whole more secure or better protected compared with standard air-gapped multi-sig? On what planet? Most of the problems in Canada stemmed from one thing - a lack of transparency. If Canadians had known what a joke Quadriga was - it wouldn't have grown to lose $400m from hard-working Canadians from coast to coast to coast. And Gerald Cotten would be in jail, not wherever he is now (at best, rotting peacefully). EZ-BTC and mister Dave Smilie would have been a tiny little scam to his friends, not a multi-million dollar fraud. Einstein would have got their act together or been shut down BEFORE losing millions and millions more in people's funds generously donated to criminals. MapleChange wouldn't have even been a thing. And maybe we'd know a little more about CoinTradeNewNote - like how much was lost in there. Almost all of the major losses with cryptocurrency exchanges involve deception with unbacked funds. So it's great to see transparency reports from BitBuy and ShakePay where someone independently verified the backing. The only thing we don't have is:
ANY CERTAINTY BALANCES WEREN'T EXCLUDED. Quadriga's largest account was $70m. 80% of funds are in 20% of accounts (Pareto principle). All it takes is excluding a few really large accounts - and nobody's the wiser. A fractional platform can easily pass any audit this way.
ANY VISIBILITY WHATSOEVER INTO THE CUSTODIANS. BitBuy put out their report before moving all the funds to their custodian and ShakePay apparently can't even tell us who the custodian is. That's pretty important considering that basically all of the funds are now stored there.
ANY IDEA ABOUT THE OTHER EXCHANGES. In order for this to be effective, it has to be the norm. It needs to be "unusual" not to know. If obscurity is the norm, then it's super easy for people like Gerald Cotten and Dave Smilie to blend right in.
It's not complicated to validate cryptocurrency assets. They need to exist, they need to be spendable, and they need to cover the total balances. There are plenty of credible people and firms across the country that have the capacity to reasonably perform this validation. Having more frequent checks by different, independent, parties who publish transparent reports is far more valuable than an annual check by a single "more credible/official" party who does the exact same basic checks and may or may not publish anything. Here's an example set of requirements that could be mandated:
First report within 1 month of launching, another within 3 months, and further reports at minimum every 6 months thereafter.
No auditor can be repeated within a 12 month period.
All reports must be public, identifying the auditor and the full methodology used.
All auditors must be independent of the firm being audited with no conflict of interest.
Reports must include the percentage of each asset backed, and how it's backed.
The auditor publishes a hash list, which lists a hash of each customer's information and balances that were included. Hash is one-way encryption so privacy is fully preserved. Every customer can use this to have 100% confidence they were included.
If we want more extensive requirements on audits, these should scale upward based on the total assets at risk on the platform, and whether the platform has loaned their assets out.
There are ways to structure audits such that neither crypto assets nor customer information are ever put at risk, and both can still be properly validated and publicly verifiable. There are also ways to structure audits such that they are completely reasonable for small platforms and don't inhibit innovation in any way. By making the process as reasonable as possible, we can completely eliminate any reason/excuse that an honest platform would have for not being audited. That is arguable far more important than any incremental improvement we might get from mandating "the best of the best" accountants. Right now we have nothing mandated and tons of Canadians using offshore exchanges with no oversight whatsoever. Transparency does not prove crypto assets are safe. CoinTradeNewNote, Flexcoin ($600k), and Canadian Bitcoins ($100k) are examples where crypto-assets were breached from platforms in Canada. All of them were online wallets and used no multi-sig as far as any records show. This is consistent with what we see globally - air-gapped multi-sig wallets have an impeccable record, while other schemes tend to suffer breach after breach. We don't actually know how much CoinTrader lost because there was no visibility. Rather than publishing details of what happened, the co-founder of CoinTrader silently moved on to found another platform - the "most trusted way to buy and sell crypto" - a site that has no information whatsoever (that I could find) on the storage practices and a FAQ advising that “[t]rading cryptocurrency is completely safe” and that having your own wallet is “entirely up to you! You can certainly keep cryptocurrency, or fiat, or both, on the app.” Doesn't sound like much was learned here, which is really sad to see. It's not that complicated or unreasonable to set up a proper hardware wallet. Multi-sig can be learned in a single course. Something the equivalent complexity of a driver's license test could prevent all the cold storage exploits we've seen to date - even globally. Platform operators have a key advantage in detecting and preventing fraud - they know their customers far better than any custodian ever would. The best job that custodians can do is to find high integrity individuals and train them to form even better wallet signatories. Rather than mandating that all platforms expose themselves to arbitrary third party risks, regulations should center around ensuring that all signatories are background-checked, properly trained, and using proper procedures. We also need to make sure that signatories are empowered with rights and responsibilities to reject and report fraud. They need to know that they can safely challenge and delay a transaction - even if it turns out they made a mistake. We need to have an environment where mistakes are brought to the surface and dealt with. Not one where firms and people feel the need to hide what happened. In addition to a knowledge-based test, an auditor can privately interview each signatory to make sure they're not in coercive situations, and we should make sure they can freely and anonymously report any issues without threat of retaliation. A proper multi-sig has each signature held by a separate person and is governed by policies and mutual decisions instead of a hierarchy. It includes at least one redundant signature. For best results, 3of4, 3of5, 3of6, 4of5, 4of6, 4of7, 5of6, or 5of7. History has demonstrated over and over again the risk of hot wallets even to highly credible organizations. Nonetheless, many platforms have hot wallets for convenience. While such losses are generally compensated by platforms without issue (for example Poloniex, Bitstamp, Bitfinex, Gatecoin, Coincheck, Bithumb, Zaif, CoinBene, Binance, Bitrue, Bitpoint, Upbit, VinDAX, and now KuCoin), the public tends to focus more on cases that didn't end well. Regardless of what systems are employed, there is always some level of risk. For that reason, most members of the public would prefer to see third party insurance. Rather than trying to convince third party profit-seekers to provide comprehensive insurance and then relying on an expensive and slow legal system to enforce against whatever legal loopholes they manage to find each and every time something goes wrong, insurance could be run through multiple exchange operators and regulators, with the shared interest of having a reputable industry, keeping costs down, and taking care of Canadians. For example, a 4 of 7 multi-sig insurance fund held between 5 independent exchange operators and 2 regulatory bodies. All Canadian exchanges could pay premiums at a set rate based on their needed coverage, with a higher price paid for hot wallet coverage (anything not an air-gapped multi-sig cold wallet). Such a model would be much cheaper to manage, offer better coverage, and be much more reliable to payout when needed. The kind of coverage you could have under this model is unheard of. You could even create something like the CDIC to protect Canadians who get their trading accounts hacked if they can sufficiently prove the loss is legitimate. In cases of fraud, gross negligence, or insolvency, the fund can be used to pay affected users directly (utilizing the last transparent balance report in the worst case), something which private insurance would never touch. While it's recommended to have official policies for coverage, a model where members vote would fully cover edge cases. (Could be similar to the Supreme Court where justices vote based on case law.) Such a model could fully protect all Canadians across all platforms. You can have a fiat coverage governed by legal agreements, and crypto-asset coverage governed by both multi-sig and legal agreements. It could be practical, affordable, and inclusive. Now, we are at a crossroads. We can happily give up our freedom, our innovation, and our money. We can pay hefty expenses to auditors, lawyers, and regulators year after year (and make no mistake - this cost will grow to many millions or even billions as the industry grows - and it will be borne by all Canadians on every platform because platforms are not going to eat up these costs at a loss). We can make it nearly impossible for any new platform to enter the marketplace, forcing Canadians to use the same stagnant platforms year after year. We can centralize and consolidate the entire industry into 2 or 3 big players and have everyone else fail (possibly to heavy losses of users of those platforms). And when a flawed security model doesn't work and gets breached, we can make it even more complicated with even more people in suits making big money doing the job that blockchain was supposed to do in the first place. We can build a system which is so intertwined and dependent on big government, traditional finance, and central bankers that it's future depends entirely on that of the fiat system, of fractional banking, and of government bail-outs. If we choose this path, as history has shown us over and over again, we can not go back, save for revolution. Our children and grandchildren will still be paying the consequences of what we decided today. Or, we can find solutions that work. We can maintain an open and innovative environment while making the adjustments we need to make to fully protect Canadian investors and cryptocurrency users, giving easy and affordable access to cryptocurrency for all Canadians on the platform of their choice, and creating an environment in which entrepreneurs and problem solvers can bring those solutions forward easily. None of the above precludes innovation in any way, or adds any unreasonable cost - and these three policies would demonstrably eliminate or resolve all 109 historic cases as studied here - that's every single case researched so far going back to 2011. It includes every loss that was studied so far not just in Canada but globally as well. Unfortunately, finding answers is the least challenging part. Far more challenging is to get platform operators and regulators to agree on anything. My last post got no response whatsoever, and while the OSC has told me they're happy for industry feedback, I believe my opinion alone is fairly meaningless. This takes the whole community working together to solve. So please let me know your thoughts. Please take the time to upvote and share this with people. Please - let's get this solved and not leave it up to other people to do. Facts/background/sources (skip if you like):
The inspiration for the paragraph about splitting wallets was an actual quote from a Canadian company providing custodial services in response to the OSC consultation paper: "We believe that it will be in the in best interests of investors to prohibit pooled crypto assets or ‘floats’. Most Platforms pool assets, citing reasons of practicality and expense. The recent hack of the world’s largest Platform – Binance – demonstrates the vulnerability of participants’ assets when such concessions are made. In this instance, the Platform’s entire hot wallet of Bitcoins, worth over $40 million, was stolen, facilitated in part by the pooling of client crypto assets." "the maintenance of participants (and Platform) crypto assets across multiple wallets distributes the related risk and responsibility of security - reducing the amount of insurance coverage required and making insurance coverage more readily obtainable". For the record, their reply also said nothing whatsoever about multi-sig or offline storage.
In addition to the fact that the $40m hack represented only one "hot wallet" of Binance, and they actually had the vast majority of assets in other wallets (including mostly cold wallets), multiple real cases have clearly demonstrated that risk is still present with multiple wallets. Bitfinex, VinDAX, Bithumb, Altsbit, BitPoint, Cryptopia, and just recently KuCoin all had multiple wallets breached all at the same time, and may represent a significantly larger impact on customers than the Binance breach which was fully covered by Binance. To represent that simply having multiple separate wallets under the same security scheme is a comprehensive way to reduce risk is just not true.
Private insurance has historically never covered a single loss in the cryptocurrency space (at least, not one that I was able to find), and there are notable cases where massive losses were not covered by insurance. Bitpay in 2015 and Yapizon in 2017 both had insurance policies that didn't pay out during the breach, even after a lengthly court process. The same insurance that ShakePay is presently using (and announced to much fanfare) was describe by their CEO himself as covering “physical theft of the media where the private keys are held,” which is something that has never historically happened. As was said with regard to the same policy in 2018 - “I don’t find it surprising that Lloyd’s is in this space,” said Johnson, adding that to his mind the challenge for everybody is figuring out how to structure these policies so that they are actually protective. “You can create an insurance policy that protects no one – you know there are so many caveats to the policy that it’s not super protective.”
The most profitable policy for a private insurance company is one with the most expensive premiums that they never have to pay a claim on. They have no inherent incentive to take care of people who lost funds. It's "cheaper" to take the reputational hit and fight the claim in court. The more money at stake, the more the insurance provider is incentivized to avoid payout. They're not going to insure the assets unless they have reasonable certainty to make a profit by doing so, and they're not going to pay out a massive sum unless it's legally forced. Private insurance is always structured to be maximally profitable to the insurance provider.
The circumvention of multi-sig was a key factor in the massive Bitfinex hack of over $60m of bitcoin, which today still sits being slowly used and is worth over $3b. While Bitfinex used a qualified custodian Bitgo, which was and still is active and one of the industry leaders of custodians, and they set up 2 of 3 multi-sig wallets, the entire system was routed through Bitfinex, such that Bitfinex customers could initiate the withdrawals in a "hot" fashion. This feature was also a hit with the hacker. The multi-sig was fully circumvented.
Bitpay in 2015 was another example of a breach that stole 5,000 bitcoins. This happened not through the exploit of any system in Bitpay, but because the CEO of a company they worked with got their computer hacked and the hackers were able to request multiple bitcoin purchases, which Bitpay honoured because they came from the customer's computer legitimately. Impersonation is a very common tactic used by fraudsters, and methods get more extreme all the time.
A notable case in Canada was the Canadian Bitcoins exploit. Funds were stored on a server in a Rogers Data Center, and the attendee was successfully convinced to reboot the server "in safe mode" with a simple phone call, thus bypassing the extensive security and enabling the theft.
The very nature of custodians circumvents multi-sig. This is because custodians are not just having to secure the assets against some sort of physical breach but against any form of social engineering, modification of orders, fraudulent withdrawal attempts, etc... If the security practices of signatories in a multi-sig arrangement are such that the breach risk of one signatory is 1 in 100, the requirement of 3 independent signatures makes the risk of theft 1 in 1,000,000. Since hackers tend to exploit the weakest link, a comparable custodian has to make the entry and exit points of their platform 10,000 times more secure than one of those signatories to provide equivalent protection. And if the signatories beef up their security by only 10x, the risk is now 1 in 1,000,000,000. The custodian has to be 1,000,000 times more secure. The larger and more complex a system is, the more potential vulnerabilities exist in it, and the fewer people can understand how the system works when performing upgrades. Even if a system is completely secure today, one has to also consider how that system might evolve over time or work with different members.
By contrast, offline multi-signature solutions have an extremely solid record, and in the entire history of cryptocurrency exchange incidents which I've studied (listed here), there has only been one incident (796 exchange in 2015) involving an offline multi-signature wallet. It happened because the customer's bitcoin address was modified by hackers, and the amount that was stolen ($230k) was immediately covered by the exchange operators. Basically, the platform operators were tricked into sending a legitimate withdrawal request to the wrong address because hackers exploited their platform to change that address. Such an issue would not be prevented in any way by the use of a custodian, as that custodian has no oversight whatsoever to the exchange platform. It's practical for all exchange operators to test large withdrawal transactions as a general policy, regardless of what model is used, and general best practice is to diagnose and fix such an exploit as soon as it occurs.
False promises on the backing of funds played a huge role in the downfall of Quadriga, and it's been exposed over and over again (MyCoin, PlusToken, Bitsane, Bitmarket, EZBTC, IDAX). Even today, customers have extremely limited certainty on whether their funds in exchanges are actually being backed or how they're being backed. While this issue is not unique to cryptocurrency exchanges, the complexity of the technology and the lack of any regulation or standards makes problems more widespread, and there is no "central bank" to come to the rescue as in the 2008 financial crisis or during the great depression when "9,000 banks failed".
In addition to fraudulent operations, the industry is full of cases where operators have suffered breaches and not reported them. Most recently, Einstein was the largest case in Canada, where ongoing breaches and fraud were perpetrated against the platform for multiple years and nobody found out until the platform collapsed completely. While fraud and breaches suck to deal with, they suck even more when not dealt with. Lack of visibility played a role in the largest downfalls of Mt. Gox, Cryptsy, and Bitgrail. In some cases, platforms are alleged to have suffered a hack and keep operating without admitting it at all, such as CoinBene.
It surprises some to learn that a cryptographic solution has already existed since 2013, and gained widespread support in 2014 after Mt. Gox. Proof of Reserves is a full cryptographic proof that allows any customer using an exchange to have complete certainty that their crypto-assets are fully backed by the platform in real-time. This is accomplished by proving that assets exist on the blockchain, are spendable, and fully cover customer deposits. It does not prove safety of assets or backing of fiat assets.
If we didn't care about privacy at all, a platform could publish their wallet addresses, sign a partial transaction, and put the full list of customer information and balances out publicly. Customers can each check that they are on the list, that the balances are accurate, that the total adds up, and that it's backed and spendable on the blockchain. Platforms who exclude any customer take a risk because that customer can easily check and see they were excluded. So together with all customers checking, this forms a full proof of backing of all crypto assets.
However, obviously customers care about their private information being published. Therefore, a hash of the information can be provided instead. Hash is one-way encryption. The hash allows the customer to validate inclusion (by hashing their own known information), while anyone looking at the list of hashes cannot determine the private information of any other user. All other parts of the scheme remain fully intact. A model like this is in use on the exchange CoinFloor in the UK.
A Merkle tree can provide even greater privacy. Instead of a list of balances, the balances are arranged into a binary tree. A customer starts from their node, and works their way to the top of the tree. For example, they know they have 5 BTC, they plus 1 other customer hold 7 BTC, they plus 2-3 other customers hold 17 BTC, etc... until they reach the root where all the BTC are represented. Thus, there is no way to find the balances of other individual customers aside from one unidentified customer in this case.
Proposals such as this had the backing of leaders in the community including Nic Carter, Greg Maxwell, and Zak Wilcox. Substantial and significant effort started back in 2013, with massive popularity in 2014. But what became of that effort? Very little. Exchange operators continue to refuse to give visibility. Despite the fact this information can often be obtained through trivial blockchain analysis, no Canadian platform has ever provided any wallet addresses publicly. As described by the CEO of Newton "For us to implement some kind of realtime Proof of Reserves solution, which I'm not opposed to, it would have to ... Preserve our users' privacy, as well as our own. Some kind of zero-knowledge proof". Kraken describes here in more detail why they haven't implemented such a scheme. According to professor Eli Ben-Sasson, when he spoke with exchanges, none were interested in implementing Proof of Reserves.
And yet, Kraken's places their reasoning on a page called "Proof of Reserves". More recently, both BitBuy and ShakePay have released reports titled "Proof of Reserves and Security Audit". Both reports contain disclaimers against being audits. Both reports trust the customer list provided by the platform, leaving the open possibility that multiple large accounts could have been excluded from the process. Proof of Reserves is a blockchain validation where customers see the wallets on the blockchain. The report from Kraken is 5 years old, but they leave it described as though it was just done a few weeks ago. And look at what they expect customers to do for validation. When firms represent something being "Proof of Reserve" when it's not, this is like a farmer growing fruit with pesticides and selling it in a farmers market as organic produce - except that these are people's hard-earned life savings at risk here. Platforms are misrepresenting the level of visibility in place and deceiving the public by their misuse of this term. They haven't proven anything.
Fraud isn't a problem that is unique to cryptocurrency. Fraud happens all the time. Enron, WorldCom, Nortel, Bear Stearns, Wells Fargo, Moser Baer, Wirecard, Bre-X, and Nicola are just some of the cases where frauds became large enough to become a big deal (and there are so many countless others). These all happened on 100% reversible assets despite regulations being in place. In many of these cases, the problems happened due to the over-complexity of the financial instruments. For example, Enron had "complex financial statements [which] were confusing to shareholders and analysts", creating "off-balance-sheet vehicles, complex financing structures, and deals so bewildering that few people could understand them". In cryptocurrency, we are often combining complex financial products with complex technologies and verification processes. We are naïve if we think problems like this won't happen. It is awkward and uncomfortable for many people to admit that they don't know how something works. If we want "money of the people" to work, the solutions have to be simple enough that "the people" can understand them, not so confusing that financial professionals and technology experts struggle to use or understand them.
For those who question the extent to which an organization can fool their way into a security consultancy role, HB Gary should be a great example to look at. Prior to trying to out anonymous, HB Gary was being actively hired by multiple US government agencies and others in the private sector (with glowing testimonials). The published articles and hosted professional security conferences. One should also look at this list of data breaches from the past 2 years. Many of them are large corporations, government entities, and technology companies. These are the ones we know about. Undoubtedly, there are many more that we do not know about. If HB Gary hadn't been "outted" by anonymous, would we have known they were insecure? If the same breach had happened outside of the public spotlight, would it even have been reported? Or would HB Gary have just deleted the Twitter posts, brought their site back up, done a couple patches, and kept on operating as though nothing had happened?
In the case of Quadriga, the facts are clear. Despite past experience with platforms such as MapleChange in Canada and others around the world, no guidance or even the most basic of a framework was put in place by regulators. By not clarifying any sort of legal framework, regulators enabled a situation where a platform could be run by former criminal Mike Dhanini/Omar Patryn, and where funds could be held fully unchecked by one person. At the same time, the lack of regulation deterred legitimate entities from running competing platforms and Quadriga was granted a money services business license for multiple years of operation, which gave the firm the appearance of legitimacy. Regulators did little to protect Canadians despite Quadriga failing to file taxes from 2016 onward. The entire administrative team had resigned and this was public knowledge. Many people had suspicions of what was going on, including Ryan Mueller, who forwarded complaints to the authorities. These were ignored, giving Gerald Cotten the opportunity to escape without justice.
There are multiple issues with the SOC II model including the prohibitive cost (you have to find a third party accounting firm and the prices are not even listed publicly on any sites), the requirement of operating for a year (impossible for new platforms), and lack of any public visibility (SOC II are private reports that aren't shared outside the people in suits).
Securities frameworks are expensive. Sarbanes-Oxley is estimated to cost $5.1 million USD/yr for the average Fortune 500 company in the United States. Since "Fortune 500" represents the top 500 companies, that means well over $2.55 billion USD (~$3.4 billion CAD) is going to people in suits. Isn't the problem of trust and verification the exact problem that the blockchain is supposed to solve?
To use Quadriga as justification for why custodians or SOC II or other advanced schemes are needed for platforms is rather silly, when any framework or visibility at all, or even the most basic of storage policies, would have prevented the whole thing. It's just an embarrassment.
We are now seeing regulators take strong action. CoinSquare in Canada with multi-million dollar fines. BitMex from the US, criminal charges and arrests. OkEx, with full disregard of withdrawals and no communication. Who's next?
We have a unique window today where we can solve these problems, and not permanently destroy innovation with unreasonable expectations, but we need to act quickly. This is a unique historic time that will never come again.
https://preview.redd.it/ysi74g2vn3251.png?width=1920&format=png&auto=webp&s=63875e316556c41144ad81cf061caf5bb3f4680d We all have heard the term Smart Contract. When Satoshi invented Blockchain, it was meant to perform transactions only. Ethereum smart contracts made it the prime choice to build Dapps over it. Smart contract enhanced Ethereum’s functionality and makes it different from the traditional blockchain (Bitcoin). This functionality was replicated by other newer Blockchains. What are Smart Contracts? Smart contracts can be defined as self-executing applications that run on a blockchain. It is an agreement between two or more parties in the form of a computer code that runs on a decentralized network in a blockchain. It consists of a set of defined rules which are agreed upon by the involved parties. The contract automatically gets activated whenever certain conditions are met. This idea will remove the involvement of any trusted third-party companies (such as banks) and will be controlled by computers on a trusted network. Ethereum is one of the most popular blockchain platforms for creating smart contracts. It supports a feature called Turing-completeness that enables the developers to build customized smart contracts. Solidity, Ethereum’s original coding language is used to develop smart contracts. Ethereum blockchain's ERC-20 and ERC-721 tokens are smart contract standards. Who created it? Nick Szabo, a computer scientist, and cryptographer, first described the idea of Smart contracts in the ‘90s. He worked on the concept of defining contract laws in businesses between parties by maintaining an electronic commerce protocol on the Internet. He further designed Bit Gold, a mechanism for a decentralized digital currency in 1998. Though the idea was never implemented it created a base that led to the popularity of Bitcoin after 10 years. Properties: · Self-verifiable · Self-executable · Tamper Proof Benefits of using Smart Contract · The removal of third-party or middleman leads to direct and transparent communication between involving parties · Helps in maintaining trust as the agreement rules were predefined and agreed by the parties involved · Helps in reducing error and frauds · Time and cost-efficient · No single point of failure or data loss as data is distributed across the network https://preview.redd.it/1e5ahcqxn3251.png?width=1024&format=png&auto=webp&s=f8a1ebb9b3a84dd721fb32f96fc1950899bc3015 Different objects of Smart contracts There are three essential and main objects of Smart Contracts · Signatories- The parties who use the smart contract. · Agreement subject · Terms and Condition-. Details like rules, obligations, and associated punishments, etc are mentioned as terms and conditions as appropriate. How Smart Contract works Ethereum has 2 types of accounts · External accounts (user account) - Controlled by public-private key pairs · Contract accounts - Controlled by the code stored together with the account These accounts contain four fields: · The nonce, which ensures that each transaction can only be processed once · The current ether balance of the account · The contract code of the account · The storage of the account Model steps
External account executes a function:
a. The user initiates the process by signing the transaction using his private key corresponding to the account. b. Local validation of the transaction happens. It is broadcasted to the network. c. The transaction is added to the transaction pool. The mines maintains such pools.
Generate EVM bytecode through compiling
a. EVM is a powerful, virtual sandbox embedded within each full Ethereum node b. The job of the EVM is to update the Ethereum state by computing valid state transitions as a result of smart contact code execution c. The EVM should not run into any exceptions during the execution
Get contract address from that transaction's receipt
Trigger contract address to invoke methods of that deployed smart contract
Upon receiving a newly created block, the local node executes all the transactions in the block.
The accuracy and quality of a smart contract depends on the following things · Open and decentralized database · The environment needs to support the use of public-key cryptography · Quality programming is crucial. · Data should be reliable. · Robust rules should be used while automating the process. Features Smart contracts automatically support the features of underlying blockchain technology. · Autonomy – Complete control of the involving parties. No need of middleman as in the case of traditional contractual system · Speed – Automated computer code runs as soon as the input criteria fulfill, thereby eliminating the delays caused by manual paperwork activity · Safety – Network encryption guarantees safety against data theft or hacking · Savings – No doubt that the removal of middleman saves a lot of overall cost and time · Accuracy – Since these smart contracts are automated software codes so they ensure accurate output as long as the data fed into the system as input is accurate · Trust – Helps in building trust as the documents are encrypted in a shared ledger · Backup – Since in Blockchain network, each node has a complete backup of data which ensures protection over data loss Potential Use cases Smart contracts can be used to exchange money, property, shares, or anything without any intervention of middleman. They are now gaining popularity and adaption in various sectors. Some of the main sectors are as follows:- · Insurance Companies · Health Systems · Government’s administrative work. · Business Management I will cover each of the potential use cases in detail in my future articles separately. Conclusion Smart Contract is the greatest innovation built on Blockchain technology. We can say it as a cherry over the pie. It has given a new dimension to technology and is one of the biggest reasons behind the popularity of Ethereum. We can say without any second thought that very soon we will be entering into the era where there will be no intervention of any third party. In this way, it can help us in saving a lot of money, time, and effort. Also, we don’t need to be dependent or trust anyone while taking any crucial transactions. This will surely help in reducing fraud, unnecessary delays, and the overall cost of transactions. Smart Contracts will make many transactional jobs redundant. We can be hopeful that further development in technology will open sources for many other new jobs. Read More: Understanding Hard Fork Register in Crypto.com and get $ 50. Linkhere. Create a Binance account using my referrallink.
Answer - As for Kava, Kava was originally founded in January 2018. It was formed by cofounders Scott Stuart, Ruaridh O’Donnell and myself with the mission to tackle the problem of interoperability. We started the company working with larger projects like Ripple, MakerDao, and Cosmos on their layer 2 and interoperability problems and developed a lot of expertise in this area. It wasn’t until 2019 that we eventually decided to put our expertise to public use and create the first interoperable DeFi blockchain, Kava.
Could you please tell me what KAVA cryptocurrency is? What problem does it solve?
Answer - KAVA is the staking, governance, and reserve asset of the Kava DeFi platform. KAVA is required by node operators to secure transactions on the blockchain. Additionally, when lending fees are paid, they are converted to Kava and burned reducing the overall supply of KAVA tokens. As more users use the Kava lending platform, KAVA should become more scarce overtime.
What is the advantage of keeping the KAVA token for a long and short term?
Answer - In the short term, if you stake KAVA you can earn additional block rewards every day, block by block. This provides a nice steady return on the Kava usually in the range of 3-20% depending on the number of people staking.
We will be opening the gates of DeFi to many top tier assets such as BNB, XRP, ATOM, and BTC which have never been able to use lending, stablecoins, or other DeFi Services. If you are a KAVA hodler you can benefit from owning and having a stake in the network as we grow because as the network grows, Kava is burned and it becomes more scarce as a resource.
Chainlink is KAVA’s partner, can you explain more about this partnership?
Answer - Yes, this is not the usual chainlink partnership where a blockchain consumes data from Chainlink’s oracle solution.
No oracle solution adequate for DeFi applications on Cosmos was available. For this reason, Kava has teamed up with Chainlink to bring its data and reliable oracle solution to the Cosmos ecosystem. Chainlink nodes now will be able to securely publish data directly on the Kava blockchain where it can be used or easily transported to other Cosmos-based blockchains and applications. Chainlink oracles on Kava utilize all the industry-leading technologies of Chainlink, while enabling more frequent price updates and improving the reach and distribution of where that data can be used.
Since Kava’s blockchain is built using Tendermint, Tendermint-based blockchains within the Cosmos ecosystem (Binance, Terra, OKChain, Cosmos Hub, Agoric, Aragon, and others) will now be able to retrieve market data such as cryptocurrency, FX, and commodity prices. For DEX’s like Binance this will enable them to create futures, options, and other derivative products they were not able to do so before.
TLDR: Kava + Chainlink Data creates the ideal hub for all blockchains and applications to get their DeFi services and Data, and as result makes Kava a natural hub for the growing Cosmos ecosystem.
What is the KAVA CDP product? Do you have any exciting things down the pipeline that you can share?
Answer - First, let me clarify that CDP simply means “collateralized-debt-position” similar to CDOs that exist in the traditional finance world. What it means is a loan using collateral to back the loan.
Kava’s lending platform offers collateralized loans to users who have crypto. Getting a loan with Kava’s platform is great if you don’t want to sell your crypto position, but need short term cash for payments or if you want to use the loan to get a levered / margin position without going through KYC.
As for news! Kava’s lending platform is scheduled to officially launch on the mainnet June 10th.
At this time, DeFi will be made available to BNB for the first time ever. Also at this time, the Kava DeFi platform will be awarding the first users that have BNB extremely high rewards for being early adopters.
Each week, 74,000 KAVA will be given out to all the users who have taken out loans on Kava. Yes, you get free KAVA, for taking out a loan using BNB!
Why should BNB users use KAVA’s lending platform and take out USDX? And how to mint USDX with BNB on KAVA CDP?
Answer - Free- maybe let's call it rewards for being good users 😉
The rewards are platform growth incentives so that we can grow the platform quickly.
Well at launch, definitely the KAVA rewards are a huge reason for BNB users to use it.
As for the product long-term, the major use case for our lending platform is to get a levered position without needing an exchange or to go through KYC.
How it works is that a BNB holder can deposit their BNB and take out USDX loans - this capital they will take and buy more BNB with it. Most people will use the loan this way to get 2-3x the original BNB amount. If the price goes up on BNB, they win 2-3x the gains!
Of course if the price goes down and they cannot repay their loan, the BNB collateral might get liquidated, so be careful, it works just like a margin trading account.
Brian do you have any more information or links for our community about this?
KAVA was initially planned to launch on Ripple network but later switched to Cosmos Tendermint Core. [email protected] is that something you see in Tendermint Core that is not available anywhere?
Answer - For clarification, Kava was never planned to be on Ripple. However, Ripple is a Kava investor, shareholder, and partner.
We selected the Cosmos-SDK featuring the Tendermint BFT consensus because during our past work with Ripple, MakerDao, ETH, and other layer 2 work we learned the value of “finality” of blockchains. For example, on ETH, the finality of blocks do not happen right away. You need to reach 15+ blocks to be confirmed on Ethereum to really know a transaction has passed. This results in really slow user experiences that aren’t acceptable in finance or any application really.
Tendermint solves this because it makes every transaction final and occur in seconds.
Additionally, we chose the Cosmos-SDK as the framework to build our stand alone blockchain, Kava because it allowed us to create our own security model and design which enables Kava as a DeFi platform responsible for millions of dollars of collateral to be very secure in a way we could net get if we built it on any other network.
KAVA does cross-chain support. Compared to other DeFi platforms, KAVA offer collateralized loans and stable coins to users too. How will volatility be managed there with so many different collateral systems in CDP?
Answer - Volatility is an important consideration and accurate and timely price reference data is needed to make sure the system works.
All the collateral positions rely on price feeds from oracles to determine if they are safe or need to be liquidated. Kava has created a novel partnership with Chainlink, where Chainlink oracles that normally run on Ethereum, operate nodes directly on Kava where they can post prices. This Kava to avoid network congestion, high gas fees, and other less desirable issues found on Ethereum, while enabling the oracles with Kava’s fast blocktimes and finality so they can actually deliver price updates 10-20x more frequently than is possible elsewhere. This makes Kava’s price feed data very reliable.
In times of volatility, if liquidations occur, the Kava platform automatically auctions collateral off for USDX on the market and burns the USDX. This mechanism keeps the system balanced and USDX algorithmically stable and always fully collateralized by real assets.
And it does this transparently, unlike the real world CDOs which caused the world issues in 2008 due to the lack of transparency in their assets and risk.
Recently, Binance has released a white paper on BSC, a Binance smart chain. So, what can I get by staking through Binance Coin BNB?
Answer - Yay for smart contracts!
What can we get by staking bnb?
Staking BNB on Kava, or depositing it in a CDP and creating USDX from it earns users KAVA in rewards everyweek. A lot of rewards. In addition, you get USDX to hold which also pays out a savings rate each block that is much better than say what USD in a checking account could do.
Various platforms are in Ethereum. So why is Kava not at Ethereum?
Answer - I could speak about this for ages, but there is a reason for Ethereum being the home to many hacks and bugs.
Kava is not on ethereum because we couldn’t build our system there. The main reasons. as I have mentioned are:
(1) Ethereum has congestion, oracle issues, high fees, and slow block times.
(2) Ethereum’s open smart contracting system can do anything. This is great for building crypto kitties, but horrible for financial software as it makes all code have infinite attack vectors that hackers can use which are impossible to test for. We built our own chain so we could scope the code and limit what attack vectors are possible.
(3) Building in solidity, the language of Ethereum, is horrible. The development environment is bad, testnets don’t work, and many other things are painful. Kava is primarily built in GO which is far superior for financial applications in most respects.
(4) The future is Cosmos. Binance, Okchain, terra, Cosmos Hub(ATOM), and Kava all are created using the Cosmos-SDK framework. I believe this is the future and the blockchain developers are moving to this in mass. Over 110 projects now are building with the Cosmos-SDK.
What are ways by which Kava project generates profit/revenue to maintain project. What is your revenue model?
Answer - Kava is a for-profit financial DAO with over 80 different businesses staking Kava and voting on its evolution. They want to see Kava succeed so they vote to fund operations and developments that drive user growth in Kava. Due to fees paid in Kava and the burning mechanism, as the system grows in users, the Kava supply decreases making those that hold Kava win due to scarcity.
Lending/Borrowing has been introduced by Binance. How can this affect the Kava since people can directly borrow BUSD from Binance with BNB used as collateral than going to Kava?
Answer - Kava will be featured on Binance as well. The main benefit of Kava is that there is no counterparty. The capital is minted on demand not sourced from somewhere. Binance and other centralized parties on the otherhand need to find capital to provide loans, creating a cost of capital. Kava is much more efficient at providing capital and avoids a lot of regulator issues.
I'll add I think BUSD in the future might be usable for collateral to Kava's loans as well. It would be cool 🙂
What's your opinions on Future of DeFi & DApps? Do you think that DeFi is the future of current Financial world? Also, How do you see the future of KAVA?
Answer - I believe Centralized Finance and the existing infrastructure has a place. It has a lot of issues that cause things like the 2008 crisis and the current insolvency issues that are happening across the world due to trust-based debt with no actual backers other than the people which end up bailing out banks and other financial institutions that have made poor decisions.
DeFi's future is bright because it solves this fundamental issue. It removes trust and adds transparency. Kava is right at the foundation for all of DeFi as things grow and mature.
Recently, we have seen some big hacks in DeFi platforms. How will KAVA deal with these bad actors of crypto and what security measures have been taken by KAVA for the safety of users' funds?"
Answer - Unlike a lot of DeFi startups, we take things seriously. We don't ""move fast and break things"" as Mark Zuckerberg would say.
We do a thorough analysis before suggesting to deploy code. Our internal team works very hard to run tests and simulations, once it passes internally, we give it to 3rd party auditors who try and game it and break the code. If it passes there, we give the code to the community to review and vote into the mainnet. In this way, I’d estimate about 100+ people review our code and test it before it goes live and consumers can touch it. I don't know many other project teams that due things with such diligence.
Binance for KAVA is a very valuable partner in terms of increasing the number of users, but what is KAVA ready to give equivalent to Binance users? What applications will be integrated into Binance to expand the ecosystem?
Answer - Kava gives the BNB users loans. It gives the DEX a stablecoin and the ability to offer margin products. Kava’s connection to binance chain and chainlink data also enables Binance DEX to offer trustless derivatives like options and futures products going forward.
Cosmos has limitations on working with PoW coins. How do you technically solve the problem of implementing DeFi products for bitcoin?
Answer - Cosmos is great for hard-to-work-with blockchains like BTC. It's flexible in how you can construct bridges. For example, the validator set can have a multisig private key split up into pieces in order to create a trustless escrow and control of assets on other blockchains. In this way, we can create peg zones with Cosmos for the best assets in the world. Once a zone is established, it can be used on Kava and other Cosmos chains.
USDX is currently a little-known stable coin. Do you plan to add it to the top exchanges with good liquidity, including Binance?
Answer - USDX will be growing quickly. We have a plan to have it listed and get liquidity across several known exchanges shortly after launch.
There are several options for using USDX on the KAVA platform, one of which is Margin Trading / Leverage. Is this a selection function or a compulsory function? Wondering since there are some investors who don`t like margin. What is the level of leverage and how does a CDP auction work?
Answer - Using Kava for Margin trading is 100% optional. You can choose how you want to use the margin loan. You don’t have to spend the USDX unless you want to. It could be used for everyday payments as well in the case you simply don’t want to sell your underlying collateral. If you don’t want the risk, do small loans with lots of collateral.
Will your team have a plan to implement the DAO module on your platform, as it provides autonomy, decentralization and transparency?
Answer - DAO - Kava is a for-profit DAO and it’s fully functional already. We have on-chain governance and have underwent several votes and evolutions you can look at. You actually can see some current voting processes taking place here: https://kava.mintscan.io/proposals
We recently implemented a cool feature called committees, which enables the DAO to elect a small group of experts to make decisions without needing a vote of the whole user base. This enables the experts to have control over a small portion of the protocol - such as monitoring the debt limit, fees, etc and enables Kava to operate faster and be more adaptable in volatile market conditions.
How can we address the possible overloads and security threats caused by increased users in the DeFi scene?
Answer - Yes, this is a huge issue for Ethereum, MakerDAO and everyone in the space. I don’t see a bright future for DeFi on Etheruem unfortunately. You can’t have a blockchain do everything well. Tether alone congests most of Ethereum and makes oracle price feeds lag the market. This can cause liquidations that should not happen and real people will lose real funds. It’s a huge issue.
The hope is for a dedicated system like Kava to provide a better backbone for DeFi applications going forward.
I should point out that Kava is not just a MakerDao for Cosmos or a CDP for Bitcoin. Kava is designed to be a foundational layer for DeFi services that every new blockchain and application will need.
Every blockchain will need DeFi services like lending, stablecoins, and data and they need it to be very secure. Kava does all this with its cross-chain lending plarform, USDX stablecoin, and Chainlink data in an incredibly secure, but accessible manner.
In this way, Kava aims to connect and serve all the major cryptocurrency communities and build it’s place at the center, where every developer can get what they need to build financial applications of the future."
What distinguishes Kava from your existing competitors like Syntetix?
Answer - Synthetix isn't really a competitor, but it is an interesting project in terms of mechanism design. We share a lot of common investors and have similar token economic ideas with them. The only blockchain project that could be is MakerDAO, but they can only work with ETH assets due to their design. We are focused on the major cap assets - BTC, BNB, XRP, ATOM and others have a much larger market than ETH to address. BTC is 10x the size alone. Currently no one serves them with DeFi. We’re going after this opportunity and believe it to be a huge one.
Why is the KAVA coin not used for Mint, why am I asking that because I see it can also make the value of KAVA coins grow naturally?
Answer - Why is Kava not used as a collateral? Well, it could be I suppose. The community might vote for this in the near future if they want us to be like synthetix. It makes the Kava token more valuable and it will incentivize much more locked-up Kava reducing overall circulating supply which is fairly favorable. The main reason we have not done this yet is that we(Kava and its community) are still weighing the risks of doing this given that Kava also functions as a reserve asset. I think it's likely Kava gets added as collateral at some point, but it will likely have a high debt-collateral ratio to address the issues similar to Synthetix which is 750%.
How do you prevent in a manipulated KAVA Mint just to take advantage of a token prize when minting?
Answer - Minting rewards and manipulation. We’ve thought of this. Each week, the blockchain counts all the blocks, counts how many people had a loan in that period, then takes the average loan amount over time to calculate the rewards. If you open and close a loan - you will get very little rewards. You only get a large reward if you keep the loan open the full period.
Who are your oracle providers? Are you also an oracle provider?
Answer - Kava may run 1 oracle in the future, but we will always have many and be the minority. Most chainlink oracle node operators are large players in the space that run staking infrastructure companies like cosmostation, chainlayer, chorus one, figment networks, etc. Binance will also be one of our oracles.
If we look at all the different types of DeFi products _(decentralized exchanges, stablecoins, atomic swaps, insurance products, loan platforms, trade financing platforms, custody platforms, and crowdfunding platforms) currently covering important areas of traditional finance...where does Kava fit in?
Answer - To make any interesting financial product work you need capital, a stable store of value, and price data. These are really hard to get on current blockchain environments. Kava provides all of these.
Many people describe Kava as similar to Maker (MKR). How is Kava different? Why do you think Kava has more potential?
Answer - MakerDAO is a smart contract with a singular purpose, to serve ETH. It sadly inherited the problems of ethereum. Kava is designed from the ground up for security and interoperability. We are targeting bigger and better assets and have more capabilities to serve them with what their developers and ecosystem need.
What is the uniqueness of KAVA project that cannot be found in other project that´s been released so far ?
Answer - Well in June 10th, we will be the first ever blockchain project to bring DeFi to another blockchain in a real way. BNB users will have loans, stablecoins, and much more.
The gas fee is an issue for blockchain besides scalability. Does your Kava provide a solution for gas?
Answer - gas fees are very low on Kava, only high enough to prevent spam. We dont need high fees for TX because validators are paid in block rewards. Additionally, we dont have competing transactions from crypto-kitties or other non-financial applications. This leaves all of Kava's throughput 100% dedicated to scaling financial transactions.
Kava project works on DeFi (Decentralized Finance) But what’s the benefits of Decentralized Financial system? What are the possibilities of DeFi over Centralized Finance system?
Answer - Open access, no need for trust, and no censorship by singular governments or parties. Kava is accessible anywhere in the world, by anyone.
Data supplied by oracles are false at times, how do you prevent this? How reliable are data received by KAVA?
Answer - This is why using premium / credentialed APIs is important for oracles. These data sources tend to be more accurate and better managed. Wrong prices can happen - for liquidation systems like Kava, we factor this into our design by using an average of data overtime form all oracles as part of the calculation.
Can anyone become a KAVA validator, or is it just an invitation from the project itself? What are the requirements for becoming a KAVA verifier?
Answer - Anyone can become a validator, but you will need to stake or have enough stake delegated to you from others to be in the top 100 validators to earn block rewards.
DEFI PULSE said that a total of 902M is currently locked. According to you, how will this number change in the next few years, and how will KAVA position itself as the top player in this market segment?
Answer - DeFi will only grow through 2020. And likely grow massively.
All projects on DeFi pulse are ""ethereum"" based. Kava is going to shake the blockchain world in the next few weeks by being the first ""multi-chain"" project on DeFi pulse and by my estimations we should quickly surpass a lot of the projects on that list.
I am an testnet minter and the process seem Simplified, now I want to know if minting of USDX will continue when you launch Mainnet and do you have plans to build your own KAVA WALLET for easy minting on your mainnet
Answer - Simple blockchain experience?! high praise! Yes the process will be the same. Kava will not provide interfaces or wallets. Kava Labs builds software for the blockchain, our community members like Cosmostation, Frontier, Trust Wallet build support for people to interact with it.
What business plans does Kava have with Seoul (South Korea) after partnering with Cosmostation? Do you plan to expand your products beyond Asia? Have you thought about harnessing the potential of South America?
Answer - South Korea is a perfect market for Kava's DeFi. Regulations prohibit fiat-backed stablecoins and margin trading. Kava's platform uses crypto-backed stabvlecoins and can enable users to get loans to margin trade. I am looking forward to further developing the Korean market for Kava, working with close partners like Cosmostation and showing the world real use cases of DeFi.
Thank you for taking the time to conduct this AMA. Do you have any parting words, and where can the people go to keep up with all of the new happenings regarding Kava Labs?
Answer - Thanks for all the awesome questions! Amazingly thoughtful!
I've been promising the world cross-chain DeFi since June of last year. The IEO and mainnet went live Nov 2019. It's been a year of hard work - but an industry first is coming on June 10th. I'm excited. I hope you guys are.
Thanks for having me, I hope you become a USDX minter and get KAVA rewards. And last but not least, I love Binance - it's Kava's first home and I'm really happy to open up DeFi to BNB first.
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.
Hi Bitcoiners! I’m back with the 30th monthly Bitcoin news recap. For those unfamiliar, each day I pick out the most popularelevant/interesting stories in Bitcoin and save them. At the end of the month I release them in one batch, to give you a quick (but not necessarily the best) overview of what happened in bitcoin over the past month. You can see recaps of the previous months on Bitcoinsnippets.com A recap of Bitcoin in May 2019 Adoption
Weekly Update: $WIB, $VID, $CHZ on ParJar, Pynk crushes Web Summit, XIO swap bridge, Sentivate reorg... – 1 Nov - 7 Nov'19
Hi folks! We are catching up real quick. Here’s your week at Parachute + partners (1 Nov - 7 Nov'19): Three new projects and their awesome communities joined the Parachute fam this week: Wibson, VideoCoin and Chiliz. Welcome! And if you missed, we also added Shuffle Monster, Harmony and CyberFM last week. #cryptoforeveryone is getting bigger by the day. Woot woot! In this week’s TTR trivias, we had Richi’s movie quiz qith a 25k $PAR pot. Charlotte's Rebus trivia in TTR on Tuesday had 25k $PAR in prizes for 10 Qs. Noice! Jason’s creative contest for this week was #artdeadmin: “draw/paint/sketch/whatever you imagine a group of the parachute admins doing together”. Click here to check out some of the entries of the TTR Halloween photo contest from last week. Doc Victor (from Cuba) hosted a Champions League wager round in tip room. And congrats to Victor (Anox) for passing his final Medical exams. We have 2 Doc Vics now. One from Cuba and the other from *redacted*. Some of the top #artdeadmin submissions. Insane talent! Jason’s running medal collection. Say what! Andy shared the latest standings in the Parachute Fantasy Football League (#PFFL). Clinton (7-2) is on top followed by Chris (7-2) in second place and Hang (7-2) in third place. So close! As we rolled into November, Parachute crew signed up for Movember. So now we have 3 teams from the Parachute fold, doing a no-shave November for men’s health issues: Parachute (Tony, Cap, Alexis, Cuban Doc Vic, Richi), TTR (Vali, Ashok, Tavo, Alejandro, Marcos, PeaceLove) and TTR-Ladies (Mery, Martha, AngellyC, Liem, Durby, LeidyElena, Charlotte). Show them some support peeps! This is all for charity. Show them some support folks! This week’s #wholesomewed was about “your most precious possession and give us the story of why it is so precious to you”. A whole lot of $PAR was given out for some real wholesome life stories. Best. Community. Eva! Two-for-Tuesday theme for this week: colors! As always, a melodic Tuesday thanks to Gian! And thank you Borna for writing about Parachute and ParJar on the Blockchain Andy blog. <- This is where Jose creates his magic. Respect / Cuban Doc Vic’s doggo, Symba, could easily be a TTR mascot. Good boi! -> This week at aXpire there were two separate $AXPR burns: 20k of last week and 200k of this week. Last week’s news recap can be seen here. Congratulations to the team for being conferred the honour of being handed a key to Miami-Dade County by Mayor Carlos A. Gimenez at the 2019 Miami-Dade Beacon Council Annual Meeting & Key Ceremony. aXpire's disruptive solutions like Resolvr (expense allocation), Bilr (invoice management) and DigitalShares (deal marketplace) help hedge funds and PE firms scale through better profit margins. How? Read here. Did you know that the 2gether Ambassador Zone lets you customise referral messages with a #PicOfTheDay while you earn some sweet 2GT rewards? Super cool! There was an upgrade to the platform this week that might have led to a temporary deactivation in withdrawals while the update was being deployed. CEO Ramón Ferraz’s interview by BeInCrypto was released. Founder Salvador Algarra travelled to an ABANCA event for a keynote speech on Fintech innovation. Next week he will be at Rankia's Blockchain and Crypto Tech gathering to speak on "Blockchain, from predicting the future to building it". CardRates’ feature article on 2gether came out this week. The BOMBX:XIO token swap bridge went live. The swap will be open till 15th December. Plus, $XIO is now listed on DDEX and Switcheo. There were some disruptions in the bridge from time to time because of heavy traffic. Hence, the team also set up a manual swap page as an alternative solution. And please be wary of scammers posing as admins to help with the swap instructions. For any doubts, always reach out to accounts with admin tags on the official Telegram channel. The first set of incubated startups will be revealed on the 22nd of November. Ever wanted to find out about the people who frequent the BOMB token chat? Well, the BOMB Board is running a "Humans of Bomb" series to feature some of the most active members. This week, say Hello to Gustavo. Key to Miami-Dade County awarded to aXpire. Cool! WednesdayCoin’s founder Mike floated the idea of making WednesdayClub open on all days. The nature of the $WED token will not change on chain. Just that it will be usable inside the DApp everyday. What do you think? Let him know in the Reddit thread. Birdchain’s $BIRD token was listed on Mercatox this week. A new monthly referral contest was launched as well. 50k BIRD tokens to be won. Nice! Want the SMS feature to be released in your country? Start promoting! A featured article on Chainleak capped off the week perfectly for Birdchain. $ETHOS, $AXPR (aXpire), $HYDRO, $BNTY (Bounty0x) and $HST (Horizon State) were added to the eToro Wallet. The airdrops for Switch’s various token holders were distributed this week. As mentioned earlier as well, $ESH and $SDEX are revenue sharing tokens. Winners of the John McAfee contest and trading competition were announced. Congratulations! Tron blockchain support will be added to the Switch-based McAfeeDex next week. The news was covered by Beincrypto, U Today, Crypto Crunch, Altcoin Buzz and Tron’s Justin Sun as well. The Dex was featured in a Forbes article about John McAfee’s views on Libra. The latest community contest at Fantom involves writing educational articles on the platform. If you have been following Fantom developments, then this would be a breeze. Also, USD 100 in FTM tokens to be won. Sweet! Check out the cool $FTM merch on display at Odd Gems fashion. Even though these are not official gear, they have the blessings from the project. CMO Michael Chen sat down for an interview with Crypto Intelligence India to talk about the upcoming mainnet launch. The crew also appeared for an AMA with Atomic Wallet community. The latest technical update covers "Golang implementation of Lachesis consensus" or Go-Lachesis in short. Check out its demo with 7 nodes here. Parachute presentation (WIP). That’s right. 500k transactions and counting. Wow! While the Uptrennd Halloween contest got over last week, AltcoinBuzz made a friggin amazing graphic! Don’t forget to follow the Ann channel to stay up to date with the latest from Uptrennd. Founder Jeff Kirdeikis also announced that he will be working closely with PrefLogic on Security Tokens. Jeff’s interview with MakerDAO Biz Dev Gustav Arentoft came out. After some upgrades on Uptrennd, withdrawals are live again. Instead of the weekly meme contest, there was a flyer contest this week. 5k $1UP prize pool for winners. Wicked! The latest community picked TA report was on ETH. And the crew reached Malta for the AIBC Summit. More pics next week! Did you know that you can get Opacity Gift Codes for various plans at ShopOpacity.com? If not, make sure to read up on the Opacity October update. Catch up on the latest at District0x from the District weekly. The District Registry was live demo’ed. Looks cool! Hydro crew travelled to the Web Summit in Lisbon to spread word on the project. They were also represented at the Chicago fintech science fair this week. For a summary of the last few weeks gone by at Hydrogen, you can read the Project update and Hydro Labs update. We have covered most of these in previous posts. For the latest scoop on Hydro Labs, there’s always the Ann channel. Silent Notary’s Ubikiri wallet is undergoing upgrades. One of which is, wallets will be auto-named after creation. A ton more upgrades to be released. Sentivate announced a reorganisation in the company in order to devote full focus on Sentivate. The parent company will close and all resources will move to Sentivate. Here’s another use-case story to emphasise the potential of Universal Web. In the latest community vote on Blockfolio, folks voted overwhelmingly Yes on whether they would like to see more explainer articles on web tech. Also, the epic shoutout from Scott Melker (The Wolf Of All Streets) has to be the best thing ever! Updated Sentivate roadmap for next 3 months Pynk travelled to the Web Summit in Lisbon (wonder if they crossed paths with Hydro and SelfKey teams) as an official delegate of the Mayor's International Business Programme and were featured by KPMG. How to catch people’s eyes in a Summit where everyone is trying to grab your attention? With LED back packs. Genius! Such a lit idea, that even Web Summit tweeted it. Woohoo! And then they rocked a series of pitches to get to the big stage. Wins in Round 1 and quarter finals ensured an entry into the semi finals on the main stage. Click here to watch their presentation. Great job guys! Business Insider Poland included Pynk in their list of 12 Fintech companies worth following. The latest Pynk Tank episode delves into deep fakes in political advertising. One of the upcoming features on the platform will be the addition of gold to the daily price prediction tool. Pynk has "absolutely no interest in Bitcoin fanatics, ‘bagholders’ or ANYONE who mentions moons or Lamborghini’s. It’s tacky". This vibes perfectly with Parachute. Read more on Pynk's guide to becoming a super-predictor here. Horizon State announced that it will be resuming business under a new management. Welcome back! The original $HST token will not be supported anymore. The team will be looking into how the token holders are included in the new system. DENGfans, don’t forget to check the mini-projects posted by Mathew in the Telegram channel. Look up #getDENG in the channel. If you’re proficient in excel and VB, get in touch. Shuffle Monster’s $SHUF token is now listed on Dex.ag which acts as a decentralised price aggregator. CyberFM distributed the $CYFM payouts for October this week. Total payout as of 1st Nov is USD 266k+ in crypto. Say what! Pynk’s LED back packs are a stroke of genius OST’s Pepo was the 19th most popular dApp on State of the DApps last week. This week it climbed to the 16th position. Upcoming features on Pepo include video replies, threads and debates. Stay tuned! OST crew was at the Web3 UX Unconference in Toronto to talk all things UX. Next week they will be at ETHWaterloo to present and judge the UX award there. SelfKey’s $KEY token got listed on Hong Kong’s Lukki exchange. Like Hydro, the SelfKey team also attended the Web Summit in Lisbon for networking. If you were there, hope you said Hi. Ever wondered how Distributed Identity keeps your information private and safe when blockchains are supposed to be public? Click here to find out how SelfKey does this. More insight was shared into the Chainlink partnership this week by Constellation CEO Ben Jorgensen. The team attended the Air Force Space Pitch Day where it was selected to pitch the platform to attendees. Go get’em! How and why does Constellation do things? Check out the Constellation Principles. The October update for Yazom covers news such as alpha build of the app nearing completion, ongoing deal negotiation with clients etc. And with that, we close for this week in Parachuteverse. See you again soon. Ciao!
Hiya folks! Happy Diwali to everyone. Here’s your week at Parachute + partners (20 Sep - 26 Sep'19): Tons of quizzes and contests this week at Parachute + TTR. Doc Vic hosted a trivia on medicine and another one on WW2 this week in TTR. A total of 50k $PAR given away. Victor hosted another trivia there too for 25k $PAR. Sweet! The Big Brother contest came to a close with the finale this week. The winner of Big Brother was Michie, who sadly no one picked. So all 21 participants won 5K $PAR each! Another 70k $PAR was given out to other winners. Plus, $202,500 PAR have been awarded in the various Big Brother contests earlier. Huge! Thank you Gian for doing all of this. And did you get a chance to partake in Tiproom’s Mememania? 50k $PAR in prizes – 25k for top 10 winners and another 25k for 100 memes. Next week’s update will feature some of the funniest memes from the contest. Richi hosted a Movie Trivia in Tiproom for a 25k $PAR prize pot for 10 questions. Woot! Looking good Alexis! Catch up on the latest at aXpire from the weekly update video compiled by Joakim. This week’s 20k $AXPR burn can be tracked here. CEO Gary Markham, who sits on the board of Hedge Fund Association, travelled to an HFA event to spread the word on the project. In the last update, we shared that 2gether was hosting a blockchain and tokenization based contest named Crypto Talent in partnership with IEB Spain for students and professionals. Read more about it here. News of the competition was shared on Cointelegraph as well. You can also listen in to Founder Salvador talk about the contest here and here. Check out the 2gether T-shirt that the team wore to the South Summit next week. Neat! CEO Ramon spoke at the Finnovista Pitch Day about FinTech innovation. Salvador’s interview along with a profile of 2gether was published in The Blockchain Land. The winner of the Birdchain Art Contest was announced this week. Congratulations! Plus, some news updates on the app were shared as well. Birdchain Art Contest winner. Wicked! Last week we shared that the $XIO ERC20:BEP2 bridge testnet trials have gone well. Here’s a sneak peek into how it looks. Once activated (condition to the acceptance of the Binance Dex listing application), the bridge will be open for roughly a month*. Dash also talked about 3 marketing mistakes that crypto startups make commonly – paying for PR (earned media > paid media), focus on follower count (organic reach > vanity metrics), airdrops (unless done strategically). If you had questions on how the XIO system will work and help startups scale, then fret not. Zachary wrote an article and video explaining it all. The community also voted this week to opt in for an SMS update option if there were ever one. The $BOMB community survey results are also out. This set the basis for a detailed SWOT analysis of the token. An excerpt from Benjamin’s 4% burn report was published on Coinbeat as well. In this week’s discussion series, Zachary reflects on market movements and the nature of the XIO incubator program. \*[As of today, the switch to Binance Chain has been shelved. $XIO will stay on Ethereum. But there will still be a token swap. Details will be shared in a later update] BOMB survey results show that the community is well distributed across the globe Fantom’s Statheros stablecoin project will be partnering with a South African bank working on a mainnet launch. Initial details of the tie-up were released. The news was covered by CFN as well. CMO Michael travelled to a CFN event in London. Click here for pics. Technical Update #14 came out too. The big exclusive at Uptrennd this week was bagging an interview Andreas Antonopoulos. Awesomeness! Loopring CMO Jay sat down with founder Jeff to talk about the road ahead for the company. In this week’s public vote, the community voted to get TomoChain a free review from Altcoin Buzz. Community member Jackson Jerry took the initiative to deliver a presentation on the platform to thousands of students during a University Blockchain Awareness tour. Writers were in for a treat with the start of an article writing challenge with a 1,750 $1UP prize pool. Say what! Like last week, this week’s Meme Monday event saw some hilarious submissions. Uptrennd also got coverage on Micky News’ PR piece. Noice! Welcome to the Sentivate crew Jack! Learn about domain extensions and universal domain systems in this detailed article and thread by Sentivate founder Thomas. Tech enthusiasts were in for a treat this week with discussion threads on 5G and packet puzzles. The latest District Weekly from District0x covers mostly dev updates from the past week. Classic memes was the theme for this week’s Meme contest :p Old school memes FTW! Lmao Hydro got nominated for the Florin Asia Innovation Award. Good Luck! The Hydrogen dApp store was opened up for beta testers. The store is also open source. Great! Click here to read up on the structure of the dApp store and how it was built. A number of third party partners joined the store this week including 3Box, TotleCrypto and Carbon. General Operations Manager Marcco Paez sat down for an AMA with Crypto Nation to talk about Hydro. Hope you got a chance to get your questions answered. The team was at InsureTech Connect to represent the project. Want to check out an awesome spectacle? Hydro’s article on visualising code activity in decentralised projects has some uber cool visualisations. You could create one too using Gource. The latest developer update summarises all work done in the past week on the dev front. Silent Notary announced the launch of a Consilium system which will be using its own blockchain network (IDL) for legal actions on the platform. This was necessary since the Ethereum chain is anonymous and legal proceedings require identifiable actors. The $SNTR token will continue to exist on both chains (Ethereum and IDL). For more titbits on the update click here, here, here and here. For updates on Ubikiri, make sure to join the ann channel on Telegram started recently. Full list of socials can be found here. The $LAW referral bonus started last week has seen 4000+ wallets receiving the tokens so far with more on the way. Plus, the presale details are now available on the IDL site. Hydro dApp store dev visualisation. Beautiful Last week, the Arena Match community voted to decide which exchange to pursue for a listing of the $AMGO token. DDEX emerged as the winner of the vote. This week, $AMGO got listed on DDEX. Also, the much awaited review of the project by the Uptrennd team was published in two parts (Part I, Part II). Blockfolio and Delta accepted $AMGO for listing on their platforms. Woohoo! Job opening alert on OST: the team is looking for a Product Lead. Apply if you’re up for it. CEO Jason explained how adding friction in early onboarding process helps achieve product-market fit in this tweet thread. Congratulations to SelfKey for becoming an official member of CryptoUK, a self-regulatory trade association based in UK. If you have considered opening an offshore bank account, check out this article on the best countries to choose from. You can make your first move using the Wallet marketplace as well. Hope you took some time out to vote for SelfKey for the Blockchain Identity Management Use Case Award. Constellation’s partnership with the US Air Force was covered by Forbes this week. The team also announced a partnership with StackPath to make node deployment scalable for enterprise clients. Co-Founder Wyatt travelled to USC, Los Angeles, to a Hyperledger meetup to talk about how blockchain protocols can achieve elasticity. Click here to watch his presentation. Bags token launched a 10k $BAGS giveaway contest for helping spread the word on the project. Sweet! The first promo video is up on the BAGS TV YouTube channel. Check it out! An Upcycle Event in the BAGS Bazaar allows you to exchange some of your tokens for $BAGS. This week, they held their 4th Bazaar Upcycle event. And with that, it's a wrap for this week at Parachute + partners. Ciao!
The History, The Current State And The Future Of NavCoin
The History, The Current State And The Future Of NavCoin
This is it. If you're interested to see what NAV is all about, this is the ultimate guide for you. You will learn about the history of NavCoin and how it evolved. You will learn about the current state and features of NavCoin and you will learn about the exciting new features that are planned and coming up in the (near) future. So buckle up, this is going to be a long ride!
Table Of Content
What is NavCoin?
Rebranding to SummerCoinV2 /NavajoCoin
Rebranding to NavCoin
The Current State
Tutorials And Guidelines
Where can you use NAV?
Introduction - What is NavCoin?
NavCoin is a cryptocurrency that has been publicly traded since mid 2014. It's a fork of the latest version of Bitcoin Core with many additional features and functionalities which differentiate NAV from other cryptos.
NavCoin has been one of the first projects to switch to Proof of Stake and is still using PoS to validate and generate blocks. NavCoin didn't have an ICO or a premine. It is self-funded from the beginning and primarily, but not solely maintained by developers of Encrypt-S - the NavCoin Core team (see below for more info about the team).
NAV is trying to simplify cryptocurrencies for the masses. It does this by providing features which make it easy to use like the implementation of OpenAlias, which allows people to send NAV to an email-like address (for example [[email protected]](mailto:[email protected])). It also provides very easy to use desktop and mobile wallets.
NAV also provides optional privacy. You can send transactions publicly or private, as you prefer.
It's block speed is really fast with about 30 seconds per block. Transactions are confirmed as spendable within only 30 second which makes it ideal for retail and e-commerce.
High levels of scalability (260+ transactions per second)
It currently has a market cap of 11.6kk (as of writing) and trades for about $0.18 / 4'872 Sats per NAV. The circulating supply is 64kk with no max supply (with an inflation of about 4%).
Staking NavCoin currently yields about 8–10% of your holdings per year. This number depends on how many NAV are currently staking. The minimum return is about 4% (if every single NAV would be staking).
NAV is available on many different exchanges with the biggest ones being Binance, Bittrex and Poloniex.
Introduction The following chapter will summarize and break down the history of NavCoin in a few sentences. NAV started a long time ago, went through rebrandings and changes of the core team before it became what it is today. SummerCoin NavCoin was initially first introduced under the name SummerCoin on April 23 in 2014. SummerCoin was a fork of the Bitcoin blockchain. It used to have a PoW/PoS hybrid algorithm with a block time of 45 seconds. SummerCoinV2 /NavajoCoin Soon after the initial launch of SummerCoin, the original developer left and SoopY (soopy452000 on bitcointalk) took over as the main developer and rebranded the project to SummerCoinV2 respectively NavajoCoin and introduced new features. The name NavajoCoin was chosen in honor of the Navajo Code Talker. The unbreakable Navajo code was used to encrypt highly classified military information and commands and decrypt the same in WW II. SoopY introduced a technology which allowed sending transactions anonymously and private. This technology was called "Navajo Anonymous Technology". SoopY also released a new wallet and set the Proof of Stake rewards at 10% for the first year, 5% for the second year and 2% for every year after. NavCoin On August 12, 2014, Craig (current lead core developer, pakage on bitcointalk) started to get involved with NAV by helping to set up a website . It was officially announced that Craig joined the core team as a "Wallet & Web Developer" on November 06, 2014. The last tokenswap and restart of the blockchain of NAV happened on May 12, 2016. Soon later, SoopY stopped showing up and Craig stepped into the role of the lead core developer. Since then, Craig has assembled a strong team with which he built NavCoin into what it is today. Currently, Craig and the NavCoin Core team is located in New Zealand and they are actively developing many ground-braking features which differentiate NAV from other cryptocurrencies. You will read more about that later in this article.
The Current State
Introduction The year 2018 has been a thriving year for the NavCoin ecosystem. Despite the USD price of NAV not reflecting it, in 2018 the core team has developed a whole bunch of new features. Also the core content creators published the first official guidelines that function as an orientation guide for community content creators. This chapter will give you an overview of the current team, the features, the prior mentioned guidelines and the community of NavCoin. Core Team  Last year, the core team has grown alot. It contains of developers, content creators and interns. The core team are employees of Encrypt S, the New Zealand's leading blockchain R&D lab. Encrypt S is developing blockchain solutions since 2014 and values building open-source software highly. Craig MacGregor - Chief Executive Officer Craig is the CEO of Encrypt S and the founder of NavCoin. He is one of the world's most experienced blockchain developers. Craig founded NavCoin in 2014 and is developing software for it since then. He has assembled a strong team of like-minded people. Craig also speaks at seminars and conferenced. Some of the companies and conferences he did blockchain education sessions at are Oracle, Xero, Air New Zealand, Blok Tex and trademe. Together with the team, he is also doing a education series on YouTube where he explains upcoming features in-depth for the community. Alex Vazquez - Chief Technical Officer Alex is the CTO of Encrypt S and the most active contributor to the NavCoin core Github. He has incredible knowledge of blockchains and proposes and implements solutions for challenges and features. He supports community developers frequently and answers any questions of the community thoroughly. Like Craig, Alex is developing software for the NavCoin ecosystem for a very long time. Alex speaks at universities at times and educates students about the blockchain technology. Paul Sanderson - Lead Software Engineer Paul is the Lead Software Engineer at Encrypt S. He has a flair for technology. His technical and management skills are perfectly suited for consultancy and investment advising. He also frequently contributes to the NavCoin core source code. Rowan Savage - Senior Software Engineer Rowan is a full stack software engineer with more than a decade experience in developing complex front-end web applications. He joined Encrypt S in February 2018 and has since been involved in the Valence Plattform, the Kauri Wallet and NavCoin Core. You will read more about these feature/projects later. Carter Xiao - Lead UX/UI Designer Carter specializes in user-centric design and is also very talented with 3D animation, motion graphics and programming. One of NavCoins core principle is "Simplifying Crypto" and UX/UI is a very important part of that. Matt Paul - Software Engineer Like Rowan, Matt is a full stack Software Engineer. He joined the core team in Mai 2017 and has since worked on NavPay, NavPi, the Kauri Wallet and NavCoin Core. Kieren Hyland - Chief Strategy Officer Kieren is one of the employees that are working for Encrypt S for a very long time. He is the CSO and is a digital strategist and growth hacker with a passion for new technology and has a lot of experience in online marketing. Laura Harris - Creative Director Laura has a combination of commercial and creative flair. She manages the social media accounts for NavCoin and ensures, that NavCoins' message is always powerful, relevant and distinctive. John Darby - Content Creator John is an internationally awarded Technology and Financial sector marketing communications specialist. He is one of the Core Content Creators for NavCoin. Features of NavCoin  The following features are currently available and have been developed in the last months and years. It is sorted from newest to oldest. Static Block Reward The soft-fork for the enabling of static block rewards have been accepted and became active recently at 5th January 2019. This means, that the block reward was changed from a percentage based reward to a static reward. This will incentivize the stakers to have their node online 24/7 which increased the security of the network. It also aligns NavCoin with the PoSv3 specification. With this implementation, the yearly inflation will be 3.6% currently and will exponentionally decrease because of the static value of the rewards. Every staked block will now give the staker 2 NAV. Depending on how many people are staking, the yearly percentage varies. With the network weight currently being around 20'000'000 NAV, stakers earn around 10% rewards from staking 24/7. Cold staking To provide extra security to participants in the staking process in the NavCoin network, the core team decided to implement cold staking. This allows to store NAV offline and still be able to sign staking inputs. Looking forward, a possible integration into the Ledger Nano S would mean, that one can stake NAV securely from a offline hardware wallet. How cool is that? OpenAlias One of the core principle of NAV is to simplify cryptocurrencies. Many non-technical people are deterred from the long, cryptic addresses used in wallets. When sending funds, you have to make sure that every single letter and digit is correct which is nerve-wracking for the average person. NavCoin has implemented OpenAlias, which allows to transform the wallet address into a email-like form. Everyone can register a name like "[[email protected]](mailto:[email protected])". Funds can then be sent to this name, which makes sending crypto much easier and less error-prone. Community Fund This is the one big feature I was most excited about. NavCoin core has implemented the first fully decentralized community fund. Acceptance of proposals and release of funds is all approved by the decentralized network. No central authority has access to the fund. The community fund enables everyone to propose their ideas to the NavCoin community and to get paid to implement these ideas. Everyone can propose whatever they like (of course there is a higher rate of success if the proposal contributes to the NavCoin ecosystem ;-)). In fact, this article was sponsored by the NAV-Community by voting "yes" for my proposal. The fund works like this: For a fee of 50 NAV, everyone can create and present his idea/proposal to the entire NavCoin network. The fee is here to help prevent spam attacks. Proposals can literally be anything - be it development, marketing or anything else you can some up with. After creating the proposal, everyone contributing to the NavCoin network can then decide if they like the proposal of not. They vote with "Yes" or "No" for the acceptance of the proposal. Voting happens via staking. Every transaction that gets validated by you gives you one vote. This means that the more NAV you are staking, the higher your voting weight is. The proposal stays in the state "Pending" until it is accepted or rejected. To be accepted, a proposal has to have a participation of at least 50% of all staked blocks and at least 75% of these votes have to be "Yes"-votes. Like-wise to be rejected a proposal need 50% participation of the network and 75% of these votes have to be "No"-votes. Additionally, if a proposal didn't pass after 6 voting cycles (about 6 weeks) it is also rejected. After a proposal has been accepted, the creator of the proposal can start his work. When the work is finished, or at in the proposal defined checkpoints, the proposal creator can create a payment request for the full or part of the requested funds. The NavCoin network can then again decide, if the work is what the creator promised to do and vote for the funds or reject the payment request because it was not what he promised. This mechanism ensures, that the funds are only release if the creator of the proposal did what he promised. The NavCoin network decides everything, there is no central authority which makes the community fund 100% decentralized. The community fund is quite new but there have already been some proposals that were accepted like paying for the development & hosting of NAV block explorer, the creation and distribution of NAV car stickers to the community for free (or paid by the community fund), the funding of interns for NavCoin Core, translation of the website into other languages and YouTube videos. What ideas could you come up with? By the way: this article was also sponsored by the community fund :-) Proof of Stake Like said before, NavCoin uses the Proof of Stake algorithm to create and validate blocks. Participants of the NavCoin network can earn rewards by putting their coins to stake and thus validating blocks and securing the network. The reward used to be 4% fixed but recently changed with the implementation of PoSv3. Currently, rewards for stakers that are staking 24/7 is about 10% but it is dependent on how many people are staking. If more nodes come online, this reward will go down. If 90% of all NAVs would be at stake, stakers would still earn 4%. Tutorials And Guidelines  The NavCoin Core team pushes the community to contribute to the NavCoin ecosystem constantly. They emphasize that NavCoin is an open source project and everyone can contribute. The team tries to make it as easy as possible for the average person to contribute and thus created different tutorials and guidelines. Tutorials To Contribute To The Website The whole website is open source. Everyone can contribute to the website. The team created different guides for people to follow . The NavCoin Developer Manifesto The content creator core team has build a developer manifesto. It defines the values that should be uphold like for example that they will always operate in the best interest of the network. If defines the principles, purposes, scope of involvement and operational requirements . The NavCoin Content Creation Manifesto Similar to the developer manifesto, there is also a content creation manifesto. Again it defines the principles for creating content, the purpose, the scope of involvement and the operational requirements . NavCoin Brand Guidelines In addition to the content creation manifesto, there is also a brand guideline booklet. This should help content creators to create images, videos, articles etc. in the same style as the core team. It defines the NAV brand. The brand guidelines contain definitions, the language to use (words to use, words not to use), the tone of voice, what the community aspires to be and what we discourage to be. It also contains the logo pack which can be used in graphics etc. It describes correct logo spacing, logo placement, the colors of NAV and different web assets. It gives tips about gradients and overlays, the typefaces (with a font pack) and many more. Check it out yourself . NavCoin Educational Series The core team has decided to actively involve the community in the creation of new features. For this reason and to allow users to ask questions, they created the NavCoin Educational Series. The core team schedules an online live meetup which can be joined by everyone. On YouTube they do live-streams and explain upcoming features. Examples of these series are explanations for cold staking, static rewards (PoSv3) and the community fund. The community can ask questions live and the core team will answer them immediately. Community During the last year there have been an influx of software developers from the community starting to create features for NAV. navexplorer.com An examples is navexplorer.com which is programmed by community developer prodpeak and is a block explorer for NavCoin. Additionally, it functions as a interface to see what is going on in the community fund. It shows pending proposals and payment requests. NEXT Wallet The NEXT Wallet is an alternative wallet for NAV and other cryptocurrencies. It has a beautiful user interface and is additionally the easiest interface to interact with the community fund (create proposals, create payment requests and vote for proposals and payment requests). It is programmed by community developer sakdeniz who put hundreds of hours into it during last year. There were also some marketing activities starting to emerge with the release of the community fund. Some of these were for example free stickers for everyone in the NAV community to stick to their car / shop / window etc. or YouTube videos of CryptoCandor and Cryptomoonie that explained the details of NAV. I am sure, that with the 500'000 NAV available in the community fund per year there will be an influx of gread ideas - development as well as marketing activities - that will be funded.
Introduction These features are planned for the future. Many of the following features are part of the 2019 roadmap. Some will not be described in great detail because not much is known about them yet. I've still listed them as they are part of what is yet to come. Features Rimu - Improved Privacy Solution NavCoin used to be a optional privacy coin. That means, that you could choose to send a transaction in private. NavCoin was criticized for the way it handles private payments because it relied on a few servers which didn't make it that decentralized. The technology was called "NavTech" and was a secondary blockchain that obscured the transaction and the amount that was sent. NavCoin Core is currently developing a new improved privacy solution that will make the private payment system completely trustless and districuted and runs at a protocol level. Alex of the NavCoin Core team has published a paper that describes this new privacy solution. It's called Zero Confidential Transactions and can be found here: https://www.researchgate.net/publication/330366788_ZeroCT_Improving_Zerocoin_with_Confidential_Transactions_and_more. What I want to highlight is the collaboration between Alex as the proposer of the solution and the Veil team, a Bitcoin Core developer and Moneros main cryptographer as reviewers. When the best work together, it will be interesting to see what the outcome is! Valence Plattform  Valence is an applied Blockchain platform that can help businesses realise the tangible benefits of blockchain. You can think of Valence as a platform with which you can build Anonymous Distributed Applications (aDapps) with. But Valence is a different kind of platform that enables developers to create new types of blockchain applications. The problem with current (turing complete) dApp platforms are their complexity and rigid nature. Security holes in smart contracts and scaling issues happen frequently . Valence provides transitional pathways that let businesses migrate only part of their activities to the blockchain without having to restructure their entire business model .
Valence will provide a spectrum of blockchain application solutions which sit along the decentralized spectrum, offering businesses simple ways to dip their toes into the blockchain at minimal risk or complexity .
Thanks to the proof of stake nature of the Valence blockchain, more of a node's resources can be used for processing and routing application data which makes the platform faster and scalable.
Valence aims to make building blockchain applications as accessible to the general public as WordPress or Squarespace has made building websites.
The developers NavCoin and Valence aim to make Valence extremely easy to work with:
A Valence application could be an open source mobile or web application that submits unencrypted or encrypted data directly to the blockchain. The only configuration necessary for the app developer would be setting up the data structure. Once they've done that they can start writing to the blockchain immediately. The Valence blockchain interface is language agnostic, meaning developers are free to build applications in whichever language they're familiar with, which greatly reduces the barrier to entry. As the platform progresses, Valence will introduce more and more smart contract templates in collaboration with the development community. These will be like plugins that users can simply select and configure for their application, without having to reinvent the wheel and risk contract errors or spend countless hours of research to program them.
NavShopper The following information is taken from the latest weekly news: NavShopper is a new project which will allow people to spend NavCoin on a growing list of retailers and service providers. NavShopper sits between traditional retailers accepting fiat and NavCoin users and purchases products on behalf of the user by managing the crypt-fiat conversion, payment and shipping. This project will unlock many more ways for people to spend NAV on existing websites/marketplaces without requiring each site to individually accept cryptocurrencies. Some of the prototypes we are working on include crediting your Uber account, buying products on Amazon and donating to charities. Kauri Wallet The Kauri Wallet aims to be an open-source, multi-currency wallet which functions as a foundation for other features. Kauri Enhanced Enhancements to the Kauri Wallet will allow multiple accounts, pin numbers, recurring payments and more. Kauri DAEx The Kauri DAEx is a Decentralised Atomic Exchange that utilises the features of the Kauri Wallet and enables users to create safe peer to peer atomic exchanges for any currency supported by the Kauri Wallet. NavDelta NavDelta will be a payment gateway that allows users to spend NAV at any business which accepts currencies supported by the Kauri Wallet. NavMorph NavMorph is a fusion of Rimu and Kauri DAEx and will allow to privately send every cryptocurrency supported by the Kauri Wallet.
If you have made it this far: Congratulations! You have learned about how NAV evolved, what its current state is and what the future will bring. To sum all up: NavCoin has made incredible progress during last year and released many long awaited features despite the bear market. Many more exciting features are yet to come and it's going to be very interesting to see where we will stand on this day next year.
Unfortunately, the giveaway was not possible in the cryptocurrency-subreddit because of their rules, so I'm doing it here :-) As a surprise, in the next 2 hours I am going to send some NAV to everyone who wants to try out the awesome features and NavPay you read about above. To get your NAVs, all you have to do is the following:
Download the app NavPay from the Android Play Store or as a iOS user, use the NavPay website
Follow the steps to set up your mobile wallet
Backup your private key (the random words) so you could restore your wallet if your phone breaks or something like that!
Post your public address, so I can send you some NAVs
If you liked the experience, I'd be happy to hear back from you :)
Binance users can now buy Bitcoin with practically all of the fiat currencies in existence; Binance, which is one of the leading cryptocurrency exchanges in the world, has partnered with the peer-to-peer crypto exchange Paxful. Via this partnership, Binance users can now use 167 different fiat currencies to buy Bitcoin. Yes, in 2020 there currently is mining software that allows users to mine for Bitcoin on laptops. However, mining directly on Bitcoin’s network with a laptop will almost certainly produce unprofitable mining results. If you want to earn any Bitcoin at all with a computer these days, you’ll have to use additional laptop Bitcoin mining software. Awesome Open Source. Sponsorship. Combined Topics. bitcoin x 📦 📦 📦 📦 📦 📦 📦 📦 📦 📦 📦 📦 📦 📦 📦 📦 📦 📦 📦 📦 📦 📦 📦 📦 📦 📦 📦 📦 📦 📦 📦 📦 📦 📦 📦 📦 📦 📦 📦 📦 📦 📦 📦 📦 📦 📦 📦 📦 📦 📦 📦 📦 📦 📦 📦 📦 📦 📦 The Top 496 Bitcoin Open Source Projects ... Tribeca - A high frequency, market-making cryptocurrency trading platform in Node.js. Arbitrage. Bitcoin Arbitrage - Bitcoin arbitrage opportunity detector. Binance Triangle Arbitrage - Detects arbitrage opportunities in Binance with triangle arbitrage. Blackbird - Blackbird Bitcoin Arbitrage: a long/short market-neutral strategy. Binance Coin, Tron, and Cosmos were some of the major altcoins that showed signals of an end to the bearish pressure. Much of the altcoin market continued to see red, as Bitcoin defended $10,000 and Ethereum oscillated between $330 and $360 range. Tron in particular could be swept upward to new highs as Sun Genesis Mining picks up pace, and Binance Coin could see further upside as the launch ... Awesome Open Source. Sponsorship. Combined Topics . bitcoin x 📦 📦 📦 📦 📦 📦 📦 📦 📦 📦 📦 📦 📦 📦 📦 📦 📦 📦 📦 📦 📦 📦 📦 📦 📦 📦 📦 📦 📦 📦 📦 📦 📦 📦 📦 📦 📦 📦 📦 📦 📦 📦 📦 📦 📦 📦 📦 📦 📦 📦 📦 📦 📦 📦 📦 📦 📦 📦 The Top 511 Bitcoin Open Source Projects ... Bitseed Core - Bitcoin full node. Bitseed Core comes preconfigured as a Bitcoin full node, allowing you to keep bitcoin running 24/7 without slowing your PC. ⧉ Payments. alexk111/awesome-bitcoin-payment-processors; blockchain/thunder - Off-Chain Bitcoin payments using smart contracts; cryptoapi/Payment-Gateway. Bitcoin/Altcoins PHP Payment ... Binance CEO Changpeng Zhao has apologized for causing concern among the crypto community when he openly spoke about the possibility of a rollback for the Bitcoin blockchain following confirmation of a hack leading to the theft of USD 40 million worth of bitcoins on its platform.. The rollback had caused a sharp backlash, particularly among Bitcoin-only communities, aghast at the very concept ... Binance charges a .1% fee for trades. To keep it simple, I purchased 4 NEO using a market order. If you’re placing a market order, you can choose the percentage of your Bitcoin balance you wish to use to buy NEO. A market order will purchase the maximum amount of NEO available for the Bitcoin amount you’ve chosen to spend. As a result, it ... BTC/USDT Perpetual Binance price chart in real-time. Stats on multiple timeframes, order book, news and trollbox. Coinalyze . Futures Data. Individual Charts; Global Charts; Technical Analysis. Bitcoin Ethereum Ripple Bitcoin Cash Chainlink Binance Coin Litecoin Cardano Bitcoin SV EOS Monero Tron Stellar Lumens Crypto.com Coin Tezos UNUS SED LEO NEO NEM Cosmos Iota VeChain Dash THETA ZCash ...
Bitcoin Price Drop, Coinbase Crash, Raspberry Pi Node, Bitcoin Dominance & The Future Is Here
A very open and revealing conversation with CZ the Founder of the Worlds' largest Crypto Exchange, Binance. Great chat, great times, you don't wanna it! Enter to WIN $100 of BCH! ATTENTION YOU ... Non-Farm Payroll Tomorrow - Live Trading - S&P 500, Bitcoin, Gold/Silver & US Dollar Conquer Trading & Investing 732 watching Live now Bitcoin's Lightning Network, Simply Explained! $10 Of Free Bitcoin, Coinbase Referral: https://goo.gl/qKZMmB ... Make A Full Time Income Day Trading On Binance - Duration: 13:08. CryptoJack 116,166 views. 13:08. What Should You Buy During This ... Binance considered rolling back the Bitcoin chain in order to recover stolen funds. How would that have happened? How likely is it that such a recovery method would be executed in the future? This video is unavailable. Watch Queue Queue. Watch Queue Binance CEO makes bold claim about rolling back Bitcoin to save the 7,000 Bitcoin hacked from the exchange. This video explores the reality of this propositi... Vite ecosystem has a lot to offer and multiple streams for generating returns. In this video I give an overview of the coin and ViteX decentralised exchange and also talk about staking, full nodes ...