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

Also, the ld failure I believe can be solve by adding the binutils-gold package to the image. You can see the same problem on ARM was solved here for the fabric images:

Somewhere I have the instructions on how to build this, but the net-net is, the Java protobuf library doesnt have a native distribution for ARM. You need to clone the protobuf repo (which will also

Hello; - From the perspective of the peer/ca/orderer etc that are written in Go, I know that others have managed to recompile for ARM. Understand it's possible, but not sure how the performance is

Thank you all for the discussion and your input! I think we now have a high-level understanding of what has to be done, looks simple enough. Now we start the process of drafting the RFC. It will take

Hello, I would like to build latest version of hypeledger fabric into a raspberry 4 (using java). As I can see in the bash script used by curl here (latest installation) the

public_state.data will be different depending on whether you use leveldb or couchdb, since couchdb saves the JSON in a different format. private_state_hashes.data should always be the same since the

Hi Team, We were investigating to use Azure Key Vault to provide for our wallet services. The CSR, Private and Public Key is basically generated by the Vault and saved securely in the same

I created snapshots from 2 peers for same channel and same height. When I checked _snapshot_signable_metadata.json file, "private_state_hashes.data" and "public_state.data" were different in each

Private Chaincode Lab When: Tuesday, 23 February 2021 8:00am to 9:00am (GMT-08:00) America/Los

In regards to changes to the blockstore, Jason is right that they would be very trivial. For the peers case, this function

Keep in mind that the orderer doesn't havea world state anyway. It only has the ledger, and its databaseconsists of the indexes that help it manage the file storage of the ledger,but nothing

Hi Jason! > > At a very high level I would suggest. > > 1) Modifying the channel participation API to allow specifying a minimum block sequence number to replicate to when joining. > 2) Add a new

Hi Dave, Thank you for your reply. The current requirements according to product is that all valid concurrent transactions should pass through without hitting mvcc/phantom read errors and should not

Hi Paritosh, Contributor Meeting is a good place to meet, share and discuss with Fabric contributors and maintainers bi-weekly. Contributor Meetings - Hyperledger Fabric - Hyperledger Confluence PS:

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