Merging Develop into Main for 2.13.0-prerelease (hashgraph#2197)

* GITBOOK-320: Added Themes UI

* GITBOOK-321: Adding Theme APIs

* Add files via upload

* Bump yup from 0.32.11 to 1.1.1

Bumps [yup](https://github.com/jquense/yup) from 0.32.11 to 1.1.1.
- [Release notes](https://github.com/jquense/yup/releases)
- [Changelog](https://github.com/jquense/yup/blob/master/CHANGELOG.md)
- [Commits](jquense/yup@v0.32.11...v1.1.1)

---
updated-dependencies:
- dependency-name: yup
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>

* Bump @types/node from 18.11.9 to 18.16.0

Bumps [@types/node](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/node) from 18.11.9 to 18.16.0.
- [Release notes](https://github.com/DefinitelyTyped/DefinitelyTyped/releases)
- [Commits](https://github.com/DefinitelyTyped/DefinitelyTyped/commits/HEAD/types/node)

---
updated-dependencies:
- dependency-name: "@types/node"
  dependency-type: direct:development
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>

* hotfix/progress-bar-schemas

* API Guideline 

This documentation is to underline the different types of validation status code and any error status code, including Naming Conventions for RESTful APIs. This documentation is apart of the API contract review PR hashgraph#1974 and issue hashgraph#1629

* fix duplicate schema field label

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

* feat: validation removed

Signed-off-by: Felipe Neuhauss <felipe.neuhauss@gmail.com>

* updated policy files [skip ci]

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

* fix merge

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

* bump version

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

* Bump @aws-sdk/client-secrets-manager from 3.310.0 to 3.319.0

Bumps [@aws-sdk/client-secrets-manager](https://github.com/aws/aws-sdk-js-v3/tree/HEAD/clients/client-secrets-manager) from 3.310.0 to 3.319.0.
- [Release notes](https://github.com/aws/aws-sdk-js-v3/releases)
- [Changelog](https://github.com/aws/aws-sdk-js-v3/blob/main/clients/client-secrets-manager/CHANGELOG.md)
- [Commits](https://github.com/aws/aws-sdk-js-v3/commits/v3.319.0/clients/client-secrets-manager)

---
updated-dependencies:
- dependency-name: "@aws-sdk/client-secrets-manager"
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>

* GITBOOK-322: Guidance for Open Source Policy

* Updated Verra ARR Timestamp

* Added Schema

* Updated Gold Standard AR Timestamp

* GITBOOK-323: Guidance

* disable application events

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

* fix

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

* fix api, fix uuid

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

* Bump axios from 0.25.0 to 1.3.6

Bumps [axios](https://github.com/axios/axios) from 0.25.0 to 1.3.6.
- [Release notes](https://github.com/axios/axios/releases)
- [Changelog](https://github.com/axios/axios/blob/v1.x/CHANGELOG.md)
- [Commits](axios/axios@v0.25.0...v1.3.6)

---
updated-dependencies:
- dependency-name: axios
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>

* Bump jose from 4.3.8 to 4.14.1

Bumps [jose](https://github.com/panva/jose) from 4.3.8 to 4.14.1.
- [Release notes](https://github.com/panva/jose/releases)
- [Changelog](https://github.com/panva/jose/blob/main/CHANGELOG.md)
- [Commits](panva/jose@v4.3.8...v4.14.1)

---
updated-dependencies:
- dependency-name: jose
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>

* Bump mongodb from 4.8.1 to 5.3.0

Bumps [mongodb](https://github.com/mongodb/node-mongodb-native) from 4.8.1 to 5.3.0.
- [Release notes](https://github.com/mongodb/node-mongodb-native/releases)
- [Changelog](https://github.com/mongodb/node-mongodb-native/blob/main/HISTORY.md)
- [Commits](mongodb/node-mongodb-native@v4.8.1...v5.3.0)

---
updated-dependencies:
- dependency-name: mongodb
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>

* Bump @mikro-orm/core from 5.3.1 to 5.7.2

Bumps [@mikro-orm/core](https://github.com/mikro-orm/mikro-orm) from 5.3.1 to 5.7.2.
- [Release notes](https://github.com/mikro-orm/mikro-orm/releases)
- [Changelog](https://github.com/mikro-orm/mikro-orm/blob/master/CHANGELOG.md)
- [Commits](mikro-orm/mikro-orm@v5.3.1...v5.7.2)

---
updated-dependencies:
- dependency-name: "@mikro-orm/core"
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>

* Bump sinon from 13.0.2 to 15.0.4

Bumps [sinon](https://github.com/sinonjs/sinon) from 13.0.2 to 15.0.4.
- [Release notes](https://github.com/sinonjs/sinon/releases)
- [Changelog](https://github.com/sinonjs/sinon/blob/main/docs/changelog.md)
- [Commits](sinonjs/sinon@v13.0.2...v15.0.4)

---
updated-dependencies:
- dependency-name: sinon
  dependency-type: direct:development
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>

* fix build

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

* GITBOOK-324: Corrected Guidance

* GITBOOK-325: guidance for open source

* Bump @mikro-orm/mongodb from 5.3.1 to 5.7.2

Bumps [@mikro-orm/mongodb](https://github.com/mikro-orm/mikro-orm) from 5.3.1 to 5.7.2.
- [Release notes](https://github.com/mikro-orm/mikro-orm/releases)
- [Changelog](https://github.com/mikro-orm/mikro-orm/blob/master/CHANGELOG.md)
- [Commits](mikro-orm/mikro-orm@v5.3.1...v5.7.2)

---
updated-dependencies:
- dependency-name: "@mikro-orm/mongodb"
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>

* Bump @mikro-orm/migrations-mongodb from 5.3.1 to 5.7.2

Bumps [@mikro-orm/migrations-mongodb](https://github.com/mikro-orm/mikro-orm) from 5.3.1 to 5.7.2.
- [Release notes](https://github.com/mikro-orm/mikro-orm/releases)
- [Changelog](https://github.com/mikro-orm/mikro-orm/blob/master/CHANGELOG.md)
- [Commits](mikro-orm/mikro-orm@v5.3.1...v5.7.2)

---
updated-dependencies:
- dependency-name: "@mikro-orm/migrations-mongodb"
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>

* fixes

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

* fix web3token

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

* GITBOOK-316: Documentation related to the PRs that were merged

* fix bugs

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

* fix

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

* fix validation

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

* cut filenames

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

* fix field type

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

* GITBOOK-326: Corrected alignment and fonts

* GITBOOK-327: Added image for Environment

* fix tag schemas

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

* GITBOOK-331: cloud infrastructure roadmap

* remove files with large name

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

* GITBOOK-332: updated images

* update irec 5 policy [skip ci]

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

* Updated irec 5 timestamp in readme

* GITBOOK-333: Updated iREC timestamps

* hotfix/horizontal-scroll-blank-spaces

* bump version

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

* bump version

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

* fix import tags

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

* fix report item

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

* fix overwriting entities

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

* fixing document validation error

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

* moved policies tab

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

* fix refreshing events

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

* fix scroll in request block

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

* upgrade ws updating messages

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

* fix lint

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

* optimize update algorithm

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

* fix issue in aggregation block

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

* update info about revoke block

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

* added converting for old revoke block

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

* fix issue with set relationships block

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

* apply updating to multiple users

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

* add new block

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

* GITBOOK-335: selective disclosure doc added

* resolve hashgraph#1923,resolve hashgraph#1693
Integrate multi env feature
Service Env can Override
configs folder in dockerfile & managed GUARDIAN_ENV
docs
Docs Manual execution
Apply changes on updated develop
DIRECT_MESSAGE_PORT is a specilized variable

Signed-off-by: otherNet <francesco.calderoni@intellecteu.com>

* fix displaying account creation document in trust chain

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

* Bump @hashgraph/sdk from 2.24.1 to 2.24.2

Bumps [@hashgraph/sdk](https://github.com/hashgraph/hedera-sdk-js) from 2.24.1 to 2.24.2.
- [Release notes](https://github.com/hashgraph/hedera-sdk-js/releases)
- [Changelog](https://github.com/hashgraph/hedera-sdk-js/blob/develop/CHANGELOG.md)
- [Commits](hashgraph/hedera-sdk-js@v2.24.1...v2.24.2)

---
updated-dependencies:
- dependency-name: "@hashgraph/sdk"
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>

* disable application events

Signed-off-by: simvalery <valeriy.simonov@envisionblockchain.com>
Signed-off-by: Felipe Neuhauss <felipe.neuhauss@gmail.com>

* fix

Signed-off-by: simvalery <valeriy.simonov@envisionblockchain.com>
Signed-off-by: Felipe Neuhauss <felipe.neuhauss@gmail.com>

* feat: prometheus and grafana integration

Signed-off-by: Felipe Neuhauss <felipe.neuhauss@gmail.com>

* feat: swagger updated

Signed-off-by: Felipe Neuhauss <felipe.neuhauss@gmail.com>

* feat: swagger updated

Signed-off-by: Felipe Neuhauss <felipe.neuhauss@gmail.com>

* feat: docs updated

Signed-off-by: Felipe Neuhauss <felipe.neuhauss@gmail.com>

* feat: prometheus and grafana integration

Signed-off-by: Felipe Neuhauss <felipe.neuhauss@gmail.com>

* update

* Updates .policy files and readme.md for ICP.

* fix merge

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

* Bump @mikro-orm/mongodb from 5.7.2 to 5.7.5

Bumps [@mikro-orm/mongodb](https://github.com/mikro-orm/mikro-orm) from 5.7.2 to 5.7.5.
- [Release notes](https://github.com/mikro-orm/mikro-orm/releases)
- [Changelog](https://github.com/mikro-orm/mikro-orm/blob/master/CHANGELOG.md)
- [Commits](mikro-orm/mikro-orm@v5.7.2...v5.7.5)

---
updated-dependencies:
- dependency-name: "@mikro-orm/mongodb"
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>

* fix lint

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

* fices

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

* Bump @mikro-orm/core from 5.7.2 to 5.7.5

Bumps [@mikro-orm/core](https://github.com/mikro-orm/mikro-orm) from 5.7.2 to 5.7.5.
- [Release notes](https://github.com/mikro-orm/mikro-orm/releases)
- [Changelog](https://github.com/mikro-orm/mikro-orm/blob/master/CHANGELOG.md)
- [Commits](mikro-orm/mikro-orm@v5.7.2...v5.7.5)

---
updated-dependencies:
- dependency-name: "@mikro-orm/core"
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>

* Bump @mikro-orm/migrations-mongodb from 5.7.2 to 5.7.5

Bumps [@mikro-orm/migrations-mongodb](https://github.com/mikro-orm/mikro-orm) from 5.7.2 to 5.7.5.
- [Release notes](https://github.com/mikro-orm/mikro-orm/releases)
- [Changelog](https://github.com/mikro-orm/mikro-orm/blob/master/CHANGELOG.md)
- [Commits](mikro-orm/mikro-orm@v5.7.2...v5.7.5)

---
updated-dependencies:
- dependency-name: "@mikro-orm/migrations-mongodb"
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>

* Bump mongodb from 5.3.0 to 5.4.0

Bumps [mongodb](https://github.com/mongodb/node-mongodb-native) from 5.3.0 to 5.4.0.
- [Release notes](https://github.com/mongodb/node-mongodb-native/releases)
- [Changelog](https://github.com/mongodb/node-mongodb-native/blob/main/HISTORY.md)
- [Commits](mongodb/node-mongodb-native@v5.3.0...v5.4.0)

---
updated-dependencies:
- dependency-name: mongodb
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>

* feat: swagger updated

Signed-off-by: Felipe Neuhauss <felipe.neuhauss@gmail.com>

* update

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

* GITBOOK-334: Felipe's May 2 changes

* GITBOOK-338: Prometheus and Grafana documentation

* update

* Bump @mikro-orm/core from 5.7.5 to 5.7.7

Bumps [@mikro-orm/core](https://github.com/mikro-orm/mikro-orm) from 5.7.5 to 5.7.7.
- [Release notes](https://github.com/mikro-orm/mikro-orm/releases)
- [Changelog](https://github.com/mikro-orm/mikro-orm/blob/master/CHANGELOG.md)
- [Commits](mikro-orm/mikro-orm@v5.7.5...v5.7.7)

---
updated-dependencies:
- dependency-name: "@mikro-orm/core"
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>

* Bump mongodb from 5.4.0 to 5.5.0

Bumps [mongodb](https://github.com/mongodb/node-mongodb-native) from 5.4.0 to 5.5.0.
- [Release notes](https://github.com/mongodb/node-mongodb-native/releases)
- [Changelog](https://github.com/mongodb/node-mongodb-native/blob/main/HISTORY.md)
- [Commits](mongodb/node-mongodb-native@v5.4.0...v5.5.0)

---
updated-dependencies:
- dependency-name: mongodb
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>

* fix 2100

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

* fix 2110

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

* Bump @mikro-orm/mongodb from 5.7.5 to 5.7.7

Bumps [@mikro-orm/mongodb](https://github.com/mikro-orm/mikro-orm) from 5.7.5 to 5.7.7.
- [Release notes](https://github.com/mikro-orm/mikro-orm/releases)
- [Changelog](https://github.com/mikro-orm/mikro-orm/blob/master/CHANGELOG.md)
- [Commits](mikro-orm/mikro-orm@v5.7.5...v5.7.7)

---
updated-dependencies:
- dependency-name: "@mikro-orm/mongodb"
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>

* Bump @mikro-orm/migrations-mongodb from 5.7.5 to 5.7.7

Bumps [@mikro-orm/migrations-mongodb](https://github.com/mikro-orm/mikro-orm) from 5.7.5 to 5.7.7.
- [Release notes](https://github.com/mikro-orm/mikro-orm/releases)
- [Changelog](https://github.com/mikro-orm/mikro-orm/blob/master/CHANGELOG.md)
- [Commits](mikro-orm/mikro-orm@v5.7.5...v5.7.7)

---
updated-dependencies:
- dependency-name: "@mikro-orm/migrations-mongodb"
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>

* fix 2133

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

* compare schemas

* GITBOOK-336: adding a subpage to the environments section

* GITBOOK-340: correction to Ecosystem Environment

* update

* update

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

* update

* change document hash in retire request

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

* update

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

* add demo policy

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

* fix update vc

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

* fix display of schema dialog buttons for mobile UI

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

* GITBOOK-343: adding guides

* GITBOOK-344: Added GoldStandard

* implement nestjs

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

* upload and verify vc

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

* fix loading animation

* change vc documents index

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

* update

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

* refactor

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

* GITBOOK-345: added Atma policy

* update order by

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

* fix migration

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

* fix tests

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

* added wizards

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

* fix

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

* added wizard docs [skip ci]

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

* fix trustchain creation

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

* change help icons

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

* fix lint

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

* fix schema updating

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

* fixed clone schemas

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

* fix importing schemas

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

* fix exporting schemas

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

* added integer to mint fields

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

* fix tips, trustchain issues

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

* remove wizard preset on publish

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

* fix ui issues

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

* added getData, setData to basic block

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

* change contracts to retirement

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

* GITBOOK-347: Added VM0042 description

* fix style

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

* fix relationship and produced schemas

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

* fix link button

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

* added rejected source addon to wizard

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

* added cdm policy [skip ci]

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

* fix build

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

* implement nestjs api

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

* wiard api

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

* add topic mask

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

* fix logs

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

* add env config

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

* fixed choose wizard state

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

* fixed wizard trustchain

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

* fix dialog size

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

* change approving for initial steps

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

* added revocationBlock

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

* added deprecation to about section

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

* remove getData, setData from basic block

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

* changed wizard config in swagger

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

* fix import/export

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

* fix build

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

* fix lots errors

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

* GITBOOK-348: added externalTopicBlock details

* changed ui displaying for deprecated blocks

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

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

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

* added ability to create schemas with draft topics

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

* GITBOOK-349: added aPI parameters for pagination

* GITBOOK-350: Integrating external policies demo

* GITBOOK-351: Policy Wizard demo using UI

* GITBOOK-352: Wizard APIs

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

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

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

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

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

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

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

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

* disable publishing for schemas with draft topic

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

* changed block tag generation in wizard

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

* fix schema type
Signed-off-by: simvalery <valeriy.simonov@envisionblockchain.com>

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

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

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

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

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

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

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

* fix get-schemas request
Signed-off-by: simvalery <valeriy.simonov@envisionblockchain.com>

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

* fix get-schemas request
Signed-off-by: simvalery <valeriy.simonov@envisionblockchain.com>

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

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

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

* fix lint

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

* fix swagger wizard endpoint paths

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

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

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

* schema active endpoint
Signed-off-by: simvalery <valeriy.simonov@envisionblockchain.com>

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

* Create ReadMe.md

* Rename ReadMe.md to readme.md

* Update readme.md of CDM

---------

Signed-off-by: dependabot[bot] <support@github.com>
Signed-off-by: artembuslaev <artem.buslaev@envisionblockchain.com>
Signed-off-by: Felipe Neuhauss <felipe.neuhauss@gmail.com>
Signed-off-by: Stepan Kiryakov <stepan.kiryakov@envisionblockchain.com>
Signed-off-by: simvalery <valeriy.simonov@envisionblockchain.com>
Signed-off-by: Artem Buslaev <artem.buslaev@envisionblockchain.com>
Signed-off-by: otherNet <francesco.calderoni@intellecteu.com>
Co-authored-by: Stepan Kiryakov <stepan.kiryakov@envisionblockchain.com>
Co-authored-by: prernaa.agarwal <prernaa.agarwal@envisionblockchain.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Co-authored-by: E. Santiago <eduardo.augusto.santiago@gmail.com>
Co-authored-by: Vanessa Lopes <111521009+vaness453@users.noreply.github.com>
Co-authored-by: artembuslaev <artem.buslaev@envisionblockchain.com>
Co-authored-by: Felipe Neuhauss <felipe.neuhauss@gmail.com>
Co-authored-by: Vanessa Lopes <vanessa.lopes@intellecteu.com>
Co-authored-by: otherNet <francesco.calderoni@intellecteu.com>
Co-authored-by: AlexIvanHoward <alexivanhoward@gmail.com>
Co-authored-by: Serg Metelin <sergey.metelin@hedera.com>
Co-authored-by: Felipe Neuhauss <felipe.neuhauss@intellecteu.com>

.env

@@ -0,0 +1,4 @@
+## GUARDIAN ECOSYSTEM ENVIRONMENT NAME
+# if you already started to use actively Guardian leave GUARDIAN_ENV empty when you want to use it as usual  
+# if you want to use a new environment configure GUARDIAN_ENV with a significative environment name
+GUARDIAN_ENV=""

.env.template

@@ -0,0 +1,4 @@
+## GUARDIAN ECOSYSTEM ENVIRONMENT NAME
+# if you already started to use actively Guardian leave GUARDIAN_ENV empty when you want to use it as usual  
+# if you want to use a new environment configure GUARDIAN_ENV with a significative environment name
+GUARDIAN_ENV=""

.gitignore

@@ -1,3 +1,4 @@
+.env
 node_modules/
 dist/
 .vscode/
@@ -16,6 +17,7 @@ tsconfig.tsbuildinfo
 .pnp.*
 node_modules
 runtime-data/
+000_*
 
 # OSX related metadata removal and IDE nonsense
 .DS_store

Makefile.justCOMPILE

@@ -0,0 +1,12 @@
+guardian_build:
+	cd interfaces && npm install && npm  run build --prod
+	cd common && npm install && npm  run build --prod
+	cd logger-service && npm install && npm  run build --prod
+	cd api-gateway && npm install && npm  run build --prod
+	cd auth-service && npm install && npm  run build --prod
+	cd worker-service && npm install && npm  run build --prod
+	cd guardian-service && npm install && npm  run build --prod
+	cd policy-service && npm install && npm  run build --prod
+	cd topic-viewer && npm install && npm  run build --prod
+	cd mrv-sender && npm install && npm  run build --prod
+	cd frontend && npm install && export NODE_OPTIONS=--openssl-legacy-provider && npm  run build --prod

Methodology Library/CDM/readme.md

@@ -0,0 +1,23 @@
+## CDM AR-ACM0003: Methodology for Afforestation and Reforestation of Lands Except Wetlands
+
+**Policy Description**: 
+
+The CDM AR-ACM0003 methodology is a comprehensive framework developed under the Clean Development Mechanism (CDM) to guide afforestation and reforestation projects aimed at combating climate change and promoting sustainable land use practices. This methodology facilitates the identification of suitable project sites, establishes baselines for measuring greenhouse gas emissions, ensures the additionality of emissions reductions, implements robust monitoring and reporting systems, addresses leakage and permanence concerns, and seeks validation and certification from accredited entities. By adhering to this methodology, projects can effectively sequester carbon dioxide, conserve biodiversity, provide ecosystem services, and generate socio-economic co-benefits, contributing to global climate change mitigation and sustainable development goals.
+
+The Guardian policy for afforestation and reforestation of lands except wetlands (AR-ACM0003) incorporates schemas for project details, baseline scenario GHG removals, project scenario GHG removals, project scenario emissions, and leakage. These schemas provide a structured framework for site selection, emissions quantification, and monitoring procedures.
+
+**Workflow Description**:
+
+The workflow for the afforestation and reforestation of lands except wetlands (AR-ACM0003) Guardian policy involves the Project Proponent preparing and submitting the project description, which is then reviewed and approved by the Designated National Authority (DNA). The UNFCCC Secretariat adds the approved project to the project pipeline and registry. The Project Proponent conducts monitoring and submits the monitoring report to the Designated Operational Entity (VVB) for assessment and validation. Upon certification by the VVB, the UNFCCC Secretariat reviews the project and issues Certified Emission Reductions (CERs).
+
+<img width="1074" alt="image" src="https://github.com/hashgraph/guardian/assets/79293833/ca1f586e-ad42-46f9-82bd-cd47e9dfaa5f">
+
+**Note** :
+For Demo purpose, we have uploaded CDM Policy into IPFS and created Timestamps, which are mentioned in the below table.
+
+**Verra REDD Versions and their IPFS timestamps:**
+
+| Version | IPFS Timestamp | Policy File Link | Version Differences |
+|---|---|---|---:|
+| CDM AR-ACM0003  | 1684768427.831434003 | [Link](https://github.com/hashgraph/guardian/blob/main/Methodology%20Library/CDM/CDM.policy) | CDM AR-ACM0003 Methodology |
+

Methodology Library/Improved CookStove/readme.md

@@ -1,98 +1,155 @@
 ## Guardian Policy for Improved Cookstoves
 
-**Introduction**:
+**Introduction**
 
 Currently, there are many different types of cookstoves and several Standards Bodies, each with their own Standard that must be followed in order to prove the quality of a given GHG emission reduction claim. This process is time and labor intensive, creating barriers to those willing to enter the market. Digitization of this manual, paper driven process is a necessary step to scaling at the speed required for climate change.
 
 The Value of Digitizing the Methodology:
 
-Creates trust via
+1. Creates trust via
+- Traceability and transparency of data
+- Digital quality assurance
+- Immutability of data
+- Transparency of Verifier credentials and approval data
+
+2. Reduces barriers to entry
+- Accessible and standardized policies and processes inform and encourage suppliers to bring their projects to market
+- Decentralized project management reduces dependency on Standards Bodies and reduces time to market.
+
+3. Contributes to Climate Goals
+- Achieves higher confidence carbon project outcomes, and scales the finance and rollout of carbon projects at the speed required by the climate emergency
+
+This first of its kind Hedera Guardian Improved Cookstove Policy (ICP) was designed per the [Anthropogenic Impact Accounting Ontology](https://wiki.hyperledger.org/display/CASIG/An+ontology+for+anthropogenic+impact+accounting). To this end, the Guardian Policy does not adhere to a specific Standard or approved methodology for carbon offset quantification, rather it abstracts concepts from the most commonly used standards and methodologies, categorizes them, models their relationships, and then instantiates them in the form of this digitally native Guardian Policy and its associated Guardian Schema. This policy issues a non-fungible Improved Cookstove Carbon Credit (ICCC) Token.
+
+**Scope and Applicability**
+
+Scope: Quantification of greenhouse gas (GHG) emission reductions from improved biomass cookstoves developed by the Nova Institute and Tolam Earth, Inc.
+
+Applicability: Applicable to activities reducing GHG emissions from cookstoves through switching to more energy efficient stoves.
+
+Token: Non-Fungible
+
+Type: Carbon Offset
+
+Standard: Multiple
+
+Methodology: Multiple
+
+Required Documents: Project Design Document (PDD), PDD Validation Report, Monitoring Report, Monitoring Report Verification, Double Counting Certification, VVB Certification and Conflict of Interest Statement. See 'Preconditions' below for more detail.
+
+NFT Owner: The agent fulfilling the 'Project Developer' role.
+
+**Preconditions**
+
+1. Standard Registry account on a Guardian instance to import the policy and its subpolicies. See [Guardian documentation](https://docs.hedera.com/guardian/policy-creation-using-the-guardian-apis/prerequesite-steps) for steps to create an account and import a policy.
+2. User accounts within the Guardian to fill the roles defined in the policy and its subpolicies.
+3. Required Project Documentation posted to traceable, immutable source which can be accessed by the Tolam Earth Marketplace.
+4. To fulfil the Project Developer role (see 'Roles' below for details), an agent must obtain an HGICP Project Developer License (HGICP-L-PD) from the ICP Agent Application Subpolicy.
+5. To fulfil the PDD Validator role, an agent must obtain an HGICP PDD Validator License (HGICP-L-PV) from the ICP Agent Application Subpolicy.
+6. To fulfil the MR Verifier role, an agent must obtain an HGICP MR Verifier License (HGICP-L-MV) form the ICP Agent Application Subpolicy.
+7. In addition to an HGICP-L-PD, a Project Developer will need to obtain an HGICP PDD Validation Certificate (HGICP-VCERT-PDD, issued by the ICP PDD Validation Subpolicy) to complete the project registration step of the main policy. To apply for an ICCC issuance, a Project Developer will furthermore need to obtain an HGICP MR Verification Certificate (HGICP-VCERT-MR, issued by the ICP MR Verification Subpolicy).
+
+Testnet message IDs:
+- Improved Cookstove Policy (main): 1676641566.153212434
+- Improved Cookstove Policy - Agent Application Subpolicy: 1676640723.598879583
+- Improved Cookstove Policy - PDD Validation Subpolicy: 1676641042.365033796
+- Improved Cookstove Policy - MR Verification Subpolicy: 1676641311.452316505
+
+**Policy User Roles**
+
+Improved Cookstove Policy (main):
+1. Project Developer (PROJECT_DEVELOPER): Person responsible for executing the Project Design and collecting Data as per the Project Application. The Project Developer submits Monitoring Reports and is the beneficiary of the Credit Claims.
+2. Public Viewer (VIEWER): Any member of the public who wishes to view the Guardian TrustChain for a specific ICCC issuance.
+3. Standard Body (OWNER): Administrative role that approves Verifiers, approves Project Applications, and manages the issuance of claims.
+
+Improved Cookstove Policy - Agent Application Subpolicy:
+1. (Anyone): Any person or legal entity who wishes to fulfil one or more of the following ICP roles:
+- Project Developer (in any of the four policies)
+- PDD Validator (in the PDD Validation Subpolicy)
+- MR Verifier (in the MR Verification Subpolicy)
+2. Standard Body (OWNER): See Improved Cookstove Policy (main).
+
+Improved Cookstove Policy - PDD Validation Subpolicy:
+1. Project Developer (PROJECT_DEVELOPER): See Improved Cookstove Policy (main).
+2. Validator (VALIDATOR): An agent who validates Project Designs by reviewing Project Design Documents.
+3. Public Viewer: Not yet implemented.
+
+Improved Cookstove Policy - MR Verification Subpolicy:
+1. Project Developer (PROJECT_DEVELOPER): See Improved Cookstove Policy (main).
+2. Verifier (VERIFIER): Approved, independent person or organization that verifies Claims Data in the form of Monitoring Reports.
+3. Public Viewer: Not yet implemented.
+
+**Schema**
+
+Improved Cookstove Policy (main):
+- Presentation Request: Role License (PR-RL)
+- Project Listing Application (PLA)
+- Document Review: Project Listing Application (DR-PLA)
+- Project Registration Request (PRR)
+- HGICV Token Issuance Request (TIR)
+
+ICP Agent Application Subpolicy:
+- Role Application (RA)
+- Agent Details (AD)
+
+ICP PDD Validation Subpolicy:
+- Presentation Request: Role License (PR-RL)
+- PDD Section A - Description of Project (PDD-XA)
+- Document Review: PDD Section A (DR-PDD-XA)
+- PDD Section B - Methodologies (PDD-XB)
+- Document Review: PDD Section B (DR-PDD-XB)
+- PDD Section C - Crediting Period (PDD-XC)
+- Document Review: PDD Section C (DR-PDD-XC)
+- PDD Section D - Other Impacts (PDD-XD)
+- Document Review: PDD Section D (DR-PDD-XD)
+- PDD Section E - Stakeholder Engagement (PDD-XE)
+- Document Review: PDD Section E (DR-PDD-XE)
+- Project Design Document (PDD)
+- Location
+- GeoCoordinate
+- GeoLine
+- GeoPolygon
+- Technology or Measure
+- Project Party
+- Table: Project Boundary
+- Table Row: Project Boundary
+- Emission Reduction Calculation
+- Table Row: Data/Parameter Monitoring
+- Table Row: Ex Ante Emissions Estimations
+- Monitoring Plan
+
+ICP MR Verification Subpolicy:
+- Presentation Request: Role License (PR-RL)
+- Monitoring Report (MR)
+- Table Row: Data/Parameter Monitoring
+- Document Review: Monitoring Report (DR-MR)
+
+**Workflow**
+
+![Table showing the workflows of the Improved Cookstove Policy and its subpolicies](https://bafybeib4ms5lkfbcccbpc6tlcs3cilsiqmgszld7mlndllg653ywjhvzyu.ipfs.w3s.link/PolicyWorkflow.png)
+
+**Glossary**
 
-●	Traceability and transparency of data
-
-●	Digital quality assurance
-
-●	Immutability of data
-
-●	Transparency of Verifier credentials and approval data
-
-Reduces barriers to entry
-
-●	Accessible and standardized policies and processes inform and encourage suppliers to bring their projects to market
-
-●	Decentralized project management reduces dependency on Standards Bodies and reduces time to market.
-
-Contributes to Climate Goals
-
-●	Achieves higher confidence carbon project outcomes, and scales the finance and rollout of carbon projects at the speed required by the climate emergency
-
-This first of its kind Improved Cookstove Guardian Policy was designed per the Anthropogenic Impact Accounting Ontology found here An ontology for anthropogenic impact accounting. To this end, the Guardian Policy does not adhere to a specific Standard or approved methodology for carbon offset quantification, rather it abstracts concepts from all known standards and methodologies, categorizes them, models their relationships, and then instantiates them in the form of this digitally native Guardian Policy and its associated Guardian Schema. This policy issues a non fungible Improved Cookstove Carbon Credit (ICCC) Token.
-
-**Scope and Applicability**:
-
-Guardian implementation of a digitally native methodology for quantifying greenhouse gas (GHG) emission reductions from improved biomass cookstoves developed by the Nova Institute and Tolam Earth, Inc.
-
-
-Applicable to activities reducing GHG emissions from cookstoves:
-
-1. Through switching to more efficient stove technology
-
-Token: Non-Fungible Type: Carbon Offset Standard: Multiple Methodology: Multiple
-
-Required Documents: Project Design Document (PDD), PDD Validation Report, Monitoring Report, Monitoring Report Verification, Double Counting Certification,
-
-VVB Certification and Conflict of Interest Statement
-
-NFT Owner:
-
-**Preconditions**:
-1.	Standard Registry account on a Guardian instance to import the policy. See Guardian documentation at
-      (https://docs.hedera.com/guardian/policy-creation-using-the-guardian-apis/prerequesite-
-      steps) for steps to create an account and import a policy.
-2.	User accounts within the Guardian to fill the roles defined in this policy.
-3.	Required Project Documentation posted to traceable, immutable source which can be accessed by the Tolam Earth Marketplace.
-
-**Policy User Roles**:
-1.	Project Developer: Person responsible for executing the Project Design and collecting Data as per the Project Application. The Project Developer submits Monitoring Reports and is the beneficiary of the Credit Claims.
-2.	Verifier: Approved, independent person or organization that Verifies the Project Application and Claims Data in the form of Monitoring Reports.
-3.	Standard Body: Administrative role that approves Verifiers, approves Project Applications, and manages the issuance of claims.
-
-**Schema**:
-
-1.	Agent Application (AA)
-2.	Project Listing Application (PLA)
-3.	Project Listing Application (PLA) - Review
-4.	Project Design Document (PDD)
-5.	Project Design Document (PDD) - Review
-6.	Project Registration Request (PRR)
-7.	Monitoring Report (MR)
-8.	Monitoring Report (MR) - Review
-9.	ICCC Issuance Request (CIR)
-
-**Glossary**:
+Claim: The end result of execution of a project, often expressed per unit time, which quantifies the impact of the initiative.
 
 Guardian: The Guardian is a modular open-source solution that includes best-in-class identity management and Decentralized Ledger Technology (DLT) libraries. At the heart of the Guardian solution is a sophisticated Policy Workflow Engine (PWE) that enables applications to offer a requirements-based tokenization implementation.
 
 Guardian Policy: Defines activities, rules, and interactions between activities on and across all levels of the activity hierarchy, that are performed in order to achieve the outcome of an auditable, transparent claim of climate impact.
 
 Guardian Schema: Describes the structure and definition of data fields required within an activity, sub-activity, or sub-sub-activity. Essentially, the schema defines the data fields that must be supplied for each activity and the characteristics of those fields.
 
-Standard: Set of project design, monitoring, and reporting criteria against which activities’ impacts can be certified or verified, e.g. Greenhouse Gas (GHG) emission reductions, or social benefits.
-
-Standards Body: Organization which defines the standard and approves project design, monitoring, and reporting criteria within it.
-
 Methodology: As part of a Standard, Methodologies define the rules for calculating emissions increase, footprint, reductions and/or removals.
 
-Project Documentation: Any documentation required by the Guardian Schema. This may include Monitoring Reports, Project Design Documents, Verifier Credentials, etc.
+Monitoring Report: Document that describes and justifies any changes to the Project Design Document, based upon what happened during execution of a project. Also includes any data and/or calculations made during the time period covered by the document. A single project can have multiple Monitoring Reports associated with it, and each Monitoring Report is associated with a Claim.
 
 Project Design Document: Documentation of plans for an activity to be executed following the prescriptions of the Standard in a concrete context for generation of assets.
 
+Project Documentation: Any documentation required by the Guardian Schema. This may include Monitoring Reports, Project Design Documents, Verifier Credentials, etc.
+
 Project Listing Application: Process during which a Project Developer expresses their intent to develop a (cookstove) project towards a specific Registry, and the Registry then acknowledges that intent by assigning a project code to the project and listing it in the Registry’s public database of projects.
 
 Project Registration: When Project Design Documents are approved by a Registry.
 
+Standard: Set of project design, monitoring, and reporting criteria against which activities’ impacts can be certified or verified, e.g. Greenhouse Gas (GHG) emission reductions, or social benefits.
 
-**Monitoring Report**:
-
-Document that describes and justifies any changes to the Project Design Document, based upon what happened during execution of a project. Also includes any data and/or calculations made during the time period covered by the document. A single project can have multiple Monitoring Reports associated, and each Monitoring Report is associated with a Claim.
-Claim: The end result of execution of a project, often expressed per unit time, which quantifies the impact of the initiative.
+Standards Body: Organization which defines the standard and approves project design, monitoring, and reporting criteria within it.