forked from hyperledger-archives/hyperledgerwp
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Modified some wording to avoid confusion that there is a single Hyperledger blockchain (line 5) - Minor edits - Note: We use the acronym DLT but also Distributed Ledger Technology. Since we've used DLT in earlier sections, I think we can just use DLT off the bat. I didn't make any changes to this yet as I wanted to see what others thought.
- Loading branch information
1 parent
5ab0d7a
commit 8765095
Showing
1 changed file
with
5 additions
and
5 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,9 +1,9 @@ | ||
We already live in a highly interconnected world. In the future, we believe that the world will become even more closely tied together: more data sharing, more communication, and more digital content will become the norm in both business and personal lives. This will necessitate careful management of security, privacy, and trust. We view distributed ledger technology as the solution to the problem where someone needs a distributed database for which there is no single owner that is trusted by all of the users. Thus, as interconnection increases, we believe that blockchain and DLT will become quite prevalent in society as distributed ledgers replace some (but not all) traditional databases. | ||
We already live in a highly interconnected world. In the future, we believe that the world will become even more closely tied together: more data sharing, more communication, and more digital content, will become the norm in both our business and personal lives. This will necessitate careful management of security, privacy, and trust. We view distributed ledger technology as the solution to the problem where someone needs a distributed database for which there is no single owner that is trusted by all of the users. Thus, as interconnection increases, we believe that blockchain technology and DLT as a whole will become quite prevalent in society as distributed ledgers replace some, but not all, traditional databases where viable. | ||
|
||
This prevalence of distributed ledgers will not come about without difficulty, however. Nothing in this space is `for free'--for instance, if you want a great deal of security and privacy features in a blockchain, you will often pay the price in terms of performance. This implies that we will need to have a large variety of different blockchains--no one blockchain will work for all applications--that can communicate and interact seamlessly. | ||
This prevalence of distributed ledgers will not come about without difficulty, however. Nothing in this space is "for free". For instance, if you want a great deal of security and privacy features in a blockchain, you will often pay the price in terms of performance. This implies that we will need to have a large variety of different blockchains--no one blockchain will work for all applications--that can communicate and interact seamlessly. | ||
|
||
Thus, our long-term vision for Hyperledger is driven by two main architectural concerns: modularity and interoperability. We hope that, eventually, Hyperledger consists of lots of modules for various different blockchain components that can be put together by a non-expert into a cohesive, functional, and secure distributed ledger. All of these modules would be interchangeable with other modules of the same time, and able to communicate with other modules of different types (or the same type if involved in communication between separate blockchains). This would ideally enable a non-expert to set up an interoperable, secure blockchain quickly, easily, and efficiently. | ||
Thus, our long-term vision for Hyperledger is driven by two main architectural concerns: modularity and interoperability. We hope that, eventually, Hyperledger consists of lots of modules for various different blockchain components that can be put together by a non-expert into a cohesive, functional, and secure distributed ledger. All of these modules would be interchangeable with other modules of the same time, and able to communicate with other modules of different types (or the same type if involved in communication between separate blockchains). This would ideally enable a non-expert to set up an interoperable and secure blockchain quickly, easily, and efficiently. | ||
|
||
We want to specifically point out that we do not believe Hyperledger should be the `one distributed ledger to rule them all'. The technical community of Hyperledger sees merit in many diverse blockchains, and, while we hope that other developers consider interoperability with Hyperledger. We do not intend for Hyperledger to be a single stack. Instead, we hope that it becomes a collection of tools purpose built with interoperability and modularity in mind. Any individual can use one, some, or all of the Hyperledger projects to to create a distributed ledger to suit their needs. | ||
We want to specifically point out that we do not believe any Hyperledger blockchain should be the `one distributed ledger to rule them all'. The Hyperledger community sees merit in many diverse blockchains and we hope that other developers consider interoperability with Hyperledger projects. We do not intend for Hyperledger to be a single stack. Instead, we hope that it becomes a collection of tools purpose built with interoperability and modularity in mind. Any individual can use one, some, or all of the Hyperledger projects to to create a distributed ledger to suit their needs. | ||
|
||
In the future, we hope that Hyperledger can solve most of the common problems in the distributed ledger space. This will necessitate a good community, strong industrial support, and solid design principles, and, as we have hopefully illustrated in this paper, we have structured Hyperledger with these tenets in mind. It is now up to us to go out and accomplish this. | ||
In the future, we hope that Hyperledger can solve most of the common problems in the distributed ledger space. This will necessitate a good community, strong industrial support, and solid design principles. As we have hopefully illustrated in this paper, we have structured Hyperledger with these tenets in mind. It is now up to us to go out and accomplish this. |