# ckETH: a canister-issued Ether twin token on the IC **URL:** \ **Category:** Developers\ **Created:** [September 8, 2023, 2:30pm UTC](https://forum.dfinity.org/t/cketh-a-canister-issued-ether-twin-token-on-the-ic/22819 "2023-09-08T14:30:44Z")\ **Posts on this page:** 20\ **Page:** 11
**Author:** ![gregory-demay](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/gregory-demay/32/8165_2.png) [@gregory-demay](https://forum.dfinity.org/u/gregory-demay)\ **Post date:** [September 11, 2024, 7:46am UTC](https://forum.dfinity.org/t/cketh-a-canister-issued-ether-twin-token-on-the-ic/22819/208 "2024-09-11T07:46:23Z")
> So expect a proposal to replace that provider soon. Proposal [132415](https://dashboard.internetcomputer.org/proposal/132415) ---
**Author:** ![Gotcha](https://avatars.discourse-cdn.com/v4/letter/g/898d66/32.png) [@Gotcha](https://forum.dfinity.org/u/Gotcha)\ **Post date:** [September 11, 2024, 12:09pm UTC](https://forum.dfinity.org/t/cketh-a-canister-issued-ether-twin-token-on-the-ic/22819/209 "2024-09-11T12:09:39Z")
Now it’s llamarpc’s turn to be failed, no? ---
**Author:** ![gregory-demay](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/gregory-demay/32/8165_2.png) [@gregory-demay](https://forum.dfinity.org/u/gregory-demay)\ **Post date:** [September 11, 2024, 12:13pm UTC](https://forum.dfinity.org/t/cketh-a-canister-issued-ether-twin-token-on-the-ic/22819/210 "2024-09-11T12:13:24Z")
Unfortunately, there is good news and there is bad news: - The good: [Proposal 132415](https://dashboard.internetcomputer.org/proposal/132415) was adopted and it did fix the problem regarding `Ankr`, (which was replaced by a `https://eth-pokt.nodies.app` from Pocket Network). Example from the [logs](https://sv3dd-oaaaa-aaaar-qacoa-cai.raw.icp0.io/logs?sort=desc): ```auto Got response (with 87 bytes): {\"id\":588,\"jsonrpc\":\"2.0\",\"result\":{\"number\":\"0x13c453f\",\"baseFeePerGas\":\"0x72671ea6\"}} from url: https://eth-pokt.nodies.app with status: 200 ``` - The bad: LlamaNodes is down since this morning and always return `no response`. Example from the [logs](https://sv3dd-oaaaa-aaaar-qacoa-cai.raw.icp0.io/logs?sort=desc): ```auto Got response (with 74 bytes): {\"id\":593,\"jsonrpc\":\"2.0\",\"error\":{\"code\":-32603,\"message\":\"no response\"}} from url: https://eth.llamarpc.com with status: 200 ``` We notified them (among others) on their [Discord](https://discord.com/channels/1049349903408713809/1049349904104964199/1283360714139893783) and opened a ticket. ---
**Author:** ![Gotcha](https://avatars.discourse-cdn.com/v4/letter/g/898d66/32.png) [@Gotcha](https://forum.dfinity.org/u/Gotcha)\ **Post date:** [September 11, 2024, 12:20pm UTC](https://forum.dfinity.org/t/cketh-a-canister-issued-ether-twin-token-on-the-ic/22819/211 "2024-09-11T12:20:18Z")
It’s time to push forward our native ethereum nodes and get rid of all those RPCs once for all. ---
**Author:** ![darwin](https://avatars.discourse-cdn.com/v4/letter/d/ee7513/32.png) [@darwin](https://forum.dfinity.org/u/darwin)\ **Post date:** [September 11, 2024, 12:23pm UTC](https://forum.dfinity.org/t/cketh-a-canister-issued-ether-twin-token-on-the-ic/22819/212 "2024-09-11T12:23:26Z")
There should be somekind of announcment people to hold back of interacting with mint/bridge of ck tokens - currently peope are “bridgint” ck tokens and get nothing in return and this is not good experience - having your assets stucked in uncertainity ---
**Author:** ![dantol29](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/dantol29/32/20601_2.png) [@dantol29](https://forum.dfinity.org/u/dantol29)\ **Post date:** [September 11, 2024, 1:31pm UTC](https://forum.dfinity.org/t/cketh-a-canister-issued-ether-twin-token-on-the-ic/22819/213 "2024-09-11T13:31:19Z")
There should be a mechanism that uses another RPC provider if one fails ---
**Author:** ![darwin](https://avatars.discourse-cdn.com/v4/letter/d/ee7513/32.png) [@darwin](https://forum.dfinity.org/u/darwin)\ **Post date:** [September 12, 2024, 4:29am UTC](https://forum.dfinity.org/t/cketh-a-canister-issued-ether-twin-token-on-the-ic/22819/214 "2024-09-12T04:29:44Z")
> [@gregory-demay](#): > > We notified them (among others) on their [Discord](https://discord.com/channels/1049349903408713809/1049349904104964199/1283360714139893783) and opened a ticket. Do you have any response ? their discord seems ghost town ---
**Author:** ![Gotcha](https://avatars.discourse-cdn.com/v4/letter/g/898d66/32.png) [@Gotcha](https://forum.dfinity.org/u/Gotcha)\ **Post date:** [September 12, 2024, 4:38am UTC](https://forum.dfinity.org/t/cketh-a-canister-issued-ether-twin-token-on-the-ic/22819/215 "2024-09-12T04:38:55Z")
I saw all previous deposits have went through 6 hours ago. However new errors can be seen like “Failed to get ERC-20 logs from block 20\_722\_325 to block 20\_723\_124” in logs and I assume newly created deposits will still be stuck. ---
**Author:** ![darwin](https://avatars.discourse-cdn.com/v4/letter/d/ee7513/32.png) [@darwin](https://forum.dfinity.org/u/darwin)\ **Post date:** [September 12, 2024, 6:06am UTC](https://forum.dfinity.org/t/cketh-a-canister-issued-ether-twin-token-on-the-ic/22819/216 "2024-09-12T06:06:18Z")
My deposit has not arrived - it has passed ~ 36 hours ---
**Author:** ![dantol29](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/dantol29/32/20601_2.png) [@dantol29](https://forum.dfinity.org/u/dantol29)\ **Post date:** [September 12, 2024, 11:33am UTC](https://forum.dfinity.org/t/cketh-a-canister-issued-ether-twin-token-on-the-ic/22819/217 "2024-09-12T11:33:34Z")
Still does not work: [https://sv3dd-oaaaa-aaaar-qacoa-cai.raw.icp0.io/dashboard](https://sv3dd-oaaaa-aaaar-qacoa-cai.raw.icp0.io/dashboard) There are 5 users waiting for ckETH: > **[CkEthDeposit | Address 0x7574eb42ca208a4f6960eccafdf186d627dcc175 | Etherscan](https://etherscan.io/address/0x7574eb42ca208a4f6960eccafdf186d627dcc175)** > > The Contract Address 0x7574eb42ca208a4f6960eccafdf186d627dcc175 page allows users to view the source code, transactions, balances, and analytics for the contract address. Users can also interact and make transactions to the contract directly on... ---
**Author:** ![gregory-demay](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/gregory-demay/32/8165_2.png) [@gregory-demay](https://forum.dfinity.org/u/gregory-demay)\ **Post date:** [September 12, 2024, 1:21pm UTC](https://forum.dfinity.org/t/cketh-a-canister-issued-ether-twin-token-on-the-ic/22819/218 "2024-09-12T13:21:14Z")
The minter seems to be back on track since the last proposal [132474](https://dashboard.internetcomputer.org/proposal/132474) was just adopted. # What happened? 1. Proposal [132415](https://dashboard.internetcomputer.org/proposal/132415) was executed at 2024.09.11 09:28 (UTC) and successfully replaced the Ethereum JSON-RPC provider Ankr ([rpc.ankr.com](http://rpc.ankr.com)) with `eth-pokt.nodies.app` from [Pocket Network](https://www.pokt.network/). 2. Unfortunately, at the same time the Ethereum JSON-RPC provider LlamaNodes `eth.llamarpc.com` was down and constantly replying with `no response`. This seems to have been resolved since the ckETH minter did make progress around 2024.09.11 22:00 (UTC) but had stopped since then. 3. The [logs](https://sv3dd-oaaaa-aaaar-qacoa-cai.raw.icp0.io/logs?sort=desc) show that responses from the Ethereum JSON-RPC provider Pocket Network (`eth-pokt.nodies.app`) differ between the replicas resulting in consensus failures. Proposal [132474](https://dashboard.internetcomputer.org/proposal/132474) replaced the Ethereum JSON-RPC provider Pocket Network (`eth-pokt.nodies.app`) with the Ethereum JSON-RPC provider BlockPi (`[https://ethereum.blockpi.network/v1/rpc/public](https://ethereum.blockpi.network/v1/rpc/public)). # Future Plans Currently, the ckETH minter uses JSON-RPC providers that do not require API keys and there are unfortunately not that many that also support IPv6 connectivity. Our goal to improve the current situation is to use the EVM-RPC canister, that does use JSON-RPC providers with API keys, to be able to use more providers. This will also allow us to use a more robust strategy (e.g. require consensus between responses from 3 providers when 4 are queried), so that a provider being down would not impact the availability of the ckETH minter. This does require some changes: 1. on the ckETH minter, to be able to communicate with the EVM-RPC canister. Those changes are already implemented and could be activated via an upgrade proposal. 2. on the EVM-RPC canister (see this [post](https://forum.dfinity.org/t/evm-rpc-canister/23313/53) for more details), which are currently on-going. That means that we are doing steady progress on that front and should be able to use the EVM-RPC canister in the next few weeks. ---
**Author:** ![darwin](https://avatars.discourse-cdn.com/v4/letter/d/ee7513/32.png) [@darwin](https://forum.dfinity.org/u/darwin)\ **Post date:** [September 12, 2024, 4:04pm UTC](https://forum.dfinity.org/t/cketh-a-canister-issued-ether-twin-token-on-the-ic/22819/219 "2024-09-12T16:04:58Z")
Thank you and the team for all your work ---
**Author:** ![Gotcha](https://avatars.discourse-cdn.com/v4/letter/g/898d66/32.png) [@Gotcha](https://forum.dfinity.org/u/Gotcha)\ **Post date:** [September 12, 2024, 11:08pm UTC](https://forum.dfinity.org/t/cketh-a-canister-issued-ether-twin-token-on-the-ic/22819/221 "2024-09-12T23:08:02Z")
Does that mean native ethereum integration is not on the plan anymore? ---
**Author:** ![gregory-demay](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/gregory-demay/32/8165_2.png) [@gregory-demay](https://forum.dfinity.org/u/gregory-demay)\ **Post date:** [October 22, 2024, 9:30am UTC](https://forum.dfinity.org/t/cketh-a-canister-issued-ether-twin-token-on-the-ic/22819/222 "2024-10-22T09:30:54Z")
Hi everyone 👋! A couple of announcements regarding the ckETH minter: - As mentioned in this [post](https://forum.dfinity.org/t/cketh-a-canister-issued-ether-twin-token-on-the-ic/22819/218), the ckETH minter is now ready to use the EVM-RPC canister with a 3-out-of-4 consensus strategy. Expect a proposal in the next few days. - We are now prioritising supporting subaccounts, both for deposits and withdrawals. This should be ready in a couple of weeks. ---
**Author:** ![gregory-demay](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/gregory-demay/32/8165_2.png) [@gregory-demay](https://forum.dfinity.org/u/gregory-demay)\ **Post date:** [November 28, 2024, 3:27pm UTC](https://forum.dfinity.org/t/cketh-a-canister-issued-ether-twin-token-on-the-ic/22819/223 "2024-11-28T15:27:02Z")
Hi everyone 👋! Quick update related to the previous [announcements](https://forum.dfinity.org/t/cketh-a-canister-issued-ether-twin-token-on-the-ic/22819/222) > - As mentioned in this [post](https://forum.dfinity.org/t/cketh-a-canister-issued-ether-twin-token-on-the-ic/22819/218), the ckETH minter is now ready to use the EVM-RPC canister with a 3-out-of-4 consensus strategy. Expect a proposal in the next few days. This was successfully rolled out with proposal [133796](https://dashboard.internetcomputer.org/proposal/133796) that was executed a month ago (2024-10-25). Since then, the ckETH/ckERC20 minter enjoyed a refreshingly problem-free interaction with Ethereum 🎉. This can for example be seen by the steady tracking of the last finalized block shown below (no plateau is good). ![Last finalized block tracked by the minter](https://us1.discourse-cdn.com/flex023/uploads/dfn/original/3X/8/b/8b809187683353236f0766bff09d8238b0fb4bc4.png) > - We are now prioritising supporting subaccounts, both for deposits and withdrawals. This should be ready in a couple of weeks. Proposal [134264](https://dashboard.internetcomputer.org/proposal/134264) was successfully executed today and that means there is now a single helper smart contract ([0x18901044688d3756c35ed2b36d93e6a5b8e00e68](https://etherscan.io/address/0x18901044688d3756c35ed2b36d93e6a5b8e00e68) 🟢) that can handle both deposits of ETH and ERC-20, while specifying a full ledger account (principal and subaccount) 🎉 ![Specify a ledger subaccount for your deposit!](https://us1.discourse-cdn.com/flex023/uploads/dfn/original/3X/3/c/3ca3f73d829aa944a428007d1b926ae15a7e1963.png) ℹ As mentioned in the proposal [134264](https://dashboard.internetcomputer.org/proposal/134264), the other helper smart contracts: - for ETH: [0x7574eB42cA208A4f6960ECCAfDF186D627dCC175](https://etherscan.io/address/0x7574eB42cA208A4f6960ECCAfDF186D627dCC175) 🟠 - for ERC-20 [0x6abDA0438307733FC299e9C229FD3cc074bD8cC0](https://etherscan.io/address/0x6abDA0438307733FC299e9C229FD3cc074bD8cC0) 🟠 are considered **deprecated** and we invite all developers to switch to using the new contract. The current plan is to reduce the frequency at which the logs of those deprecated smart contracts are scraped in a couple of months. ---
**Author:** ![ICPSwap](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/icpswap/32/11193_2.png) [@ICPSwap](https://forum.dfinity.org/u/ICPSwap)\ **Post date:** [November 30, 2024, 4:22am UTC](https://forum.dfinity.org/t/cketh-a-canister-issued-ether-twin-token-on-the-ic/22819/224 "2024-11-30T04:22:28Z")
Dear Grégory @Gotcha and the team, Thank you so much for the update! Regarding the latest mint contract, we encountered an issue: when minting ckUSDC, we receive the following error: _Gas estimation failed: Error: cannot estimate gas; transaction may fail or may require manual gas limit._ Additionally, we’ve observed many failed transactions with this latest mint contract: > **[CkDeposit | Address 0x18901044688d3756c35ed2b36d93e6a5b8e00e68 | Etherscan](https://etherscan.io/address/0x18901044688d3756c35ed2b36d93e6a5b8e00e68)** > > The Contract Address 0x18901044688d3756c35ed2b36d93e6a5b8e00e68 page allows users to view the source code, transactions, balances, and analytics for the contract address. Users can also interact and make transactions to the contract directly on... ![1](https://us1.discourse-cdn.com/flex023/uploads/dfn/original/3X/1/4/1498cd08f26a2f2af6dbbb3bd227dfb2178b06bf.png) Could you please help investigate if there is an issue? Thank you so much for your assistance! ---
**Author:** ![peterparker](https://avatars.discourse-cdn.com/v4/letter/p/b9bd4f/32.png) [@peterparker](https://forum.dfinity.org/u/peterparker)\ **Post date:** [November 30, 2024, 6:47am UTC](https://forum.dfinity.org/t/cketh-a-canister-issued-ether-twin-token-on-the-ic/22819/225 "2024-11-30T06:47:49Z")
I noticed the same error this morning as I was testing OISY and shared the question with the team on internal channels for visibility. ---
**Author:** ![gregory-demay](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/gregory-demay/32/8165_2.png) [@gregory-demay](https://forum.dfinity.org/u/gregory-demay)\ **Post date:** [November 30, 2024, 10:22am UTC](https://forum.dfinity.org/t/cketh-a-canister-issued-ether-twin-token-on-the-ic/22819/226 "2024-11-30T10:22:37Z")
Thanks @ICPSwap and @peterparker for reporting the problem. It seems the faulty transactions, such as this [one](https://etherscan.io/tx/0x202252e8290e3a37245ad966ad3b3095742d7550177ed85530b460ddd8bb5bd8) target a method (`deposit`) that doesn’t exist on the new [helper smart contract](https://etherscan.io/address/0x18901044688D3756C35Ed2b36D93e6a5B8e00E68). It should be one of 1. `depositErc20` (`0xdb9751af`) 2. `depositEth` (`0x17c819c4`) Note that given those methods have an additional parameter (subaccount) in contrast to their equivalent method on the previous helper smart contract (besides having a different name on purpose), they cannot have the same function signature and hence must have a different function selector. I hope this helps. Feel free to reach out if you have any question. ---
**Author:** ![gregory-demay](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/gregory-demay/32/8165_2.png) [@gregory-demay](https://forum.dfinity.org/u/gregory-demay)\ **Post date:** [November 30, 2024, 10:35am UTC](https://forum.dfinity.org/t/cketh-a-canister-issued-ether-twin-token-on-the-ic/22819/227 "2024-11-30T10:35:24Z")
It seems there was un unattended breaking change that sneaked in with [proposal 134264](https://dashboard.internetcomputer.org/proposal/134264): 1. The value of `get_minter_info::erc20_helper_contract_address` and `get_minter_info:: eth_helper_contract_address` was changed to point to the new helper smart contract, which is a breaking change because as explained above it cannot expose the same ABI. We plan on doing the following fixes: 1. Revert the value of those 2 fields back to the previous helper smart contract addresses. 2. Add a new field in `get_minter_info` to give the address of the new helper smart contract address. ---
**Author:** ![peterparker](https://avatars.discourse-cdn.com/v4/letter/p/b9bd4f/32.png) [@peterparker](https://forum.dfinity.org/u/peterparker)\ **Post date:** [November 30, 2024, 2:58pm UTC](https://forum.dfinity.org/t/cketh-a-canister-issued-ether-twin-token-on-the-ic/22819/228 "2024-11-30T14:58:07Z")
The issue was treated as an urgent incident and resolved with proposal [134344](https://dashboard.internetcomputer.org/proposal/134344). I tested a conversion in OISY, and it worked out. Shoutout to @gregory-demay and team for fixing this on a Saturday. [Previous page](https://forum.dfinity.org/t/cketh-a-canister-issued-ether-twin-token-on-the-ic/22819.md?page=10) [Next page](https://forum.dfinity.org/t/cketh-a-canister-issued-ether-twin-token-on-the-ic/22819.md?page=12)