Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

We propose to implement a carbon emissions token based on the eThaler project from the CMSIG.  eThaler is a Central Bank Digital Currency (CBDC) implemented on a private Ethereum network running Hyperledger Besu.  It supports a central bank which creates and mints tokens and transfers them to member banks, who would then distribute them to retail customers of the banks.  In the case of carbon emissions, it could support a registry authority, which could be a network operator or supranational/national/regional carbon authority, which authorizes a number of issuers of tokens.  The issuers could be auditors of carbon emissions or project developers of renewable energy or carbon offsets, who issue tokens based on audits of companies' or projects' operations.  eThaler's features can be mapped to emissions tokens like this:

Token Types

  • Emissions audit - represents the actual emissions of an organization, as reported by an auditor.
  • Carbon offsets - represents reduction of emissions through projects such as forestry, sequestration, etc.
  • Renewable Energy Certificates (REC's) - represents energy generated from renewable sources such as wind and solar 

Token Operations

  • Add new token definition – Multiple types of emissions tokens can be supported on the network, such as emissions, Renewable Energy Certificates (REC's), and offsets.
  • Mint – Authorizes a supply of tokens to be issued in the future, based on results of operations from audited companies and renewable/offsets projects.
  • Register/Unregister dealer – In our case, it would be registering and unregistering auditors or project developers authorized to issue tokens.
  • Transfer – In eThaler, the central bank transfers tokens to dealer banks.  In our case, we would allow an auditor or project developer to create a token based on audited results and then transfer it to a party, which could be a business or individual.  After that, the token would be flagged as "used" Emissions audit tokens cannot be transferred: They stay with the organization that was audited as a record of their emissions.  Offsets and REC's can be transferred until they are retired.
  • Retire - this is not in eThaler but would need to be implemented.  When a token is marked as "retired," it is counted towards the emissions reduction of the retiring organization and cannot be transferred again. 
  • Burn – this would not be implemented.

...

  • Renewable Energy Certificate:
    • Issuer ID = Generator of REC
    • Recipient ID = Buyer of REC
    • Asset Type = REC
    • Quantity = 1
    • UOM = MWH
    • From/thru date time stamp = do we need this for REC's?
    • Metadata = Region and Time of energy enerated
    • Manifest = URL linking to the registration for the REC purchased
  • Carbon emissions offest:
    • Issuer ID = Certifier or Issuer
    • Recipient ID = Buyer
    • Asset Type = Emissions Offset
    • Quantity = amount
    • UOM = MtCO2e
    • From/thru date time stamp = do we need this for emissions offset?
    • Metadata = type of project, location, etc.
    • Manifest = URL linking to the registration of the emissions offset
  • Utility Emissions DataAudit:
    • Issuer ID = utility or auditor Recipient ID = organization or entity
    • Asset Type = CO2 emissions
    • Quantity = amount of emissions
    • UOM = MtCO2e
    • From/thru date time stamp = time period of the net emissions
    • Meatadata = background data such as utility, billing period, amount and UOM of usage, etc.
    • Manifest = link to access the utility emissions data on the utility emissions channel 
    Net Emissions Data:
    • Issuer ID = auditor
    • Recipient ID = organization or entity
    • Asset Type = CO2 emissions
    • Quantity = amount of emissions
    • UOM = MtCO2e
    • Metadata =
    • From/thru date time stamp = time period of the net emissions
    • Manifest = links to access all the emissions tokens/assets used to prepare this net emissions

...

An auditor could issue tokens to the customer of a recipient by referencing the recipient's token in a newly issued token, thus passing emissions down the supply chain.  

With these tokens, we can calculate the net emissions by first subtracting the effect of Renewable Energy Certificates (REC's.)  REC's offset the energy produced by non-renewable sources, so we'll need to get the non-renewable vs renewable energy mix in the original emissions tokens/assets from utility emissions data channel.  Then we subtract the offsets to get the net emissions.

How to avoid double counting: My emissions are mine.  I cannot transfer them to someone else.  But if you hire me to do some work for you, a portion of my emissions should also be part of your responsbility.  Does that mean my emissions should be reduced and yours increased?  Not if you only contact my total emissions, but yes if you count the total emissions from both of us.  So rather than a simple transfer between two parties, inter-party emissions should be cancelled when they are summed up in calculations that involve both parties.

Outstanding Issues

Transfer of emissions down the supply chain and avoiding double counting are major issues to be addressed.Image Removed