Platform Updates 2026

Announcing Hedera Guardian 3.7

The Hedera Guardian 3.7 release is now available, 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.

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 #6422

Policies can now validate a submitted document against related documents and closing a gap identified in real-world methodology work. #6312

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

Schema fields can be repeated to appear in multiple location, keeping data entered by users in sync across related form inputs and questions. #6509

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, #6355, #6239

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 program. #6033

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

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

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

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

Announcing Hedera Guardian 3.6

The Hedera Guardian 3.6 release is now available. 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.

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.

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.

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.

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.

(#5795, #5955, #5799, #5800, #1987, #3642)

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.

Developing Digital Methodologies with Guardian: VM0050 and VM0047

Over two sessions in April and May, Jailine Molina, Lead Environmental Solutions Lead at Hashgraph and Waqar Ashiq, Senior Program Officer at Verra 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 and what a complete bounty submission looks like: encoded schemas, calculations, transformation blocks, and documentation.

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

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

Shaping the next evolution of testing policy integrity

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, Giuseppe Bertone, Jailine Molina, and Wes Geisenberger.

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

See related docs

Announcing Hedera Guardian 3.5.1 Hotfix

This release is a small but important hotfix, prompted by a detailed report from the BladeLabs 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 and the BladeLabs 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

Announcing the Hedera Guardian Calendar

Hashgraph recently shared what's next for the open-source Guardian initiative in Hedera Guardian 2026: The Next Chapter — including a larger Hashgraph role in open-source development alongside Climission, 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.

We're looking forward to seeing you there.