Sending Ethereum Classic from one wallet to another usually takes less than a minute. The transaction appears in a block explorer, receives its first confirmation, and looks complete.<\/p>\n
However, when ETC is sent to a cryptocurrency exchange or an online exchange service, the situation may be very different. The platform may require 300, 500, or even several thousand confirmations before the coins are credited to the user\u2019s account.<\/p>\n
For someone who is used to faster deposits, this can be confusing. The transaction is already visible on the blockchain, so why is the exchange still showing it as pending?<\/p>\n
The reason is not a technical failure. In most cases, the exchange is simply waiting for additional security before treating the deposit as final.<\/p>\n
A transaction receives its first confirmation when a miner includes it in a block. Every new block added after that increases the confirmation count by one.<\/p>\n
For example:<\/p>\n
The transaction does not have to be processed again each time. It remains in the same block. The growing confirmation count only shows how deeply that block is buried under newer blocks.<\/p>\n
The deeper a transaction is in the blockchain, the more difficult and expensive it becomes to reverse.<\/p>\n
Ethereum Classic produces a new block approximately every 13 seconds. Under normal conditions, a properly funded transaction can therefore appear on the blockchain within several seconds.<\/p>\n
This is enough for a wallet to display the received ETC. It may not be enough for an exchange.<\/p>\n
The Ethereum Classic network does not impose a universal rule saying that every transaction must wait for 300 or 500 confirmations.<\/p>\n
The required number is chosen by the receiving service.<\/p>\n
A personal wallet may show incoming coins after the first confirmation. A small payment processor may wait for several confirmations. A cryptocurrency exchange holding large amounts of customer funds may require hundreds or thousands.<\/p>\n
Each platform creates its own deposit policy based on factors such as:<\/p>\n
This is why the same ETC transaction may be considered complete by one service while another service still treats it as pending.<\/p>\n
Ethereum Classic is a proof-of-work blockchain. Miners use computing power to create new blocks and protect the history of transactions.<\/p>\n
Like other proof-of-work networks, ETC can theoretically experience a chain reorganization. This happens when one version of the blockchain is replaced by another version containing more accumulated work.<\/p>\n
Small reorganizations can occur naturally when two miners produce blocks at nearly the same time. Usually, one branch quickly becomes longer, and the network continues using it.<\/p>\n
A much deeper reorganization is more serious. It can remove transactions that previously appeared to be confirmed.<\/p>\n
This matters especially to exchanges because they are attractive targets for double-spending attacks.<\/p>\n
Imagine that an attacker deposits ETC on an exchange and trades it for another cryptocurrency. The attacker then withdraws the purchased cryptocurrency. If the original ETC deposit is later removed through a malicious blockchain reorganization, the exchange loses the funds that were withdrawn.<\/p>\n
The attacker may keep the original ETC while also keeping the assets received from the exchange.<\/p>\n
Waiting for more confirmations makes such an attack increasingly difficult. To remove an older transaction, an attacker would need to rebuild a larger part of the blockchain and catch up with the honest miners.<\/p>\n
Ethereum Classic experienced several major 51% attacks and deep chain reorganizations in 2019 and 2020.<\/p>\n
During a 51% attack, an attacker gains enough mining power to build an alternative version of the blockchain faster than the rest of the network. This does not allow the attacker to take coins directly from arbitrary wallets or create ETC from nothing.<\/p>\n
However, it may allow recent transactions made by the attacker to be reversed.<\/p>\n
Cryptocurrency exchanges were among the parties most exposed to this risk. After the attacks, many platforms increased the number of confirmations required for ETC deposits.<\/p>\n
These confirmation limits remained high even after the immediate incidents had passed. From the exchange\u2019s point of view, a longer waiting period is cheaper than covering losses caused by a successful double spend.<\/p>\n
The result is an unusual situation: the ETC network itself may process a transaction quickly, while a centralized service waits much longer before making the funds available.<\/p>\n
With an average block time of approximately 13 seconds, the expected waiting time can be estimated quite easily.<\/p>\n
Three hundred confirmations take around 3,900 seconds, or about 65 minutes.<\/p>\n
Five hundred confirmations take around 6,500 seconds, or approximately 108 minutes.<\/p>\n
In practice, the waiting time may be somewhat shorter or longer. Blocks are not produced at perfectly regular intervals. The exchange may also need additional time to detect the deposit, update its internal database, perform security checks, and credit the account.<\/p>\n
As a result, a service requiring 300 to 500 confirmations may take roughly one to two hours to credit an ETC deposit.<\/p>\n
Platforms requiring several thousand confirmations may take many hours. An exceptionally high confirmation requirement can make the deposit process last most of a day.<\/p>\n
Users sometimes become concerned when a transaction is marked as successful in a block explorer but does not appear in their exchange balance.<\/p>\n
Usually, this simply means that the exchange has detected the deposit but has not yet reached its confirmation threshold.<\/p>\n
There are two separate stages:<\/p>\n
A block explorer shows the first stage. The exchange balance reflects the second.<\/p>\n
As long as the destination address is correct and the transaction appears successfully on the Ethereum Classic blockchain, the coins are normally not lost. They are waiting to be credited by the receiving platform.<\/p>\n
The user can monitor the confirmation count using an ETC block explorer and compare it with the number required by the exchange.<\/p>\n
A high confirmation requirement can make Ethereum Classic appear slow, but it is important to separate transaction speed from deposit policy.<\/p>\n
The network usually includes ETC transactions quickly. Waiting for hundreds of blocks is a security decision made by the exchange.<\/p>\n
The transaction is not stuck in the mempool during this period. It has already been mined. The exchange is simply waiting to become more confident that the blockchain history containing the deposit will not change.<\/p>\n
This distinction also explains why ETC can arrive quickly in a self-custodial wallet but take much longer to become available on a trading platform.<\/p>\n
A higher fee may help a transaction enter its first block sooner, especially when the network is busy. It does not reduce the number of confirmations required by the exchange.<\/p>\n
Once the transaction has been included in a block, the confirmation count increases only when new blocks are mined.<\/p>\n
If an exchange requires 500 confirmations, paying a larger fee will not turn that requirement into 50 confirmations. The user still has to wait for the remaining blocks.<\/p>\n
There is no universally correct confirmation number for every ETC deposit.<\/p>\n
One exchange may consider 300 confirmations sufficient. Another may require 500. A more conservative platform may demand several thousand or apply different rules to large deposits.<\/p>\n
Some services may also change their requirements without much notice. They can raise the limit after unusual network activity or lower it when they believe the security situation has improved.<\/p>\n
This means users should check the current deposit information on the receiving platform before sending ETC, especially when the funds are needed for urgent trading or conversion.<\/p>\n
A confirmation requirement shown in an old review, forum post, or tutorial may no longer be accurate.<\/p>\n
Before making a deposit, confirm that the platform supports the native Ethereum Classic network. ETC should not be confused with ETH or with a token using a different blockchain.<\/p>\n
It is also useful to check:<\/p>\n
For a large transfer, sending a small test amount first can help confirm that the address and network have been selected correctly.<\/p>\n
Ethereum Classic transactions are normally recorded on the blockchain within seconds. The long delay seen on exchanges comes from their security policies, not from the basic speed of the ETC network.<\/p>\n
Requirements of 300 to 500 confirmations are designed to reduce the risk of deep blockchain reorganizations and double-spending attacks. At an average block time of around 13 seconds, this usually means waiting approximately one to two hours.<\/p>\n
Some platforms are considerably more cautious and may require thousands of confirmations.<\/p>\n
For users, the most important thing is to understand the difference between a confirmed blockchain transaction and a deposit credited by an exchange. The first can happen quickly. The second happens only when the receiving platform decides that enough blocks have passed to accept the transaction as final.<\/p>\n","protected":false},"excerpt":{"rendered":"
Sending Ethereum Classic from one wallet to another usually takes less than a minute. The transaction appears in a block explorer, receives its first confirmation, and looks complete. However, when ETC is sent to a […]<\/a><\/p>\n<\/div>","protected":false},"author":1,"featured_media":678,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[2],"tags":[],"class_list":["post-676","post","type-post","status-publish","format-standard","has-post-thumbnail","category-ethereum-classic-reviews"],"_links":{"self":[{"href":"https:\/\/ethereumclassicwallet.com\/articles\/wp-json\/wp\/v2\/posts\/676","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/ethereumclassicwallet.com\/articles\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/ethereumclassicwallet.com\/articles\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/ethereumclassicwallet.com\/articles\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/ethereumclassicwallet.com\/articles\/wp-json\/wp\/v2\/comments?post=676"}],"version-history":[{"count":4,"href":"https:\/\/ethereumclassicwallet.com\/articles\/wp-json\/wp\/v2\/posts\/676\/revisions"}],"predecessor-version":[{"id":681,"href":"https:\/\/ethereumclassicwallet.com\/articles\/wp-json\/wp\/v2\/posts\/676\/revisions\/681"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/ethereumclassicwallet.com\/articles\/wp-json\/wp\/v2\/media\/678"}],"wp:attachment":[{"href":"https:\/\/ethereumclassicwallet.com\/articles\/wp-json\/wp\/v2\/media?parent=676"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/ethereumclassicwallet.com\/articles\/wp-json\/wp\/v2\/categories?post=676"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/ethereumclassicwallet.com\/articles\/wp-json\/wp\/v2\/tags?post=676"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}