Merging develop into main for 2.23 release (#3405)

* fix filebase

Signed-off-by: simvalery <valeriy.simonov@envisionblockchain.com>

* fix filebase validation

Signed-off-by: simvalery <valeriy.simonov@envisionblockchain.com>

* fix lint

Signed-off-by: simvalery <valeriy.simonov@envisionblockchain.com>

* fix

Signed-off-by: simvalery <valeriy.simonov@envisionblockchain.com>

* fix

Signed-off-by: simvalery <valeriy.simonov@envisionblockchain.com>

* fix serialize schema

Signed-off-by: Stepan Kiryakov <stepan.kiryakov@envisionblockchain.com>

* GITBOOK-115: Updated Frameworks

* GITBOOK-116: Added Auto Suggestion images

* GITBOOK-117: Example data screens updated

* Update readme.md of AMS-III.AV

* Add files via upload

* GITBOOK-118: policy diff screens corrected

* fix destroy worker client

Signed-off-by: artembuslaev <artem.buslaev@envisionblockchain.com>

* tests fixes and enchancement

* fixes for tests and reporters

* test check fix

* small fixes for tokens tests

* GITBOOK-119: Added AMS-I.D guide

* Create readme.md of AMS-I.D

* add expected tokens count

Signed-off-by: simvalery <valeriy.simonov@envisionblockchain.com>

* api tests scheduler

Signed-off-by: simvalery <valeriy.simonov@envisionblockchain.com>

* fix pipeline and generation test data

Signed-off-by: simvalery <valeriy.simonov@envisionblockchain.com>

* bump version

Signed-off-by: simvalery <valeriy.simonov@envisionblockchain.com>

* [skip ci] Add swagger.yaml

* GITBOOK-120: AMS-III.F Guide added

* GITBOOK-121: Updated demo link

* fix verification schema

Signed-off-by: Stepan Kiryakov <stepan.kiryakov@envisionblockchain.com>

* GITBOOK-122: Added AMS-III.H Demo guide

* Update readme.md of AMS-III.H

* Update readme.md of AMS-III.F

* GITBOOK-123: Added note for calculateMathAddonblock

* GITBOOK-124: Added table for CalculateMathAddoonblock

* Add files via upload

* GITBOOK-125: ACM0002 Demo guide added

* Update readme.md of ACM0002

* Add files via upload

* Add files via upload

* Add files via upload

* Add files via upload

* Add files via upload

* Add files via upload

* Add files via upload

* Add files via upload

* Add files via upload

* Add files via upload

* Add files via upload

* Add files via upload

* Update readme.md

* GITBOOK-126: Added descriptions

* GITBOOK-127: added pre build containers

* Update readme.md of ACM0006

* upload i.d policy [skip ci]

Signed-off-by: Artem Buslaev <artem.buslaev@envisionblockchain.com>

* Update readme.md of ACM0007

* Update readme.md of AMS-I.D

* Update readMe.md of AMS-II.G

* Update readme.md of CDM-III.AR

* Update readme.md of AMS III.BB

* Update readme.md of AMS-III.D

* Update readme.md of AMS-III.D

* Update readme.md of AMS-III.F

* Update readme.md of AMS-III.H

* Create readme.md of Tools

* Update readme.md of AMS-II.J

* Update readme.md of ACM0002

* Update readme.md of ACM0001

* Update readme.md of Tools

* Create readme.md of Tool 7

* Update readme.md of AMS-II.J

* Create readme.md of Tool 1

* Create readme.md of Tool 2

* Create readme.md of Tool 3

* Create readme.md of Tool 4

* Create readme.md of Tool 5

* Create readme.md of Tool 6

* Create readme.md of Tool 8

* Create readme.md of Tool 9

* Create readme.md of Tool 10

* Create readme.md of tool 12

* Create readme.md of Tool 32

* Update readme.md of ACM0001

* Updated worker-service to use replicas; updated external dependencies;

Signed-off-by: Giuseppe Bertone <giuseppe.bertone@swirldslabs.com>

* Create readme.md of Tool 13

* Create readme.md of Tool 14

* Create readme.md of Tool 16

* Create readme.md of Tool 19

* Create readme.md of Tool 21

* Create readme.md of Tool 22

* Create readme.md of Tool 30

* Create readme.md of Tool 33

* Update readme.md of Tool 13

* Update readme.md of Tool 14

* Update readme.md of Tool 16

* Update readme.md of Tool 19

* Update readme.md of Tool 21

* Update readme.md of Tool 22

* Update readme.md of Tool 30

* Update readme.md of Tool 32

* Update readme.md of Tool 33

* Update readme.md of ACM0002

* Update readme.md of ACM0006

* Update readme.md of ACM0007

* Update readme.md of ACM0018

* Update readme.md of AMS-I.A

* Update readme.md of AMS-I.C

* Update readme.md of AMS-I.D

* Update readme.md of AMS-I.F

* Update readMe.md of AMS-II.G

* Update readme.md of AMS-III.AR

* Update readme.md of AMS-III.AV

* Update readme.md of AMS-III.BB

* Update readme.md of AMS-III.D

* Update readme.md of AMS-III.F

* Update readme.md of AMS-III.H

* GITBOOK-128: updated screens of BYOD

* Create readme.md of Tool 11

* Update readme.md of ACM0018

* Update readme.md of Tools with Timestamps

* Add files via upload

* Add files via upload

* fix tools naming

Signed-off-by: simvalery <valeriy.simonov@envisionblockchain.com>

* Update readme.md of ACM0001

* Update readme.md of ACM0002

* Update readme.md of ACM0006

* Update readme.md of ACM0007

* Update readme.md of ACM0018

* Update readme.md of AMS-I.A

* Update readme.md of AMS-I.C

* Update readme.md of AMS-I.D

* Update readme.md of AMS-I.F

* Update readme.md of AMS-II.J

* Update readme.md of III.AR

* Update readme.md of AMS-III.AV

* Update readme.md of AMS-III.BB

* Update readme.md of III.D

* Update readme.md of III.F

* Update readme.md of III.H

* GITBOOK-129: Added AMS-III.D Guide

* GITBOOK-130: Added demo link for AMS-III.D

* Update readme.md of AMS-III.D

* Create readme.md of Verra Tools

* Update readme.md of Verra Tools

* GITBOOK-131: Added Demo link for BYOD

* GITBOOK-132: Added flow to BYOD

* fix schema form view

Signed-off-by: artembuslaev <artem.buslaev@envisionblockchain.com>

* renaming, refactoring and accounts api test updating

* GITBOOK-133: Updated Topics mapping architecture

* added tests for analytics

* provide CI creds to API tests

* provide CI creds to API tests

* added tests for analytics

* Update README.md

This commit introduces a minor but important adjustment in the README documentation to enhance clarity regarding service updates. Specifically, we have moved the note about the web3.storage upload API sunsetting to a new, separate line below the list of account setup links. This change ensures there is no confusion that the sunsetting of the upload API is related specifically to Filebase. The intention is to clearly differentiate between the services listed and the general update about web3.storage's API transition.

* update tests and add new workflow

* Update api-manual.yml

* Update api-manual.yml

* fixed tests and updating cypress version

* update CI pipeline for manual run

* upd vm0044 [skip ci]

Signed-off-by: artembuslaev <artem.buslaev@envisionblockchain.com>

* fix import schemas

Signed-off-by: Stepan Kiryakov <stepan.kiryakov@envisionblockchain.com>

* fix import schemas

Signed-off-by: Stepan Kiryakov <stepan.kiryakov@envisionblockchain.com>

* upload pwrm0002 [skip ci]

Signed-off-by: artembuslaev <artem.buslaev@envisionblockchain.com>

* fix 3237

Signed-off-by: simvalery <valeriy.simonov@envisionblockchain.com>

* fix 3202

Signed-off-by: simvalery <valeriy.simonov@envisionblockchain.com>

* fix OPENAI_API_KEY validation

Signed-off-by: simvalery <valeriy.simonov@envisionblockchain.com>

* remove ai-service deps

Signed-off-by: simvalery <valeriy.simonov@envisionblockchain.com>

* disable creation of tool schema without tool selected

Signed-off-by: simvalery <valeriy.simonov@envisionblockchain.com>

* rename ai-service config files

Signed-off-by: simvalery <valeriy.simonov@envisionblockchain.com>

* fix service error while scaling

Signed-off-by: simvalery <valeriy.simonov@envisionblockchain.com>

* update pwrm0002 [skip ci]

Signed-off-by: artembuslaev <artem.buslaev@envisionblockchain.com>

* update mint

Signed-off-by: artembuslaev <artem.buslaev@envisionblockchain.com>

* added multiple property to compare

Signed-off-by: artembuslaev <artem.buslaev@envisionblockchain.com>

* fix

Signed-off-by: artembuslaev <artem.buslaev@envisionblockchain.com>

* fix lint

Signed-off-by: artembuslaev <artem.buslaev@envisionblockchain.com>

* changed name for exporting policy, tools, modules

Signed-off-by: artembuslaev <artem.buslaev@envisionblockchain.com>

* dynamic token dialog

Signed-off-by: artembuslaev <artem.buslaev@envisionblockchain.com>

* fix

Signed-off-by: artembuslaev <artem.buslaev@envisionblockchain.com>

* fix

Signed-off-by: artembuslaev <artem.buslaev@envisionblockchain.com>

* fix env setting validation

Signed-off-by: artembuslaev <artem.buslaev@envisionblockchain.com>

* fix

Signed-off-by: artembuslaev <artem.buslaev@envisionblockchain.com>

* update token dialog

Signed-off-by: artembuslaev <artem.buslaev@envisionblockchain.com>

* change export schema name

Signed-off-by: artembuslaev <artem.buslaev@envisionblockchain.com>

* fix

Signed-off-by: artembuslaev <artem.buslaev@envisionblockchain.com>

* fix

Signed-off-by: artembuslaev <artem.buslaev@envisionblockchain.com>

* remove console log

Signed-off-by: artembuslaev <artem.buslaev@envisionblockchain.com>

* added displaying transfer token

Signed-off-by: artembuslaev <artem.buslaev@envisionblockchain.com>

* fix error handling in mint block

Signed-off-by: artembuslaev <artem.buslaev@envisionblockchain.com>

* fix notification reciever

Signed-off-by: artembuslaev <artem.buslaev@envisionblockchain.com>

* fix notifications clicking

Signed-off-by: artembuslaev <artem.buslaev@envisionblockchain.com>

* added retry interval

Signed-off-by: artembuslaev <artem.buslaev@envisionblockchain.com>

* fix

Signed-off-by: artembuslaev <artem.buslaev@envisionblockchain.com>

* change name for env variable

Signed-off-by: artembuslaev <artem.buslaev@envisionblockchain.com>

* fix timeout error

Signed-off-by: artembuslaev <artem.buslaev@envisionblockchain.com>

* fix resolving nft mint transactions

Signed-off-by: artembuslaev <artem.buslaev@envisionblockchain.com>

* fix multi policy mint

Signed-off-by: artembuslaev <artem.buslaev@envisionblockchain.com>

* change notification order

Signed-off-by: artembuslaev <artem.buslaev@envisionblockchain.com>

* added check for amount

Signed-off-by: artembuslaev <artem.buslaev@envisionblockchain.com>

* update setting env variables

Signed-off-by: artembuslaev <artem.buslaev@envisionblockchain.com>

* fix transactions serials amount

Signed-off-by: artembuslaev <artem.buslaev@envisionblockchain.com>

* fix

Signed-off-by: artembuslaev <artem.buslaev@envisionblockchain.com>

* fix mint errors

Signed-off-by: artembuslaev <artem.buslaev@envisionblockchain.com>

* fix typo [skip ci]

Signed-off-by: artembuslaev <artem.buslaev@envisionblockchain.com>

* fix transfer amount

Signed-off-by: artembuslaev <artem.buslaev@envisionblockchain.com>

* added irec 4 retry mint policy [skip ci]

Signed-off-by: artembuslaev <artem.buslaev@envisionblockchain.com>

* fix Nobinding schema error
disable creation of schema without policy binded

Signed-off-by: simvalery <valeriy.simonov@envisionblockchain.com>

* enable creation of schema without policy binded

Signed-off-by: simvalery <valeriy.simonov@envisionblockchain.com>

* disable policy dropdown for editing schemas

Signed-off-by: simvalery <valeriy.simonov@envisionblockchain.com>

* fix image upload bug

Signed-off-by: simvalery <valeriy.simonov@envisionblockchain.com>

* fix image upload bug

Signed-off-by: simvalery <valeriy.simonov@envisionblockchain.com>

* load images into database in dryRun mode

Signed-off-by: simvalery <valeriy.simonov@envisionblockchain.com>

* [skip ci] Add swagger.yaml

* remove console.log

Signed-off-by: simvalery <valeriy.simonov@envisionblockchain.com>

* GITBOOK-134: Added PWRM0002 Demo guide

* GITBOOK-135: 3311 ticket changes updated

* Create Readme.md of PWRM0002

* Update timestamps of Tool 13, 14 16

* Create readme.md of Hackathon

* Add files via upload

* fix file upload issue
fix clear dry run files

Signed-off-by: simvalery <valeriy.simonov@envisionblockchain.com>

* apply only image upload

Signed-off-by: simvalery <valeriy.simonov@envisionblockchain.com>

* fix draft schemas in wisard

Signed-off-by: simvalery <valeriy.simonov@envisionblockchain.com>

* fix amount

Signed-off-by: artembuslaev <artem.buslaev@envisionblockchain.com>

* fix

Signed-off-by: artembuslaev <artem.buslaev@envisionblockchain.com>

* use global common and interfaces modules

Signed-off-by: simvalery <valeriy.simonov@envisionblockchain.com>

* Add files via upload

* bump version

Signed-off-by: simvalery <valeriy.simonov@envisionblockchain.com>

* [skip ci] Add swagger.yaml

* increase timeout for import tool

---------

Signed-off-by: simvalery <valeriy.simonov@envisionblockchain.com>
Signed-off-by: Stepan Kiryakov <stepan.kiryakov@envisionblockchain.com>
Signed-off-by: artembuslaev <artem.buslaev@envisionblockchain.com>
Signed-off-by: Artem Buslaev <artem.buslaev@envisionblockchain.com>
Signed-off-by: Giuseppe Bertone <giuseppe.bertone@swirldslabs.com>
Co-authored-by: Stepan Kiryakov <stepan.kiryakov@envisionblockchain.com>
Co-authored-by: prernaa.agarwal <prernaa.agarwal@envisionblockchain.com>
Co-authored-by: artembuslaev <artem.buslaev@envisionblockchain.com>
Co-authored-by: Celiant <nikita.nikishin@envisionblockchain.com>
Co-authored-by: envision-ci-agent <envision-ci-agent@users.noreply.github.com>
Co-authored-by: Giuseppe Bertone <giuseppe.bertone@swirldslabs.com>
Co-authored-by: Kichen <kichen1984@live.com>

Methodology Library/CDM/CDM ACM0018/readme.md

@@ -56,7 +56,7 @@ ACM0018 is a Clean Development Mechanism (CDM) methodology designed to support c
 
 **[Methodological Tool 10](https://github.com/hashgraph/guardian/blob/main/Methodology%20Library/CDM/Tools/Tool%2010/readme.md)** – Tool to determine the remaining lifetime of equipment. 
 
-**[Methodological Tool 11]()** - Assessment of the validity of the original/current baseline and update of the baseline at the renewal of the crediting period. 
+**[Methodological Tool 11](https://github.com/hashgraph/guardian/blob/main/Methodology%20Library/CDM/Tools/Tool%2011/readme.md)** - Assessment of the validity of the original/current baseline and update of the baseline at the renewal of the crediting period. 
 
 **[Methodological Tool 12](https://github.com/hashgraph/guardian/blob/main/Methodology%20Library/CDM/Tools/Tool%2012/readme.md)** - Project and leakage emissions from transportation of freight. 
 

Methodology Library/CDM/CDM AMS-III.D/readme.md

@@ -80,94 +80,117 @@ Certified Emission Reduction (CER) credits, each equivalent to one tonne of CO2.
 
 ### Step By Step 
 
-1. The policy can be imported using IPFS timestamp 1698756329.359347003
+1. Log in as the Standard Registry and import the policy either by file or through IPFS timestamp by selecting the third button at the top right. As the policy is importing you can see the schemas, tools, and tokens importing.
 
-   <img width="800" alt="image" src="https://github.com/hashgraph/guardian/assets/79293833/ec89168d-8020-47da-8322-df0ce7b0cf08">
+![image](https://github.com/hashgraph/guardian/assets/79293833/58557a8d-8a56-4375-a66e-eb4f2784988a)
 
-2. Select “Import”.
+![image](https://github.com/hashgraph/guardian/assets/79293833/0c0933de-7683-4f50-893b-a3d80311fe41)
 
-   <img width="800" alt="image" src="https://github.com/hashgraph/guardian/assets/79293833/f3067523-ac2c-4b5a-913f-4169e3616bd9">
+![image](https://github.com/hashgraph/guardian/assets/79293833/17a364a9-53dc-4c0a-ae5c-dc081ff5b629)
 
-3. Place status in “Dry Run” and select “Go”.
+2. By clicking on the pen icon, we can open the policy configurator to see the workflow blocks. To expand the containers, click on the dropdown arrow, we’ll then see where the tools are located, like tool 14 in the AMS-III.D policy. Then we can click on the block for tool 14 and scroll down in the properties section at the bottom right of the page this is where we can find the message ID for this tool.
 
-   <img width="800" alt="image" src="https://github.com/hashgraph/guardian/assets/79293833/dda9204b-cd94-4366-9ce5-d2369dc63c3a">
+![image](https://github.com/hashgraph/guardian/assets/79293833/354b8a81-96e6-4e94-b1c4-2a12b1ebd0dd)
 
-4. By selecting the edit button in the operations tab, you can access the policy configurator and view the workflow blocks.   
+![image](https://github.com/hashgraph/guardian/assets/79293833/893d857c-97d8-4058-abc7-d48478187934)
 
-   <img width="800" alt="image" src="https://github.com/hashgraph/guardian/assets/79293833/2c75d4b8-6e82-4d13-880e-d7ab339c8882">
+![image](https://github.com/hashgraph/guardian/assets/79293833/3938b474-4fd8-4eea-a56b-15d71f2aae25)
 
-5. Going back to the policy workflow, add users by selecting the “create user” button. Then select the dropdown user menu and select “Virtual User 1”.
+![image](https://github.com/hashgraph/guardian/assets/79293833/02a4c7cb-9006-406d-bd09-ec9771406a9c)
 
-   <img width="800" alt="image" src="https://github.com/hashgraph/guardian/assets/79293833/e710bb25-44c9-4b60-bacc-7d2f8a92c73e">
+3. To start using the policy you first have to change the status of the policy from “Draft” to “Dry Run” or “Publish”, then select the “Register” button.
 
-6. Virtual User 1 will be assigned to the Project_Proponent
+![image](https://github.com/hashgraph/guardian/assets/79293833/2346308f-c92c-49ae-8b76-954883a55b71)
 
-   <img width="800" alt="image" src="https://github.com/hashgraph/guardian/assets/79293833/1e8cd70d-68ba-436e-a5e5-4d7bd58dac02">
-
-7. Virtual User 2 will be assigned to the VVB  
+![image](https://github.com/hashgraph/guardian/assets/79293833/c0d60a85-f942-4243-a58b-ccde0e759cb9)
 
-   <img width="800" alt="image" src="https://github.com/hashgraph/guardian/assets/79293833/575c4df1-b298-4d51-bf18-97b6cf341ea0">
+4. Create a new user by clicking the “Create User” button and assign their role as Project Participant.
 
-8.	Add the VVBs name 
-
-   <img width="800" alt="image" src="https://github.com/hashgraph/guardian/assets/79293833/e0a94a7e-a771-4ed8-a7dd-57ac85449144">
-
-9.  The final role that will be assigned to Virtual User 3 is the Designated National Authority
+![image](https://github.com/hashgraph/guardian/assets/79293833/4d19ca9f-b83f-45e8-9c20-3a7d159c7952)
+
+5. The Project Participant can now provide their name or the name they would like to see reflect when registering for this project (i.e. their organization’s name).
+
+![image](https://github.com/hashgraph/guardian/assets/79293833/74fd003c-ed9d-447d-9202-9afe928a2a63)
+
+6. Сreate a new user again and assign their role as VVB.
+
+![image](https://github.com/hashgraph/guardian/assets/79293833/d719b890-05d4-46a0-a290-d981428dcf29)
+
+7. The VVB can now provide their name or the name they would like users to see when reviewing projects (i.e. their organization’s name).
+
+![image](https://github.com/hashgraph/guardian/assets/79293833/dc0fb6f4-6ffa-402a-b95d-819e33d543b1)
+
+8. Log in as the SR and select the “Project Participants” or the “VVBs” tab to view the documents submitted by the Project Participant and by the VVB. The SR can approve their requests by clicking on the “Approve" button.
+
+![image](https://github.com/hashgraph/guardian/assets/79293833/dd5b22f1-b993-46a1-9fd3-f5f6a6b51381)
+
+![image](https://github.com/hashgraph/guardian/assets/79293833/8916d689-fb15-45c5-99d1-97ae0ae6efb0)
+
+9. Log in as the Project Participant and create a new project by clicking on the "New Project" button. This form is used to collect information about the project, organization, and all the data needed to run the emission reduction calculations. Once all the required fields have been filled the “Create” button will turn dark blue. By selecting the “Create” button all the data will be sent to the SR for review/approval.
+
+![image](https://github.com/hashgraph/guardian/assets/79293833/ed2bbad8-5e41-433d-bd0a-9ded04f970af)
+
+![image](https://github.com/hashgraph/guardian/assets/79293833/31f97be2-a85c-4e98-b133-41de38d5008f)
+
+10. Log back in as the SR and after reviewing the document by selecting the “View Document” button, the SR can validate the project submitted by the Project Participant by clicking the “Validate” button. If the data does not satisfy the rules set by the SR, then the “Reject” button can be used.
+
+![image](https://github.com/hashgraph/guardian/assets/79293833/6489d38d-b60b-44d4-bad3-e6811fc2fac7)
+
+![image](https://github.com/hashgraph/guardian/assets/79293833/bf455ef2-0bc5-4b87-9094-5e88087b791e)
+
+11. Log in as the Project Participant and create a monitoring report by clicking on the “Add Report” button then fill out the monitoring report form.
+
+![image](https://github.com/hashgraph/guardian/assets/79293833/40b2dc5c-57bc-423e-b33d-52a4b8bf6dbd)
+
+![image](https://github.com/hashgraph/guardian/assets/79293833/fb10431f-213a-4212-baa5-4cb856c43462)
+
+12. After creating the monitoring report, the project participant assigns the VVB to verify it by navigating to the “Monitoring Reports” tab and selecting the dropdown under “Assign”.
+
+![image](https://github.com/hashgraph/guardian/assets/79293833/f03ed650-9892-43d8-ad9f-0b6437cb573a)
+
+13. Log in as the VVB and click the “Monitoring Reports” tab to review the document submitted by the Project Participant. After reviewing the monitoring report by selecting “View Document”, the VVB can select “Verify”.
+
+![image](https://github.com/hashgraph/guardian/assets/79293833/79768f2a-ca48-4c53-98f7-1f942cdeecdf)
+
+![image](https://github.com/hashgraph/guardian/assets/79293833/4e018b1f-5eb4-49bc-9c45-7763c27bcaed)
+
+14. Log in as the SR to review the monitoring report by selecting the “View Document” button in the “Monitoring Reports” tab. The SR can approve the monitoring report by selecting “Approve”. This will also trigger the minting process. You can see the minting status under “Status” change from “Minting” to “Minted”.
+
+![image](https://github.com/hashgraph/guardian/assets/79293833/1614299f-e797-489b-8095-82a37cae35b0)
+
+15. Once the minting process is completed, you can view the token amount by selecting the “VP” tab.
+
+![image](https://github.com/hashgraph/guardian/assets/79293833/a9e0ef55-ffe1-42c6-a0f0-3e9b2485f35f)
+
+16. The TrustChain can also be viewed by clicking on the “View TrustChain” button. Please note that the token amount may show “-1” when the tokens are still minting. Once the process is complete a notification will appear stating that the tokens have been minted and transferred.
+
+![image](https://github.com/hashgraph/guardian/assets/79293833/4de00af5-fbe4-451b-b1d9-e72cd903c86b)
+
+![image](https://github.com/hashgraph/guardian/assets/79293833/504ee3f0-a26e-44ec-9b68-df912a2fb7f2)
 
-   <img width="800" alt="image" src="https://github.com/hashgraph/guardian/assets/79293833/037d8386-a61a-4731-b572-dd31e3e4201e"> 
-
-10. Go to the Administrator’s (Standard Registry) profile. The Standard Registry can now approve the VVB.
 
-   <img width="800" alt="image" src="https://github.com/hashgraph/guardian/assets/79293833/552fe67c-3772-4de5-a5c4-8bb8a81ebaab">
 
-11. Click on the Users dropdown menu and select Virtual User 1 (Project Proponent) and select the “New Project” button.
 
-   <img width="800" alt="image" src="https://github.com/hashgraph/guardian/assets/79293833/da3e4c74-c983-48f3-b1c6-2a0d37d14e6a">
 
-12. Once the form is completed, go to Virtual User 3’s (Designated National Authority) profile. The Designated National Authority can now view the project information document by selecting “view document” and then they can select validate or reject.
 
-   <img width="800" alt="image" src="https://github.com/hashgraph/guardian/assets/79293833/05412bf4-0caa-4b93-b083-137886ac4d45">
 
-13. Return to the Administrator’s (Standard Registry) profile. The Standard Registry now has access to the project information document by clicking “view document” once they have reviewed it they can select “Add” to add the project to the project pipeline.
 
-   <img width="800" alt="image" src="https://github.com/hashgraph/guardian/assets/79293833/1907b148-6397-4295-a9f9-ae567f92d1e6">
 
-14. Navigate back to Virtual User 1’s (Project Proponent) profile and assign the VVB.
 
-   <img width="800" alt="image" src="https://github.com/hashgraph/guardian/assets/79293833/56574c63-7e4b-4425-94bc-ce6223409d15">
 
-15. Go to the VVB profile and select the “Project” tab. The VVB can now see all the information submitted by the Project Proponent. Once the document has been reviewed the VVB will select Approve or Reject.
 
-  <img width="800" alt="image" src="https://github.com/hashgraph/guardian/assets/79293833/7e290a3e-a9f8-4555-b396-358387a971f3">
-
-16. Navigate back to the Administrator. For this workflow step the Standard Registry reviews the document and adds the project to the project pipeline. Select Add.
 
-  <img width="800" alt="image" src="https://github.com/hashgraph/guardian/assets/79293833/b00f88da-0bba-42e0-a6cc-a1bb3f51b8e0">
 
-17. Navigate back to Virtual User 1’s (Project Proponent) profile and select “Add Report”.
 
-   <img width="800" alt="image" src="https://github.com/hashgraph/guardian/assets/79293833/3efecee6-8654-4c03-9f3b-1ce929410a6d">
 
-18. Go to the Virtual User 2’s (VVB) profile. The VVB has access to the monitoring report form by selecting “View Document”. Then the VVB can select Verify or Reject.
 
-    <img width="800" alt="image" src="https://github.com/hashgraph/guardian/assets/79293833/15d3b8bb-ef52-4c0f-ad0c-5f41c0b5675f">
 
-19. Navigate back to the Administrator’s profile and select the “Mint” button.
 
-    <img width="800" alt="image" src="https://github.com/hashgraph/guardian/assets/79293833/14d8c331-ebdd-455f-9511-50cb584f22fe">
 
-20. The status should now say “Minted”.
 
-    <img width="800" alt="image" src="https://github.com/hashgraph/guardian/assets/79293833/60b0e9b2-45ab-413e-9e5a-cf7cde0dad88">
 
-21. By selecting the “Token History” tab you can see the number of tokens minted and then you can select “View TrustChain”
 
-    <img width="800" alt="image" src="https://github.com/hashgraph/guardian/assets/79293833/053294c6-ff74-4916-9fda-c2d0e9853044">
 
-22. The Verifiable Presentation should now be open. You can view information like the recipient's name, token amount, mint date, verified signature, etc. This example resulted in 0 tokens minted due to the demo values used.
 
-    <img width="800" alt="image" src="https://github.com/hashgraph/guardian/assets/79293833/43aae129-0541-4108-afc0-c01fb055d5d5">
 
-23. By scrolling to the bottom of the page you can view the TrustChain.
 
-    <img width="800" alt="image" src="https://github.com/hashgraph/guardian/assets/79293833/9c91102b-caa0-4391-b8b9-1e08201682c1">

Methodology Library/CDM/Tools/Tool 11/readme.md

@@ -0,0 +1,25 @@
+# UNFCCC CDM Tool 11: Assessment of the Validity of the Original/Current Baseline and Update of the Baseline at the Renewal of the Crediting Period (Version 03.0.1)
+
+**UNFCCC CDM Tool 11** is essential for CDM project participants facing the renewal of their crediting period. This tool provides a stepwise procedure for assessing the continued validity of the existing baseline and for updating this baseline when necessary, ensuring the project remains aligned with current conditions and continues to contribute to GHG emission reductions.
+
+## Purpose and Scope
+
+- To assess and update the project baseline at the time of crediting period renewal, ensuring continued relevance and accuracy.
+
+## Key Features
+
+- **Two-Step Procedure:** A systematic approach to evaluate the current baseline's validity and to update the baseline accordingly.
+- **Compliance and Circumstances Assessment:** Evaluates baseline compliance with new policies and examines the impact of changed circumstances on the baseline scenario.
+
+## Application Process
+
+1. **Assess Current Baseline Validity:** Determine if the existing baseline remains valid for the upcoming crediting period.
+2. **Update the Baseline:** Update the baseline as required based on current policies, market characteristics, and other relevant factors.
+
+## Importance in CDM Projects
+
+Tool 11 is crucial for the integrity of ongoing CDM projects, ensuring their baselines reflect the latest conditions and policies, thereby accurately representing their emission reduction contributions.
+
+## Conclusion
+
+**UNFCCC CDM Tool 11** facilitates the critical process of baseline assessment and update, supporting the sustained impact of CDM projects in the fight against climate change.

Methodology Library/CDM/Tools/readme.md

@@ -27,9 +27,9 @@ Tools are used to calculate, determine, demonstrate, estimate, identify and/or t
 | Tool 9 | Tool to determinine the baseline efficiency of thermal or electric energy generation systems | -|
 | Tool 10 | Tool to determine the remaining lifetime of equipment | 1706867224.09846 |
 | Tool 12 | Tool to calculate project and leakage emissions from transportation of freight |1709106946.91315|
-| Tool 13 | Tool to calculate project and leakage emissions from composting  |1708419091.40539|
-| Tool 14 | Tool to calculate project and leakage emissions from anaerobic digesters | 1709652639.33901 |
-| Tool 16 | Tool to calculate project and leakage emissions from biomass   | 1709655070.11995 |
+| Tool 13 | Tool to calculate project and leakage emissions from composting  |1711359002.029988003|
+| Tool 14 | Tool to calculate project and leakage emissions from anaerobic digesters | 1711360482.771988021 |
+| Tool 16 | Tool to calculate project and leakage emissions from biomass   | 1711361537.374647879 |
 | Tool 19 | Tool to perform demonstration of additionality of microscale project activities |  1706869798.17793 |
 | Tool 21 | Tool to perform demonstration of additionality of small-scale project activities  3 | 1706873385.45582 |
 | Tool 22 | Tool to calculate leakage in biomass small-scale project activities  | |

Methodology Library/Hackathon/readme.md

@@ -0,0 +1 @@
+