Introduction
Business blockchain requirements vary. Some uses require rapid network consensus
systems and short block confirmation times before being added to the chain. For others,
a slower processing time may be acceptable in exchange for lower levels of required
trust. Scalability, confidentiality, compliance, workflow complexity, and even security
requirements differ drastically across industries and uses. Each of these requirements, and
many others, represent a potentially unique optimization point for the technology.
For these reasons, Hyperledger incubates and promotes a range of business blockchain
technologies including distributed ledgers, smart contract engines, client libraries, graphical
interfaces, utility libraries, and sample applications. Hyperledger’s umbrella strategy
encourages the re-use of common building blocks via a modular architectural framework.
This enables rapid innovation of distributed ledger technology (DLT), common functional
modules, and the interfaces between them. The benefits of this modular approach include
extensibility, flexibility, and the ability for any component to be modified independently
without affecting the rest of the system.
This document discusses distributed ledger technology and its potential applications. It begins with an overview of how record keeping has evolved from stone tablets to today's digital systems. It then explains that ledgers are now shifting to a global network of cryptographically secure and decentralized computers using distributed ledger technology. Examples of distributed ledger technologies include blockchain, hashgraph, and directed acyclic graphs. The document outlines several potential real-world applications of distributed ledger technology such as securing copyrighted content, insurance, and digital voting.
Distributed Systems for Blockchain using CloudHridyesh Bisht
1. The document discusses implementing blockchain using cloud computing. Blockchain provides a distributed ledger and enables secure transfer of assets without intermediaries. It consists of blocks, miners, and nodes.
2. Several research papers are reviewed that propose using blockchain for data provenance in cloud storage. Blockchain can provide tamper-proof records and transparency of data accountability. It also enhances privacy and availability of provenance data.
3. Implementing blockchain using cloud computing provides benefits like better decentralization, efficient ownership tracking, increased data security, faster disaster recovery, and geo-independence. Security challenges like 51% attacks are also discussed.
Distributed systems and blockchain technologyAlket Cecaj
Blockchain is a distributed ledger system where nodes work together to validate transactions in a coordinated fashion without a central authority. It allows for decentralized consensus through mechanisms like proof-of-work. The main challenges in distributed systems are coordination between nodes and achieving fault tolerance. The CAP theorem states that a distributed system cannot achieve consistency, availability, and partition tolerance simultaneously. Blockchain sacrifices consistency for availability and partition tolerance. It uses elements like addresses, transactions, blocks, and consensus mechanisms like proof-of-work to securely and immutably record transactions on the distributed ledger.
Is Azure Blockchain Cloud the Future of Cloud Computing | SysforeSysfore Technologies
Azure Blockchain as a Service (BaaS) is the new and experimental cloud technology service which Microsoft Azure is offering for its Platform as a Service (PaaS) customers. It is trying to create a marketplace for the blockchain, the distributed ledger technology on which bitcoin is built. IBM is the other adopter of this new cloud service, through its Bluemix Cloud service.
Sysfore can give you all the facts about Bitcoin cloud technology. Before going into how Bitcoin cloud works, you need to understand what the Bitcoin technology is.
This document provides a tutorial on how to build your first blockchain in three steps:
1. It explains the key components of blockchain including cryptography, peer-to-peer networks, and programming.
2. It demonstrates how to set up and run a private blockchain using the Multichain platform in 10 minutes.
3. It briefly introduces Hyperledger as an alternative open source blockchain platform supported by major companies.
Blockchain is a growing list of records called blocks that are linked using cryptography. Each block contains a cryptographic hash of the previous block, a timestamp, and transaction data. This design makes blockchains resistant to modification, as altering any block would require recalculating hashes for the entire chain. The blockchain is managed by a peer-to-peer network collectively adhering to a protocol for validating new blocks. By design, blockchains are inherently resistant to modification of the data.
Blockchain technology provides several benefits for finance applications:
1. It enables more efficient processes, reduced costs, and new services in banking through open and secure networks.
2. It allows digital securities to be issued faster and at lower costs with more customization.
3. Applications include reducing fraud, improving security and trust through transparency and smart contracts, and enabling new tools for activities like clearing and settlement, collateral management, and insurance claims processing.
Blockchains and Smart Contracts: Architecture Design and Model-Driven Develop...Ingo Weber
The document discusses research conducted by Data61's Architecture and Analytics Platforms (AAP) team on blockchains and smart contracts. The research includes developing a taxonomy and design process for architecting applications on blockchain, comparing the cost of using blockchain versus cloud services for business process execution, using architectural modeling to predict latency for blockchain-based systems, and developing a model-driven approach to define and execute smart contracts for monitoring and executing collaborative business processes across untrusted organizations.
This document discusses distributed ledger technology and its potential applications. It begins with an overview of how record keeping has evolved from stone tablets to today's digital systems. It then explains that ledgers are now shifting to a global network of cryptographically secure and decentralized computers using distributed ledger technology. Examples of distributed ledger technologies include blockchain, hashgraph, and directed acyclic graphs. The document outlines several potential real-world applications of distributed ledger technology such as securing copyrighted content, insurance, and digital voting.
Distributed Systems for Blockchain using CloudHridyesh Bisht
1. The document discusses implementing blockchain using cloud computing. Blockchain provides a distributed ledger and enables secure transfer of assets without intermediaries. It consists of blocks, miners, and nodes.
2. Several research papers are reviewed that propose using blockchain for data provenance in cloud storage. Blockchain can provide tamper-proof records and transparency of data accountability. It also enhances privacy and availability of provenance data.
3. Implementing blockchain using cloud computing provides benefits like better decentralization, efficient ownership tracking, increased data security, faster disaster recovery, and geo-independence. Security challenges like 51% attacks are also discussed.
Distributed systems and blockchain technologyAlket Cecaj
Blockchain is a distributed ledger system where nodes work together to validate transactions in a coordinated fashion without a central authority. It allows for decentralized consensus through mechanisms like proof-of-work. The main challenges in distributed systems are coordination between nodes and achieving fault tolerance. The CAP theorem states that a distributed system cannot achieve consistency, availability, and partition tolerance simultaneously. Blockchain sacrifices consistency for availability and partition tolerance. It uses elements like addresses, transactions, blocks, and consensus mechanisms like proof-of-work to securely and immutably record transactions on the distributed ledger.
Is Azure Blockchain Cloud the Future of Cloud Computing | SysforeSysfore Technologies
Azure Blockchain as a Service (BaaS) is the new and experimental cloud technology service which Microsoft Azure is offering for its Platform as a Service (PaaS) customers. It is trying to create a marketplace for the blockchain, the distributed ledger technology on which bitcoin is built. IBM is the other adopter of this new cloud service, through its Bluemix Cloud service.
Sysfore can give you all the facts about Bitcoin cloud technology. Before going into how Bitcoin cloud works, you need to understand what the Bitcoin technology is.
This document provides a tutorial on how to build your first blockchain in three steps:
1. It explains the key components of blockchain including cryptography, peer-to-peer networks, and programming.
2. It demonstrates how to set up and run a private blockchain using the Multichain platform in 10 minutes.
3. It briefly introduces Hyperledger as an alternative open source blockchain platform supported by major companies.
Blockchain is a growing list of records called blocks that are linked using cryptography. Each block contains a cryptographic hash of the previous block, a timestamp, and transaction data. This design makes blockchains resistant to modification, as altering any block would require recalculating hashes for the entire chain. The blockchain is managed by a peer-to-peer network collectively adhering to a protocol for validating new blocks. By design, blockchains are inherently resistant to modification of the data.
Blockchain technology provides several benefits for finance applications:
1. It enables more efficient processes, reduced costs, and new services in banking through open and secure networks.
2. It allows digital securities to be issued faster and at lower costs with more customization.
3. Applications include reducing fraud, improving security and trust through transparency and smart contracts, and enabling new tools for activities like clearing and settlement, collateral management, and insurance claims processing.
Blockchains and Smart Contracts: Architecture Design and Model-Driven Develop...Ingo Weber
The document discusses research conducted by Data61's Architecture and Analytics Platforms (AAP) team on blockchains and smart contracts. The research includes developing a taxonomy and design process for architecting applications on blockchain, comparing the cost of using blockchain versus cloud services for business process execution, using architectural modeling to predict latency for blockchain-based systems, and developing a model-driven approach to define and execute smart contracts for monitoring and executing collaborative business processes across untrusted organizations.
Blockchain security relies on cryptography, decentralization, and consensus. Cryptography uses mathematical codes to securely store and transmit data values. Decentralization distributes control across a network rather than centralized control. Consensus requires all parties on the network to anonymously approve transactions. Key characteristics of blockchain security include distribution of processing across all peers, immutable and persistent records, use of digital signatures, and difficulty for hackers to edit blocks.
Blockchain Scalability - Architectures and AlgorithmsGokul Alex
My presentation on 'Blockchain Scalability - Architectures and Algorithms' for the TechAthena Digital Community Webinar.
Blockchain Scalability is one of the most significant concern for Minimum Viable Blockchain Implementation. It is one of the key aspects determining the relevance and feasibility of Blockchain Technology for a particular use case.This session will cover the fundamental aspects of distributed computing that determine the contours of scalability.
Subsequently, the session will outline the parameters and metrics related to Blockchain Scalability in detail. In this context, the session will deep dive into architectural and algorithmic techniques that enables a scalable Blockchain.Architectural techniques such as vertical scaling and horizontal scaling will be explained in detail. Design techniques such as State Channels, Sharding, SideChains, Off chain computations, Block Size and Time Optimization etc. will be explained.
In summary, this session will conclude with the implications and trade-off between Blockchain Scalability, Security, Simplicity and Interoperability. Looking forward to your views and thoughts !
Blockchain: The New Technology of TrustMacha Pujitha
Blockchain is a digital ledger of records arranged in blocks that are linked through cryptography. Each block contains a cryptographic hash of the previous block, transaction data, and a timestamp. This forms a chain where transactions are permanently recorded and can be verified. Blockchain has various applications including cryptocurrencies, e-government services, healthcare, and voting. It allows for decentralized trust and verification of digital information and transactions without intermediaries.
Today, blockchain technology doesn't need to be implemented. A word that once was foreign has now earned accolades from individuals across the globe. This technology is being talked about by every business and investor. Blockchain started its journey as an underlying Bitcoin exchange technology, and it has gained so much popularity over the years. Everyone speaks about Blockchain, from students to working professionals; but what makes Blockchain so attractive is that you need to know the concepts of Blockchain technology for this.
Hyperledger Sawtooth Lake Intel's OSS Contribution to Enterprise BlockchainAltoros
Sawtooth Lake is an open source distributed ledger project within Hyperledger. It uses a blockchain architecture where each node holds a copy of the shared ledger and transactions are grouped into blocks and chained together cryptographically. Sawtooth Lake allows for modular transaction families that encapsulate business logic and smart contracts. The latest release focuses on improvements to transaction processing, including parallel execution and multi-language support.
Yao Yao, Jack Rasmus-Vorrath, Ivelin Angelov
https://github.com/yaowser/basic_blockchain
https://www.slideshare.net/YaoYao44/blockchain-security-and-demonstration/
Distributed ledger technology over a network of computers, which provides an alternative to the centralized system
Distributed Database
Peer-to-Peer Transmission
Transparency with Pseudonymity
Records are immutable
Computational Logic
https://www.youtube.com/watch?v=5ArZxRdhyPc
This document discusses key concepts related to decentralized networks and blockchain technology. It begins by describing the basic components of a blockchain network, including nodes that exchange information and maintain an identical and immutable record of historical data. It then explores the differences between decentralized, fractal, distributed, and diversified network types. The document also notes some potential problems with decentralization, such as centralized elements like mining pools, hardware manufacturers, and exchanges. Finally, it provides an overview of distributed ledgers, peer-to-peer networks, and defines blocks and blockchains as sequences of immutable records of transactions.
Blockchain Technology and Its Application in LibrariesNabi Hasan
Background
Blockchain: Conceptual Understanding
What is Blockchain Technology?
The Three Pillars of Blockchain Technology
Why is Blockchain Popular?
What is Distributed Ledger?
Blockchain for Enterprise Application Developer
Possible Areas of Implimention of Blockchain Technology in Libraries
Blockchain Essentials for Enterprise ArchitectsGokul Alex
My session on Blockchain : Protocols, Platforms, Principles and Paradigms presented in the Benagluru Chamber of Industries and Commerce #BCIC Talk Series held at VMware Software India in collaboration with WomenWhoCode. This presentation is a compilation of essential concepts about Bitcoin, Ethereum, IPFS, Hyperledger, R3 Corda.
The Cloud is dead ?! Blockchain in the new cloudYuval Birenboum
The document discusses the potential for a "decentralized cloud" using blockchain technology for decentralized applications (Dapps), computing, databases, and storage. It defines blockchain and how it allows for a distributed ledger and peer-to-peer transactions without an central authority. The benefits of decentralization are reduced need for trust and privacy risks while unleashing resources at the network edges. Decentralized storage and databases on the blockchain could provide an alternative to current cloud-based services.
This document outlines a seminar on blockchain technology. It begins with an introduction to blockchain as a growing list of linked data blocks that cannot be altered. It then discusses the history of bitcoin and how it relates to blockchain as an application of the technology. The working of the bitcoin ecosystem is explained as a public, decentralized network that builds consensus among participants through increasing security and participation. Key features of blockchain like immutability, transparency, and decentralization without intermediaries are also highlighted. Challenges like energy usage and scalability are noted.
Murughan Palaniachari presents information on blockchain concepts. He discusses how blockchain enables a decentralized future (Web 3.0) with distributed and individual ownership of data. Blockchain uses distributed ledgers and cryptography to securely record transactions in an immutable, transparent and verifiable way without centralized control. Key concepts covered include how blockchain works, the structure of blocks and blockchains, consensus mechanisms, smart contracts, and examples of blockchain use cases.
This document provides an overview of blockchain technology, how it works, and its applications. It defines blockchain as a decentralized digital ledger consisting of blocks that record transactions across networks so past transactions cannot be altered. The document outlines the history of blockchain, how it provides security through hashing and proof-of-work algorithms, and how cryptocurrencies use blockchain to be immune from counterfeiting without central authorities. It then provides an example of how a basic bitcoin transaction occurs between parties on the blockchain network.
This document provides an overview of consensus mechanisms for blockchain networks. It begins by defining key terms like blockchain, distributed ledger, and consensus mechanism. It then discusses the Byzantine General's Problem and how consensus solves it. The document outlines basic parameters of consensus mechanisms and provides examples of widely used mechanisms like Proof-of-Work. It also summarizes several alternative consensus algorithms like Proof-of-Stake, Delegated Proof-of-Stake, Raft, and Byzantine Fault Tolerant variants. Throughout, it emphasizes the need for different consensus approaches based on use cases and technical requirements.
Blockchain is a system of recording information in a way that makes it difficult or impossible to change, hack, or cheat the system. A blockchain is essentially a digital ledger of transactions that is duplicated and distributed across the entire network of computer systems on the blockchain.
IRJET- Security Threats on Blockchain and its CountermeasuresIRJET Journal
This document summarizes a research paper that examines security threats to blockchain systems. It begins with an abstract that introduces the topic and outlines the paper's goals. The introduction provides background on blockchain technology and discusses how, while it provides benefits like security and decentralization, it also faces challenges around scalability, security, and privacy that have not been fully addressed. The paper then reviews existing literature on blockchain security issues and vulnerabilities. It conducts a systematic survey of security threats to blockchain systems and how existing vulnerabilities can enable these threats to disrupt normal blockchain functionality. Key security threats discussed include double-spending attacks. The document outlines the paper's analysis of blockchain characteristics, types, consensus algorithms, and technical challenges like scalability and throughput that
Blockchain is a distributed ledger that maintains a permanent record of transactions in a peer-to-peer network. Each computer in the network maintains a copy of the ledger to prevent a single point of failure. Blockchain consists of blocks of validated transactions that are linked using cryptography. It allows transactions to be recorded and validated without the need for a central authority. Blockchain has applications in finance, healthcare, and other industries by automating processes and removing trust issues through transparency. However, blockchain also faces challenges from its current limitations in scalability and regulation.
* What makes a blockchain special in terms of inherent security?
* When could a blockchain become insecure / unstable? Examples and implications
* Novel use cases exploiting a blockchain's inherent security
* When could a blockchain pose a cyber threat?
Author : Haydn Jones, Managing Director, Blockchain Hub
Learn Basics & advances of Hyperledger - 101-BlockchainsJackSmith435850
Hyperledger is an open-source blockchain project that supports the development of blockchain applications. It was initiated in 2015 by the Linux Foundation and does not define a specific blockchain standard, instead focusing on collaborative development. Hyperledger Fabric is the most notable project in Hyperledger and uses smart contracts and permissioned ledgers. It differs from other blockchains by requiring members to enroll through a Membership Service Provider.
Blockchain security relies on cryptography, decentralization, and consensus. Cryptography uses mathematical codes to securely store and transmit data values. Decentralization distributes control across a network rather than centralized control. Consensus requires all parties on the network to anonymously approve transactions. Key characteristics of blockchain security include distribution of processing across all peers, immutable and persistent records, use of digital signatures, and difficulty for hackers to edit blocks.
Blockchain Scalability - Architectures and AlgorithmsGokul Alex
My presentation on 'Blockchain Scalability - Architectures and Algorithms' for the TechAthena Digital Community Webinar.
Blockchain Scalability is one of the most significant concern for Minimum Viable Blockchain Implementation. It is one of the key aspects determining the relevance and feasibility of Blockchain Technology for a particular use case.This session will cover the fundamental aspects of distributed computing that determine the contours of scalability.
Subsequently, the session will outline the parameters and metrics related to Blockchain Scalability in detail. In this context, the session will deep dive into architectural and algorithmic techniques that enables a scalable Blockchain.Architectural techniques such as vertical scaling and horizontal scaling will be explained in detail. Design techniques such as State Channels, Sharding, SideChains, Off chain computations, Block Size and Time Optimization etc. will be explained.
In summary, this session will conclude with the implications and trade-off between Blockchain Scalability, Security, Simplicity and Interoperability. Looking forward to your views and thoughts !
Blockchain: The New Technology of TrustMacha Pujitha
Blockchain is a digital ledger of records arranged in blocks that are linked through cryptography. Each block contains a cryptographic hash of the previous block, transaction data, and a timestamp. This forms a chain where transactions are permanently recorded and can be verified. Blockchain has various applications including cryptocurrencies, e-government services, healthcare, and voting. It allows for decentralized trust and verification of digital information and transactions without intermediaries.
Today, blockchain technology doesn't need to be implemented. A word that once was foreign has now earned accolades from individuals across the globe. This technology is being talked about by every business and investor. Blockchain started its journey as an underlying Bitcoin exchange technology, and it has gained so much popularity over the years. Everyone speaks about Blockchain, from students to working professionals; but what makes Blockchain so attractive is that you need to know the concepts of Blockchain technology for this.
Hyperledger Sawtooth Lake Intel's OSS Contribution to Enterprise BlockchainAltoros
Sawtooth Lake is an open source distributed ledger project within Hyperledger. It uses a blockchain architecture where each node holds a copy of the shared ledger and transactions are grouped into blocks and chained together cryptographically. Sawtooth Lake allows for modular transaction families that encapsulate business logic and smart contracts. The latest release focuses on improvements to transaction processing, including parallel execution and multi-language support.
Yao Yao, Jack Rasmus-Vorrath, Ivelin Angelov
https://github.com/yaowser/basic_blockchain
https://www.slideshare.net/YaoYao44/blockchain-security-and-demonstration/
Distributed ledger technology over a network of computers, which provides an alternative to the centralized system
Distributed Database
Peer-to-Peer Transmission
Transparency with Pseudonymity
Records are immutable
Computational Logic
https://www.youtube.com/watch?v=5ArZxRdhyPc
This document discusses key concepts related to decentralized networks and blockchain technology. It begins by describing the basic components of a blockchain network, including nodes that exchange information and maintain an identical and immutable record of historical data. It then explores the differences between decentralized, fractal, distributed, and diversified network types. The document also notes some potential problems with decentralization, such as centralized elements like mining pools, hardware manufacturers, and exchanges. Finally, it provides an overview of distributed ledgers, peer-to-peer networks, and defines blocks and blockchains as sequences of immutable records of transactions.
Blockchain Technology and Its Application in LibrariesNabi Hasan
Background
Blockchain: Conceptual Understanding
What is Blockchain Technology?
The Three Pillars of Blockchain Technology
Why is Blockchain Popular?
What is Distributed Ledger?
Blockchain for Enterprise Application Developer
Possible Areas of Implimention of Blockchain Technology in Libraries
Blockchain Essentials for Enterprise ArchitectsGokul Alex
My session on Blockchain : Protocols, Platforms, Principles and Paradigms presented in the Benagluru Chamber of Industries and Commerce #BCIC Talk Series held at VMware Software India in collaboration with WomenWhoCode. This presentation is a compilation of essential concepts about Bitcoin, Ethereum, IPFS, Hyperledger, R3 Corda.
The Cloud is dead ?! Blockchain in the new cloudYuval Birenboum
The document discusses the potential for a "decentralized cloud" using blockchain technology for decentralized applications (Dapps), computing, databases, and storage. It defines blockchain and how it allows for a distributed ledger and peer-to-peer transactions without an central authority. The benefits of decentralization are reduced need for trust and privacy risks while unleashing resources at the network edges. Decentralized storage and databases on the blockchain could provide an alternative to current cloud-based services.
This document outlines a seminar on blockchain technology. It begins with an introduction to blockchain as a growing list of linked data blocks that cannot be altered. It then discusses the history of bitcoin and how it relates to blockchain as an application of the technology. The working of the bitcoin ecosystem is explained as a public, decentralized network that builds consensus among participants through increasing security and participation. Key features of blockchain like immutability, transparency, and decentralization without intermediaries are also highlighted. Challenges like energy usage and scalability are noted.
Murughan Palaniachari presents information on blockchain concepts. He discusses how blockchain enables a decentralized future (Web 3.0) with distributed and individual ownership of data. Blockchain uses distributed ledgers and cryptography to securely record transactions in an immutable, transparent and verifiable way without centralized control. Key concepts covered include how blockchain works, the structure of blocks and blockchains, consensus mechanisms, smart contracts, and examples of blockchain use cases.
This document provides an overview of blockchain technology, how it works, and its applications. It defines blockchain as a decentralized digital ledger consisting of blocks that record transactions across networks so past transactions cannot be altered. The document outlines the history of blockchain, how it provides security through hashing and proof-of-work algorithms, and how cryptocurrencies use blockchain to be immune from counterfeiting without central authorities. It then provides an example of how a basic bitcoin transaction occurs between parties on the blockchain network.
This document provides an overview of consensus mechanisms for blockchain networks. It begins by defining key terms like blockchain, distributed ledger, and consensus mechanism. It then discusses the Byzantine General's Problem and how consensus solves it. The document outlines basic parameters of consensus mechanisms and provides examples of widely used mechanisms like Proof-of-Work. It also summarizes several alternative consensus algorithms like Proof-of-Stake, Delegated Proof-of-Stake, Raft, and Byzantine Fault Tolerant variants. Throughout, it emphasizes the need for different consensus approaches based on use cases and technical requirements.
Blockchain is a system of recording information in a way that makes it difficult or impossible to change, hack, or cheat the system. A blockchain is essentially a digital ledger of transactions that is duplicated and distributed across the entire network of computer systems on the blockchain.
IRJET- Security Threats on Blockchain and its CountermeasuresIRJET Journal
This document summarizes a research paper that examines security threats to blockchain systems. It begins with an abstract that introduces the topic and outlines the paper's goals. The introduction provides background on blockchain technology and discusses how, while it provides benefits like security and decentralization, it also faces challenges around scalability, security, and privacy that have not been fully addressed. The paper then reviews existing literature on blockchain security issues and vulnerabilities. It conducts a systematic survey of security threats to blockchain systems and how existing vulnerabilities can enable these threats to disrupt normal blockchain functionality. Key security threats discussed include double-spending attacks. The document outlines the paper's analysis of blockchain characteristics, types, consensus algorithms, and technical challenges like scalability and throughput that
Blockchain is a distributed ledger that maintains a permanent record of transactions in a peer-to-peer network. Each computer in the network maintains a copy of the ledger to prevent a single point of failure. Blockchain consists of blocks of validated transactions that are linked using cryptography. It allows transactions to be recorded and validated without the need for a central authority. Blockchain has applications in finance, healthcare, and other industries by automating processes and removing trust issues through transparency. However, blockchain also faces challenges from its current limitations in scalability and regulation.
* What makes a blockchain special in terms of inherent security?
* When could a blockchain become insecure / unstable? Examples and implications
* Novel use cases exploiting a blockchain's inherent security
* When could a blockchain pose a cyber threat?
Author : Haydn Jones, Managing Director, Blockchain Hub
Learn Basics & advances of Hyperledger - 101-BlockchainsJackSmith435850
Hyperledger is an open-source blockchain project that supports the development of blockchain applications. It was initiated in 2015 by the Linux Foundation and does not define a specific blockchain standard, instead focusing on collaborative development. Hyperledger Fabric is the most notable project in Hyperledger and uses smart contracts and permissioned ledgers. It differs from other blockchains by requiring members to enroll through a Membership Service Provider.
Blockchain technology offers a plethora of possibilities for creativity. It has the potential to transform industries by radically altering the way they are conducted.
So, how can developers get started writing code for blockchain networks? We suggest beginning with a thorough understanding of the Hyperledger Fabric project.
IRJET- Study of Blockchain and its ConceptsIRJET Journal
This document discusses using blockchain technology to implement a log storage system. It begins with an introduction to blockchain and its key properties. It then discusses several concepts related to implementing a log storage system using blockchain, including using a logchain as a service and the Medusa system which utilizes Hyperledger. It also covers different blockchain platforms like Hyperledger Fabric and Ethereum. Consensus algorithms including proof-based and voting-based methods are described. Finally, potential applications of a blockchain-based log storage system are outlined such as for libraries, organizations, healthcare, and cloud storage.
This document provides an overview and guidelines for implementing blockchain technology. It discusses key considerations for selecting a blockchain platform, including assessing technical requirements and understanding how the selected platform meets business needs. It then describes the major components of blockchain deployments and presents a reference architecture. Implementation is broken into three tracks: detailing business workflows, setting up infrastructure, and developing business applications and services. Factors for integrating blockchain with existing internal and external systems are also covered.
Custom Blockchain App Development_ A Comprehensive Guide for 2024.pdfJPLoft Solutions
Blockchain technology is not an euphemism that has generated much interest in the field. It's a digital ledger that records secure transactions and the ability to be transparent. It makes records and transactions immune to cyber-attacks.
How to Build Your Blockchain Project with ChainstackChainstack
This document introduces Chainstack, a blockchain as a service platform that allows users to rapidly build, deploy, and manage decentralized networks. It discusses key considerations for choosing a blockchain platform such as supported protocols, deployment options, costs, and ease of use. Chainstack offers flexibility in protocols (Fabric, MultiChain, Quorum, Ethereum, Corda), deployment locations (public cloud, on-premises, hybrid), and aims to simplify complex processes like node deployment and synchronization through its user interface and synchronization technology.
Hyperledger is an open source blockchain project started in 2015 by the Linux Foundation. It includes various blockchain frameworks and tools to support collaborative development of blockchain distributed ledgers. Hyperledger Fabric is a modular and permissioned blockchain framework that provides applications and solutions for enterprises. As an open source project, anyone can contribute to Hyperledger Fabric, which currently has 35 organizations working together to develop it. Key components of Hyperledger Fabric include membership services, certificate authorities, nodes, peers, and chaincode to handle business logic on the network.
Benchmark and comparison between hyperledger and MySQLTELKOMNIKA JOURNAL
In this paper, we report the benchmarking results of Hyperledger, a Distributed Ledger, which is the derivation Blockchain Technology. Method to evaluate Hyperledger in a limited infrastructure is developed. Themeasured infrastructure consists of 8 nodes with a load of up to 20000 transactions/second. Hyperledger consistently runs all evaluation, namely, for 20,000 transactions, the run time 74.30s, latency 73.40ms latency, and 257 tps. The benchmarking of Hyperledger shows better than a database system in a high workload scenario. We found that the maximum size data volume in one transaction on the Hyperledger network is around ten (10) times of MySQL. Also, the time spent on processing a single transaction in the blockchain network is 80-200 times faster than MySQL. This initial analysis can provide an overview for practitioners in making decisions about the adoption of blockchain technology in their IT systems.
Chaincode refers to programs that are run on Hyperledger blockchain networks to manage ledger state and transactions. It handles business logic that is agreed to by network members. Chaincode is isolated from endorsing peers for security and initializes and manages state through submitted transactions.
The document describes Kyber, an on-chain liquidity protocol that allows for instant token swaps in a decentralized manner across blockchains. It discusses the key actors in the protocol including takers, reserves, and maintainers. It outlines the core functions including getting conversion rates from reserves and executing trades. It also describes how basic token trades and token-to-token trades are executed. The document discusses connecting liquidity across blockchains through practical relay approaches and envisioning a unified liquidity network.
- Hyperledger Fabric now supports Ethereum smart contracts through integration with the Ethereum Virtual Machine (EVM). This will allow Ethereum developers to work with Hyperledger Fabric and migrate smart contracts and decentralized apps between the platforms.
- Hyperledger is an open source blockchain project hosted by the Linux Foundation. It includes various blockchain frameworks and tools including Fabric, Sawtooth, and Composer. Fabric is the most widely adopted Hyperledger blockchain framework.
- Hyperledger blockchain applications interact with peers to access and update the shared ledger. The ledger contains a growing list of immutable transaction records organized into blocks.
Blockchain solution architecture deliverableSarmad Ibrahim
This document discusses key architectural decisions for designing blockchain solution networks using Hyperledger Fabric. It outlines considerations for direct vs indirect network participation, secure key management, certificate authority design, data storage choices regarding on-chain and off-chain data, endorsement policy design, integration with enterprise systems, and deployment models. The document provides guidance for solution architects in assessing these decisions and designing blockchain business networks.
IRJET- Credible Data through Distributed Ledger TechnologyIRJET Journal
This document proposes a decentralized data marketplace platform based on Ethereum blockchain. It discusses some limitations of existing centralized data marketplaces, where users must trust the centralized authority. The proposed system aims to make data buying and selling cheaper, faster, easier and more trustworthy. It describes key components like a smart contract for handling transactions, and a web application for users to authenticate, buy and sell data. Implementation details are provided for a prototype built using Django, Python, Solidity and a private Ethereum blockchain network. Future work ideas include adding encryption of stored data locations and migrating file storage to the cloud.
The Fabric platform is intended as a foundation for developing blockchain applications, products or solutions. The fabric is a Private and Permissioned system which delivers a high degree of confidentiality, resiliency, flexibility, and scalability. It adopted a modular architecture and supports pluggable implementations of different components like consensus, membership services etc. Like other blockchain technologies, Fabric has a ledger, smart contracts, and it is a system by which participants manage their transactions. The smart contract in the fabric is known as chaincode and it is in the chaincode the business logic is embedded. The following features impart high degree of security and privacy for the fabric framewor
Over the last few years, enterprises have come to realize how blockchain, the technology that powers public networks such as Bitcoin and Ethereum, can be used to streamline their own business processes. However, they have also found that most existing blockchain protocols fail to meet several key enterprise requirements—including acceptable transaction throughput and latency, confidentiality, effective governance, and computational efficiency (i.e., the energy cost for mining/proof of work). Efforts to adapt existing public blockchain protocols or to create new protocols to meet these needs have generally traded one required enterprise attribute for another—such as improved confidentiality at the cost of greater complexity or lower performance.
The Coco Framework is an open-source system that enables high-scale, confidential blockchain networks that meet all key enterprise requirements—providing a means to accelerate production enterprise adoption of blockchain technology. Coco achieves this by re-evaluating existing assumptions for public blockchain protocols in the context of a confidential consortium, where nodes and actors (including voting members and other non-voting participants) are explicitly declared and controlled. Based on this new set of requirements, Coco brings together the power of existing blockchain protocols, trusted execution environments, distributed systems, and cryptography to enable enterprise-ready blockchain networks that deliver: • Throughput and latency approaching database speeds. • Richer, more flexible, business-specific confidentiality models. • Network policy management through distributed governance. • Support for non-deterministic transactions. • Reduced energy consumption.
The document discusses key aspects of blockchain technology including:
1) Blocks in a blockchain contain a hash of the previous block, a timestamp, and transaction data represented as a Merkle tree.
2) Centralized systems have issues like single points of failure, lack of trust, and scalability limitations. Blockchain addresses these through decentralization and immutability.
3) Blockchain maintains immutability through cryptographic hashing of blocks, decentralization across nodes, and consensus algorithms.
IRJET- Photogroup: Decentralized Web Application using Ethereum BlockchainIRJET Journal
This document describes a proposed decentralized photo sharing application called Photogroup that is built using blockchain technology. Photogroup allows users to view, like, comment on and share photos in a peer-to-peer network without a central server. It uses Ethereum for the blockchain platform and smart contracts to manage transactions and the addition of new blocks. When a user shares a photo, the transaction is added to the blockchain through smart contracts to ensure the data is distributed and immutable across all nodes. The system aims to provide more security than centralized social networks by avoiding single points of failure and making the data difficult to hack or tamper with.
Similar to Hyperledger arch wg_paper_1_consensus (20)
Attack 1: OilRig infected software used by the visually impaired with malware to spy on targets in the Middle East, Europe, and US. This damaged the software company's sales and reputation.
Attack 2: OilRig created fake Oxford University websites to distribute their malware. People who registered or downloaded files from the sites unknowingly infected their devices. This hurt Oxford's credibility.
Attack 3: OilRig sent a phishing email with malware to the Saudi financial group Samba through the compromised network of Saudi contractor Al-Elm. Opening the email attachment installed OilRig's surveillance software.
Cyber Security for Everyone Course - Final Project PresentationCMR WORLD TECH
OilRig is an advanced persistent threat (APT) group based in Iran that conducts cyber espionage operations. It has carried out several attacks targeting the oil and gas industry as well as other sectors. The attacks involved compromising legitimate software and websites to distribute malware. The motivations for OilRig's operations are believed to be related to sanctions against Iran and its pursuit of stolen intellectual property and sensitive information from other countries. Policymakers need to consider responses that address both the private impacts on businesses, as well as the broader public and geopolitical concerns given OilRig's targeting of both private and public sector organizations internationally.
1) O documento fornece instruções passo-a-passo para criar uma cota no CPQ, incluindo como criar uma conta, contato e oportunidade, adicionar produtos à cota e atualizar quantidades.
2) Também explica como criar pacotes de produtos contendo itens relacionados e definir características, opções e restrições para os pacotes.
3) Fornece detalhes sobre como criar novos produtos e preços padrão e vincular produtos em pacotes.
This document provides instructions for installing and configuring Salesforce CPQ. It outlines pre-installation steps like enabling email deliverability, Chatter, Orders and CRM content. It then details how to install the CPQ package, authorize the calculation service, execute post-install scripts and change page layout assignments. The goal is to leverage the out-of-box CPQ fields and configurations by properly setting up profiles and permissions.
The Salesforce Automation Landscape
The Salesforce Automation Landscape
Declarative Tolls points and clicks admins
Coding tools Salesforce Gods
For Developers it is very important understand
the tools available and know when they should be applied.
Declarative tool set – Workflowrules, same object updates
Email notifications, limited applications.
Process Builder – Related object updates
Create a records, no unrelated objects
Bulk issues everywhere
Visual flow unrelated object updates variables and loops.
Same learning curve as code, but without the benefits.
The document discusses process automation by repeating the phrase "Process Automation" multiple times without providing any additional context or details about what process automation entails. The high-level topic appears to be process automation, but no meaningful information is given beyond stating the topic.
A high-level overview of the key features and benefits of Workflow and Approval process automation in Enterprise Edition. Your sales force operates more efficiently with standardized internal procedures and automated business processes. Many of the tasks you normally assign, the emails you regularly send, and other record updates are part of an organization's standard processes. Instead of doing this work manually, you can configure workflow and approvals to do it automatically.
Begin by designing workflow rules and approval processes, and associating them with actions such as email alerts, tasks, field updates, or outbound messages.
This document lists a series of courses completed by Cesar Murilo Ribeiro on topics including getting started with SharePoint add-ins, mobile app development with Office 365 APIs, advanced Windows 10 development with Office 365 APIs, and advanced web development using Angular with Office 365 APIs. It also includes courses on advanced SharePoint add-in development, advanced Office add-in development with Excel, Word, and PowerPoint, and advanced Office add-in development with Outlook.
Migrating
your
existing applications and IT assets to the Amazon Web Services
(AWS)
Cloud
presents
an opportunity to transform the way your organization
does
business.
It can help
you
lower costs, become more agile, develop new
skills
more quickly
, and deliver reliable, globally available services to your
customers.
Our goal is to help you to
implement
your cloud strategy
successfully.
Delivery readness for pick season and higth volumeCMR WORLD TECH
This document provides guidance on preparing for and managing email deliverability during peak seasons and high-volume sending periods. It covers best practices around data hygiene and list acquisition, content and branding, volume and frequency, segmentation and targeting, monitoring and reporting, and includes a deliverability readiness checklist. The key recommendations are to begin planning well in advance, focus on clean subscriber data and permission, avoid sudden volume spikes, scale up IPs and volume gradually, and leverage segmentation and monitoring tools to optimize performance.
Why digital-will-become-the-primary-channel-for-b2 b-engagementCMR WORLD TECH
The document discusses how digital commerce is becoming the primary channel for B2B engagement. Some key points:
- B2B customers and decision-makers now prefer digital channels and self-service options for repeat purchases. This positions digital as the primary engagement channel.
- B2B organizations that invested early in digital see benefits like increased customer retention, acquisition, and expected business growth attributed to digital commerce programs.
- Features like tailored products, order automation, and self-service are valuable for both B2B businesses and customers in the digital channel.
This document lists a series of courses completed by Cesar Murilo Ribeiro on topics including getting started with SharePoint add-ins, mobile app development with Office 365 APIs, advanced Windows 10 development with Office 365 APIs, and advanced web development using Angular with Office 365 APIs. It also includes courses on advanced SharePoint add-in development, advanced Office add-in development with Excel, Word, and PowerPoint, and advanced Office add-in development with Outlook.
UK Export Finance (UKEF) provides financing support to help overseas buyers purchase goods and services from UK companies, including direct loans, guarantees on bank loans, and supplier credit facilities, with financing terms of up to 10 years. UKEF has supported over $20 billion in export contracts across over 50 countries in sectors like healthcare, engineering, and infrastructure. The document outlines the various financing support options available from UKEF and provides examples of projects it has supported.
1) The document outlines the Hyperledger design philosophy of modularity and interoperability for permissioned blockchain networks. It describes the core components defined by the Architecture Working Group including the consensus layer.
2) The consensus layer is responsible for agreeing on the order and validity of transactions to include in a block. Various consensus algorithms are compared including lottery-based and voting-based methods.
3) The document explores how consensus interacts with other layers like the smart contract layer to validate transactions and reach agreement on the state. Transactions are ordered into blocks by a service before being validated according to endorsement and consensus policies.
The document discusses how Cloud Services can help different departments within a company achieve their goals by using Salesforce. It focuses on how Cloud Services supports IT departments. Some key ways it helps IT include: boosting productivity and lowering costs through Success Plans, training resources, and 24/7 support; achieving operational excellence through comprehensive support and monitoring from experts; and clearing a path for innovation and transformation by collaborating with experts on strategies and best practices.
This document provides resources for learning Apex and Visualforce development on the Salesforce platform. It covers objectives related to design and functionality, performance and scalability, and maintainability and reuse. For each objective, core and recommended learning materials are identified at beginner, intermediate, and advanced skill levels. The resources include documentation, guides, webinars and videos to help developers of all experience levels learn Apex and Visualforce.
General Motors' OnStar division leveraged the Salesforce platform to build an app called AtYourService that allows drivers to access location-based deals and services from nearby retailers and merchants directly from their vehicle. By analyzing usage data, OnStar recognized an opportunity to offer additional value to customers beyond emergency assistance. The Salesforce platform provided the scalability needed to build a personalized, connected experience that engages customers every day and keeps them returning to OnStar.
Berkeley program on_data_science___analytics_1CMR WORLD TECH
The document provides information about the Berkeley Program on Data Science & Analytics, including an overview of the program, details on modules and curriculum, faculty directors, the application process, and benefits of attending. The 6-month program is delivered through a combination of in-person sessions in Singapore, Berkeley, and online modules. It aims to help executives build and lead effective data science teams through applying data-driven decision making approaches.
Rep consumer experience_in_the_retail_renaissance_en_28_mar18_final_dm_CMR WORLD TECH
This document discusses how leading brands are building consumer experiences in the current retail renaissance. It finds that while many brands say they aim to put customers at the center, their efforts often fall short due to disconnected experiences. The report surveys over 500 retail and consumer goods leaders to understand how they harness consumer data and technology to engage customers. It reveals that brands overly focus on products over experiences and need to better understand customer needs.
This document provides guidelines for writing content for Salesforce using the appropriate voice and tone. It discusses how voice reflects personality while tone reflects mood or feeling. The guidelines recommend writing in an honest, clear, fun, and inspiring voice. Tone should be adjusted based on the audience, such as being encouraging for admins but direct for developers. The document provides tips for writing concisely, conversationally, directly, and positively. It also discusses using humor judiciously and avoiding cultural references. Examples are given to illustrate how to apply different tones for various audiences and scenarios.
Do you want Software for your Business? Visit Deuglo
Deuglo has top Software Developers in India. They are experts in software development and help design and create custom Software solutions.
Deuglo follows seven steps methods for delivering their services to their customers. They called it the Software development life cycle process (SDLC).
Requirement — Collecting the Requirements is the first Phase in the SSLC process.
Feasibility Study — after completing the requirement process they move to the design phase.
Design — in this phase, they start designing the software.
Coding — when designing is completed, the developers start coding for the software.
Testing — in this phase when the coding of the software is done the testing team will start testing.
Installation — after completion of testing, the application opens to the live server and launches!
Maintenance — after completing the software development, customers start using the software.
Graspan: A Big Data System for Big Code AnalysisAftab Hussain
We built a disk-based parallel graph system, Graspan, that uses a novel edge-pair centric computation model to compute dynamic transitive closures on very large program graphs.
We implement context-sensitive pointer/alias and dataflow analyses on Graspan. An evaluation of these analyses on large codebases such as Linux shows that their Graspan implementations scale to millions of lines of code and are much simpler than their original implementations.
These analyses were used to augment the existing checkers; these augmented checkers found 132 new NULL pointer bugs and 1308 unnecessary NULL tests in Linux 4.4.0-rc5, PostgreSQL 8.3.9, and Apache httpd 2.2.18.
- Accepted in ASPLOS ‘17, Xi’an, China.
- Featured in the tutorial, Systemized Program Analyses: A Big Data Perspective on Static Analysis Scalability, ASPLOS ‘17.
- Invited for presentation at SoCal PLS ‘16.
- Invited for poster presentation at PLDI SRC ‘16.
E-commerce Application Development Company.pdfHornet Dynamics
Your business can reach new heights with our assistance as we design solutions that are specifically appropriate for your goals and vision. Our eCommerce application solutions can digitally coordinate all retail operations processes to meet the demands of the marketplace while maintaining business continuity.
Software Engineering, Software Consulting, Tech Lead, Spring Boot, Spring Cloud, Spring Core, Spring JDBC, Spring Transaction, Spring MVC, OpenShift Cloud Platform, Kafka, REST, SOAP, LLD & HLD.
UI5con 2024 - Boost Your Development Experience with UI5 Tooling ExtensionsPeter Muessig
The UI5 tooling is the development and build tooling of UI5. It is built in a modular and extensible way so that it can be easily extended by your needs. This session will showcase various tooling extensions which can boost your development experience by far so that you can really work offline, transpile your code in your project to use even newer versions of EcmaScript (than 2022 which is supported right now by the UI5 tooling), consume any npm package of your choice in your project, using different kind of proxies, and even stitching UI5 projects during development together to mimic your target environment.
DDS Security Version 1.2 was adopted in 2024. This revision strengthens support for long runnings systems adding new cryptographic algorithms, certificate revocation, and hardness against DoS attacks.
Transform Your Communication with Cloud-Based IVR SolutionsTheSMSPoint
Discover the power of Cloud-Based IVR Solutions to streamline communication processes. Embrace scalability and cost-efficiency while enhancing customer experiences with features like automated call routing and voice recognition. Accessible from anywhere, these solutions integrate seamlessly with existing systems, providing real-time analytics for continuous improvement. Revolutionize your communication strategy today with Cloud-Based IVR Solutions. Learn more at: https://thesmspoint.com/channel/cloud-telephony
Neo4j - Product Vision and Knowledge Graphs - GraphSummit ParisNeo4j
Dr. Jesús Barrasa, Head of Solutions Architecture for EMEA, Neo4j
Découvrez les dernières innovations de Neo4j, et notamment les dernières intégrations cloud et les améliorations produits qui font de Neo4j un choix essentiel pour les développeurs qui créent des applications avec des données interconnectées et de l’IA générative.
Introducing Crescat - Event Management Software for Venues, Festivals and Eve...Crescat
Crescat is industry-trusted event management software, built by event professionals for event professionals. Founded in 2017, we have three key products tailored for the live event industry.
Crescat Event for concert promoters and event agencies. Crescat Venue for music venues, conference centers, wedding venues, concert halls and more. And Crescat Festival for festivals, conferences and complex events.
With a wide range of popular features such as event scheduling, shift management, volunteer and crew coordination, artist booking and much more, Crescat is designed for customisation and ease-of-use.
Over 125,000 events have been planned in Crescat and with hundreds of customers of all shapes and sizes, from boutique event agencies through to international concert promoters, Crescat is rigged for success. What's more, we highly value feedback from our users and we are constantly improving our software with updates, new features and improvements.
If you plan events, run a venue or produce festivals and you're looking for ways to make your life easier, then we have a solution for you. Try our software for free or schedule a no-obligation demo with one of our product specialists today at crescat.io
Top Features to Include in Your Winzo Clone App for Business Growth (4).pptxrickgrimesss22
Discover the essential features to incorporate in your Winzo clone app to boost business growth, enhance user engagement, and drive revenue. Learn how to create a compelling gaming experience that stands out in the competitive market.
What is Augmented Reality Image Trackingpavan998932
Augmented Reality (AR) Image Tracking is a technology that enables AR applications to recognize and track images in the real world, overlaying digital content onto them. This enhances the user's interaction with their environment by providing additional information and interactive elements directly tied to physical images.
A Study of Variable-Role-based Feature Enrichment in Neural Models of CodeAftab Hussain
Understanding variable roles in code has been found to be helpful by students
in learning programming -- could variable roles help deep neural models in
performing coding tasks? We do an exploratory study.
- These are slides of the talk given at InteNSE'23: The 1st International Workshop on Interpretability and Robustness in Neural Software Engineering, co-located with the 45th International Conference on Software Engineering, ICSE 2023, Melbourne Australia
Utilocate offers a comprehensive solution for locate ticket management by automating and streamlining the entire process. By integrating with Geospatial Information Systems (GIS), it provides accurate mapping and visualization of utility locations, enhancing decision-making and reducing the risk of errors. The system's advanced data analytics tools help identify trends, predict potential issues, and optimize resource allocation, making the locate ticket management process smarter and more efficient. Additionally, automated ticket management ensures consistency and reduces human error, while real-time notifications keep all relevant personnel informed and ready to respond promptly.
The system's ability to streamline workflows and automate ticket routing significantly reduces the time taken to process each ticket, making the process faster and more efficient. Mobile access allows field technicians to update ticket information on the go, ensuring that the latest information is always available and accelerating the locate process. Overall, Utilocate not only enhances the efficiency and accuracy of locate ticket management but also improves safety by minimizing the risk of utility damage through precise and timely locates.
Need for Speed: Removing speed bumps from your Symfony projects ⚡️Łukasz Chruściel
No one wants their application to drag like a car stuck in the slow lane! Yet it’s all too common to encounter bumpy, pothole-filled solutions that slow the speed of any application. Symfony apps are not an exception.
In this talk, I will take you for a spin around the performance racetrack. We’ll explore common pitfalls - those hidden potholes on your application that can cause unexpected slowdowns. Learn how to spot these performance bumps early, and more importantly, how to navigate around them to keep your application running at top speed.
We will focus in particular on tuning your engine at the application level, making the right adjustments to ensure that your system responds like a well-oiled, high-performance race car.
Need for Speed: Removing speed bumps from your Symfony projects ⚡️
Hyperledger arch wg_paper_1_consensus
1. Introduction to Hyperledger Business Blockchain
Design Philosophy and Consensus
This is the first in a series of papers from the Hyperledger Architecture Working
Group (WG). These papers describe a generalized reference architecture for
permissioned blockchain networks and share the recommendations of the
Hyperledger Architecture WG with the end goal of guiding all Hyperledger
projects towards modular designs. These papers also serve as a vendor-
neutral resource for technical blockchain users and developers interested in
using permissioned blockchain networks.
In this initial paper, we aim to:
1. Outline the overarching Hyperledger design philosophy for permissioned
blockchain networks.
2. Explain how our approach optimizes the development of flexible,
interoperable enterprise blockchain technologies.
3. Identify the core permissioned blockchain network components that the
Architecture WG has been and will continue to define through its work.
4. Provide a generalized reference architecture for consensus.
5. Explore how each Hyperledger business blockchain framework manifests
the reference architecture.
Forthcoming papers in this series will expand the Hyperledger generalized
reference architecture to include the following business blockchain components:
Smart Contract Layer, Communication Layer, Data Store Abstraction, Crypto
Abstraction, Identity Services, Policy Services, APIs, and Interoperation.
ABOUT HYPERLEDGER
Hyperledger is an open source
collaborative effort created
to advance cross-industry
blockchain technologies.
It is a global collaboration
including leaders in finance,
banking, Internet of Things,
supply chains, manufacturing
and Technology. The Linux
Foundation hosts Hyperledger
under the foundation.
Hyperledger
Architecture, Volume 1
2. 2
About the Hyperledger Architecture Working Group
The Hyperledger Architecture WG serves as a cross-project forum for architects and
technologists from the Hyperledger community to exchange ideas and explore alternate
architectural options and tradeoffs. Their focus is on developing a modular architectural
framework for enterprise-class distributed ledgers. This includes identifying common and
critical components, providing a functional decomposition of an enterprise blockchain stack
into component layers and modules, standardizing interfaces between the components,
and ensuring interoperability between ledgers.
Introduction
Business blockchain requirements vary. Some uses require rapid network consensus
systems and short block confirmation times before being added to the chain. For others,
a slower processing time may be acceptable in exchange for lower levels of required
trust. Scalability, confidentiality, compliance, workflow complexity, and even security
requirements differ drastically across industries and uses. Each of these requirements, and
many others, represent a potentially unique optimization point for the technology.
For these reasons, Hyperledger incubates and promotes a range of business blockchain
technologies including distributed ledgers, smart contract engines, client libraries, graphical
interfaces, utility libraries, and sample applications. Hyperledger’s umbrella strategy
encourages the re-use of common building blocks via a modular architectural framework.
This enables rapid innovation of distributed ledger technology (DLT), common functional
modules, and the interfaces between them. The benefits of this modular approach include
extensibility, flexibility, and the ability for any component to be modified independently
without affecting the rest of the system.
HYPERLEDGER MODULAR UMBRELLA APPROACH
3. 3
Architecture Overview
All Hyperledger projects follow a design philosophy that includes a modular extensible
approach, interoperability, an emphasis on highly secure solutions, a token-agnostic
approach with no native cryptocurrency, and the development of a rich and easy-to-
use Application Programming Interface (API). The Hyperledger Architecture WG has
distinguished the following business blockchain components:
• Consensus Layer - Responsible for generating an agreement on the order and
confirming the correctness of the set of transactions that constitute a block.
• Smart Contract Layer - Responsible for processing transaction requests and
determining if transactions are valid by executing business logic.
• Communication Layer - Responsible for peer-to-peer message transport between
the nodes that participate in a shared ledger instance.
• Data Store Abstraction - Allows different data-stores to be used by other modules.
• Crypto Abstraction - Allows different crypto algorithms or modules to be swapped
out without affecting other modules.
• Identity Services - Enables the establishment of a root of trust during setup of a
blockchain instance, the enrollment and registration of identities or system entities
during network operation, and the management of changes like drops, adds, and
revocations. Also, provides authentication and authorization.
• Policy Services - Responsible for policy management of various policies specified
in the system, such as the endorsement policy, consensus policy, or group
management policy. It interfaces and depends on other modules to enforce the
various policies.
• APIs - Enables clients and applications to interface to blockchains.
• Interoperation - Supports the interoperation between different blockchain instances.
In this document, we will explore consensus. The goal of consensus is to generate an
agreement on the order and to validate the correctness of the set of transactions that
constitute the block.
Consensus
Consensus is the process by which a network of nodes provides a guaranteed ordering
of transactions and validates the block of transactions. Consensus must provide the
following core functionality:
• Confirms the correctness of all transactions in a proposed block, according to
endorsement and consensus policies.
• Agrees on order and correctness and hence on results of execution (implies
agreement on global state).
• Interfaces and depends on smart-contract layer to verify correctness of an ordered
set of transactions in a block.
4. 4
Comparison of Consensus Types
Consensus may be implemented in different ways such as through the use of lottery-
based algorithms including Proof of Elapsed Time (PoET) and Proof of Work (PoW) or
through the use of voting-based methods including Redundant Byzantine Fault Tolerance
(RBFT) and Paxos. Each of these approaches targets different network requirements and
fault tolerance models.
The lottery-based algorithms are advantageous in that they can scale to a large number
of nodes since the winner of the lottery proposes a block and transmits it to the rest
of the network for validation. On the other hand, these algorithms may lead to forking
when two “winners” propose a block. Each fork must be resolved, which results in a
longer time to finality.
The voting-based algorithms are advantageous in that they provide low-latency finality.
When a majority of nodes validates a transaction or block, consensus exists and finality
occurs. Because voting-based algorithms typically require nodes to transfer messages
to each of the other nodes on the network, the more nodes that exist on the network,
the more time it takes to reach consensus. This results in a trade-off between scalability
and speed.
The operating assumption for Hyperledger developers is that business blockchain
networks will operate in an environment of partial trust. Given this, we are expressly not
including standard Proof of Work consensus approaches with anonymous miners. In our
assessment, these approaches impose too great a cost in terms of resources and time to
be optimal for business blockchain networks.
Table 1 offers an at-a-glance view of the main considerations and pros and cons of
different business blockchain approaches to reaching consensus.
Permissioned
Lottery-based
Permissioned
Voting-based
Standard Proof of
Work (Bitcoin)
Speed
Scalability
Finality
TABLE 1. COMPARISON OF PERMISSIONED CONSENSUS APPROACHES AND STANDARD PoW
MODERATE
MODERATE
GOOD
GOOD
GOOD POOR
POOR
GOOD
GOOD
5. 5
Consensus and Its Interaction with Other
Architectural Layers
While there are many ways in which consensus can be achieved, our analysis of
blockchain platforms suggests that the process shown in Figure 1 is commonly used.
This is a generalized view, and the different Hyperledger frameworks may choose to
implement these steps differently.
Hyperledger business blockchain frameworks reach consensus by performing two
separate activities:
1. Ordering of transactions
2. Validating transactions
By logically separating these activities, we ensure that any Hyperledger framework can
work with any Hyperledger consensus module.
The first step of the consensus process flow is receiving the transactions from the client
application. Consensus depends on an ordering service to order transactions. The ordering
service can be implemented in different ways: ranging from a centralized service, which can
be used in development and testing, to distributed protocols that target different network and
node fault models. To enable confidentiality of the transactions, the ordering service may be
agnostic to the transaction; that is, the transaction content can be hashed or encrypted.
FIGURE 1. GENERALIZED HYPERLEDGER CONSENSUS PROCESS FLOW
6. 6
Transactions are submitted via an interface to the ordering service. This service collects
transactions based on the consensus algorithm and configuration policy, which may
define a time limit or specify the number of transactions allowed. Most of the time, for
efficiency reasons, instead of outputting individual transactions, the ordering service will
group multiple transactions into a single block. In this case, the ordering service must
impose and convey a deterministic ordering of the transactions within each block.
To validate transactions, consensus depends on the smart contract layer because it
contains the business logic behind what makes a transaction valid. The smart contract
layer validates each transaction by ensuring they conform to policy and the contract
specified for the transaction. Invalid transactions are rejected and possibly dropped from
inclusion within a block.
We can divide potential validation errors into two categories: syntax and logic errors. For
syntax errors such as invalid inputs, unverifiable signature, and repeated transaction (due
to error or replay attacks), the transaction should be dropped. The second category of
errors is more complex and should be policy driven whether to continue processing or
not. For example, a transaction that would result in double-spend or versioning control
failure. We might want to log these transactions for auditing if the policy requires.
The consensus layer uses the communication layer for communicating with the client and
other peers on the network.
Consensus Properties
Consensus must satisfy two properties to guarantee agreement among nodes: safety
and liveness.
Safety means that each node is guaranteed the same sequence of inputs and results
in the same output on each node. When the nodes receive an identical series of
transactions, the same state changes will occur on each node. The algorithm must
behave identical to a single node system that executes each transaction atomically one
at a time.
Liveness means that each non-faulty node will eventually receive every submitted
transaction, assuming that communication does not fail.
Consensus in the Hyperledger Frameworks
Because business blockchain requirements will vary, the Hyperledger community
is working on several different consensus mechanisms as well as implementation
approaches to ensure modularity.
Table 2 provides a comparison of the consensus algorithms used across Hyperledger
frameworks. Apache Kafka in Hyperledger Fabric, RBFT in Hyperledger Indy, and
Sumeragi in Hyperledger Iroha use a voting-based approach to consensus that provides
fault tolerance and finality within seconds. PoET in Hyperledger Sawtooth uses a lottery-
based approach to consensus that provides scale at the cost of finality being delayed
due to forks that must be resolved.
7. 7
Consensus Algorithm Consensus Approach Pros Cons
Kafka in
Hyperledger Fabric
Ordering Service
Permissioned voting-
based. Leader does
ordering. Only in-sync
replicas can be voted as
leader. (“Kafka,” 2017).
Provides crash fault
tolerance. Finality
happens in a matter of
seconds.
While Kafka is crash
fault tolerant, it is not
Byzantine fault tolerant,
which prevents the
system from reaching
agreement in the case of
malicious or faulty nodes.
RBFT in
Hyperledger Indy
Pluggable election
strategy set to a
permissioned, voting-
based strategy by
default (“Plenum,” 2016).
All instances do
ordering, but only the
requests ordered by
the master instance are
actually executed.
(Aublin, Mokhtar & Quéma, 2013)
Provides Byzantine
fault tolerance. Finality
happens in a matter of
seconds.
The more nodes that
exist on the network,
the more time it takes to
reach consensus.
The nodes in the
network are known
and must be totally
connected.
Sumeragi in
Hyperledger Iroha
Permissioned server
reputation system.
Provides Byzantine
fault tolerance. Finality
happens in a matter
of seconds. Scale to
petabytes of data,
distributed across many
clusters (Struckhoff, 2016).
The more nodes that
exist on the network,
the more time it takes to
reach consensus.
The nodes in the network
are known and must be
totally connected.
PoET in
Hyperledger
Sawtooth
Pluggable election
strategy set to a
permissioned, lottery-
based strategy by
default.
Provides scalability and
Byzantine fault tolerance.
Finality can be delayed
due to forks that must be
resolved.
TABLE 2. COMPARISON OF CONSENSUS ALGORITHMS USED IN HYPERLEDGER FRAMEWORKS
8. 8
Consensus in Hyperledger Fabric
Consensus in Hyperledger Fabric is broken out into 3 phases: Endorsement, Ordering,
and Validation.
• Endorsement is driven by policy (eg m out of n signatures) upon which participants
endorse a transaction.
• Ordering phase accepts the endorsed transactions and agrees to the order to be
committed to the ledger.
• Validation takes a block of ordered transactions and validates the correctness of the
results, including checking endorsement policy and double-spending.
Hyperledger Fabric supports pluggable consensus service for all 3 phases. Applications
may plugin different endorsement, ordering, and validation models depending on their
requirements. In particular, the ordering service API allows plugging in BFT-based agreement
algorithms. The ordering service API consists of two basic operations: broadcast and deliver.
• broadcast(blob): a client calls this to broadcast an arbitrary message blob for
dissemination over the channel. This is also called request(blob) in the BFT context,
when sending a request to a service.
• deliver(seqno, prevhash, blob): the ordering service calls this on the peer to deliver
the message blob with the specified non-negative integer sequence number
(seqno) and hash of the most recently delivered blob (prevhash). In other words, it is
an output event from the ordering service. deliver() is also sometimes called notify()
in pub-sub systems or commit() in BFT systems.
Multiple ordering plugins are being developed currently, including BFT Smart, Simplified
Byzantine Fault Tolerance (SBFT), Honey Badger of BFT, etc. For Fabric v1, Apache Kafka
is provided out-of-the-box as a reference implementation. The application use-cases and
its fault tolerance model should determine which plugin to use.
FIGURE 2. ILLUSTRATION OF ONE POSSIBLE TRANSACTION FLOW (COMMON-CASE
PATH) IN HYPERLEDGER FABRIC
9. 9
Consensus in Hyperledger Indy
Consensus in Hyperledger Indy is based on Redundant Byzantine Fault Tolerance (RBFT),
which is a protocol inspired by Plenum Byzantine Fault Tolerance (Plenum). Think of RBFT as
running several instances of Plenum in parallel. Ordered requests from a single instance called
the master is used to update the ledger, but the master’s performance in terms of throughput
and latency is periodically compared to the average performance of other instances. If the
master is found to be degraded, a view change occurs that appoints a different instance to
the role of master. Like PBFT, RBFT needs at least 3f+1 nodes to handle f faulty nodes. Figure 3
shows a network of 4 nodes that can handle 1 faulty node, has 2 PBFT-like instances running,
one master and one backup. Each node can host one primary (leader) instance.
Source: (Aublin, Mokhtar & Quéma, 2013)
FIGURE 3. RBFT OVERVIEW
Figure 4 shows a different view of RBFT. Here the client is sending a request to nodes.
It does not have to send to all nodes because sending to f+1 nodes is sufficient. After
receiving the client request, the nodes do a dissemination process through PROPAGATE
in which every other node is made aware of the request. Each primary creates a proposal
from the received requests called a PRE-PREPARE and sends it to all other nodes. If the
nodes accept the primary’s proposal, they send an acknowledgement to the proposal by
a message called PREPARE. Once a node gets a PRE-PREPARE proposal and 2f PREPARE
messages, then it has sufficient information to accept the proposal and sends a COMMIT
message. Once a node gets 2f+1 COMMIT messages, then the batch of requests can
be ordered and added to the ledger since a sufficient number of nodes have agreed
that a majority of nodes have accepted the proposal. The primary does not require one
proposal to complete before it can send the next proposal.
10. 10
Hyperledger Indy uses RBFT to handle ordering and validation, which results in a single
ledger containing both ordered and validated transactions. This is unlike many blockchain
networks that use a Byzantine Fault Tolerance (BFT) protocol only for ordering. These
networks leave domain-specific validation to happen after requests are ordered.
Plenum, and therefore RBFT, maintains a projection of the ledger called state. All valid,
accepted operations performed may change the state, which is stored in a database
as a collection of variables and their values. The state is kept in a cryptographically
authenticated data structure called a Merkle Patricia tree, which is specified by Ethereum.
Hyperledger Indy stores Decentralized Identifiers (DIDs) as state variables with values
including the current verification key and a few other things. The in memory copy of the
ledger transactions and resulting state are optimistically updated during the proposal
phase. The primary is updated while sending the proposal and non-primaries are
updated while accepting a valid proposal. The proposal gets ordered, then the ledger
and the resulting state are committed. If the proposal gets rejected for some reason, then
the changes made to the ledger and the resulting state are reverted.
This optimistic update is necessary to have multiple proposals being proposed without
the previous proposals being completely ordered. For example, if the first proposal
contained a request which was creating a new identity Id1 on the ledger and the second
proposal contained a request adding an attribute for Id1, then if the state did not reflect
the existence of Id1, the second proposal would be rejected. So, before the second
proposal is accepted, the changes in the first proposal should be visible. When changes
have been proposed, but not yet committed, it’s called an uncommitted change.
Source: (Aublin et al., 2013)
FIGURE 4. RBFT PROTOCOL STEPS
11. 11
FIGURE 5. NORMAL TRANSACTION FLOW IN HYPERLEDGER IROHA WITH SUMERAGI
Consensus in Hyperledger Iroha
Hyperledger Iroha introduces a BFT consensus algorithm called Sumeragi, which tolerates
f numbers of Byzantine faulty nodes in a network, like all BFT systems. It is heavily inspired
by the B-Chain Algorithm described by Duan, Meling, Peisert, & Zhang (2014).
As in B-Chain, we consider the concept of a global order over validating peers and sets
A and B of peers, where A consists of the first 2f+1 peers and B consists of the remainder.
As 2f+1 signatures are needed to confirm a transaction, under the normal case only 2f+1
peers are involved in transaction validation. The remaining peers only join the validation
when faults are exhibited in peers in set A. The 2f+1th peer is called the proxy tail. For
normal (non-failure) cases, the transaction flow is shown as in Figure 5.
The client, which will typically be an API server interfacing with an end-user client, first
submits a transaction to the lead validating peer. This leader then verifies the transaction,
orders it into the queue, and signs the transaction. It then broadcasts this transaction to
the remaining 2f+1 validating peers.
The order of processing nodes is determined based on the server reputation system
called hijiri. Hijiri calculates the reliability of servers based on three factors. First, based
on the time each server registered with the membership service. Second, based on the
number of successful transactions processed by each server. Third, based on whether
failures have been detected.
12. 12
FIGURE 6. TRANSACTION FLOW IN THE CASE OF A SERVER FAILURE IN
HYPERLEDGER IROHA WITH SUMERAGI
To detect failures, each server sets a timer when it signs and broadcasts a transaction
to the proxy tail. If there is a failure in an intermediate server and a reply is not received
before the timer goes off, then the server rebroadcasts the transaction and its signature
to the next server in the chain after the proxy tail. The case of a failure in the proxy tail is
shown in Figure 6.
Consensus in Sumeragi is performed on individual transactions and on the global state
resulting from the application of the transaction. When a validating peer receives a
transaction over the network, it performs the following steps in order:
1. Validate the signature (or signatures, in the case of multi-signature transactions) of the
transaction.
2. Validate the contents of the transaction, where applicable. For example, transfer
transactions must leave the payer’s account with a non-negative balance.
3. Temporarily apply the transaction to the ledger. This involves updating the Merkle root
of the global state.
4. Sign the updated Merkle root and the hash of the transaction contents.
5. Broadcast the tuple, which is a finite ordered list of transactions.
6. When syncing nodes with each other, valid parts of the Merkle tree are shared until
the roots match.
13. 13
Consensus in Hyperledger Sawtooth
Hyperledger Sawtooth facilitates pluggable consensus for both lottery and voting
algorithms. By default, Hyperledger Sawtooth uses a lottery-based, Nakamoto consensus
algorithm called PoET. As with Bitcoin’s PoW, PoET uses a lottery for leader election
based on a guaranteed wait time provided through a Trusted Execution Environment (TEE)
(Sandell, Bowman, & Shah, 2016). For the purpose of achieving distributed consensus
efficiently, a good lottery function has several characteristics that have been defined by
Sandell et al. (2016) as:
• Fairness - The function should distribute leader election across the broadest possible
population of participants.
• Investment - The cost of controlling the leader election process should be
proportional to the value gained from it.
• Verification - It should be relatively simple for all participants to verify that the leader
was legitimately selected.
The current implementation of Hyperledger Sawtooth builds on a TEE provided by Intel’s
Software Guard Extensions (SGX). This ensures the safety and randomness of the leader
election process without requiring the costly investment of power and specialized hardware
inherent in most “proof” algorithms.
Every PoET validator requests a random time to wait from a trusted function before claiming
leadership. The validator with the shortest wait time for a particular transaction block is
implicitly elected the leader. The function “CreateTimer” creates a timer for a transaction
block that is guaranteed to have been created by the TEE. The “CheckTimer” function
verifies that the timer was created by the TEE and, if it has expired, creates an attestation
that can be used to verify that validator did, in fact, wait the allotted time before claiming the
leadership role.
The PoET leader election algorithm meets the criteria for a good lottery algorithm. It
randomly distributes leadership election across the entire population of validators with a
distribution that is similar to what is provided by other lottery algorithms. The probability of
election is proportional to the resources contributed, where resources are general purpose
processors with a TEE. An attestation of execution provides information for verifying that the
certificate was created within the TEE and that the validator waited the allotted time. Further,
the low cost of participation increases the likelihood that the population of validators will be
large, increasing the robustness of the consensus algorithm.
14. 14
Conclusion
In this initial paper, we introduced the modular architectural framework used by all
Hyperledger projects and explored multiple ways that consensus can be implemented
within this modular framework.
Key takeaways include:
1. The overarching Hyperledger design philosophy for permissioned blockchain
networks follows a modular approach that enables extensibility and flexibility.
2. Within this modular approach, Hyperledger defines common functional components
and the interfaces between them, which allows any component to be modified
independently without affecting the rest of the system.
3. The Architecture WG has been and will continue to define the following core
components for permissioned blockchain networks: Consensus Layer, Smart
Contract Layer, Communication Layer, Data Store Abstraction, Crypto Abstraction,
Identity Services, Policy Services, APIs, and Interoperation.
4. The Architecture WG has shared a generalized reference architecture for
consensus that can be used by any Hyperledger project.
5. Hyperledger Fabric, Hyperledger Indy, Hyperledger Iroha, and Hyperledger
Sawtooth each manifest the reference architecture principles in unique ways.
The comparison of consensus algorithms commonly used with these frameworks
is provided in Table 1, which can be used to quickly determine the strengths and
weaknesses of algorithms including Kafka, RBFT, Sumeragi, and PoET.
Forthcoming papers in this series will expand the Hyperledger generalized reference
architecture to cover all the core components for permissioned blockchain networks.
The next paper in the series will cover the Smart Contract Layer. If you are interested in
participating in Hyperledger’s Architecture working group, please visit the Wiki page for
more information.
15. References
Aublin, P., Mokhtar, S.B., & Quéma, V. (2013). RBFT: Redundant Byzantine Fault Tolerance.
Distributed Computing Systems (ICDCS), 2013 IEEE 33rd International Conference on, pp.
297-306. doi:10.1109/ICDCS.2013.53 or http://dx.doi.org/10.1109/ICDCS.2013.53
Cachin, C., & Vukolić, M. (July 7, 2017). Blockchain Consensus Protocols in the Wild. IBM
Research - Zurich. arXiv:1707.01873 or https://arxiv.org/abs/1707.01873v2
Duan S., Meling H., Peisert S., & Zhang H. (2014). BChain: Byzantine Replication with High
Throughput and Embedded Reconfiguration. In: Aguilera M.K., Querzoni L., & Shapiro M.
(eds) Principles of Distributed Systems. OPODIS 2014. Lecture Notes in Computer Science,
vol 8878, pp. 91-106. Springer, Cham. doi:10.1007/978-3-319-14472-6_7 or http://dx.doi.
org/10.1007/978-3-319-14472-6_7
Kafka 0.11.0 Documentation. (2017). Retrieved from https://kafka.apache.org/
documentation/
Plenum Byzantine Fault Tolerant Protocol. (2016). Retrieved from https://github.com/
hyperledger/indy-plenum/wiki
Sandell, P., Bowman, M., & Shah, P. (2016). Blockchain and Its Emerging Role in
Healthcare Related Research. Intel Corporation – Health and Life Sciences Group. https://
oncprojectracking.healthit.gov/wiki/download/attachments/14582699/19-Blockchain_
Whitepaper_Intel_Final.pdf
Struckhoff, Roger. The Iroha Project to Bring Mobility to Blockchain with Simple APIs.
(December 22, 2016). Retrieved from https://www.altoros.com/blog/the-iroha-project-to-
bring-mobility-to-blockchain-with-simple-apis/
Iroha Whitepaper. (March 7, 2017). Retrieved from https://github.com/hyperledger/iroha/
blob/master/docs/iroha_whitepaper.md