hi, I’ve been working on two enhancements on the side that I think will be useful at some point down the road beyond a basic robust fabric: 1) persistent events support by utilizing an external messag

Hi Imre, To your point #3 below, you are right, this is a complex question. When the busywork/counters driver is configured with the -interlock option, the TPS measurement is currently predicated on a

Just FYI. The test node is a single physical 4c8g linux 3.16 machine. Currently only using 1 client/1 API to test the query and invoke transaction. The sample testing code can be found at https://gith

Description Agenda: https://github.com/hyperledger/fabric/wiki/Weekly-Development-Planning https://meetings.webex.com/collabs/meetings/join?uuid=M7ME8OZ0FX8ZY45U79CEWHFSOD-9VIB Meeting number: 195 533

Today we have successfully executed our release process and made available the Fabric developer preview release v0.5. In the coming days, we will continue to exercise the remaining items on the releas

Hi Marko, After many rounds of discussions in the Architecture working group I became a fan of your Next Consensus Architecture Proposal at https://github.com/hyperledger/fabric/wiki/Next-Consensus-Ar

Join #fabric-pr-review channel to discuss the pull requests at 10a EDT tomorrow Wed. 6/212 Thanks - Binh

We created a noop system chain code that does nothing but store an invoke transaction. Since it is a system chain code written in go and deployed at startup, it does not require the grpc-docker roundt

We at DA raised several pull requests for fabric, that implement features useful to connect fabric-api with fabric. The pull requests are pending and were rebased several times during last weeks. I in

This PR will require a vagrant destroy/up to install the python grpcio package, as without it, your behave tests will fail to run attempting to load the grpcio package. NOTE!!!!!!!!!!: You can manuall

Description Agenda: https://github.com/hyperledger/fabric/wiki/Weekly-Development-Planning https://meetings.webex.com/collabs/meetings/join?uuid=M7ME8OZ0FX8ZY45U79CEWHFSOD-9VIB Meeting number: 195 533

I've posted a blog post on how to get Fabric peer and membersrvc running natively on Docker on a Mac. tl;dr: pretty simple to spin up the fabric with just a docker-compose.yml. Hopefully, this lowers

On the Fabric technical call today, we discussed the ability for folks to collaborate on a feature development without having to use someone's fork branch. The advantage is that everyone would be able

An announcement for anyone who is still using the "sieve" or "classic" PBFT variants. There is a pending PR ( https://github.com/hyperledger/fabric/pull/2030 ) which removes the "sieve" and "classic"

So I've been following the firehose from watching the github issues (feeling foolish for not looking there before) and am loving all the activity. I am concerned, though, that sometimes important arch

All, A change was merged just now that removed peer command-line flags that shadowed configuration variables from YAML files: https://github.com/hyperledger/fabric/pull/2054 The reason for this change

Hi Yi, You might find a better response to your question by posting it to the fabric discussion list - hyperledger-fabric@.... I've taken the liberty of cc'ing it there. Brian -- Brian Behlendorf Exec

- Binh

I think it would make sense to move proposals from Github wiki to the regular repository. I'd like to suggest amendments to the Next Consensus Architecture Proposal which would be best submitted as a

Gabor Hosszu (Digital Asset) submitted a notable new pull request to fabric: https://github.com/hyperledger/fabric/pull/2101 Its motivation is to move code base toward the consensus architecture propo