From 4f80bf852214db1b5184a8d95c3595df4bcd0a3e Mon Sep 17 00:00:00 2001 From: Jessie Mongeon <133128541+jessiemongeon1@users.noreply.github.com> Date: Fri, 13 Dec 2024 09:37:12 -0600 Subject: [PATCH] KYT check info (#3879) --- .../multi-chain/chain-key-tokens/overview.mdx | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/docs/developer-docs/multi-chain/chain-key-tokens/overview.mdx b/docs/developer-docs/multi-chain/chain-key-tokens/overview.mdx index 1b04ffbf64..3e41d08f21 100644 --- a/docs/developer-docs/multi-chain/chain-key-tokens/overview.mdx +++ b/docs/developer-docs/multi-chain/chain-key-tokens/overview.mdx @@ -34,6 +34,12 @@ In addition to the requirement that a chain-key token must adhere to an [ICRC](/ - Builds must be reproducible. - The canisters must be immutable or controlled by a DAO, for example, an [SNS](https://internetcomputer.org/docs/current/developer-docs/daos/sns) or a [threshold canister](https://github.com/dfinity/threshold) with a large number of verified voters. +## Know-your-transaction (KYT) checks + +The ckBTC minter interacts with a dedicated KYT canister that executes KYT checks. Checks are applied to both incoming and outgoing transactions. + +The ckETH and ckERC20 minters implement a local OFAC checklist for both incoming and outgoing transactions. + ## Available chain-key tokens The current chain-key tokens are supported: