> For the complete documentation index, see [llms.txt](https://guardian.hedera.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guardian.hedera.com/updates/2026/updates-2026.md).

# Platform Updates 2026

A summary of our latest releases, events, and improvements to the Guardian Platform.

{% updates format="full" %}
{% update date="2026-08-17" tags="new-releases,improvements,fixes" %}

## Guardian 3.7.0

**Announcing Hedera Guardian 3.7**

{% embed url="<https://docs.google.com/presentation/d/e/2PACX-1vRw6ki6qFAEbEji2aJRnFejmxI8eMd2bPNq1SVVn_1BeIRIT-qZN6HRvXBUNr-s7RpK1j7cBShEeZs8/pubembed?delayms=3000&loop=false&start=false>" %}

The [Hedera Guardian 3.7 release is now available](https://github.com/hashgraph/guardian/releases/tag/3.6.0), focusing on schema authoring, policy editing, and a better getting started experience. This release introduces Schema Templates, a redesigned schema editor and Policy Configurator, first-steps onboarding, refreshed navigation, and many anticipated new authoring improvements. Community contributors added a much anticipated Organization entity, a new explorer called the Sustainability Atlas, and numerous stability and performance improvements.

<a href="https://www.loom.com/share/02b4f28f07dd4a958c9926f7dc44b409" class="button primary" data-icon="circle-play">Watch recording</a>

### Schema Templates & Editor Redesign

<table data-card-size="large" data-column-title-hidden data-card-wrap="false" data-view="cards"><thead><tr><th data-hidden data-card-cover data-type="image">Cover image</th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td data-object-fit="fill"><a href="https://1628665597-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPNzY5zOHjim5noRwV71Q%2Fuploads%2FvM77N2haNq76s4k6nMJr%2F1189d3b1d1fc48b5846e6beba2e6b475-681941b83aa946da-full-play.gif?alt=media&amp;token=4b114126-af57-4c82-8a93-3dae6d5e791e">1189d3b1d1fc48b5846e6beba2e6b475-681941b83aa946da-full-play.gif</a></td><td><a href="https://www.loom.com/share/1189d3b1d1fc48b5846e6beba2e6b475">https://www.loom.com/share/1189d3b1d1fc48b5846e6beba2e6b475</a></td></tr></tbody></table>

The schema editor has been rebuilt with a live form preview, drag-and-drop field reordering, and clearer sub-schema visualization. Schema Templates are a new entity type that lets authors define schemas once and\
apply them across policies with field-level locking and version-controlled updates. [#6504](https://github.com/hashgraph/guardian/issues/6504) [#6422](https://github.com/hashgraph/guardian/issues/6422)

<a href="/guardian/workspace/schema-templates.md" class="button primary">View docs</a>

### Cross Document Source Validation

<table data-card-size="large" data-column-title-hidden data-card-wrap="false" data-view="cards"><thead><tr><th data-hidden></th><th data-hidden data-card-cover data-type="image">Cover image</th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td></td><td><a href="https://cdn.loom.com/sessions/thumbnails/27689a407c7748cba1ce77fa2e7ffd38-f1f3a2697f788f18-full-play.gif#t=0.1">https://cdn.loom.com/sessions/thumbnails/27689a407c7748cba1ce77fa2e7ffd38-f1f3a2697f788f18-full-play.gif#t=0.1</a></td><td><a href="https://www.loom.com/share/27689a407c7748cba1ce77fa2e7ffd38">https://www.loom.com/share/27689a407c7748cba1ce77fa2e7ffd38</a></td></tr></tbody></table>

Policies can now validate a submitted document against related documents and closing a gap identified in real-world methodology work. [#6312](https://github.com/hashgraph/guardian/issues/6312)

<a href="/guardian/workspace/policies/policy-creation/introduction/documentvalidatorblock/document-validator-block-source-validations.md" class="button primary">View docs</a>

### Sub-Schema Conditions

<table data-card-size="large" data-column-title-hidden data-card-wrap="false" data-view="cards"><thead><tr><th data-hidden data-card-cover data-type="image">Cover image</th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><a href="https://cdn.loom.com/sessions/thumbnails/320df57418704624ab7b35ea6713da6d-f0be2e5fd8259062-full-play.gif#t=0.1">https://cdn.loom.com/sessions/thumbnails/320df57418704624ab7b35ea6713da6d-f0be2e5fd8259062-full-play.gif#t=0.1</a></td><td><a href="https://www.loom.com/share/320df57418704624ab7b35ea6713da6d">https://www.loom.com/share/320df57418704624ab7b35ea6713da6d</a></td></tr></tbody></table>

Conditional logic can now reach into nested sub-schema fields, not just top-level fields which gives authors much finer control over how and when parts of a form appear. [#4907](https://github.com/hashgraph/guardian/issues/4907)&#x20;

<a href="/guardian/workspace/schemas/cross-schema-conditions.md" class="button primary">View docs</a>

### Repeatable Links

<table data-card-size="large" data-column-title-hidden data-card-wrap="false" data-view="cards"><thead><tr><th data-hidden></th><th data-hidden data-card-cover data-type="image">Cover image</th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td></td><td><a href="https://cdn.loom.com/sessions/thumbnails/75c77524f5344cc2845ee059e0431953-6df0f6c419dc11cb-full-play.gif#t=0.1">https://cdn.loom.com/sessions/thumbnails/75c77524f5344cc2845ee059e0431953-6df0f6c419dc11cb-full-play.gif#t=0.1</a></td><td><a href="https://www.loom.com/share/75c77524f5344cc2845ee059e0431953">https://www.loom.com/share/75c77524f5344cc2845ee059e0431953</a></td></tr></tbody></table>

Schema fields can be repeated to appear in multiple location, keeping data entered by users in sync across related form inputs and questions. [#6509](https://github.com/hashgraph/guardian/issues/6509)

<a href="/guardian/workspace/schemas/repeatable-field-links.md" class="button primary">View docs</a>

### First Time User Experience

<table data-card-size="large" data-column-title-hidden data-card-wrap="false" data-view="cards"><thead><tr><th data-hidden data-card-cover data-type="image">Cover image</th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><a href="https://cdn.loom.com/sessions/thumbnails/77feb0c9283e4a5b81f1de42bf7369e5-2d5e0e48dce6c7df-full.jpg#t=0.1">https://cdn.loom.com/sessions/thumbnails/77feb0c9283e4a5b81f1de42bf7369e5-2d5e0e48dce6c7df-full.jpg#t=0.1</a></td><td><a href="https://www.loom.com/share/77feb0c9283e4a5b81f1de42bf7369e5">https://www.loom.com/share/77feb0c9283e4a5b81f1de42bf7369e5</a></td></tr></tbody></table>

New users now get a guided onboarding experience from the moment they sign in, alongside a refreshed login screen, navigation, and profile page. The tutorial walks users through importing a policy from the methodology library, publishing their first policy, submitting data, and inspecting verifiable credentials documents reducing the time it takes to go from setup to productive. [#6401](https://github.com/hashgraph/guardian/issues/6401), [#6355](https://github.com/hashgraph/guardian/pull/6355), [#6239](https://github.com/hashgraph/guardian/issues/6239)

### Bulk Device Registration for MECD v2.0

{% embed url="<https://www.youtube.com/watch?feature=youtu.be&si=5MvmA6MLBsIGUNF1&v=fwhB9GW2ccM>" %}

Hundreds of Metered Energy Cooking Devices can now be commissioned concurrently, with each device anchored on Hedera and publicly auditable end-to-end. Included in the Paris aligned vintage under MECD v2.0 and first project to issue credits via [Gold Standard’s dMRV](https://www.goldstandard.org/news/first-fully-digital-cookstove-carbon-credits-issued-publicly-traceable-on-hedera-guardian) program. [#6033](https://github.com/hashgraph/guardian/pull/6033)

### Policy Configurator Redesign

<figure><img src="https://1628665597-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPNzY5zOHjim5noRwV71Q%2Fuploads%2FTT5plVCU3NjT84u0iCLs%2Fimage.png?alt=media&amp;token=accb95ae-b8a0-4c4c-ac9b-08dc7f737722" alt=""><figcaption></figcaption></figure>

The Policy Configurator — Guardian's core policy-building interface — has been fully redesigned. The updated layout reduces visual clutter and aligns with the platform's current design language, so authors can focus on building rather than navigating the tool. [#3532](https://github.com/hashgraph/guardian/issues/3532)

<a href="/guardian/workspace/policies/policy-creation/policy-configurator.md" class="button primary">View docs</a>

### Sustainability Atlas

{% embed url="<https://youtu.be/pmz0p26PrCM>" %}

A new on-chain explorer giving a real-time view of the Guardian network — registries, methodologies, projects, and issuances — now live on mainnet. Contributed by the [Xeptagon](https://xeptagon.com/?utm_source=guardian) team.&#x20;

<a href="/explorers/sustainability-atlas.md" class="button primary">View docs</a><a href="https://atlas.xeptagon.com/?utm_source=guardian" class="button primary">Visit Sustainability Atlas</a>

### Excel Guidance Tab

Exported Excel schema files now include a built-in README tab explaining the workbook layout, every field, and accepted values. Authors can fill in their first schema without leaving the spreadsheet or consulting\
external documentation. [#5587](https://github.com/hashgraph/guardian/issues/5587)

### Organizations

Users can now be grouped into named Organizations, each with its own Hedera account, DID, and role-based permissions. Assign a policy to an organization and all members get instant access, with no per-member\
policy assignment required. [#5802](https://github.com/hashgraph/guardian/issues/5802)

<details>

<summary>Bug Fixes</summary>

* Dry-run mock data: schema mock recording now runs in-process with batch DB insertion — 5-minute start times on large schema sets now resolve in seconds [#6535](https://github.com/hashgraph/guardian/issues/6535) / [PR #6536](https://github.com/hashgraph/guardian/pull/6536) + [PR #6533](https://github.com/hashgraph/guardian/pull/6533)
* customLogicBlock JavaScript runtime exceptions now surface to UI [#6419](https://github.com/hashgraph/guardian/issues/6419) — *community contribution: Climission*
* customLogicBlock execution errors no longer silently swallowed [#6271](https://github.com/hashgraph/guardian/issues/6271) — *community contribution: Climission*
* GridFS write errors no longer silent — *community contribution: Climission* [PR #6487](https://github.com/hashgraph/guardian/pull/6487)
* Dry-run IPFS 404 request loop eliminated — *community contribution: Climission* [PR #6411](https://github.com/hashgraph/guardian/pull/6411)
* Dry-run virtual user scoped per session — *community contribution: Climission* [PR #6328](https://github.com/hashgraph/guardian/pull/6328)
* GridFS connection added to queue-service startup — *community contribution: Climission* [PR #6370](https://github.com/hashgraph/guardian/pull/6370)
* Step block unavailable flash fixed — *community contribution: Climission* [PR #6447](https://github.com/hashgraph/guardian/pull/6447)
* Policy import no longer silently rebinds sub-schemas by title match [#6298](https://github.com/hashgraph/guardian/issues/6298)
* Page now refreshes after document submission without manual reload [#6383](https://github.com/hashgraph/guardian/issues/6383)
* Default branding applies on load; branding fetch deduplicated; no error toasts on fetch failure [#6323](https://github.com/hashgraph/guardian/issues/6323)
* Schema test data cleared/updated when field type changes [#6315](https://github.com/hashgraph/guardian/issues/6315)
* Navigation menu no longer jumps when opening sub-menus [#3117](https://github.com/hashgraph/guardian/issues/3117)
* Navigation items no longer collapse unexpectedly [#6404](https://github.com/hashgraph/guardian/issues/6404)
* Old UI updated: Tokens > Retirement [#5538](https://github.com/hashgraph/guardian/issues/5538), Manage Contracts [#5506](https://github.com/hashgraph/guardian/issues/5506), Policy Comparison (Schemas) [#3553](https://github.com/hashgraph/guardian/issues/3553)
* Stored XSS in branding company name fixed (CVE-2026-22674): company name was rendered via `innerHTML`; replaced with safe text assignment [PR #6190](https://github.com/hashgraph/guardian/pull/6190)
* BbsBlsSignature2020 (EVC) signing restored — broken after `@transmute → @digitalbazaar` migration; EVC schemas can now sign and verify correctly [PR #6273](https://github.com/hashgraph/guardian/pull/6273)
* Large policy publish payloads offloaded to GridFS — prevents crash at MongoDB's 16 MB BSON document limit on queue-service [PR #6275](https://github.com/hashgraph/guardian/pull/6275)
* Unhandled promise rejections no longer crash services — process-level error handlers prevent a stray rejection from terminating guardian-service or api-gateway [PR #6314](https://github.com/hashgraph/guardian/pull/6314) / [PR #6321](https://github.com/hashgraph/guardian/pull/6321)
* Migrations serialized across replicas with a Mongo lock — concurrent boot migrations on multi-replica deployments no longer race [PR #6340](https://github.com/hashgraph/guardian/pull/6340)
* Policy messages fast-fail when policy not loaded — previously waited out the full timeout (up to 5 min) before reporting unavailable [PR #6341](https://github.com/hashgraph/guardian/pull/6341)
* Pathological VC canonicalization on large GeoJSON geometries fixed — large `MultiPolygon` fields were taking tens of seconds and causing multi-GB memory spikes; geometry now signed as a `@json` literal [PR #6251](https://github.com/hashgraph/guardian/pull/6251)
* Stale SPA after redeploy fixed — `index.html` now served with no-cache headers so browsers always load the latest build [PR #6361](https://github.com/hashgraph/guardian/pull/6361)

**Schema Editor / Templates**

* Schema templates: "Save all" stopped working after several edits to a schema ([#6629](https://github.com/hashgraph/guardian/issues/6629))
* Schema list: Create and Publish buttons were clipped ([#6613](https://github.com/hashgraph/guardian/issues/6613))
* Deleted schemas were still served by a stale schema-listing cache for up to 10 minutes ([#6626](https://github.com/hashgraph/guardian/issues/6626))
* Schema import dialog: errors and warnings now surfaced prominently ([#6641](https://github.com/hashgraph/guardian/issues/6641))
* Conditional fields rendering in reverse order fixed ([#6622](https://github.com/hashgraph/guardian/issues/6622))
* Nested sub-schemas with conditional visibility failed to render, blocking form submission in dry-run with payload ([#6562](https://github.com/hashgraph/guardian/issues/6562))
* Geo cascade fields: value could not be changed once selected ([#6592](https://github.com/hashgraph/guardian/issues/6592))

**Policy Configurator / Blocks**

* MathBlock path autocomplete not resolving input variable schema paths correctly
* Switch Block condition field not rendering existing value from policy JSON ([#6492](https://github.com/hashgraph/guardian/issues/6492))
* Blocks library: static color coding now preserved when brand colors are updated ([#6595](https://github.com/hashgraph/guardian/issues/6595))
* documentValidatorBlock: array field path resolution and dual-source conditions fixed ([#6546](https://github.com/hashgraph/guardian/issues/6546))
* Components and policy properties no longer shown in the UI when in JSON/YAML mode

**Dry-Run**

* Progress bar added during dry-run setup ([#6600](https://github.com/hashgraph/guardian/issues/6600))
* Frame flicker fixed when burger menu closed during dry-run ([#6604](https://github.com/hashgraph/guardian/issues/6604))

**Navigation / Feature Flag / Profile**

* Feature Flag banner z-order overlap with Policy Configurator and Schema Editor fixed ([#6560](https://github.com/hashgraph/guardian/issues/6560))
* Navigation menu labels and page help text clarified ([#6538](https://github.com/hashgraph/guardian/issues/6538))
* Docs widget no longer shown when disabled in profile ([#6627](https://github.com/hashgraph/guardian/issues/6627))

**Policy Management**

* Remote policy public link naming standardized to "Policy Public ID" ([#6599](https://github.com/hashgraph/guardian/issues/6599))
* Policy action menu: schema items left-aligned ([#6596](https://github.com/hashgraph/guardian/issues/6596))
* Export policy dialog no longer stays open after download
* Draft token no longer orphaned when a policy is deleted ([#6610](https://github.com/hashgraph/guardian/issues/6610))
* "List of policies" link no longer misplaced when opening a policy ([#6612](https://github.com/hashgraph/guardian/issues/6612))
* UI no longer requires a double-click to appear when opening a policy ([#6611](https://github.com/hashgraph/guardian/issues/6611))
* Comment count now refreshes without re-entering the policy ([#6606](https://github.com/hashgraph/guardian/issues/6606))
* Save and restore draft buttons no longer disappear while scrolling ([#6605](https://github.com/hashgraph/guardian/issues/6605))

**Other improvements**

* MAX\_TRANSACTION\_FEE not applied to wipe and retirement contracts ([#6591](https://github.com/hashgraph/guardian/issues/6591))
* Token ID link not opening HashScan ([#6601](https://github.com/hashgraph/guardian/issues/6601))
* AI Search hidden when not configured ([#6602](https://github.com/hashgraph/guardian/issues/6602))
* Indexer: NATS connection now retries indefinitely instead of giving up
* Indexer: allOf conditions with no `if.properties` now skipped instead of erroring
* Related policies now sorted by version when seeding previousVersion
* Assessment values now read correctly from a non-array credentialSubje

</details>

<details>

<summary>Other Enhancements</summary>

**Schema / Excel**

* Cross-schema source validation in documentValidatorBlock [#6312](https://github.com/hashgraph/guardian/issues/6312)
* New field types: Country, Continent, State/Province with cascading dependencies [#6381](https://github.com/hashgraph/guardian/issues/6381)
* Dynamic Calculation Inputs for Multiple Locations [#6506](https://github.com/hashgraph/guardian/issues/6506)
* Inline sub-schemas and consolidated enum tab in Excel schema templates [#5584](https://github.com/hashgraph/guardian/issues/5584)
* Guidance tab in generated Excel schema templates [#5587](https://github.com/hashgraph/guardian/issues/5587)
* Contextual Excel upload validation error messages [#5582](https://github.com/hashgraph/guardian/issues/5582)

**Policy authoring**

* MathBlock path autocomplete [#6326](https://github.com/hashgraph/guardian/issues/6326)
* Policy comparison value columns now use full available width [#3716](https://github.com/hashgraph/guardian/issues/3716)
* In-app User Guide links on general pages and complex forms [#4072](https://github.com/hashgraph/guardian/issues/4072)
* Dry-Run Mock Data is now opt-in: a "Move to Dry-Run" dialog replaces the forced enable prompt, with a per-policy "don't ask again" option [PR #6518](https://github.com/hashgraph/guardian/pull/6518)
* Request form drafts can now be exported to a local JSON file and restored — portable alternative to server and autosave drafts [PR #6353](https://github.com/hashgraph/guardian/pull/6353)
* Policy Manifest spec — machine-readable metadata contract for the methodology library [#6031](https://github.com/hashgraph/guardian/issues/6031)

**Navigation / UI**

* Dark mode — theme variables, PrimeNG preset, and user-selectable toggle [PR #6212](https://github.com/hashgraph/guardian/pull/6212)
* Login page modernized: branded gradient banner, Hedera watermark, card-based form [PR #6355](https://github.com/hashgraph/guardian/pull/6355)
* Navigation redesign: design tokens, PrimeIcons, vertical/horizontal layout toggle [#6401](https://github.com/hashgraph/guardian/issues/6401)
* Hedera navigation group: Tokens, Contracts, and Relayer Accounts grouped under "Hedera" [#6485](https://github.com/hashgraph/guardian/issues/6485)
* Feature Flag toggle for future UI features [#6254](https://github.com/hashgraph/guardian/issues/6254)
* Profile page redesigned: identity and settings consolidated into a card layout with copy-to-clipboard for DID and Hedera IDs [PR #6234](https://github.com/hashgraph/guardian/pull/6234)

**Platform**

* Angular 18 → 21 / PrimeNG 17 → 21 migration [#6132](https://github.com/hashgraph/guardian/issues/6132)
* Node.js 20 → 24 LTS migration [#5537](https://github.com/hashgraph/guardian/issues/5537)
* Yarn Classic → Yarn Berry v4 migration [#6184](https://github.com/hashgraph/guardian/issues/6184)

**Developer**

* Auto-updating Gitbook API documentation via GitHub Actions [#5619](https://github.com/hashgraph/guardian/issues/5619)
* Scalar API reference replaces Swagger UI at `/api-docs`: branded, sidebar grouped by tag; `/api-docs-json` and `/api-docs-yaml` spec endpoints unchanged [PR #6513](https://github.com/hashgraph/guardian/pull/6513)
* Policy grid actions API: four endpoints under `/policies/:policyId/grids` — access role-scoped at the policy engine level [#5797](https://github.com/hashgraph/guardian/issues/5797) / [PR #6498](https://github.com/hashgraph/guardian/pull/6498) — *community contribution: Xeptagon*
* Tool import permissions extensible to non-SR users [#6282](https://github.com/hashgraph/guardian/issues/6282)
* Policy schema lazy-loading: on-demand schema loading reduces memory and startup time — *community contribution: Climission* [PR #6489](https://github.com/hashgraph/guardian/pull/6489)
* Schema reference in form block data: eliminates tens-of-MB payloads on large schemas — *community contribution: Climission* [PR #6402](https://github.com/hashgraph/guardian/pull/6402)
* Improved IPFS policy import error message [#6423](https://github.com/hashgraph/guardian/issues/6423) — *community contribution: Climission*
* Dynamic Read API endpoint for policy data: external consumers can query Guardian policy data via dynamic MongoDB filter fields — *community contribution: gayanath8* [#5796](https://github.com/hashgraph/guardian/issues/5796) / [PR #6074](https://github.com/hashgraph/guardian/pull/6074)

</details>
{% endupdate %}

{% update date="2026-06-01" tags="feature,improvement,fix,new-releases,improvements,fixes" %}

## Guardian 3.6.0

**Announcing Hedera Guardian 3.6**

{% embed url="<https://docs.google.com/presentation/d/19Tg7RweZirf1Lo-fQdGbCng4fonHT4lehZlGYqxVMtQ/edit?usp=drive_link>" %}

The [Hedera Guardian 3.6 release is now available](https://github.com/hashgraph/guardian/releases/tag/3.6.0). After publishing a policy, registry operators and methodology authors need repeatable, automated ways to confirm that their published work behave as intended after iterative policy changes, to the Guardian, or any underlying system component. In this release we've introduced Policy Integrity Tests to ensure policies continue producing expected outputs as they evolve or as the Guardian platform changes. This release also adds runtime parameter editing, reducing the overhead of managing live integrations. Community contributors added multi-factor authentication, schema tooling improvements, expanded developer API support, and more.

<a href="https://drive.google.com/file/d/1xXcj5AR2CudncwhSqSkrEqX0hug7U10A/view?usp=drive_link" class="button primary" data-icon="youtube">View Recording</a>

### Policy Integrity Tests

{% embed url="<https://www.loom.com/share/5be378e66aa144e780a40c6cc1ef0b6d>" %}

Standard registries and registry operators now have a native way to verify that policies continue to produce the outputs they were designed to produce — even as policies are edited, Guardian versions change, or platform dependencies shift.

Building on Guardian's existing record-and-replay capability, Policy Integrity Tests let authors declare scope: the input documents submitted to the policy, and the specific output documents expected in return. When a test runs, Guardian evaluates whether the declared outputs match — passing if they do, failing with inspectable detail if they don't. This makes tests stable across edits and upgrades — they only fail when the logic the author actually cares about changes.

Tests are saved as named baselines and can be re-run at any point: before publishing a policy edit, after a Guardian upgrade, or as part of a regular integrity check. Tests are accessible from both the UI and the API, and results are managed from a single dialog with pass/fail status and inspectable output.

<a href="https://guardian.hedera.com/3.6.0/guardian/standard-registry/policies/dry-run/policy-integrity-tests" class="button primary">View Docs</a>

### Policy API Documentation & DMRV Aliases

{% embed url="<https://www.loom.com/share/f423f9c64206406889e00b5ea901f9fb>" %}

Policy authors can define clean, human-readable API endpoint aliases for their policies, giving each integration point a simple, descriptive name instead of a raw internal URL. These aliases, along with descriptions, can be configured directly in the policy editor and are published as browsable documentation, making it easier for external systems and third-party developers to integrate with a policy's API.

<a href="https://guardian.hedera.com/3.6.0/guardian/standard-registry/policies/policy-api-documentation-and-dmrv-aliases" class="button primary">View Docs</a>

### Adjust Policy Parameters without Republishing

Standard registries and registry operators frequently need to adjust policy parameters — calculation thresholds, deadline windows, configuration inputs — after a methodology is already running at scale. Until now, any such change required publishing a new policy version, which meant data migration overhead and operational disruption to active policies. With this release, policy authors can designate specific parameters as runtime-editable, allowing authorized users to update values in place without touching the policy version or migrating historical data. Active methodologies continue running uninterrupted, and the change is reflected immediately without republishing.

<a href="https://guardian.hedera.com/3.6.0/guardian/standard-registry/policies/5539-editing-policy-parameters-at-runtime" class="button primary">View Docs</a>

### Easier Integrations Overall

This release takes a meaningful step toward making Guardian easier to integrate with. Setting up a new user now takes a single API call instead of three chained operations, policy block documentation is auto-generated so it's always accurate, and block completion events let external systems react to policy execution without polling. Token transfers are now directly accessible outside policy workflows, and top-level convenience methods cut the boilerplate for common tasks. For developers integrating with Guardian, that's a noticeably lower barrier across the board.&#x20;

([#5795](https://github.com/hashgraph/guardian/issues/5795),[ #5955](https://github.com/hashgraph/guardian/issues/5955),[ #5799](https://github.com/hashgraph/guardian/issues/5799),[ #5800](https://github.com/hashgraph/guardian/issues/5800),[ #1987](https://github.com/hashgraph/guardian/issues/1987),[ #3642](https://github.com/hashgraph/guardian/issues/3642))

### New Features

* Policy Block API documentation is now auto-generated directly from block configurations, so external developers always have documentation that reflects the actual implementation ([#5955](https://github.com/hashgraph/guardian/issues/5955)).
* The Math Block (aka formula calculation block) now supports nested arrays, multiple conditions, and special characters in variable names, with additional Formula Linked Definition (FDL) usability improvements ([#5928](https://github.com/hashgraph/guardian/issues/5928),[ #5980](https://github.com/hashgraph/guardian/issues/5980)).

<details>

<summary>Bounties &#x26; Community Contributions</summary>

This release includes a broad set of enhancements contributed through our bounty program and community. Big thank you to the teams at \[Xeptagon, Climission, Atec, … ]

* Multi-Factor Authentication is now supported for Guardian logins ([#4108](https://github.com/hashgraph/guardian/issues/4108)).
* Schema tooling additions include sub-schema creation and assignment, a fix for policy binding assignment, the ability to disable policy rebinding in already-created schemas, and filter/search for schemas by ID ([#4887](https://github.com/hashgraph/guardian/issues/4887),[ #4913](https://github.com/hashgraph/guardian/issues/4913),[ #4919](https://github.com/hashgraph/guardian/issues/4919),[ #4758](https://github.com/hashgraph/guardian/issues/4758)).
* API documentation for external developers is expanded, and the Indexer now includes a dedicated view for diving into external MRV data ([#5178](https://github.com/hashgraph/guardian/issues/5178),[ #5167](https://github.com/hashgraph/guardian/issues/5167)).
* A new external event is emitted on token mint failures; Python library support in custom logic blocks is extended; token minting rounding is now configurable; policy import includes search; refresh tokens now default to a one-year expiry ([#5108](https://github.com/hashgraph/guardian/issues/5108),[ #5504](https://github.com/hashgraph/guardian/issues/5504),[ #4065](https://github.com/hashgraph/guardian/issues/4065),[ #3378](https://github.com/hashgraph/guardian/issues/3378),[ #4060](https://github.com/hashgraph/guardian/issues/4060)).
* Expressions can now be written using placeholder code within Schema UI on import, Worker Tasks are added to the permission modal, and the Dry Run API user listing is corrected ([#4905](https://github.com/hashgraph/guardian/issues/4905),[ #4438](https://github.com/hashgraph/guardian/issues/4438),[ #3642](https://github.com/hashgraph/guardian/issues/3642)).
* Xeptagon (Sustainability Atlas) contributions add API endpoints for token transfers outside policy workflows, block completion events to the Guardian event stream so external systems can react when policy blocks finish execution, and one-step API user onboarding that auto-generates a Hedera account, DID, and keys in a single call ([#5800](https://github.com/hashgraph/guardian/issues/5800),[ #5799](https://github.com/hashgraph/guardian/issues/5799),[ #5795](https://github.com/hashgraph/guardian/issues/5795)).

</details>

<details>

<summary>Bug Fixes</summary>

* Retry failed mint and transfer operations directly from the policy viewer ([#5926](https://github.com/hashgraph/guardian/issues/5926))
* IPFS misconfiguration no longer causes profile setup to hang indefinitely with no useful error message ([#5992](https://github.com/hashgraph/guardian/issues/5992)).
* CustomLogicBlock no longer receives a mutated document in event-driven fan-out scenarios, which previously caused unpredictable downstream behavior ([#5953](https://github.com/hashgraph/guardian/issues/5953)).
* Guardian now correctly creates a new initialization topic when INITIALIZATION\_TOPIC\_ID is not defined ([#4959](https://github.com/hashgraph/guardian/issues/4959)).
* The policy publication status page now remains reachable after navigating away and returning, and the notifications badge counter is corrected ([#5695](https://github.com/hashgraph/guardian/issues/5695),[ #5699](https://github.com/hashgraph/guardian/issues/5699)).

</details>

***

Explore the latest updates, join our next event, and share your thoughts with us. Your feedback plays a crucial role in helping to improve Hedera Guardian for everyone.

<a href="https://luma.com/guardian?utm_source=gitbook" class="button primary">Join Next Event</a>
{% endupdate %}

{% update date="2026-05-15" tags="feature,improvement,fix,events" %}

## Training Recap

**Developing Digital Methodologies with Guardian: VM0050 and VM0047**

<figure><img src="https://1628665597-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPNzY5zOHjim5noRwV71Q%2Fuploads%2FLuH03jMCIn04jTg8hHQb%2Fimage.png?alt=media&amp;token=d4136c23-5667-4a17-9c4c-2857d81795fb" alt=""><figcaption></figcaption></figure>

Over two sessions in April and May, [Jailine Molina](https://www.linkedin.com/in/jailine-molina/), Lead Environmental Solutions Lead at [Hashgraph](https://www.hashgraph.com/) and [Waqar Ashiq](https://ca.linkedin.com/in/waqar-ashiq-2b410193), Senior Program Officer at [Verra](http://verra.com/) walked methodology developers through what it takes to digitalize a Verra methodology end to end using the Hedera Guardian — from reading the standard to a production-ready policy that submits structured data directly to Verra's Project Hub.

The sessions used VM0050 (Energy Efficiency and Fuel-Switch Measures in Cookstoves) and VM0047 (Afforestation, Reforestation, and Revegetation) as worked examples, covering the six-step process: methodology research, workflow mapping, schema creation, policy configurator, data transformation, and end-to-end testing. Attendees saw how Guardian turns a methodology's requirements into structured data inputs, built-in calculations, and a verifiable trust chain — and how that data flows into Project Hub for Verra's review and issuance process.

The sessions also introduced the [Methodology Bounty Program](https://www.dltearth.com/news/updating-our-bounty-programme-expanding-impact-across-key-climate-methodologies) and what a complete bounty submission looks like: encoded schemas, calculations, transformation blocks, and documentation.
{% endupdate %}

{% update date="2026-05-08" tags="feature,improvement,fix,events" %}

## HederaCon Recap

**From Promise to Proven: our HederaCon panel on scaling credible climate finance**

{% embed url="<https://www.youtube.com/watch?v=U9qFa6N7rhg>" %}

At HederaCon 2026, Wes Geisenberger of Hashgraph moderated a panel on how sustainable finance moves from promise to proven outcomes — and the role DLT and networks like Hedera play in getting there. Bringing together a carbon standard, a project-origination platform, an institutional investor, and a securities exchange, the conversation centered on a single idea: capital for climate is largely ready, and the binding constraint is trust — the infrastructure to track credits across their lifecycle, strengthen MRV and auditability, and report verifiable impact end to end. Guardian came up throughout as the digital backbone for that trust layer, from digitized methodologies to tokenized carbon instruments and the traceable flow of funds to projects on the ground.

**Panelists**

* Wes Geisenberger, Hashgraph (moderator)
* Joe Dell'Orfano, [Verra](https://verra.org/staff/joe-dellorfano/)
* Raphael de Ry, [Straatos](https://www.straatos.io/)
* Bruce Keith, [Regia Capital](https://www.regiacapital.com.br/)
* Frank Mwiti, [Nairobi Securities Exchange](https://www.nse.co.ke/)
  {% endupdate %}

{% update date="2026-04-24" tags="feature,improvement,fix,events" %}

## Workshop Recap

**Shaping the next evolution of testing policy integrity**

<figure><img src="https://1628665597-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPNzY5zOHjim5noRwV71Q%2Fuploads%2FfqJa0jKANWUsaLVbuKYn%2Fimage.png?alt=media&amp;token=f979e425-6c8b-43ad-bf3e-6b2fc22bcdda" alt=""><figcaption></figcaption></figure>

Guardian's design workshops bring together policy authors, developers, and domain practitioners to stress-test early-stage thinking before it becomes code. This session focused on the next evolution of Guardian's policy testing capability — and the feedback gathered will directly shape its feature scope and UX in the upcoming 3.6 release.

The session was hosted by Guardian team members [Daniel Swid](https://www.linkedin.com/in/danielswid), [Giuseppe Bertone](https://it.linkedin.com/in/giuseppebertone), [Jailine Molina](https://www.linkedin.com/in/jailine-molina), and [Wes Geisenberger](https://www.linkedin.com/in/wesgeisenberger).

Guardian already supports automated end-to-end policy testing, allowing two versions of a policy to be compared for identical workflow outputs. The gap the team brought to the workshop: today's testing operates at the technical execution level — comparing full workflows including UUIDs and metadata that policy authors neither own nor care about. The new capability under design lets authors define what actually matters to them: specify the input, declare the expected output documents, and mark the test as passed when those outputs match — regardless of surrounding workflow differences outside the declared scope. Protecting published policies from regressions introduced by policy edits or Guardian platform updates is the core use case.

Participants were invited to validate the mental model, pressure-test the proposed interaction patterns, and surface edge cases before development begins.

See workshop details

* <https://luma.com/g9ivn494>

See related docs

* [Automated Policy Testing](https://guardian.hedera.com/guardian/standard-registry/policies/auto-testing-of-the-policies/auto-testing-using-ui)
* [Programmatic Policy Testing](https://guardian.hedera.com/methodology-digitization/methodology-digitization-handbook/part-4/chapter-16#programmatic-policy-testing)
  {% endupdate %}

{% update date="2026-04-17" tags="new-releases,fixes" %}

## Guardian 3.5.1 Hotfix

**Announcing Hedera Guardian 3.5.1 Hotfix**

This release is a small but important hotfix, prompted by a detailed report from the [BladeLabs](https://bladelabs.io/) team as they upgraded to 3.5.0.

They found that in policies where a single submission branches into several Custom Logic Blocks, the converters weren't staying independent — each one could pick up the changes made by the converter before it, so the resulting verifiable credentials ended up carrying accumulated, chained values instead of each reflecting only its own intended modification. For a policy designed to produce clean, distinct credentials from one request, that's a meaningful correctness issue, and it surfaced specifically in sync-events execution.

3.5.1 fixes it: each block now works from its own isolated copy of the document, so converters run cleanly and independently.

Our thanks to [Olena Yaroslavska](https://ua.linkedin.com/in/olena-yaroslavska-419b39b7) and the [BladeLabs](https://bladelabs.io/) team whose issue report came with a clear reproduction and expected-versus-actual outputs which is exactly what made the fix fast to land and verify.

[See the full release on GitHub](https://github.com/hashgraph/guardian/releases/tag/3.5.1)
{% endupdate %}

{% update date="2026-04-07" tags="events,improvements" %}

## New Calendar Launched

**Announcing the Hedera Guardian Calendar**

<figure><img src="https://1628665597-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPNzY5zOHjim5noRwV71Q%2Fuploads%2FK2Vm8jUx8rNpNCs6pqAS%2Fimage.png?alt=media&amp;token=39eb9b6c-847a-4b17-81c6-1ff1e8a99527" alt=""><figcaption></figcaption></figure>

Hashgraph recently shared what's next for the open-source Guardian initiative in [Hedera Guardian 2026: The Next Chapter](https://hashgraph.com/blog/hedera-guardian-2026-the-next-chapter/) — including a larger Hashgraph role in open-source development alongside [Climission](https://www.climission.com), key contributors joining the team, and a growing slate of community bounties and contributions. Today's announcement is part of putting that commitment into practice.

A renewed investment in the ecosystem calls for more regular, predictable ways to connect with the people building Guardian. So we're introducing a shared community calendar to do exactly that.

You'll now find a consistent rhythm of events in one place: **community** calls to stay current on direction, raise awareness of what's on your mind and hear from featured speakers in the ecosystem, **workshops** to preview upcoming releases and shape them with your feedback, hands-on **trainings** to help new and existing users get more out of the platform, and **updates** tied to each release or milestone to demo notable highlights. Whether you're digitalizing policies, integrating against the APIs, or following the carbon and environmental-asset trends more broadly, there's a touchpoint for you.

Everything lives on our calendar, and the easiest way to keep up is to subscribe — you'll get new events as they're scheduled, reminders ahead of each, and notable external events listed around the globe for more opportunities to cross paths and collaborate within our ecosystem.

<a href="https://luma.com/guardian?utm_source=gitbook" class="button primary">Subscribe to the Guardian calendar</a>

We're looking forward to seeing you there.
{% endupdate %}
{% endupdates %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://guardian.hedera.com/updates/2026/updates-2026.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.