From e976537cf3c70aaa8673328a9c5e08ed92110656 Mon Sep 17 00:00:00 2001 From: Connor Davis <17688291+PoisonPhang@users.noreply.github.com> Date: Tue, 3 Oct 2023 22:06:40 -0500 Subject: [PATCH] fix(site): an MVP of a beta --- site/src/routes/blog/ics20-transfers-to-ethereum/+page.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/site/src/routes/blog/ics20-transfers-to-ethereum/+page.md b/site/src/routes/blog/ics20-transfers-to-ethereum/+page.md index dcd1350dbd..7c1fc9ab83 100644 --- a/site/src/routes/blog/ics20-transfers-to-ethereum/+page.md +++ b/site/src/routes/blog/ics20-transfers-to-ethereum/+page.md @@ -35,6 +35,10 @@ Claim $UNO from the Union faucet for bridging usage. If you opt-in to sharing yo IBC transfers from `union-testnet-3` to `sepolia` are just contract interactions, which need to be sent to either Sepolia or Union, depending on the transfer direction. We start by sending $UNO to Sepolia (Ethereum Testnet), and then back again. This showcase uses a single-threaded relayer with simple nonce management. This means it is not optimized for throughput, resulting in a lot of queued transactions. It's an MVP of a beta product after all. Optimized nonce management should land next week. +IBC is as fast as the underlying chains. When you do Tendermint to Tendermint transactions, IBC is quite fast because the finality time is 6 seconds. However, when connecting to Sepolia, which has the same configuration as the Ethereum Mainnet, it takes two epochs for a block to finalize, which is approximately thirteen minutes. However, we are using the "justified" (or "safe") commitment level to decrease the required number of epocs to one, which is approximately six and a half minutes. + +If you want to learn more about these commitment levels, read [What are Ethereum commitment levels? Latest, Safe, Finalized](https://www.alchemy.com/overviews/ethereum-commitment-levels), from the Alchemy team. + Inside the testnet, a full IBC transfer is now occuring: