[Update from my change watch]

1. Dedicated CLPR CI completed successfully for the first time

Draft PR #27354 now runs three dedicated test groups: standard CLPR, embedded CLPR and multi-network CLPR.

The successful September 30 workflow reported:

• 115 tests passed.
• Seven tests skipped.
• Zero failures.
• 230 underlying runs, with 223 passing.
• The multi-network task separately logged 142 passing test operations.
• Reports and artifacts were successfully published.

The earlier TSS-bootstrap timeout was traced to a test-fixture mismatch. Random runtime ports changed the roster’s gossip endpoints, which changed its hash and prevented reuse of the preloaded WRAPS-extensible construction. The revised suites pin their gRPC ports to those encoded in the committed TSS fixtures. The mTLS fixtures were also regenerated on non-overlapping port ranges.

Effect on the prior finding: This clears the previously reported CLPR CI failure and provides the first completed, published CLPR-specific test result. It indicates that the fixture-backed multi-network, restart, manifest and mTLS scenarios can complete under the intended configuration.

It does not prove that a network can dynamically build a fresh WRAPS construction after arbitrary production recovery. The test deliberately preserves the roster hash so the preloaded chain of trust is reused. The PR remains draft and unmerged.

2. Stronger CLPR feature isolation merged into Hiero main

PR #27416 merged on September 30 as commit 223fdae2.

When clpr.enabled=false:

• CLPR system-contract addresses behave as they did before CLPR existed.
• Account 0.0.803, used for Connector stake, is not created.
• CLPR transaction types are not required in throttle definitions.
• Node bundle submissions retain their normal throttle treatment.
• CLPR state singletons are not prematurely initialized.

When CLPR is activated, its state is initialized during post-upgrade setup using the network properties effective after that upgrade. The CLPR schema was also renamed/versioned for release 0.78.0.

A consequential operational rule now emerges: CLPR is intended to be enabled at an upgrade boundary. Enabling it mid-life solely through property file 0.0.121 can leave staking account 0.0.803 absent, causing Connector completion to fail until the next upgrade.

Effect on prior findings: This materially improves the safety of shipping dormant CLPR code and makes the activation procedure more explicit. It does not activate CLPR on Hedera or change Connector stake, reimbursement, margin or slashing amounts.

3. Strict protobuf decoding merged

PR #27405 merged as commit faedd124.

It replaces permissive PBJ parsing with parseStrict across CLPR bundle handling, Channel and endpoint synchronization, verifier inputs, state proofs and relevant block-stream paths.

Assessment: This is defensive parser hardening. Malformed encodings now have a narrower path to being accepted and interpreted differently across components. It does not alter the wire schema or resolve the QBFT quorum, Ethereum-BLS or broader Channel-binding findings.

4. A streaming-only synchronization redesign is under review

Two maintainer-controlled Hiero branches propose a significant transport change.

PR #27367 adds the client side of two-phase streaming synchronization. The peer communicates its current receive position before the sender constructs bundles, avoiding needless retransmission of messages the peer already holds. Bundle construction and peer selection are also consolidated into shared components.

That PR is not yet dependency-injected and its latest CI currently fails at compile/formatting.

Dependent PR #27407 goes further:

• Makes bidirectional streaming the sole sync protocol.
• Removes the old unary protocol.
• Aligns Hiero with the EVM relay’s current streaming interface.
• Derives bundle ranges from state-proven ClprMessageKey values.
• Sorts proven message leaves and rejects gaps, duplicates, messages from another Channel and IDs outside the proven Channel range.
• Fixes receiver behavior for bundles beginning at the peer’s live received_message_id.

This is explicitly wire-breaking for endpoints that support only the old unary sync. Its current CI is green, including repository-wide unit and integration testing, but it is based on the unmerged clpr-streaming-synchronizer branch rather than main.

The author also reports successful Hiero/Besu and dual-EVM testing. Those tests used several development refs that are not present on the current authoritative LFDT repository branches, so they are useful author-reported integration evidence, not a reproducible release qualification of the published LFDT revisions.

Effect on prior findings: Proven message-key validation narrows an important cross-Channel and bundle-range ambiguity. It should not yet be treated as complete resolution of the broader Channel-context binding finding. Neither streaming PR is merged.

Economic implication — inference: Two-phase synchronization should reduce redundant bandwidth, bundle construction, proof transport and verification work. That could lower endpoint operating costs and Connector service prices, but no tariff or reimbursement parameter changes here.

5. Connector authorization economics and traceability are being reworked

Open PR #27380 addresses a concrete inefficiency in sendMessage.

The merged implementation currently launches a separate synthetic ContractCall, paid synthetically by 0.0.50, to ask the Connector contract for authorization. This has two problems:

• It creates an additional execution path described by the issue as highly wasteful.
• The originating application transaction’s EVM trace does not show the call to the Connector contract, impairing auditability.

The proposal executes Connector authorization within the original EVM frame stack. That would make the Connector authorization call visible in the application’s trace and avoid the separate synthetic transaction context.

Economic implication — inference: This could reduce execution overhead and make Connector charging and authorization easier to audit. It does not establish what Connectors charge applications or give Hashgraph a share of Connector revenue.

The PR remains unmerged. Its current CI fails at compile/formatting and it has an unresolved DCO check.

6. Mirror Node support has reached the design stage

Maintainer-controlled Mirror Node PR #14362 adds a comprehensive, implementation-oriented CLPR design document. It proposes indexing Channels, pending commitments, Connectors, messages, ledger configuration and endpoint manifests.

Six REST surfaces are proposed:

• Known chains.
• Channels by chain.
• Messages by Connector.
• Messages by Channel.
• Pending Channel commitments.
• Connectors by Channel.

The design also identifies material integration gaps:

• Verifier-derived CLPR state exists in block-stream state changes but has no carrier in classic transaction records or sidecars.
• ClprSubmitBundle may produce multiple messages from one transaction.
• The native protobufs still contain redaction functionality that the HIP describes as removed.
• Deprecated endpoint_node_id and endpoint_signature fields remain unresolved.
• A declared chain_id is useful for indexing but is not independently proof that the remote network really owns that CAIP-2 identity.

This PR contains design documentation only, not Mirror Node implementation.

Economic implication — inference: Public indexing is necessary for a transparent Connector market. It could expose service activity, Channel adoption and Connector-level message flow to applications and analysts. It does not yet expose Connector tariffs, reimbursements, revenues or profitability.

7. External draft proposes fork-aware verifiers and Channel succession

The LFDT specification received its first open PR: draft PR #1, containing a fork-aware verifier ADR.

Important provenance: this comes from the external fork shayansal/clpr-spec, is marked draft and is not adopted CLPR specification text.

The proposal addresses a genuine lifecycle problem: deployed verifiers pin fork parameters, proof layouts and sometimes rotating signer sets. A ledger hard fork can therefore stall a Channel, while a sufficiently long stall on Ethereum can strand it beyond sync-committee recovery.

It proposes:

• Consensus-proven fork identity.
• Fork profiles for parameter and proof-layout changes.
• Dual control through a source-ledger announcement plus destination-side timelocked registration.
• Direct state-proof submission independent of normal Channel message delivery.
• Typed, fail-closed fork errors that do not punish endpoints as malicious.
• Fork-readiness metrics and testnet conformance evidence.
• Successor Channels for semantic verifier changes.
• Exactly-once handoff of undelivered predecessor messages.

Effect on prior findings: This is the first detailed proposal directly addressing fork upgrades, rotating trust anchors and Channel replacement without losing queue position. It does not resolve those findings until normative text, contracts, endpoints and native implementations adopt and test the mechanism.

Economic/HBAR implication — inference: The proposal estimates one profile-registration transaction per fork per Channel. If such registration occurs on public Hedera, it would produce public-HBAR fee activity. Its larger economic value is preventing long-lived Channels and funded Connectors from becoming stranded after peer-ledger upgrades.

8. Deployment tooling exposes another CLPR upgrade dependency

Draft Solo PR #6083 adds explicit upgrade handling for fee schedules and throttle files. Its testing found that a newer throttle file containing CLPR transaction types can be rejected by an older consensus-node release.

This reinforces the requirement that CLPR activation coordinate:

• Consensus-node version.
• CLPR feature flag.
• Staking-account initialization.
• Fee schedule.
• Throttle definitions.

The Solo work is still draft and currently has a dirty merge state.

Economic and deployment conclusion

September 30 materially strengthens the engineering foundation, but does not change the core CLPR commercial model:

• Dedicated CLPR CI has now passed.
• Dormant feature isolation and upgrade-boundary activation are merged.
• Strict decoding is merged.
• More efficient streaming and Connector authorization are proposed.
• Mirror Node market observability is designed.
• Fork and trust-anchor continuity now has a serious external design proposal.

No application-facing Connector tariff, actual-gas reimbursement formula, Hashgraph revenue share or evidence that Hashgraph will operate commercial Connectors was introduced.

There is also still no CLPR-enabled Hedera release, testnet or mainnet activation, production Connector, independent audit, production benchmark, liquidity, revenue or attributable public-HBAR usage.

HIP-1535 remains unchanged at 4c1782c3. The authoritative LFDT main branches remain at the audited baselines, with no releases or tags. The SHA-256 proof migration and production Ethereum BLS verification also remain unfinished.

As insurers modernize how risk data moves between companies, one not-for-profit consortium is building the rails to make that possible. The Institutes RiskStream Collaborative, the P&C industry's largest not-for-profit emerging technology consortium, just joined the Hedera Council as a strategic partner.

Pat Schmid, President of RiskStream, joins Solomon on the interoperable property risk and resilience solution being built with Hashgraph and how a hybrid public and permissioned model gives P&C a shared source of truth.

Property data today largely moves through spreadsheets and email without a consistent identifier. That fragmentation is getting more costly as wildfire, flood, and severe convective storm risks evolve. RiskStream assigns each property a persistent, public token on Hedera, while sensitive COPE data (construction, occupancy, protection, exposure) is exchanged on the permissioned HashSphere ledger.

Pat's broader vision: an asset-policy-claim token chain extending to auto and surety bonds, portable to healthcare, finance, and energy. The initiative is moving from proof of concept into a pilot phase, with 3rd party data partners next.

In a recent Cyber Insider article, Stefan Deiss, CEO of The Hashgraph Group, explains why holding every credential in one database has become the bigger risk.

Verizon’s 2026 DBIR found credential abuse present in 39% of breaches, and once there’s a path in, an attacker can reach every application behind it. That’s why we built IDTrust, which verifies credentials without ever storing the data, with Hedera confirming each one.

Source: https://x.com/hashgraphgroup/status/2086855714119852200?s=46

Source: https://x.com/hashgraph/status/2085752509809803622?s=46

August 7, 2026

By Lewis Nibbelin, Research Writer, Triple-I
Few industries handle data as sensitive or at as large a scale as the property/casualty insurance industry, estimated by S&P Global to now exceed $1 trillion in direct annual premiums in the U.S. Supporting a market this size hinges on protecting the data required to underwrite it, which has grown increasingly granular as risks intersect with new levels of complexity.

Much of this data, however, passes through a system of carriers, brokers, reinsurers, data providers, and other organizations, none of which can collectively track or validate what each party collects and reassesses along the way. Rising data granularity exacerbates these challenges, leaving legacy systems ill-equipped to store and share information needed to capture modern risk.

In addition to putting data privacy at risk, the current system creates data gaps and inconsistences that can impact underwriting accuracy and long-term insurance affordability, necessitating greater standards for data verification.

To help fill the gap, The Institutes RiskStream Collaborative – like Triple-I, an affiliate of The Institutes – recently partnered with enterprise software and technology company Hashgraph to establish a shared source for authenticating and distributing data among all stakeholder groups. Known as an “interoperable property risk and resilience portal,” the initiative aims to manage data in a private environment while anchoring properties to a public ledger, allowing third parties to track and provide data more accurately and efficiently.

Combining Hashgraph’s private infrastructure with its public Hedera network, the solution will tie each property to a unique “token,” or digital asset, that stakeholders can identify without revealing its associated risk data, which remains in the private layer. As such, no single party controls the source data, preserving data confidentiality and fair competition.

Initially, the partnership will focus on tokenizing commercial and residential properties, with plans to expand the portal for additional insurance lines and other parts of the insurance process such as the policy or claim record.

“The process of gathering and sharing data for insurance placement and underwriting today is tedious, highly manual, and inefficient,” said Pat Schmid, RiskStream president and Triple-I chief insurance officer, in a press release on the portal. “The vision is to tokenize risk assets to create a persistent, unique identifier that serves as a shared data foundation for the risk management and insurance industry. Property is the perfect place to start.”

Great convo, worth a watch. Several teases of upcoming developments.

RAUSP Management Journal is a peer-reviewed, open-access academic journal in business and management published by the Department of Management at the School of Economics, Business and Accounting of the University of São Paulo. It publishes original research across fields such as strategy, finance, marketing, entrepreneurship, operations, sustainability, and innovation. It uses double-blind peer review and is internationally indexed, including in Scopus.

Thought this was worth sharing.

The latest editorial in the peer-reviewed RAUSP Management Journal (“Digital assets at a crossroads: risk, governance, and sustainability in the evolving crypto ecosystem”) uses Hedera as its featured example when discussing sustainable distributed ledger infrastructure.

Rather than simply mentioning Hedera in passing, the editorial dedicates a section to explaining hashgraph’s consensus mechanism, highlighting:

• “Gossip about gossip” and asynchronous Byzantine Fault Tolerance (aBFT)
• High throughput and low latency
• Significantly lower computational requirements than Proof of Work
• Low energy consumption and long-term sustainability

The author ultimately presents Hedera as a compelling alternative to traditional blockchain protocols and argues that architectures like Hedera, combined with robust governance and risk-management frameworks, can help build a more resilient institutional digital asset ecosystem.

Worth noting that this is an editorial rather than original research, so it shouldn’t be interpreted as an independent technical evaluation. Still, it’s interesting to see Hedera singled out as the primary example in a peer-reviewed management journal discussing the future of digital assets.

A document is signed.

LedgerSign computes a SHA-256 cryptographic hash of the completed document.

That hash is anchored on the Hedera network, creating an immutable, publicly verifiable record. The document itself is not placed on Hedera—only its fingerprint (the hash) is. A SHA-256 hash changes completely if even one bit of the document changes, making it an effective integrity proof.

LedgerSign issues a verification certificate showing that the SHA-256 hash is anchored on Hedera and provides a HashScan link so anyone can independently inspect the on-chain proof.

Later, anyone can verify the document by recomputing its SHA-256 hash and confirming it matches the hash anchored on Hedera. If the hashes match, the document has not been altered since it was anchored.

The Financial Action Task Force (FATF) is an independent inter-governmental body that develops and promotes policies to protect the global financial system against money laundering, terrorist financing and the financing of proliferation of weapons of mass destruction.

The FATF Recommendations are recognised as the global anti-money laundering (AML) and counter-terrorist financing (CFT) standard.

www.fatf-gafi.org

Three billion people transact locally but are locked out of global income. @go_rosen is changing that: everyday "helps" become instant cross-border earnings, paid in Hedera $USDC in seconds, at a fraction of a cent, with no banking or language barriers.

Source: https://x.com/hedera/status/2080277248238838190?s=46

By Eric Piscini

As tokenization matures, Europe’s governance and regulatory strengths become its competitive advantage. This is because trust, not technological prowess, will determine who captures the market.

Banks, asset managers, and governments are exploring tokenized assets at scale. However, as the technology matures, many commentators are still getting the debate wrong. Too often the focus is on the speed of blockchains rather than the trusted infrastructure that underpins them. The jurisdictions that combine innovation with legal certainty, robust governance, and institutional credibility will be best placed to shape the next generation of global capital markets.

Most conversations about tokenization used to start with the same nervous question: will this actually work?  Engineers have answered that one. Settlement that took days now takes minutes, fractional ownership turns illiquid assets into tradeable ones, and markets that used to close at 5pm now run continuously.

So institutions stopped asking if tokenization works and started asking the same question every phishing email is engineered to make you skip: do I actually know who I’m talking to, and can I trust you?

That shift changes the shape of this race. It isn’t won by whoever has the fastest chain or the boldest whitepaper. It’s won by whoever can make a pension fund, an insurer, or a central bank feel safe enough to actually move real money. That answer doesn’t live in a GitHub repo or a benchmark. It lives in legal certainty and institutional governance, things that take decades to build, not sprints. On that score, Europe is sitting on a stronger hand than most people give it credit for.

The bottleneck nobody wants to talk about 

Ask anyone who has run a tokenization pilot where it actually got stuck, and you rarely hear “the blockchain couldn’t keep up.” You hear about governance. Custody. Who’s liable if something breaks at 2am. 

You can have the fastest settlement layer on the planet, but if a French insurer and a German custodian can’t agree on whose name is on the deed, the project sits half-built while the lawyers argue. Governance, custody, cross-border clearing: that’s the real bottleneck. 

Trust doesn’t ship in a software update 

You can’t build trust in a sprint. You build it slowly, over years, one kept promise at a time. Europe has been at this longer than almost anyone. A pension fund committing capital needs a legal backstop it recognizes, not a terms-of-service page from a company that didn’t exist eighteen months ago. The same instinct shows up with privacy: GDPR wasn’t popular when it landed, but it trained European builders to treat privacy as something poured into the foundation, not wallpaper hung up after the regulator calls.

Then there’s cross-border plumbing, which Europe has been mastering since long before anyone had heard of blockchain. Euroclear, Clearstream, Deutsche Börse, SIX Digital Exchange: these institutions spent decades getting different jurisdictions and legal traditions to talk to each other.

And then there’s MiCA. Plenty called it red tape when it landed. But what rules deliver is predictability, and predictability is what gets capital off the sidelines. MiCA didn’t slow Europe down; it gave the rest of the world a reason to pick up the phone. Add the digital euro, and Europe stops looking like a participant and starts looking like the one setting the conditions. 

Infrastructure isn’t distribution 

Here’s the part that gets glossed over: blockchain was never a distribution mechanism. It’s a settlement and record-keeping layer. Getting an asset onto a chain doesn’t get it in front of the people who’d actually buy it, and it doesn’t make a fund manager who’s run the same process for twenty years suddenly want a new one. That work is still slow, manual, still about relationships and habits.

What tokenization does instead is multiply the number of doors available. Every new rail or platform is one more option sitting next to the legacy way of doing things. None of them force adoption. But pile up enough of them, and the old system starts looking like an inconvenient choice rather than the only one.

A real example 

I’ve watched teams try to build tokenization infrastructure on foundations that weren’t designed for it. You can force it, but it’s not pretty.

What gives me optimism is seeing platforms emerge from within Europe that reflect this thinking natively. Asseto, built by ioBuilders in Madrid, is a useful example of where the market is heading: infrastructure designed around institutional workflows from the start, rather than retail crypto assumptions retrofitted for banks and asset managers. It brings issuance, management, trading, and settlement into a framework institutions can actually use, with flexibility across networks depending on their regulatory and operational requirements.

The point is to reduce forced trade-offs between transparency, compliance, and data sovereignty. It’s not flashy, but that’s precisely the point.

The real opportunity 

Europe isn’t just a market for tokenization. It can be the trust layer the global tokenized economy runs on, exporting the governance models, privacy habits, and institutional standards that make tokenized markets usable everywhere else. The infrastructure question is mostly solved. The trust question is still wide open, and that’s Europe’s lane, warming up for decades. 

Institutions aren’t only shopping for faster settlement anymore. They want somewhere they can put their money and not lie awake at 3am wondering if the rules will hold. The rails are forming, the technology is ready, and the scarce commodity here is exactly what Europe has been quietly manufacturing all along: trust. 

Source: https://x.com/hashgraph/status/2077355723512545358?s=46

Source: https://x.com/hedera/status/2077022879812645245?s=46

Case Study highlighted in the WDMC Report (page 15-16): https://www.theglobalcity.uk/PositiveWebsite/media/Research-reports/Wholesale-Digital-Markets-Champion-First-report.pdf

Case Study (Hedera): https://hedera.com/case-study/abrdn-lloyds-archax/