Enable KeyList Support in HTS Precompile #1069
Conversation
✅ Deploy Preview for hedera-hips ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
|
|
||
| IHederaTokenService.TokenKey memory key = IHederaTokenService.TokenKey({ | ||
| keyType: KeyType.SUPPLY, | ||
| key: KeyList({ |
There was a problem hiding this comment.
Q: Are we aiming to support both KeyList and Threshold key types? I can see only KeyList mentioned but this example is using a Threshold type for the KeyList.
There was a problem hiding this comment.
My suggestion is to simplify the HIP and only support threshold key types with threshold = 1.
This will satisfy the use case where developers want to define a list of potential administrators for a specific function (i.e. supply key), each with the same permissions.
I don't think other cases are technically feasible: since Ethereum lacks the concept of native multi signature transactions, we will never reach a threshold > 1 in any case.
Enable KeyList Support in HTS updateTokenKeys Precompile
This update adds support for using complex keys (
KeyLists) within theupdateTokenKeysHTS precompile function, allowing developers to set token keys with multiple signatories directly in smart contracts. While complex keys are supported in the SDK, this enhancement allows on-chain token management with multi-signature and threshold-controlled permissions, expanding flexibility for applications requiring decentralized control over token keys.