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.
why
- Loading branch information
Showing
4 changed files
with
46 additions
and
0 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 |
---|---|---|
@@ -0,0 +1,15 @@ | ||
At Hyperledger, all projects follow a design philosophy that includes a modular extensible approach, interoperability, emphasis on highly secure solutions, a token agnostic approach with no native cryptocurrency and the development of a rich and easy-to-use Application Program Interface (API). | ||
|
||
Distributed ledgers for different use cases can have vastly different requirements. For instance, in use cases where participants have high trust between one another, such as many financial applications, blockchains can use rapid network consensus systems and short block confirmation times before being added to the chain. However, other applications where there is minimal trust between participants may tolerate slower processing times. | ||
|
||
Hyperledger embraces the full spectrum of these uses cases, especially enterprise scenarios with widely varied requirements for decentralization, trust, continuity, confirmation times, etc. Each represents a potentially unique “optimization point” for the technology. To address this, Hyperledger is developing modular, extensible frameworks that allow the re-use of common building blocks, while enabling experimentation and evolution with DLT components. This modular approach enables extensibility and flexibility by defining common functional modules and the interfaces between them. This allows components to be changed independently without affecting the rest of the system. We are in the early stages in the evolution of DLT systems, and by taking a modular approach we will be able to experiment with different approaches to functional components. A modular approach allows us to develop optimal components which may be combined to compose DLT solutions that are best suited to different sets of requirements. Another advantage of the modular approach is that it allows a diverse community of developers to work independently on different modules, and allows the re-use of common modules across multiple projects. We define modules and interfaces for consensus, ledger storage, smart contract, communication, identity and policy and crypto functions\footnote{The architecture working group rocks!}. | ||
|
||
Security is a key consideration for distributed ledgers, as many use cases may involve high value transactions or otherwise sensitive data. Securing a blockchain is quite a difficult task: distributed ledger components must be secure against online, persistent adversaries while still containing a large, feature-rich set of functionalities. The large codebase and open, networked nature of distributed ledgers make them prime targets for attackers. | ||
|
||
In Hyperledger we view security and robustness as key aspects of Enterprise class blockchains and DLTs, which will evolve into critical infrastructure for next generation business networks. This includes embracing security by design and following best practices as specified by the Linux Foundation’s Core Infrastructure Initiative, and ensuring that the algorithms, protocols and crypto are reviewed and audited by security experts. | ||
|
||
Interoperability and portability are key aspects for the work done under the Hyperledger umbrella. We envision that there will be many interconnected blockchain networks which will need to communicate and interact with each other to form potentially complicated networks. It is also highly desirable that smart contracts and applications be portable across different instances of blockchain/DLT networks in order to make development easier. | ||
|
||
Hyperledger is independent and agnostic of currency and tokens. In Hyperledger we do not require a native token either as a means to provide incentives to operate the network or for resource management.The explicit focus on managing digital objects (which may represent currencies) removes the requirement for intrinsic crypto-currencies and native tokens. | ||
|
||
Hyperledger projects will also supports a well defined set of API’s and SDK’s that allows external clients and applications to interface with core DLT infrastructure. These API’s will enable a rich developer ecosystem that is needed to be successful in proliferating blockchain and DLT solutions across a diverse set of markets and use cases. |
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
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 |
---|---|---|
@@ -0,0 +1,11 @@ | ||
While blockchain is a powerful piece of technology, it is not a one-size-fits-all solution. Modifications and special features are needed in order for it to operate at an optimal level, or even operate at all for its intended purpose. Customized functionality and features are essential to making blockchain technology the appropriate solution for the organization that uses it. Since organizations have varying needs, it can be assumed that there will be multiple blockchains customized with different features for a wide-range of solutions instead of a single standard blockchain. | ||
|
||
Because of this development of multiple systems, collaboration plays a larger role in order to help reduce the overall resources consumed with these efforts. For example, navigating through various developments in an open source environment can be daunting and subsequently cause organizations to forego keeping up with the changes or starting at all due to significant costs. Hyperledger fills this organizational need and makes the coordination process more effective by creating a collaborative environment that streamlines project development and communication. With this environment, keeping up with the various developments in the blockchain industry is simplified. This also makes it easier for newer participants that join the umbrella organization to catch up with the latest developments as information is properly structured to ensure that new participants have an easy way of joining the collaborative effort. | ||
|
||
The umbrella organization structure also allows for specialization among the participants. Specialization has historically proven to be a driving factor in global economic development and the same benefits can be realized with participants specializing in various areas of the technology. Outside an umbrella organization, such would still be possible in an open source environment, but would be much more difficult. As communication and collaboration is streamlined, implementation of these developments and access to necessary information can be done with ease across various projects for the benefit of the entire ecosystem. However, unlike most cases, participants that specialize in similar areas won’t be competing against each other. With an umbrella organization, joint research efforts are not only possible, but also encouraged in order to prevent duplicate efforts, which have a stronger negative effect in a relatively new industry where the development pool is not yet deep.. | ||
|
||
The umbrella organization facilitates more collaboration between industry participants than would otherwise occur. This can streamline the development of newer projects and avoid duplicative efforts by allowing for the creation of common components that benefit the entire community. Interoperability between ledgers, similar or not, also becomes much more of a possibility, not just because of a better understanding of the other ledger projects, but also because of the collaborative environment. The governing structure provided by Hyperledger also helps solve potential interoperability disputes that may arise. | ||
|
||
The structure enforces quality control by having a technical governing committee review all projects throughout their life cycles. For new projects, this provides a chance to be critiqued and gain knowledge from members of all existing projects. Cross-project exposure increases the likelihood of collaboration, which can potentially mitigate duplicated efforts. Additionally, existing project members may discover innovations and developments introduced by the new projects, and implement them in their own projects. This structure also fosters potential interoperability between new and old projects. | ||
|
||
Consistency of licenses and handling of intellectual property is another value provided by the umbrella organization. In particular, Hyperledger operates under an Apache 2.0 license for code and Creative Commons Attribution 4.0 International license for content. These licenses are known to be particularly enterprise friendly. A single, consistent approach to intellectual property removes the need for expensive and complex development relationships amongst the members. Expectations for participants are clearly communicated and those building and using Hyperledger technologies can participate without fear of hidden legal encumbrances. |
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 |
---|---|---|
@@ -0,0 +1,11 @@ | ||
The concept of trust is indelibly woven into the very essence of blockchain technologies. It must be for the reason discussed above - blockchain technologies are used to enable direct, peer-to-peer transactions between parties that don’t fully trust one another or have a trusted central authority. Consequently, trust in the blockchain technologies themselves is an essential prerequisite to their adoption. | ||
|
||
We believe that an open source, collaborative approach that invites participation from all stakeholders is the most effective way to produce the necessary degree of trust in blockchain technologies for businesses to broadly and rapidly adopt them. The transparency of open source development facilitates audit and review from a diverse community of experts. This practice of open development and review is standard within the security and cryptography communities to ensure correctness of concept and implementation. | ||
|
||
An effective open source project must have an open governance model, an open development model and an open review model. Hyperledger fully embraces the transparency and openness common to Linux Foundation Projects, which provides the legal, governance, technical, logistical and promotional structure that all software initiatives need. Anyone can download the codebase and start contributing, and the positions of authority are determined in an open and democratic manner. | ||
|
||
The open source structure has been the driving force of the growing number of distinct software projects, contributors, meet-up groups, hackfests, and corporate members, all under the Hyperledger umbrella. Companies deploying blockchain internally, and those building products and services based on Hyperledger projects tell us that their trust and confidence comes from knowing that Hyperledger technologies are built in the open, with and by an extremely broad consortium of users and vendors regularly reviewing and checking the code to ensure that it is of the highest standard. | ||
|
||
The open source nature of Hyperledger technologies also ensures no surprises when it comes to integration and interoperability between various blockchains - something we believe will be very common in the poly-chain future we expect. We expect that achieving needed interaction across proprietary chains would otherwise be much more difficult. In addition to interoperability between different chains, the open source nature of Hyperledger will enable more application portability between various blockchain implementations, hopefully leading to easier application creation for developers. | ||
|
||
Economics is also powerfully on the side of a collaborative development effort like Hyperledger. Businesses as diverse as banks, car and plane makers, healthcare companies and a broad ecosystem of vendors, all need robust, feature-rich, modular blockchain platforms that they can tailor to meet their exact needs. When all these different users and vendors collaborate to co-create common platform technologies, the investment required from each is a fraction of what it would be if each created their own. |