Summary
A real peer programming session! We fixed a couple of bad links on this wiki during the call.
Bertrand WILLIAMSRIOUX fixed some more bugs and made this demo video:
In summary, the steps are:
As emissions auditor, go to Track tab. Click on Create certificate. Create an audited emissions from the auditor to the utility. This creates an audited emissions token.
Now select "Emissions Certificates: requested". You can add product details, such as kWH or therms. You can add more emissions, such as other sources of emissions.
When you're done, click on Issue to issue the certificate.
Next, as the utility, go to the Track tab. You will see your product certificates. Click on Transfer to transfer it to building owners.
Finally, follow the example from 2022-11-21 Peer Programming Call, as the Building owner, create a certificate to transfer it to your tenant.
Time:
- Monday December 5, 2022 at 09 AM Pacific
- Add Climate Action and Accounting SIG calls to your calendar
Dial-In Information: [ZOOM]
You can join either from your computer or from your phone:
- From computer: https://zoom.us/j/6223336701?pwd=dkJKdHRlc3dNZEdKR1JYdW40R2pDUT09
- From phone: +1(855)880-1246 (toll free US number) or view International numbers
Meeting ID: 622 333 6701
Hyperledger is committed to creating a safe and welcoming community for all. For more information please visit the Hyperledger Code of Conduct. |
---|
9 Comments
Si Chen
Bertrand WILLIAMSRIOUX I tried to follow your steps here
But only an audited emissions certificate was created. It does not show up under the "Track" tab.
Bertrand WILLIAMSRIOUX
I’m also not seeing the tokens with the “I requested” drop down option.
But the certificate should appear when selecting the “Requested” option.
Bertrand WILLIAMSRIOUX
"I requested" is not displaying anything because the issuedFrom address recorded in the tracker token was stored as the NET contract address, the operator of the CarbonTracker.track() function.
You can check this in the tracker PG table. issuedFrom should equal "0x2279b7a0a67db372996a5fab50d91eaa73d2ebe6" and not the auditor's address.
I'll fix this by setting the issuedFrom address as tx.origin instead of msg.sender.
Si Chen
Is this correct?
Si Chen
I tried both of these and there is still nothing in the Track tab
0x610178dA211FEF7D417bC0e6FeD39F05609AD788 is the carbon tracker address. 0x2279b7a0a67db372996a5fab50d91eaa73d2ebe6 is the net emisisions token network:
Bertrand WILLIAMSRIOUX
Is the PG tracker table being synched? If it is also empty then there is an issue in the api-server.
Bertrand WILLIAMSRIOUX
hardhat should show the following after sending the issueAndTrack function with this form
The eth_call follwoing the transaction verify that the api-server is synching to the ledger
Bertrand WILLIAMSRIOUX
Also make sure you add to .env LEDGER_CARBON_TRACKER_ADDRESS="0x610178dA211FEF7D417bC0e6FeD39F05609AD788"
As listed in .env.SAMPLE. The api-server uses this to synchronize.
Si Chen
I checked it again and posted the results on a github issue. See https://github.com/hyperledger-labs/blockchain-carbon-accounting/issues/661