diff --git a/iips/IIP-0009/IIP-0009.md b/iips/IIP-0009/IIP-0009.md index 65c6548..21d3a43 100644 --- a/iips/IIP-0009/IIP-0009.md +++ b/iips/IIP-0009/IIP-0009.md @@ -229,14 +229,14 @@ This proposal is designed to be fully backward compatible with the existing IOTA The following test cases SHOULD be implemented to validate the correctness and completeness of the AI Account model: -| Test Case | Description | Reference Move Implementation | -| ------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------- | -| **Single-key EOA replication** | An AI Account that replicates standard single-key cryptographic authentication, including key rotation capability. | https://github.com/iotaledger/iota/tree/develop/examples/move/iotaccount | -| **Dynamic multisig** | An AI Account authenticated via dynamic multisignature logic based on signatures or on-chain capabilities. | https://github.com/lzpap/isafe/tree/main/contracts/isafe | -| **Function-Call keys** | An AI Account authenticated using a method similar to [Near's Function-Call keys](https://docs.near.org/protocol/access-keys), limiting access only to the execution of some methods for an account. | https://github.com/iotaledger/iota/tree/develop/examples/move/function_keys | -| **Spending limit** | An AI Account where several users are authorized to access but having a specific allowance of IOTA conis set for each one. | https://github.com/iotaledger/iota/tree/develop/examples/move/spending_limit | -| **Third-party authentication** | An AI Account authenticated using an external or third-party verification mechanism, such as ZK proofs validation. | https://github.com/iotaledger/iota/pull/10227 | -| **Time locked** | An AI Account where the authentication is constrained by time. | https://github.com/iotaledger/iota/tree/develop/examples/move/time_locked | +| Test Case | Description | Reference Move Implementation | +| ------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------- | +| **Single-key EOA replication** | An AI Account that replicates standard single-key cryptographic authentication, including key rotation capability. | https://github.com/iotaledger/iota/tree/develop/examples/move/abstract_iota_accounts/iotaccount | +| **Dynamic multisig** | An AI Account authenticated via dynamic multisignature logic based on signatures or on-chain capabilities. | https://github.com/lzpap/isafe/tree/main/contracts/isafe | +| **Function-Call keys** | An AI Account authenticated using a method similar to [Near's Function-Call keys](https://docs.near.org/protocol/access-keys), limiting access only to the execution of some methods for an account. | https://github.com/iotaledger/iota/tree/develop/examples/move/abstract_iota_accounts/function_call_keys | +| **Spending limit** | An AI Account where several users are authorized to access but having a specific allowance of IOTA conis set for each one. | https://github.com/iotaledger/iota/tree/develop/examples/move/abstract_iota_accounts/spending_limit | +| **Third-party authentication** | An AI Account authenticated using an external or third-party verification mechanism, such as ZK proofs validation. | https://github.com/iotaledger/iota/pull/10227 | +| **Time locked** | An AI Account where the authentication is constrained by time. | https://github.com/iotaledger/iota/tree/develop/examples/move/abstract_iota_accounts/time_locked | ## Reference Implementation