Kim Letkeman

I would very much like to be able to "take over" an active database with a new contract version, as I described in #1217

A few thoughts on our requirements for IoT contract upgrades. Includes a short intro to our current thinking on IoT contracts. And ends with several questions on how to subsume...

[#1217](https://github.com/hyperledger/fabric/issues/1217) is needed for fast upgrades

The tricky part here is that a contract invocation will return either a byte stream that goes nowhere, or an error, that again goes nowhere. If, for example, an event...

Chaincode level is widely regarded as the appropriate mechanism. The "creator" of the transaction is available through the stub API and the fields in there can be used to provide...

The Hyperledger Composer is compatible with both fabric v0.6 and fabric v1, and v0.6 is being deprecated and removed from Bluemix fairly soon. Composer is compatible with Bluemix fabrics, with...

You changed the content of a contract platform file, which is not appropriate. The iotcontractcontainersample is the appropriate sample to follow for a custom contract. What probably happened is that...

Fabric v1 allows chaincode to be named during deployment, so this is no longer much of an issue. As in, one need only follow best practices for JSON databases to...

Hi all ... I have not formally verified the port of the IoTCP (contract platform) to fabric v1, and don't have an ETA for that. What I would do (or...

It works on Windows and presumably on MAC. These are the high priority platforms and apparently the only ones on which it has been tested. If you choose to add...