TCK: Implement endpoint for `deleteTopic`

[MonaaEid]

We don’t yet have an implementation for the deleteTopic JSON-RPC endpoint in python-sdk , so we should go ahead and add it

[github-actions]

Thanks for your submission.

This issue is awaiting approval from @hiero-ledger/hiero-sdk-python-triage and @hiero-ledger/hiero-sdk-python-committers and @hiero-ledger/hiero-sdk-python-maintainers.

[github-actions]

Approved by @hiero-ledger/hiero-sdk-python-triage and @hiero-ledger/hiero-sdk-python-committers and @hiero-ledger/hiero-sdk-python-maintainers.

[github-actions]

@coderabbitai plan

[coderabbitai]

Coding Plan

Summary

Reuse the already-implemented SDK TopicDeleteTransaction; the work is confined to the TCK's param/response/handler layers. Mirror the existing deleteToken endpoint (params → status-only response → handler) to stay consistent with established conventions. Rely on the existing decorator-based registry and the already-imported topic module, so no routing or registration changes are required.

Implementation Steps

Add the deleteTopic JSON-RPC endpoint

This phase introduces the full request/response/handler triad for deleteTopic, mirroring the established deleteToken pattern and reusing the already-implemented SDK TopicDeleteTransaction. The goal is a status-returning delete endpoint that accepts a topicId plus the standard commonTransactionParams, requiring no changes to routing since the topic handler module is already registered.

Task 1: Add the DeleteTopicParams request dataclass

Introduce the typed request params for the new endpoint.

• Add a DeleteTopicParams(BaseTransactionParams) dataclass to tck/param/topic.py with a single topicId: str | None = None field (session and common params are inherited).
• Implement a parse_json_params(cls, params: dict) classmethod mirroring DeleteTokenParams in tck/param/token.py: read topicId from the dict and populate sessionId/commonTransactionParams via the existing parse_session_id / parse_common_transaction_params helpers.
• No new imports are needed in this file; existing imports cover the requirements.

Task 2: Add the DeleteTopicResponse response dataclass

Provide the status-only response payload for the endpoint.

• Add a DeleteTopicResponse(StatusOnlyResponse) dataclass to tck/response/topic.py, matching the convention used by DeleteTokenResponse.
• Import StatusOnlyResponse from tck.response.base in that module.

Task 3: Implement the deleteTopic handler

Wire the SDK transaction into the registry so the endpoint is dispatchable.

• In tck/handlers/topic.py, add an import for TopicDeleteTransaction from hiero_sdk_python.consensus.topic_delete_transaction, and import the new DeleteTopicParams / DeleteTopicResponse.
• Add a private _build_delete_topic_transaction(params) helper that constructs a TopicDeleteTransaction, sets the gRPC deadline via DEFAULT_GRPC_TIMEOUT, and calls set_topic_id(TopicId.from_string(params.topicId)) when topicId is provided (mirroring _build_delete_token_transaction).
• Add a @rpc_method("deleteTopic") handler delete_topic(params) -> DeleteTopicResponse following the existing topic/token pattern: resolve the client via get_client, build the transaction, conditionally apply commonTransactionParams, execute with wait_for_receipt=False, fetch the receipt with validate_status=True, and return the response built from ResponseCode(receipt.status).name.
• No changes to tck/handlers/__init__.py or tck/handlers/registry.py are needed—the topic module is already imported and auto-registers the new method.

🤖 Prompt for AI agents

Implement the `deleteTopic` JSON-RPC endpoint in the TCK server by adding the
request/response/handler triad, mirroring the existing `deleteToken` endpoint
and reusing the SDK's `TopicDeleteTransaction`.

- In `tck/param/topic.py`: add a `DeleteTopicParams(BaseTransactionParams)`
dataclass with a single field `topicId: str | None = None` (session and common
params are inherited). Implement a `parse_json_params(cls, params: dict)`
classmethod mirroring `DeleteTokenParams` in `tck/param/token.py`: read
`topicId` from the dict and populate `sessionId`/`commonTransactionParams` via
the existing `parse_session_id` / `parse_common_transaction_params` helpers. No
new imports are needed.

- In `tck/response/topic.py`: add `DeleteTopicResponse(StatusOnlyResponse)`,
matching the convention used by `DeleteTokenResponse`. Import
`StatusOnlyResponse` from `tck.response.base`.

- In `tck/handlers/topic.py`: import `TopicDeleteTransaction` from
`hiero_sdk_python.consensus.topic_delete_transaction`, and import the new
`DeleteTopicParams` / `DeleteTopicResponse`. Add a private
`_build_delete_topic_transaction(params)` helper that constructs a
`TopicDeleteTransaction`, sets the gRPC deadline via `DEFAULT_GRPC_TIMEOUT`, and
calls `set_topic_id(TopicId.from_string(params.topicId))` when `topicId` is
provided (mirroring `_build_delete_token_transaction`). Add a
`@rpc_method("deleteTopic")` handler function `delete_topic(params) ->
DeleteTopicResponse` following the existing topic/token pattern: resolve the
client via `get_client`, build the transaction, conditionally apply
`commonTransactionParams`, execute with `wait_for_receipt=False`, fetch the
receipt with `validate_status=True`, and return the response built from
`ResponseCode(receipt.status).name`.

- No changes are needed in `tck/handlers/__init__.py` or
`tck/handlers/registry.py`, since the `topic` module is already imported and
will auto-register the new method.

Research

The TCK server (tck/) exposes a single Flask JSON-RPC endpoint that dispatches methods through a decorator-based registry (@rpc_method in tck/handlers/registry.py). Each JSON-RPC method is composed of a request params dataclass (tck/param/), a response dataclass (tck/response/), and a handler function (tck/handlers/) that builds an SDK transaction, applies common transaction params, executes it, and returns the receipt status.

The topic domain currently implements createTopic and submitTopicMessage but not deleteTopic. The underlying SDK already provides a complete TopicDeleteTransaction (constructor/set_topic_id, standard base execute), and the closest delete-style precedent is the fully implemented deleteToken endpoint.

File-Level Change Summary

• tck/param/topic.py: add DeleteTopicParams dataclass with topicId and a parse_json_params classmethod.
• tck/response/topic.py: add DeleteTopicResponse(StatusOnlyResponse) and import StatusOnlyResponse.
• tck/handlers/topic.py: import TopicDeleteTransaction and the new param/response types; add _build_delete_topic_transaction helper and the @rpc_method("deleteTopic") handler.

---

🚀 Next Steps

🤖 All AI agent prompts combined

Implement the `deleteTopic` JSON-RPC endpoint in the TCK server by adding the
request/response/handler triad, mirroring the existing `deleteToken` endpoint
and reusing the SDK's `TopicDeleteTransaction`.

- In `tck/param/topic.py`: add a `DeleteTopicParams(BaseTransactionParams)`
dataclass with a single field `topicId: str | None = None` (session and common
params are inherited). Implement a `parse_json_params(cls, params: dict)`
classmethod mirroring `DeleteTokenParams` in `tck/param/token.py`: read
`topicId` from the dict and populate `sessionId`/`commonTransactionParams` via
the existing `parse_session_id` / `parse_common_transaction_params` helpers. No
new imports are needed.

- In `tck/response/topic.py`: add `DeleteTopicResponse(StatusOnlyResponse)`,
matching the convention used by `DeleteTokenResponse`. Import
`StatusOnlyResponse` from `tck.response.base`.

- In `tck/handlers/topic.py`: import `TopicDeleteTransaction` from
`hiero_sdk_python.consensus.topic_delete_transaction`, and import the new
`DeleteTopicParams` / `DeleteTopicResponse`. Add a private
`_build_delete_topic_transaction(params)` helper that constructs a
`TopicDeleteTransaction`, sets the gRPC deadline via `DEFAULT_GRPC_TIMEOUT`, and
calls `set_topic_id(TopicId.from_string(params.topicId))` when `topicId` is
provided (mirroring `_build_delete_token_transaction`). Add a
`@rpc_method("deleteTopic")` handler function `delete_topic(params) ->
DeleteTopicResponse` following the existing topic/token pattern: resolve the
client via `get_client`, build the transaction, conditionally apply
`commonTransactionParams`, execute with `wait_for_receipt=False`, fetch the
receipt with `validate_status=True`, and return the response built from
`ResponseCode(receipt.status).name`.

- No changes are needed in `tck/handlers/__init__.py` or
`tck/handlers/registry.py`, since the `topic` module is already imported and
will auto-register the new method.

💡 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 design choice 1 go ahead with option 3 and replan.

---

💬 Have feedback or questions? Drop into our discord!

[github-actions]

Hello, this is CommunityCallBot.

This is a reminder that the Hiero Python SDK Community Call will begin in approximately 3 hours and 15 minutes (14:00 UTC).

The call is an open forum where contributors and users can discuss topics, raise issues, and influence the direction of the Python SDK.

Details:

• Time: 14:00 UTC
• Join Link: Zoom Meeting

Disclaimer: This is an automated reminder. Please verify the schedule here for any changes.