Roadmap
Filtering data for blocks is stateful API, introduce stateless data filters for API usage.
July 2024
Yes
Yes
2.27
Code audit: support and resolution of issues
October 2024
Yes
Yes
3.0
GHG Scorecards Research
October 2024
Yes
Yes
3.0
Enhance MongoDB Integration
October 2024
Yes
Yes
3.0
Leverage the pre-built images as the default way to start Guardian locally
October 2024
Yes
Yes
3.0
Rationalize API and UI return error codes
October 2024
Yes
Yes
3.0
Simplify default SR schema to take out optional properties
October 2024
Yes
Yes
3.0
Calculation logic for values in 'automatic fields' in schemas
October 2024
Yes
Yes
3.0
Verify and Fix the features that got affected by Mirror node changes
October 2024
Yes
Yes
3.0
Scope 3/PCF Referencing Demo (Methodology Breakdown)
January 2025
Yes
Yes
3.1
January 2025
Yes
Yes
3.1
Trustchain support for contract-based issuance and retirement implementation
January 2025
Yes
Yes
3.1
GHGP Version 3
January 2025
Yes
Yes
3.1
January 2025
Yes
Yes
3.1
Standardize UI on Angular Material, remove/replace PrimeNG
January 2025
Yes
Yes
3.1
Enhancing Research on Indexer and Analytics Use Cases
January 2025
Yes
Yes
3.1
Cross-context (API+UI) refresh token invalidation (regression from v2.18.0)
May 2025
Yes
Yes
3.2
Business UseCase for Emissions Reduction/Removals (ERRs)Calculation Pre-Calculator in Guardian
May 2025
Yes
Yes
3.2
Weak Default configuration
May 2025
Yes
Yes
3.2
Article 6.4 Forms Research
May 2025
Yes
Yes
3.2
Session Token in URL
May 2025
Yes
Yes
3.2
May 2025
Yes
Yes
3.2
Server-Side Request Forgery (SSRF) in Request Data module
July 2025
Yes
Yes
3.3
Detailed Research on Indexer Enhancements
July 2025
Yes
Yes
3.3
July 2025
Yes
Yes
3.3
Outdated Software/Libraries
July 2025
Yes
Yes
3.3
Authorization Headers Potentially Leaked through IPFS in Request Data Module
July 2025
Yes
Yes
3.3
July 2025
Yes
Yes
3.3
Payload Shapefile Ingestion
August 2025
Improvement in the error handling for excel schema exports
August 2025
Dry-run savepoint[s] to survive exit and policy editing
August 2025
Locations Data Field enhancement
August 2025
SLA Ticket Import and Policy Publish Performance in Guardian
August 2025
Validation for project data submission
September 2025
Guardian Form UI Improvements
September 2025
Make testing easier for subflows
September 2025
--— August 2025 ----
Payload Shapefile Ingestion
Make the payload ingest shapefiles, KML etc.
Referral Link: https://github.com/hashgraph/guardian/issues/5046
Improvement in the error handling for excel schema imports
To have better validation when excel is imported into guardian which will help prevent all the points I mentioned above and some more that I probably missed while working on methodology digitization
Referral Link: https://github.com/hashgraph/guardian/issues/4755
Dry-run savepoint[s] to survive exit and policy editing
Make savepoints 'survive' multiple "exit dry-run -> edit policy -> execute dry-run" cycles such that policy authors would not have to enter values in fields again on subsequent dry-runs.
Enable to existence of multiple 'savepoints' per policy
Enable policy authors to choose when savepoint to apply on each policy dry-run session.
Users can clean-up savepoints by deleting them individually, or choosing to 'Delete All'
Referral Link: https://github.com/hashgraph/guardian/issues/5056
Locations Data Field enhancement
Validation Check: Implement a validation step to confirm that location data being passed to the policy is in polygon format (e.g., Polygon or MultiPolygon in GeoJSON).
Data Format Enforcement: Ensure that only valid polygon geometry types are accepted. Reject or flag submissions that use unsupported formats (e.g., Point, LineString, or malformed geometries).
GeoJSON Handling (Optional Enhancement): Explore and, if feasible, implement a conversion method to extract the location GeoJSON and convert it into a downloadable file format (e.g., .geojson or .json).
Referral Link: https://github.com/hashgraph/guardian/issues/5061
Authorization for /change-password endpoint
Need provide access token to change password
Referral Link: https://github.com/hashgraph/guardian/issues/4574
SLA Ticket Import and Policy Publish Performance in Guardian
Investigate bottlenecks in the SLA Ticket Import process:
File parsing and validation
Schema mapping and VC generation
Backend processing queues
Optimize the policy publishing process:
Reduce the time to publish policies with SLA blocks
Improve processing time for VC issuance and anchor creation on Hedera
Implement batch processing or lazy loading where applicable
Evaluate and optimize:
MongoDB write operations
Hedera anchoring transaction handling
Large file buffer management
Provide loading indicators and progress status updates to the user
Add backend logs/metrics to measure:
SLA import time
VC issuance time
Total policy publishing duration
Referral Link: https://github.com/hashgraph/guardian/issues/5120
--— September ----
Validation for project data submission
Validation Rules Enhancement Implement robust validation for schema fields in both UI-level form inputs and backend processing logic for key field types:
GeoJSON: Ensure that the data is a valid FeatureCollection or Geometry object following RFC 7946 standards.
IPFS Links: Ensure that the link is not empty and follows proper CID or ipfs:// format.
Error Handling and Feedback
Inform the user with clear error messages during submission if data fails validation.
Prevent submission if any required or format-sensitive fields are invalid.
Backward Compatibility Handling
Optionally, mark or flag previously submitted documents with invalid data for review or correction.
Unit and Integration Tests
Add test cases to ensure all validations work across various scenarios and edge cases
Referral Link: https://github.com/hashgraph/guardian/issues/5060
Guardian Form UI Improvements
These four can be made into their individual issues as well. Let me know, I'd be happy to submit four separate ones.
Support a table input(and csv import) field for multi-year data fields. Often methodologies require multi-year inputs(think 10 or 100 year) and it's not the easiest to visualize or input them with a typical form UI. It'd be good to have a way to have tabular inputs and a way to specify how they will be read within calculations code.
Support attachments to a field (justifications, report). Corresponding to a submitted field, a VVB or SR may ask for justification report which is usually a file. A similar issue is already there - Manual input of additional data for inclusion into the VC document #2076
For large documents for example PDD, it'd be good to divide them into sections when user is submitting. We must allow draft saves and make dry-run testing feasible. Such a feature already exists(tabbed/navigation UI), but if document is too big, policy developer needs to click test data button multiple times to fill the entire form.
GeoJSON/Shapefiles rendering - Allow file uploads of such types and they should be rendered with maps in best way in form UI.
Referral Link: https://github.com/hashgraph/guardian/issues/5042
Make testing easier for subflows
There should be a way to test the sub-flows similar to unit test paradigm we have in programming. Each unit should be individually runnable and testable. Following the entire workflow for testing takes up ~50-60% of time of policy development.
Referral Link: https://github.com/hashgraph/guardian/issues/5045
--— October ----
Complex iterative review and approval workflows
Introduce reviewVcDocumentBlock
as a complement to the requestVcDocumentBlock
into Policy definition language and corresponding Guardian UI tools which would facilitate complex iterative document review workflows supporting rich communications, namely the ability to:
send messages/descriptions associated with actions
conduct stand-alone (not action-linked) message exchanges (questions, responses, general comms)
send requests for providing additional documents/evidence, and provide facilities to upload/receive them
ability to edit/correct previously submitted (but rejected) document and resubmit again
forward messages to another user
involve other users into 'conversations'
These actions, steps, message exchanges have to be verifiably traceable, i.e. recorded and published as VC/VP documents alongside the usual data-containing documents produce by the policy workflows.
Referral Link: https://github.com/hashgraph/guardian/issues/4548
Policy warnings
Introduce the generic capability to highlight blocks, elements within them, and groups of blocks
Introduce the generic capability to produce and display warning/error/info messages, their numbers and ability to disable/resolve:
ignore (this one)
ignore all like this
Add the corresponding API capability to access and manage the warnings etc via API
Referral Link: https://github.com/hashgraph/guardian/issues/2230
Schema deletion with child schemas
Implement a safe way to delete all schemas embedded into the parent schema in one operation such that:
the system check whether the schemas embedded into the parent schema being deleted are used anywhere else, and if so prevents the delete operation
users can select whether to delete all embedded schema together with the parent one or not before the deletion
Referral Link: https://github.com/hashgraph/guardian/issues/2692
Implementing Artifacts such as Schemas/Policies/tokens Deletion all at once
Create a checkbox at the top of the schema/policy/token table, which will allow to select all the artifacts.
Once, all the schemas/policies/tokens are selected, and clicked on delete, we should be able to delete all the schemas/policies/tokens at once
Referral Link: https://github.com/hashgraph/guardian/issues/3375
Option to delete all schemas for a particular policy in Draft stage
There may be another solution/improvement to the excel where it checks for duplicates and provides with an option to replace. Similar to the file system in macOS for example where it doesnt allow 2 folders with the same name at a particular destination. Issue for that created here: #4754
Referral Link: https://github.com/hashgraph/guardian/issues/4753
Import Excel to check for duplicates by schema name
But I believe there is one more check which the guardian can do when the excel is imported and that is to check for duplicates and provide the user with an option to either replace the schema or keep both the files.
Referral Link: https://github.com/hashgraph/guardian/issues/4754
Deterministic compression
Implement deterministic compression for all cases in which compression is applied by Guardian.
Referral Link: https://github.com/hashgraph/guardian/issues/4931
Project Account Wallet (ex:Project Developer or Accountable Impact Organisation)
Each new Project must have a unique wallet address generated/associated upon creation.
The Project wallet must support:
Receiving funds (Hedera tokens/HBAR)
Sending funds (to users, vendors, or community members)
Holding and managing tokens (if applicable)
Transactions must be traceable back to the Project wallet for reporting/financial audit.
Referral Link: https://github.com/hashgraph/guardian/issues/5044
Need to implement best practices on Schema Cycle
We need to implement and document best practices covering the following aspects of the schema lifecycle:
Schema Design & Format Guidance
Explain how to design schemas that align with Guardian requirements.
Describe valid formats and structure (e.g., JSON Schema).
Outline file format expectations for importing into Guardian.
Manual Schema Creation in Guardian
Step-by-step process to create schemas directly in the Guardian UI.
Include tips for defining required fields, types, and constraints.
Emphasize validation logic to reduce submission errors.
Schema Mapping
When and why to map schemas.
Best practices for setting up mapping relationships (if applicable).
Examples of mapped vs. unmapped use cases.
Referral Link: https://github.com/hashgraph/guardian/issues/5062
Update Walkthroughs in Documentation
A clear and concise description of what you expected to happen.
Referral Link: https://github.com/hashgraph/guardian/issues/4507
Graphical View of formula linked definitions
Add the capability to display dependencies and relationships of data feeding into Formula definitions as a diagram similar to 'schema tree view' or 'statistics'.
Color code (or in other way identify) the data points based on:
their values (missing/default/as suggested/not-null)
type (data structure/scalar value)
in the future other criteria (e.g. "outside of 'normal' range")
Referral Link: https://github.com/hashgraph/guardian/issues/4730
Capture/replay and compare data of published policies
Introduce the capability to record and publish 'runs' of the policy for published policies such that it would be possible to replay these runs locally (in dry-run mode) and compare the results.
Additionally the runs need to be secured as a certified artifact which can be undeniably attributed to an instance of the Guardian and Standard Registry in it. Thus it would provides additional execution environment verification tool for auditors etc potentially other interested parties.
Make the recording of the runs for published policies executions 'on' by default (which can be disabled by the user), with an option to publish the final 'runs' artifact on IPFS which is also 'on' by default.
Referral Link: https://github.com/hashgraph/guardian/issues/3008
Last updated