Bitcoin Gold 51% Attacked - Network Loses $70,000 in ...

Dragonchain Great Reddit Scaling Bake-Off Public Proposal

Dragonchain Great Reddit Scaling Bake-Off Public Proposal

Dragonchain Public Proposal TL;DR:

Dragonchain has demonstrated twice Reddit’s entire total daily volume (votes, comments, and posts per Reddit 2019 Year in Review) in a 24-hour demo on an operational network. Every single transaction on Dragonchain is decentralized immediately through 5 levels of Dragon Net, and then secured with combined proof on Bitcoin, Ethereum, Ethereum Classic, and Binance Chain, via Interchain. At the time, in January 2020, the entire cost of the demo was approximately $25K on a single system (transaction fees locked at $0.0001/txn). With current fees (lowest fee $0.0000025/txn), this would cost as little as $625.
Watch Joe walk through the entire proposal and answer questions on YouTube.
This proposal is also available on the Dragonchain blog.

Hello Reddit and Ethereum community!

I’m Joe Roets, Founder & CEO of Dragonchain. When the team and I first heard about The Great Reddit Scaling Bake-Off we were intrigued. We believe we have the solutions Reddit seeks for its community points system and we have them at scale.
For your consideration, we have submitted our proposal below. The team at Dragonchain and I welcome and look forward to your technical questions, philosophical feedback, and fair criticism, to build a scaling solution for Reddit that will empower its users. Because our architecture is unlike other blockchain platforms out there today, we expect to receive many questions while people try to grasp our project. I will answer all questions here in this thread on Reddit, and I've answered some questions in the stream on YouTube.
We have seen good discussions so far in the competition. We hope that Reddit’s scaling solution will emerge from The Great Reddit Scaling Bake-Off and that Reddit will have great success with the implementation.

Executive summary

Dragonchain is a robust open source hybrid blockchain platform that has proven to withstand the passing of time since our inception in 2014. We have continued to evolve to harness the scalability of private nodes, yet take full advantage of the security of public decentralized networks, like Ethereum. We have a live, operational, and fully functional Interchain network integrating Bitcoin, Ethereum, Ethereum Classic, and ~700 independent Dragonchain nodes. Every transaction is secured to Ethereum, Bitcoin, and Ethereum Classic. Transactions are immediately usable on chain, and the first decentralization is seen within 20 seconds on Dragon Net. Security increases further to public networks ETH, BTC, and ETC within 10 minutes to 2 hours. Smart contracts can be written in any executable language, offering full freedom to existing developers. We invite any developer to watch the demo, play with our SDK’s, review open source code, and to help us move forward. Dragonchain specializes in scalable loyalty & rewards solutions and has built a decentralized social network on chain, with very affordable transaction costs. This experience can be combined with the insights Reddit and the Ethereum community have gained in the past couple of months to roll out the solution at a rapid pace.

Response and PoC

In The Great Reddit Scaling Bake-Off post, Reddit has asked for a series of demonstrations, requirements, and other considerations. In this section, we will attempt to answer all of these requests.

Live Demo

A live proof of concept showing hundreds of thousands of transactions
On Jan 7, 2020, Dragonchain hosted a 24-hour live demonstration during which a quarter of a billion (250 million+) transactions executed fully on an operational network. Every single transaction on Dragonchain is decentralized immediately through 5 levels of Dragon Net, and then secured with combined proof on Bitcoin, Ethereum, Ethereum Classic, and Binance Chain, via Interchain. This means that every single transaction is secured by, and traceable to these networks. An attack on this system would require a simultaneous attack on all of the Interchained networks.
24 hours in 4 minutes (YouTube):
24 hours in 4 minutes
The demonstration was of a single business system, and any user is able to scale this further, by running multiple systems simultaneously. Our goals for the event were to demonstrate a consistent capacity greater than that of Visa over an extended time period.
Tooling to reproduce our demo is available here:
https://github.com/dragonchain/spirit-bomb

Source Code

Source code (for on & off-chain components as well tooling used for the PoC). The source code does not have to be shared publicly, but if Reddit decides to use a particular solution it will need to be shared with Reddit at some point.

Scaling

How it works & scales

Architectural Scaling

Dragonchain’s architecture attacks the scalability issue from multiple angles. Dragonchain is a hybrid blockchain platform, wherein every transaction is protected on a business node to the requirements of that business or purpose. A business node may be held completely private or may be exposed or replicated to any level of exposure desired.
Every node has its own blockchain and is independently scalable. Dragonchain established Context Based Verification as its consensus model. Every transaction is immediately usable on a trust basis, and in time is provable to an increasing level of decentralized consensus. A transaction will have a level of decentralization to independently owned and deployed Dragonchain nodes (~700 nodes) within seconds, and full decentralization to BTC and ETH within minutes or hours. Level 5 nodes (Interchain nodes) function to secure all transactions to public or otherwise external chains such as Bitcoin and Ethereum. These nodes scale the system by aggregating multiple blocks into a single Interchain transaction on a cadence. This timing is configurable based upon average fees for each respective chain. For detailed information about Dragonchain’s architecture, and Context Based Verification, please refer to the Dragonchain Architecture Document.

Economic Scaling

An interesting feature of Dragonchain’s network consensus is its economics and scarcity model. Since Dragon Net nodes (L2-L4) are independent staking nodes, deployment to cloud platforms would allow any of these nodes to scale to take on a large percentage of the verification work. This is great for scalability, but not good for the economy, because there is no scarcity, and pricing would develop a downward spiral and result in fewer verification nodes. For this reason, Dragonchain uses TIME as scarcity.
TIME is calculated as the number of Dragons held, multiplied by the number of days held. TIME influences the user’s access to features within the Dragonchain ecosystem. It takes into account both the Dragon balance and length of time each Dragon is held. TIME is staked by users against every verification node and dictates how much of the transaction fees are awarded to each participating node for every block.
TIME also dictates the transaction fee itself for the business node. TIME is staked against a business node to set a deterministic transaction fee level (see transaction fee table below in Cost section). This is very interesting in a discussion about scaling because it guarantees independence for business implementation. No matter how much traffic appears on the entire network, a business is guaranteed to not see an increased transaction fee rate.

Scaled Deployment

Dragonchain uses Docker and Kubernetes to allow the use of best practices traditional system scaling. Dragonchain offers managed nodes with an easy to use web based console interface. The user may also deploy a Dragonchain node within their own datacenter or favorite cloud platform. Users have deployed Dragonchain nodes on-prem on Amazon AWS, Google Cloud, MS Azure, and other hosting platforms around the world. Any executable code, anything you can write, can be written into a smart contract. This flexibility is what allows us to say that developers with no blockchain experience can use any code language to access the benefits of blockchain. Customers have used NodeJS, Python, Java, and even BASH shell script to write smart contracts on Dragonchain.
With Docker containers, we achieve better separation of concerns, faster deployment, higher reliability, and lower response times.
We chose Kubernetes for its self-healing features, ability to run multiple services on one server, and its large and thriving development community. It is resilient, scalable, and automated. OpenFaaS allows us to package smart contracts as Docker images for easy deployment.
Contract deployment time is now bounded only by the size of the Docker image being deployed but remains fast even for reasonably large images. We also take advantage of Docker’s flexibility and its ability to support any language that can run on x86 architecture. Any image, public or private, can be run as a smart contract using Dragonchain.

Flexibility in Scaling

Dragonchain’s architecture considers interoperability and integration as key features. From inception, we had a goal to increase adoption via integration with real business use cases and traditional systems.
We envision the ability for Reddit, in the future, to be able to integrate alternate content storage platforms or other financial services along with the token.
  • LBRY - To allow users to deploy content natively to LBRY
  • MakerDAO to allow users to lend small amounts backed by their Reddit community points.
  • STORJ/SIA to allow decentralized on chain storage of portions of content. These integrations or any other are relatively easy to integrate on Dragonchain with an Interchain implementation.

Cost

Cost estimates (on-chain and off-chain) For the purpose of this proposal, we assume that all transactions are on chain (posts, replies, and votes).
On the Dragonchain network, transaction costs are deterministic/predictable. By staking TIME on the business node (as described above) Reddit can reduce transaction costs to as low as $0.0000025 per transaction.
Dragonchain Fees Table

Getting Started

How to run it
Building on Dragonchain is simple and requires no blockchain experience. Spin up a business node (L1) in our managed environment (AWS), run it in your own cloud environment, or on-prem in your own datacenter. Clear documentation will walk you through the steps of spinning up your first Dragonchain Level 1 Business node.
Getting started is easy...
  1. Download Dragonchain’s dctl
  2. Input three commands into a terminal
  3. Build an image
  4. Run it
More information can be found in our Get started documents.

Architecture
Dragonchain is an open source hybrid platform. Through Dragon Net, each chain combines the power of a public blockchain (like Ethereum) with the privacy of a private blockchain.
Dragonchain organizes its network into five separate levels. A Level 1, or business node, is a totally private blockchain only accessible through the use of public/private keypairs. All business logic, including smart contracts, can be executed on this node directly and added to the chain.
After creating a block, the Level 1 business node broadcasts a version stripped of sensitive private data to Dragon Net. Three Level 2 Validating nodes validate the transaction based on guidelines determined from the business. A Level 3 Diversity node checks that the level 2 nodes are from a diverse array of locations. A Level 4 Notary node, hosted by a KYC partner, then signs the validation record received from the Level 3 node. The transaction hash is ledgered to the Level 5 public chain to take advantage of the hash power of massive public networks.
Dragon Net can be thought of as a “blockchain of blockchains”, where every level is a complete private blockchain. Because an L1 can send to multiple nodes on a single level, proof of existence is distributed among many places in the network. Eventually, proof of existence reaches level 5 and is published on a public network.

API Documentation

APIs (on chain & off)

SDK Source

Nobody’s Perfect

Known issues or tradeoffs
  • Dragonchain is open source and even though the platform is easy enough for developers to code in any language they are comfortable with, we do not have so large a developer community as Ethereum. We would like to see the Ethereum developer community (and any other communities) become familiar with our SDK’s, our solutions, and our platform, to unlock the full potential of our Ethereum Interchain. Long ago we decided to prioritize both Bitcoin and Ethereum Interchains. We envision an ecosystem that encompasses different projects to give developers the ability to take full advantage of all the opportunities blockchain offers to create decentralized solutions not only for Reddit but for all of our current platforms and systems. We believe that together we will take the adoption of blockchain further. We currently have additional Interchain with Ethereum Classic. We look forward to Interchain with other blockchains in the future. We invite all blockchains projects who believe in decentralization and security to Interchain with Dragonchain.
  • While we only have 700 nodes compared to 8,000 Ethereum and 10,000 Bitcoin nodes. We harness those 18,000 nodes to scale to extremely high levels of security. See Dragonchain metrics.
  • Some may consider the centralization of Dragonchain’s business nodes as an issue at first glance, however, the model is by design to protect business data. We do not consider this a drawback as these nodes can make any, none, or all data public. Depending upon the implementation, every subreddit could have control of its own business node, for potential business and enterprise offerings, bringing new alternative revenue streams to Reddit.

Costs and resources

Summary of cost & resource information for both on-chain & off-chain components used in the PoC, as well as cost & resource estimates for further scaling. If your PoC is not on mainnet, make note of any mainnet caveats (such as congestion issues).
Every transaction on the PoC system had a transaction fee of $0.0001 (one-hundredth of a cent USD). At 256MM transactions, the demo cost $25,600. With current operational fees, the same demonstration would cost $640 USD.
For the demonstration, to achieve throughput to mimic a worldwide payments network, we modeled several clients in AWS and 4-5 business nodes to handle the traffic. The business nodes were tuned to handle higher throughput by adjusting memory and machine footprint on AWS. This flexibility is valuable to implementing a system such as envisioned by Reddit. Given that Reddit’s daily traffic (posts, replies, and votes) is less than half that of our demo, we would expect that the entire Reddit system could be handled on 2-5 business nodes using right-sized containers on AWS or similar environments.
Verification was accomplished on the operational Dragon Net network with over 700 independently owned verification nodes running around the world at no cost to the business other than paid transaction fees.

Requirements

Scaling

This PoC should scale to the numbers below with minimal costs (both on & off-chain). There should also be a clear path to supporting hundreds of millions of users.
Over a 5 day period, your scaling PoC should be able to handle:
*100,000 point claims (minting & distributing points) *25,000 subscriptions *75,000 one-off points burning *100,000 transfers
During Dragonchain’s 24 hour demo, the above required numbers were reached within the first few minutes.
Reddit’s total activity is 9000% more than Ethereum’s total transaction level. Even if you do not include votes, it is still 700% more than Ethereum’s current volume. Dragonchain has demonstrated that it can handle 250 million transactions a day, and it’s architecture allows for multiple systems to work at that level simultaneously. In our PoC, we demonstrate double the full capacity of Reddit, and every transaction was proven all the way to Bitcoin and Ethereum.
Reddit Scaling on Ethereum

Decentralization

Solutions should not depend on any single third-party provider. We prefer solutions that do not depend on specific entities such as Reddit or another provider, and solutions with no single point of control or failure in off-chain components but recognize there are numerous trade-offs to consider
Dragonchain’s architecture calls for a hybrid approach. Private business nodes hold the sensitive data while the validation and verification of transactions for the business are decentralized within seconds and secured to public blockchains within 10 minutes to 2 hours. Nodes could potentially be controlled by owners of individual subreddits for more organic decentralization.
  • Billing is currently centralized - there is a path to federation and decentralization of a scaled billing solution.
  • Operational multi-cloud
  • Operational on-premises capabilities
  • Operational deployment to any datacenter
  • Over 700 independent Community Verification Nodes with proof of ownership
  • Operational Interchain (Interoperable to Bitcoin, Ethereum, and Ethereum Classic, open to more)

Usability Scaling solutions should have a simple end user experience.

Users shouldn't have to maintain any extra state/proofs, regularly monitor activity, keep track of extra keys, or sign anything other than their normal transactions
Dragonchain and its customers have demonstrated extraordinary usability as a feature in many applications, where users do not need to know that the system is backed by a live blockchain. Lyceum is one of these examples, where the progress of academy courses is being tracked, and successful completion of courses is rewarded with certificates on chain. Our @Save_The_Tweet bot is popular on Twitter. When used with one of the following hashtags - #please, #blockchain, #ThankYou, or #eternalize the tweet is saved through Eternal to multiple blockchains. A proof report is available for future reference. Other examples in use are DEN, our decentralized social media platform, and our console, where users can track their node rewards, view their TIME, and operate a business node.
Examples:

Transactions complete in a reasonable amount of time (seconds or minutes, not hours or days)
All transactions are immediately usable on chain by the system. A transaction begins the path to decentralization at the conclusion of a 5-second block when it gets distributed across 5 separate community run nodes. Full decentralization occurs within 10 minutes to 2 hours depending on which interchain (Bitcoin, Ethereum, or Ethereum Classic) the transaction hits first. Within approximately 2 hours, the combined hash power of all interchained blockchains secures the transaction.

Free to use for end users (no gas fees, or fixed/minimal fees that Reddit can pay on their behalf)
With transaction pricing as low as $0.0000025 per transaction, it may be considered reasonable for Reddit to cover transaction fees for users.
All of Reddit's Transactions on Blockchain (month)
Community points can be earned by users and distributed directly to their Reddit account in batch (as per Reddit minting plan), and allow users to withdraw rewards to their Ethereum wallet whenever they wish. Withdrawal fees can be paid by either user or Reddit. This model has been operating inside the Dragonchain system since 2018, and many security and financial compliance features can be optionally added. We feel that this capability greatly enhances user experience because it is seamless to a regular user without cryptocurrency experience, yet flexible to a tech savvy user. With regard to currency or token transactions, these would occur on the Reddit network, verified to BTC and ETH. These transactions would incur the $0.0000025 transaction fee. To estimate this fee we use the monthly active Reddit users statista with a 60% adoption rate and an estimated 10 transactions per month average resulting in an approximate $720 cost across the system. Reddit could feasibly incur all associated internal network charges (mining/minting, transfer, burn) as these are very low and controllable fees.
Reddit Internal Token Transaction Fees

Reddit Ethereum Token Transaction Fees
When we consider further the Ethereum fees that might be incurred, we have a few choices for a solution.
  1. Offload all Ethereum transaction fees (user withdrawals) to interested users as they wish to withdraw tokens for external use or sale.
  2. Cover Ethereum transaction fees by aggregating them on a timed schedule. Users would request withdrawal (from Reddit or individual subreddits), and they would be transacted on the Ethereum network every hour (or some other schedule).
  3. In a combination of the above, customers could cover aggregated fees.
  4. Integrate with alternate Ethereum roll up solutions or other proposals to aggregate minting and distribution transactions onto Ethereum.

Bonus Points

Users should be able to view their balances & transactions via a blockchain explorer-style interface
From interfaces for users who have no knowledge of blockchain technology to users who are well versed in blockchain terms such as those present in a typical block explorer, a system powered by Dragonchain has flexibility on how to provide balances and transaction data to users. Transactions can be made viewable in an Eternal Proof Report, which displays raw data along with TIME staking information and traceability all the way to Bitcoin, Ethereum, and every other Interchained network. The report shows fields such as transaction ID, timestamp, block ID, multiple verifications, and Interchain proof. See example here.
Node payouts within the Dragonchain console are listed in chronological order and can be further seen in either Dragons or USD. See example here.
In our social media platform, Dragon Den, users can see, in real-time, their NRG and MTR balances. See example here.
A new influencer app powered by Dragonchain, Raiinmaker, breaks down data into a user friendly interface that shows coin portfolio, redeemed rewards, and social scores per campaign. See example here.

Exiting is fast & simple
Withdrawing funds on Dragonchain’s console requires three clicks, however, withdrawal scenarios with more enhanced security features per Reddit’s discretion are obtainable.

Interoperability Compatibility with third party apps (wallets/contracts/etc) is necessary.
Proven interoperability at scale that surpasses the required specifications. Our entire platform consists of interoperable blockchains connected to each other and traditional systems. APIs are well documented. Third party permissions are possible with a simple smart contract without the end user being aware. No need to learn any specialized proprietary language. Any code base (not subsets) is usable within a Docker container. Interoperable with any blockchain or traditional APIs. We’ve witnessed relatively complex systems built by engineers with no blockchain or cryptocurrency experience. We’ve also demonstrated the creation of smart contracts within minutes built with BASH shell and Node.js. Please see our source code and API documentation.

Scaling solutions should be extensible and allow third parties to build on top of it Open source and extensible
APIs should be well documented and stable

Documentation should be clear and complete
For full documentation, explore our docs, SDK’s, Github repo’s, architecture documents, original Disney documentation, and other links or resources provided in this proposal.

Third-party permissionless integrations should be possible & straightforward Smart contracts are Docker based, can be written in any language, use full language (not subsets), and can therefore be integrated with any system including traditional system APIs. Simple is better. Learning an uncommon or proprietary language should not be necessary.
Advanced knowledge of mathematics, cryptography, or L2 scaling should not be required. Compatibility with common utilities & toolchains is expected.
Dragonchain business nodes and smart contracts leverage Docker to allow the use of literally any language or executable code. No proprietary language is necessary. We’ve witnessed relatively complex systems built by engineers with no blockchain or cryptocurrency experience. We’ve also demonstrated the creation of smart contracts within minutes built with BASH shell and Node.js.

Bonus

Bonus Points: Show us how it works. Do you have an idea for a cool new use case for Community Points? Build it!

TIME

Community points could be awarded to Reddit users based upon TIME too, whereas the longer someone is part of a subreddit, the more community points someone naturally gained, even if not actively commenting or sharing new posts. A daily login could be required for these community points to be credited. This grants awards to readers too and incentivizes readers to create an account on Reddit if they browse the website often. This concept could also be leveraged to provide some level of reputation based upon duration and consistency of contribution to a community subreddit.

Dragon Den

Dragonchain has already built a social media platform that harnesses community involvement. Dragon Den is a decentralized community built on the Dragonchain blockchain platform. Dragon Den is Dragonchain’s answer to fake news, trolling, and censorship. It incentivizes the creation and evaluation of quality content within communities. It could be described as being a shareholder of a subreddit or Reddit in its entirety. The more your subreddit is thriving, the more rewarding it will be. Den is currently in a public beta and in active development, though the real token economy is not live yet. There are different tokens for various purposes. Two tokens are Lair Ownership Rights (LOR) and Lair Ownership Tokens (LOT). LOT is a non-fungible token for ownership of a specific Lair. LOT will only be created and converted from LOR.
Energy (NRG) and Matter (MTR) work jointly. Your MTR determines how much NRG you receive in a 24-hour period. Providing quality content, or evaluating content will earn MTR.

Security. Users have full ownership & control of their points.
All community points awarded based upon any type of activity or gift, are secured and provable to all Interchain networks (currently BTC, ETH, ETC). Users are free to spend and withdraw their points as they please, depending on the features Reddit wants to bring into production.

Balances and transactions cannot be forged, manipulated, or blocked by Reddit or anyone else
Users can withdraw their balance to their ERC20 wallet, directly through Reddit. Reddit can cover the fees on their behalf, or the user covers this with a portion of their balance.

Users should own their points and be able to get on-chain ERC20 tokens without permission from anyone else
Through our console users can withdraw their ERC20 rewards. This can be achieved on Reddit too. Here is a walkthrough of our console, though this does not show the quick withdrawal functionality, a user can withdraw at any time. https://www.youtube.com/watch?v=aNlTMxnfVHw

Points should be recoverable to on-chain ERC20 tokens even if all third-parties involved go offline
If necessary, signed transactions from the Reddit system (e.g. Reddit + Subreddit) can be sent to the Ethereum smart contract for minting.

A public, third-party review attesting to the soundness of the design should be available
To our knowledge, at least two large corporations, including a top 3 accounting firm, have conducted positive reviews. These reviews have never been made public, as Dragonchain did not pay or contract for these studies to be released.

Bonus points
Public, third-party implementation review available or in progress
See above

Compatibility with HSMs & hardware wallets
For the purpose of this proposal, all tokenization would be on the Ethereum network using standard token contracts and as such, would be able to leverage all hardware wallet and Ethereum ecosystem services.

Other Considerations

Minting/distributing tokens is not performed by Reddit directly
This operation can be automated by smart contract on Ethereum. Subreddits can if desired have a role to play.

One off point burning, as well as recurring, non-interactive point burning (for subreddit memberships) should be possible and scalable
This is possible and scalable with interaction between Dragonchain Reddit system and Ethereum token contract(s).

Fully open-source solutions are strongly preferred
Dragonchain is fully open source (see section on Disney release after conclusion).

Conclusion

Whether it is today, or in the future, we would like to work together to bring secure flexibility to the highest standards. It is our hope to be considered by Ethereum, Reddit, and other integrative solutions so we may further discuss the possibilities of implementation. In our public demonstration, 256 million transactions were handled in our operational network on chain in 24 hours, for the low cost of $25K, which if run today would cost $625. Dragonchain’s interoperable foundation provides the atmosphere necessary to implement a frictionless community points system. Thank you for your consideration of our proposal. We look forward to working with the community to make something great!

Disney Releases Blockchain Platform as Open Source

The team at Disney created the Disney Private Blockchain Platform. The system was a hybrid interoperable blockchain platform for ledgering and smart contract development geared toward solving problems with blockchain adoption and usability. All objective evaluation would consider the team’s output a success. We released a list of use cases that we explored in some capacity at Disney, and our input on blockchain standardization as part of our participation in the W3C Blockchain Community Group.
https://lists.w3.org/Archives/Public/public-blockchain/2016May/0052.html

Open Source

In 2016, Roets proposed to release the platform as open source to spread the technology outside of Disney, as others within the W3C group were interested in the solutions that had been created inside of Disney.
Following a long process, step by step, the team met requirements for release. Among the requirements, the team had to:
  • Obtain VP support and approval for the release
  • Verify ownership of the software to be released
  • Verify that no proprietary content would be released
  • Convince the organization that there was a value to the open source community
  • Convince the organization that there was a value to Disney
  • Offer the plan for ongoing maintenance of the project outside of Disney
  • Itemize competing projects
  • Verify no conflict of interest
  • Preferred license
  • Change the project name to not use the name Disney, any Disney character, or any other associated IP - proposed Dragonchain - approved
  • Obtain legal approval
  • Approval from corporate, parks, and other business units
  • Approval from multiple Disney patent groups Copyright holder defined by Disney (Disney Connected and Advanced Technologies)
  • Trademark searches conducted for the selected name Dragonchain
  • Obtain IT security approval
  • Manual review of OSS components conducted
  • OWASP Dependency and Vulnerability Check Conducted
  • Obtain technical (software) approval
  • Offer management, process, and financial plans for the maintenance of the project.
  • Meet list of items to be addressed before release
  • Remove all Disney project references and scripts
  • Create a public distribution list for email communications
  • Remove Roets’ direct and internal contact information
  • Create public Slack channel and move from Disney slack channels
  • Create proper labels for issue tracking
  • Rename internal private Github repository
  • Add informative description to Github page
  • Expand README.md with more specific information
  • Add information beyond current “Blockchains are Magic”
  • Add getting started sections and info on cloning/forking the project
  • Add installation details
  • Add uninstall process
  • Add unit, functional, and integration test information
  • Detail how to contribute and get involved
  • Describe the git workflow that the project will use
  • Move to public, non-Disney git repository (Github or Bitbucket)
  • Obtain Disney Open Source Committee approval for release
On top of meeting the above criteria, as part of the process, the maintainer of the project had to receive the codebase on their own personal email and create accounts for maintenance (e.g. Github) with non-Disney accounts. Given the fact that the project spanned multiple business units, Roets was individually responsible for its ongoing maintenance. Because of this, he proposed in the open source application to create a non-profit organization to hold the IP and maintain the project. This was approved by Disney.
The Disney Open Source Committee approved the application known as OSSRELEASE-10, and the code was released on October 2, 2016. Disney decided to not issue a press release.
Original OSSRELASE-10 document

Dragonchain Foundation

The Dragonchain Foundation was created on January 17, 2017. https://den.social/l/Dragonchain/24130078352e485d96d2125082151cf0/dragonchain-and-disney/
submitted by j0j0r0 to ethereum [link] [comments]

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.



Many of you have limited time to read the full proposal, so here are the highlights:

Offline Multi-Signature

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.

Insurance Requirements

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.

Steps Forward

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.
submitted by azoundria2 to QuadrigaInitiative [link] [comments]

Bitcoin (BTC)A Peer-to-Peer Electronic Cash System.

Bitcoin (BTC)A Peer-to-Peer Electronic Cash System.
  • Bitcoin (BTC) is a peer-to-peer cryptocurrency that aims to function as a means of exchange that is independent of any central authority. BTC can be transferred electronically in a secure, verifiable, and immutable way.
  • Launched in 2009, BTC is the first virtual currency to solve the double-spending issue by timestamping transactions before broadcasting them to all of the nodes in the Bitcoin network. The Bitcoin Protocol offered a solution to the Byzantine Generals’ Problem with a blockchain network structure, a notion first created by Stuart Haber and W. Scott Stornetta in 1991.
  • Bitcoin’s whitepaper was published pseudonymously in 2008 by an individual, or a group, with the pseudonym “Satoshi Nakamoto”, whose underlying identity has still not been verified.
  • The Bitcoin protocol uses an SHA-256d-based Proof-of-Work (PoW) algorithm to reach network consensus. Its network has a target block time of 10 minutes and a maximum supply of 21 million tokens, with a decaying token emission rate. To prevent fluctuation of the block time, the network’s block difficulty is re-adjusted through an algorithm based on the past 2016 block times.
  • With a block size limit capped at 1 megabyte, the Bitcoin Protocol has supported both the Lightning Network, a second-layer infrastructure for payment channels, and Segregated Witness, a soft-fork to increase the number of transactions on a block, as solutions to network scalability.

https://preview.redd.it/s2gmpmeze3151.png?width=256&format=png&auto=webp&s=9759910dd3c4a15b83f55b827d1899fb2fdd3de1

1. What is Bitcoin (BTC)?

  • Bitcoin is a peer-to-peer cryptocurrency that aims to function as a means of exchange and is independent of any central authority. Bitcoins are transferred electronically in a secure, verifiable, and immutable way.
  • Network validators, whom are often referred to as miners, participate in the SHA-256d-based Proof-of-Work consensus mechanism to determine the next global state of the blockchain.
  • The Bitcoin protocol has a target block time of 10 minutes, and a maximum supply of 21 million tokens. The only way new bitcoins can be produced is when a block producer generates a new valid block.
  • The protocol has a token emission rate that halves every 210,000 blocks, or approximately every 4 years.
  • Unlike public blockchain infrastructures supporting the development of decentralized applications (Ethereum), the Bitcoin protocol is primarily used only for payments, and has only very limited support for smart contract-like functionalities (Bitcoin “Script” is mostly used to create certain conditions before bitcoins are used to be spent).

2. Bitcoin’s core features

For a more beginner’s introduction to Bitcoin, please visit Binance Academy’s guide to Bitcoin.

Unspent Transaction Output (UTXO) model

A UTXO transaction works like cash payment between two parties: Alice gives money to Bob and receives change (i.e., unspent amount). In comparison, blockchains like Ethereum rely on the account model.
https://preview.redd.it/t1j6anf8f3151.png?width=1601&format=png&auto=webp&s=33bd141d8f2136a6f32739c8cdc7aae2e04cbc47

Nakamoto consensus

In the Bitcoin network, anyone can join the network and become a bookkeeping service provider i.e., a validator. All validators are allowed in the race to become the block producer for the next block, yet only the first to complete a computationally heavy task will win. This feature is called Proof of Work (PoW).
The probability of any single validator to finish the task first is equal to the percentage of the total network computation power, or hash power, the validator has. For instance, a validator with 5% of the total network computation power will have a 5% chance of completing the task first, and therefore becoming the next block producer.
Since anyone can join the race, competition is prone to increase. In the early days, Bitcoin mining was mostly done by personal computer CPUs.
As of today, Bitcoin validators, or miners, have opted for dedicated and more powerful devices such as machines based on Application-Specific Integrated Circuit (“ASIC”).
Proof of Work secures the network as block producers must have spent resources external to the network (i.e., money to pay electricity), and can provide proof to other participants that they did so.
With various miners competing for block rewards, it becomes difficult for one single malicious party to gain network majority (defined as more than 51% of the network’s hash power in the Nakamoto consensus mechanism). The ability to rearrange transactions via 51% attacks indicates another feature of the Nakamoto consensus: the finality of transactions is only probabilistic.
Once a block is produced, it is then propagated by the block producer to all other validators to check on the validity of all transactions in that block. The block producer will receive rewards in the network’s native currency (i.e., bitcoin) as all validators approve the block and update their ledgers.

The blockchain

Block production

The Bitcoin protocol utilizes the Merkle tree data structure in order to organize hashes of numerous individual transactions into each block. This concept is named after Ralph Merkle, who patented it in 1979.
With the use of a Merkle tree, though each block might contain thousands of transactions, it will have the ability to combine all of their hashes and condense them into one, allowing efficient and secure verification of this group of transactions. This single hash called is a Merkle root, which is stored in the Block Header of a block. The Block Header also stores other meta information of a block, such as a hash of the previous Block Header, which enables blocks to be associated in a chain-like structure (hence the name “blockchain”).
An illustration of block production in the Bitcoin Protocol is demonstrated below.

https://preview.redd.it/m6texxicf3151.png?width=1591&format=png&auto=webp&s=f4253304912ed8370948b9c524e08fef28f1c78d

Block time and mining difficulty

Block time is the period required to create the next block in a network. As mentioned above, the node who solves the computationally intensive task will be allowed to produce the next block. Therefore, block time is directly correlated to the amount of time it takes for a node to find a solution to the task. The Bitcoin protocol sets a target block time of 10 minutes, and attempts to achieve this by introducing a variable named mining difficulty.
Mining difficulty refers to how difficult it is for the node to solve the computationally intensive task. If the network sets a high difficulty for the task, while miners have low computational power, which is often referred to as “hashrate”, it would statistically take longer for the nodes to get an answer for the task. If the difficulty is low, but miners have rather strong computational power, statistically, some nodes will be able to solve the task quickly.
Therefore, the 10 minute target block time is achieved by constantly and automatically adjusting the mining difficulty according to how much computational power there is amongst the nodes. The average block time of the network is evaluated after a certain number of blocks, and if it is greater than the expected block time, the difficulty level will decrease; if it is less than the expected block time, the difficulty level will increase.

What are orphan blocks?

In a PoW blockchain network, if the block time is too low, it would increase the likelihood of nodes producingorphan blocks, for which they would receive no reward. Orphan blocks are produced by nodes who solved the task but did not broadcast their results to the whole network the quickest due to network latency.
It takes time for a message to travel through a network, and it is entirely possible for 2 nodes to complete the task and start to broadcast their results to the network at roughly the same time, while one’s messages are received by all other nodes earlier as the node has low latency.
Imagine there is a network latency of 1 minute and a target block time of 2 minutes. A node could solve the task in around 1 minute but his message would take 1 minute to reach the rest of the nodes that are still working on the solution. While his message travels through the network, all the work done by all other nodes during that 1 minute, even if these nodes also complete the task, would go to waste. In this case, 50% of the computational power contributed to the network is wasted.
The percentage of wasted computational power would proportionally decrease if the mining difficulty were higher, as it would statistically take longer for miners to complete the task. In other words, if the mining difficulty, and therefore targeted block time is low, miners with powerful and often centralized mining facilities would get a higher chance of becoming the block producer, while the participation of weaker miners would become in vain. This introduces possible centralization and weakens the overall security of the network.
However, given a limited amount of transactions that can be stored in a block, making the block time too longwould decrease the number of transactions the network can process per second, negatively affecting network scalability.

3. Bitcoin’s additional features

Segregated Witness (SegWit)

Segregated Witness, often abbreviated as SegWit, is a protocol upgrade proposal that went live in August 2017.
SegWit separates witness signatures from transaction-related data. Witness signatures in legacy Bitcoin blocks often take more than 50% of the block size. By removing witness signatures from the transaction block, this protocol upgrade effectively increases the number of transactions that can be stored in a single block, enabling the network to handle more transactions per second. As a result, SegWit increases the scalability of Nakamoto consensus-based blockchain networks like Bitcoin and Litecoin.
SegWit also makes transactions cheaper. Since transaction fees are derived from how much data is being processed by the block producer, the more transactions that can be stored in a 1MB block, the cheaper individual transactions become.
https://preview.redd.it/depya70mf3151.png?width=1601&format=png&auto=webp&s=a6499aa2131fbf347f8ffd812930b2f7d66be48e
The legacy Bitcoin block has a block size limit of 1 megabyte, and any change on the block size would require a network hard-fork. On August 1st 2017, the first hard-fork occurred, leading to the creation of Bitcoin Cash (“BCH”), which introduced an 8 megabyte block size limit.
Conversely, Segregated Witness was a soft-fork: it never changed the transaction block size limit of the network. Instead, it added an extended block with an upper limit of 3 megabytes, which contains solely witness signatures, to the 1 megabyte block that contains only transaction data. This new block type can be processed even by nodes that have not completed the SegWit protocol upgrade.
Furthermore, the separation of witness signatures from transaction data solves the malleability issue with the original Bitcoin protocol. Without Segregated Witness, these signatures could be altered before the block is validated by miners. Indeed, alterations can be done in such a way that if the system does a mathematical check, the signature would still be valid. However, since the values in the signature are changed, the two signatures would create vastly different hash values.
For instance, if a witness signature states “6,” it has a mathematical value of 6, and would create a hash value of 12345. However, if the witness signature were changed to “06”, it would maintain a mathematical value of 6 while creating a (faulty) hash value of 67890.
Since the mathematical values are the same, the altered signature remains a valid signature. This would create a bookkeeping issue, as transactions in Nakamoto consensus-based blockchain networks are documented with these hash values, or transaction IDs. Effectively, one can alter a transaction ID to a new one, and the new ID can still be valid.
This can create many issues, as illustrated in the below example:
  1. Alice sends Bob 1 BTC, and Bob sends Merchant Carol this 1 BTC for some goods.
  2. Bob sends Carols this 1 BTC, while the transaction from Alice to Bob is not yet validated. Carol sees this incoming transaction of 1 BTC to him, and immediately ships goods to B.
  3. At the moment, the transaction from Alice to Bob is still not confirmed by the network, and Bob can change the witness signature, therefore changing this transaction ID from 12345 to 67890.
  4. Now Carol will not receive his 1 BTC, as the network looks for transaction 12345 to ensure that Bob’s wallet balance is valid.
  5. As this particular transaction ID changed from 12345 to 67890, the transaction from Bob to Carol will fail, and Bob will get his goods while still holding his BTC.
With the Segregated Witness upgrade, such instances can not happen again. This is because the witness signatures are moved outside of the transaction block into an extended block, and altering the witness signature won’t affect the transaction ID.
Since the transaction malleability issue is fixed, Segregated Witness also enables the proper functioning of second-layer scalability solutions on the Bitcoin protocol, such as the Lightning Network.

Lightning Network

Lightning Network is a second-layer micropayment solution for scalability.
Specifically, Lightning Network aims to enable near-instant and low-cost payments between merchants and customers that wish to use bitcoins.
Lightning Network was conceptualized in a whitepaper by Joseph Poon and Thaddeus Dryja in 2015. Since then, it has been implemented by multiple companies. The most prominent of them include Blockstream, Lightning Labs, and ACINQ.
A list of curated resources relevant to Lightning Network can be found here.
In the Lightning Network, if a customer wishes to transact with a merchant, both of them need to open a payment channel, which operates off the Bitcoin blockchain (i.e., off-chain vs. on-chain). None of the transaction details from this payment channel are recorded on the blockchain, and only when the channel is closed will the end result of both party’s wallet balances be updated to the blockchain. The blockchain only serves as a settlement layer for Lightning transactions.
Since all transactions done via the payment channel are conducted independently of the Nakamoto consensus, both parties involved in transactions do not need to wait for network confirmation on transactions. Instead, transacting parties would pay transaction fees to Bitcoin miners only when they decide to close the channel.
https://preview.redd.it/cy56icarf3151.png?width=1601&format=png&auto=webp&s=b239a63c6a87ec6cc1b18ce2cbd0355f8831c3a8
One limitation to the Lightning Network is that it requires a person to be online to receive transactions attributing towards him. Another limitation in user experience could be that one needs to lock up some funds every time he wishes to open a payment channel, and is only able to use that fund within the channel.
However, this does not mean he needs to create new channels every time he wishes to transact with a different person on the Lightning Network. If Alice wants to send money to Carol, but they do not have a payment channel open, they can ask Bob, who has payment channels open to both Alice and Carol, to help make that transaction. Alice will be able to send funds to Bob, and Bob to Carol. Hence, the number of “payment hubs” (i.e., Bob in the previous example) correlates with both the convenience and the usability of the Lightning Network for real-world applications.

Schnorr Signature upgrade proposal

Elliptic Curve Digital Signature Algorithm (“ECDSA”) signatures are used to sign transactions on the Bitcoin blockchain.
https://preview.redd.it/hjeqe4l7g3151.png?width=1601&format=png&auto=webp&s=8014fb08fe62ac4d91645499bc0c7e1c04c5d7c4
However, many developers now advocate for replacing ECDSA with Schnorr Signature. Once Schnorr Signatures are implemented, multiple parties can collaborate in producing a signature that is valid for the sum of their public keys.
This would primarily be beneficial for network scalability. When multiple addresses were to conduct transactions to a single address, each transaction would require their own signature. With Schnorr Signature, all these signatures would be combined into one. As a result, the network would be able to store more transactions in a single block.
https://preview.redd.it/axg3wayag3151.png?width=1601&format=png&auto=webp&s=93d958fa6b0e623caa82ca71fe457b4daa88c71e
The reduced size in signatures implies a reduced cost on transaction fees. The group of senders can split the transaction fees for that one group signature, instead of paying for one personal signature individually.
Schnorr Signature also improves network privacy and token fungibility. A third-party observer will not be able to detect if a user is sending a multi-signature transaction, since the signature will be in the same format as a single-signature transaction.

4. Economics and supply distribution

The Bitcoin protocol utilizes the Nakamoto consensus, and nodes validate blocks via Proof-of-Work mining. The bitcoin token was not pre-mined, and has a maximum supply of 21 million. The initial reward for a block was 50 BTC per block. Block mining rewards halve every 210,000 blocks. Since the average time for block production on the blockchain is 10 minutes, it implies that the block reward halving events will approximately take place every 4 years.
As of May 12th 2020, the block mining rewards are 6.25 BTC per block. Transaction fees also represent a minor revenue stream for miners.
submitted by D-platform to u/D-platform [link] [comments]

What is Quant Networks Blockchain Operating System, Overledger? And why are Enterprises adopting it at mass scale?

What is Quant Networks Blockchain Operating System, Overledger? And why are Enterprises adopting it at mass scale?
Overledger is the world’s first blockchain operating system (OS) that not only inter-connects blockchains but also existing enterprise platforms, applications and networks to blockchain and facilitates the creation of internet scale multi-chain applications otherwise known as mApps.
In less than 10 months since launching Overledger they have provided interoperability with the full range of DLT technologies from all the leading Enterprise Permissioned blockchains such as Hyperledger, R3’s Corda, JP Morgan’s Quorum, permissioned variants of Ethereum and Ripple (XRPL) as well as the leading Public Permissionless blockchains / DAGs such as Bitcoin, Stellar, Ethereum, IOTA and EOS as well as the most recent blockchain to get added Binance Chain. In addition, Overledger also connects to Existing Networks / Off Chain / Oracle functionality and it does all of this in a way that is hugely scalable, without imposing restrictions / requiring blockchains to fork their code and can easily integrate into existing applications / networks by just adding 3 lines of code.

https://preview.redd.it/3t3z6hkbxel31.png?width=1920&format=png&auto=webp&s=ac989c2752c726e10d2291eb271721ceaa332a30

What is a blockchain Operating system?

You will be familiar with Operating systems such as Microsoft Windows, Apple Mac OS, Google’s Android etc but these are all Hardware based Operating Systems. Hardware based Operating Systems provide a platform to build and use applications that abstracts all of the complexities involved with integrating with all the hardware resources such as CPU, Memory, Storage, Mouse, Keyboard, Video etc so software can easily integrate with it. It provides interoperability between the Hardware devices and Software.
Overledger is a Blockchain Operating System, it provides a platform to build and use applications that abstracts all of the complexities involved with integrating with all the different blockchains, different OP_Codes being used, messaging formats etc as well as connecting to existing non-blockchain networks. It provides interoperability between Blockchains, Existing Networks and Software / MAPPs

How is Overledger different to other interoperability projects?

Other projects are trying to achieve interoperability by adding another blockchain on top of existing blockchains. This adds a lot of overhead, complexity, and technical risk. There are a few variants but essentially they either need to create custom connectors for each connected blockchain and / or require connected chains to fork their code to enable interoperability. An example of the process can be seen below:
User sends transaction to a multi sig contract on Blockchain A, wait for consensus to be reached on Blockchain A
A custom connector consisting of Off Chain Relay Nodes are monitoring transactions sent to the smart contract on Blockchain A. Once they see the transaction, they then sign a transaction on the Interoperability blockchain as proof the event has happened on Blockchain A.
Wait for consensus to be reached on the Interoperability Blockchain.
The DAPP running on the Interoperability Blockchain is then updated with the info about the transaction occurring on Blockchain A and then signs a transaction on the Interoperability blockchain to a multi sig contract on the Interoperability Blockchain.
Wait for consensus to be reached on the interoperability Blockchain.
A different custom connector consisting of Off Chain Relay Nodes are monitoring transactions sent to the Smart Contract on the Interoperability Blockchain which are destined for Blockchain B. Once they see the transaction, they sign a transaction on Blockchain B. Wait for consensus to be reached on Blockchain B.

https://preview.redd.it/xew1eu1exel31.png?width=1558&format=png&auto=webp&s=df960ded46d40fc9bf0ae8b54ff3b3b86276708a
Other solutions require every connecting blockchain to fork their code and implement their Interoperability protocol. This means the same type of connector can be used instead of a custom one for every blockchain however every connected blockchain has to fork their code to implement the protocol. This enforces a lot of restrictions on what the connected blockchains can implement going forward.

https://preview.redd.it/pe166qyexel31.png?width=1561&format=png&auto=webp&s=d4c982089276e64cd909537c9ce744b59e168b6d
Some problems with these methods:
  • They add a lot of Overhead / Latency. Rather than just having the consensus of Blockchain A and B, you add the consensus mechanism of the Interoperability Blockchain as well.
  • Decentralisation / transaction security is reduced. If Blockchain A and Blockchain B each have 1,000 nodes validating transactions, yet the Interoperability Blockchain only has 100 nodes then you have reduced the security of the transaction from being validated by 1000 to validated by 100.
  • Security of the Interoperability Blockchain must be greater than the sum of all transactions going through it. JP Morgan transfer $6 Trillion every day, if they move that onto blockchain and need interoperability between two Permissioned blockchains that have to connect via a public Interoperability blockchain, then it would always have to be more costly to attack the blockchain than the value from stealing the funds transacted through the blockchain.
  • Imposes a lot of limitations on connected blockchains to fork their code which may mean they have to drop some existing functionality as well as prevent them from adding certain features in the future.
  • Creates a single point of failure — If the Interoperability blockchain or connector has an issue then this affects each connected blockchain.
  • It doesn’t scale and acts as a bottleneck. Not only does building complex custom connectors not scale but the Interoperability blockchain that they are forcing all transactions to go through has to be faster than the combined throughput of connected blockchains. These Interoperability blockchains have limited tps, with the most being around 200 and is a trade off between performance and decentralisation.

But some Interoperability blockchains say they are infinitely scalable?

If the interoperability blockchain is limited to say 200 tps then the idea is to just have multiple instances of the blockchain and run them in parallel, so you benefit from the aggregated tps, but just how feasible is that? Lets say you want to connect Corda (capable of 2000+ tps) to Hyperledger (capable of up to 20,000 tps with recent upgrade). (Permissioned blockchains such as Hyperledger and Corda aren’t one big blockchain like say Bitcoin or Ethereum, they have separate instances for each consortium and each is capable of those speeds). So even when you have just 1 DAPP from one consortium that wants to connect Corda to Hyperledger and use 2000 tps for their DAPP, you would need 100 instances of the Interoperability blockchain, each with their own validators (which maybe 100–200 nodes each). So, 1 DAPP would need to cover the costs for 100 instances of the blockchain and running costs for 10,000 nodes…This is just one DAPP connected to one instance of a two permissioned blockchains, which are still in the early stages. Other blockchains such as Red Belly Blockchain can achieve 440,000 tps, and this will surely increase as the technology matures. There is also the added complexity of then aggregating the results / co-coordinating between the different instances of the blockchain. Then there are the environmental concerns, the power required for all of these instances / nodes is not sustainable.

https://preview.redd.it/yz2wvnhgxel31.png?width=1070&format=png&auto=webp&s=e6cb66e362b18e9924245a6a99e0eac4c9083308
It’s not just transactions per second of the blockchain as well, its the latency of all these added consensuses along the path to reach to the destination and not knowing whether the security of each of the hops is sufficient and can be trusted. To see examples of how this potential issue as well as others effect Cosmos you can see my article here. I recommend also reading a blog done by the CEO of Quant, Gilbert Verdian, which explains how Overledger differs here as well as detailed in the whitepaper here.

https://preview.redd.it/2cwj4k7hxel31.png?width=1169&format=png&auto=webp&s=d6fc49086f944089cef7ffa1dfc9d284107ad2e3

Overledger’s approach

In 1973 Vint Cerf invented the protocol that rules them all: TCP/IP. Most people have never heard of it. But it describes the fundamental architecture of the internet, and it made possible Wi-Fi, Ethernet, LANs, the World Wide Web, e-mail, FTP, 3G/4G — as well as all of the inventions built upon those inventions.
Wired: So from the beginning, people, including yourself, had a vision of where the internet was going to go. Are you surprised, though, that at this point the IP protocol seems to beat almost anything it comes up against?Cerf: I’m not surprised at all because we designed it to do that.This was very conscious. Something we did right at the very beginning, when we were writing the specifications, we wanted to make this a future-proof protocol. And so the tactic that we used to achieve that was to say that the protocol did not know how — the packets of the internet protocol layer didn’t know how they were being carried. And they didn’t care whether it was a satellite link or mobile radio link or an optical fiber or something else.We were very, very careful to isolate that protocol layer from any detailed knowledge of how it was being carried. Plainly, the software had to know how to inject it into a radio link, or inject it into an optical fiber, or inject it into a satellite connection. But the basic protocol didn’t know how that worked.And the other thing that we did was to make sure that the network didn’t know what the packets had in them. We didn’t encrypt them to prevent it from knowing — we just didn’t make it have to know anything. It’s just a bag of bits as far as the net was concerned.We were very successful in these two design features, because every time a new kind of communications technology came along, like frame relay or asynchronous transfer mode or passive optical networking or mobile radio‚ all of these different ways of communicating could carry internet packets.We would hear people saying, ‘The internet will be replaced by X25,’ or ‘The internet will be replaced by frame relay,’ or ‘The internet will be replaced by APM,’ or ‘The internet will be replaced by add-and-drop multiplexers.’Of course, the answer is, ‘No, it won’t.’ It just runs on top of everything. And that was by design. I’m actually very proud of the fact that we thought of that and carefully designed that capability into the system.
This is the approach Quant have taken with their Blockchain OS, Overledger to solve Blockchain interoperability. Compared to other Interoperability platforms that are trying to achieve interoperability at the transaction layer by connecting two blockchains via another blockchain, these will be ultimately be made redundant once faster methods are released. Overledger is designed to be future proof by isolating the layers so it doesn’t matter whether it’s a permissioned blockchain, permissionless, DAG, Legacy network, POW, POS etc because it abstracts the transaction layer from the messaging layer and runs on top of blockchains. Just as the Internet wasn’t replaced by X25, frame relay, APM etc, Overledger is designed to be future proof as it just runs on top of the Blockchains rather than being a blockchain itself. So, if a new blockchain technology comes out that is capable of 100,000 TPS then it can easily be integrated as Overledger just runs on top of it.
Likewise, with protocols such as HTTPS, SSH etc these will also emerge for blockchains such as ZK-Snarks and other privacy implementations as well as other features made available, all will be compatible with Overledger as its just sitting on top rather than forcing their own implementation for all.
It doesn’t require blockchains to fork their code to make it compatible, it doesn’t add the overhead of adding another blockchain with another consensus mechanism (most likely multiple as it has to go through many hops). All of this adds a lot of latency and restrictions which isn’t needed. The developer can just choose which blockchains they want to connect and use the consensus mechanisms of those blockchains rather than forced to use one.
Overledger can provide truly internet scale to meet whatever the demands may be, whether that be connecting multiple red belly blockchains together with 440,000 tps it doesn’t matter as it doesn’t add its consensus mechanism and uses proven internet scale technology such as that based on Kubernetes, which is where each task is split up into a self-contained container and each task is scaled out by deploying more to meet demand. Kubernetes is what runs Google Search engine where they scale up and down billions of containers every week.
Due to this being more of a summary, I strongly recommend you read this article which goes into detail about the different layers in Overledger.

https://preview.redd.it/1lpt98cixel31.png?width=1126&format=png&auto=webp&s=3928cf66cfe25bfce7dc84be7b6db670ac952ccf

But how does it provide the security of a blockchain if it doesn’t add its own blockchain?

This is often misunderstood by people. Overledger is not a blockchain however it still uses a blockchain for security, immutability, traceability etc, just rather than force people to use their own blockchain, it utilises the source and destination blockchains instead. The key thing to understand is the use of its patented technology TrustTag, which was made freely available to anyone with the Overledger SDK.
Please see this article which explains TrustTag in detail with examples showing how hashing / digital signatures work etc
A quick overview is if i want to send data from one blockchain to another the Overledger SDK using Trusttag will put the data through a hashing algorithm. The Hash is then included in digital signature as part of the transaction which is signed by the user’s private key and then validated through normal consensus and stored as metadata on the source blockchain. The message is then sent to the MAPP off chain. The MAPP periodically scans the blockchains and puts the received message through a hashing algorithm and compares the Hash to the one stored as metadata on the blockchain. This ensures that the message hasn’t been modified in transit, the message is encrypted and only the Hash is stored on chain so completely private, provides immutability as it was signed by the user’s private key which only they have and is stored on the blockchain for high availability and secure so that it can’t be modified, with the ability to refer back to it at any point in time.
Despite Overledger being a very secure platform, with the team having a very strong security background such as Gilbert who was chief security information officer for Vocalink (Bank of England) managing £6 trillion of payments every year and classified as national critical security (highest level you can get), ultimately you don’t need to trust Overledger. Transactions are signed and encrypted at client side, so Overledger has no way of being able to see the contents. It can’t modify any transaction as the digital signature which includes a hash of the transaction would be different so would get rejected. Transaction security isn’t reduced as it is signed at source using however many nodes the source blockchain has rather than a smaller amount of nodes with an interoperability blockchain in the middle.

Patents

The core code of Overledger is closed source and patented, one of the recent patents can be seen here, along with TrustTag and further ones are being filed. The Overledger SDK is open source and is available in Java and Javascript currently, with plans to support Pyhton and Ruby in the near future. Java and Javascript are the most popular programming languages used today.
The Blockchain connectors are also open source and this allows the community to create connectors to connect their favourite blockchain so that it can benefit from blockchain interoperability and making it available to all enterprises / developers currently utilising Overledger. Creating is currently taking around a week to implement and so far, have been added based upon client demand.

Multi Chain Applications (MAPPs)

Multi Chain Applications (MAPPs) enable an application to use multiple blockchains and interoperate between them. Treaty Contracts enable a developer to build a MAPP and then change the underlying blockchain it uses with just a quick change of couple of lines of code. This is vital for enterprises as it’s still early days in Blockchian and we don’t know which are going to be the best blockchain in the future. Overledger easily integrates into existing applications using the Overledger SDK by just adding 3 lines of code. They don’t need to completely rewrite the application like you do with the majority of other projects and all existing java / javascript apps on Windows / Mobile app stores / business applications etc can easily integrate with overledger with minimal changes in just 8 minutes.

Treaty Contracts

What Overledger will allow with Treaty contracts is to use popular programming languages such as Java and create a smart contract in Overledger that interacts with all of the connected blockchains. Even providing Smart contract functionality to blockchains that don’t support them such as Bitcoin. This means that developers don’t have to create all the smart contracts on each blockchain in all the different programming languages but instead just create them in Overledger using languages such as Java that are widely used today. If they need to use a different blockchain then it can be as easy as changing a line of code rather than having to completely rewrite the smart contracts.
Overledger isn’t a blockchain though, so how can it trusted with the smart contract? A Hash of the smart contract is published on any blockchain the MAPP developer requires and when called the smart contract is run its run through a hashing function to check that it matches the Hash value stored on the blockchain, ensuring that it has not been modified.
By running the Smart contract off chain this also increases Scalability enormously. With a blockchain all nodes have to run the smart contract one after another rather than in parallel. Not only do you get the performance benefit of not having to run the code against every single node but you can also run them in parallel to others executing smart contracts.
You can read more about Treaty Contracts here

The different versions of Overledger

Enterprise version

The current live version is the Enterprise version as that is where most of the adoption is taking place in blockchain due to permissioned blockchains being preferred until permissionless blockchains resolve the scalability, privacy and regulatory issues. Please see this article which goes into more details about Entereprise blockchain / adoption. The Enterprise version connects to permissioned blockchains as well as additional features / support suited for Enterprises.

Community version

The community version is due to be released later this year which will allow developers to benefit from creating MAPPs across permissionless blockchains. Developers can publish their MAPPs on the MAPP Store to create additional revenue streams for developers.

Where does Overledger run from? Is it Centralised?

Overledger can run from anywhere. The community version will have instances across multiple public clouds, Enterprises / developers may prefer to host the infrastructure themselves within a consortium which they can and are doing. For example SIA is the leading private Financial Network provider in Europe, it provides a dedicated high speed network which connects all the major banks, central banks, trading venues etc. SIA host Overledger within their private network so that all of those clients can access it in the confinement of their heavily regulated, secure, fast network. AUCloud / UKCLoud host Overledger in their environment to offer as a service to their clients which consist of Governments and critical national infrastructure.
For Blockchain nodes that interact with Overledger the choice is entirely up to the developer. Each member within a consortium may choose to host a node, some developers may prefer to use 3rd party hosting providers such as Infura, or Quant can also host them if they prefer, its entirely their choice.
Overledger allows for higher levels of decentralisation by storing the output across multiple blockchains so you not only benefit from the decentralisation of one blockchain but the combination of all of them. Ultimately though decentralisation is thrown around too much without many actually understanding what it means. It’s impossible to have complete decentralisation, when you sign a transaction to be added to a blockchain ultimately you still connect through a single ISP, connect through a single router, or the input into a transaction is done through a piece of software etc. What matters to be decentralised is where trust is involved. As i have mentioned before you don’t need to trust the OS, it’s just providing instructions on how to interact with the blockchains, the end user is signing the transactions / encrypting at client side. Nothing can be seen or modified with the OS. Even if somehow the transaction did get modified then it would get rejected when consensus is done as the hash / digital signature won’t match at the destination blockchain. Where the transaction actually gets put onto the blockchain is where decentralisation matters, because thats what needs to be trusted and conensus is reached and Overledger enables this to be written across multiple blockchains at the same time.

The Team

The team are very well connected with a wealth of experience at very senior roles at Global enterprises which I will include a few examples below. Gilbert Verdian the CEO was the Head of security for the payment infrastructure for the Bank of England through his CISO role with Vocalink (Mastercard)managing £6 trillion every year. This is treated by the government as critical national infrastructure which is the highest level of criticallity because its so fundamental to the security of the country. They have experience and know what it takes to run a secure financial infrastructure and meeting requirements of regulators. Gilbert was director for Cybersecurity at PWC, Security for HSBC and Ernst & Young as well as various government roles such as the CISO for the Australian NSW Health, Head of Security at the UK government for Ministry of Justice and HM Treasury in addition to being part of the committee for the European Commission, US Federal Reserve and the Bank of England.
Cecilia Harvey is the Chief Operating Officer, where she was previously a Director at HSBC in Global Banking and Markets and before that Director at Vocalink. Cecilia was also Chief Operating Officer at Citi for Markets and Securities Services Technology as well as working for Barclays, Accenture, IBM and Morgan Stanley.
Vijay Verma is the Overledger platform lead with over 15 years of developer experience in latest technologies like Java, Scala, Blockchain & enterprise technology solutions. Over the course of his career, he has worked for a number of prestigious organisations including J&J, Deutsche, HSBC, BNP Paribas, UBS Banks, HMRC and Network Rail.
Guy Dietrich, the managing director of Rockefeller Capital (manages $19 Billion in assets) has joined the board of Quant Network, and has recently personally attended meetings with the Financial Conduct Authority (FCA) with Gilbert

https://preview.redd.it/1x25xg78efl31.png?width=566&format=png&auto=webp&s=abea981ff40355eed2d0e3be1ca414c5b1b8573c
As well as advisors such as Paolo Tasca, the founder and Executive Director of the Centre for Blockchain Technologies (UCL CBT) at University College Londonfounder and executive director as well as Chris Adelsbach, Managing Director at Techstars, the worldwide network that helps entrepreneurs succeed. Techstars has partners such as Amazon, Barclays, Boeing, Ford, Google, Honda, IBM, Microsoft, PWC, Sony, Target, Total, Verizon, Western Union etc.
Due to client demand they are expanding to the US to setup a similar size office where board members such as Guy Dietrich will be extremely valuable in assisting with the expansion.
https://twitter.com/gverdian/status/1151549142235340800
The most exciting part about the project though is just how much adoption there has been of the platform, from huge global enterprises, governments and cloud providers they are on track for a revenue of $10 million in their first year. I will go through these in the next article, followed by further article explaining how the Token and Treasury works.
You can also find out more info about Quant at the following:
Part One — Blockchain Fundamentals
Part Two — The Layers Of Overledger
Part Three — TrustTag and the Tokenisation of data
Part Four — Features Overledger provides to MAPPs
Part Five — Creating the Standards for Interoperability
Part Six — The Team behind Overledger and Partners
Part Seven — The QNT Token
Part Eight — Enabling Enterprise Mass Adoption
Quant Network Enabling Mass Adoption of Blockchain at a Rapid Pace
Quant Network Partner with SIA, A Game Changer for Mass Blockchain Adoption by Financial Institutions
submitted by xSeq22x to QuantNetwork [link] [comments]

What is Quant Networks Blockchain Operating System, Overledger? And why are Enterprises adopting it at mass scale?

What is Quant Networks Blockchain Operating System, Overledger? And why are Enterprises adopting it at mass scale?
Overledger is the world’s first blockchain operating system (OS) that not only inter-connects blockchains but also existing enterprise platforms, applications and networks to blockchain and facilitates the creation of internet scale multi-chain applications otherwise known as mApps.
In less than 10 months since launching Overledger they have provided interoperability with the full range of DLT technologies from all the leading Enterprise Permissioned blockchains such as Hyperledger, R3’s Corda, JP Morgan’s Quorum, permissioned variants of Ethereum and Ripple (XRPL) as well as the leading Public Permissionless blockchains / DAGs such as Bitcoin, Stellar, Ethereum, IOTA and EOS as well as the most recent blockchain to get added Binance Chain. In addition, Overledger also connects to Existing Networks / Off Chain / Oracle functionality and it does all of this in a way that is hugely scalable, without imposing restrictions / requiring blockchains to fork their code and can easily integrate into existing applications / networks by just adding 3 lines of code.

https://preview.redd.it/30jclqe3wel31.png?width=1920&format=png&auto=webp&s=2bcce5d296c3a287dccdd28b72877ca9e03a5f31

What is a blockchain Operating system?

You will be familiar with Operating systems such as Microsoft Windows, Apple Mac OS, Google’s Android etc but these are all Hardware based Operating Systems. Hardware based Operating Systems provide a platform to build and use applications that abstracts all of the complexities involved with integrating with all the hardware resources such as CPU, Memory, Storage, Mouse, Keyboard, Video etc so software can easily integrate with it. It provides interoperability between the Hardware devices and Software.
Overledger is a Blockchain Operating System, it provides a platform to build and use applications that abstracts all of the complexities involved with integrating with all the different blockchains, different OP_Codes being used, messaging formats etc as well as connecting to existing non-blockchain networks. It provides interoperability between Blockchains, Existing Networks and Software / MAPPs

How is Overledger different to other interoperability projects?

Other projects are trying to achieve interoperability by adding another blockchain on top of existing blockchains. This adds a lot of overhead, complexity, and technical risk. There are a few variants but essentially they either need to create custom connectors for each connected blockchain and / or require connected chains to fork their code to enable interoperability. An example of the process can be seen below:
User sends transaction to a multi sig contract on Blockchain A, wait for consensus to be reached on Blockchain A
A custom connector consisting of Off Chain Relay Nodes are monitoring transactions sent to the smart contract on Blockchain A. Once they see the transaction, they then sign a transaction on the Interoperability blockchain as proof the event has happened on Blockchain A.
Wait for consensus to be reached on the Interoperability Blockchain.
The DAPP running on the Interoperability Blockchain is then updated with the info about the transaction occurring on Blockchain A and then signs a transaction on the Interoperability blockchain to a multi sig contract on the Interoperability Blockchain.
Wait for consensus to be reached on the interoperability Blockchain.
A different custom connector consisting of Off Chain Relay Nodes are monitoring transactions sent to the Smart Contract on the Interoperability Blockchain which are destined for Blockchain B. Once they see the transaction, they sign a transaction on Blockchain B. Wait for consensus to be reached on Blockchain B.
https://preview.redd.it/2apm3pb5wel31.png?width=1558&format=png&auto=webp&s=7027514706d7b12690b1be8f4f4af7cfc9c43354
Other solutions require every connecting blockchain to fork their code and implement their Interoperability protocol. This means the same type of connector can be used instead of a custom one for every blockchain however every connected blockchain has to fork their code to implement the protocol. This enforces a lot of restrictions on what the connected blockchains can implement going forward.

https://preview.redd.it/4axzxx57wel31.png?width=1561&format=png&auto=webp&s=a8c3de8468ef9b67bc1db75cffbef81ef8c0aa70
Some problems with these methods:
  • They add a lot of Overhead / Latency. Rather than just having the consensus of Blockchain A and B, you add the consensus mechanism of the Interoperability Blockchain as well.
  • Decentralisation / transaction security is reduced. If Blockchain A and Blockchain B each have 1,000 nodes validating transactions, yet the Interoperability Blockchain only has 100 nodes then you have reduced the security of the transaction from being validated by 1000 to validated by 100.
  • Security of the Interoperability Blockchain must be greater than the sum of all transactions going through it. JP Morgan transfer $6 Trillion every day, if they move that onto blockchain and need interoperability between two Permissioned blockchains that have to connect via a public Interoperability blockchain, then it would always have to be more costly to attack the blockchain than the value from stealing the funds transacted through the blockchain.
  • Imposes a lot of limitations on connected blockchains to fork their code which may mean they have to drop some existing functionality as well as prevent them from adding certain features in the future.
  • Creates a single point of failure — If the Interoperability blockchain or connector has an issue then this affects each connected blockchain.
  • It doesn’t scale and acts as a bottleneck. Not only does building complex custom connectors not scale but the Interoperability blockchain that they are forcing all transactions to go through has to be faster than the combined throughput of connected blockchains. These Interoperability blockchains have limited tps, with the most being around 200 and is a trade off between performance and decentralisation.

But some Interoperability blockchains say they are infinitely scalable?

If the interoperability blockchain is limited to say 200 tps then the idea is to just have multiple instances of the blockchain and run them in parallel, so you benefit from the aggregated tps, but just how feasible is that? Lets say you want to connect Corda (capable of 2000+ tps) to Hyperledger (capable of up to 20,000 tps with recent upgrade). (Permissioned blockchains such as Hyperledger and Corda aren’t one big blockchain like say Bitcoin or Ethereum, they have separate instances for each consortium and each is capable of those speeds). So even when you have just 1 DAPP from one consortium that wants to connect Corda to Hyperledger and use 2000 tps for their DAPP, you would need 100 instances of the Interoperability blockchain, each with their own validators (which maybe 100–200 nodes each). So, 1 DAPP would need to cover the costs for 100 instances of the blockchain and running costs for 10,000 nodes…This is just one DAPP connected to one instance of a two permissioned blockchains, which are still in the early stages. Other blockchains such as Red Belly Blockchain can achieve 440,000 tps, and this will surely increase as the technology matures. There is also the added complexity of then aggregating the results / co-coordinating between the different instances of the blockchain. Then there are the environmental concerns, the power required for all of these instances / nodes is not sustainable.

https://preview.redd.it/myjx8t29wel31.png?width=1070&format=png&auto=webp&s=550ac862c3c5b46df8ed42cf37282cad0a960819
It’s not just transactions per second of the blockchain as well, its the latency of all these added consensuses along the path to reach to the destination and not knowing whether the security of each of the hops is sufficient and can be trusted. To see examples of how this potential issue as well as others effect Cosmos you can see my article here. I recommend also reading a blog done by the CEO of Quant, Gilbert Verdian, which explains how Overledger differs here as well as detailed in the whitepaper here.

https://preview.redd.it/m9036lzfwel31.png?width=1169&format=png&auto=webp&s=50e54198a97106b3921f79ca928f7e808a5529d7

Overledger’s approach

In 1973 Vint Cerf invented the protocol that rules them all: TCP/IP. Most people have never heard of it. But it describes the fundamental architecture of the internet, and it made possible Wi-Fi, Ethernet, LANs, the World Wide Web, e-mail, FTP, 3G/4G — as well as all of the inventions built upon those inventions.
***Wired: So from the beginning, people, including yourself, had a vision of where the internet was going to go. Are you surprised, though, that at this point the IP protocol seems to beat almost anything it comes up against?***Cerf: I’m not surprised at all because we designed it to do that.This was very conscious. Something we did right at the very beginning, when we were writing the specifications, we wanted to make this a future-proof protocol. And so the tactic that we used to achieve that was to say that the protocol did not know how — the packets of the internet protocol layer didn’t know how they were being carried. And they didn’t care whether it was a satellite link or mobile radio link or an optical fiber or something else.We were very, very careful to isolate that protocol layer from any detailed knowledge of how it was being carried. Plainly, the software had to know how to inject it into a radio link, or inject it into an optical fiber, or inject it into a satellite connection. But the basic protocol didn’t know how that worked.And the other thing that we did was to make sure that the network didn’t know what the packets had in them. We didn’t encrypt them to prevent it from knowing — we just didn’t make it have to know anything. It’s just a bag of bits as far as the net was concerned.We were very successful in these two design features, because every time a new kind of communications technology came along, like frame relay or asynchronous transfer mode or passive optical networking or mobile radio‚ all of these different ways of communicating could carry internet packets.We would hear people saying, ‘The internet will be replaced by X25,’ or ‘The internet will be replaced by frame relay,’ or ‘The internet will be replaced by APM,’ or ‘The internet will be replaced by add-and-drop multiplexers.’Of course, the answer is, ‘No, it won’t.’ It just runs on top of everything. And that was by design. I’m actually very proud of the fact that we thought of that and carefully designed that capability into the system.
This is the approach Quant have taken with their Blockchain OS, Overledger to solve Blockchain interoperability. Compared to other Interoperability platforms that are trying to achieve interoperability at the transaction layer by connecting two blockchains via another blockchain, these will be ultimately be made redundant once faster methods are released. Overledger is designed to be future proof by isolating the layers so it doesn’t matter whether it’s a permissioned blockchain, permissionless, DAG, Legacy network, POW, POS etc because it abstracts the transaction layer from the messaging layer and runs on top of blockchains. Just as the Internet wasn’t replaced by X25, frame relay, APM etc, Overledger is designed to be future proof as it just runs on top of the Blockchains rather than being a blockchain itself. So, if a new blockchain technology comes out that is capable of 100,000 TPS then it can easily be integrated as Overledger just runs on top of it.
Likewise, with protocols such as HTTPS, SSH etc these will also emerge for blockchains such as ZK-Snarks and other privacy implementations as well as other features made available, all will be compatible with Overledger as its just sitting on top rather than forcing their own implementation for all.
It doesn’t require blockchains to fork their code to make it compatible, it doesn’t add the overhead of adding another blockchain with another consensus mechanism (most likely multiple as it has to go through many hops). All of this adds a lot of latency and restrictions which isn’t needed. The developer can just choose which blockchains they want to connect and use the consensus mechanisms of those blockchains rather than forced to use one.
Overledger can provide truly internet scale to meet whatever the demands may be, whether that be connecting multiple red belly blockchains together with 440,000 tps it doesn’t matter as it doesn’t add its consensus mechanism and uses proven internet scale technology such as that based on Kubernetes, which is where each task is split up into a self-contained container and each task is scaled out by deploying more to meet demand. Kubernetes is what runs Google Search engine where they scale up and down billions of containers every week.
Due to this being more of a summary, I strongly recommend you read this article which goes into detail about the different layers in Overledger.

https://preview.redd.it/6x7tjq9jwel31.png?width=1126&format=png&auto=webp&s=52ac5b9ebb45908ef6070d2eed6d107d380da1df

But how does it provide the security of a blockchain if it doesn’t add its own blockchain?

This is often misunderstood by people. Overledger is not a blockchain however it still uses a blockchain for security, immutability, traceability etc, just rather than force people to use their own blockchain, it utilises the source and destination blockchains instead. The key thing to understand is the use of its patented technology TrustTag, which was made freely available to anyone with the Overledger SDK.
Please see this article which explains TrustTag in detail with examples showing how hashing / digital signatures work etc
A quick overview is if i want to send data from one blockchain to another the Overledger SDK using Trusttag will put the data through a hashing algorithm. The Hash is then included in digital signature as part of the transaction which is signed by the user’s private key and then validated through normal consensus and stored as metadata on the source blockchain. The message is then sent to the MAPP off chain. The MAPP periodically scans the blockchains and puts the received message through a hashing algorithm and compares the Hash to the one stored as metadata on the blockchain. This ensures that the message hasn’t been modified in transit, the message is encrypted and only the Hash is stored on chain so completely private, provides immutability as it was signed by the user’s private key which only they have and is stored on the blockchain for high availability and secure so that it can’t be modified, with the ability to refer back to it at any point in time.
Despite Overledger being a very secure platform, with the team having a very strong security background such as Gilbert who was chief security information officer for Vocalink (Bank of England) managing £6 trillion of payments every year and classified as national critical security (highest level you can get), ultimately you don’t need to trust Overledger. Transactions are signed and encrypted at client side, so Overledger has no way of being able to see the contents. It can’t modify any transaction as the digital signature which includes a hash of the transaction would be different so would get rejected. Transaction security isn’t reduced as it is signed at source using however many nodes the source blockchain has rather than a smaller amount of nodes with an interoperability blockchain in the middle.

Patents

The core code of Overledger is closed source and patented, one of the recent patents can be seen here, along with TrustTag and further ones are being filed. The Overledger SDK is open source and is available in Java and Javascript currently, with plans to support Pyhton and Ruby in the near future. Java and Javascript are the most popular programming languages used today.
The Blockchain connectors are also open source and this allows the community to create connectors to connect their favourite blockchain so that it can benefit from blockchain interoperability and making it available to all enterprises / developers currently utilising Overledger. Creating is currently taking around a week to implement and so far, have been added based upon client demand.

Multi Chain Applications (MAPPs)

Multi Chain Applications (MAPPs) enable an application to use multiple blockchains and interoperate between them. Treaty Contracts enable a developer to build a MAPP and then change the underlying blockchain it uses with just a quick change of couple of lines of code. This is vital for enterprises as it’s still early days in Blockchian and we don’t know which are going to be the best blockchain in the future. Overledger easily integrates into existing applications using the Overledger SDK by just adding 3 lines of code. They don’t need to completely rewrite the application like you do with the majority of other projects and all existing java / javascript apps on Windows / Mobile app stores / business applications etc can easily integrate with overledger with minimal changes in just 8 minutes.

Treaty Contracts

What Overledger will allow with Treaty contracts is to use popular programming languages such as Java and create a smart contract in Overledger that interacts with all of the connected blockchains. Even providing Smart contract functionality to blockchains that don’t support them such as Bitcoin. This means that developers don’t have to create all the smart contracts on each blockchain in all the different programming languages but instead just create them in Overledger using languages such as Java that are widely used today. If they need to use a different blockchain then it can be as easy as changing a line of code rather than having to completely rewrite the smart contracts.
Overledger isn’t a blockchain though, so how can it trusted with the smart contract? A Hash of the smart contract is published on any blockchain the MAPP developer requires and when called the smart contract is run its run through a hashing function to check that it matches the Hash value stored on the blockchain, ensuring that it has not been modified.
By running the Smart contract off chain this also increases Scalability enormously. With a blockchain all nodes have to run the smart contract one after another rather than in parallel. Not only do you get the performance benefit of not having to run the code against every single node but you can also run them in parallel to others executing smart contracts.
You can read more about Treaty Contracts here

The different versions of Overledger

Enterprise version

The current live version is the Enterprise version as that is where most of the adoption is taking place in blockchain due to permissioned blockchains being preferred until permissionless blockchains resolve the scalability, privacy and regulatory issues. Please see this article which goes into more details about Entereprise blockchain / adoption. The Enterprise version connects to permissioned blockchains as well as additional features / support suited for Enterprises.

Community version

The community version is due to be released later this year which will allow developers to benefit from creating MAPPs across permissionless blockchains. Developers can publish their MAPPs on the MAPP Store to create additional revenue streams for developers.

Where does Overledger run from? Is it Centralised?

Overledger can run from anywhere. The community version will have instances across multiple public clouds, Enterprises / developers may prefer to host the infrastructure themselves within a consortium which they can and are doing. For example SIA is the leading private Financial Network provider in Europe, it provides a dedicated high speed network which connects all the major banks, central banks, trading venues etc. SIA host Overledger within their private network so that all of those clients can access it in the confinement of their heavily regulated, secure, fast network. AUCloud / UKCLoud host Overledger in their environment to offer as a service to their clients which consist of Governments and critical national infrastructure.
For Blockchain nodes that interact with Overledger the choice is entirely up to the developer. Each member within a consortium may choose to host a node, some developers may prefer to use 3rd party hosting providers such as Infura, or Quant can also host them if they prefer, its entirely their choice.
Overledger allows for higher levels of decentralisation by storing the output across multiple blockchains so you not only benefit from the decentralisation of one blockchain but the combination of all of them. Ultimately though decentralisation is thrown around too much without many actually understanding what it means. It’s impossible to have complete decentralisation, when you sign a transaction to be added to a blockchain ultimately you still connect through a single ISP, connect through a single router, or the input into a transaction is done through a piece of software etc. What matters to be decentralised is where trust is involved. As i have mentioned before you don’t need to trust the OS, it’s just providing instructions on how to interact with the blockchains, the end user is signing the transactions / encrypting at client side. Nothing can be seen or modified with the OS. Even if somehow the transaction did get modified then it would get rejected when consensus is done as the hash / digital signature won’t match at the destination blockchain. Where the transaction actually gets put onto the blockchain is where decentralisation matters, because thats what needs to be trusted and conensus is reached and Overledger enables this to be written across multiple blockchains at the same time.

The Team

The team are very well connected with a wealth of experience at very senior roles at Global enterprises which I will include a few examples below. Gilbert Verdian the CEO was the Head of security for the payment infrastructure for the Bank of England through his CISO role with Vocalink (Mastercard)managing £6 trillion every year. This is treated by the government as critical national infrastructure which is the highest level of criticallity because its so fundamental to the security of the country. They have experience and know what it takes to run a secure financial infrastructure and meeting requirements of regulators. Gilbert was director for Cybersecurity at PWC, Security for HSBC and Ernst & Young as well as various government roles such as the CISO for the Australian NSW Health, Head of Security at the UK government for Ministry of Justice and HM Treasury in addition to being part of the committee for the European Commission, US Federal Reserve and the Bank of England.
Cecilia Harvey is the Chief Operating Officer, where she was previously a Director at HSBC in Global Banking and Markets and before that Director at Vocalink. Cecilia was also Chief Operating Officer at Citi for Markets and Securities Services Technology as well as working for Barclays, Accenture, IBM and Morgan Stanley.
Vijay Verma is the Overledger platform lead with over 15 years of developer experience in latest technologies like Java, Scala, Blockchain & enterprise technology solutions. Over the course of his career, he has worked for a number of prestigious organisations including J&J, Deutsche, HSBC, BNP Paribas, UBS Banks, HMRC and Network Rail.
Guy Dietrich, the managing director of Rockefeller Capital (manages $19 Billion in assets) has joined the board of Quant Network, and has recently personally attended meetings with the Financial Conduct Authority (FCA) with Gilbert

https://preview.redd.it/wj5ubgv4efl31.png?width=566&format=png&auto=webp&s=2c0cb650f6aceae3d133beefdac04ba0aeea63f6
As well as advisors such as Paolo Tasca, the founder and Executive Director of the Centre for Blockchain Technologies (UCL CBT) at University College Londonfounder and executive director as well as Chris Adelsbach, Managing Director at Techstars, the worldwide network that helps entrepreneurs succeed. Techstars has partners such as Amazon, Barclays, Boeing, Ford, Google, Honda, IBM, Microsoft, PWC, Sony, Target, Total, Verizon, Western Union etc.
Due to client demand they are expanding to the US to setup a similar size office where board members such as Guy Dietrich will be extremely valuable in assisting with the expansion.
https://preview.redd.it/7zlrragqffl31.png?width=578&format=png&auto=webp&s=36980e86da6d050f086eb2171f679ac1716f97dc
The most exciting part about the project though is just how much adoption there has been of the platform, from huge global enterprises, governments and cloud providers they are on track for a revenue of $10 million in their first year. I will go through these in the next article, followed by further article explaining how the Token and Treasury works.
You can also find out more info about Quant at the following:
Part One — Blockchain Fundamentals
Part Two — The Layers Of Overledger
Part Three — TrustTag and the Tokenisation of data
Part Four — Features Overledger provides to MAPPs
Part Five — Creating the Standards for Interoperability
Part Six — The Team behind Overledger and Partners
Part Seven — The QNT Token
Part Eight — Enabling Enterprise Mass Adoption
Quant Network Enabling Mass Adoption of Blockchain at a Rapid Pace
Quant Network Partner with SIA, A Game Changer for Mass Blockchain Adoption by Financial Institutions
submitted by xSeq22x to CryptoCurrency [link] [comments]

What is Quant Networks Blockchain Operating System, Overledger? And why are Enterprises adopting it at mass scale?

Won't let me post the related images here, but please refer to this article which includes them https://medium.com/@CryptoSeq/what-is-a-blockchain-operating-system-and-what-are-the-benefits-c561d8275de6
Overledger is the world’s first blockchain operating system (OS) that not only inter-connects blockchains but also existing enterprise platforms, applications and networks to blockchain and facilitates the creation of internet scale multi-chain applications otherwise known as mApps.
In less than 10 months since launching Overledger they have provided interoperability with the full range of DLT technologies from all the leading Enterprise Permissioned blockchains such as Hyperledger, R3’s Corda, JP Morgan’s Quorum, permissioned variants of Ethereum and Ripple (XRPL) as well as the leading Public Permissionless blockchains / DAGs such as Bitcoin, Stellar, Ethereum, IOTA and EOS as well as the most recent blockchain to get added Binance Chain. In addition, Overledger also connects to Existing Networks / Off Chain / Oracle functionality and it does all of this in a way that is hugely scalable, without imposing restrictions / requiring blockchains to fork their code and can easily integrate into existing applications / networks by just adding 3 lines of code.

What is a blockchain Operating system?

You will be familiar with Operating systems such as Microsoft Windows, Apple Mac OS, Google’s Android etc but these are all Hardware based Operating Systems. Hardware based Operating Systems provide a platform to build and use applications that abstracts all of the complexities involved with integrating with all the hardware resources such as CPU, Memory, Storage, Mouse, Keyboard, Video etc so software can easily integrate with it. It provides interoperability between the Hardware devices and Software.
Overledger is a Blockchain Operating System, it provides a platform to build and use applications that abstracts all of the complexities involved with integrating with all the different blockchains, different OP_Codes being used, messaging formats etc as well as connecting to existing non-blockchain networks. It provides interoperability between Blockchains, Existing Networks and Software / MAPPs

How is Overledger different to other interoperability projects?

Other projects are trying to achieve interoperability by adding another blockchain on top of existing blockchains. This adds a lot of overhead, complexity, and technical risk. There are a few variants but essentially they either need to create custom connectors for each connected blockchain and / or require connected chains to fork their code to enable interoperability. An example of the process can be seen below:
User sends transaction to a multi sig contract on Blockchain A, wait for consensus to be reached on Blockchain A
A custom connector consisting of Off Chain Relay Nodes are monitoring transactions sent to the smart contract on Blockchain A. Once they see the transaction, they then sign a transaction on the Interoperability blockchain as proof the event has happened on Blockchain A.
Wait for consensus to be reached on the Interoperability Blockchain.
The DAPP running on the Interoperability Blockchain is then updated with the info about the transaction occurring on Blockchain A and then signs a transaction on the Interoperability blockchain to a multi sig contract on the Interoperability Blockchain.
Wait for consensus to be reached on the interoperability Blockchain.
A different custom connector consisting of Off Chain Relay Nodes are monitoring transactions sent to the Smart Contract on the Interoperability Blockchain which are destined for Blockchain B. Once they see the transaction, they sign a transaction on Blockchain B. Wait for consensus to be reached on Blockchain B.

Other solutions require every connecting blockchain to fork their code and implement their Interoperability protocol. This means the same type of connector can be used instead of a custom one for every blockchain however every connected blockchain has to fork their code to implement the protocol. This enforces a lot of restrictions on what the connected blockchains can implement going forward.
Some problems with these methods:

But some Interoperability blockchains say they are infinitely scalable?

If the interoperability blockchain is limited to say 200 tps then the idea is to just have multiple instances of the blockchain and run them in parallel, so you benefit from the aggregated tps, but just how feasible is that? Lets say you want to connect Corda (capable of 2000+ tps) to Hyperledger (capable of up to 20,000 tps with recent upgrade). (Permissioned blockchains such as Hyperledger and Corda aren’t one big blockchain like say Bitcoin or Ethereum, they have separate instances for each consortium and each is capable of those speeds). So even when you have just 1 DAPP from one consortium that wants to connect Corda to Hyperledger and use 2000 tps for their DAPP, you would need 100 instances of the Interoperability blockchain, each with their own validators (which maybe 100–200 nodes each). So, 1 DAPP would need to cover the costs for 100 instances of the blockchain and running costs for 10,000 nodes…This is just one DAPP connected to one instance of a two permissioned blockchains, which are still in the early stages. Other blockchains such as Red Belly Blockchain can achieve 440,000 tps, and this will surely increase as the technology matures. There is also the added complexity of then aggregating the results / co-coordinating between the different instances of the blockchain. Then there are the environmental concerns, the power required for all of these instances / nodes is not sustainable.
It’s not just transactions per second of the blockchain as well, its the latency of all these added consensuses along the path to reach to the destination and not knowing whether the security of each of the hops is sufficient and can be trusted. To see examples of how this potential issue as well as others effect Cosmos you can see my article here. I recommend also reading a blog done by the CEO of Quant, Gilbert Verdian, which explains how Overledger differs here as well as detailed in the whitepaper here.

Overledger’s approach

In 1973 Vint Cerf invented the protocol that rules them all: TCP/IP. Most people have never heard of it. But it describes the fundamental architecture of the internet, and it made possible Wi-Fi, Ethernet, LANs, the World Wide Web, e-mail, FTP, 3G/4G — as well as all of the inventions built upon those inventions.
Wired: So from the beginning, people, including yourself, had a vision of where the internet was going to go. Are you surprised, though, that at this point the IP protocol seems to beat almost anything it comes up against? Cerf: I’m not surprised at all because we designed it to do that. This was very conscious. Something we did right at the very beginning, when we were writing the specifications, we wanted to make this a future-proof protocol. And so the tactic that we used to achieve that was to say that the protocol did not know how — the packets of the internet protocol layer didn’t know how they were being carried. And they didn’t care whether it was a satellite link or mobile radio link or an optical fiber or something else. We were very, very careful to isolate that protocol layer from any detailed knowledge of how it was being carried. Plainly, the software had to know how to inject it into a radio link, or inject it into an optical fiber, or inject it into a satellite connection. But the basic protocol didn’t know how that worked. And the other thing that we did was to make sure that the network didn’t know what the packets had in them. We didn’t encrypt them to prevent it from knowing — we just didn’t make it have to know anything. It’s just a bag of bits as far as the net was concerned. We were very successful in these two design features, because every time a new kind of communications technology came along, like frame relay or asynchronous transfer mode or passive optical networking or mobile radio‚ all of these different ways of communicating could carry internet packets. We would hear people saying, ‘The internet will be replaced by X25,’ or ‘The internet will be replaced by frame relay,’ or ‘The internet will be replaced by APM,’ or ‘The internet will be replaced by add-and-drop multiplexers.’ Of course, the answer is, ‘No, it won’t.’ It just runs on top of everything. And that was by design. I’m actually very proud of the fact that we thought of that and carefully designed that capability into the system.
This is the approach Quant have taken with their Blockchain OS, Overledger to solve Blockchain interoperability. Compared to other Interoperability platforms that are trying to achieve interoperability at the transaction layer by connecting two blockchains via another blockchain, these will be ultimately be made redundant once faster methods are released. Overledger is designed to be future proof by isolating the layers so it doesn’t matter whether it’s a permissioned blockchain, permissionless, DAG, Legacy network, POW, POS etc because it abstracts the transaction layer from the messaging layer and runs on top of blockchains. Just as the Internet wasn’t replaced by X25, frame relay, APM etc, Overledger is designed to be future proof as it just runs on top of the Blockchains rather than being a blockchain itself. So, if a new blockchain technology comes out that is capable of 100,000 TPS then it can easily be integrated as Overledger just runs on top of it.
Likewise, with protocols such as HTTPS, SSH etc these will also emerge for blockchains such as ZK-Snarks and other privacy implementations as well as other features made available, all will be compatible with Overledger as its just sitting on top rather than forcing their own implementation for all.
It doesn’t require blockchains to fork their code to make it compatible, it doesn’t add the overhead of adding another blockchain with another consensus mechanism (most likely multiple as it has to go through many hops). All of this adds a lot of latency and restrictions which isn’t needed. The developer can just choose which blockchains they want to connect and use the consensus mechanisms of those blockchains rather than forced to use one.
Overledger can provide truly internet scale to meet whatever the demands may be, whether that be connecting multiple red belly blockchains together with 440,000 tps it doesn’t matter as it doesn’t add its consensus mechanism and uses proven internet scale technology such as that based on Kubernetes, which is where each task is split up into a self-contained container and each task is scaled out by deploying more to meet demand. Kubernetes is what runs Google Search engine where they scale up and down billions of containers every week.
Due to this being more of a summary, I strongly recommend you read this article which goes into detail about the different layers in Overledger.

But how does it provide the security of a blockchain if it doesn’t add its own blockchain?

This is often misunderstood by people. Overledger is not a blockchain however it still uses a blockchain for security, immutability, traceability etc, just rather than force people to use their own blockchain, it utilises the source and destination blockchains instead. The key thing to understand is the use of its patented technology TrustTag, which was made freely available to anyone with the Overledger SDK.
Please see this article which explains TrustTag in detail with examples showing how hashing / digital signatures work etc
A quick overview is if i want to send data from one blockchain to another the Overledger SDK using Trusttag will put the data through a hashing algorithm. The Hash is then included in digital signature as part of the transaction which is signed by the user’s private key and then validated through normal consensus and stored as metadata on the source blockchain. The message is then sent to the MAPP off chain. The MAPP periodically scans the blockchains and puts the received message through a hashing algorithm and compares the Hash to the one stored as metadata on the blockchain. This ensures that the message hasn’t been modified in transit, the message is encrypted and only the Hash is stored on chain so completely private, provides immutability as it was signed by the user’s private key which only they have and is stored on the blockchain for high availability and secure so that it can’t be modified, with the ability to refer back to it at any point in time.
Despite Overledger being a very secure platform, with the team having a very strong security background such as Gilbert who was chief security information officer for Vocalink (Bank of England) managing £6 trillion of payments every year and classified as national critical security (highest level you can get), ultimately you don’t need to trust Overledger. Transactions are signed and encrypted at client side, so Overledger has no way of being able to see the contents. It can’t modify any transaction as the digital signature which includes a hash of the transaction would be different so would get rejected. Transaction security isn’t reduced as it is signed at source using however many nodes the source blockchain has rather than a smaller amount of nodes with an interoperability blockchain in the middle.

Patents

The core code of Overledger is closed source and patented, one of the recent patents can be seen here, along with TrustTag and further ones are being filed. The Overledger SDK is open source and is available in Java and Javascript currently, with plans to support Pyhton and Ruby in the near future. Java and Javascript are the most popular programming languages used today.
The Blockchain connectors are also open source and this allows the community to create connectors to connect their favourite blockchain so that it can benefit from blockchain interoperability and making it available to all enterprises / developers currently utilising Overledger. Creating is currently taking around a week to implement and so far, have been added based upon client demand.

Multi Chain Applications (MAPPs)

Multi Chain Applications (MAPPs) enable an application to use multiple blockchains and interoperate between them. Treaty Contracts enable a developer to build a MAPP and then change the underlying blockchain it uses with just a quick change of couple of lines of code. This is vital for enterprises as it’s still early days in Blockchian and we don’t know which are going to be the best blockchain in the future. Overledger easily integrates into existing applications using the Overledger SDK by just adding 3 lines of code. They don’t need to completely rewrite the application like you do with the majority of other projects and all existing java / javascript apps on Windows / Mobile app stores / business applications etc can easily integrate with overledger with minimal changes in just 8 minutes.

Treaty Contracts

What Overledger will allow with Treaty contracts is to use popular programming languages such as Java and create a smart contract in Overledger that interacts with all of the connected blockchains. Even providing Smart contract functionality to blockchains that don’t support them such as Bitcoin. This means that developers don’t have to create all the smart contracts on each blockchain in all the different programming languages but instead just create them in Overledger using languages such as Java that are widely used today. If they need to use a different blockchain then it can be as easy as changing a line of code rather than having to completely rewrite the smart contracts.
Overledger isn’t a blockchain though, so how can it trusted with the smart contract? A Hash of the smart contract is published on any blockchain the MAPP developer requires and when called the smart contract is run its run through a hashing function to check that it matches the Hash value stored on the blockchain, ensuring that it has not been modified.
By running the Smart contract off chain this also increases Scalability enormously. With a blockchain all nodes have to run the smart contract one after another rather than in parallel. Not only do you get the performance benefit of not having to run the code against every single node but you can also run them in parallel to others executing smart contracts.
You can read more about Treaty Contracts here

The different versions of Overledger

Enterprise version

The current live version is the Enterprise version as that is where most of the adoption is taking place in blockchain due to permissioned blockchains being preferred until permissionless blockchains resolve the scalability, privacy and regulatory issues. Please see this article which goes into more details about Entereprise blockchain / adoption. The Enterprise version connects to permissioned blockchains as well as additional features / support suited for Enterprises.

Community version

The community version is due to be released later this year which will allow developers to benefit from creating MAPPs across permissionless blockchains. Developers can publish their MAPPs on the MAPP Store to create additional revenue streams for developers.

Where does Overledger run from? Is it Centralised?

Overledger can run from anywhere. The community version will have instances across multiple public clouds, Enterprises / developers may prefer to host the infrastructure themselves within a consortium which they can and are doing. For example SIA is the leading private Financial Network provider in Europe, it provides a dedicated high speed network which connects all the major banks, central banks, trading venues etc. SIA host Overledger within their private network so that all of those clients can access it in the confinement of their heavily regulated, secure, fast network. AUCloud / UKCLoud host Overledger in their environment to offer as a service to their clients which consist of Governments and critical national infrastructure.
For Blockchain nodes that interact with Overledger the choice is entirely up to the developer. Each member within a consortium may choose to host a node, some developers may prefer to use 3rd party hosting providers such as Infura, or Quant can also host them if they prefer, its entirely their choice.
Overledger allows for higher levels of decentralisation by storing the output across multiple blockchains so you not only benefit from the decentralisation of one blockchain but the combination of all of them. Ultimately though decentralisation is thrown around too much without many actually understanding what it means. It’s impossible to have complete decentralisation, when you sign a transaction to be added to a blockchain ultimately you still connect through a single ISP, connect through a single router, or the input into a transaction is done through a piece of software etc. What matters to be decentralised is where trust is involved. As i have mentioned before you don’t need to trust the OS, it’s just providing instructions on how to interact with the blockchains, the end user is signing the transactions / encrypting at client side. Nothing can be seen or modified with the OS. Even if somehow the transaction did get modified then it would get rejected when consensus is done as the hash / digital signature won’t match at the destination blockchain. Where the transaction actually gets put onto the blockchain is where decentralisation matters, because thats what needs to be trusted and conensus is reached and Overledger enables this to be written across multiple blockchains at the same time.

The Team

The team are very well connected with a wealth of experience at very senior roles at Global enterprises which I will include a few examples below. Gilbert Verdian the CEO was the Head of security for the payment infrastructure for the Bank of England through his CISO role with Vocalink (Mastercard)managing £6 trillion every year. This is treated by the government as critical national infrastructure which is the highest level of criticallity because its so fundamental to the security of the country. They have experience and know what it takes to run a secure financial infrastructure and meeting requirements of regulators. Gilbert was director for Cybersecurity at PWC, Security for HSBC and Ernst & Young as well as various government roles such as the CISO for the Australian NSW Health, Head of Security at the UK government for Ministry of Justice and HM Treasury in addition to being part of the committee for the European Commission, US Federal Reserve and the Bank of England.
Cecilia Harvey is the Chief Operating Officer, where she was previously a Director at HSBC in Global Banking and Markets and before that Director at Vocalink. Cecilia was also Chief Operating Officer at Citi for Markets and Securities Services Technology as well as working for Barclays, Accenture, IBM and Morgan Stanley.
Vijay Verma is the Overledger platform lead with over 15 years of developer experience in latest technologies like Java, Scala, Blockchain & enterprise technology solutions. Over the course of his career, he has worked for a number of prestigious organisations including J&J, Deutsche, HSBC, BNP Paribas, UBS Banks, HMRC and Network Rail.
Guy Dietrich, the managing director of Rockefeller Capital (manages $19 Billion in assets) has joined the board of Quant Network, and has recently personally attended meetings with the Financial Conduct Authority (FCA) with Gilbert
https://twitter.com/gverdian/status/1168628166644183042
As well as advisors such as Paolo Tasca, the founder and Executive Director of the Centre for Blockchain Technologies (UCL CBT) at University College Londonfounder and executive director as well as Chris Adelsbach, Managing Director at Techstars, the worldwide network that helps entrepreneurs succeed. Techstars has partners such as Amazon, Barclays, Boeing, Ford, Google, Honda, IBM, Microsoft, PWC, Sony, Target, Total, Verizon, Western Union etc.
Due to client demand they are expanding to the US to setup a similar size office where board members such as Guy Dietrich will be extremely valuable in assisting with the expansion.
The most exciting part about the project though is just how much adoption there has been of the platform, from huge global enterprises, governments and cloud providers they are on track for a revenue of $10 million in their first year. I will go through these in the next article, followed by further article explaining how the Token and Treasury works.
You can also find out more info about Quant at the following:
Part One — Blockchain Fundamentals
Part Two — The Layers Of Overledger
Part Three — TrustTag and the Tokenisation of data
Part Four — Features Overledger provides to MAPPs
Part Five — Creating the Standards for Interoperability
Part Six — The Team behind Overledger and Partners
Part Seven — The QNT Token
Part Eight — Enabling Enterprise Mass Adoption
Quant Network Enabling Mass Adoption of Blockchain at a Rapid Pace
Quant Network Partner with SIA, A Game Changer for Mass Blockchain Adoption by Financial Institutions
submitted by xSeq22x to CryptoMoonShots [link] [comments]

Bitcoin: Beyond The Bubble - Full Documentary - YouTube This Bitcoin Price Metric Is Up 940% Since BTC $20,000 High  Chainlink (LINK) Nears $5 ATH Brave(BAT) Partners with Binance, Kyber(KNC) protocol upgrade and demand increase, livestream recap Cryptoverse - YouTube Why Didn't Bitcoin BOUNCE YET? - Weakness Binance CZ - Ethereum Special Campaign and Platform Latest ... Bitcoin Back OVER $10,400! BAKKT? Highest BTC Hash Rate  Use Shopify With Bitcoin Lightning Network How to hack Bitcoin - Cracking CryptoCurrency Brainwallets Hot! Get Free Bitcoins and Claim Daily! Horizen (ZEN) Airdrop

Difficulty is measured in the hashes per second of the Bitcoin validation transaction. Was brauche ich fürs Bitcoin-Mining? Bitcoin miners are in a 'hash rate arms race,' and that's driving the costs of minting new bitcoin to all-time highs.Fully Comprehensive Blockgeeks Guide We as a team firmly believe in the bitcoin as a foundation of innovative space, capable of reshaping real Bitcoin ... On January 1, the BTC network hashrate touched an all-time high at close to 120 exahash per second (EH/s). Despite the crypto market lull and lower BTC prices, the 2020 milestone happened just ... Hash rate measures the number of times a hash function can be computed per second. A hash function — which for bitcoin in SHA256 — takes an input of any length and produces an output with a specified length. However, with hash functions, the same input will always produce the same output, and if you want to find an input that hashes to a specific output, you need to try random inputs until ... SHA stand for “Secure hash Algorithm” (SHA-256) generates unique 256-bit (32-byte) signature for a text string. Block processing time for SHA-256 generally ranges from six to ten minutes and requires hash rates at the Giga hashes per second (GH/s). SHA-256 hash measure: GH/s: Gigahashes per second, or one billion hash computations per second. According to statistics from the Crypto51 application, BTG only has 3 million hashes per second (3MH/s) securing the chain. It would only cost $788 per hour to 51% attack the BTG blockchain and ... Below are various Bitcoin Mining ASIC hardware and their performance. Mhash/s = millions hashes per second; Mhash/J = millions hashes per joule; W = watt (maximum power consumption, i.e. energy per unit of time: 1 W = 1 J/s) ASIC. Some of the information on this chart may be outdated. Always do sufficient research before purchasing any hardware ... The algorithm used by Bitcoin for the hash function is SHA-256, which produces a 256-bit hash and requires a predictable amount of processing power from the computer. To add a new block to the Bitcoin blockchain, a data packet of queued transactions in the mempool waiting to be confirmed is used as input to the hash function.

[index] [13719] [18587] [19027] [12745] [23788] [2430] [6146] [6862] [18671] [15659]

Bitcoin: Beyond The Bubble - Full Documentary - YouTube

Horizen (ZEN) Airdrop. Make money online and I will teach you how to earn free bitcoins. Fast and instant withdrawals. You can claim once a day and no need invite! Make money using your mobile ... Bitcoin Technical Analysis & Bitcoin News Today: The Bitcoin hashrate is breaking record after record and is at an all-time high right now. Also, I'll use technical analysis on the Bitcoin price ... Thanks for watching! For donations: Bitcoin - 1CpGMM8Ag8gNYL3FffusVqEBUvHyYenTP8 Brave(BAT) Partners with Binance, Kyber(KNC) protocol upgrade and demand increase, livestream recap ----- Check out my other channels: My other... Case in point: the hash rate of the Bitcoin network reached a new all-time high of 136 exahashes (or 136,000,000 terahashes) per second just two days ago - nearly three times higher than it was ... Bitcoin COULD HIT $11,400 THIS WEEK? ️LIVE Crypto Trading Analysis TA &BTC Cryptocurrency Price News - Duration: 27:34. Crypto Kirby Trading 15,633 views 27:34 WHAT IS BITCOIN MINING HASH RATE? HOW HASH RATE CALCULATES? IN HINDI & URDU - Duration: 10 minutes, 30 seconds. 370 views; 1 month ago; 19:46. BITCOIN MINING POOLS SHUT DOWN, SOLONA BINANCE LISING How to hack Bitcoin - Cracking CryptoCurrency Brainwallets Imagine a bank that, by design, made everyone's password hashes and balances public. No two-factor authentication, no backsies on ... Bitcoin rewards last fell on 9 July 2016 at the point of the second halving – an event which saw the block reward fall from 25 new bitcoin per block to 12.5 bitcoin. Bitcoin’s price surged ... This market trading analysis applies to various exchanges, including Bitmex and Binance. Tackling questions like if Bitcoin can reach 20k again and if we will be seeing a crypto currency market ...

#