Closed sichen1234 closed 3 years ago
currently all user's certificate and private keys are stored in aws-s3 and at the time of invoking fabric chaincode certs and private key are firstly fetched from S3.
should I remove this S3 dependence and use cactus keychain (in memory for now)? Later this in-memory keychain can be converted into cactus's vault keychain.
@sichen1234 @petermetz
Si Chen Open Source Strategies, Inc.
Video: Fighting Climate Change with Blockchain and Open Source https://youtu.be/NgxNWXa_IjE
On Mon, Jun 14, 2021 at 10:05 AM Pritam Singh @.***> wrote:
currently all user's certificate and private keys are stored in aws-s3 and the time of invoking fabric chaincode certs and private key are firstly fetched from S3.
should I remove this S3 dependence and use cactus keychain (in memory for now). Later this in-memory keychain can be converted into cactus's vault keychain.
@sichen1234 https://github.com/sichen1234 @petermetz https://github.com/petermetz
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/hyperledger-labs/blockchain-carbon-accounting/issues/176#issuecomment-860844177, or unsubscribe https://github.com/notifications/unsubscribe-auth/AANAS4IGAFI7GOR7T5ZVZRTTSYZFJANCNFSM46RDBVLA .
@Zzocker +1, sounds good as a first step!
@Zzocker Might come in handy for testing purposes later (also might not, so this is just an FYI) the @hyperledger/cactus-test-tooling
package on npm has a test class for pulling up a vault test container, see details here: packages/cactus-test-tooling/src/main/typescript/vault-test-server/vault-test-server.ts
Following up on #175, also refactor
/utility-emissions-channel/typescript_app/src/routers/utilityEmissionsChannel/ivokeEmissionscontract.v0.ts
to use the Cactus Fabric Connector.