I noticed that each time I restart the service and try to issue a new credential, some remote requests are made to fetch Json documents defined in dids (@context). I could not look in depth at the original cause, but it looks to be related to a dependency in the jsonld-common library. This library allows to be initialized with some pre-cached content according to tests.
Being able to cache this content at startup can potential save from some "downtimes" when the remote endpoints are "down" or fix problems when running deployments with no Internet access.
I noticed that each time I restart the service and try to issue a new credential, some remote requests are made to fetch Json documents defined in dids (@context). I could not look in depth at the original cause, but it looks to be related to a dependency in the jsonld-common library. This library allows to be initialized with some pre-cached content according to tests.
Being able to cache this content at startup can potential save from some "downtimes" when the remote endpoints are "down" or fix problems when running deployments with no Internet access.