I would echo what Yacov said early on. Pruning orderers should not be especially challenging. The biggest challenge will be preventing orderers from attempting to replicate old blocks and producing

The Validation/Commit refactoring for post-order execution has been resource starved behind other priorities. Glad to hear there is interest in collaboration however. Could you summarize the

> But for some reasonwhen this feature was implemented for peers, it was not implemented fororderers, so I presume there are some not-so-obvious issues with orderersthat make their case different from

> Join peers to a new channel should be easier than dealing with orderers. The point is not to migrate all the data over. You want to start fresh and leave the old data in its own channel. Doing

Join peers to a new channel should be easier than dealing with orderers. The point is not to migrate all the data over. You want to start fresh and leave the old data in its own channel. Doing

Hi Tong! > Wonder if you create a new channel with a new set of orderers will help with your scenario. Not exactly what you are looking for, but thinking if you work with a new channel for a

Hi Yacov! > Given that the (common) ledger in the orderer and the peers is the same (common) implementation, I guess (but I'm not sure) that we don't need to make additional changes in the ledger to

Vitalii, Wonder if you create a new channel with a new set of orderers will help with your scenario. Not exactly what you are looking for, but thinking if you work with a new channel for a

Conceptually, it should be fairly easyto implement pruning for orderers when they running without a system channel. When you join such orderers to a channel,you do it by giving them the latest

Hello Fabric Team, I'm from Oracle Blockchain Platform Team. Few of us are working on Tokenisation feature in our HLF platform. As of now, we have implemented this in chaincode. This works fine with

Hi all! Our company (norbloc AB) is facing a problem with managing disk space occupied by ledger DB. Thanks to the snapshot feature in Fabric v2.3 the problem was solved for the peers, but we still

Looks like the issue is resolved. Dave Enyeart

Hello, There seems to be something wrong with the Hyperledger fabric read the docs sites. Attached a screenshot of the same.

Thanks Bret for the good job! Best Regards, David Liu 发件人: Brett T Logan 发送时间: 2021年2月20日 7:35 收件人: fabric@... 主题: [Hyperledger Fabric] Hyperledger Fabric Gerrit

Hi Tomás, The transactions are validated and then committed by the peers. The transactions that are invalid are not committed and their content will not change the world state (the KVS):

Hello Fabric Community, When we migrated off Gerrit to GitHub we took a snapshot of the existing state of the Hyperledger Gerrit Server. I converted all of the Gerrit Change Requests and their

Hey everyone, I've been wondering about something. I know that a block can be commited with transactions inside it that are marked as invalid and therefore don't alter the world state. Is there anyway

Hyperledger Fabric Documentation Workgroup call - Western hemisphere When: Friday, 19 February 2021 11:00am to 12:00pm (GMT-05:00) America/New

Hello Team, Can you guys confirm what would be the difference between "peer lifecycle chaincode querycommitted" and "peer chaincode list --instantiated" command. What makes the end result different

Reminder: Hyperledger Fabric Documentation Workgroup call - Western hemisphere When: Friday, 19 February 2021, 11:00am to 12:00pm, (GMT-05:00) America/New