threshold and list keys

Author: littletarzan

hip-1284.md

@@ -34,6 +34,16 @@ The precompile would return the following:
 
 By doing so, developers can build safer and more robust smart contracts that **refuse to interact with unsafe tokens** or alert administrators when unexpected configurations are found.
 
+`IHederaTokenService.sol` does expose `getTokenKey(address,uint)`
+```solidity
+interface IHederaTokenService {
+    function getTokenKey(address token, uint keyType)
+        external
+        returns (int64 responseCode, KeyValue memory key);
+}
+```
+, which erroneously returns threshold and list key types as empty in [keyTupleFor](https://github.com/hiero-ledger/hiero-consensus-node/blob/main/hedera-node/hedera-smart-contract-service-impl/src/main/java/com/hedera/node/app/service/contract/impl/utils/ConversionUtils.java#L1062) in the services codebase.
+
 ## User Stories
 1. As a dApp developer, I want to prevent tokens with malicious fee schedules from being deposited into my contract.
 2. As a protocol admin, I want to audit the fee characteristics of incoming tokens.