distributed-ledger

When installing a new chaincode on the peer you do get the package id of the chaincode which is good... this allows customers to use that data to go through the approve/commit steps.

However the issue is when they are reinstalling an existing chaincode there is nothing in the response to indicate the package id(hash). Install in that case returns a message that the chaincode already exists. We

Currently there seem to be 3 options for testing Corda:

1. MockNetwork
2. Driver DSL
3. Manually start a network then run tests

The MockNetwork is useful for testing flows but it doesn't implement an RPC interface so you can't use it in your Spring REST API tests.

The Driver DSL has an RPC interface but all the work appears to have to be done in the dsl closure which means you can't get

The problem is that buffer array seems to have a different prototype than js definition and when convertBytetoString is called then:

for (const index in buffer_array) {

will start iterating over the prototype properties and result is incorrectly set to be a string of the function definitions instead of being empty string.
Could be fixed by adding a guard:

for (const index in buffer_array

There's a bunch of back-and-forth between domain.Offset and String in AcsTxStreams and [ContractsFetch](https://github.com/digital-asset/daml/blob/9fd8182bbb6c7ee85b65a7edbeba68ca5ac9b901/ledger-service/http-json/src/main/scala/c

It would be handy for longevity stand to have export of logs into some file which can be structurally filtered. Bunyan format fits for that case:
https://crates.io/crates/tracing-bunyan-formatter

As an enhancement it would great to limit file size somehow and let new logs overwrite old ones.