hiero-ledger / hiero-ledger/hiero-consensus-node
CLPR-11: Ecosystem Tooling
- Dominant language
- Java
- Stars
- 406
- Forks
- 226
- Avg merge
- 3d 4h
- Merged PRs (30d)
- 210
Description
## Epic CLPR-11: Ecosystem Tooling
**Parent:** hiero-ledger/roadmap#48
**Repo:** Multiple (SDK repos, Mirror Node, Block Node)
### Objective
Extend Hiero ecosystem tools (SDKs, Mirror Node, Block Node) to support CLPR.
### Expected Functionality
1. **SDK support** — Java, JavaScript, Go SDKs: transaction builders and query methods for all CLPR operations.
2. **Mirror Node REST API** — Endpoints for Connections, messages, Connectors, configuration. Connection state queries are explicitly NOT exposed as HAPI queries (impl spec §3.3) — Mirror Node is the primary consumer interface.
3. **Mirror Node indexing** — CLPR transactions indexed and searchable.
4. **Block Node support** — CLPR transaction types parsed in block stream.
### Dependencies
- CLPR-1 (first transactions to support; progresses incrementally)
### Risk
**Medium** — Many repos/teams. SDK release cycles may not align.
Contributor guide
Research direction
Start with the CLPR-1 dependency and the parent roadmap#48, then review the SDK, Mirror Node, and Block Node repositories named in the issue. Break the work down by component and confirm which CLPR operations are in scope. Done means the SDK builders and queries, Mirror Node endpoints and indexing, and Block Node transaction parsing support the incremental CLPR scope.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, java, javascript
- Domain
- api, backend, data, distributed-systems, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100