Binance Futures Releases API Java SDKBinance Support
Binance Futures Releases API Java SDKBinance Support
Binance joins blockchain-based Shyft Network for FATF ...
Binance Futures Historical Data Now Available Binance ...
Selfish Mining Explained Binance Academy
What Will It Take to Regulate Crypto Exchanges? - CoinDesk
Binance API Documentation
Binance announces Binance Pool, will they also dominate ...
Binance Throws Weight Behind Shyft Network in 'Travel Rule ...
Binance.US Buy & Sell Crypto
How to 51% Attack Bitcoin - Lacker
Ultimate glossary of crypto currency terms, acronyms and abbreviations
How To End The Cryptocurrency Exchange "Wild West" Without Crippling Innovation
In case you haven't noticed the consultation paper, staff notice, and report on Quadriga, regulators are now clamping down on Canadian cryptocurrency exchanges. The OSC and other regulatory bodies are still interested in industry feedback. They have not put forward any official regulation yet. Below are some ideas/insights and a proposed framework.
Typical securities frameworks will cost Canadians millions of dollars (ie Sarbanes-Oxley estimated at $5m USD/yr per firm). Implementation costs of this proposal are significantly cheaper.
Canadians can maintain a diverse set of exchanges, multiple viable business models are still fully supported, and innovation is encouraged while keeping Canadians safe.
Many of you have limited time to read the full proposal, so here are the highlights:
Effective standards to prevent both internal and external theft. Exchange operators are trained and certified, and have a legal responsibility to users.
Regular Transparent Audits
Provides visibility to Canadians that their funds are fully backed on the exchange, while protecting privacy and sensitive platform information.
Establishment of basic insurance standards/strategy, to expand over time. Removing risk to exchange users of any hot wallet theft.
Background and Justifications
Cold Storage Custody/Management After reviewing close to 100 cases, all thefts tend to break down into more or less the same set of problems: • Funds stored online or in a smart contract, • Access controlled by one person or one system, • 51% attacks (rare), • Funds sent to the wrong address (also rare), or • Some combination of the above. For the first two cases, practical solutions exist and are widely implemented on exchanges already. Offline multi-signature solutions are already industry standard. No cases studied found an external theft or exit scam involving an offline multi-signature wallet implementation. Security can be further improved through minimum numbers of signatories, background checks, providing autonomy and legal protections to each signatory, establishing best practices, and a training/certification program. The last two transaction risks occur more rarely, and have never resulted in a loss affecting the actual users of the exchange. In all cases to date where operators made the mistake, they've been fully covered by the exchange platforms. • 51% attacks generally only occur on blockchains with less security. The most prominent cases have been Bitcoin Gold and Ethereum Classic. The simple solution is to enforce deposit limits and block delays such that a 51% attack is not cost-effective. • The risk of transactions to incorrect addresses can be eliminated by a simple test transaction policy on large transactions. By sending a small amount of funds prior to any large withdrawals/transfers as a standard practice, the accuracy of the wallet address can be validated. The proposal covers all loss cases and goes beyond, while avoiding significant additional costs, risks, and limitations which may be associated with other frameworks like SOC II. On The Subject of Third Party Custodians Many Canadian platforms are currently experimenting with third party custody. From the standpoint of the exchange operator, they can liberate themselves from some responsibility of custody, passing that off to someone else. For regulators, it puts crypto in similar categorization to oil, gold, and other commodities, with some common standards. Platform users would likely feel greater confidence if the custodian was a brand they recognized. If the custodian was knowledgeable and had a decent team that employed multi-sig, they could keep assets safe from internal theft. With the right protections in place, this could be a great solution for many exchanges, particularly those that lack the relevant experience or human resources for their own custody systems. However, this system is vulnerable to anyone able to impersonate the exchange operators. You may have a situation where different employees who don't know each other that well are interacting between different companies (both the custodian and all their customers which presumably isn't just one exchange). A case study of what can go wrong in this type of environment might be Bitpay, where the CEO was tricked out of 5000 bitcoins over 3 separate payments by a series of emails sent legitimately from a breached computer of another company CEO. It's also still vulnerable to the platform being compromised, as in the really large $70M Bitfinex hack, where the third party Bitgo held one key in a multi-sig wallet. The hacker simply authorized the withdrawal using the same credentials as Bitfinex (requesting Bitgo to sign multiple withdrawal transactions). This succeeded even with the use of multi-sig and two heavily security-focused companies, due to the lack of human oversight (basically, hot wallet). Of course, you can learn from these cases and improve the security, but so can hackers improve their deception and at the end of the day, both of these would have been stopped by the much simpler solution of a qualified team who knew each other and employed multi-sig with properly protected keys. It's pretty hard to beat a human being who knows the business and the typical customer behaviour (or even knows their customers personally) at spotting fraud, and the proposed multi-sig means any hacker has to get through the scrutiny of 3 (or more) separate people, all of whom would have proper training including historical case studies. There are strong arguments both for and against using use of third party custodians. The proposal sets mandatory minimum custody standards would apply regardless if the cold wallet signatories are exchange operators, independent custodians, or a mix of both. On The Subject Of Insurance ShakePay has taken the first steps into this new realm (congratulations). There is no question that crypto users could be better protected by the right insurance policies, and it certainly feels better to transact with insured platforms. The steps required to obtain insurance generally place attention in valuable security areas, and in this case included a review from CipherTrace. One of the key solutions in traditional finance comes from insurance from entities such as the CDIC. However, historically, there wasn't found any actual insurance payout to any cryptocurrency exchange, and there are notable cases where insurance has not paid. With Bitpay, for example, the insurance agent refused because the issue happened to the third party CEO's computer instead of anything to do with Bitpay itself. With the Youbit exchange in South Korea, their insurance claim was denied, and the exchange ultimately ended up instead going bankrupt with all user's funds lost. To quote Matt Johnson in the original Lloyd's article: “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.” ShakePay's insurance was only reported to cover their cold storage, and “physical theft of the media where the private keys are held”. Physical theft has never, in the history of cryptocurrency exchange cases reviewed, been reported as the cause of loss. From the limited information of the article, ShakePay made it clear their funds are in the hands of a single US custodian, and at least part of their security strategy is to "decline to confirm the custodian’s name on the record". While this prevents scrutiny of the custodian, it's pretty silly to speculate that a reasonably competent hacking group couldn't determine who the custodian is. A far more common infiltration strategy historically would be social engineering, which has succeeded repeatedly. A hacker could trick their way into ShakePay's systems and request a fraudulent withdrawal, impersonate ShakePay and request the custodian to move funds, or socially engineer their way into the custodian to initiate the withdrawal of multiple accounts (a payout much larger than ShakePay) exploiting the standard procedures (for example, fraudulently initiating or override the wallet addresses of a real transfer). In each case, nothing was physically stolen and the loss is therefore not covered by insurance. In order for any insurance to be effective, clear policies have to be established about what needs to be covered. Anything short of that gives Canadians false confidence that they are protected when they aren't in any meaningful way. At this time, the third party insurance market does not appear to provide adequate options or coverage, and effort is necessary to standardize custody standards, which is a likely first step in ultimately setting up an insurance framework. A better solution compared to third party insurance providers might be for Canadian exchange operators to create their own collective insurance fund, or a specific federal organization similar to the CDIC. Such an organization would have a greater interest or obligation in paying out actual cases, and that would be it's purpose rather than maximizing it's own profit. This would be similar to the SAFU which Binance has launched, except it would cover multiple exchanges. There is little question whether the SAFU would pay out given a breach of Binance, and a similar argument could be made for a insurance fund managed by a collective of exchange operators or a government organization. While a third party insurance provider has the strong market incentive to provide the absolute minimum coverage and no market incentive to payout, an entity managed by exchange operators would have incentive to protect the reputation of exchange operators/the industry, and the government should have the interest of protecting Canadians. On The Subject of Fractional Reserve There is a long history of fractional reserve failures, from the first banks in ancient times, through the great depression (where hundreds of fractional reserve banks failed), right through to the 2008 banking collapse referenced in the first bitcoin block. The fractional reserve system allows banks to multiply the money supply far beyond the actual cash (or other assets) in existence, backed only by a system of debt obligations of others. Safely supporting a fractional reserve system is a topic of far greater complexity than can be addressed by a simple policy, and when it comes to cryptocurrency, there is presently no entity reasonably able to bail anyone out in the event of failure. Therefore, this framework is addressed around entities that aim to maintain 100% backing of funds. There may be some firms that desire but have failed to maintain 100% backing. In this case, there are multiple solutions, including outside investment, merging with other exchanges, or enforcing a gradual restoration plan. All of these solutions are typically far better than shutting down the exchange, and there are multiple cases where they've been used successfully in the past. Proof of Reserves/Transparency/Accountability Canadians need to have visibility into the backing on an ongoing basis. The best solution for crypto-assets is a Proof of Reserve. Such ideas go back all the way to 2013, before even Mt. Gox. However, no Canadian exchange has yet implemented such a system, and only a few international exchanges (CoinFloor in the UK being an example) have. Many firms like Kraken, BitBuy, and now ShakePay use the Proof of Reserve term to refer to lesser proofs which do not actually cryptographically prove the full backing of all user assets on the blockchain. In order for a Proof of Reserve to be effective, it must actually be a complete proof, and it needs to be understood by the public that is expected to use it. Many firms have expressed reservations about the level of transparency required in a complete Proof of Reserve (for example Kraken here). While a complete Proof of Reserves should be encouraged, and there are some solutions in the works (ie TxQuick), this is unlikely to be suitable universally for all exchange operators and users. Given the limitations, and that firms also manage fiat assets, a more traditional audit process makes more sense. Some Canadian exchanges (CoinSquare, CoinBerry) have already subjected themselves to annual audits. However, these results are not presently shared publicly, and there is no guarantee over the process including all user assets or the integrity and independence of the auditor. The auditor has been typically not known, and in some cases, the identity of the auditor is protected by a NDA. Only in one case (BitBuy) was an actual report generated and publicly shared. There has been no attempt made to validate that user accounts provided during these audits have been complete or accurate. A fraudulent fractional exchange, or one which had suffered a breach they were unwilling to publicly accept (see CoinBene), could easily maintain a second set of books for auditors or simply exclude key accounts to pass an individual audit. The proposed solution would see a reporting standard which includes at a minimum - percentage of backing for each asset relative to account balances and the nature of how those assets are stored, with ownership proven by the auditor. The auditor would also publicly provide a "hash list", which they independently generate from the accounts provided by the exchange. Every exchange user can then check their information against this public "hash list". A hash is a one-way form of encryption, which fully protects the private information, yet allows anyone who knows that information already to validate that it was included. Less experienced users can take advantage of public tools to calculate the hash from their information (provided by the exchange), and thus have certainty that the auditor received their full balance information. Easy instructions can be provided. Auditors should be impartial, their identities and process public, and they should be rotated so that the same auditor is never used twice in a row. Balancing the cost of auditing against the needs for regular updates, a 6 month cycle likely makes the most sense. Hot Wallet Management The best solution for hot wallets is not to use them. CoinBerry reportedly uses multi-sig on all withdrawals, and Bitmex is an international example known for their structure devoid of hot wallets. However, many platforms and customers desire fast withdrawal processes, and human validation has a cost of time and delay in this process. A model of self-insurance or separate funds for hot wallets may be used in these cases. Under this model, a platform still has 100% of their client balance in cold storage and holds additional funds in hot wallets for quick withdrawal. Thus, the risk of those hot wallets is 100% on exchange operators and not affecting the exchange users. Since most platforms typically only have 1%-5% in hot wallets at any given time, it shouldn't be unreasonable to build/maintain these additional reserves over time using exchange fees or additional investment. Larger withdrawals would still be handled at regular intervals from the cold storage. Hot wallet risks have historically posed a large risk and there is no established standard to guarantee secure hot wallets. When the government of South Korea dispatched security inspections to multiple exchanges, the results were still that 3 of them got hacked after the inspections. If standards develop such that an organization in the market is willing to insure the hot wallets, this could provide an acceptable alternative. Another option may be for multiple exchange operators to pool funds aside for a hot wallet insurance fund. Comprehensive coverage standards must be established and maintained for all hot wallet balances to make sure Canadians are adequately protected.
Current Draft Proposal
(1) Proper multi-signature cold wallet storage. (a) Each private key is the personal and legal responsibility of one person - the “signatory”. Signatories have special rights and responsibilities to protect user assets. Signatories are trained and certified through a course covering (1) past hacking and fraud cases, (2) proper and secure key generation, and (3) proper safekeeping of private keys. All private keys must be generated and stored 100% offline by the signatory. If even one private keys is ever breached or suspected to be breached, the wallet must be regenerated and all funds relocated to a new wallet. (b) All signatories must be separate background-checked individuals free of past criminal conviction. Canadians should have a right to know who holds their funds. All signing of transactions must take place with all signatories on Canadian soil or on the soil of a country with a solid legal system which agrees to uphold and support these rules (from an established white-list of countries which expands over time). (c) 3-5 independent signatures are required for any withdrawal. There must be 1-3 spare signatories, and a maximum of 7 total signatories. The following are all valid combinations: 3of4, 3of5, 3of6, 4of5, 4of6, 4of7, 5of6, or 5of7. (d) A security audit should be conducted to validate the cold wallet is set up correctly and provide any additional pertinent information. The primary purpose is to ensure that all signatories are acting independently and using best practices for private key storage. A report summarizing all steps taken and who did the audit will be made public. Canadians must be able to validate the right measures are in place to protect their funds. (e) There is a simple approval process if signatories wish to visit any country outside Canada, with a potential whitelist of exempt countries. At most 2 signatories can be outside of aligned jurisdiction at any given time. All exchanges would be required to keep a compliant cold wallet for Canadian funds and have a Canadian office if they wish to serve Canadian customers. (2) Regular and transparent solvency audits. (a) An audit must be conducted at founding, after 3 months of operation, and at least once every 6 months to compare customer balances against all stored cryptocurrency and fiat balances. The auditor must be known, independent, and never the same twice in a row. (b) An audit report will be published featuring the steps conducted in a readable format. This should be made available to all Canadians on the exchange website and on a government website. The report must include what percentage of each customer asset is backed on the exchange, and how those funds are stored. (c) The auditor will independently produce a hash of each customer's identifying information and balance as they perform the audit. This will be made publicly available on the exchange and government website, along with simplified instructions that each customer can use to verify that their balance was included in the audit process. (d) The audit needs to include a proof of ownership for any cryptocurrency wallets included. A satoshi test (spending a small amount) or partially signed transaction both qualify. (e) Any platform without 100% reserves should be assessed on a regular basis by a government or industry watchdog. This entity should work to prevent any further drop, support any private investor to come in, or facilitate a merger so that 100% backing can be obtained as soon as possible. (3) Protections for hot wallets and transactions. (a) A standardized list of approved coins and procedures will be established to constitute valid cold storage wallets. Where a multi-sig process is not natively available, efforts will be undertaken to establish a suitable and stable smart contract standard. This list will be expanded and improved over time. Coins and procedures not on the list are considered hot wallets. (b) Hot wallets can be backed by additional funds in cold storage or an acceptable third-party insurance provider with a comprehensive coverage policy. (c) Exchanges are required to cover the full balance of all user funds as denominated in the same currency, or double the balance as denominated in bitcoin or CAD using an established trading rate. If the balance is ever insufficient due to market movements, the firm must rectify this within 24 hours by moving assets to cold storage or increasing insurance coverage. (d) Any large transactions (above a set threshold) from cold storage to any new wallet addresses (not previously transacted with) must be tested with a smaller transaction first. Deposits of cryptocurrency must be limited to prevent economic 51% attacks. Any issues are to be covered by the exchange. (e) Exchange platforms must provide suitable authentication for users, including making available approved forms of two-factor authentication. SMS-based authentication is not to be supported. Withdrawals must be blocked for 48 hours in the event of any account password change. Disputes on the negligence of exchanges should be governed by case law.
Continued review of existing OSC feedback is still underway. More feedback and opinions on the framework and ideas as presented here are extremely valuable. The above is a draft and not finalized. The process of further developing and bringing a suitable framework to protect Canadians will require the support of exchange operators, legal experts, and many others in the community. The costs of not doing such are tremendous. A large and convoluted framework, one based on flawed ideas or implementation, or one which fails to properly safeguard Canadians is not just extremely expensive and risky for all Canadians, severely limiting to the credibility and reputation of the industry, but an existential risk to many exchanges. The responsibility falls to all of us to provide our insight and make our opinions heard on this critical matter. Please take the time to give your thoughts.
[Part 2] KAVA Historical AMA Tracker! (Questions & Answers)
ATTN: These AMA questions are from Autumn 2019 - before the official launch of the Kava Mainnet, and it's fungible Kava Token. These questions may no longer be relevant to the current Kava landscape, however, they do provide important historical background on the early origins of Kava Labs. Please note, that there are several repeat questions/answers.
How do you think about France in Kava market development plan?
What is your next plan to raise awareness among French about Kava?
Answer: It is important to reach many top markets. For countries like France we need to find 1st regulator partners such as Binance that can help provide access to KAVA for users. When our CDP platform launches, we will work through local validator partners to help translate content and work with local users.
We have some great community efforts where people create content for us.
Why did you choose Cosmos instead of Aion, which comes with AVM built on JAVA, which can be accepted by many developers?
Will there be a possibility that one day we will be able to collateralize a privacy coin, such as Monero, on KAVA?
Answer: We like programming in GO, interfaces are OK for Java. Cosmos will also feature a WASM module and EVM later. The Cosmos-SDK is very flexible and it allowed us to choose our own security model. That was unique compared to other frameworks where we had to adopt the underlying blockchains. In Cosmos-SDK we can create our own blockchain.
Re: privacy - you can do some fun things in payment channels to make transactions more private. Such as onion routing clearing and settlement across different nodes. This can be possible in the future, but not our priority now.
The biggest advantage of finance is the efficient allocation of resource allocation. If KAVA connects assets of multiple platforms through the interchain technology, the efficiency across the market will be improved.
But in terms of connectivity, Facebook's Libra, with its centralized giant platform, could be a big threat for the future. Of course, regulatory uncertainty still exists. KAVA wonders what big platform companies think about entering the blockchain field and how they can cope with their competition.
Answer: We think of Kava as a DeFi service that can integrate with wallets, exchanges, and other platforms when users want loans or stable coins for payments. We don't see competition with Libra, but we see lots of users potentially getting into crypto which will be good for the market, good for BTC, and good for Kava.
What will you do with the money after IEO?
What is the most important markets that Kava is focusing?
What is your marketing strategy to approach those markets?
Answer: What will we do with the IEO money? Put it in a bank and keep building. We keep our funds safe in secure accounts that are insured. We always maintain at least 2 years runway in pure fiat to ensure we can survive in any bear market conditions and come out on top in the end.
On mainnet, which function/feature can we expect to see on Kava since i only saw informations about its testnet?
Answer: mainnet will feature KAVA, staking, delegating, validator software, voting and governance / parameter changes. Following mainnet, the validators will vote to enable transactions and the CDP platform. We expect this to be towards the end of the yeaQ1 2020
How does Kava maintain the stability of its stablecoin? Are there any opportunties for outsiders to arbitrage or any other mechanisms to maintain price stabilization?
Answer: Kava users deposit crypto assets as collateral and can withdraw a loan based on the amount they deposited. They must always provide more collateral than the loan is worth. When the value of the collateral drops due to market conditions, before it reaches the value of the loaned amount, the platform will auction off the crypto assets for USDX that is on the market at a discount. Holders of USDX can buy these assets at a profit. This removes USDX from the market and makes sure that the global USDX to collateral in the system remains balanced. Similar to MakerDao, 3rd parties can run "keepers" - very simple implementations which continuously monitors the Kava/USDX credit system for unsafe CDPs, and execute the liquidation function the moment they become unsafe. Keepers can also perform arbitrage on DEX/Exchanges executing trades across the Kava platform and the markets.
Alright! So KAVA is doing DeFi right, could you explain DeFi in layman term to us.
Answer: Decentralized Finance. Finance is really ensuring everything about past, present, and future value of money. You need safe custody and a store of value to keep money you earned in the past safe to be used later when you need it. You need something liquid and easily tradable to be used in the present. And the trickier one is the future - people need to get loans on the assets they have or hedge against the assets they have in order to ensure they can build for a better future. That’s finance.
DeFi is taking all those things and making them open access and unregulated so that regardless if you were born with out an ID, if your credit score is bad, or if the government is trying to censor your actions and limit your spending - DeFi promises to give you a way to get access to the financial products you need.
Could you please briefly explain your projects, and why you choose DeFi as a problem to solve?
Answer: Kava is a cross-chain DeFi platform for cryptocurrencies. Kava offers decentralized loans and stable coins for any other crypto asset such as BTC, XRP, BNB, and ATOM.
DeFi is the killer use case of crypto today. I think most people see this clearly now. We believe providing the basic DeFi services is the very first step that is required before blockchain technology can really become wide spread - so we started here.
Why the name of the project KAVA?
Answer: We started in crypto thinking we would build banking products and we wanted a more relaxed cool name to stand out from other solutions. Turns out Kava means many things.
Kava = Hippopotamus in Japanese
Kava = crow in hindi
Cava = wine region in spain
Kava = a medicinal root you add to Tea
Kava = now a cross-chain DeFi platform
But TLDR - we liked the name and thought it sounded short and sweet.
What do you think of the future of DeFi in this space? Will DeFi one day take over the traditional financial systems? -- any wild guess on when it might happen?
Answer: I think centralized solutions will always have certain advantages and DeFi will also have certain advantages.
But truthfully, KYC is a problem from a user experience point of view. One of the big things with DeFi is there is no need to make people go through a KYC process anymore.
If we imagine a world where USD Is king, or Renminbi is king, or BTC is king. DeFi has a place in all of them because open access to financial services is a basic human necessity.
As we have known, Lending is not the only problem to solve in the whole financial areas, are you planning on going beyond lending? What other financial products are in your pipeline?
Answer: Thats a good #Q .
While we have a lot to solve to offer lending to other crypto assets - we can expand our support to non-crypto assets, to NFT tokens, and other assets.
We also have plans to offer derivatives and other synthetics other than USDX - such as synthetic bitcoin and Yuan. What is exciting about Kava and the oracle system run by validators is that we can leverage this infrastructure around the world to do all sort of things.
One of the more interesting products is creating under-collateralized loans using payment channel (layer-2 tech) of our USDX coin. Two parties can lock funds in payment channels and place bets on the price feeds from the oracles. When the funds reach a maximum threshold, the bet closes. Since a price feed is just a data set, we can have the settlement rules be multiples of the real data. In simple terms we can create 100x leverage products for the craziest of traders 😉
Btw KAVA is a bit unique because it use Cosmos/Tendermint. While other DeFi use Ethereum , why you guys choose Cosmos?
Answer: Cosmos is the future. Even facebook’s Libra consensus design was just a copy of Tendermint. Kava, Binance, the Cosmos Hub and many other blockchains are built on the same Cosmos-SDK framework.
It’s very flexible and soon interoperable. This is a huge advantage over Ethereum. Where system’s like MakerDAO will be forced to develop in a slowly evolving chain like Ethereum and only touching Erc20 assets, Kava will be able to rapidly evolve, program in GO rather than solidity, and interoperate with chains like Binance directly.
We’re very excited to get BNB and BTCB onto Kava’s CDPs and to put KAVA and USDX onto the Binance DEX. This is fairly easy on Cosmos.
I saw in KAVA deck that you guys will use USDX, is it a stable coin? How is it going to work and its relationship with KAVA token itself?
Answer: USDX is an algorithmically stable token pegged to the USD. USDX is the token users recieve when they get a loan from the Kava platform. USDX is collateralized or backed by crypto assets so the Kava platform should always hold more crypto value than the USDX it loans making USDX a very safe store of value even if the market crashes 10x overnight. That is what a stable coin should do.
USDX is special though. Natively, users can spend or trade USDX freely like other stable coins, but the important difference is that 1) USDX is free of censorship and does not require a bank or anything else. 2) USDX can be “bonded” or “staked” providing an interest bearing yield between 2-10% APR. This is substantially more than what I can even get from my bank account.
From your point of view as KAVA team, what would be most anticipated feature in KAVA ?
Answer: Our CDP platform launch later this year. The first USDX will be minted then.
Support of BTC in the CDP smart contracts. No blockchain has supported a real decentralized custody and use of BTC with smart contracts before.
Indonesia is one of the “developing” countries, how is DeFi can help in making a difference in those “developing” countries?
Answer: I can’t speak for developing countries as it’s not my expertise, but DeFi in general is trying to offer the exact same services to EVERYONE. Whether you are in San Francisco or Indonesia, the financial services you should have should be similar. The rates and fees you pay should be the same. DeFi is fair treatment and open access for everyone. That is what’s nice about having things run on a protocol.
Last but no least, since we are doing AMA in Indonesian group, I believed our members wants to know if you are interested in going to Indonesia to expand your community and reach?
Answer: As I said, I have not been before! I am traveling throughout South East Asia for a lot of the year. It is one of my destinations. I hope to meet many of you while I am out there.
Defi companies are growing at a rapid pace, but they're actually smaller than traditional financial institutions. In order for Defy to become a global trend, it must eventually acquire consumers within the traditional financial industry.
Traditional financial consumers, however, have poor technical understanding and want psychological stability through government guarantees such as deposit insurance. After all, what does KAVA think about long-term competitors as traditional financial institutions, and what long-term strategies do they have to embrace traditional financial consumers?
Answer: We think of financial institutions as big honey pots of potential DeFi users. For example, if Kava can offer margin lending at better rates than a bank because there is no middle men or compliance costs, users should want to use that service.
As crypto grows, I believe more FIs will integrate crypto assets and DeFi services. For example, in the US you cannot currently margin trade crypto as a retail user. But it could be possible for a regulated FI to integrate a lending service like KAVA without causing issues with regulators due to Kava having no counter party risk other than the user itself.
MakerDAO is only for ethereum but Kava support multiple assets, is this only difference?
What are Kava main advantages compared to MakerDAO?
Answer: Kava supports multiple assets THAT are on different blockchains. Maker can only support ETH. This is a huge difference. In addtion, the role of Maker is quite likely a security token. It represents fees paid by others. Where in Kava, the token is used in security of the blockchain protocol itself. The holders of Kava have a lot at stake and need it to govern the system. Maker holders have nothing at stake.
I think a huge difference is that with our model being POS and based on validators with slashing if they don't participate our governance participation and management will be much more effective than MakerDao.
Ticket claim for KAVA Launchpad is comming around the corner. This maybe last IEO ticket claim of this year. With this hype and expectation of investors/traders, do you think KAVA will be a big boom to end this year with happy tears?
If someone wants to manipulate Governance function of KAVA by changing voting result by possessing many Validators Node through buying over 51% KAVA of market, what will KAVA team do? Do you think Emergency Shutdown(Maker has this) can be considerd as a solution?
How will USDX be minted and backed on KAVA platform? If its based on uses crypto collateral, how will KAVA team make it stable since the inflation of crypto price?
Answer: I believe Kava to be underpriced currently, especially compared to maker which is 10x the value and serving ETH which is much smaller market than ours.
But I cannot tell you with certain if Kava will boom or bust - only the market can decide that. As with all speculative assets, do your homework and trade at your own risk. We here at kava are very LONG Kava, but we are biased 😉
Stablecoin is the word that I heard everyday, so do you have any plans to release wallet for stablecoin?
Answer: There are already wallets created for Kava that can hold our tokens 😉
My first question is: Why do traders choose to use KAVA instead of margin on exchanges?
My second #Q is: What happens whenKAVA doesn't have enough cash to loan out?
Answer: Traders who cannot get passed KYC can use Kava. Traders who want better rates than exchanges can use Kava. If regulators like in the US prevent margin trading, Kava is a great solution.
Kava creates USDX out of thin air when users withdraw loans. It will only create Kava is the user locks a great value of crypto in the system to back it. When the USDX loan is repaid, it is destroyed. In this way, Kava can scale however big it wants - it will never run out of cash.
i heard as you said before in San Fransisco, Silicon Valley. what is the relationship about Silicon Valley and KAVA? and what will KAVA done in this Q1 ?
Answer: I am born and raised in Silicon Valley. I am blessed to have grown up in this area where lots of tech innovation is. However, I am the only one at Kava that lives here full time. The others on my team are in the Cayman Islands and Cambridge.
San Francisco is a hub for the largest crypto projects - Ripple, Coinbase, Stellar, etc. It's a great place to network with founders and feel inspired to do big things. It is not the best weather here, but the people are focused and extremely helpful if they can be if you aim to do big things.
With regard to minting new USDX, is there any potential chance to against Global financial law? Likewise USDT, issuing money should guarantee deposit of real collateral as I have known.
Answer: USDX is debt. It is not a guarantee, but the protocol's rules state it must have more crypto assets behind it than the # of USDX issued. In this way, rules are better than guarantees. Tether guaranteed 1:1 USD, it turned out not to be true because their funds were seized by regulators. That is impossible in the case of Kava.
What is the uniqueness of KAVA project that cannot be found in other project that´s been released before?
Answer: Cross-chain is unique for us. But most unique is our partners and validator group that is launching our blockchain. We have incredible partners that support our work including Ripple, Cosmos, Arrington, Hashkey, SNZ, Lemniscap, etc.
KAVA was initially planned to launch on Ripple network but later switched to Cosmos Tindermint Core. What is that something you see in Tindermint Core that is not available anywhere.
Answer: We did not plan to launch on ripple and did not launch on "Tinder"-mint. I have a fiance - she would be quite mad.
We did however use the Cosmos SDK - a tool set, to build our blockchain that features tendermint consensus.
Tendermint is just the consensus so I assume you mean the SDK. The SDK is very much "choose your own adventure" you can build anything and design all the spec of your blockchain easily. In this way you choose the tradeoffs that make the most sense for your special application/network
How much portion of USDX is backed from crypto/fiat money ...& please mention why any trader, hodler will prefer USDX over other stable coins?
What are the biggest challenges you expect to face and how do you plan to overcome these challenges?
Answer: 150% of USDX or more is backed by crypto. Traders will use USDX because it offers a savings rate. This rate allows traders heding bitcoin or other assets to not only store value, but earn a return.
What do you think about creating liquidity for the Kava project?
Answer: It's the biggest challenge. My hope is the savings rate USDX offers will give it natural organic demand over existing stable coins. It will definitely be a large BD process to get USDX listed and used worldwide.
We work with some of the worlds best market makers to seed liquidity today. But we will need organic demand in the long-term
So many IEO projects consistently drop in price after listing. Whats different with KAVA, what are some special highlights?
Answer: Why is Kava based on Cosmos? Based on what considerations?
How do you see the chinese language community? How do you view the opportunities for growth in the chinese community?
Answer: You will be soon listing on Binance, what are your plans on the business side after listing? In one years time, what are your thoughts on where Kava's development will be?
If we take a look at all the different types of DeFi products/apps out there, including decentralized exchanges, stablecoins, atomic swaps, insurance products, lending platforms, trade financing platforms, custodial platforms, crowd investment platforms, etc, nearly cover all the important areas of traditional finance.
In this age of all these different platforms taking hold, where does Kava see itself appealing to its app developers, users, investors?
Answer: What does Kava do? What can a normal user (of crypto) achieve by using KAVA?
How does Kava maintain the stability of its stablecoin? Are there any opportunities for outsiders to arbitrage or any other mechanisms to maintain price stabilization
Answer: What is the reason for the IEO price reaching 6x the first round private sale price? How did you come about to reaching this valuation?
What would you be able to do more for Russian-speaking communities and regions?
Answer: one thing to keep in mind is that yes, we do have limitations and regulations to follow when it comes to certain countries and we will adhere to those regulations in hopes of proving ourselves to be a thoughtful and long-term solution. while we may not directly work with some countries, we hope that communities there can understand that we're here focused on being sustainable rather than another project around shorter-term gains.
for myself, I'm actually belarusian myself so I absolutely see the value of working in the CIS/Russian-speaking regions. we'll continue to do AMAs, interviews, and always engage with Russian-speaking communities to better understand what the #Q s, concerns, and thoughts.
If there's anything else we can do in this region and with the @gagarin_ico communities, please let us know!
What are your major goals to archive in the next 3-4 years? Where can we KAVA ecosystem in this period? What are your plans to expand and gain more adoption?
Do you guys feel satisfied by seeing your progresses and achievements till now, when you look back to the day when you have started this project?
Answer: We want to really build out great DeFi products for the masses. I really believe that DeFi will be a major force to allow much more mass adoption for crypto over the coming years. In the sorter term, we want to push out our blockchain and build on top of that our CDP platform, which allows users to trustlessly put collateral onto the Kava blockchain, and receive a loan in USDX that will be also trustlessly administered.
We will then build out more complex products and financial derivatives for crypto users and traders. We have barely scratched the surface in what we can do with DeFi so I can't predict the future, but we want to build products that are pegged to BTC values so that traders have more leverage purely in crypto.
Which one of your milestone do you think was difficult and which was the encouragement that courages you to achieve it?
What were the Minimum and Maximum limit of KAVA tokens that one can be able to STAKE after the Mainnet launch ? And What will be the percentage of reward one gets and will it in future ?
Answer: Good #Q ! Well we've been working on open source cross-chain technologies for a number of years and honestly it can be a pain. I think the Cosmos SDK made it significantly easier to implement the features that we wanted into the software.
I think the largest challenges for Kava are not software based but in market adoption. Makerdao is a great project and they have spearheaded a lot of the work in the lending field. Hopefully Kava can be a very meaningful contributor as well
What if someone fails to repay the debt? Is that KAVA is taking collateral system to enterprise level & if so, what's the plan? How secure KAVA is to safely handle the collateral tokens?
Answer: These CDPs or "collateral debt positions" are always over-collateralized, which means you have to have more asset locked up in the bucket than you can draw from the bucket. The system leaves a margin when the collateral is 'called' to be able to sell off. If the asset cannot be fully redeemed KAVA is minted to cover the balance. Hence KAVA is a 'lender of last resort". This is why its important that we select good initially assets to support 👍
I am very impressed with your voting method, how does it work? Whether users can vote to change things in the platform, are you a programmer with filters to decide what can be voted on and what is not possible?
Answer: Thanks. A lot of this was pioneered with the Tendermint team. Basically voting is entirely open and asynchronous, meaning anyone can submit a proposal to be voted on. All the project in the Cosmos ecosystem are working diligently to expand the space of variable or features that can be modified via this governance method in protocol. For example, we were the first to enable transactions directly via governance in our Testnet-2000!
Where does the interest rate come from for holding USDX specifically & technically?
Answer: Great #Q ! Just like in MakerDAO, lenders of collateral (e.g. BTC, BNB) pay an annual interest rate to borrow USDX. A portion of that interest rate accretes to holders of KAVA, the rest we can apply a 'carrot' for users to adopt USDX. In short, Savings rate is loan interest rate less 'rents' collected from KAVA holders
As far as I understand it KaVa is used both as a staking token and as collateral for Kava stablecoins (UsDX) .Can you talk a bit about the stability mechanism? Can other forms of collateral be used to create Kava stablecoins (a la Multi-Collateral Dai)?
Answer: KAVA will not be used as a collateral type in the CDPs. Collateral types will be assets exogenous to the system, like BTC and BNB. Of course BTC and BNB's value fluctuates. To make USDX not fluctate we ensure there is always more BTC or BNB in the CDP bucket than 'stable' USDX. Therefore BTC could increase or decrease a lot, as long as its less than the 'stable' debt of USDX that you have drawn, the system is healthy and functional 👌
As far as I know, KAVA had 150 Validators in the test. Why do you have so much. Which conditions are your team based on to choose / invite them to stay decentralized, important for a Defi platform like KAVA?
Answer: KAVA mainnet will launch with a cap of 100 validators. We want as many validators as possible. The reason? What if KAVA was run by just you and me. Well that works if people trust us, but its pretty for us to collude and act maliciously. Its harder for 100 people to collude -- its still possible, but harder. And so we put a lot of effort in to promoting a healthy and large validator community, and empowering them to grow their stake in the system
As a developer, which program languages can i use in kava core smart contracts?
2How secure your fully on-chain liquidity protocol & What's is a core Smart Contract ?can you briefly explain.
Answer: Yay developers! 🤓 The Cosmos SDK is currently written in Golang. So thats a good start. What other language would you like to work in?
What do you think of DEFI in the Blockchain space?
DeFi brings many benefits to users, but conflicts of interests with the Bank. What is the solution of kava?
Answer: Defi to me is offering financial primates, the supplies of which are spreadout amongst many participants, as opposed to few. People offer loans on BTC today. Kava's goal is to maximize the amount of counterparties to any loan, thereby 'socializing' the returns on any activiely used financial product
What is the crucial thing, in your opinion,that would increase adoption of KAVA and possibly the rest of crypto. What’s the KAVA economic model and how will it is architecture ensure scarcity of the token and help to growth token price?
Can you tell me more about the new technology that combines the benefits and interactive functions of Cosmos with the DeFi applications you have built?
Answer: Principly what I believe is 'new' about the KAVA tech stack is that we are building a standalone piece of software that treats other network techologies as 'first class citizens'. This means from the ground up our design is mean to easily incorporate and work with other software. A lot of blockchain is a story of "everyone will use my software, because its the best". Kava Labs worked for years against this view while bringing open Interledger to market.
As Per Kava website ! $KAVA was done many partnerships with Big project like Ripple, Cosmos, TenderMint, Hashkey, etc ! So, whats the major reason and benefits of these partnerships to kava project?
Kava Project have their own Mainnet Blockchain So, whats the main work of Cosmos Blockchain in Kava ? Is Kava projects is on Both mainnet and Cosmos OR Kava is just using the Cosmos Blockchain services?
Answer: Working together. Pooling resources and talent to make something bigger! Crypto is still a little fish in a huge ocean of financial services. Kava Labs has always had an eye for inclusivity. Grow the pie!
I have been too involved in KAVA's AMA, I think I know all about your technology.I want to ask a successful person like you why come with cryptocurrencies and blockchain, with talent. There are many other areas for you to choose, so why are you targeting such a risky market?
Answer: Successful ay? hehe. Depends how you define success and what your goals are. I love delivering products to users. Crypto has some fantastic users, and there is still sooo much to be built. I think KAVA has a lot of promise, but there is still so much work to be done and I hope users like you all become producers some day as well
What's the most critical and innovative point of KAVA to ensure users that it is the best under DeFi niche?
How can you compete MakerDAO which has done good number of business with recent market! If I hold KAVA tokens how KAVA leverage the tokens value and make it moon for me? 🙈
Answer: "IF" you hold KAVA tokens now? 😂 Again I think this a markets concern. To the extend that users on other chains begin to trust KAVA brand for loan issuance, and we get some solid adoption of USDX I think we're in a good spot. I would say a benefit of KAVA is that we are FOCUSED. We're not trying to be everything for everyone. This is lending, quite simply, for the large market cap coins -- and that's hard enough
Why KAVA needs to create it's own stable coin, whereas there are are many other options available in the market? Is that crypto tokens can be stable!!?
Answer: Yeah there are a lot of USD backed stable coins that is true. Indeed we have looked around with working together with a number of them. The difference with USDX (and DAI) is that its crypto-collateral backed. Doesnt mean we won't work with others in the future 😉
Processing fees on loans we need to pay in kava or usdx?
Which types of success you've been seen in testnet? Why on Nov 5th you've planned to launch mainnet? How many testnet was processed in the past?
Answer: Three major testnets with some minor iterations therein. Testnet-3000's software was pinned to KAVA mainnet software. That testnet is looking good which is a good indicator for smooth sailing on mainnet launch, we'll see 🤞
DeFi is a hot niche when it comes to crypto/blockchain project! Most of the projects are developing aiming DeFi, How KAVA is looking to contribute in DeFi ecosystem? What will be the approach of KAVA to systemize & increase adoptability?
Answer: DeFi is big. Mostly on Ethereum, which is great! KAVA is for non-ethereum networks 😇
What is the main reason that you think that Cosmos-based Kava zone will present a new validator opportunity :- a complex and multi-faceted governance system that allows differentiation?
Answer: Validator #Q , nice. I believe its important for validators to be able to distiguish there service in multiple ways, not just on security (otherwise they will be treated as a commodity). KAVA present an opportunity for validators to distiguish themselves on the basis of proper governance of system parameters on behalf of their delegating constituents. KAVA is a "lender of last resort", so delegating to a sophisticated validator could lead to better results beyond security.
How is kavas tendermint better than other defi consensus especially with the introduction of etheruem 2.0 which many believe will be better than all others - considering kavas association with ripple, is it possible to foresee defi loans from crypto to fiat ?
Maybe kava partnership with centralised banks?
Answer: IDK about that. But we will be working closely with the great folks over at Ripple, thats for sure!
Adoption is one of the important factor that all sustainable blockchain projects should focus to be more attractive in the invertors' eyes.
Can you tell me what KAVA has done and plan to do to achieve Adoption in the reality, real use cases, our real society?
Answer: Bitcoin is real!? I'm continuously impressed by the demand and size of that network. Help us capture that demand! Really, if we can I think the future looks bright for KAVA!
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.
LIVE Beijing Conference June 22, 2017: English Translation
Me and my partner are going to do English play by play here. Tickets were around 570 each, so if you found this helpful , please donate. 2:10 Checked in. Around 100 guests attending so far. Conference should officially start in 20 mins. 2:30 Conference started. Currently in the Microsoft Beijing Office Lobby. Just introductions so far. The video trailer they played before the conference was quite impressive and in English. 2:32 srikanth Raju is speaking in English. You guys are good for this part. Big point: Microsoft believes in a heterogeneous Blockchain environment for Azure. Mentioned Ethereum specifically coexisting with antshares. 2:41 Skipped Jiang Li, Microsoft senior consultant's section for some reason. 2:45 Feng han is talking about the rise of alipay and transactions becoming electronic. Believes that full automation is the next step. Alibaba is still only half automated in their logistics. Huawei is interested in building smart cities, and will need blockchain. Note: they aren't announcing a partnership. Just talking about it. 2:51 Feng han talking about current internet infrastructure not being safe for the futures smart infrastructure. Then talked about a class offered by a genius cryptography professor, wangxiaoyun at tsinghua. Made a joke about 300x returns since ICO. 2:57 Hongfei Da. Talking about bitcoin and history of crypto. Now talking about founding of Antshares. Discussing dBFT and consensus briefly. Now talking about ICO. State of AntShares: 432 nodes, 1058300 blocks, main env running for 150 days. 352 stars on GitHub. LOL talking about this subreddit specifically now. Coinmarketcap ranking. All assets will be digitized. Two categories: 1. Proof of existence is on the blockchain. 2. Off chain physical assets like IDs, bikeshare locks, intellectual property. Spirit of blockchain isn't decentralization. It is transparency and fairness via publicly agreed upon rules and data. Mantra: digital asset + digital ID + smart contract = smart economy. REBRANDING: NEO smart economy. Green logo Neo contracts with C#, Java/kotlin, python, go NeoX is like an interledger protocol NeoQ is quantum safe encryption NeoFS is a new database layer Emphasized ecosystem partnership with bancor agrello matchpool Missed some points because too fast. Will go back later. 3:28 innospace CEO talking. Selected AntShares to join a pool of 10 companies out of 800 applicants. Best companies get 100x growth. Talked about Neo contracts active dev community and emphasized fintrch fundamental paper. 3:35 Alex norta from agrello. English speaking. Introducing the agrello platform currently. Announced new white paper finished today and ICO occurring now. 3:43 Adam from Coindash. Marketing Coindash as a onestop crypto portfolio that enables social trading and facilitates ICOs. Gives test runs for ICOs and let's you gauge interest. Announcing foray into China with close partnership with NEST partnership. 3:59 they made a reference to the matrix where they all pushed buttons and the screen said, WAKE UP NEO 4:00 break for 30 mins 4:31 restarting. CTO of AntShares speaking. Explaining smart contracts. Telling a story about Coke vending machine software executing a smart contract, except it ate his money because of a malicious party blocking the coin entry. Blockchain is necessary to allow smart contracts to be executed fairly. Neo is different from Eth and fabric because it has static contract calls, deterministic blockchain network calls, and uses oracle's instead of internet API calls. Example, different nodes will have different Google search results based off of IP location. NeoVM vs EthVM vs Docker Dyanmic sharding for NeoVM makes parallel processing scale better than EVM which has static sharding. Variables in NeoVM are determined beforehand and then the sharding is done before computation as opposed to EVM which divides work inflexibly. EVM has high coupling (bad). NVM has low coupling like docker. Execution of contracts depends too much on the nodes and blockchain. This point wasn't too clear. Coupling seems to be a concept that people don't talk about often. Sounds like he was saying that you need to run eth smart contracts on a test blockchain environment while NeoVM allows you to test and run code independent of blockchain. Microsoft offers IDE plugins and compilers to help people develop on the Neo platform. Digital certificate issuance and asset digitization are supported in Neo but not inherently in Eth. Storage layer for contracts is built into Neo. You can give authorization for others to read or write your contract storage space. Also, if your contract has a bug, you can take the data and migrate it to a patched contract. Lastly, allows rental of storage space for contracts. No support for any of the three points above in EVM. Giving example of locking an account for a period of time. Showing decentralized domains. Sounds a lot like Eth name service. 5:21 bijie tech CEO. Talking about Binance ICO. Introducing the Binance team. Binance is a coin to coin centralized exchange. Made a joke about not wanting to ICO but did it after seeing everyone elses valuations. 5:35 fangzhou charity entrepreneur. Became a multimillionaire after getting some ANS. Money is freedom. Now wants to give charity loans to kids that need an operation but parents don't have the money. Because of new Chinese laws only 113 out of 500 NGOs can receive donation money. Therefore the market for charity is undersupplied by organizations that can use the money. 5:46 xiaobai medical founder No fixed location, employees or resources. Wants to make a medical system where people record their illnesses and compare outcomes with other patients to determine what is the best treatment. Can also match patients with doctors. Sounds like a combo of ZocDoc and patientory. 5:55 nest smart fund founder Problems of most funds are lack of liquidity, inability to participate in the invested company, and high management cost. DAO on ethereum was hacked, but NEST wants to do what DAO does but more safely and more transparently. They choose C# ( made a joke about being at Microsoft and using C#). Going to make a nest coin that is redeemable for some of the coins that the project backs. ................................. Questions: what's going to happen to ANS? AntShares will retire and get redistributed as NEO in the new wallet software. You don't have to do anything. No reissue so investors don't get screwed. Exchanges will get contacted automatically. How many devs do you have now? 2 full time devs. They are going to offer NEO bounties on code and hire more. New exchange announcement? Binance ................................. DONE .,.............................. ETH donation address: 0x92CBE3Ae9ECB30Fa52BE536d55616571380c43b5 LTC donation address: LZXsdjZJJBWpAx7VQmQ4turVrvgBJwguru ANS donation address: ARA25KDeQMbcR7nAAjTbbnf3pkW98etD2U
This week in crypto: The biggest news in the cryptocurrency space
News by Coingeek: Noah Bradley As active as the blockchain and cryptocurrency spaces are on a continual basis, it may sometimes be difficult to keep up with everything that’s going on. It’s also difficult to separate the real news from the fluff — those pieces that are only designed to appear noteworthy but that are, in fact, just publicity campaigns. In an effort to provide crypto enthusiasts with an overview of what’s going on, here is a rundown on some of the top stories of the week. Bitfinex and Tether have had another rough week. There was some good news, as well as bad, as the saga over their close relationship and questionable activities continues. On the one hand, Bitfinex has been told by a judge that it won’t have to turn over documents related to those activities for now. The New York Attorney General’s Office wants to know exactly what the two have been doing behind closed doors, and they’re fighting the office over its reported lack of jurisdiction. Until a request to have the case dismissed over those jurisdiction claims can be answered by a judge, Bitfinex can ignore the request. On the other hand, though, neither of the two entities should think that it’s off the hook. While they have been given a brief reprieve in the fight with the New York government, they face a separate one with New York investors. A law firm in the state, Roche Freedman, has filed a class-action suit against Tether for its “fraudulent” stablecoin scheme. Tether’s USDT stablecoin is no longer pegged to the U.S. dollar, as it had been advertised, and the company is accused of using its position to manipulate the crypto market. Alipay was forced to take a defensive stance this week after rumors started circulating that it was now accepting crypto payments. This would have been against the Alibaba-owned payment platform’s own rules and would, according to the company, possibly violate payment financial regulations. Alipay has a strict no-crypto policy that doesn’t permit the platform to be tied in any way to digital currencies. The announcement came after the Binance exchange stated publicly that it was now able to receive fiat payments using Alipay, via a third-party processor, which didn’t sit well with Alibaba. The U.S. Securities and Exchange Commission (SEC) rejected yet another rule change proposal that sought to introduce a crypto-based exchange-traded fund (ETF). This one had been submitted by Bitwise Asset Management and the NYSE Arca exchange at the beginning of the year, and received the same response as have the myriad of other requests — the possibility of market manipulation prevents the SEC from signing off on the proposal. Bitwise has indicated that it might try again, but at a much later date. On October 6, Bitcoin SV (BSV) reached a new milestone. A review of blockchain activity revealed that BSV had surpassed BTC in the total number of transactions per day. That day, BSV saw 290,000 transactions, while BTC saw 288,000. One of the biggest reasons for the increase comes from the difference in transaction fees. An average BTC transaction will set someone back around $51.42, while the average cost for a BSV transaction is just $0.31. If there were any questions about how Bank of America (BoA) views the future of digital currency, things were just cleared up a little. BoA had long been a staunch opponent to anything having to do with crypto, but then began to seek blockchain patents and explore the fringes of the Bitcoin ecosystem. Its latest move leaves zero doubt about what is coming, as it has recently completed a recruitment action that was launched to find a Ripple expert to work in-house. The individual, according to BoA’s LinkedIn job posting, would “lead the project management team for the Ripple Project.” Lichtenstein is still determined to be a leading financial hub, even if that hub centers on digital currency and not fiat. The country’s Parliament just approved a new Blockchain Act, which will give better protection to companies and investors, and will almost certain attract a lot of activity to the mid-Europe country.
From Bitcoin Gold’s hard fork to London’s Fintech Week, here are a few events to keep an eye on.
There are a few ICOs ending and starting this week, keep track of them.
Want to get more involved in the crypto space and be completely aware of what’s going on? Here’s a small list of upcoming events you can attend or monitor, including: Bitcoin Gold to Hard Fork, Blockchain Events: Chainers 2018 (Seoul), TechCrunch Sessions 2018 (Zug), TechCrunch Sessions Ethereum Meetup (Zug), London Fintech Week (London). If you’re looking to increase your crypto wealth or know where all those tokens are coming from, here are a few airdrops occurring this week: CPS-SPACE-INS-LRN, ICOs Ending: WINS-SHR-BITX-EJAC-AMO, ICOs Starting: FNP-BETT-VLUX
Following a 51% hack in May, the BTG project’s team decided to upgrade its network via a hard fork in order to improve network security. This is expected to occur at block 536200 (Est. Date: 1st July). The upgrade will implement the Equihash-BTG PoW algorithm as a replacement for the existing Equihash algorithm, among other changes.
Syscoin (SYS) Holders — CPS Coin Airdrop — Snapshot Date on July 1, 2018
CoinPayments (CPS) is built on the Syscoin blockchain, and aims to power a decentralised marketplace. 6% of the total CPS coin supply will be distributed to owners of Syscoin wallet addresses on the snapshot’s date.
Siacoin (SC) Holders — Space Cash (SPACE) Airdrop — Snapshot Date on July 1, 2018
Space cash is going to be distributed to Siacoin (SC) holders at a 10:1 ratio by the Hyperspace team. The Hyperspace network aims to be a global cloud storage marketplace powered by SPACE.
INS Ecosystem aims to develop a platform to enable direct interaction between FMCG (Fast Moving Consumer Goods) manufacturers and consumers. INS tokens will be distributed via an airdrop to all INS holders based on balances had during April 1, 2018 to June 30, 2018.
Loopring is a protocol for building decentralized exchanges, and will distribute 60% of the LRN supply to all LRC token holders during this airdrop.
WinStars (WINS) — Ends Tuesday July 3, at 13:00 UTC
Start Price: $ 0.2000, Funds Raised $ 3.30 M, Funding Target: 500,000 USD, Funding Cap: 5,000,000 USD, Coins Offered: 103.50 M (69.00%). WinStars is a decentralized gaming platform with a catalogue of gambling resources, built on Ethereum.
ShareRing (SHR) — Ends Wednesday July 4, at 13:00 UTC
Start Price: $ 0.02000, Funds Raised: — , Funding Target: $10,000,000, Funding Cap: $38,000,000, Coins Offered: 3.47 B (52.00%). ShareRing is a decentralized marketplace that enables users to securely access, connect, and pay for services anywhere in the world. Users can share anything from storage space to tools, clothes, jewellery and food with the SHR token being the primary payment method.
BitScreener (BITX) — Ends Thursday July 5, at 00:59 UTC
Start Price: $ 0.06049, Fund Raised: — , Funding Target: 1,000 ETH, Funding Cap: 15,000 ETH, Coins Offered: 139.50 M (31.00%). BitScreener aims to build a financial data and content marketplace on the blockchain. BitX is used as the primary means of payment for services.
EJA Coin (EJAC) — Ends Thursday July 5, at 01:00 UTC
Start Price: $ 0.1000, Funds Raised: $ 500.00 k, Funding Target: 500,000 USD, Funding Cap: 15,000,000 USD, Coins Offered: 150.00 M (60.00%). Eja Coin intends to implement a project that will make it easy for people to invest in Mining.
Amo Coin (AMO) — Ends Saturday July 7, at 01:00 UTC
Start Price: $ 0.002164, Funds Raised: $ 1.74 M, Funding Target: — , Funding Cap: — , Coins Offered: 10.00 B (50.00%). AMO is a project that aims to create and operate the AMO Market, where car data can be shared and exchanged. The AMO coin is set to be used as the primary means of payment within the platform.
FlipNpik (FNP) — Starts Sunday July 1, at 01:00 UTC
Start Price: $ 0.1238, Funding Target: — , Funding Cap: 100,000 ETH, Coins Offered: 350.00 M (35.00%). FlipNpik is a commercial social media platform that is designed to connect shoppers to merchants within their communities.
Bettium (BETT) — Starts Sunday July 1, at 01:00 UTC
Start Price: $ 0.05000, Funding Target: 7,500,000 USD, Funding Cap: 30,000,000 USD, Coins Offered: 600.00 M (60.00%). Bettium is a platform enabling users to engage in p2p sports betting against each other. The platform offers users a series of tools, ranging from machine learning services to help from established experts to improve forecasts and strategy.
VLUX (VLUX) — Starts Wednesday July 4, at 01:00 UTC
Start Price: — , Funding Target: 25,000,000 GBP, Funding Cap: 25,000,000 GBP, Coins Offered: 44.31 M (70.00%). VLUX aims to improve access to affordable, low carbon energy by enabling peers to trade energy between one another via the Verv energy trading platform.
When: July 1–2, 2018 Where: Seoul, Korea As part of the Blockchainer Global Global Tour Series, the 11th tour stops in Korea to provide audiences with a series of talks covering Global Blockchain Regulation & Development, Public Chains, Private Chains & Consortium Chains, and Venture Capital and Token Economy to name a few. There are several notable speakers confirmed, including Patrick Dai (Co-founder, QTUM), Jun Li (Founder, Ontology) and Kim Seong Silk (CTO, Huobi Korea) among many others. The event also includes a Blockchain Projects Pitch Roadshow where teams can showcase their respective projects to investors.
When: July 6, 2018 Where: Theater Casino Zug, Artherstrasse 2–4, Zug, 6300 Switzerland TechCrunch is proud to announce their first event dedicated entirely to blockchain, crypto and the future of the internet. The event will feature a series of talks from industry leaders including Vitalik Buterin (Creator, Ethereum), Jutta Steiner (Co-founder, Polkadot), Joe Lubin (Founder, Consensys), Balaji Srinivasan (CTO, Coinbase) and Changpeng Zhao (CEO, Binance).
When: July 7, 2018 Where: Theater Casino Zug, Artherstrasse 2–4, Zug, 6300 Switzerland TechCrunch will produce the event with support from the Ethereum Foundation and other members of the Ethereum community the day after the TC Sessions: Blockchain event. The meetup will feature Vitalik Buterin (Founder, Ethereum Foundation), Karl Floersch (Developer, Ethereum Foundation), among others. It will cover a range of topics including scaling, protocol improvements, and improvements to consensus mechanisms.
When: July 6 -13, 2018 Where: QEII Centre, Broad Sanctuary, Westminster, London, UK The 5th Annual London Fintech Week starts next week, bringing together a series of key industry speakers across several areas within the Fintech space. The event will include a collection of conferences, exhibitions, workshops, a hackathon, and several networking events throughout the week. Notable attendees include Adam Stradling (co-founder of Bitcoin.com), Anish Mohammed (advisor at Ripple Labs), and Dominik Schiener (co-founder of IOTA) among many others. For a full list of industry speakers and event partners, please click here. The week-long event kicks off on Friday July 6 with a Blockchain Hackathon over the weekend, followed by a series of talks starting on Monday July 9th covering Fintech Disruptors, Capital Markets & Wealthtech on Tuesday, and Blockchain & Crypto-Finance on Wednesday. Thursday is a designated day for investors and startups/ICO participants to showcase their projects, followed by a series of blockchain and legal workshops on Friday. Notably panel discussions during the Blockchain & Crypto-Finance day include: Women in Blockchain — Discussion on the role of women in blockchain, with a closer look at the impact that women are making across the industry. Includes Helen Disney (CEO Unblocked), Dr Jane Thomason (CEO, Blockchain Quantum Impact) and Michelle Chivunga N (Regional Advisor, British Blockchain Association) among others. Linklaters Panel: Blockchain and Financial Services — How Blockchain fits in within the current regulatory environment, as well as its impact on enterprises, business and compliance across users’ digital identities, trust and transparency. Discussion between Ajit Tripathi (Partner EMEA, Consensys Enterprise), Harry Eddis (Partner, Global Co-Head of Fintech, Linklaters), and Clair Wells (Director, Legal and Business Affairs EMEA, Circle). VC/Investor Panel — Discussion on how industry figures and organizations are using blockchain to impact value and growth. Panellists include Ivan Soto-Wright (Founder and Managing Partner, HODL.vc), Andrew Adcock (CMO, Crowd for Angels), and Aditya Nagarsheth (Investor, Red Pill). Blockchain Becoming Real Beyond Finance & Less Regulated Industries — Adam Strading (Co-founder, Bitcoin.com), Ashley Fox (MEP for SW England and Gibraltar, The European Parliament) and Tim Huegdon (Co-founder & CIO, InstaSupply) discuss the impact of blockchain and the growing autonomy of machines on society. Source
Binance Futures will now provide users with historical data to assist with backtesting and trading strategies. The data provided will be year-to-date tick level trading data, including official records of trade times, prices, and quantities. Trade over 40 cryptocurrencies and enjoy the lowest trading fees in America. Crypto exchange Binance announced that it just participated in the blockchain-based Shyft Network to implement its decentralized infrastructure to comply with the Financial Action Task Force (FATF) Travel Rule.In a... New endpoints for Binance Savings: ... The /api/v3/exchangeInfo rateLimits array contains objects related to the exchange's RAW_REQUEST, REQUEST_WEIGHT, and ORDER rate limits. These are further defined in the ENUM definitions section under Rate limiters (rateLimitType). A 429 will be returned when either rate limit is violated. IP Limits. Every request will contain X-MBX-USED-WEIGHT ... Understanding the Bitcoin incentives. Bitcoin is a carefully-balanced game of incentives. In a decentralized ecosystem, aligning the interests of participants is vital to the long-term viability of the network. The incentives that drive nodes to secure the network are mainly financial – in acting honestly, they stand to be rewarded. By attempting to cheat, they miss out on potential revenue ... Binance, the world’s largest crypto exchange group, has chosen the Shyft Network to help address a looming regulatory requirement. News Learn Videos Podcasts Research. Trending. Taproot. Bitcoin ... Fellow Binancians, Binance Futures has released their API Java SDK. You can Binance, one of the world’s leading exchanges is adding yet another project to its ecosystem after launching its own mining pool called, “Binance Pool”. Supported by both Proof-of-Work (PoW) and Proof-of-Stake (PoS) mining mechanisms, Binance Pool will mine Bitcoin initially, before more tokens are added. If Binance were a monopoly exchange, then delisting a cryptocurrency would result in driving it out of the market. Or, if the cost of switching from Binance to another exchange was prohibitively ... Deposit Bitcoin from wallet B into Binance; Exchange it for USDT (takes about 2 hours) Withdraw the USDT; 51% attack Bitcoin, rolling back the chain 2.5 hours, moving the contents of wallet A to wallet C. The attacker now has $4 million of Bitcoin in wallet C and $4 million of USDT; The attacker in this scenario spent $6.5 million to get $8 ...
I’ve Changed My Mind on Binance!! BNB #1 Altcoin!?
How To Trade Bitcoin Cryptocurrency ... 17:31. Coinbase, Binance, & Bittrex - Which Crypto Exchange To Use in 2019 - Duration: 41:22. The Cryptoviser 13,365 views. 41:22. YESS!! BITCOIN SMASHING ... Welcome back to the no BS blockchain channel covering bitcoin, cryptocurrency and everything around FinTech. Episode 9 is with the Ted Lin, CGO of Binance, the most popular and innovating crypto ... CryptoRobert's quick and easy tutorial on how easy it is to send Bitcoin or Ethereum to Binance using GDAX. You read that correctly. ANYONE can use GDAX to quickly fund not just your Binance ... Binance is blocking US residence soon. Are you wondering which alternative Bitcoin and Crypto exchanges to use? If so tune in! Become a CryptosRus INSIDER to gain exclusive insight on the market ... India's Best & Cheapest Crypto Exchange How to Buy Bitcoin in India - Duration: 6:56. Crypto India I क्रिप्टो इंडिया 5,690 views 6:56 Binance Exchange - (5% BACK): ... TOP 5 BITCOIN DECENTRALIZED EXCHANGES (DEX) IN 2020 - Duration: 12:24. Hack Crypto 2,764 views. 12:24. How to Apply for a US Passport 2020 - Get a US Passport in ... How to get started on Binance, tutorial and review by OJ Jordan First steps, placing a buy order, trading Bitcoin and hundreds of Alt coins. 📍 BINANCE LINK: ... 51 videos Play all Create Binance Bot in Python - Cryptocurrency Trader Blockchain Engineer How to Prepare for the Future and Avoid Being Caught the Crash - Robert Kiyosaki & George Gammon ... Como enviar tus Bitcoin o cryptomonedas a un exchange de intercambio como Binance, Bittrex, Bitfinex... https://www.facebook.com/people/Daniel-Garcia/1000095... Chico Crypto has changed his heart regarding Binance? The exchange just acquired Coinmarketcap, and now controls crypto largest data aggregator!! Is 2020 the year Binance gets complete control ...