Dave Kelsey

If we do add this to the README then we really need to get [hyperledger.org/projects/caliper](https://www.hyperledger.org/projects/caliper) updated first, it's very out of date.

- the page states: when using the following blockchain solutions: Hyperledger Besu, Hyperledger Burrow, Ethereum, Hyperledger Fabric, FISCO BCOS, Hyperledger Iroha and Hyperledger Sawtooth. Caliper now only has capabilities for...

The hyperledger.org/projects/caliper page has now been updated.

As we don't have any easy control over this projects page I don't think we want to link to it. It's already out of date and I've not looked at...

@aklenik Can you take a look ?

I've started to have a look at this and was looking to use prebuilt nodejs binaries and add oqs to the environment to run nodejs code. Unfortunately I hit a...

@SWilson4 Yep, that sounds good, I assume we can invalidate the cache if we want to change the version of node. If it's at a file level (so it invalidates...

@baentsch I do a lot of builds of apps that use openssl/oqs and nodejs is by far the worst for me taken the longest (and it doesn't include openssl, liboqs...

I don't know if this project gets favourable github runner treatment, but I've now run a build of nodejs in my fork and the nodejs part takes 1 hour 18mins...

@baentsch @SWilson4 I've created a PR for nodejs here https://github.com/open-quantum-safe/oqs-demos/pull/362 On my github actions I was seeing build times of between 1hr 20mins and 1hr 45mins. On my machine I...