diff --git a/docs/.gitbook/assets/image (1) (1) (1) (1) (1) (1) (1) (1).png b/docs/.gitbook/assets/image (1) (1) (1) (1) (1) (1) (1) (1).png new file mode 100644 index 0000000000..64dcbfce4a Binary files /dev/null and b/docs/.gitbook/assets/image (1) (1) (1) (1) (1) (1) (1) (1).png differ diff --git a/docs/.gitbook/assets/image (1) (1) (1) (1) (1) (1) (1).png b/docs/.gitbook/assets/image (1) (1) (1) (1) (1) (1) (1).png index 64dcbfce4a..fd487e4449 100644 Binary files a/docs/.gitbook/assets/image (1) (1) (1) (1) (1) (1) (1).png and b/docs/.gitbook/assets/image (1) (1) (1) (1) (1) (1) (1).png differ diff --git a/docs/.gitbook/assets/image (1) (1) (1) (1) (1) (1).png b/docs/.gitbook/assets/image (1) (1) (1) (1) (1) (1).png index fd487e4449..f215c151a7 100644 Binary files a/docs/.gitbook/assets/image (1) (1) (1) (1) (1) (1).png and b/docs/.gitbook/assets/image (1) (1) (1) (1) (1) (1).png differ diff --git a/docs/.gitbook/assets/image (1) (1) (1) (1) (1).png b/docs/.gitbook/assets/image (1) (1) (1) (1) (1).png index f215c151a7..e40832f472 100644 Binary files a/docs/.gitbook/assets/image (1) (1) (1) (1) (1).png and b/docs/.gitbook/assets/image (1) (1) (1) (1) (1).png differ diff --git a/docs/.gitbook/assets/image (1) (1) (1) (1).png b/docs/.gitbook/assets/image (1) (1) (1) (1).png index e40832f472..f9e2ba27c1 100644 Binary files a/docs/.gitbook/assets/image (1) (1) (1) (1).png and b/docs/.gitbook/assets/image (1) (1) (1) (1).png differ diff --git a/docs/.gitbook/assets/image (1) (1) (1).png b/docs/.gitbook/assets/image (1) (1) (1).png index f9e2ba27c1..33409f86c1 100644 Binary files a/docs/.gitbook/assets/image (1) (1) (1).png and b/docs/.gitbook/assets/image (1) (1) (1).png differ diff --git a/docs/.gitbook/assets/image (1) (1).png b/docs/.gitbook/assets/image (1) (1).png index 33409f86c1..5e9d4c646e 100644 Binary files a/docs/.gitbook/assets/image (1) (1).png and b/docs/.gitbook/assets/image (1) (1).png differ diff --git a/docs/.gitbook/assets/image (1).png b/docs/.gitbook/assets/image (1).png index 5e9d4c646e..bf2fded8de 100644 Binary files a/docs/.gitbook/assets/image (1).png and b/docs/.gitbook/assets/image (1).png differ diff --git a/docs/.gitbook/assets/image (10) (1) (1) (1).png b/docs/.gitbook/assets/image (10) (1) (1) (1).png new file mode 100644 index 0000000000..4260e5b162 Binary files /dev/null and b/docs/.gitbook/assets/image (10) (1) (1) (1).png differ diff --git a/docs/.gitbook/assets/image (10) (1) (1).png b/docs/.gitbook/assets/image (10) (1) (1).png index 4260e5b162..41c3c47af3 100644 Binary files a/docs/.gitbook/assets/image (10) (1) (1).png and b/docs/.gitbook/assets/image (10) (1) (1).png differ diff --git a/docs/.gitbook/assets/image (10) (1).png b/docs/.gitbook/assets/image (10) (1).png index 41c3c47af3..93de69b997 100644 Binary files a/docs/.gitbook/assets/image (10) (1).png and b/docs/.gitbook/assets/image (10) (1).png differ diff --git a/docs/.gitbook/assets/image (10).png b/docs/.gitbook/assets/image (10).png index 93de69b997..777d27b21a 100644 Binary files a/docs/.gitbook/assets/image (10).png and b/docs/.gitbook/assets/image (10).png differ diff --git a/docs/.gitbook/assets/image (2) (1) (1) (1) (1) (1) (1).png b/docs/.gitbook/assets/image (2) (1) (1) (1) (1) (1) (1).png new file mode 100644 index 0000000000..75381204f2 Binary files /dev/null and b/docs/.gitbook/assets/image (2) (1) (1) (1) (1) (1) (1).png differ diff --git a/docs/.gitbook/assets/image (2) (1) (1) (1) (1) (1).png b/docs/.gitbook/assets/image (2) (1) (1) (1) (1) (1).png index 75381204f2..9fc0c8426e 100644 Binary files a/docs/.gitbook/assets/image (2) (1) (1) (1) (1) (1).png and b/docs/.gitbook/assets/image (2) (1) (1) (1) (1) (1).png differ diff --git a/docs/.gitbook/assets/image (2) (1) (1) (1) (1).png b/docs/.gitbook/assets/image (2) (1) (1) (1) (1).png index 9fc0c8426e..00b72f5662 100644 Binary files a/docs/.gitbook/assets/image (2) (1) (1) (1) (1).png and b/docs/.gitbook/assets/image (2) (1) (1) (1) (1).png differ diff --git a/docs/.gitbook/assets/image (2) (1) (1) (1).png b/docs/.gitbook/assets/image (2) (1) (1) (1).png index 00b72f5662..003d493bc5 100644 Binary files a/docs/.gitbook/assets/image (2) (1) (1) (1).png and b/docs/.gitbook/assets/image (2) (1) (1) (1).png differ diff --git a/docs/.gitbook/assets/image (2) (1) (1).png b/docs/.gitbook/assets/image (2) (1) (1).png index 003d493bc5..6dbe4b9004 100644 Binary files a/docs/.gitbook/assets/image (2) (1) (1).png and b/docs/.gitbook/assets/image (2) (1) (1).png differ diff --git a/docs/.gitbook/assets/image (2) (1).png b/docs/.gitbook/assets/image (2) (1).png index 6dbe4b9004..600c763d47 100644 Binary files a/docs/.gitbook/assets/image (2) (1).png and b/docs/.gitbook/assets/image (2) (1).png differ diff --git a/docs/.gitbook/assets/image (2).png b/docs/.gitbook/assets/image (2).png index 600c763d47..fa3093c027 100644 Binary files a/docs/.gitbook/assets/image (2).png and b/docs/.gitbook/assets/image (2).png differ diff --git a/docs/.gitbook/assets/image (3) (1) (1) (1) (1) (1) (1) (1).png b/docs/.gitbook/assets/image (3) (1) (1) (1) (1) (1) (1) (1).png new file mode 100644 index 0000000000..ade9ae13a4 Binary files /dev/null and b/docs/.gitbook/assets/image (3) (1) (1) (1) (1) (1) (1) (1).png differ diff --git a/docs/.gitbook/assets/image (3) (1) (1) (1) (1).png b/docs/.gitbook/assets/image (3) (1) (1) (1) (1).png index ade9ae13a4..ecebc76904 100644 Binary files a/docs/.gitbook/assets/image (3) (1) (1) (1) (1).png and b/docs/.gitbook/assets/image (3) (1) (1) (1) (1).png differ diff --git a/docs/.gitbook/assets/image (3) (1) (1) (1).png b/docs/.gitbook/assets/image (3) (1) (1) (1).png index ecebc76904..13eea5a6ff 100644 Binary files a/docs/.gitbook/assets/image (3) (1) (1) (1).png and b/docs/.gitbook/assets/image (3) (1) (1) (1).png differ diff --git a/docs/.gitbook/assets/image (3) (1) (1).png b/docs/.gitbook/assets/image (3) (1) (1).png index 13eea5a6ff..2f623aff02 100644 Binary files a/docs/.gitbook/assets/image (3) (1) (1).png and b/docs/.gitbook/assets/image (3) (1) (1).png differ diff --git a/docs/.gitbook/assets/image (3) (1).png b/docs/.gitbook/assets/image (3) (1).png index 2f623aff02..734d730eba 100644 Binary files a/docs/.gitbook/assets/image (3) (1).png and b/docs/.gitbook/assets/image (3) (1).png differ diff --git a/docs/.gitbook/assets/image (3).png b/docs/.gitbook/assets/image (3).png index 734d730eba..7802b32b61 100644 Binary files a/docs/.gitbook/assets/image (3).png and b/docs/.gitbook/assets/image (3).png differ diff --git a/docs/.gitbook/assets/image (4) (1) (1) (1) (1) (1) (1).png b/docs/.gitbook/assets/image (4) (1) (1) (1) (1) (1) (1).png new file mode 100644 index 0000000000..a3104c901a Binary files /dev/null and b/docs/.gitbook/assets/image (4) (1) (1) (1) (1) (1) (1).png differ diff --git a/docs/.gitbook/assets/image (4) (1) (1) (1) (1) (1).png b/docs/.gitbook/assets/image (4) (1) (1) (1) (1) (1).png index a3104c901a..2a8cb2b6c6 100644 Binary files a/docs/.gitbook/assets/image (4) (1) (1) (1) (1) (1).png and b/docs/.gitbook/assets/image (4) (1) (1) (1) (1) (1).png differ diff --git a/docs/.gitbook/assets/image (4) (1) (1) (1) (1).png b/docs/.gitbook/assets/image (4) (1) (1) (1) (1).png index 2a8cb2b6c6..516fbdf12b 100644 Binary files a/docs/.gitbook/assets/image (4) (1) (1) (1) (1).png and b/docs/.gitbook/assets/image (4) (1) (1) (1) (1).png differ diff --git a/docs/.gitbook/assets/image (4) (1) (1) (1).png b/docs/.gitbook/assets/image (4) (1) (1) (1).png index 516fbdf12b..c98f9b2510 100644 Binary files a/docs/.gitbook/assets/image (4) (1) (1) (1).png and b/docs/.gitbook/assets/image (4) (1) (1) (1).png differ diff --git a/docs/.gitbook/assets/image (4) (1) (1).png b/docs/.gitbook/assets/image (4) (1) (1).png index c98f9b2510..c9bac87ba7 100644 Binary files a/docs/.gitbook/assets/image (4) (1) (1).png and b/docs/.gitbook/assets/image (4) (1) (1).png differ diff --git a/docs/.gitbook/assets/image (4) (1).png b/docs/.gitbook/assets/image (4) (1).png index c9bac87ba7..a7eb0f2070 100644 Binary files a/docs/.gitbook/assets/image (4) (1).png and b/docs/.gitbook/assets/image (4) (1).png differ diff --git a/docs/.gitbook/assets/image (4).png b/docs/.gitbook/assets/image (4).png index a7eb0f2070..f4a6551096 100644 Binary files a/docs/.gitbook/assets/image (4).png and b/docs/.gitbook/assets/image (4).png differ diff --git a/docs/.gitbook/assets/image (5) (1) (1) (1) (1).png b/docs/.gitbook/assets/image (5) (1) (1) (1) (1).png new file mode 100644 index 0000000000..8f2ac4204c Binary files /dev/null and b/docs/.gitbook/assets/image (5) (1) (1) (1) (1).png differ diff --git a/docs/.gitbook/assets/image (5) (1) (1) (1).png b/docs/.gitbook/assets/image (5) (1) (1) (1).png index 8f2ac4204c..9f4f68ee19 100644 Binary files a/docs/.gitbook/assets/image (5) (1) (1) (1).png and b/docs/.gitbook/assets/image (5) (1) (1) (1).png differ diff --git a/docs/.gitbook/assets/image (5) (1) (1).png b/docs/.gitbook/assets/image (5) (1) (1).png index 9f4f68ee19..3e62b79545 100644 Binary files a/docs/.gitbook/assets/image (5) (1) (1).png and b/docs/.gitbook/assets/image (5) (1) (1).png differ diff --git a/docs/.gitbook/assets/image (5) (1).png b/docs/.gitbook/assets/image (5) (1).png index 3e62b79545..cbfa38ad80 100644 Binary files a/docs/.gitbook/assets/image (5) (1).png and b/docs/.gitbook/assets/image (5) (1).png differ diff --git a/docs/.gitbook/assets/image (5).png b/docs/.gitbook/assets/image (5).png index cbfa38ad80..312e257bfb 100644 Binary files a/docs/.gitbook/assets/image (5).png and b/docs/.gitbook/assets/image (5).png differ diff --git a/docs/.gitbook/assets/image (6) (1) (1) (1) (1) (1).png b/docs/.gitbook/assets/image (6) (1) (1) (1) (1) (1).png new file mode 100644 index 0000000000..deb83004f2 Binary files /dev/null and b/docs/.gitbook/assets/image (6) (1) (1) (1) (1) (1).png differ diff --git a/docs/.gitbook/assets/image (6) (1) (1) (1) (1).png b/docs/.gitbook/assets/image (6) (1) (1) (1) (1).png index deb83004f2..a520be4d62 100644 Binary files a/docs/.gitbook/assets/image (6) (1) (1) (1) (1).png and b/docs/.gitbook/assets/image (6) (1) (1) (1) (1).png differ diff --git a/docs/.gitbook/assets/image (6) (1) (1) (1).png b/docs/.gitbook/assets/image (6) (1) (1) (1).png index a520be4d62..0482b79d28 100644 Binary files a/docs/.gitbook/assets/image (6) (1) (1) (1).png and b/docs/.gitbook/assets/image (6) (1) (1) (1).png differ diff --git a/docs/.gitbook/assets/image (6) (1) (1).png b/docs/.gitbook/assets/image (6) (1) (1).png index 0482b79d28..cceb01b44c 100644 Binary files a/docs/.gitbook/assets/image (6) (1) (1).png and b/docs/.gitbook/assets/image (6) (1) (1).png differ diff --git a/docs/.gitbook/assets/image (6) (1).png b/docs/.gitbook/assets/image (6) (1).png index cceb01b44c..cf1ad696cb 100644 Binary files a/docs/.gitbook/assets/image (6) (1).png and b/docs/.gitbook/assets/image (6) (1).png differ diff --git a/docs/.gitbook/assets/image (6).png b/docs/.gitbook/assets/image (6).png index cf1ad696cb..068123ac5e 100644 Binary files a/docs/.gitbook/assets/image (6).png and b/docs/.gitbook/assets/image (6).png differ diff --git a/docs/.gitbook/assets/image (7) (1) (1) (1).png b/docs/.gitbook/assets/image (7) (1) (1) (1).png new file mode 100644 index 0000000000..fb6f48768f Binary files /dev/null and b/docs/.gitbook/assets/image (7) (1) (1) (1).png differ diff --git a/docs/.gitbook/assets/image (7) (1) (1).png b/docs/.gitbook/assets/image (7) (1) (1).png index fb6f48768f..b96b872c04 100644 Binary files a/docs/.gitbook/assets/image (7) (1) (1).png and b/docs/.gitbook/assets/image (7) (1) (1).png differ diff --git a/docs/.gitbook/assets/image (7) (1).png b/docs/.gitbook/assets/image (7) (1).png index b96b872c04..db3a31549d 100644 Binary files a/docs/.gitbook/assets/image (7) (1).png and b/docs/.gitbook/assets/image (7) (1).png differ diff --git a/docs/.gitbook/assets/image (7).png b/docs/.gitbook/assets/image (7).png index db3a31549d..328dbe5d28 100644 Binary files a/docs/.gitbook/assets/image (7).png and b/docs/.gitbook/assets/image (7).png differ diff --git a/docs/.gitbook/assets/image (8) (1) (2).png b/docs/.gitbook/assets/image (8) (1) (2).png index cf5ee54e0f..1d884344fa 100644 Binary files a/docs/.gitbook/assets/image (8) (1) (2).png and b/docs/.gitbook/assets/image (8) (1) (2).png differ diff --git a/docs/.gitbook/assets/image (8) (1).png b/docs/.gitbook/assets/image (8) (1).png index 1d884344fa..936e1da226 100644 Binary files a/docs/.gitbook/assets/image (8) (1).png and b/docs/.gitbook/assets/image (8) (1).png differ diff --git a/docs/.gitbook/assets/image (8).png b/docs/.gitbook/assets/image (8).png index 936e1da226..8a89d2ce97 100644 Binary files a/docs/.gitbook/assets/image (8).png and b/docs/.gitbook/assets/image (8).png differ diff --git a/docs/.gitbook/assets/image (9) (2).png b/docs/.gitbook/assets/image (9) (2).png index dd5676fbc9..99e9b4deb7 100644 Binary files a/docs/.gitbook/assets/image (9) (2).png and b/docs/.gitbook/assets/image (9) (2).png differ diff --git a/docs/.gitbook/assets/image (9).png b/docs/.gitbook/assets/image (9).png index 99e9b4deb7..cbc960c157 100644 Binary files a/docs/.gitbook/assets/image (9).png and b/docs/.gitbook/assets/image (9).png differ diff --git a/docs/.gitbook/assets/image.png b/docs/.gitbook/assets/image.png index 777d27b21a..bf9251d588 100644 Binary files a/docs/.gitbook/assets/image.png and b/docs/.gitbook/assets/image.png differ diff --git a/docs/SUMMARY.md b/docs/SUMMARY.md index 26d0513db3..58827ce573 100644 --- a/docs/SUMMARY.md +++ b/docs/SUMMARY.md @@ -409,8 +409,6 @@ * [Unsetting KYC for the User](guardian/tokens/token-operations/apis-for-asynchronous-execution/unsetting-kyc-for-the-user.md) * [📔 Token Retirement Contract](guardian/tokens/retirement-contract/README.md) * [đŸ’» Creating Contract using UI](guardian/tokens/retirement-contract/creating-contract-using-ui.md) - * [đŸ’» Creating Token Pair UI](guardian/tokens/retirement-contract/creating-token-pair-ui.md) - * [⚒ Creating Retire Request](guardian/tokens/retirement-contract/creating-retire-request.md) * [⚙ Retirement APIs](guardian/tokens/retirement-contract/retirement-apis/README.md) * [Returning all contracts](guardian/tokens/retirement-contract/retirement-apis/returns-all-contracts.md) * [Creating new Contract](guardian/tokens/retirement-contract/retirement-apis/creating-new-contract.md) diff --git a/docs/guardian/automation-testing/performing-ui-automation-testing.md b/docs/guardian/automation-testing/performing-ui-automation-testing.md index bb263284ba..c9673a39ae 100644 --- a/docs/guardian/automation-testing/performing-ui-automation-testing.md +++ b/docs/guardian/automation-testing/performing-ui-automation-testing.md @@ -28,7 +28,7 @@ and then select test under ui-tests/specs/policies Finally, all the selected test runs and you can see the key components of the Test Runner that you need to pay attention to when executing tests. -
+
**Test Status Menu:** The menu shows a summary of the number of tests passed, passed, failed, or incomplete, and the time spent on the test. diff --git a/docs/guardian/demo-guide/carbon-emissions/remote-work-ghg-policy/introduction-to-remote-work-ghg.md b/docs/guardian/demo-guide/carbon-emissions/remote-work-ghg-policy/introduction-to-remote-work-ghg.md index ead385970b..c5584b482a 100644 --- a/docs/guardian/demo-guide/carbon-emissions/remote-work-ghg-policy/introduction-to-remote-work-ghg.md +++ b/docs/guardian/demo-guide/carbon-emissions/remote-work-ghg-policy/introduction-to-remote-work-ghg.md @@ -12,4 +12,4 @@ Heating and cooling energy consumption defaults were calculated based on Energy The workflow begins with each employee completing a survey to help refine their GHG estimates based on location; actual office, heating, and cooling equipment; and other important variables. Based on the responses, a verified credentials (VC) document is created. Then, employees track hours worked and GHG emissions are auto-calculated by customized schemas featuring built-in equations, defaults, and emission factors. Workforce emissions are calculated as the sum of all employee emissions and the resulting emissions are tokenized. -
+
diff --git a/docs/guardian/demo-guide/carbon-offsets/dovu-methodologies.md b/docs/guardian/demo-guide/carbon-offsets/dovu-methodologies.md index 2e2ba114aa..dcdcbdd305 100644 --- a/docs/guardian/demo-guide/carbon-offsets/dovu-methodologies.md +++ b/docs/guardian/demo-guide/carbon-offsets/dovu-methodologies.md @@ -38,7 +38,7 @@ The first step towards compliance was building a system to support manual attest For AgreCalc we see below form: -
+
for Cool Farm, we see below form: @@ -48,11 +48,11 @@ for Cool Farm, we see below form: 6. Now we log out and login as Standard Registry, once viewing the registrant documents, we approve the application by clicking on Approve button. 7. Once approved, we again login back as Registrant and submit Farm Registrant form by clicking on Create Farm button: -
+
8. Once filled and clicked on OK, Registrant waits for approval from Standard Registry: -
+
9. Now we login as Standard Registry and click on Farm Projects tab, we can see the Request being submitted by Registrant for Approve/Reject @@ -62,7 +62,7 @@ For testing purpose, we will approve the farm project. 10. Once SR approves, we login back as Registrant and submit AgreCalc Document by filling out the form: -
+
For Cool Farm Tool methodology, you will see the below request form: @@ -71,12 +71,12 @@ For Cool Farm Tool methodology, you will see the below request form: 11. Once the Request is submitted, Registrant is waiting for it to be approved by Verifier. 12. Now we logout and login as Verifier, we verify the documents by clicking on approve. -
+
13. Once approved, we login as SR and check the Token History by clicking on Token History Tab: -
+
14. We can also check the TrustChain by clicking on View TrustChain button: -
+
diff --git a/docs/guardian/demo-guide/carbon-offsets/improved-cookstove.md b/docs/guardian/demo-guide/carbon-offsets/improved-cookstove.md index c091f8a053..4f36a4fa03 100644 --- a/docs/guardian/demo-guide/carbon-offsets/improved-cookstove.md +++ b/docs/guardian/demo-guide/carbon-offsets/improved-cookstove.md @@ -40,7 +40,7 @@ We need to first import the policy from open source repository. Once imported, there will be 2 additional users with different roles (aside from the Standard Registry) that need to be created. Create a user account for the Project Developer. Once created and entered into the Policy, select the Project Developer role from the drop-down. -
+
Fill out the Agent Application and wait for the approval. @@ -74,7 +74,7 @@ Now, the Project Developer must go into their screen and "Submit a PDD" and fill
-
+
Now, the Project Developer must go into their screen and "Submit a PDD" and fill out the Project Design Document form. @@ -84,23 +84,23 @@ Now, the Project Developer must go into their screen and "Submit a PDD" and fill The Verifier must now go into their Policy screen and view the PDD by click on the "Review button" and filling out the review form. -
+
After that, the Verifer can select a Review ID and "Finalise review."
-
+
Once the PDD has been verified, the Project Developer can "Request registration." -
+
The Standard Registry can log into their Policy screen, view the incoming Project Registration, and approve it. -
+
Once the Standard Registry approved the Project Developer's Project Registration, the Project Developer can submit the report by clicking on the "Submit MR" button and filling out the form. diff --git a/docs/guardian/demo-guide/carbon-offsets/verra-redd+-demo-guide.md b/docs/guardian/demo-guide/carbon-offsets/verra-redd+-demo-guide.md index 936b58b1f4..2227590b6d 100644 --- a/docs/guardian/demo-guide/carbon-offsets/verra-redd+-demo-guide.md +++ b/docs/guardian/demo-guide/carbon-offsets/verra-redd+-demo-guide.md @@ -29,7 +29,7 @@ Verra REDD 4 = 1695250025.604149003 Verra REDD 5 = 1695251173.300475003 ``` -
+
Once Policy is imported successfully, you get two options : Publish and Dry Run mode. diff --git a/docs/guardian/standard-registry/policies/introduction/multisignblock.md b/docs/guardian/standard-registry/policies/introduction/multisignblock.md index e36932437c..c63c8f8b59 100644 --- a/docs/guardian/standard-registry/policies/introduction/multisignblock.md +++ b/docs/guardian/standard-registry/policies/introduction/multisignblock.md @@ -108,7 +108,7 @@ To get detailed information on Signature status, we have an info icon near the t To get the final Signature Result with detailed information such as which users have Signed / Declined, we need to hover on the Status as shown below: -
+
### API Parameters diff --git a/docs/guardian/standard-registry/policies/introduction/reportblock-and-reportitemblock.md b/docs/guardian/standard-registry/policies/introduction/reportblock-and-reportitemblock.md index 3c488072e2..0fece22146 100644 --- a/docs/guardian/standard-registry/policies/introduction/reportblock-and-reportitemblock.md +++ b/docs/guardian/standard-registry/policies/introduction/reportblock-and-reportitemblock.md @@ -20,7 +20,7 @@ We have added new Impacts Section to display Primary/Secondary Impacts token det In the case when multiple linked mint blocks are used then the system displays all linked VPs as shown below: -
+
#### 2.1 Data Format: diff --git a/docs/guardian/standard-registry/policies/page-1.md b/docs/guardian/standard-registry/policies/page-1.md index 7532812281..e810241f7b 100644 --- a/docs/guardian/standard-registry/policies/page-1.md +++ b/docs/guardian/standard-registry/policies/page-1.md @@ -21,7 +21,7 @@ Step 1: Need to click on the linking icon for the policy, which you wanted to be Step 2: We get a policy linking pop up to create a link for the primary policy or joining an existing policy: -
+
After the ‘primary’ policy is registered a special ‘link’ becomes accessible which can be used to ‘connect’ additional ‘secondary’ policies. diff --git a/docs/guardian/standard-registry/policies/policy-demo.md b/docs/guardian/standard-registry/policies/policy-demo.md index a1d67feabe..422106fbd7 100644 --- a/docs/guardian/standard-registry/policies/policy-demo.md +++ b/docs/guardian/standard-registry/policies/policy-demo.md @@ -2,7 +2,7 @@ Once you login as a Standard Registry and finish the setup, click on Policies tab. -![](<../../../.gitbook/assets/image (4) (1) (1) (1) (1) (1).png>) +![](<../../../.gitbook/assets/image (4) (1) (1) (1) (1) (1) (1).png>) We have two options to create Policy : diff --git a/docs/guardian/standard-registry/policies/search-block/search-block-using-ui.md b/docs/guardian/standard-registry/policies/search-block/search-block-using-ui.md index 9f246a7998..f5cf25d168 100644 --- a/docs/guardian/standard-registry/policies/search-block/search-block-using-ui.md +++ b/docs/guardian/standard-registry/policies/search-block/search-block-using-ui.md @@ -4,19 +4,19 @@ Blocks of similar configuration can be searched by clicking on search icon with respect to the block as shown below: -
+
## 2. Search Result Search result displays all the policies and its blocks, which have same flow with respect to the base block search. -
+
### 2.1 Context The search finds and displays the ranked list (most similar on top) of longest continuous matching sequences of blocks surrounding the target block (highlighted). The search considers all dimensions - next/previous, parent/child - to be of equal weight and thus ranks results by the number of blocks in the found ‘similar’ sequence. -
+
Additionally, the system compares the configuration of the blocks individually, and displays the %% of similarity to the right of each block in comparison with the corresponding blocks in the base policy. @@ -30,13 +30,13 @@ Clicking “Apply” button will transfer (or apply) the configuration of the fo **Note:** Original settings of the base policy block will be lost if ‘Apply’ action is executed. {% endhint %} -
+
### 2.3 Search Results Layout Display Search results are displayed as folded groups by Policy (policy name is displayed in the group heading). -
+
The results are sorted by (in the correct order): @@ -44,4 +44,4 @@ The results are sorted by (in the correct order): 2\. Cumulative similarity score (%%) of the blocks -
+
diff --git a/docs/guardian/standard-registry/policies/search-policy/search-policy-using-ui.md b/docs/guardian/standard-registry/policies/search-policy/search-policy-using-ui.md index c493e63b74..9b9167f796 100644 --- a/docs/guardian/standard-registry/policies/search-policy/search-policy-using-ui.md +++ b/docs/guardian/standard-registry/policies/search-policy/search-policy-using-ui.md @@ -2,12 +2,12 @@ Policies can be searched by clicking on "Search policies" button. It can be searched based on their similarity to the given policy. -
+
The results are displayed in the descending order, the most similar policy is displayed at the top. It also displays similarity rate percentage. -
+
We can also have an option for full display mode of similarity result as shown: -
+
diff --git a/docs/guardian/standard-registry/schemas/creating-system-schema-using-ui.md b/docs/guardian/standard-registry/schemas/creating-system-schema-using-ui.md index 5a43bd165d..f35958585e 100644 --- a/docs/guardian/standard-registry/schemas/creating-system-schema-using-ui.md +++ b/docs/guardian/standard-registry/schemas/creating-system-schema-using-ui.md @@ -6,7 +6,7 @@ To create a new Schemas, click on the **New** button at the top right corner. After clicking on the New button, you will be asked to enter Schema details such as Schema Name, Policy Dropdown, Entity : VC/MRV/NONE, Schema Description and any other required fields. -![](<../../../.gitbook/assets/image (1) (1) (1) (1) (1) (1) (1).png>) +![](<../../../.gitbook/assets/image (1) (1) (1) (1) (1) (1) (1) (1).png>) In addition to the basic Schema details we also have an option to add Field and Condition to each field. @@ -14,7 +14,7 @@ In addition to the basic Schema details we also have an option to add Field and We can also customize the Field keys and Field Title by clicking on Advanced Tab. -![](<../../../.gitbook/assets/image (3) (1) (1) (1) (1) (1).png>) +![](<../../../.gitbook/assets/image (3) (1) (1) (1) (1) (1) (1).png>) Instead of creating a new Schema from scratch, there is also an option to import it via File or via IPFS. @@ -36,7 +36,7 @@ Import from IPFS: You can also import Schema from IPFS by entering the correct S Once the Schema is imported, we need to select the Policy from the Policy dropdown to connect the Schema and the Policy. -
+
diff --git a/docs/guardian/standard-registry/schemas/schema-differentiation/schema-differentiation-using-ui.md b/docs/guardian/standard-registry/schemas/schema-differentiation/schema-differentiation-using-ui.md index 1d48aaf920..474956a5e0 100644 --- a/docs/guardian/standard-registry/schemas/schema-differentiation/schema-differentiation-using-ui.md +++ b/docs/guardian/standard-registry/schemas/schema-differentiation/schema-differentiation-using-ui.md @@ -6,7 +6,7 @@ We can compare two schemas by following some steps as follows: We click on **Compare** button present in Schemas tab as shown below: -
+
## 2. Comparison View diff --git a/docs/guardian/standard-registry/schemas/system-policy-schemas.md b/docs/guardian/standard-registry/schemas/system-policy-schemas.md index 0da95afb18..c62678b638 100644 --- a/docs/guardian/standard-registry/schemas/system-policy-schemas.md +++ b/docs/guardian/standard-registry/schemas/system-policy-schemas.md @@ -17,7 +17,7 @@ To display System / Policy Schemas in the GUI, we have added a toggle in the Sch Whenever an account is created, System Schemas are generated automatically. -
+
{% hint style="info" %} Note: By default System Schemas cannot be edited/deleted. diff --git a/docs/guardian/tokens/retirement-contract/README.md b/docs/guardian/tokens/retirement-contract/README.md index 6725c7446a..af5bda712b 100644 --- a/docs/guardian/tokens/retirement-contract/README.md +++ b/docs/guardian/tokens/retirement-contract/README.md @@ -6,10 +6,10 @@ The ‘retirement contracts’ are responsible for the mechanics of matching ‘ The high-level flow of the actions which configure token retirement is illustrated on the sequence diagram below: -
+
Guardian contains a full production retirement system implementation which allows the configuration of arbitrary pools of tokens (two-sided, one-sides, with arbitrary ‘exchange rates’ etc), issued by different SRs, operating on different Guardian instances, to be configured for retirement with arbitrary additional rules further controlling their lifecycle. A simplified architecture diagram of the retirement contracts implementation is shown on the diagram below. -
+
diff --git a/docs/guardian/tokens/retirement-contract/creating-contract-using-ui.md b/docs/guardian/tokens/retirement-contract/creating-contract-using-ui.md index 3451ca1288..b30a88e3c2 100644 --- a/docs/guardian/tokens/retirement-contract/creating-contract-using-ui.md +++ b/docs/guardian/tokens/retirement-contract/creating-contract-using-ui.md @@ -2,11 +2,11 @@ 1. Guardian instance out of the box contains implementations for ‘Wiping’ and ‘Retirement’ contracts which can be deployed/enabled from the UI. -
+
2. Each SR has its own contract permissions. Since contracts are deployed on Hedera and their methods can be called independently via 3rd party systems but the status of these contracts can change without Guardian’s knowledge. SRs can action a ‘refresh’ of their permissions by clicking on the refresh sign (chargeable Hedera operation, costs < 1 hbar) -
+
### **Contract Roles:** @@ -26,3 +26,41 @@ | OWNER |
  1. Add/Remove ADMIN
  2. Clear Retire Requests/Pools
| | ADMIN |
  1. Set/Unset Pools
  2. Approve/Unset Retire Requests
| +4\) At the token creation the system can be configured to delegate all permissions for wiping tokens to a specific wiping contract + +
+ +5\) _SRs_ can add pools with tokens which have a wipe contract (Set pool operation in retire contract). + +Also you can check “without approval” to set retirement tokens as immediate operation (without approval).\ + + +
+ +6\) _SRs_ can check/delete/refresh pools (Pools operation in retirement contract). Not enabled means that the retirement contract has no wiper permissions in the appropriate wipe contract. It will be changed to enabled automatically when _the SR_ approves a request for a wiper role from this retirement contract. If the wipe contract is not in Guardian a manual refresh is required to update the instance permissions status. + +
+ +7\) _SRs_ can check/approve/reject/ban requests for the wiper role in the wipe contract (Requests operation in wipe contract). + +
+ +8\) To execute the retirement Guardian users which hold USER role navigate to the ‘Retire’ tab and click on ‘Retire’ button, choose appropriate pool and set token count/serials + +
+ +
+ +9\) If a token retirement requires approval, _users_ which hold USER role can see their requests by clicking on the ‘Requests’ button. + +
+ +10\) Contract owners can also see these requests and approve or reject (Requests operation on retirement contract). + +
+ +11\) After approval or rejection of the requests _users_ which hold USER role can see retire VCs on ‘Retire’ tab + +
+ +
diff --git a/docs/guardian/tokens/retirement-contract/creating-retire-request.md b/docs/guardian/tokens/retirement-contract/creating-retire-request.md deleted file mode 100644 index 306aa55173..0000000000 --- a/docs/guardian/tokens/retirement-contract/creating-retire-request.md +++ /dev/null @@ -1,35 +0,0 @@ -# ⚒ Creating Retire Request - -Once Standard Registry creates Token Pairs, Users can perform token retirement by clicking on Retire tab: - -
- -Users can create Retire Request by clicking on Create Retire Request. - -
- -Users can choose interested tokens, which they want to retire from the drop down: - -
- -Once tokens are selected, user needs to select the respective contract depending on the ratio needed. - -
- -{% hint style="info" %} -**Note:** - -Contract in the drop down is only available if the user is added to the contract by Standard Registry. -{% endhint %} - -Once, contract is selected, the third and final step is to select the base token and opposite token serials to perform retirement of tokens. - -
- -In addition to creation of requests, Users also can see created requests, they can cancel created requests (by clicking on “Cancel Request” button) and return their tokens from contract account before it will be approved by SR. If request is already approved users can see details of retire VC. - -
- -Standard Registry can see all retire requests by each contract. He can also view VC if it is already approved, or approve retire by clicking on “Retire Tokens” button. - -
diff --git a/docs/guardian/tokens/retirement-contract/creating-token-pair-ui.md b/docs/guardian/tokens/retirement-contract/creating-token-pair-ui.md deleted file mode 100644 index 5341681df7..0000000000 --- a/docs/guardian/tokens/retirement-contract/creating-token-pair-ui.md +++ /dev/null @@ -1,13 +0,0 @@ -# đŸ’» Creating Token Pair UI - -Once the contract is created, we have an option to create Token Pair by selecting first option in the Operations drop down: - -
- -Once clicked, Standard Registry can create token pair and can also set ratio between two tokens as shown below: - -
- -{% hint style="info" %} -Note: Token pair can be created only by entering Base Token. -{% endhint %} diff --git a/docs/guardian/tokens/token-template/how-to-create-token-template.md b/docs/guardian/tokens/token-template/how-to-create-token-template.md index 89cf9dc9b1..78f1fa33b0 100644 --- a/docs/guardian/tokens/token-template/how-to-create-token-template.md +++ b/docs/guardian/tokens/token-template/how-to-create-token-template.md @@ -2,4 +2,4 @@ We have a new tab as Token for all Blocks. This tab is used to add token template and set value for each token option. These values will be filled by User if it is null. -
+