Abstract: Multi-node resiliency may provide two or more points in a blockchain architecture from which a restarted peer can synchronize its local ledger with local ledgers of other peers that collectively form a distributed ledger. Storage-based resiliency may include providing storage that is separate from the nodes on which peers execute, and configuring a peer to store a copy of a synchronized local ledger to storage prior to restart, and synchronizing a new instance of a local ledger with the synchronized copy from storage upon restarting the peer. Peer-based resiliency may include obtaining a synchronized local ledger or genesis block from a first peer after restarting a second peer. Another point of resiliency may be provided by an orderer cluster that distributes blocks to the peers for committing to their local ledger. A peer may access obtain a synchronized ledger or genesis block from the orderer cluster upon restart.

Abstract: Multi-node resiliency may provide two or more points in a blockchain architecture from which a restarted peer can synchronize its local ledger with local ledgers of other peers that collectively form a distributed ledger. Storage-based resiliency may include providing storage that is separate from the nodes on which peers execute, and configuring a peer to store a copy of a synchronized local ledger to storage prior to restart, and synchronizing a new instance of a local ledger with the synchronized copy from storage upon restarting the peer. Peer-based resiliency may include obtaining a synchronized local ledger or genesis block from a first peer after restarting a second peer. Another point of resiliency may be provided by an orderer cluster that distributes blocks to the peers for committing to their local ledger. A peer may access obtain a synchronized ledger or genesis block from the orderer cluster upon restart.

Abstract: Multi-node resiliency may provide two or more points in a blockchain architecture from which a restarted peer can synchronize its local ledger with local ledgers of other peers that collectively form a distributed ledger. Storage-based resiliency may include providing storage that is separate from the nodes on which peers execute, and configuring a peer to store a copy of a synchronized local ledger to storage prior to restart, and synchronizing a new instance of a local ledger with the synchronized copy from storage upon restarting the peer. Peer-based resiliency may include obtaining a synchronized local ledger or genesis block from a first peer after restarting a second peer. Another point of resiliency may be provided by an orderer cluster that distributes blocks to the peers for committing to their local ledger. A peer may access obtain a synchronized ledger or genesis block from the orderer cluster upon restart.

Abstract: Multi-node resiliency may provide two or more points in a blockchain architecture from which a restarted peer can synchronize its local ledger with local ledgers of other peers that collectively form a distributed ledger. Storage-based resiliency may include providing storage that is separate from the nodes on which peers execute, and configuring a peer to store a copy of a synchronized local ledger to storage prior to restart, and synchronizing a new instance of a local ledger with the synchronized copy from storage upon restarting the peer. Peer-based resiliency may include obtaining a synchronized local ledger or genesis block from a first peer after restarting a second peer. Another point of resiliency may be provided by an orderer cluster that distributes blocks to the peers for committing to their local ledger. A peer may access obtain a synchronized ledger or genesis block from the orderer cluster upon restart.