๐Ÿ›ฃ๏ธRoadmap

---- October 2024----

Code audit: support and resolution of issues

  • Define scope and organise code audit and application penetration testing by a reputable 3rd party security firm.

  • Support audit team with Q&A and setting up environments etc

  • Resolve critical issues found.

Referral Link: https://github.com/hashgraph/guardian/issues/2989

GHG scorecards Research

  • Identify the KPIs (and the data requirements behind them) to be captured by the Environmental scorecards to best support demand signaling.

  • Identify the business requirements for the Environmental Scorecards, i.e., how they could be used by supply and demand-side actors, markets, etc.?

Referral Link : https://github.com/hashgraph/guardian/issues/1017

Token action block to work with token templates

Enhance token action block to work with token templates in the same way as it works with pre-defined tokens.

Referral Link: https://github.com/hashgraph/guardian/issues/2839

Documentation Link : https://docs.hedera.com/guardian-dev-1/guardian/tokens/dynamic-token-creation-in-policies/dynamic-token-creation-in-guardian-policies-using-ui

Different token IDs for different projects by the same policy

  • Introduce the facility to dynamically create new TokenIDs and 'assign' them to (newly registered) specific projects such that all data associated with these specific projects would be linked to the corresponding TokenIDs upon minting instances of the token.

  • Ensure clear association with the same methodology for all TokenIDs and their respective trustchains. I.e. it should be clear that 'these tokens' have been issued by the same Policy, but for different projects.

  • Extend trust chain to show multiple tokens and multiple projects 'managed' by the same policy

Referral Link : https://github.com/hashgraph/guardian/issues/3267

Documentation Link : https://docs.hedera.com/guardian-dev-1/guardian/tokens/dynamic-token-creation-in-policies/dynamic-token-creation-in-guardian-policies-using-ui

The task at hand involves modifying the codebase to seamlessly integrate the new MongoDB Atlas connection string without the redundant mongodb:// prefix. The correct format for the DB_HOST environment variable should be mongodb+srv://:@staging.wj9lvfj.mongodb.net/?retryWrites=true&w=majority. This adjustment will ensure a successful and accurate connection to our MongoDB Atlas instance.

Referral Link: https://github.com/hashgraph/guardian/issues/2940

Documentation Link : https://docs.hedera.com/guardian-dev-1/guardian/readme/getting-started/installation/setting-up-environment-parameters

Leverage the pre-built images as the default way to start Guardian locally

  • Update docker-compose.yml to leverage pre-built images from the latest Push

  • Create a docker-compose-build.yml with the same content as the current docker-compose.yml file to allow developers to build images locally via docker

  • Update the docs accordingly

Referral Link: https://github.com/hashgraph/guardian/issues/3551

Global Carbon Council (GCC) GCCM001: Methodology for Renewable Energy Generation Projects Supplying Electricity to Grid or Captive Consumers โ€“ Version 4.0

  1. Creating Schema design for this methodology.

  2. Development of the schema and policy.

  3. Testing the policy development through Guardian UI and configurator.

Referral Link: https://github.com/hashgraph/guardian/issues/3705

Documentation Link: https://docs.hedera.com/guardian-dev-1/guardian/demo-guide/carbon-offsets/gccm001-v.4-methodology-for-renewable-energy-generation-projects-supplying-electricity-to-grid

API versioning and support/deprecation schedule

Introduce versioning of Guardian API such that:

  • Backward compatibility is not broken for 'old' clients which are unaware of the existence of API versions

  • The versioning technology selected (see options here) is aligned with the wishes of Guardian community

  • API versions deprecation is appropriately embedded into the Guardian Push schedule

  • Versioning numbering scheme:

  • Meaningfully reflects changes in the API from version to version

  • Is aligned with the generally accepted practice

  • Is separate from the Guardian versions

Referral Link: https://github.com/hashgraph/guardian/issues/3236

Documentation Link:

Default values for schema-defined fields

  • Introduce facilities into the Guardian schema language which would allow Guardian policy engine (and humans when they read these schemas in json) to recognize what values should be considered default for the documents based on these schemas.

  • Make Guardian policy engine UI to put in the default values into the fields of forms based on such schemas. The fact that these are default values automatically inserted into the field should be clearly identifiable, i.e. they need to look different from the values users explicitly put into the (other) fields.

  • All standard tools/libraries (e.g. for verification) should work with such schemas out of the box

Referral Link: https://github.com/hashgraph/guardian/issues/2942

Documentation Link: https://docs.hedera.com/guardian-dev-1/guardian/standard-registry/schemas/schema-predefined-values-using-ui

Calculation Logic for values in 'automatic fields' in schemas

  • Introduce facilities into schema definition language which would allow for the referencing of other fields/values and specification of mathematics needed to calculate the field value based on those.

  • It should be possible to reference fields from 'other' schemas in the chain - parents/children.

Referral Link: https://github.com/hashgraph/guardian/issues/2986

Guardian analytics: bottom-up data traceability

  1. Design and implement specialized analytics engine which would enable Guardian to identify, trace and display mathematical relations between data in different artifacts (VCs/VPs/tokens) including events (transactions/messages) on Hedera hashgraph, with unlimited traceability depth.

  2. Intelligent 'understanding' of the nature of the transformations (e.g. in formulas in calculation blocks) is out of scope of this ticket, the analytics engine can view transformations as black boxes. If the 'original' data are used as 'input' into such a black box, for the purposes of this analytics reporting it can be assumed that the 'output' data depends on that 'original' data.

  3. The system should correctly identify and display references to the 'original' data such as when VC document fields reference document fields in other VCs.

  4. Users should be able to perform complex data searches with the scope limited to the dependencies graph.

  5. Guardian UI should enable Project Developers to define (and name) new datapoints and publish these definitions in a standardized manner linking them both to the originator's author DID, project ID and policy ID.

Referral Link: https://github.com/hashgraph/guardian/issues/3336

Rationalize API and UI return error codes

Letโ€™s say I submit incorrect data to a block (as I would like to rely on the schema validation on the guardian) Looking at the logs, I received an error about JSON schema validation:

2023-11-22 17:00:39 hedera-guardian-guardian-service-1 | 2023-11-22T17:00:39.765Z [GUARDIAN_SERVICE]: Error: Error: {"type":"JSON_SCHEMA_VALIDATION_ERROR","details":[{"instancePath":"","schemaPath":"#/required","keyword":"required","params":{"missingProperty":"field4"},"message":"must have required property 'field4'"}]} 

I am receiving a 500 status code back from a block submission in point where I would normally expect to receive something kin to a 422 (unprocessable entity)?

Referral Link: https://github.com/hashgraph/guardian/issues/2933

Simplify default SR schema to take out optional properties

Remove ISIC, geography, law 'required' fields so to simplify the creation of the SRs.

Referral Link: https://github.com/hashgraph/guardian/issues/3435

Data Parameterization and Conditional Review Logic

The ability to set parameters, which may not be public on Verifiable Credential based answers within a schema.

Referral Link: https://github.com/hashgraph/guardian/issues/4025

Scope 3/PCF Referencing Demo (Methodology Breakdown)

Once the approach has been approved, we can update the GHGP policy and run the example data, publish the PCFs to the Hedera Network, and demonstrate how another guardian policy (of a supply chain partner) can reference a dynamic PCF to support scope 3 calculations. I believe Wes was interested in having this be a methodology breakdown.

Referral Link: https://github.com/hashgraph/guardian/issues/3723

Verify and Fix the features that got affected by Mirror Node changes

  1. Need to research on all the features, which got affected by this change.

  2. Fix all the features issues and make sure all the data related to Mirror node is displayed and not missed.

  3. Test all the features affected.

Referral Link: https://github.com/hashgraph/guardian/issues/4204

Climate Action Reserve's U.S. Landfill Protocol

  1. Creating Schema design for this methodology.

  2. Development of the schema and policy.

  3. Testing the policy development through Guardian UI and configurator.

Referral Link: https://github.com/hashgraph/guardian/issues/3709

---- January 2025----

API facilities to retrieve unique references (IDs) of results for API-triggered operations

  • Design a generic approach to the 'traceability' of API calls such that for each API call a chain of events and actions within Guardian policy and especially to outside systems can be established via the unique IDs culminating in:

  • Hedera transactions

  • Hedera topics messages

  • Hedera contract calls

  • Artifacts published on IPFS

  • Introduce a corresponding UI where users can visually observe the same information

  • Consider packaging this into Interactions Resilience Module (see related Hedera interactions resilience module #2905)

Referral Link: https://github.com/hashgraph/guardian/issues/3139

Guardian analytics: insights and top-down data way points

The overall goal is to create a tool which provides non-technical high-level users (banks, auditors, analysts, accountants, etc) with insights out the box, and can serve as a way point for further data analytics, discovery and diagnostics.

  • Introduce an AI data analytics backend which automatically and continuously processes and analyses Guardian data across the entire ecosystem with the purpose of identifying patterns, dependencies, trends, important factors and variables, groups (cohorts) of data, etc.

  • Develop an analytics UI and visualization tool which is useable by non-technical users. This UI should allow users to continuously 'zoom in' or 'shift horizontally' on the data or the analytics results to examine them on a more detailed level or for a different parameter set: a different location, industry, sector, time range, specific values etc.

  • Implement functionality to visualize and search the structure (or organization) of Guardian data, which allows users to determine for example which schemas refer to attributes, in which policies they are used, and then seamlessly navigate to which data has been generated that's connected to these.

  • Provide an intelligent search interface which allows users at any point, while looking at a selection of data or an analytics result, to search for a 'similar' data or analytics result, while parameterizing the search with additional criteria. E.g. 'find similar set of MRVs but from projects in West Africa and those produced between 2021 and 2023'.

  • Allow users to save the configuration of their searches, UI settings/configurations and other parameters generating analytics results, etc so users can repeat and further enhance their previous analysis later - with newly available data.

Referral Link: https://github.com/hashgraph/guardian/issues/3341

Trustchain support for contract-based issuance and retirement implementation

Extend/modify trustchain implementation to support new contract-based issuance and retirement functionality such that users have visibility to the entire lifecycle of the token and have access to all significant artifacts produced as a result.

Referral Link: https://github.com/hashgraph/guardian/issues/2243

American Carbon Registry (ACR) ACR Methodology for Quantifying, Monitoring, Reporting, and Verifying Greenhouse Gas Emissions Reductions and Removals from Landfill Gas Destruction and Beneficial Use Projects

  1. Creating Schema design for this methodology.

  2. Development of the schema and policy.

  3. Testing the policy development through Guardian UI and configurator.

Referral Link: https://github.com/hashgraph/guardian/issues/3710

Reviewing and Verifying Atma policy

Some interesting next steps could be to address the final data gaps; engage with PACT to review the policy and schema, provide feedback, and identify new use cases and features; engage with a third-party auditor to review or potentially verify the policy; and eventually have actual downstream supply chain partners referencing the PCF.

Referral Link: https://github.com/hashgraph/guardian/issues/3729

Emissions Reduction/Removals (ERRs) Calculation Pre-Calculator in Guardian

Based on input data a estimated ERRs should be able to be queried in project development.

Referral Link: https://github.com/hashgraph/guardian/issues/3619

Formula Driven Definitions & Schema Tree Enhancement

A clear label (and an ability to define a formula) for a business user to build high level definitions and link them to underlying schemas, tools, and patterns closer aligned with VCM formulaic definitions

Referral Link: https://github.com/hashgraph/guardian/issues/3408

Dry-run policy execution 'savepoints' - restart policy dry-run from the list of 'saved' places

  • Introduce a new functionality for users to 'save' dry-run execution status at arbitrary points by clicking 'save state' button.

  • The system should support the creation of multiple save points for the same execution workflow

  • Next time the (draft) policy is executed in the dry-run mode users should be given a choice whether to restart from the beginning or continue execution from any of the 'save points'.

  • Starting execution from a 'save point' invalidates and removes all the other save points that logically followed it

  • It should be possible to delete some or all save points manually

Referral Link: https://github.com/hashgraph/guardian/issues/2838

Standardize UI on Angular Material, remove/replace PrimeNG

  • Standardize Guardian UI to be Material-based

  • Remove/Replace all PrimeNG with Material without changing the look feel

Referral Link: https://github.com/hashgraph/guardian/issues/3141

Clean Cooking and Climate Consortium Comprehensive Lowered Emissions Assessment and Reporting (CLEAR) Methodology for Cooking Energy Transitions

  1. Creating Schema design for this methodology.

  2. Development of the schema and policy.

  3. Testing the policy development through Guardian UI and configurator.

Referral Link: https://github.com/hashgraph/guardian/issues/3711

Enhancing Research on Indexer and Analytics Use Cases

Identify and map out potential uses cases for the indexer and what type of analytics if could be used for.

Referral Link: https://github.com/hashgraph/guardian/issues/3730

Development of AMS-I.C.: Thermal Energy Production with or Without Electricity

  1. Designing the Schema for the methodology

  2. Development of the policy

  3. Development of all the tools involved in this policy

    • Tool 03- Tool to calculate project or leakage CO2 emissions from fossil fuel combustion

    • Tool 05- Baseline, project and/or leakage emissions from electricity consumption and monitoring of electricity generation

    • Tool 06- Project emissions from flaring

    • Tool 07- Tool to calculate the emission factor for an electricity system

    • Tool 09- Determining the baseline efficiency of thermal or electric energy generation systems

    • Tool 12- Project and leakage emissions from transportation of freight

    • Tool 16- Project and leakage emissions from biomas

    • Tool 19- Demonstration of additionality of microscale project activities

    • Tool 21- Demonstration of additionality of small-scale project activities* Tool 22- Leakage in biomass small-scale project activities

Referral Link : https://github.com/hashgraph/guardian/issues/2873

Documentation Link : https://docs.hedera.com/guardian/guardian/demo-guide/carbon-offsets/cdm-ams-i.c.-thermal-energy-production-with-or-without-electricity

Last updated