Page History

Versions Compared

Old Version 22

changes.mady.by.user Bobbi Muscara

Saved on Dec 03, 2020

compared with

New Version Current

changes.mady.by.user Bobbi Muscara

Saved on Jan 25, 2023

Key

This line was added.
This line was removed.
Formatting was changed.

Comment: Migration of unmigrated content due to installation of a new plugin

2023 Q1 Hyperledger Fabric

Image Added

2022 Q2 Hyperledger Fabric

Image Added

2022 Q1 Hyperledger Fabric

For more details on v2.4 see the What's New documentation.

Recording at Contributor Meetings 2022.

Image Added

Q4 Report

v2.2 is the current LTS release with patch releases quarterly.

project delivered v2.4.0-beta with two significant new features:

Fabric Gateway - The Fabric Gateway will remove much of the transaction submission and query logic from the client application and shift it to a common gateway running within the Fabric peer, enabling each of the various client SDKs to be slimmer, more consistent, and require less maintenance. Applications will interact with a trusted peer (e.g. at their organization) and the peer will coordinate endorsements from other peers and submission to the ordering service. It will also simplify the administrative overhead of running a Fabric network because client applications will be able to connect and submit transactions via a single network port at their organization rather than the current situation where ports have to be opened from a client application to multiple peers across potentially multiple organizations. The Fabric Gateway is delivered along with slim SDKs in the https://github.com/hyperledger/fabric-gateway repository. Check out the client application samples.
Peer unjoin - The new command "peer node unjoin" enables an administrator to remove (unjoin) a channel from a peer.
The peer must be stopped when the command is executed so that channel artifacts can be cleaned up.
The channel's blockchain, state database, and associated entries will be removed from the peer.
When the peer is restarted it will no longer receive blocks for the channel.

Image Added

Q3 Report

Image Added

Hyperledger Fabric

Welcome to Hyperledger Fabric - Details on how to get started
Main documentation
Getting Started for application developers

Q2 Report

4/15/2021
Image Added

Image Added

Project

Hyperledger Fabric

Image Removed

...

Image Removed

...

Quarterly Report: 2020 Q4 Hyperledger Fabric

Academic paper

https://dl.acm.org/doi/10.1145/3190508.3190538

...

Image Added

Statistics

Image Added

12/8

11/15

Q$	Image AddedImage Added

Contributing to Fabric and related sub-projects
Coding Guidelines
Design docs
Meeting notes
Videos on YouTube for Hyperledger Fabric. Includes informational and playbacks. Subscribe to be automatically notified when new videos are posted.
Getting Started in CI - Debugging CI jobs failures

Releases

v1.4 and v2.2 are the current LTS releases. Each has patch releases at least quarterly.

...

Ledger checkpointing
Channel participation API
WASM for smart contracts (tech preview released)
Samples and tutorials revamp
Production deployment guides
Documentation translation

...

Email issues:

There are no results for Just like all public state transitions (including deletes) are stored in the peer's block store, all private data state transitions (including deletes) are stored in the peer's private data store. The peer's private data store ensures that listeners and other peers that may be catching up at lower heights can retrieve the private data that they need. You are correct that only the blockToLive policy will purge the private data from the peer's private data store. Others have also requested an on demand delete from both private state and private data store, and as a result we created enhancement request https://jira.hyperledger.org/browse/FAB-5097 which you can vote for and watch in Jira. Solutions that want more control over private data often prefer to hash the data prior to submitting it to Fabric, rather than having Fabric disseminate it through the private data feature.