Open sichen1234 opened 3 years ago
opentpas SEAS is designed for an auditor or bureau to manage the energy use and emissions data of a number of customers.
If we have true client side authentication such as trust id or #11, we could have a customer application such as a mobile app which sends utility data and signs them with a customer's ID.
During this week's peer programming call we talked about using Indy/Aries to store user identities and TrustID to authenticate the user. This may become the basis of a client side application.
We're currently using opentpas SEAS for connecting utility data to the ledger.
There could and should be other client apps that could connect to the ledger, calculate total emissions, manage offsets, etc.
We should discuss ideas on what these apps should look like and how they should be built.