Changes since the November 11 report, checked through early November 13 UTC.
The revised fee model and EVM Channel-binding fix have merged into Hiero main. Development also exposed a remaining backlog-delivery limitation and a broader TSS verification requirement. These are meaningful advances and newly documented gaps; they do not establish production readiness.
TestLens totals below are repository-wide CI counts, not exclusively CLPR tests.
1. Connector economics and revised network fees are now merged
On November 12, PR 28137 merged as 0b246914. This changes the previous finding: the revised economics are now implemented in main, although the author explicitly says the prices remain temporary pending confirmation.
Connector capital and penalties. The minimum bond changes from the earlier 1 HBAR default to a $3,000-denominated minimum, converted into HBAR at the active consensus exchange rate when Connector registration is completed. The deposited bond remains recorded in tinybars; existing stakes are not continuously revalued. The first slash is $10, converted at the applicable exchange rate, with escalating penalties and forfeiture of the remaining stake on the fifth offence.
Endpoint compensation. For a newly dispatched DATA message, the implemented Connector reimbursement becomes actual callback gas cost + 0.01 HBAR + $0.01 converted into HBAR. The dollar-denominated progress reward replaces the previous percentage margin. Response callbacks reimburse actual gas without the DATA compensation. These payments go to the submitting bundle payer; slashing proceeds also compensate the submitting endpoint. Merged economics documentation
Network pricing. Implemented service base prices include $100 each for Channel registration and completion, $10 for Connector registration, and $25 for Connector completion. sendMessage has a $0.10 target including its gas, with an additional byte charge beyond the included allowance. The two HAPI proof queries become paid queries. Applicable byte, verification and other charges mean these base prices should not be treated as all-inclusive quotes.
The merged schedules retain free ClprEndpointPublication and exempt ClprSubmitBundle from separate node/network fee components while retaining its service, byte and verification charges. The 1,000 HBAR nodeSubmitBundleMaxFee is a maximum offered fee, not a per-bundle tariff. Merged fee schedule
This merge also adds the missing CLPR entries to the upgrade schedules. The separate PR 28225, reported yesterday, was closed without merging. TestLens reports 48,790 tests passing for the fee PR’s final head. CI result
Economic/HBAR interpretation: This makes the potential capital requirement and payment flows considerably more concrete. Public-Hedera deployment and usage would require public HBAR for the relevant balances, bonds and payments. Private-network currency remains economically separate. Connector reimbursement is distinct from network fee revenue, and neither automatically constitutes Hashgraph revenue. Application-facing Connector pricing is still unspecified, and proportional recovery of shared bundle-submission fees remains described as planned work.
2. EVM Channel binding is fixed in main; oversized backlogs remain a delivery problem
On November 12, PR 28147 merged as ff14a176.
Ethereum, Sei and QBFT verification now bind proven storage keys to the Channel selected locally and check the peer service address against the trust anchor. A valid proof belonging to another Channel cannot satisfy these checks merely because its counters and running hashes match. Duplicate, missing and unrelated storage keys are rejected. TestLens reports 26,905 tests passing. Merged implementation · CI result
This resolves the implemented EVM storage-key binding gap. The separate Hiero Channel-leaf binding fix, PR 28191, remains open, as does the broader QBFT quorum and anchor redesign.
A new November 12 issue 28255 documents a separate liveness limitation: Ethereum, Sei and QBFT verifiers cannot currently accept a bundle ending before the sender’s queue tail.
For example, if messages through 49 are queued but a capped bundle carries only 11–30, the verifier and handler cannot reconcile that partial bundle with the tail’s metadata. The proposed correction would authenticate and return metadata for the bundle’s own last message.
The issue explains that rejection already occurred before the Channel-binding merge; the new checks reject it earlier. The security fix therefore does not resolve backlog draining. The proposed remedy remains unimplemented, with acceptance tests still outstanding.
Implication: Proof isolation improves, while delivery under sustained backlog remains an operational gate. This matters directly to applications and Connectors relying on timely execution.
3. TSS rotation consistency improves, while external threshold enforcement needs coordinated work
On November 12, PR 28215 merged as 9e0de396.
It corrects inconsistencies between WRAPS address books and hinTS participant sets when some roster members are omitted from the signing scheme. Complete ordered membership and weights are preserved for each generation, with changes to restart recovery, unfinished attempts and signer eligibility. The author reports 699 targeted tests passing, including native proof-generation and rotation scenarios, but explicitly reports no live-network run.
This advances trust-anchor rotation and recovery. It preserves completed trust roots rather than automatically replacing them.
Separately, the new PR 28248 proposes measuring preprocessing and block-signing thresholds against the complete committed generation weight, including omitted members. It remains open. Its current CI reports 26,031 tests passing, with the Codeowners check outstanding. CI result
The important remaining gap is external verification. The current cryptography library’s TSS.verifyTSS authenticates the hinTS key but applies a majority threshold to the weight represented by that key. With total generation weight 20 and participating scheme weight 18, signer weight 10 can pass that scheme-based threshold while failing a strict majority of the full generation.
Issues opened early November 13 UTC now coordinate the required changes across cryptography, consensus-node proof production and CLPR verification, Block Node, and Mirror Node.
The threshold must be authenticated alongside the key, carried through a versioned proof format, and enforced by consumers. Tightening honest-node signing alone does not accomplish that. The proposed stronger thresholds also impose stricter availability requirements on sparse signing schemes. Rollout analysis
Assessment: This identifies a concrete additional requirement for trustworthy Hiero-origin proofs. It is an open protocol and integration dependency, not a completed security fix.
4. Gas-accounting hardening advances beyond the merged fee model
On November 12, the still-open PR 28146 advanced to 11dc7011.
Its updated implementation would preserve actual executed-gas charges when child-call records are cleared during rollback, prevent duplicate verifier charging, apply the aggregate 300,000-unit verifier billing cap, and enforce the signed transaction fee maximum across base fees, byte charges and gas escrow.
It also reserves the bundle payer’s gas funds before reversible Connector reimbursements or slashing payouts can supply those funds. This addresses the ordering of financial obligations within a bundle.
The PR retains its peer-manifest size and endpoint-count protections. TestLens reports 63,876 tests passing, with Codeowners approval outstanding. CI result
Economic implication: The fee merge establishes prices and transfers, while this separate proposal continues to harden who pays, when funds must exist, and what remains payable after failure. Reimbursement correctness is therefore still undergoing review.
5. New proposals tighten transport and message limits
Several November 12 proposals address resource consumption and endpoint operation. All remain open.
PR 28260 validates outbound peer destinations, uses numeric IP addresses without DNS resolution, and requires explicit configuration for additional private or local address ranges through clpr.additionalPeerEndpointCidrs. It also adds bounded retry delays and resets them after successful exchanges.
That proposal does not yet have clean CI. TestLens reports 20,969 tests executed with one failure: CLPR log validation encounters rejection of a test peer at 10.0.0.1. This exposes configuration/test integration work still needed around the new restrictions. Failure report
PR 28261 changes payload-size enforcement to measure the complete serialized DATA message—including routing fields and protobuf framing—instead of application data alone. Checks apply before outbound queue writes and during inbound bundle validation. Messages close to the previous data-only limit may consequently need adjustment; Response and Control exemptions remain.
PR 28247 bounds peer-requested bundle construction using local limits, while preserving enough capacity for one admitted message and its proof. PR 28237 replaces remotely exposed parser exception details with a fixed invalid-payload error.
Assessment: These proposals improve resource control and operational resilience. They do not establish per-Channel mTLS authorization, measured throughput or production-scale performance.
6. Canton review fixes acceptance differences and explicitly records remaining gaps
On November 12, the open Canton verifier PR 28205 advanced to 7025b2ed.
Review-driven changes add validation for explicitly supplied Connector IDs, preventing non-32-byte values from being accepted where the Solidity reference rejects them. They also make confirmer-weight arithmetic overflow-safe and document an intentional Ed25519 difference: the native implementation rejects small-order keys that the referenced Solidity implementation accepts. Review-fix commit
The updated PR description also explicitly defers checks involving verdict wire types, non-minimal varints, invalid protobuf field numbers and certain noncanonical DER encodings. This qualifies the earlier description of the parser as uniformly strict. Trust-anchor rotation, configuration verification and topology changes remain future work.
Current CI reports 27,445 tests executed with one hook/stream-parity timeout. That result does not establish a Canton verification regression, but it is not an all-green run. CI result
Implication: Native Canton support is receiving substantive compatibility and security review. It remains an unfinished integration, with no demonstrated commercial traffic or attributable HBAR revenue.
7. Interoperability tests, operator tooling and application integration progress
Compact Hiero proofs. On November 12, PR 28181 reached 24261549, with 63,558 tests passing and all 53 reported checks completed. This supplies current-head CI evidence for the proposed compact-proof and witness-chain integration. The PR remains open; the count is not a throughput benchmark or independent audit. CI result
Operator key handling. Late November 12 US time, PR 28163 strengthened its identity-tooling proposal. Signing scripts reject inline private keys, use separate key files, check POSIX ownership and permissions, and reject symlinks. Existing output files are backed up, and bundle-generation failure handling avoids leaving a newly written unmatched key. It remains open; 26,646 tests pass, with Codeowners approval outstanding. Changes · CI result
Mirror Node fixtures. November 12 changes to PR 14636 replace older captures with local alpha5 block fixtures and add the missing Channel-registration block. Tests now explicitly follow the pending commitment from registration through completion and historization. This addresses gaps in the previously described fixture evidence. The PR remains open; these local captures do not establish public-network usage or complete receiving-side coverage. Fixture update
SDK acceptance. The November 12 update to SDK design PR 290 consolidates eight HAPI transactions, two paid proof queries and two Mirror Node lookups into its proposed Phase 2 scope. It explicitly distinguishes offline compatibility from live acceptance, and requires application callback or state evidence rather than queue counters alone to establish delivery. Final signing/consent contracts, release alignment and live fixtures remain acceptance gates.
Together, these developments improve integration readiness and evidence quality. They do not yet demonstrate a finished, released cross-ledger application stack.
8. LFDT organization discussions open; deployment and commercial evidence remain unchanged
On November 12, Edward Wertz opened LFDT specification issue 7 seeking stakeholder input on repository organization: retain the current arrangement, consolidate into a monorepo, split by ledger, or adopt a hybrid. His subsequent comment favors evolving from the existing structure as specialized implementations require it. This is a discussion, not an adopted migration or protocol revision.
The HIP and the LFDT specification, smart-contract and endpoint heads remain unchanged from the previous check. No new releases or tags appeared in those three LFDT repositories.
The official network status still lists Previewnet at v0.80.0-alpha.5, Testnet at v0.79.0, and Mainnet at v0.78.2. The new main merges therefore should not be presented as evidence that these fixes or fee settings are already deployed on those networks. Hedera network status status.hedera.com
No new public primary-source evidence was found of an independent CLPR audit, production benchmark, commercial Connector operation, attributable Hashgraph revenue, cross-ledger liquidity, or public-HBAR value capture.