From da9a283acb5f67d42578656fe285b5be91b084db Mon Sep 17 00:00:00 2001 From: j pimmel Date: Wed, 24 Apr 2024 15:16:41 -0700 Subject: [PATCH] Changed status to implemented --- application/20231222-evm-vm-bridge.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/application/20231222-evm-vm-bridge.md b/application/20231222-evm-vm-bridge.md index 2b545da7..c14b259b 100644 --- a/application/20231222-evm-vm-bridge.md +++ b/application/20231222-evm-vm-bridge.md @@ -1,5 +1,5 @@ --- -status: approved +status: implemented flip: 237 title: Flow EVM VM Bridge authors: Giovanni Sanchez (giovanni.sanchez@dapperlabs.com) @@ -2018,4 +2018,4 @@ Interchain Token Service](https://github.com/AnChainAI/anchain-axelar-dapper-flo - What if any issues with the NFT ID type differences - `UInt64` in Cadence & `uint256` in Solidity - present for potential overflow & collisions when moving between EVM -> Flow? - Are there additional metadata mechanisms we should consider in the contract designs that would help platforms better - represent bridged assets? \ No newline at end of file + represent bridged assets?