Skip to content

Latest commit

 

History

History
57 lines (42 loc) · 3.16 KB

0004-FGTP-Content-Address-EACs.md

File metadata and controls

57 lines (42 loc) · 3.16 KB
FGTP title status original author created
0004
Content address EACs
Proposed
redransil
2022-03-31

Title

Content address EACs

Abstract

Data for EACs is currently tracked in several places, including in the EAC Summary Archive and the Zero Labs system.

We'd like to take all of the relevant data, including certifictes, and track it with IPDL.

Authors

redransil

Status

Proposed

What is the goal

Build Web3-native tools to assign CIDs to renewable energy certificates and the metadata mapping from them to SPs.

This should live, at least for now, in the filecoin-renewables-purchases repo.

What are the inputs

  • Spreadsheet with renewable energy information
  • Certificates outputted from the registry; pdfs

Example #1: Zero Labs REC tracker for EACs already in the system. This is a private sheet, let us know if you need access to this or a copy. Example #2: Order sheet, which we are expecting to come back with pdfs soon

What are the outputs

IPLD data stored on Estuary which tracks pdf certificates and associated metadata.

Metadat should include, at least, all of the information returned by a transaction call to the ZL API

Proposed Solution

  • The pdf certificate should be stored on Estuary and have its own CID: example
  • An object should hold a link to the pdf and metadata for each line in the EAC pdf. Each certificate will have at least one line. For example, the above I-REC has only one, this certificate has one and this certificate has 24.
  • Each transaction, mapping renewable energy to a minerID - for example an item in the array here which corresponds to an entry here, should have its own CID and a bidirectional link to the corresponding line in the CID pdf.
  • There should be a tool to validate that when you follow from certificate->line->transaction and add all of the transactions, sum(transactions) <= the total on the certificate

Implementations and Artifacts

If you have built a version of this tool, link to it here as an implementation. If you have given a talk, published a paper or created other artifacts about this tool, link to them here.

Relevant Background

What publications, projects, or companies are relevant to this tool, and would provide useful information for someone working to implement it?