Code diagram

Zooms into individual components.

The solution is a 3-step process:

  1. Register producing devices in EnergyWeb and collect metered data
  2. Peg the device to an Ocean Market datatoken pool having the metered data as the underlying dataset
  3. Signal device behavior by Stakers, Auditors and Optimizers using the datatoken pool

ad 1.) we cloned the EW-DOS origin repo and managed to get a dashboard with devices. Unfortunately to register a device ourselves, you need to have undergone some formal approval process so that's too inconvenient for this submission. However, we are able to simulate having a device registered and attach metered data to it, therefore we used the data.csv file of the solar-simulator package as an example.

ad 2.) Building upon the solar-simulator package, we used the i-rec registered devices to add a dropdown field in the Ocean Market front-end populated with these devices in order to have an EnergyWeb registered device use their metered data as a proxy for the datatoken pool. Selecting a device will populate all meta-data fields of the Publishing form, having a basic integration between EnergyWeb and Ocean Market.

ad 3.) This is where the actual Tokenized Power Balancing job is done. Once we have a datatoken pool with metered data as an underlying dataset, stakeholders are going to use it to add value. Stakers signal curation by investigating the behavior of the power producing device as inferred by EnergyWeb EACs (and the claims thereof), but also by relying on other stakeholders like Auditors verifying metered data with sell orders in EnergyWeb Exchange and Optimizers making power production forecasts based on this metered data and possibly other datatoken pools having weather history and forecast datasets. For a detailed interplay between these stakeholders, see our documentation.

The output of 3. is accomplished by using an energyweb branch of the tokenspice2 simulation model looking primarily at the effects of the Optimizer.