#9 Unifying using the contract ID

[Jiri Hodik]

In the D3.1 (not only there) it is mentioned there that the contract name (String) is the unique ID of the contract, while the Contract Repository uses its own ID (Long). We suggest unifying using the contract ID and use the contract name (unique String) everywhere. For the Contract Repository API it invokes modification of most of methods in their parameters and returned types. Moreover, the create() method should manage (not allow) situation when somebody try to upload new contract having the same ID as another one already uploaded.