Bertrand Rioux

This issue resolved in PR referenced above

@sichen1234 Yes. The only question I have is how emissions would be distributed among Sempra's products, electricity and natural gas. A CarbonTracker is issued unitless product tokens that determine the...

@sichen1234 the order of magnitude difference between reported and calculated scope 1 may be because of differences in generation tech, assuming they use a lot of low carbon infrastructure... Have...

@sichen1234 thanks for the suggestions I am taking these into consideration as I finalize the integration of the tracker with of the methane react-app.

@sichen1234 With regards to the above, several of these are already covered by the contract > 1. The CarbonTracker should have some additional fields: > * an amountUsed in addition...

@Sichen, first response to your questions from last week. - Regarding the User vs. Producer product amounts. Their are two different entities for tracking products: - [ProductDetails amount stored within...

@sichen1234 Regarding the second use case, emissions issued from a carbon tracker : consumers receive products issued to an audited carbon tracker. They tell the consumer exactly how many embodied...

There are two ways to do this. 1. In the transaction where emissions are derived from an existing product, both are used as inputs to a new carbon tracker, linking...

In the second case custom instructions are needed to track emissions to the previous contract. I.e., standardize protocol for reading the carbon tracker address and product Ids from the NET...

The approach adopted in [PR 616](https://github.com/hyperledger-labs/blockchain-carbon-accounting/pull/616) was to introduce a new oracle api into the chaincode, rather than an explicit connection to the existing rest API. The oracle can then...