Paper doesn't mature. about cp-web

[masterDev1985]

Currently, we can't rely on chaincode to handle checking these trades and processing transfers on maturation dates. This is because chaincode containers can die on the network. Peers will just bring them back up whenever the next invoke or query comes up, but this is a game-over for letting chaincode handle maturation. I'm thinking we could just have the web app send a query to the chaincode every minute or so, calling a function that runs through all the trades and processes any that have matured.

[gregmisiorek]

if it doesn't mature, what makes it a 'paper'? maybe it should be called a perpetual annuity until it 'acquires' an expiration date?

[masterDev1985]

There are other issues I'm currently working on, but I do intend to implement this functionality, eventually. I don't want to discourage the community from helping, however. If anyone has an idea for how to implement this, we'd love to see it!

[russelldc]

@masterDev1985
Has there been any headway in this direction?

[masterDev1985]

@russelldc I'm afraid not. For now, I'm not adding any new features to cp-web.

[russelldc]

@masterDev1985 Regardless of the cp-web project, is there still an issue with chaincode containers indeterminately dying?

[masterDev1985]

Well, chaincode containers dying shouldn't be an issue. Whenever the peer needs chaincode, it should start or recreate the chaincode container from the image.