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

ContractCallLocalHandler to support local call for account and schedule

Open
#20,897 1 comment 0 reactions 0 assignees View on GitHub
Hedera Smart Contract Service Team Promoted
Dominant language
Java
Stars
406
Forks
226
Avg merge
3d 4h
Merged PRs (30d)
210

Description

### Background

With this ticket https://github.com/hiero-ledger/hiero-consensus-node/issues/3659 `ContractGetBytecodeQuery` able to response with redirect bytecode when contract,account,token,schedule ids are sent as contractId of the query. We want to introduce similar logic to ContractCallLocalQuery.

### Solution
Now `ContractCallLocalQuery` allow to execute local call for contract and token. We want it to be able to execute local calls additionally for account and schedule.

Moved from https://github.com/hashgraph/hedera-smart-contracts/issues/1297

### Acceptance Criteria

1. `ContractCallLocalQuery` able to execute local calls additionally for account and schedule
2. JavaDocs updated/created
3. Unit tests created/updated for all new functionality
4. HAPI test create for all new functionality

### Dependencies

_No response_

### Definition of Ready (DoR) Checklist

- [ ] Clear acceptance criteria
- [ ] Clear and detailed description
- [ ] Dependencies identified
- [ ] Links to documentation
- [ ] Should be completable in 2-3 Days
- [ ] Initial draft of Low-level design document
- [ ] At least high level test plan
- [ ] Groomed/Estimated

### Definition of Done (DoD) Checklist

- [ ] Acceptance Criteria complete
- [ ] No Codacy issues greater than minor (in new code)
- [ ] JavaDocs updated/created
- [ ] Code commented
- [ ] Unit tests created/updated
- [ ] 80% test code coverage (in new code)
- [ ] Happy Path and major negative cases in HAPI tests as applicable

Contributor guide

Open the contributing guide

Research direction

Start by reading the ContractCallLocalQuery handling for existing contract and token local calls, then trace the related unit and HAPI tests. Extend the behavior for account and schedule calls, update or add JavaDocs, and verify the new functionality with unit and HAPI coverage.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
api, backend-api-design
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.