diff --git a/docs/developer-docs/multi-chain/faq/ckbtc-faq.mdx b/docs/developer-docs/multi-chain/faq/ckbtc-faq.mdx deleted file mode 100644 index 211ea727aa..0000000000 --- a/docs/developer-docs/multi-chain/faq/ckbtc-faq.mdx +++ /dev/null @@ -1,194 +0,0 @@ ---- -keywords: [advanced, faq, ckbtc, bitcoin] ---- - -import { MarkdownChipRow } from "/src/components/Chip/MarkdownChipRow"; - -# ckBTC FAQ - - - -The following questions and answers are from the POV of a developer who wants to know things such as "how does a canister send ckBTC?". - -For questions from the POV of a user who wishes to know how to hold, send, receive these tokens, please see the user FAQs. - -### How do I write a smart contract that uses ckBTC? - -The best place to start is to follow the [ckBTC and Bitcoin integration developer tutorial](/docs/current/tutorials/developer-journey/level-4/4.3-ckbtc-and-bitcoin). This tutorial will guide you through the process of creating a smart contract that uses ckBTC or integrates with Bitcoin. - -### What is the purpose of ckBTC? - -Chain-key Bitcoin (ckBTC) is a token on the Internet Computer that is backed 1:1 by bitcoin (BTC). It is designed to integrate Bitcoin with the Internet Computer Protocol (ICP) and decentralized finance (DeFi) applications. ckBTC is an ICP-native token that uses chain-key cryptography to own and control all underlying bitcoin, extending the ICP protocol stack so the blockchain behaves like a faster, less expensive, and more environmentally sustainable solution than the Bitcoin network. - -ckBTC facilitates bitcoin holders to participate in the DeFi ecosystem, activating the world’s largest crypto economy. It offers a secure and scalable environment to use bitcoin in DeFi applications, including lending, borrowing, asset management, decentralized exchanges, and more. - -ckBTC is not a bridged or wrapped token; it is a direct link between the Bitcoin network and the Internet Computer, reducing the risks tied to bridges. This approach not only tackles security concerns but also launches Bitcoin into a world of better adaptability and user experiences. - -ckBTC also offers the first bonafide use case for bringing smart contracts to BTC. Building DeFi on ICP is more secure, faster, environmentally friendly, and cost-effective. - -### What specific problem does ckBTC aim to solve within the Bitcoin ecosystem? - -ckBTC aims to solve the following problems: - -1. **Lack of programmability**: The Bitcoin blockchain lacks a programmable layer that is expressive enough to build complex decentralized applications in the form of smart contracts - -2. **Intermediary dependence**: Self-custody solutions are cumbersome and not ideal for non-technical people but the alternative relies on trusted parties such as custody providers, which is not ideal, either. - -3. **Limited integration with DeFi**: Bitcoin has been largely unable to integrate smoothly with decentralized finance (DeFi) applications. ckBTC, being an ICP-native token backed 1:1 with real BTC and governed on chain by ICP smart contracts, facilitates bitcoin holders to participate in the DeFi ecosystem. - -4. **High latency and fees**: Every Bitcoin transaction is processed with the same low throughput, high latency, and high fees native to the Bitcoin network. ckBTC, being a digital bitcoin twin created by chain-key cryptography and canister smart contracts, can be sent with 2–5 second finality and negligible fees. - -5. **Security concerns with bridges**: ckBTC gets rid of the need for bridges, reducing the risks tied to them. - -### How does ckBTC relate to Bitcoin? - -The Internet Computer integrates with the Bitcoin network at a protocol level, allowing ICP canister smart contracts to create Bitcoin addresses and send and receive bitcoin directly on the Bitcoin network. This integration is made up of two key building blocks: network integration and chain-key ECDSA. With these building blocks, canisters can directly and securely hold, receive, and send bitcoin seamlessly as if the Internet Computer and the Bitcoin network were one blockchain [source](https://internetcomputer.org/bitcoin-integration/faq#bitcoin-integration). - -### How is ckBTC transaction different from a regular Bitcoin transaction? - -ckBTC is different from regular Bitcoin transactions in several ways: - -1. **Speed and cost**: ckBTC can be sent with 1-2 second finality and negligible fees, making it much faster and cheaper than regular Bitcoin transactions which can take roughly an hour and have high fees. - -2. **Smart contract integration**: Canister smart contracts can programmatically hold and transfer ckBTC, making it possible to develop fully onchain Layer-2 applications for Bitcoin. This is not possible with regular Bitcoin transactions. - -3. **Fixed transaction fees**: ckBTC transaction fees are fixed. Bitcoin transaction fees depend on the size of the transaction and the current backlog of transactions in the Bitcoin network (if the load is high, the fee rate is high). - -### Why should I choose ckBTC for my application or service? - -Choosing ckBTC for your application or service comes with several advantages: - -1. **Trustless Bitcoin-based commerce**: ckBTC allows Bitcoin-based commerce to run natively on Internet Computer Protocol (ICP) smart contracts, enabling custodial solutions where the custodian is a decentralized application, mitigating the third-party risk. - -2. **Security**: ckBTC is truly decentralized, potentially reversing the negative DeFi trend caused by large scale hacks and rug pulls. - -3. **Low fees and fast transactions**: ckBTC acts as a local ledger facilitating fast transactions with low fees (10 satoshis), and only settles transactions on the Bitcoin network when necessary. - -4. **Easy integration**: Compatible with the ICRC-1 token standard, and now also ICRC-2, ckBTC is easy to integrate into dapps running on the Internet Computer. - -5. **Verifiable**: All transfer activity and metrics of the ckBTC ledger and ckBTC minter are verifiable on chain. Issuing and redeeming ckBTC also goes through Know Your Transaction (KYT) checks to protect end users by ensuring no tainted bitcoin enters the Internet Computer blockchain or is transferred out to tainted Bitcoin addresses. - -### What advantages does ckBTC offer in terms of speed, fees, and security? - -Chain-key Bitcoin (ckBTC) offers several advantages in terms of speed, fees, and security: - -**Speed**: ckBTC transactions are finalized within seconds, which is a significant speed-up compared to traditional Bitcoin transactions that can take up to an hour or more for 6 confirmations. - -**Fees**: The transaction fees for ckBTC are fixed and negligible, costing only 0.0000001 ckBTC. This is approximately two orders of magnitude lower than traditional Bitcoin miner fees. - -**Security**: ckBTC is backed 1:1 by Bitcoin (BTC), meaning 1 ckBTC can always be redeemed for 1 BTC and vice versa. Unlike other tokens pegged to Bitcoin, ckBTC does not rely on a third-party bridge for conversion between BTC and ckBTC, making it a more secure alternative. The security of ckBTC has been assessed for potential risks, including double-spending of funds, denial-of-service attacks, and insufficient access controls. - -Furthermore, ckBTC is issued and redeemed via canister smart contracts that are verifiable by anyone at any time, eliminating centralized custodians, bridges, and traditional cloud providers that could act as attack vectors. - -### How can I integrate ckBTC into my existing applications or platforms? - -To integrate ckBTC into your existing applications or platforms, you can follow the developer documentation. Here are some resources that you might find useful: - -1. [ckBTC developer documentation page](/docs/current/developer-docs/multi-chain/chain-key-tokens/ckbtc/overview): This page provides detailed information about ckBTC, including its functionality and how it works. - -2. [ckBTC minter GitHub repository](https://github.com/dfinity/ic/tree/master/rs/bitcoin/ckbtc/minter): This repository contains the code for the ckBTC minter, which is responsible for minting and burning ckBTC. - -3. [Creating a ckBTC point of sale dapp](https://github.com/dfinity/examples/tree/master/motoko/ic-pos): This is another sample code for a ckBTC point of sale dapp. - -If you need further assistance, you can also ask questions in the [Internet Computer Developer Forum](https://forum.dfinity.org). - -### What are the technical requirements for developers to work with ckBTC? - -For more specific technical requirements, developers may want to refer to the [ckBTC API reference](/docs/current/references/ckbtc-reference) and the [GitHub repository](https://github.com/dfinity/ic/tree/master/rs/bitcoin/ckbtc/minter) for ckBTC. They might also find it helpful to follow the [developer journey for ckBTC and Bitcoin integration](/docs/current/tutorials/developer-journey/level-4/4.3-ckbtc-and-bitcoin) and to look at examples of [deploying a Bitcoin dapp](https://github.com/dfinity/examples/tree/master/motoko/basic_bitcoin) and [creating a ckBTC point of sale dapp](https://github.com/dfinity/examples/tree/master/motoko/ic-pos). - -### How does ckBTC ensure the security of the funds it handles? - -ckBTC ensures the security of the funds it handles through several measures: - -1. **No third-party bridges**: ckBTC does not rely on any third-party bridges for the conversion between BTC and ckBTC. This eliminates the vulnerabilities associated with bridge hacks, which have been a prime target for hackers due to their easy-to-compromise architecture. - -2. **Security assessment**: The security of ckBTC was a high priority for DFINITY and its community. A third party [security assesment](https://github.com/trailofbits/publications/blob/master/reviews/2023-06-dfinity-ckBTC-securityreview.pdf) was performed by Trail of Bits. The assessment covered testing the possible risks including double-spending of funds, denial-of-service attacks, and insufficient access controls. - -3. **KYT checks**: Cross-chain transactions go through Know Your Transaction (KYT) checks to protect honest users. KYT is a process that monitors and tracks financial transactions in order to detect and prevent fraudulent or criminal activity. - -4. **Trustless process**: The conversion of ckBTC back to BTC and vice versa is controlled at the Internet Computer protocol-level in a decentralized manner. - -5. **Decentralized process**: Every step of converting BTC to ckBTC and back is decentralized, meaning there are no centralized custodians, no bridges and no traditional cloud providers that could act as attack vectors. - -6. **1:1 pegging**: Securing ckBTC 1:1 with BTC is crucial as it eliminates the risk of depegging. - -### How does ckBTC handle transactions across multiple blockchains? - -ICP nodes communicate with Bitcoin nodes to download the Bitcoin network’s blocks and maintain its Unspent Transaction Output (UTXO) set. Using this information, the Internet Computer acts as a sidechain and hosts a trustless “bitcoin twin” called ckBTC that can be directly processed by canister smart contract logic and transferred with 1-3 seconds finality at near zero cost. - -To create ckBTC, a user transfers their bitcoin to a specific Bitcoin address (under the ckBTC minter’s control), which then triggers the minting of ckBTC for the user. The NNS dapp facilitates the conversion (in both directions). - -In the future, ckBTC will be available on other networks like Ethereum – also directly, and without bridges, thanks to chain-key cryptography integrations. - -### Can I build smart contracts that interact with ckBTC? - -Yes, you can build smart contracts that interact with ckBTC on the Internet Computer. - -### What are the transaction fees associated with ckBTC? - -The transaction fees for ckBTC on the Internet Computer are designed to be minimal. It is set at 0.0000001 ckBTC, which is equivalent to less than a cent or 10 satoshis. Users only need to pay the transaction fees of the Bitcoin network when converting Bitcoins to ckBTC or vice versa. See: [How ckBTC Solves the Dilemma of Blockchain Bridges](https://medium.com/dfinity/how-ckBTC-solves-the-dilemma-of-blockchain-bridges-ee8e0b72ee59#f847). - -In addition, there is a fee when bitcoins are retrieved. The formula `246*in + 7*out + 52` is used to determine the ckBTC minter’s fee in satoshi. Since transactions to redeem bitcoin usually have two inputs and outputs, the fee is typically 558 satoshi but can be lower if multiple retrieval requests are handled together.. See [Chain-key_Bitcoin wiki](https://wiki.internetcomputer.org/wiki/Chain-key_Bitcoin#firstHeading). - -There is also a Know Your Transaction (KYT) fee (currently 2000 satoshi) when converting BTC to ckBTC and vice versa. See [Chain-key_Bitcoin wiki](https://wiki.internetcomputer.org/wiki/Chain-key_Bitcoin#firstHeading). - -### How quickly can ckBTC transactions be finalized? - -ckBTC transactions can be finalized very quickly. They achieve a near-instant transaction finality with transaction confirmation within 1–2 seconds. This rapid finality can increase throughput and efficiency, facilitating more scalability for blockchain applications. - -### Who controls the development and governance of ckBTC? - -ckBTC has two main canister smart contracts (ckBTC `minter` and ckBTC `ledger`). Both are controlled by [the NNS DAO](https://wiki.internetcomputer.org/wiki/Chain-key_Bitcoin), updated via community proposals and run on the `pzp6e` subnet. - -The conversion of ckBTC back to BTC and vice versa is controlled at the Internet Computer protocol-level. This process is completely trustless and managed by automated software programs (smart contracts). - -### Is there a community-driven approach to decision-making? - -Yes, the Internet Computer blockchain employs a community-driven approach to decision-making. This is facilitated by the Network Nervous System (NNS), which is a decentralized algorithmic authority that oversees the network's operations and evolution. - -Each node provider is verified and voted in by token holders via the NNS. This means that the community of token holders has a say in the governance of the Internet Computer, including admitting new node providers to the network and assigning them to subnets based on community member votes. - -This approach ensures that the Internet Computer remains decentralized and that decisions are made collectively by the community, rather than being controlled by a single entity. - -### Can you provide examples of current applications that utilize ckBTC? - -Yes, there are several decentralized applications (dapps) on the Internet Computer that already support ckBTC. Here are some of them: - -1. [PlethoraGame](https://twitter.com/PlethoraGame) -2. [OpenChat](https://twitter.com/OpenChat) -3. [DSCVR](https://twitter.com/DSCVR1) -4. [ICLighthouse](https://twitter.com/ICLighthouse) -5. [DistriktApp](https://twitter.com/DistriktApp) -6. [Hot Or Not dapp](https://twitter.com/hotornot_dapp) -7. [infinity_swap](https://twitter.com/infinity_swap) -8. [catalyze_one](https://twitter.com/catalyze_one) - -You can follow these projects on Twitter to stay updated on their latest developments. - -### Does ckBTC incorporate KYT? - -Yes, cross-chain transactions go through KYT checks to protect honest users. Know Your Transaction (KYT) is a process that monitors and tracks financial transactions in order to detect and prevent fraudulent or criminal activity, such as money laundering or terrorist financing. - -If ckBTC were to operate without a KYT implementation, there would be a risk of 'tainted' bitcoin entering the Internet Computer, that an honest user could unknowingly withdraw. Such bitcoin may be rejected by CEXs, which means honest users could potentially lose their bitcoin when trying to sell. - -KYT is an important security component of ckBTC. Read more about how ckBTC implements KYT and the motivation behind it in [this forum post](https://forum.dfinity.org/t/ckbtc-and-kyt-compliance/18754). - -## Additional reading - -- [Bitcoin smart contracts are coming to Internet Computer DeFi projects](https://medium.com/dfinity/bitcoin-smart-contracts-are-coming-to-internet-computer-defi-projects-dd6786078853#e28c) -- [Chain-key bitcoin: A decentralized bitcoin twin](https://medium.com/dfinity/chain-key-bitcoin-a-decentralized-bitcoin-twin-ceb8f4ddf95e#2f6e) -- [Chain-key bitcoin](https://wiki.internetcomputer.org/wiki/Chain-key_Bitcoin#firstHeading) -- [Chain-key technology](https://internetcomputer.org/how-it-works#Chain-key-technology) -- [ckBTC ledger](https://wiki.internetcomputer.org/wiki/Chain-key_Bitcoin) -- [ckBTC sparks a new era on the Internet Computer](https://medium.com/dfinity/ckBTC-sparks-a-new-era-on-the-internet-computer-86463a7be20f#4690) -- [Deploying your first Bitcoin dapp](https://github.com/dfinity/examples/tree/master/motoko/basic_bitcoin) -- [Governance of the Internet Computer](https://wiki.internetcomputer.org/wiki/Governance_of_the_Internet_Computer#firstHeading) -- [How ckBTC solves the dilemma of blockchain bridges](https://medium.com/dfinity/how-ckBTC-solves-the-dilemma-of-blockchain-bridges-ee8e0b72ee59#08ea) -- [ICP multi-chain](https://internetcomputer.org/chainfusion) -- [Local development workflow](/docs/current/developer-docs/multi-chain/bitcoin/using-btc/local-development) -- [Native Bitcoin & ckBTC developer docs](/docs/current/developer-docs/multi-chain/bitcoin/overview) -- [Native Bitcoin on ICP](https://internetcomputer.org/bitcoin-integration) -- [Taking security seriously: two top ICP features assessed by Trail of Bits](https://medium.com/dfinity/taking-security-seriously-two-top-icp-features-assessed-by-trail-of-bits-4a0023ab1e68#8e43) -- [The Internet Computer blockchain takes a first step towards digital sovereignty in Europe](https://medium.com/dfinity/the-internet-computer-blockchain-takes-a-first-step-towards-digital-sovereignty-in-europe-782531894780#6f0c) -- [What is ckBTC?](/docs/current/tutorials/developer-journey/level-4/4.3-ckbtc-and-bitcoin#what-is-ckBTC) -- [What you need to know about Bitcoin integration and ckBTC](https://internetcomputer.org/bitcoin-integration/faq#bitcoin-integration) \ No newline at end of file diff --git a/docs/developer-docs/multi-chain/faq/ckerc20-faq.mdx b/docs/developer-docs/multi-chain/faq/ckerc20-faq.mdx deleted file mode 100644 index 42171cce59..0000000000 --- a/docs/developer-docs/multi-chain/faq/ckerc20-faq.mdx +++ /dev/null @@ -1,41 +0,0 @@ ---- -keywords: [advanced, faq, erc20] ---- - -import { MarkdownChipRow } from "/src/components/Chip/MarkdownChipRow"; - -# ckERC20 FAQ - - - -The following questions and answers are from the POV developer who wants to know things such as "how does a canister send ckERC20?" or how to write code for smart contracts to hold, send, or receive, please see the other FAQs. - -For questions from the POV of a user who wishes to know how to hold, send, receive these tokens, please see the user FAQs. - -### What is ckERC20? - -[Learn about ckERC20 tokens](/docs/current/developer-docs/multi-chain/chain-key-tokens/ckerc20/overview#what-is-ckerc20). - -### How can you create a ckERC20 token? - -[Learn how to create a ckERC20 token](/docs/current/developer-docs/multi-chain/chain-key-tokens/ckerc20/creating-new-ckerc20). - -### How can you use ckERC20 in a dapp? - -[Learn how to use ckERC20 in a smart contract](/docs/current/developer-docs/multi-chain/chain-key-tokens/ckerc20/using-ckerc20-in-dapps). - -### How can you convert ERC-20 tokens to ckERC20 tokens? - -[Learn how to convert ERC-20 tokens to ckERC20 tokens](/docs/current/developer-docs/multi-chain/chain-key-tokens/ckerc20/making-transactions#converting-erc-20-tokens-to-ckerc20-tokens). - -### How can you convert ckERC20 tokens to ERC-20 tokens? - -[Learn how to convert ckERC20 tokens to ERC-20 tokens](/docs/current/developer-docs/multi-chain/chain-key-tokens/ckerc20/making-transactions#converting-ckerc20-tokens-to-erc-20-tokens). - -### What ckERC20 tokens are currently supported? - -To view all currently supported ckERC20 tokens, make the following canister call to the ckERC20 minter canister: - -``` -dfx canister --ic call sv3dd-oaaaa-aaaar-qacoa-cai get_minter_info -``` \ No newline at end of file diff --git a/docs/developer-docs/multi-chain/faq/cketh-faq.mdx b/docs/developer-docs/multi-chain/faq/cketh-faq.mdx deleted file mode 100644 index b9c80a125f..0000000000 --- a/docs/developer-docs/multi-chain/faq/cketh-faq.mdx +++ /dev/null @@ -1,207 +0,0 @@ ---- -keywords: [advanced, ethereum, faq, cketh] ---- - -import { MarkdownChipRow } from "/src/components/Chip/MarkdownChipRow"; - -# ckETH FAQ - - - -The following questions and answers are from the POV of a developer. - -For questions from the POV of a user who wishes to know how to hold, send, receive these tokens, please see the user FAQs. - -### How do I write a smart contract that uses ckETH? - -At high-level: - -1. ckETH complies with the [ICRC-1 ledger token standard](/docs/current/developer-docs/defi/overview#icrc-1-ledgers). - -2. You can write a smart contract that works with ckETH just like you would for any other `ICRC-1`-compliant token. - -3. You can find all the ICRC-1 ledger endpoints [here](https://github.com/dfinity/ICRC-1/tree/main/standards/ICRC-1). - -4. Requests for balances and transfers must be sent to the ckETH ledger, which has the canister ID `ss2fx-dyaaa-aaaar-qacoq-cai`. - -For detailed information and potential code examples, check out out the [ICP documentation](https://internetcomputer.org/docs), the [DFINITY forum](https://forum.dfinity.org), and the [ckETH minter documentation](https://github.com/dfinity/ic/blob/master/rs/ethereum/ckETH/minter/README.adoc). - -### What is the best place to start to write contracts that handle ckETH? - -* [High level technical summary](https://forum.dfinity.org/t/cketh-a-canister-issued-ether-twin-token-on-the-ic/22819) - -## Examples of using the dfx CLI to: - -* [Deposit: ETH to ckETH](https://github.com/dfinity/ic/blob/master/rs/ethereum/cketh/docs/cketh.adoc#deposit-eth-to-cketh) - -* [Withdrawal: ckETH to ETH](https://github.com/dfinity/ic/blob/master/rs/ethereum/cketh/docs/cketh.adoc#withdrawal-cketh-to-eth) - -### What is the purpose of ckETH? What specific problem does ckETH aim to solve within the ETH ecosystem? - -ckETH, or chain-key Ether, is an Internet Computer (ICP)-native token that represents Ether (ETH), the native token of Ethereum. It serves as a digital twin of ETH on the Internet Computer blockchain. The purpose of ckETH is to address some of the challenges associated with using Ethereum, particularly in terms of usability and transaction costs. - -One of the main issues it addresses is the high transaction fees (or "gas fees") on the Ethereum network. By allowing Ethereum holders to interact with ckETH on the Internet Computer, which has significantly lower gas fees, users can enjoy fast and cheap transactions. They can then convert back to Ethereum whenever they want to transact on the Ethereum network. - -Another problem that ckETH aims to solve is the complexity and friction involved in using blockchain systems, particularly for mainstream users who are not familiar with the intricacies of tokens and wallets. The process of acquiring and using ckETH is designed to be straightforward and user-friendly, removing many of the barriers that can deter people from engaging with blockchain technology. - -Furthermore, ckETH enables direct interaction between ICP canister smart contracts and Ethereum, bypassing potential attack vectors by directly calling Ethereum RPCs through HTTPS outcalls. - -In summary, ckETH aims to enhance the usability of the Ethereum ecosystem by providing a more accessible, cost-effective, and secure way for users to engage with blockchain technology. - -### How does ckETH relate to ETH? How is ckETH different from a regular ETH transaction? Can I use ckETH just like I would use ETH? - -The main difference between a ckETH transaction and a regular ETH transaction lies in the transaction fees and the blockchain they operate on. Regular ETH transactions occur on the Ethereum network and are subject to Ethereum's gas fees, which can be quite high. On the other hand, ckETH transactions occur on the Internet Computer blockchain, which has significantly lower transaction fees. - -Yes, you can use ckETH just like you would use ETH, but within the Internet Computer ecosystem. You can deposit your ETH to a specific function in the ckETH helper contract on Ethereum, which then triggers the ICP ckETH canister smart contract to mint the same amount of ckETH to the specified ICP principal. This ckETH can then be used natively on the Internet Computer, and can be converted back to ETH at any time. - -However, it's important to note that while ckETH can be used in a similar manner to ETH, the platforms and services that accept ckETH might be different from those that accept ETH, as they are operating on different blockchains. - -### What are the benefits of using ckETH over traditional Ethereum transactions? - -The benefits of using ckETH over traditional Ethereum transactions primarily revolve around transaction speed, cost, and interoperability with the ICP ecosystem. - -1. **Lower transaction fees**: One of the main advantages of using ckETH is the significantly lower transaction fees compared to Ethereum. Ethereum transactions can sometimes be expensive, especially during periods of high network congestion. On the other hand, ckETH transactions occur on the Internet Computer blockchain, which has significantly lower transaction fees. - -2. **Faster transaction speed**: The ICP blockchain has a faster transaction speed compared to the Ethereum network. This means that transactions using ckETH can be processed more quickly, providing a smoother and more efficient user experience. - -3. **Interoperability**: ckETH allows for seamless interaction between the Ethereum and ICP ecosystems. This interoperability can potentially unlock new use cases and applications, such as decentralized finance (DeFi) platforms that span multiple blockchains. - -4. **Usability**: The process of acquiring and using ckETH is designed to be straightforward and user-friendly, removing many of the barriers that can deter people from engaging with blockchain technology. - -However, it's important to note that while ckETH provides these benefits, it's not a direct replacement for ETH. Each has its own unique features and use cases, and the choice between them will depend on your specific needs and circumstances. - -### Why should I choose ckETH for my application or service? - -Choosing ckETH for your application or service can provide several benefits: - -1. **Lower transaction fees**: Ethereum holders can interact with ckETH on the Internet Computer, which has significantly lower gas fees than on Ethereum. This allows for more [cost-effective transactions](https://medium.com/dfinity/a-data-driven-exploration-of-ckETH-the-digital-twin-of-ether-on-the-internet-computer-36b762be72e7#b197). - -2. **Manage an Ethereum wallet directly in an ICP canister**: ICP canister smart contracts can create and manage an Ethereum wallet address using threshold ECDSA. This provides a seamless way to manage [Ethereum wallets](https://medium.com/dfinity/a-data-driven-exploration-of-ckETH-the-digital-twin-of-ether-on-the-internet-computer-36b762be72e7#b197). - -3. **Seamless conversion**: ckETH allows you to enjoy the benefits of fast and cheap transactions and higher security on the Internet Computer, while still being able to seamlessly [convert back to your ETH anytime](https://medium.com/dfinity/a-data-driven-exploration-of-ckETH-the-digital-twin-of-ether-on-the-internet-computer-36b762be72e7#b197). - -4. **Multi-chain environment**: ICP enables a multi-chain environment where centralized bridges are obsolete and smart contracts can seamlessly communicate across blockchains. This provides increased asset liquidity, expanded market access, improved scalability and throughput, and access to [ICP’s unique capabilities](https://internetcomputer.org/ethereum-integration). - -5. **Gasless token swaps**: Using ckETH, users can swap tokens for a few cents with [0 gas fees](https://internetcomputer.org/ethereum-integration). - -6. **Web2 integration**: Connect smart contracts to the world outside blockchain. Fetch real-time price data and more from Web2. - -In summary, ckETH provides a secure, cost-effective, and efficient way to interact with the Ethereum blockchain, making it a great choice for your application or service. - -### What advantages does ckETH offer in terms of speed, fees, and security? - -ckETH offers several advantages in terms of speed, fees, and security: - -1. **Speed:** ckETH transactions on ICP have significantly lower latency compared to Ethereum. They can be transferred with 1-2 seconds finality, making them almost instant . - -2. **Fees:** Ethereum holders can interact with ckETH on ICP, which has significantly lower fees than on Ethereum. Users can swap tokens for a few cents with 0 gas fees . - -3. **Security:** ckETH bypasses attack vectors by directly calling Ethereum RPCs through HTTPS outcalls, a feature that enables ICP canister smart contracts to call API requests directly. This minimizes the risk of data leaks, hacks, and breaches. - -### How can I integrate ckETH into my existing applications or platforms? - -To integrate ckETH into your existing applications or platforms, you can follow these steps: - -1. **Obtain an ICP principal or wallet address.** -2. **Deposit your ETH**: Ethereum holders can deposit Ether to the *deposit* function in the ckETH helper contract on Ethereum and specify their ICP principal or wallet address where they want their minted ckETH to appear. -3. **Mint ckETH**: The ICP ckETH canister smart contract will then mint the same amount of ckETH to the indicated ICP principal or wallet address. -4. **Use ckETH**: The ICP principal or wallet address can now use ckETH natively on the Internet Computer. -5. **Convert back to ETH any time**: When the ICP principal wants to convert ckETH back to ETH, they can request the ckETH canister smart contract with the ETH amount and Ethereum address to which they want to send the ETH. - -Please note that the ckETH integration is part of a larger Ethereum integration on ICP. [Learn more about the Ethereum integration on ICP](https://internetcomputer.org/ethereum-integration). - -Also, remember that the Internet Computer makes it possible to build almost any online service fully onchain, in a full stack decentralization model. This is because canister smart contracts can hold up to 400GiB of memory each, and run in parallel with great efficiency. Moreover, they can directly serve interactive web-based user experiences to users by processing HTTP requests, thanks to ICP’s reverse-gas model (canister smart contracts pay for their own execution using “cycles” that they have been charged with). Now they can also be trustlessly combined with DeFi and other functionality [Ethereum hosts in a World Computer paradigm](https://internetcomputer.org/chainfusion). - -### What are the technical requirements for developers to work with ckETH? - -[View the ckETH documentation](/docs/current/developer-docs/multi-chain/chain-key-tokens/cketh/overview#cketh-production-application-examples) - -### How does ckETH ensure the security of the funds it handles? - -ckETH ensures the security of the funds it handles in several ways: - -1. **No need for bridges**: ckETH uses a feature called HTTPS outcalls that enables ICP canister smart contracts to call API requests directly. This bypasses attack vectors by directly calling Ethereum RPCs, eliminating the need for potentially insecure bridges. - -2. **Managing an Ethereum wallet directly in an ICP canister**: ICP canister smart contracts can create and manage an Ethereum wallet address using threshold ECDSA. This means that the ICP ckETH minter canister smart contract can generate an address that holds ETH and signs transactions, adding an extra layer of security. - -3. **NNS DAO governance**: The development of ckETH includes measures to guarantee long-term maintenance and provide more security to ETH through NNS DAO governance. This ensures that the management and development of ckETH are in the hands of a decentralized community, reducing the risk of malicious actions by a single party. - -4. **Chain-key signatures**: ICP has the ability to sign native transactions on other blockchains without using risky bridges. This feature is used in the operation of ckETH, further enhancing its security. - -Remember, while these features enhance the security of ckETH, it's always important to exercise caution and good security practices when dealing with cryptocurrencies. - -### Can I trust that my funds are safe when using ckETH? - -Yes, you can trust that your funds are safe when using ckETH. ICP offers several features that enhance the security and trustworthiness of its canister smart contracts, such as ckETH. - -However, as with any blockchain technology, it's important to do your own research and understand the risks involved. - -### Can I build smart contracts that interact with ckETH? What kind of functionalities can these smart contracts provide? - -Yes, you can build smart contracts that interact with ckETH on the Internet Computer. These smart contracts, also known as canisters, can provide a wide range of functionalities. Here are some of the key capabilities: - -1. **Minting ckETH**: When you deposit your ETH to the ckETH helper contract on Ethereum, the ICP ckETH canister smart contract will mint the same amount of ckETH to your specified ICP principal or wallet address. - -2. **Using ckETH**: Once the ckETH is minted, it can be used natively on the Internet Computer. This means that your smart contracts can interact with ckETH just like they would with any other token on the Internet Computer. - -3. **Converting ckETH back to ETH**: If you want to convert your ckETH back to ETH, you can do so by requesting the ckETH canister smart contract with the ETH amount and Ethereum address to which you want to send the ETH. - -4. **Interacting with Ethereum smart contracts**: ICP canisters can interact with Ethereum smart contracts. This is made possible by the Internet Computer's ability to make HTTPS outcalls to Ethereum APIs to securely query and send transactions to the Ethereum network. - -5. **Managing an Ethereum wallet**: ICP canister smart contracts can create and manage an Ethereum wallet address using threshold ECDSA. This means that your smart contracts can hold ETH and sign transactions. - -6. **Processing and storing large volumes of data**: Smart contracts can process and store large volumes of data at a relatively stable cost that is a tiny fraction of that on a traditional blockchain. - -7. **Serving web experiences directly to end users**: Smart contracts on ICP can serve web experiences directly to end users, providing end-to-end blockchain security. - -8. **Creating and managing other Ethereum asset twins**: In addition to ckETH, you can also create and manage "twins" of other Ethereum [ERC-20 tokens](/docs/current/developer-docs/multi-chain/chain-key-tokens/ckerc20/overview). - -Please note that the ICP ETH integration is still in development, and more functionalities will be added in the future. - -### What are the transaction fees associated with ckETH? - -The transaction fees are 0.000002 ckETH. - -### How quickly can transactions be finalized? - -ICP is designed to finalize transactions very quickly. Specifically, it can finalize transactions that update canister smart contract state in 1–2 seconds. This is a significant improvement over traditional blockchains like Bitcoin and Ethereum, which can take much longer to finalize transactions. - -In addition, ICP splits canister function execution into two types: "update calls" and "query calls". Update calls take 1–2 seconds to finalize their execution. On the other hand, query calls work differently because any changes they make to state are discarded after they run. This allows query calls to execute in milliseconds. - -ICP is capable of processing up to over 30 thousand transactions per second (as of [November 2023](https://wiki.internetcomputer.org/wiki/Internet_Computer_performance)), executed with an average 1-second finality on dapp subnets and a 2-second finality on the Network Nervous System (NNS) subnet. - -### Who controls the development and governance of ckETH? - -Like many ICP canisters, the development and governance of ckETH is managed by the ICP ecosystem. - -Software updates to the ckETH canisters are voted on by the NNS DAO. - -### Can you provide examples of current applications that utilize ckETH? - -[View sample projects that use ckETH](/docs/current/developer-docs/multi-chain/chain-key-tokens/cketh/overview#cketh-production-application-examples) - -### What is the current state of ckETH project? - -ckETH is live on the Internet Computer mainnet. It has been added to the ICP dashboard. However, with the current ckETH integration, you cannot withdraw to ETH directly from the ICRC-1 wallet. - -The integration is being carried out in phases. Phase 0, which enables chain-key signing and HTTPS outcalls, is already complete. Phase 1 is being built to allow ETH API calls by accessing Web-2 based API providers through HTTPS outcalls. This phase also includes designing and building ckETH and ckERC-20 tokens. The final phase, Phase 2, will revolve around native ETH integration. - -For more information on the current state of the ckETH project, you can join the forum discussion or check out the Ethereum integration page on the ICP website. - -## Additional reading - -- [A data driven exploration of ckETH](https://medium.com/dfinity/a-data-driven-exploration-of-ckETH-the-digital-twin-of-ether-on-the-internet-computer-36b762be72e7#e978). -- [Developer Journey: 5.2: ICP ETH tutorial](/docs/current/tutorials/developer-journey/level-5/5.2-ICP-ETH-tutorial#overview). -- [Dfinity - Global R&D: May 2023 Edition - ETH Integration: Status update](https://medium.com/dfinity/global-r-d-may-2023-edition-d96859039ca6#a28d). -- [Ethereum + ICP > Multi-chain DeFi](https://internetcomputer.org/ethereum-integration) -- [Extend Bitcoin, Ethereum and other blockchains](https://wiki.internetcomputer.org/wiki/Extend_Bitcoin,_Ethereum_and_other_blockchains#firstHeading) -- [How does ckETH work?](https://medium.com/dfinity/a-data-driven-exploration-of-ckETH-the-digital-twin-of-ether-on-the-internet-computer-36b762be72e7#e978) -- [How to Acquire ckETH](https://medium.com/dfinity/how-to-acquire-ckETH-02d863c835fc#c324) -- [ICP Ethereum integration explained](https://medium.com/dfinity/internet-computer-ethereum-integration-explained-6967456e35f9#58f6). -- [Internet Computer Blog - ckETH: now live!](https://internetcomputer.org/blog/2023/12/06/news-and-updates/update#ckETH-now-live). -- [Internet Computer for Ethereum Developers](https://wiki.internetcomputer.org/wiki/The_Internet_Computer_for_Ethereum_Developers#A_very_brief_introduction_to_the_Internet_Computer) -- [Internet Computer Wiki - Decentralization](https://wiki.internetcomputer.org/wiki/Decentralization#firstHeading) -- [Learn more about how ckETH works](https://forum.dfinity.org/t/ckETH-a-canister-issued-ether-twin-token-on-the-ic/22819). -- [Multi-chain DeFi](https://internetcomputer.org/defi) -- [The Purposes of the Internet Computer](https://medium.com/dfinity/announcing-internet-computer-mainnet-and-a-20-year-roadmap-790e56cbe04a#0289) -- [Trustless multi-chain on ICP](https://internetcomputer.org/chainfusion) diff --git a/docs/developer-docs/multi-chain/faq/signatures-faq.mdx b/docs/developer-docs/multi-chain/faq/signatures-faq.mdx deleted file mode 100644 index 15d1dace2f..0000000000 --- a/docs/developer-docs/multi-chain/faq/signatures-faq.mdx +++ /dev/null @@ -1,55 +0,0 @@ ---- -keywords: [advanced, faq, signatures] ---- - -import { MarkdownChipRow } from "/src/components/Chip/MarkdownChipRow"; - -# Signatures FAQ - - - -## Does ICP support ECDSA signatures? - -Yes, the Internet Computer (ICP) does support ECDSA signatures. It implements a novel threshold ECDSA protocol as part of its chain-key signatures toolbox. In this protocol, the private ECDSA key exists only as secret shares held by designated parties, namely the replicas of a threshold-ECDSA-enabled subnet on ICP. Signatures are computed using those secret shares without the private key ever being reconstructed. Each replica of such subnet holds a key share that provides no information on its own. At least one third of the replicas are required to generate a threshold signature using their respective key shares. - -The threshold ECDSA protocol on ICP also includes protocols for secure distributed key generation and periodic key resharing, which are crucial parts of the protocol. This makes chain-key ECDSA signatures much more powerful than any off-the-shelf threshold ECDSA protocol. - -Each canister on any subnet of the Internet Computer has control over a unique ECDSA public key and can request signatures for this public key to be computed. A signature is only issued to the eligible canister, i.e., the legitimate holder of this ECDSA key. Each canister can obtain signatures only for its own ECDSA keys. Note that canisters do not hold any private ECDSA keys or key shares themselves. - -For more details, you can refer to the [ICP documentation on Threshold ECDSA](/docs/current/developer-docs/smart-contracts/encryption/t-ecdsa#overview). - -## Does ICP support Schnorr signatures? - -ICP supports Schnorr signatures as part of the [Deuterium milestone](https://internetcomputer.org/roadmap#Chain%20Fusion-Deuterium). This is particularly important for the processing of certain types of assets and transactions. For instance, inscribing Ordinals and creating and processing BRC20 assets involves Schnorr cryptography, which ICP supports. This also enables web-based smart contract wallets such as Oisy to self-host BRC20, Ethereum, and native ICP assets. - -## Does ICP support EdDSA signatures? - -ICP will support EdDSA signatures as part of the [Helium milestone](https://internetcomputer.org/roadmap#Chain%20Fusion-Helium). - -## Does ICP support BLS signatures? - -Yes, the Internet Computer Protocol (ICP) does support BLS (Boneh-Lynn-Shacham) signatures. As mentioned in the extracts, the threshold signature scheme used to implement chain-key cryptography in ICP is based on BLS signatures. However, it's important to note that while BLS signatures have distinct advantages, they are not compatible with other blockchains. To work with other blockchains, ICP uses threshold signatures that are compatible with the digital signature schemes of those other blockchains, such as ECDSA for Bitcoin and Ethereum. - -For more information, you can refer to the [ICP documentation](https://internetcomputer.org/docs) or the [ICP wiki](https://wiki.internetcomputer.org/wiki). - -## Does ICP support multi-signature (multi-sig)? - -Not currently in the protocol, but there are projects like: [https://github.com/ICPsig/icpsig](https://github.com/ICPsig/icpsig) working on it. - -## Does ICP support hash time locked contracts (HTLCs)? - -Not currently. - -For more detailed information on ICP's cryptographic mechanisms, you may want to refer to the [ICP documentation](https://internetcomputer.org/docs) or the [ICP wiki](https://wiki.internetcomputer.org/wiki). - -## Does ICP support zero-knowledge succinct non-interactive arguments of knowledge (zk-SNARKs)? - -Not currently. - -For more detailed information on ICP's cryptographic mechanisms, you may want to refer to the [ICP documentation](https://internetcomputer.org/docs) or the [ICP wiki](https://wiki.internetcomputer.org/wiki). - -## Does ICP support proof of logical obliviousness (PLONK)? - -Not currently. - -For more detailed information on ICP's cryptographic mechanisms, you may want to refer to the [ICP documentation](https://internetcomputer.org/docs) or the [ICP wiki](https://wiki.internetcomputer.org/wiki). diff --git a/docs/developer-docs/multi-chain/faq/user-faq.mdx b/docs/developer-docs/multi-chain/faq/user-faq.mdx deleted file mode 100644 index 4f1ecae34f..0000000000 --- a/docs/developer-docs/multi-chain/faq/user-faq.mdx +++ /dev/null @@ -1,174 +0,0 @@ ---- -keywords: [advanced, faq] ---- - -import { MarkdownChipRow } from "/src/components/Chip/MarkdownChipRow"; - -# User facing FAQ - - - -The following questions and answers are from the POV of a user using consumer applications like the NNS frontend dapp or others. They are meant to help consumers who want to hold, send, or receive tokens. - -For questions from the POV of a developer who wants to know things such as "how does a canister send ckBTC?" or how to write code for smart contracts to hold, send, or receive tokens, please see the other FAQs. - -## General multi-chain questions - -### What is the purpose of the Internet Computer being having multi-chain smart contracts that can call into other blockchains? - -1. ICP canister smart contracts have a lot of functionality that other blockchain smart contracts do not. Developers of other blockchains can use ICP smart contract functionality for custody on other chains. - -2. ICP canister smart contracts are able to call into Bitcoin, giving Bitcoin a powerful smart contract layer, since Bitcoin (unlike Ethereum) does not have native smart contracts. - -3. ICP canister smart contract developers can create software systems that are interoperable with other blockchain smart contracts. - -## ckBTC user questions - -### What is ckBTC? - -Chain-key Bitcoin (ckBTC) is a token on the Internet Computer that is backed 1:1 by bitcoin (BTC). This means that 1 ckBTC can always be redeemed for 1 BTC and vice versa. Unlike other tokens pegged to bitcoin, the ckBTC token does not rely on a third-party bridge for the conversion between BTC and ckBTC, making it a substantially more secure alternative to “wrapped” tokens. - -One of the main advantages of ckBTC over regular bitcoin is its speed and cost of transfers. A transfer of ckBTC is finalized within a few seconds, which is significantly faster compared to transfers on the Bitcoin blockchain where even one confirmation can take minutes (and typically people wait for 5-7 confirmations). Additionally, the cost of a ckBTC transfer is only 0.0000001 ckBTC, which is approximately two orders of magnitude lower than the Bitcoin miner fees. - -In terms of usage, ckBTC can be used in applications on the Internet Computer. For example, there is a point of sale app that allows users to accept ckBTC payments. This is made possible because the Internet Computer integrates directly with the Bitcoin network, allowing canisters (akin to smart contracts) on the Internet Computer to receive, hold, and send Bitcoin, all directly with transactions on the Bitcoin network. - -### How do I convert ckBTC to BTC and vice versa? - -[Learn how to convert ckBTC to BTC](/docs/current/developer-docs/multi-chain/chain-key-tokens/ckbtc/making-transactions). - -### How do I transfer ckBTC from one account to another? - -[Learn how to transfer ckBTC from one account to another](/docs/current/developer-docs/multi-chain/chain-key-tokens/ckbtc/making-transactions#transferring-ckbtc-to-another-accounts). - -### How do I receive ckBTC? - -[Learn how to receive ckBTC](/docs/current/developer-docs/multi-chain/chain-key-tokens/ckbtc/making-transactions). - -### Can I convert ICP to ckBTC? - -ICP and ckBTC are two separate tokens so there is no protocol way to convert one to another. Typically people who want to exchange one for the other use exchanges. - -### Can I convert ICP to BTC? - -ICP and BTC are two separate tokens so there is no protocol way to convert one to another. Typically people who want to exchange one for the other use exchanges. - -### What are the average ckBTC transfer fees? - -The transaction fees for ckBTC on the Internet Computer (ICP) are designed to be minimal. It is currently configured to at 0.0000001 ckBTC, which is equivalent to less than a cent or 10 satoshis. - -When calling `retrieve_btc`, the formula for the ckBTC minter fee is determined as follows: -``` -246*in + 7*out + 52 satoshi -``` -This formula is used to determine the ckBTC minter’s fee in satoshi. Since every transaction has at least one input and one output, the fee is at least 305 satoshi. - -There is also a know your transaction (KYT) fee, currently set at 2000 satoshi, when converting BTC to ckBTC and vice versa. - -### How can I view the entire history of ckBTC transactions? - -You can view the transactions for ckBTC or BTC on the Internet Computer through the [Internet Computer Dashboard](https://dashboard.internetcomputer.org/bitcoin/transactions). - -## ckETH user questions - -### How do I convert ckETH to ETH and vice versa? - -[Learn how to convert ckETH to ETH](/docs/current/developer-docs/multi-chain/chain-key-tokens/cketh/making-transactions). - -### Can I convert ICP to ckETH? - -ICP and ckETH are two separate tokens so there is no protocol way to convert one to another. Typically people who want to exchange one for the other use exchanges. - -## General multi-chain questions - -### Is there a user interface for managing my multi-chain assets on the Internet Computer? - -Yes, one example is the [NNS frontend dapp](https://nns.ic0.app/). Another example is [Oisy Wallet](https://oisy.com/). - -### How does ICP ensure the security and privacy of my cross-chain transactions? - -Internet Computer (ICP) ensures the security and privacy of your cross-chain transactions through several mechanisms: - -1. **Bitcoin integration**: ICP's native Bitcoin integration allows canisters (advanced smart contracts) to interact with the Bitcoin network at the protocol level. This means they can directly receive, hold, and send BTC on the Bitcoin mainnet without using intermediaries and third-party blockchain bridges, which often have security issues. Canisters can read from and write to the Bitcoin ledger. - -2. **Ethereum integration**: ICP aims for a native integration with the Ethereum network by running Ethereum nodes co-located with ICP nodes. The current mechanism to interact with smart contracts on Ethereum is to use the [EVM RPM canister](https://github.com/internet-computer-protocol/evm-rpc-canister/), which uses HTTPS outcalls to communicate with JSON-RPC services such as CloudFlare, Alchemy, Ankr, or BlockPI. Since it is not bound to any single service provider, it can read state information from and transmit transactions to Ethereum in a secure and reliable manner. - -3. **Chain-key cryptography**: ICP uses chain-key cryptography to sign native transactions on other blockchains. This set of cryptographic protocols allows ICP to securely communicate across chains. - -4. **Platform privacy**: The Internet Computer runs a decentralized network, where data and computation are replicated across nodes in data centers located around the world. Communication with the Internet Computer relies on a set of boundary nodes, which can see the IP address of the sending user, as well as which canister the user is sending it to and the payload. All communication to the Internet Computer and within it is encrypted and the state of canisters is private by default. - -### Can I track the status of my multi-chain transactions on the Internet Computer dashboard? - -The dashboard currently shows conversions between: - -- ckBTC and Bitcoin on the [ckBTC transaction page](https://dashboard.internetcomputer.org/bitcoin/transactions) - -- ckETH and Ether on the [ckETH transaction page](https://dashboard.internetcomputer.org/ethereum/transactions) - -- Chain-key ERC-20 tokens and their ERC-20 counterpart, such as ckUSDC and USDC on their [respective dashboard](https://dashboard.internetcomputer.org/ethereum/xevnm-gaaaa-aaaar-qafnq-cai). - -### What are the steps involved in setting up a multi-chain wallet on the Internet Computer? - -The [NNS frontend dapp](https://nns.ic0.app/) serves as a multi-chain wallet enabling users to hold many types of tokens such as ICP, ckBTC, ckETH, etc. - -### How does ICP handle the conversion of tokens between different chains, such as converting ICP to ckBTC? - -The Internet Computer (ICP) has a rich ecosystem of DeFi apps and services such as AMM's and Decentralized exchanges which enable swapping between tokens, such as ICP or a chain-key token such as ckBTC or ckETH. Tools like [ICPSwap](https://app.icpswap.com/swap), [Sonic](https://www.sonic.ooo/), and [ICLight](https://iclight.io/) can be used for this purpose. On ICPSwap, for instance, you can connect to the dapp with several different wallet types, such as Internet Identity, NFID, Bitfinity and more. Then, you can select the type of token you'd like to swap for another, such as ICP, and enter the value you'd like to swap. Finally, select the token you'd like to receive in return for your ICP. - -In the future, when the Internet Computer blockchain integrates with additional blockchains, more chain-key tokens will become available on ICP. - -### Is there a guide or tutorial on how to use multi-chain features on the Internet Computer for beginners? - -Yes, there are several resources available for beginners who want to use the multi-chain features on the Internet Computer. - -1. The [ETH starter tutorial](/docs/current/tutorials/developer-journey/level-5/5.2-ICP-ETH-tutorial) is a great place to start. It provides a step-by-step guide on how to interact with Ethereum on the Internet Computer. - -2. You can also check out the [Code ckETH](https://github.com/dfinity/ic/tree/master/rs/ethereum/cketh) and [Code ckBTC](/docs/current/developer-docs/multi-chain/chain-key-tokens/ckbtc/overview) for code samples on how to use these features. - -3. The [DeFi sample code](https://internetcomputer.org/samples?selectedDomains=Asynchronous+DeFi) provides examples of decentralized finance applications that utilize the multi-chain features of the Internet Computer. - -4. For more advanced topics, you can explore the [Multi-chain DeFi](https://internetcomputer.org/defi) page which discusses how the Internet Computer can be used for decentralized finance applications. - -5. The [developer resources](https://internetcomputer.org/developers) page also provides a wealth of information, including documentation, sample code, tooling, and support. - -Remember, the Internet Computer allows you to create smart contracts that directly interact with other blockchains without the need for trusted centralized bridges. This is made possible using chain-key cryptography. You can learn more about this on the [wiki](https://wiki.internetcomputer.org/wiki/Trustless_multi-chain_web3_using_the_IC#firstHeading). - -### How does ICP handle the integration of smart contracts across different chains? - -Internet Computer Protocol (ICP) handles the integration of smart contracts across different chains through a process known as cross-chain interoperability. This is achieved through advanced cryptography, specifically threshold ECDSA and chain-key cryptography. - -For instance, ICP can natively create signed transactions on other blockchains like Ethereum and Bitcoin, allowing decentralized applications (dapps) deployed on ICP to interact directly with other networks and their smart contracts, tokens, and other digital assets. - -ICP has integrated with Bitcoin at the protocol level. This integration coupled with the chain-key threshold ECDSA feature allows a canister (a computational unit on the ICP) to create a Bitcoin address, then send or receive bitcoin directly as if they were a regular Bitcoin user. - -ICP is also working on an integration with Ethereum that will allow Ethereum smart contracts and digital assets like ERC-20 tokens to be used in ICP canisters. This integration is being worked on. - -In the future, ICP aims to become fully compatible with the Ethereum Virtual Machine (EVM), enabling developers to deploy Ethereum smart contracts directly on the ICP network. - -### Can I use my existing hardware wallets or mobile apps to manage my multi-chain assets on the Internet Computer? - -Yes! Please see documentation here on using Ledger Nanos and other hardware wallets: [hardware wallets](https://support.dfinity.org/hc/en-us/articles/8760495850900-How-do-I-use-my-Ledger-Nano-with-the-Internet-Computer). - - -## Additional reading - -- [Chain-key bitcoin overview](https://wiki.internetcomputer.org/wiki/Chain-key_Bitcoin#firstHeading) -- [Chain-key bitcoin: A decentralized bitcoin twin](https://medium.com/dfinity/chain-key-bitcoin-a-decentralized-bitcoin-twin-ceb8f4ddf95e#99f9) -- [Chain-key tokens](https://internetcomputer.org/how-it-works/chain-key-tokens) -- [cketh](https://github.com/dfinity/ic/blob/master/rs/ethereum/cketh/docs/cketh.adoc) -- [Cross chain interoperability](/docs/current/tutorials/hackathon-prep-course/what-is-icp#cross-chain-interoperability) -- [Eliminating smart contract bugs with TLA+](https://medium.com/dfinity/eliminating-smart-contract-bugs-with-tla-e986aeb6da24#3a8b) -- [Exploring data on ckETH, the digital twin of ETH on ICP](https://medium.com/dfinity/a-data-driven-exploration-of-cketh-the-digital-twin-of-ether-on-the-internet-computer-36b762be72e7#e978) -- [Full protocol integration](https://internetcomputer.org/ethereum-integration) -- [How ckBTC solves the dilemma of blockchain bridges](https://medium.com/dfinity/how-ckbtc-solves-the-dilemma-of-blockchain-bridges-ee8e0b72ee59#f847) -- [How do I convert BTC to ckBTC in the NNS dapp?](https://support.dfinity.org/hc/en-us/articles/20708056282132-What-is-ckBTC#h_01HE64A4QKANB6JX8VERRP5Y80) -- [How ICP’s Bitcoin integration secures private keys part 1](https://medium.com/dfinity/how-icps-bitcoin-integration-secures-private-keys-c2af14597846#6a5c) -- [How ICP’s Bitcoin integration secures private keys part 2](https://medium.com/dfinity/how-icps-bitcoin-integration-secures-private-keys-c2af14597846#6a5c) -- [How to acquire ckETH](https://medium.com/dfinity/how-to-acquire-cketh-02d863c835fc#e10f) -- [https://internetcomputer.org/blog/2023/12/06/news-and-updates/update#cketh-now-live](https://internetcomputer.org/blog/2023/12/06/news-and-updates/update#cketh-now-live). -- [Internet Computer Ethereum integration](https://internetcomputer.org/ethereum-integration) -- [Securing cross-chain communication from Ethereum to the Internet Computer with an onchain Light Client](https://medium.com/dfinity/securing-cross-chain-communication-from-ethereum-to-the-internet-computer-with-an-on-chain-light-fedfb4fb24b4#1329) -- [SourThe Future: Chain-key ERC-20 tokens](https://internetcomputer.org/how-it-works/chain-key-tokens#the-future-chain-key-erc-20-tokens) -- [Swapping between tokens](/docs/current/tutorials/hackathon-prep-course/integrating-with-tokens#swapping-between-tokens) -- [Team spotlight - Financial integration](https://internetcomputer.org/blog/news-and-updates/team-spotlight-fi) -- [The Internet Computer blockchain privacy advantages](https://medium.com/dfinity/the-internet-computer-blockchains-privacy-advantages-73340c6c42db#6ec2) -- [Withdrawing ckETH](https://github.com/timohanke/ic/blob/d34903fc2c41e2cff5df86248628f5d0b4fd7168/rs/ethereum/cketh/minter/README.adoc#withdrawal-cketh-to-eth) diff --git a/plugins/utils/redirects.js b/plugins/utils/redirects.js index bdd437386d..2747965d71 100644 --- a/plugins/utils/redirects.js +++ b/plugins/utils/redirects.js @@ -406,11 +406,11 @@ const redirects = ` /docs/current/developer-docs/daos/nns/proposal-requirements /docs/current/developer-docs/daos/nns/concepts/proposal-requirements /docs/current/tokenomics/index /docs/current/developer-docs/daos/overview /docs/current/tokenomics/ /docs/current/developer-docs/daos/overview - /docs/current/developer-docs/integrations/multi-chain/user-faq /docs/current/developer-docs/multi-chain/faq/user-faq - /docs/current/developer-docs/integrations/multi-chain/ckbtc-faq /docs/current/developer-docs/multi-chain/faq/ckbtc-faq - /docs/current/developer-docs/integrations/multi-chain/cketh-faq /docs/current/developer-docs/multi-chain/faq/cketh-faq - /docs/current/developer-docs/integrations/multi-chain/ckerc20-faq /docs/current/developer-docs/multi-chain/faq/ckerc20-faq - /docs/current/developer-docs/integrations/multi-chain/signatures-faq /docs/current/developer-docs/multi-chain/faq/signatures-faq + /docs/current/developer-docs/integrations/multi-chain/user-faq /docs/current/developer-docs/multi-chain/overview + /docs/current/developer-docs/integrations/multi-chain/ckbtc-faq /docs/current/developer-docs/multi-chain/chain-key-tokens/ckbtc/overview + /docs/current/developer-docs/integrations/multi-chain/cketh-faq /docs/current/developer-docs/multi-chain/chain-key-tokens/cketh/overview + /docs/current/developer-docs/integrations/multi-chain/ckerc20-faq /docs/current/developer-docs/multi-chain/chain-key-tokens/ckerc20/overview + /docs/current/developer-docs/integrations/multi-chain/signatures-faq /docs/current/references/t-sigs-how-it-works /docs/current/developer-docs/integrations/bitcoin/ /docs/current/developer-docs/multi-chain/bitcoin/overview /docs/current/developer-docs/integrations/bitcoin/index /docs/current/developer-docs/multi-chain/bitcoin/overview /docs/current/developer-docs/integrations/bitcoin/ckbtc /docs/current/developer-docs/multi-chain/chain-key-tokens/ckbtc/overview @@ -619,6 +619,11 @@ const redirects = ` /docs/current/concepts/subnet-types /docs/current/references/subnets/subnet-types /docs/current/concepts/glossary /docs/current/references/glossary /docs/current/concepts/trust-in-canisters /docs/current/developer-docs/smart-contracts/overview/trust-in-canisters + /docs/current/developer-docs/multi-chain/faq/user-faq /docs/current/developer-docs/multi-chain/overview + /docs/current/developer-docs/multi-chain/faq/ckbtc-faq /docs/current/developer-docs/multi-chain/chain-key-tokens/ckbtc/overview + /docs/current/developer-docs/multi-chain/faq/cketh-faq /docs/current/developer-docs/multi-chain/chain-key-tokens/cketh/overview + /docs/current/developer-docs/multi-chain/faq/ckerc20-faq /docs/current/developer-docs/multi-chain/chain-key-tokens/ckerc20/overview + /docs/current/developer-docs/multi-chain/faq/signatures-faq /docs/current/references/t-sigs-how-it-works ` .split(/[\r\n]+/) .map((line) => line.trim().replace(/^#.*$/, "").trim()) diff --git a/sidebars.js b/sidebars.js index 18678f93da..51aa3e18f3 100644 --- a/sidebars.js +++ b/sidebars.js @@ -1476,17 +1476,6 @@ const sidebars = { "references/subnets/subnet-types", ], }, - { - type: "category", - label: "FAQs", - items: [ - "developer-docs/multi-chain/faq/user-faq", - "developer-docs/multi-chain/faq/ckbtc-faq", - "developer-docs/multi-chain/faq/cketh-faq", - "developer-docs/multi-chain/faq/ckerc20-faq", - "developer-docs/multi-chain/faq/signatures-faq", - ], - }, ], }, ],