consensus

When deploying fabric in enterprise's intranet (without the ability to access internet), users maybe upload chaincode builder images and chaincode runtime images to a private docker registry which requires authentication when pulling images.
I think fabric can support this scenario by adding configuration in chaincode section of core.yaml, such as:

chaincode:
    registry:
        

This would allow the CLI to try connecting to a different node is the first node goes down.

A parametrized option to set the blocksize would be useful to experiment with. As quorum is used in a private setting I think this option should be available

非常感谢大家对 SOFAStack 开源的关注和支持，这是我们前进最大的动力。

收集目的

• 了解 SOFAStack 的使用场景以便更好的规划技术路线
• 聆听社区的不同声音，让 SOFAStack 变得更好
• 吸引更多的开源爱好者参与贡献，共同打造 SOFAStack

收集方式

请按如下参考格式回复本 Issue 进行登记：

• 公司/组织名称：蚂蚁金服
• 地点：中国杭州
• 网址：http://www.antfin.com
• 使用组件及场景：全套金融级分布式中间件
• 联系方式：zhanggeng.zg@antfin.com

展示

我们会定期同步信息至「Awesome SOFA」的用户列表中。

服务

如果您已经在生产环境中使

Here is a rough idea of what this test should do:

• It should be quite similar to the other tests which are currently in place.
• It should isolate a follower node, write a data to the cluster which will cause that node to fall behind into lagging state, but not into snapshotting state.
• It should then spawn a task which will continue to write data to the cluster.
• Just after it is spawne

Description

The app doesn't close when pressing the CTRL-C hotkey immediately after start. Pressing it again and again doesn't change the behavior

Steps to reproduce

1. Run go-spacemesh
2. Immediately press CTRL-C

Actual Behavior

Th

https://github.com/paritytech/sub-flood

And more... What might you add? 😁

Instead of a single validator (a.k.a. pivot node), the test net_dynamic_hb should pick a subset of validators at random for removal. This will better reflect the [interface](https://github.com/poanetwork/hbbft/blob/742ad7b83a3f613fd9a7b4ff88cfa82b10bd7dd3/src/dynamic_honey_badger/dyn