Orie Steele

Indeed, this issue is caused by how jest handles globals... A work around is to use a custom environment: `custom-jest-node-environment.js` ```js const Environment = require('jest-environment-jsdom'); const { BbsBlsSignature2020 } =...

https://github.com/OR13/GNARLY/blob/main/package.json#L57 ``` "ts-jest": "^27.0.2", ```

Please add comments regarding likes / dislikes for this use case... needs additional opinions... Consider how this discussion effects layers... and how we can get our high level interface on...

@csuwildcat @dmitrizagidulin to make sure there is a PR for use cases and close this.

@venu2062 I think we will address this on the next call, when we discuss authorization.

At the same layer? probably not, for most definitions of "layer"... granting authorization to plaintext and a serialization format / APIs for replica-table cipher texts are 2 different things entirely....

Layers: - Storage - Encryption - Authorization This is how pretty much every system including dropbox / drive / filesystems work.

@agropper sure ### Case 1 Trusted Service Provider The "Provider Client" runs on my computer, it is authorized to upload content to my "Provider Cloud Account", encryption happens only in...

"Ferrous Mountain " :) As far as I can tell, Case 3 is actually "Case 2" with a new entity that consumes "Case 2 Provider as a service". Essentially: Patient...

lol :) Assume the labs are associated with Alice, Bob can receive them from either "Lab Provider" or "Ferrous Mountain" depending on the eula / legal contracts that were signed....