Date
1 - 2 of 2
one org upgrade chaincode
|
qs meng <qsmeng@...>
Hi, In 1 August, Wang discussed that only one org can upgrade a chaincode and change its endorsing policy. I also think this is a serious security problem. I also notice that more 1.4.x versions are being released in sequence. why not solve this problem in future version 1.4.x+1? After all this is LTS and may be already used in production environment by many teams. Thank you. best regards, qs meng
|
|
|
|
Alessandro Sorniotti
Hi
toggle quoted message
Show quoted text
The issue is being addressed by the new lifecycle work: a preview of this work has been showed in the 2.0 alpha release and the feature is scheduled for release in the 2.0 version in the upcoming months. It's unlikely that the feature will be backported to the 1.4 version given its size and scope. Note that it's possible to upgrade a 1.4 network to 2.0 and start using the new lifecycle also for already defined chaincodes. Thanks! Ale On Wed, 14 Aug 2019, at 11:41 AM, qs meng wrote:
Hi, |
|
|