From 7204c94e81a7e4184f7c9eb5bfaf3b185fcd1309 Mon Sep 17 00:00:00 2001 From: Ilaria <43253244+ilariae@users.noreply.github.com> Date: Mon, 23 Dec 2024 10:54:31 +0100 Subject: [PATCH] Update build/contract-integrations/native-token-transfers/deployment-process/deploy-to-evm.md Co-authored-by: Erin Shaben --- .../deployment-process/deploy-to-evm.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/build/contract-integrations/native-token-transfers/deployment-process/deploy-to-evm.md b/build/contract-integrations/native-token-transfers/deployment-process/deploy-to-evm.md index 4aab34d9..125e75b3 100644 --- a/build/contract-integrations/native-token-transfers/deployment-process/deploy-to-evm.md +++ b/build/contract-integrations/native-token-transfers/deployment-process/deploy-to-evm.md @@ -47,8 +47,8 @@ For more detailed information, see the [Deployment Models](/docs/learn/messaging ### Key Differences Between Modes - - **Burn-and-Mint** - tokens must implement custom `mint` and `burn` functions, allowing each chain to manage token issuance independently - - **Hub-and-Spoke** - tokens only need to be ERC20 compliant, with the hub chain acting as the source of truth for supply consistency + - **Burn-and-mint** - tokens must implement custom `mint` and `burn` functions, allowing each chain to manage token issuance independently + - **Hub-and-spoke** - tokens only need to be ERC20 compliant, with the hub chain acting as the source of truth for supply consistency ## Deploy NTT