Can you really be that ignorant? It is not the ZCL wallet that cannot handle the pressure. It's the exchanges wallet and their infrastructure behind that (databases and backend i.e.). Exchange wallets confirm withdraws and deposits differently than normal wallet to wallet transfer.. This issue has nothing to do with the coin infrastructure or private wallet.
Yeah, they have few hundred coins with more volume who are working without problem
Conspiracy against Zclassic ahah you are right
You really are one ignorant human being. Please go and educate yourself before posting.
If you cannot understand what you read, well that is your problem. ZCL is not the first and not the last coin that will have EXCHANGE end issues. This is similar scenario to what happened with LTC and Doge markets in Cryptopia. I'll just leave it here, tired of people who cannot use their brains.
Everything you need to know about these technical issues can be found here:
https://www.cryptopia.co.nz/Newshttps://www.coinbureau.com/news/bitcoin-private-fork-facing-zclassic-withdrawal-issues-exchanges/For you, genius :
https://support.bittrex.com/hc/en-us/articles/360001271272Additional technical notes:
The upstream project Zcash does not have these wallet issues as we worked closely with their team to implement the following changes:
Zcash GitHub issue 2446 - Add field indicating coinbase tx in output of listunspent
Zcash GitHub issue 2448 - Add an RPC function or flag to create a shielding transaction that only contains coinbase
The Zclassic codebase is behind the upstream Zcash codebase so it does not have these changes implemented. We have requested that the Zclassic team test and implement these changes ASAP.
Tell me it's infrastructures behind Bittrex or Cryptopia now.
It is exchange issue. They use Z wallet in a wrong manner. They skip a few steps as many other wallets work differently. Every new coin should go Z (private) first. Please don't try to be some master developer as you were a mere bounty hunter for BTCP team, if even that.
https://github.com/zcash/zcash/issues/2449"Zcash has a consensus rule that coinbase UTXOs must be shielded. This causes problems for e.g. exchanges using the Bitcoin-inherited RPCs, where they run into errors. As the only way coinbase can be spent is via z_sendmany, it should never be considered for transparent RPCs.
We should modify the transparent coin selection rules used by the inherited transparent RPCs to exclude coinbase. One usability issue is that mining users might get confused if they can't spend everything they appear to have; we should ensure that if users try to spend more than can be funded without coinbase, but could be funded with coinbase, that they still receive an appropriate error."
#2448 - Miners sending NEWLY mined coins to an exchange, these should always go Z first then T. Educate yourself on how Zcoins work, before you come howling here. It is not Zclassic wallet issue, but purely exchange wallet issue as they only give public addresses to people.
"Requested by an exchange. If a miner is sending their mining rewards to an address, and they happen to receive a coinbase output instead of a regular mining payout, then it becomes almost impossible to send transactions from that address until the coinbase output has been shielded. But the Bitcoin-inherited RPCs make it very expensive (in terms of RPC time) to figure out which UTXOs are from coinbase."