refactoring of directory structure

[sichen1234]

I think the current directory structure is getting confusing and propose a refactoring like this:

• data/: loading base data into database, such as emissions factors, and the dataLoader scripts for loading them
• common/: common code for calculating emissions from data/
• fabric/: code for storing emissions on Hyperledger Fabric, deploying Fabric, and tokenizing from Fabric to Ethereum
• solidity/: solidity version, including the ERC contracts, IPFS, and API server for working with the contracts
• hardhat/: hardhat scripts for development and deployment
• app/: applications built on top of the other components, including
• app/scripts: scripts such as the emissions.js
• app/api-server: for serving up the frontend UI and the synchronizing with the blockchain network
• app/frontend: the react-app UI
• open-offsets-directory/: the open offsets directory, which is completely separate righ tnow

Question: Should multi-cloud-deployment (for deploying fabric) and secure-identities (for signing fabric transactions as clients) be in the fabric/ directory?

[brioux]

These changes makes sense. For secure-identities, not sure these should go to the fabric directory. While the identity connectors (web-socket, vault) have been configured to integrate with fabric, it could be setup differently, or generalized in the future.

Identity solutions could also be built for other network components, e.g. IPFS, or a key manager/multisig tool for EVM or other public networks where NET is deployed.

[sichen1234]

That makes sense. We'll leave the secure-identities in its own directory.

[sichen1234]

This is done now.