hiero-ledger / hiero-ledger/hiero-consensus-node

CLPR-10: End-to-End Integration

Open
#24,557 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Java
Stars
407
Forks
226
Avg merge
3d 4h
Merged PRs (30d)
210

Description

Epic CLPR-10: End-to-End Integration

Parent: hiero-ledger/roadmap#48
Repo: hiero-ledger/hiero-consensus-node + Ethereum contracts repo

Objective

Deploy CLPR on testnet (Hiero + Ethereum), demonstrate 1,000 successful cross-ledger messages end-to-end.

Expected Functionality
  1. Testnet deployment — CLPR on Hiero testnet, ClprService on Ethereum testnet (Sepolia or equivalent).
  2. Verifier deployment — HieroTSS on Ethereum, EthereumBLS on Hiero.
  3. Connection — At least one bilateral Connection.
  4. Connector — At least one bilateral Connector with funds.
  5. Test applications — Contracts on both ledgers sending/receiving/verifying round-trip delivery.
  6. 1K messages — 500 Hiero→Ethereum, 500 Ethereum→Hiero. Verified delivery.
  7. Reliability metrics — Delivery rate, latency (p50/p95/p99), failures root-caused.
  8. Stress testing — Queue saturation, concurrent Connectors, endpoint failures, pause/resume under load.
Dependencies
  • All of CLPR-1 through CLPR-9
Risk

High — First real cross-ledger operation. Integration across two platforms.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing CLPR-1 through CLPR-9 and the parent roadmap issue, then identify the deployment and integration entry points in the Hiero consensus node and Ethereum contracts repository. Done means both testnet deployments, verifiers, bilateral connection and connector, round-trip applications, 1,000 verified messages, reliability metrics, and the listed stress tests are demonstrated.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
blockchain, devops, distributed-systems
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.