Roadmap

Feature	Release month	Develop branch?	Released?	Release Version
Development of AMS-I.E and Mass Comparison on Cookstove	July 2024	Yes	Yes	2.27
Indexer API	July 2024	Yes	Yes	2.27
Development of VMR0006	July 2024	Yes	Yes	2.27
Filtering data for blocks is stateful API, introduce stateless data filters for API usage.	July 2024	Yes	Yes	2.27
Auto-testing community submitted policies	October 2024	Yes	Yes	3.0
Code audit: support and resolution of issues	October 2024	Yes	Yes	3.0
GHG Scorecards Research	October 2024	Yes	Yes	3.0
Token action block to work with token templates	October 2024	Yes	Yes	3.0
Different token IDs for different projects by the same policy	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
Global Carbon Council (GCC) GCCM001	October 2024	Yes	Yes	3.0
Default values for schema-defined fields	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
Guardian analytics: bottom-up data traceability	October 2024	Yes	Yes	3.0
API versioning and support/deprecation schedule	October 2024	Yes	Yes	3.0
Data Parameterization and Conditional Review Logic	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
Climate Action Reserve's U.S. Landfill Protocol	January 2025	Yes	Yes	3.1
Scope 3/PCF Referencing Demo (Methodology Breakdown)	January 2025	Yes	Yes	3.1
Development of AMS-I.C	January 2025	Yes	Yes	3.1
API facilities to retrieve unique references (IDs) of results for API-triggered operations	January 2025	Yes	Yes	3.1
Guardian analytics: labels and top down data way points	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
Enhancements and Bugs of Indexer	January 2025	Yes	Yes	3.1
Formula Linked Definitions & Schema Tree Enhancement	January 2025	Yes	Yes	3.1
Dry-run policy execution 'savepoints' - restart policy dry-run from the list of 'saved' places	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
Add policy support for more than one external data block	May 2025	Yes	Yes	3.2
Firing external event when minting process is finished	May 2025	Yes	Yes	3.2
Establish deprecation policy for architectural APIs	May 2025	Yes	Yes	3.2
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
Add capabilities to display complex geoJSON shapes superimposed on maps	May 2025	Yes	Yes	3.2
Weak Default configuration	May 2025	Yes	Yes	3.2
System Logs Accessible by All Registries	May 2025	Yes	Yes	3.2
Development of VM0042 v2.1: Improved Agricultural Land Management	May 2025	Yes	Yes	3.2
Manual trigger of re-indexing for specific policy, SR, token	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
Accessing a Guardian policy from a Guardian instance other than the publishing instance	May 2025	Yes	Yes	3.2
Exporting Project Data in CSV format	July 2025	Yes	Yes	3.3
Missing Authentication between Services	July 2025	Yes	Yes	3.3
Server-Side Request Forgery (SSRF) in Request Data module	July 2025	Yes	Yes	3.3
No Password Policy	July 2025	Yes	Yes	3.3
Development of VM0033	July 2025	Yes	Yes	3.3
Detailed Research on Indexer Enhancements	July 2025	Yes	Yes	3.3
Guardian policy embedded code testing/debugging facility for Custom Logic, Calculate, etc blocks	July 2025	Yes	Yes	3.3
Substitute Google maps API in Guardian UI with an OSS alternative	July 2025	Yes	Yes	3.3
Outdated Software/Libraries	July 2025	Yes	Yes	3.3
Identifying, Implementing and Integrating 3rd Party data resources	July 2025	Yes	Yes	3.3
Authorization Headers Potentially Leaked through IPFS in Request Data Module	July 2025	Yes	Yes	3.3
Facilities to use specialist math tooling (such as R language) for calculatio ns in Guardian Policies .	July 2025	Yes	Yes	3.3
Payload Shapefile Ingestion	August 2025	Yes	Yes	3.4
Improvement in the error handling for excel schema exports	August 2025	Yes	Yes	3.4
Dry-run savepoint[s] to survive exit and policy editing	August 2025	Yes	Yes	3.4
Locations Data Field enhancement	August 2025	Yes	Yes	3.4
SLA Ticket Import and Policy Publish Performance in Guardian	August 2025	Yes	Yes	3.4
Validation for project data submission	September 2025	Yes	Yes	3.4
Guardian Form UI Improvements	September 2025	Yes	Yes	3.4
Add an option to hide some buttons in case the policy is discontinued	September 2025	Yes	Yes	3.4
Make testing easier for subflows	September 2025	Yes	Yes	3.4
Complex iterative review and approval workflows​	October 2025	Yes	Yes	3.4
Policy warnings	October 2025	Yes	Yes	3.4
Import Excel to check for duplicates by schema name​	October 2025	Yes	Yes	3.4
Project (Relayer) Account (ex:Project Developer or Accountable Impact Organization)	October 2025	Yes	Yes	3.4
Nested schemas for complex conditions	October 2025	Yes	Yes	3.4
Need to implement best practices on Schema Cycle	October 2025	Yes	Yes	3.4
Update Walkthroughs in Documentation	October 2025	Yes	Yes	3.4
Schema deletion with child schemas	October 2025	Yes	Yes	3.4
Capability to retire tokens by serial number	October 2025	Yes	Yes	3.4
Option to delete all schemas for a particular policy in Draft stage​	October 2025	Yes	Yes	3.4
Next phase of 'Tools' evolution in Guardian Policies	November 2025
Development of VM0050: Energy Efficiency and Fuel-Switch Measures in Cookstoves, v1.0*	November 2025
Implementing Artifacts such as Schemas/Policies/tokens Deletion all at once​	November 2025
Graphical View of formula linked definitions	November 2025
Capture/replay and compare data of published policies	November 2025
Formula-linked definitions enhancements​	November 2025
Development of AMS-II.C: Demand-side energy efficiency activities for specific technologies*	November 2025
Development of VM0045: Improved Forest Management Using Dynamic Matched Baselines from National Forest Inventories, v1.2*	November 2025
Development of AR-ACM0003 : Afforestation and reforestation of lands except wetlands - Version 2.0*	November 2025
Development of VM0051 : Improved Management in Rice Production Systems, v1.0*	November 2025
Guardian as a multi-workflow engine for independent data streams​	December 2025
Tamper-resistant Policy and Module export/import	December 2025
Data Entry Updatability	December 2025
Development of ACM0022: Alternative waste treatment processes --- Version 3.0*	December 2025
Development of AMS-III.C.: Emission reductions by electric and hybrid vehicles --- Version 16.0*	December 2025
Development of AMS-III.F.: Avoidance of methane emissions through controlled biological treatment of biomass --- Version 8.0*	December 2025
Fine grained Policy workflow certification labels​	January 2026
Extend Policy definition language to include a Formula calculations block​	January 2026
On-demand state proof generation for critical Guardian operations	January 2026
Development of VM0008 Weatherization of Single Family and Multi-Family Buildings, v1.2*	January 2026
Development of VM0043 CO2 Utilization in Concrete Production, v1.1*	January 2026
Development of VM0041 Methodology for the Reduction of Enteric Methane Emissions from Ruminants through the Use of Feed Ingredients, v2.0*	January 2026
Development of VM0044 Biochar Utilization in Soil and Non-Soil Applications, v1.2*	January 2026
Development of ACM0008: Abatement of methane from coal mines --- Version 8.0*	February 2026
Development of ACM0009: Fuel switching from coal or petroleum fuel to natural gas --- Version 5.0*	February 2026
Development of AMS-II.J.: Demand-side activities for efficient lighting technologies --- Version 8.0*	March 20

Note: The above items marked as "*"are subject to change.

Upcoming Releases

--— August 2025 ----

Payload Shapefile Ingestion

Make the payload ingest shapefiles, KML etc.

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

Documentation Link: https://docs.hedera.com/guardian/guardian/standard-registry/schemas/how-to-handle-large-location-files

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

1. 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.

2. Enable to existence of multiple 'savepoints' per policy

3. Enable policy authors to choose when savepoint to apply on each policy dry-run session.

4. Users can clean-up savepoints by deleting them individually, or choosing to 'Delete All'

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

Documentation Link: https://docs.hedera.com/guardian/guardian/standard-registry/policies/savepoints/demo-using-ui

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

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

Add an option to hide some buttons in case the policy is discontinued

• Policy developers can flag a button as available only if the policy is not discontinued.

• Buttons flagged as hide/WhenDiscontinued won't be displayed in the webUI when the policy is discontinued

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

Documentation Link: https://docs.hedera.com/guardian/guardian/standard-registry/policies/policy-creation/introduction/buttonblock

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.

1. 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.

2. 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

3. 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.

4. 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

Documentation Link: https://docs.hedera.com/guardian/guardian/standard-registry/schemas/available-schema-types/table-data-input-field

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

Documentation Link: https://docs.hedera.com/guardian/guardian/complex-iterative-review-and-approval-workflows

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

Documentation Link: https://docs.hedera.com/guardian/guardian/standard-registry/policies/policy-warnings

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

Documentation Link: https://docs.hedera.com/guardian/guardian/standard-registry/schemas/deleting-schema#id-2.1-deleting-schemas-with-child-schemas

Project (Relayer) Account (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

Documentation Link: https://docs.hedera.com/guardian/guardian/standard-registry/project-account-relayer-account/demo-using-ui

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

Documentation Link: https://docs.hedera.com/guardian/guardian/standard-registry/schemas/best-practices-to-implement-schema

Update Walkthroughs in Documentation

A clear and concise description of what you expected to happen.

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

Documentation Link: https://docs.hedera.com/guardian/guardian/readme/vm0033-api-workthrough

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

Documentation Link: https://docs.hedera.com/guardian/guardian/standard-registry/schemas/deleting-schema#id-2.3-deleting-all-schemas

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

Nested schemas for complex conditions

• Cross-sub-schema referencing: - Conditions should be able to reference fields located in other sub-schemas or sections. - Example: A “Parameters for Validation” field’s visibility or requirement should depend on the “Application of Methodology” field located in a different sub-schema.

• Multi-field logic: - A single condition should support evaluation of multiple fields simultaneously. - Example: A field becomes visible or required only when both “GHG Sources/Carbon Pools” and “Temporal Boundary” fields meet specific values.

• Chained conditional logic (presentation order): - Conditional fields should be able to reference other conditional fields, allowing a sequential display order. - Example: - If Field 1 is true → show Field 2. - If Field 2 is true → show Field 3.

• Dynamic updates: - When a user changes a field value, all dependent conditions across the entire schema should re-evaluate in real time. - This ensures immediate UI updates for visibility and requirement changes.

• Automatic data reset: - If a field becomes hidden due to a condition change, all data previously entered in that field should automatically clear. - This avoids invalid or inconsistent state retention.

• User guidance and clarity: - Sequential logic and real-time updates should create a natural flow for users. - Only relevant questions are displayed based on prior responses, improving data accuracy and reducing confusion.

Referral Link: https://github.com/hashgraph/guardian/issues/5344 Documentation Link: https://docs.hedera.com/guardian/guardian/standard-registry/schemas/creating-system-schema-using-ui#id-4.-define-schema-fields

---November---

Implementing Artifacts such as Schemas/Policies/tokens Deletion all at once​

1. Create a checkbox at the top of the schema/policy/token table, which will allow to select all the artifacts.

2. 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

Documentation Link: TBD

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

Formula-linked definitions enhancements

1. "Name" column in formula records table should be wider. Now it's unreadable

2. After creating a formula record I need to find it in a list to edit. It's quite difficult according to point 1

3. On the top of a formula edit page I see button "Back to policies" but button redirects me to list of formulas

4. I cannot move a formula item when I'm scrolling the page. Drag-n-drop works only in visible part of screen and it's impossible to add const/variable and move it to the top of a long list

5. I cannot re-use constants which are defined in another formula in relationships. It makes me to define same constants in different formula records

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

---December---

Guardian as a multi-workflow engine for independent data streams

Guardian should be able to inject machine-readable product data and process them simultaneously in multiple independent Policy processing streams, each with an independent ruleset, however with the possibility to coordinate and cross reference the artifacts produced by these streams, all while maintaining and referencing the single original instance of the 'master' data.

1. Extend and adapt the topics architecture to support multi-workflow processing of the master data (from a topic)

2. Develop a multi-streams Guardian policy coordination mechanisms which were in a single instance and across different Guardian instances, which include

   • trigger workflow execution based on an event such as NFT issuance, data events.

   • pause and wait for the availability of specific data

3. Introduce additional (to token issuance) Guardian policy actions to enable 'final' stages of policy streams executions, such as:

   • payment execution

   • certificate (invoice, bill of lading, etc) issuance

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

Tamper-resistant Policy and Module export/import

• Introduce the signing of Policies and Policy Modules such that on import their authenticity is evaluated - which proves that they have not been tampered with.

• In an indicator into the Policy grid (or other appropriate place) which would show whether the Policies (and/or their elements such as schemas, modules etc) that have been imported (whether from the file system or IPFS) have been modified from their original state.

• Introduce the ability to compare all Policies which have been 'created' in the particular instance by import with their original 'just after import' state.

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

Data Entry Updatability

An ability to make schema data that is non-material to calculations updatable, while not changing the token issuance in flight.

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

Fine grained Policy workflow certification labels

Introduce the capability to select arbitrary sections of Policy workflows and then assign tags to them, which should result in these tags being visible whenever the policy sections or any artefacts produced in these sections are viewed by users such that:

• Policy sections can be selected and assessed/tagged after the policy is published

• Assessment/tagging can be done by users who are not policy authors

• Tags then applied retrospectively to artefacts produced by the 'target' section of the Policy (where the tag has been applied)

• Tags are visible whenever users view artefacts and/or policy in Guardian and Indexer, including trustchain view

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

Extend Policy definition language to include a Formula calculations block​

Introduce a Formula calculation block which would:

• Allow Policy authors to input mathematical formulas directly into the policy (using Gurdian UI formula editor) in the standard mathematical notation (https://cortexjs.io/mathlive/editor/)

• Enable policy authors to bind variables/parameters in these formulas to data (fields in schemas) for inputs/outputs to integrate the block into the Policy workflow

• At Policy run time perform the calculations directly without any additional input etc from users (https://arthanzel.github.io/evaluatex/)

Extend Guardian UI to:

• Whenever the result of such calculation is shown to the user to also display the formula definition in the standard math notation

• Also display the values of the variables/parameters in the formula which were used to calculate these results

• Enable users to navigate to the data sources of these values (used for the calculations) by providing links to the required levels dept.

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

On-demand state proof generation for critical Guardian operations

• Introduce the ability to trigger Hedera State Proof generation from Guardian interface for particular actions/operations or the general status of the Policy.

• State proofs are to be generated and presented to users for download. Guardian will not keep any registry or store them on the system.

• Introduce UI and the backend functionality to verify Hedera State Proofs generated by Guardian, ensure the long-term compatibility of this functionality.

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

Previous Releases