This repository is not designed for productive usage. Instead it should be used for demonstration and learning purposes.

Install the Certificate of Origin: npm install.

The Certificate of Origin app can be deployed on any ethereum-network

• For testing purposes, we recommend deploying it on a local ganache-rpc
  • The app is pre-configured to start ganache with: npm run start-ganache

Deploy contracts to preferred network (default ganache-cli): npm run migrate

Mnemonic : outer moment twin salmon shuffle amused twice evil rapid hotel burst stand

• A TopAdmin or UserAdmin can onboard new users with: setUser()
• After, the roles of the users have to be added by either calling:
  • setRoles()
  • addRoles()

Electricity Producing Implement

Example: Power Plant

(The procedure for onboarding a producing asset is nearly the same as the consuming ones.)

1. createAsset() (Roles: TopAdmin or AssetAdmin)
   • returns your new assetId in event
2. initProducingProperties(uint _assetId,...)
3. initGeneral(uint _assetId,...).

(You should recieve a LogAssetFullyInitialized event including your assetId)

saveSmartMeterRead() to log consumed energy

Electricity Consuming Implement Example: Factory

1. createAsset() (Roles: TopAdmin or AssetAdmin)
   • returns a new assetId in an event

After receiving the assetId you're able to call the functions:

2. initGeneral(uint _assetId,...)
3. initLocation (uint _assetId, ...)

(You should receive a LogAssetFullyInitialized event including your assetId)

saveSmartMeterRead() to log consumed energy

Electricity Demand

1. createDemand(): As TopAdmin or AgreementAdmin
   • Requires an array with 10 elements for the different properties that are enabled or disabled (see smart contracts).
2. initGeneralAndCoupling()
3. initMatchProperties()
4. initPriceDriving()

The smart contract will require the following:

• The demand can't have both and originator and a specific producing asset
• If the producing asset is enabled, it must exist
• If the consuming asset is enabled, it must exists
• The Matcher's address must have the Matcher's role

Ways to match:

• matchCertificate(): Match an Existing Certificate to a demand
• matchDemand(): Match Produced Energy to a demand

Internally both functions are calling the same functions for checking the compatibility of the demand and the energy certificate.

These functions can also be called before a transaction, to check if an error would result:

• checkDemandCoupling()
• checkDemandGeneral()
• checkMatcher()
• checkPriceDriving()

Only these certificates can be matched with demands: