Add `stacking_info` field to ContractInfo

[manishdait]

The protobuf ContractGetInfoResponse.ContractInfo message includes a staking_info field that provides staking-related metadata for contracts. This field is already supported and exposed in the other SDK, but it is currently missing from the Python SDK ContractInfo class.

Proposed Solution

• Add a new optional field to the Python ContractInfo class:

  staking_info: Optional[StakingInfo] = None

• Update from_proto() to correctly deserialize staking data:

  # eg
   @classmethod
    def _from_proto(cls, proto: ContractGetInfoResponse.ContractInfo) -> "ContractInfo":
        ...  
        return cls(
            ...,
            staking_info=(
               StakingInfo.from_proto(proto.stakingInfo)
               if proto.HasField("stakingInfo")
               else None
            )
         )

• Update to_proto to serialize staking data back to protobuf:

  def _to_proto(self) -> ContractGetInfoResponse.ContractInfo:
        ....
        return ContractGetInfoResponse.ContractInfo(
            ...,
            staking_info=(
              self.staking_info.to_proto()
              if self.staking_info is not None
              else None
              )
          )

• Ensure unit test for fromBytes / toBytes round-tripping includes staking information once added.

[github-actions]

@coderabbitai plan

[coderabbitai]

Coding Plan

Approach

Add support for the staking_info field from the protobuf ContractGetInfoResponse.ContractInfo message to the Python SDK's ContractInfo class, including proper deserialization, serialization, and test coverage.

Observations

The project is a Python SDK for Hedera/Hiero that wraps protobuf-generated classes with SDK-friendly Python dataclasses. The ContractInfo class is a dataclass in src/hiero_sdk_python/contract/contract_info.py that currently has 14 fields and implements _from_proto() and _to_proto() methods for protobuf conversion. Tests follow a comprehensive pattern with round-trip conversion tests in tests/unit/contract_info_test.py. The project uses auto-generated protobuf classes from hiero_sdk_python.hapi.services.basic_types_pb2, including the StakingInfo protobuf message.

Assumptions

Assumption 1: How to represent staking information in ContractInfo

Options Considered:

• Follow AccountInfo pattern: Extract individual staking fields (staked_account_id, staked_node_id, decline_staking_reward) as separate ContractInfo attributes
• Store StakingInfo protobuf object directly as a single field
• Create a new StakingInfo SDK wrapper class with _from_proto()/_to_proto() methods

Chosen Option: 1

Rationale: The AccountInfo class already handles staking information by extracting individual fields from the protobuf StakingInfo object rather than storing it directly. This follows the established SDK pattern of converting protobuf types to native SDK types, maintains consistency with how accounts expose staking data, and avoids exposing protobuf class interfaces to SDK users.

💡 User Tips

Regenerate the plan with different choices with @coderabbitai <feedback>.

Implementation Steps

Phase 1: Add Staking Fields to ContractInfo

Add staking-related fields to ContractInfo following the pattern established by AccountInfo, including protobuf conversion logic.

Task 1: Add staking field declarations to ContractInfo

Add three staking-related fields to the ContractInfo dataclass.

• Add staked_account_id: Optional[AccountId] = None field to the ContractInfo dataclass in src/hiero_sdk_python/contract/contract_info.py
• Add staked_node_id: Optional[int] = None field
• Add decline_staking_reward: Optional[bool] = None field
• Place these fields logically near the end of the class definition, after max_automatic_token_associations and before token_relationships
• Add import for StakingInfo protobuf class: from hiero_sdk_python.hapi.services.basic_types_pb2 import StakingInfo

Task 2: Update _from_proto() to extract staking fields

Modify the _from_proto() method to deserialize staking information from the protobuf message.

• In src/hiero_sdk_python/contract/contract_info.py, locate the _from_proto() method
• After extracting existing fields, add logic to check if the protobuf has staking info: proto.HasField('stakingInfo')
• If present, extract staked_account_id by converting proto.stakingInfo.staked_account_id using AccountId._from_proto() (with HasField() check)
• Extract staked_node_id directly from proto.stakingInfo.staked_node_id if present (using HasField() check)
• Extract decline_staking_reward by mapping from proto.stakingInfo.decline_reward
• Follow the same pattern used in AccountInfo's _from_proto() method (lines 105-116 as shown in exploration)

Task 3: Update _to_proto() to reconstruct staking protobuf

Modify the _to_proto() method to serialize staking fields back to protobuf format.

• In src/hiero_sdk_python/contract/contract_info.py, locate the _to_proto() method
• Add construction of StakingInfo protobuf object within the ContractGetInfoResponse.ContractInfo return statement
• Create StakingInfo with: staked_account_id converted via self.staked_account_id._to_proto() if not None, staked_node_id passed directly, and decline_reward mapped from self.decline_staking_reward
• Follow the same pattern used in AccountInfo's _to_proto() method (lines 150-154 as shown in exploration)

🤖 Prompt for AI agents

This phase adds staking-related fields to the ContractInfo class, following the
established AccountInfo pattern for handling staking information.

In `src/hiero_sdk_python/contract/contract_info.py`:
- Add import for StakingInfo protobuf class
- Add three staking fields to the ContractInfo dataclass: `staked_account_id`,
`staked_node_id`, and `decline_staking_reward`
- Update `_from_proto()` method to extract staking fields from protobuf
StakingInfo (check HasField, extract each field with appropriate conversions)
- Update `_to_proto()` method to construct StakingInfo protobuf from the staking
fields

Phase 2: Add Test Coverage for Staking Fields

Add comprehensive unit tests for the staking fields following established testing patterns.

Task 1: Add staking field tests to contract_info_test.py

Create test cases for staking field handling in the ContractInfo unit tests.

• In tests/unit/contract_info_test.py, add test cases for staking fields following the existing test pattern
• Add test for _from_proto() with staking_info present: verify staked_account_id, staked_node_id, and decline_staking_reward are correctly extracted
• Add test for _from_proto() with staking_info absent (None case): verify fields default to None
• Add test for _to_proto() with staking fields populated: verify StakingInfo protobuf is correctly constructed
• Add round-trip test: verify converting to proto and back preserves staking field values
• Include edge cases: test with staked_account_id set (node staking), test with staked_node_id set (account staking), test with decline_staking_reward true/false

Task 2: Update existing proto conversion tests

Extend existing round-trip tests to include staking fields.

• In tests/unit/contract_info_test.py, locate the existing test_proto_conversion_full_object() test
• Add assertions to verify staking fields are preserved during round-trip conversion
• Ensure the test fixture includes sample staking data for comprehensive validation

🤖 Prompt for AI agents

This phase adds comprehensive test coverage for the new staking fields in
ContractInfo.

In `tests/unit/contract_info_test.py`:
- Add test cases for `_from_proto()` with staking info present and absent
- Add test cases for `_to_proto()` with staking fields populated
- Add round-trip conversion tests for staking fields
- Include edge cases (staked to account vs node, decline reward variations)
- Update existing `test_proto_conversion_full_object()` to include staking field
assertions

---

🚀 Next Steps

🤖 All AI agent prompts combined

Task: 1

This phase adds staking-related fields to the ContractInfo class, following the
established AccountInfo pattern for handling staking information.

In `src/hiero_sdk_python/contract/contract_info.py`:
- Add import for StakingInfo protobuf class
- Add three staking fields to the ContractInfo dataclass: `staked_account_id`,
`staked_node_id`, and `decline_staking_reward`
- Update `_from_proto()` method to extract staking fields from protobuf
StakingInfo (check HasField, extract each field with appropriate conversions)
- Update `_to_proto()` method to construct StakingInfo protobuf from the staking
fields
===============================================================================

Task: 2

This phase adds comprehensive test coverage for the new staking fields in
ContractInfo.

In `tests/unit/contract_info_test.py`:
- Add test cases for `_from_proto()` with staking info present and absent
- Add test cases for `_to_proto()` with staking fields populated
- Add round-trip conversion tests for staking fields
- Include edge cases (staked to account vs node, decline reward variations)
- Update existing `test_proto_conversion_full_object()` to include staking field
assertions

💡 Iterate on the plan with: @coderabbitai <feedback>

Example Feedback
- @coderabbitai You can skip phase 3. Add a simple unit test case for phase 2.
- @coderabbitai For assumption 1 go ahead with option 3 and replan.

---

💬 Have feedback or questions? Drop into our discord!