yacovm
yacovm
I think that instead of mimicking Fabric semantics in a complete manner, the strategy should be really deviating from Fabric by: 1. Restricting functionality of what you can do 2....
> The challenge is, though, that current trusted ledger architecture, besides validation of fpc chaincode transaction, relies on proper validation of (a) standard fabric channel definition with, e.g., msp and...
> Hmm, i don't think you can rely on this. If the trusted ledger doesn't validate the config-changes but just takes them at face value, a bad peer could create...
> Given that we need MSP-rooted signature verification, (subsets of) policy evaluation and the parsing of the protobufs elsewhere (and hence corresponding library functions), it's less clear how much complexity...
panic: tocommit(25) is out of range [lastIndex(16)]. Was the raft log corrupted, truncated, or lost?
How did you redeploy? Did you backup the files of the orderer's file system or something?
panic: tocommit(25) is out of range [lastIndex(16)]. Was the raft log corrupted, truncated, or lost?
I'm sorry but I don't understand what steps you followed. Can you be more clear and accurately describe everything you did?
5 seconds is normal.
But even without this abdication, if the leader is removed, the other two nodes should be able to select a new leader. The test, tests this property. so it should...
> > Hi @denyeart https://go.dev/ref/mod#incompatible-versions > > Do we have plan to referring this module name convention on module in format of `../v2` in next LTS 2.5 release? Fabric core...
> > > > > > > > > > Hi @denyeart https://go.dev/ref/mod#incompatible-versions > > > Do we have plan to referring this module name convention on module in format...