Posts about Zclassic
UPDATE: Electrum has been released and we recommend using that wallet instead: https://github.com/BTCP-community/electrum-zcl/releases
If you were previously using this wallet, when you first open it you can press new wallet from private keys which will allow you to import your private keys from your old wallet. The wallet.dat file from Eleos or Swing will NOT work with Electrum.
Some people report issues recovering private keys from Eleos. You may be able to use the following tool to get your private keys out. Thanks to community member Dwerg for developing this tool and BestServerNA for writing a useful guide on how to use it.
Our development team has put a great deal of effort into making this release happen along with approximately 100 wallet testers in our discord server helping us find and correct issues. You can find the release here. We have also put together 6 dedicated server nodes around the globe to ensure connectivity for all users with more to come! I will also continue to update the config file here if anyone is experiencing issues. I want to remind everyone that they should always test their wallets with small transactions first to ensure it is working properly before sending larger balances. Also, for troubleshooting you can ask questions here or go directly to our discord where there is a channel for each OS to help with troubleshooting with members of our community.
We want to be clear this is a beta wallet and still has issues, though it should install with relative ease and be able to store your ZCL. If you already have a working wallet, then you do not have any reason to use this one. It is an upgrade designed to work for the people who were unable to get the swing wallet working. Here are some issues noted in alpha testing that may be unresolved:
You cannot import a private key into this wallet, though you can export it. The only way to import your wallet is with a wallet.dat file placed in C:\Users\Your-Username\AppData\Roaming\Zclassic. Also, when you export your private keys, please ensure you save it in .txt format. Also, the keys will look jumbled in notepad on Windows, but will look fine when opened with wordpad or equivalent. This may be the same case with the config file.
Sometimes the program does not start properly on the first start up. Just exit and restart it.
The sync status jumps around a lot when you first start the program. Please be patient, it will sync eventually.
The Mac version only works on the latest version of Mac OS (High Sierra and Sierra) and will not work on older versions.
The program is 64 bit and will not work on 32 bit OS.
When sending funds, you must allow for a small transaction fee. If you send all funds out of the wallet with no fee, it will say the transaction was successful but nothing will have happened. Leave at least 0.0001 ZCL in the wallet to pay for a fee when performing transactions.
You cannot run this wallet simultaneously with ZCash wallet or you will have significant trouble.
Transparent addresses will not show in the "addresses" tab until a transaction has posted to it. Please make one in the "receive" tab and then use immediately.
If you found this post and wallet useful, please considering donating to our contribution/development team:
[PLEASE READ] ZClassic > BitcoinPrivate Snapshot/Fork Frequently Asked Questions (FAQ) MEGATHREAD 2.0
I’ve been seeing a lot of repeated questions being asked every day so an updated FAQ/Megathread to address all of those questions will be detailed here. If we are missing something, please feel free to let us know and we will add it. We will try to edit this posting as more information becomes available.
Keep in mind the official Bitcoin Private Support portal has now been launched. We have a live chat feature to chat with support, as well as a knowledge base. Please visit the portal at support.btcprivate.org and use the knowledge base’s search function before asking other users.
When is the snapshot date? Snapshot date will take place on February 28th 2018. The exact moment the snapshot will be taken WILL NOT be announced as a TIME, rather it will be announced as a specific block height. Whatever time happens to be when the block height occurs is whatever time the snapshot is taken. This is to address users who are asking for a specific time or time zone. Once the block height has been mined, the snapshot would have been successfully completed instantly. Users can choose to wait until the NEXT block after the snapshot block has been mined for peace of mind. Once again, the exact block height has not been announced yet. We can only estimate the exact block height as we get closer to the snapshot date. Announcements will come via posts on Reddit, Discord, Twitter/Facebook, Telegram and the official BitcoinPrivate Twitter account which is the primary source of all official announcements.
Why can't we announce a block height instead? Why did we choose to announce a date? Block height is not announced for a reason. Keep in mind this is a DOUBLE FORK. BTC and ZCL. 2 Block heights need to be announced. It's impossible to determine the exact block heights so far away from the snapshot date, because BTC and ZCL both have different block time intervals, and the total hashing power of the entire network of BTC and ZCL are changing so rapidly that it is extremely hard to determine a block height in advance, so we decided to pick a date for when we expect the snapshot block to occur instead. We need to determine the exact moment both block heights of BTC and ZCL will coincide in order to get an accurate and successful snapshot. Also, do not forget that 2 simulated snapshot runs have already been completed and validated by the team some time ago, so the process has already been proven.
When is the Hard fork date? The Hard fork will occur approximately 2 days after the snapshot, on March 2nd, 2018.
Is the snapshot on the 28th for ZClassic or for Bitcoin? The snapshot will be taken simultaneously for both ZCL and BTC. Block heights will be announced for both.
Do I need to hold my ZCL until the snapshot or fork? Snapshot. As soon as the snapshot occurs you are free to do whatever you like with your ZCL and you will still receive your BTCP.
What will happen to ZCL after the Bitcoin Private Fork? Current ZClassic's wallet server nodes (Electrum) will still continue to be supported after the fork, and the core dev team will be actively supporting BTCP, whereas the community can choose to further support development for ZCL.
How can I safely participate in the fork? There are certain safety/security concerns regarding participating in forks. I have addressed this topic here. Please make sure you give it a read.
Claiming BTCP Coins
How does Bitcoin Private rewards/claims work? BTCP Coins will be distributed on a 1:1 ratio. Example: (1 ZCL = 1 BTCP.) (1 Bitcoin = 1 BTCP.) (1 ZCL & 0.5 BTC = 1.5 BTCP.) The total combined amount of ZCL and BTC you own at the time of the snapshot will grant you eligibility to claim the same combined amount in Bitcoin Private. You do NOT need to hold a full amount of a coin. You can own partial amounts of ZCL/BTC.
Do I have to store my ZCL in transparent addresses or private addresses to participate in the fork? Any kind of address will be supported through the fork. However, as of Feb. 13, the ZCL electrum wallet only supports transparent addresses.
Are Segwit-enabled wallet addresses for Bitcoin (BTC) supported for the fork? We have confirmation that BTC being held on Segwit enabled addresses WILL BE supported through the fork.
How do I claim my BTCP? More information will become available as we get closer to the snapshot date. An official dedicated guide will be released. In summary, users will need to export a copy of their private key for the corresponding wallet/wallet addresses that hold their ZCL funds at the time of the snapshot. Users can then take the private key and import it into the Bitcoin Private Electrum wallet once it is released in order to claim their BTCP coins. The same goes for Bitcoin holders. **In case exchange(es) support will be announced, users will not need to do anything. The exchanges will automatically credit your account with BTCP. This may vary, so again, please stay tuned for official news regarding this.
BTCP/ZCL Exchange and Wallet Support
Which exchanges will support the fork? The team CANNOT talk about exchange support at this time. Once the support is announced, we will let users know ASAP. All we can say is that the BTCP team has already applied to Binance, as posted on BTCP's Twitter. This is the only thing we can discuss. Binance strictly forbids teams from disclosing IF or WHEN/DATE they will list on Binance. But they allow teams to announce that they HAVE applied for listing, to ease the urge to talk about it. See the official tweet from the CEO of binance. Please do not spam and repeatedly ask this question. News will come as time passes.
Can users register for Bittrex Accounts? No. Registrations are currently closed. Users can submit a request to open a new account using their Bittrex support form.
Is the Binance application to list ZClassic or Bitcoin Private? The application is to list Bitcoin Private for trading.
Which wallets support the fork? Any wallet which you control the private keys to will support the fork. Right now there are currently 3 available wallets to hold ZClassic in. The original Swing wallet, ELEOS wallet and the new Electrum-Zclassic wallet. We highly recommend users to switch to/begin using the ZClassic Electrum wallet, as it is the most stable and will be updated going into the future. Users have reported to be experiencing issues with the Swing and ELEOS wallet related to “Wallet daemon cannot be started” or “connection cannot be established.” I already have a guide published showing users how to migrate from Swing wallet/ELEOS wallet to the new Electrum wallet. Side note: As of Feb. 13 2018, Coinomi wallet announced support for the fork. ZCL Support will be added by this week, and BTCP support is coming soon as well. Stay tuned for more news regarding this.
Is Bitcoin Private supported by Ledger/Trezor Hardware wallets? Currently it is not supported yet because of a technical implementation that the team has not worked on yet because it doesn't take priority. However, the team will be working on BTCP with regards to hardware wallets after the fork, so stay tuned for announcements.
Where can I find the ZClassic Electrum Wallet? Here, at the ZCL github. Version 1.0.3 is the latest version as of Feb. 13. Please download the latest version, whatever it may be at the time of reading this.
Is there a paper wallet for ZClassic? Yes, there is! You can find it here.
When is the Bitcoin Private wallet being released? Currently the Bitcoin Private Electrum wallet is being developed and rigorously tested by the team. We expect the BTCP Electrum wallet beta to be released slightly before or slightly after the fork occurs. Stay tuned for news.
What other wallets will support Bitcoin Private? The Bitcoin Private Electrum wallet will serve as the “Lite-Client” without having to download the entire blockchain. The team will be working on a GUI version of the BTCP wallet (similar to the java based ZClassic Swing wallet) shortly after the fork. More announcements to come in the future. Coinomi will also support Bitcoin Private.
Issues withdrawing from Cryptopia exchange? As of the week of February 13th 2018, users are reporting issues regarding withdrawing ZCL from Cryptopia. Cryptopia’s coininfo page is showing 0 connections/nodes available. The BTCP team has already tweeted, emailed, called and left voicemails to Cryptopia reaching out to help. It is up to Cryptopia to handle things on their part now. Stay tuned for news regarding this. We have made a separate post addressing this topic. Cryptopia Edit 2: As of February 15 2018, Cryptopia has fixed their node connections. Their backlog is incredibly full and withdrawals are being queued. This may take another few days before your transactions go through.
Where can I buy ZClassic? Currently there are 4 main exchanges that support ZClassic, ranked from ascending order in terms of volume. Bittrex, Cryptopia, Coinexchange.io and TradeSatoshi. Keep in mind as of February 13th, Bittrex is not currently accepting any new registrations. This will hopefully change very shortly.
Donations and Contributions program
Can I donate to the team? Yes, you can! We are all volunteers and your donation is greatly appreciated. See the below wallet donation addresses. You can also join the Voluntary Miner Contribution Program to help raise funds in the form of ZCL for the team’s operations to support the future of BTCP.
Why can't we simply pay/donate the team ZCL in return be rewarded BTCP after the fork? By definition, this is illegal. Doing so would make BTCP act as an ICO. Instead donations to the team directly to support us voluntarily without the expectation of BTCP, or contributing to the ZCL mining pool fund is the only way to support the team.
How can I join the Voluntary Contribution Miner Program even if I’m not a miner? Good news for users who aren’t miners. You can take advantage of NiceHash’s hashing power marketplace to participate in the contribution program. Please refer to the following Steemit tutorial article on how to set everything up.
Can Bitcoin Private be mined, if so, could you provide details? Of course! It will be very similar to ZClassic. Bitcoin Private runs on the Equihash PoW algorithm. Because BTCP runs on Equihash, there WILL be ASIC resistance. The privacy algorithm will be run on zk-snarks. Block time will be every 2.5 Minutes (150 Seconds) with a block size of 2MB. Difficulty Adjustments will be made after every block. Replay Protection is also supported. There will be a 21 Million BTCP Supply WITHOUT a pre-mine.
Which pools can we mine Bitcoin Private on? Currently there are no announcements for pool support yet. More news will become available as we get closer to fork date. Most likely, majority of current pools that support mining ZClassic will support mining BTCP. Yet to be confirmed, stay tuned for announcements.
Is the team releasing any video/article tutorials to prepare for the fork? Yes, our content creation team is working hard to produce high quality video/article tutorials to assist users in preparing for the fork. The official BTCP Youtube channel can be found here. This is also where we stream our conferences live. More announcements on this is forthcoming.
What will be the opening price of Bitcoin Private? Just like every other coin (besides tether), the price will depend on the market and what people value it at.
How do I back up my wallet.dat file or back up my private keys? Please see this guide on how to backup your wallet.dat file(s) and private keys, as well as for any troubleshooting you may require. This is also covered in our support portal's knowledge base..
My wallet is not starting up or cannot connect, what can I do? Please refer to this guide on troubleshooting you may require. This is also covered in our support portal's knowledge base..
Miscellaneous/BTCP Project Questions
Where is the official BTCP Whitepaper? As of the Feb. 13, Finishing touches are being made, and the official Whitepaper will be arriving this week!
Who is part of the Bitcoin Private team? Please see the official BTCP site for a list of team members and contributors!
Details about press inquiries? To reach out to the primary coordinators of the team for any inquiries related to press, please contact us on Twitter!
Donate towards the BTCP contribution team, Your donations are 100% voluntary but they are much appreciated!
BTCP Related Important Links
BTCP Blockchain Explorer To Be Announced
For the official list of links from the BTCP Github, refer to the repo.
Just a re-iteration, the BTCP team has launched the support portal offering resources ranging from live support from our teams, as well as a knowledge base that is constantly being updated. https://support.btcprivate.org Again, please feel free to let me know any questions that’s not currently listed above and we will do our best to answer and include it in the megathread.
(Upvote to the top) > SOLUTION FOR ZCLASSIC Eleos Wallet: "Wallet daemon can not be run. Check if daemon does not already run"
So I noticed a lot of people recently (including myself) are experiencing the error "Wallet daemon can not be run. Check if daemon does not already run" when trying to open up their ZCL Eleos wallet, and people are unable to access their funds or cannot export their private keys as well. A solution to this is now official (thanks to /u/JBrutWhat from the BTCP team for helping me out on this.) Note: Post is being edited as more info becomes available to me.
This solution also works for users who are on the ZClassic Swing wallet experiencing the error "A general unexpected critical error has occurred: error: Couldn't connect to server, see the console output for more detailed error information!."
Eleos Wallet Troubleshooting section
The Wallet.dat file from the Eleos wallet or Swing wallet DOES NOT work with Zclassic electrum, so we are going to import the private key of the wallet into electrum instead.
Navigate to the c:\users\username\appdata\roaming\zclassic folder and copy the wallet.dat file from there, back it up somewhere.
Download the entire .zip of the walletaid tool from this github repo. The tool has been forked from the original dev /u/Dwerg1 officially by the BTCP team and has been confirmed to be legitimate according to /u/JBrutWhat (instructions on how to operate the walletaid tool wasn't clear or in-depth to some users.)
Download & Install python 2.7 and select "Add python.exe to Path" during installation
Extract the .ZIP file somewhere
Paste the wallet.dat you backed up earlier into the same folder as the walletaid tool folder
Right click the config.ini file and edit the file using notepad or notepad++ or your own text editor
remove the "#" symbol from the zclassic sections under "#Pubkeyprefix list" and "#privkeyprefix list"
copy the text "1cb8" and replace the "00" under the pubkeyprefix section under "[settings]" at the top
Doubleclick the walletaid.py file and press enter. Let it create the entire file with ALL the wallet addresses from your wallet.dat file. Or you could paste in the exact address you want and it should export a foundkeys.txt file into the walletaid directory. (The extract keys.bat file doesn't always work. It didn't work for me.) NOTE: If the walletaid.py script opens and instantly closes, this is because your wallet.dat file has a different name. Please rename your wallet file back to "wallet.dat" for compatibility.
Open up the foundkeys.txt file and it should list out every detected address and it's corresponding private key from your wallet.dat file you pasted in earlier
Do a ctrl + F and paste in the wallet address that contains your funds.
Locate the wallet address you are looking for and it's corresponding private key. We'll come back to this later.
IMPORTANT: MAKE SURE YOU DELETE THE PRIVATE KEYS FILE FROM YOUR COMPUTER AFTER FINISHING WITH IT. BACK IT UP TO AN OFFLINE USB STICK. DO NOT KEEP IT ON YOUR DESKTOP/HARD DRIVES OR ONLINE. Your private keys can potentially compromise ALL of your funds. Keep this safe and NEVER share it with anybody.
ZClassic Electrum Wallet
For users that are experiencing problems syncing their Electrum ZCL wallets, or their transactions are showing "not verified" after importing a wallet, this is because the blockchain_headers have not been successfully downloaded. We'll have to delete them let it re-sync. For Windows users, first close the electrum wallet. Then navigate to *C:\Users\UsernameXXX\Appdata\Roaming\Electrum-ZCL* and from there delete ONLY the "blockchain_headers" file. Then re-open the wallet and allow it to sync. For Mac OS users, close the wallet and navigate to ~/.electrum-zcl/ and delete ONLY the blockchain_headers file once again. Then reopen the wallet. Please see github issue #77 thread here for more help.
**FOR USERS HAVING ISSUES SENDING/WITHDRAWING ZCL FUNDS FROM A 2FA ENABLED ELECTRUM-ZCL WALLET, PLEASE FOLLOW STEPS BELOW FOR RESOLUTION. Alternatively, this is also covered in our official ZCL electrum github repository under issue #44. Thanks to wallet dev Ch4otic for helping with this issue.
Create a new standard wallet and restore the 2FA wallet using your "seed" codes. DO NOT password protect this wallet.
Disable the 2FA feature when presented with the option.
Navigate to C:/Users/YOUR-NAME/AppData/Roaming/Electrum-zcl/wallets. Open the new standard wallet file with Notepad.
You will need to gather the 2 private keys and one public key. To find this easily, press “CTRL+F” and search for “xprv”. Copy the 2 “xprv” values as well as the last “xpub” value. You will need these in a later step.
Create a new “Multi-signature wallet”. Select “From 3 co-signers” on the first slider. Select “Require 2 signatures” on the second slider.
To add the first co-signer, click “Use public or private keys”. Enter the first xprv key in this box.
Add the second co-signer via a private key also.
Add the third co-signer with the public key. Complete the set-up.
Your wallet funds now have the ability to be sent from the multi-signature wallet.
It's recommended by the BTCP team to switch over to the ZCLASSIC Electrum wallet ASAP as the Eleos wallet has become unstable now. The original ZClassic swing wallet is reported to still be working. Up to you whether or not to use the electrum wallet, but I'd personally recommend it.
Download Link to Zclassic electrum wallet (v1.0.3 latest version) (Grab the latest win.zip file for windows users)
Open up the wallet and create a new wallet, then when it gives you the option to import private keys, paste in your appropriate private key from the foundkeys.txt file we generated earlier.
Afterwards, your wallet should have successfully migrated your wallet into the ZCL electrum wallet. There's currently a synchronization issue upon first boot of the wallet, so close and re-open it again and you should be fine. If not, try closing the electrum wallet, navigate to "c:\users\username\appdata\roaming\Electrum-zcl folder and delete the "blockchain_headers file, as initial download of the blockchain headers sometimes initially fails. Then restart the wallet and you should be fine, according to the dev team.
Users of older ZCL electrum wallets before version 1.0.3 should download the latest version. I was on the older version (1.0.0 and noticed my wallet wouldn't sync.) So I upgraded to the latest version and wallet has successfully synced.
Also make sure to encrypt your electrum wallet by clicking the little settings icon at the bottom right.
For Users who were already using the Electrum wallet beforehand, you can go to file > new/restore wallet > next > import zclassic private keys and input the private key you obtained from the walletaid tool, and it should import the wallet into the electrum wallet. Then from there, go to file > backup wallet and export a copy of the wallet.dat file onto an offline USB.
Side notes: ZCL-Electrum wallet Does support mining directly to it. More ZCL Electrum servers will be added along with newer releases soon. Another note: Every time you want to migrate funds from one address to another, test it with a small amount first before proceeding with the full amount. BTCP Team has also partnered with Coinomi to release a wallet supporting ZCL and BTCP after the hard fork occurs.
Reminder: Backup and delete the private keys file from your desktop pc/hard drive, move it into an offline USB for safekeeping. Do not leave it on an online device.
Donate to me if you found the guide useful! Your donations 100% voluntary but they are greatly appreciated and keep us going!
(You can join the discord rooms where there are channels for users looking for help)
We have released the Electrum wallet which you can find here: https://github.com/BTCP-community/electrum-zcl/releases
This is an old wallet which we do not recommend for new users. Please use the electrum wallet. I am leaving the guide here just in case it proves to be useful for someone.
Please make sure you install the latest version of java before proceeding: https://java.com/en/download/
New Install, Even Faster and Easier
Download the following Zip file from our GitHub and follow the installation instructions within:
Once installed, please do the following to become a full node and help with connections
In order to become a full node, you will need to open port 8133 on your router firewall. You can check if your port is open here. For me, I was able to do this by navigating my browser to the router setting page and find the advanced settings to open port 8133 and then also set my IP for my computer running the node to static. Fact is that every router is different so I cannot teach you how to do this for your router, you will likely need to google it or search around for the proper settings. I hope that everyone will take the time to do this so we can fix our connectivity issues.
Alternative Install from Walter S: THIS IS EXPERIMENTAL, USE AT OWN RISK. Run this installer as administrator or it will not work! This also downloads the blockchain when installing.
Blockchain download up to Dec 3, 2017
Using this will allow for faster syncing and connections will occur faster as well, I highly recommend using it. People who are having trouble connecting quickly will benefit greatly from this. Just drop the files and folders inside into C:\Users\Your-Username\AppData\Roaming\Zclassic\
Please let me know if you need anymore help. Also, please consider a donation if this guide helped you! I have plenty of student debt to pay off :-P
-JBrutWhat aka BlueSilver
I get the error "The wallet will not open or gives me the following error: For input string: "0,02". What should I do?" From user Lockalyo: 'I found the cause and the solution for this problem. You have another date and number format set in Windows. The reason is that the decimal symbol in US is "." (dot) and in other languages it is comma ",". So the GUI gives you error because it expects dot, but gets comma as delimiter. The specified number is actually the sync percent of the chain - 0.02 for brand new installation and over 90.1 in case you downloaded the chain from the link in description.'
Why can't I get any connections?! See information here and firewall instructions above. I added a new zclassic.conf file to the github release with significantly more nodes and will continue to update daily for people to grab if they are having issues connecting; you will find the latest config file here. At any time if you are having trouble connecting, please go here to see a list of active nodes and add them (along with :8133 at the end or [node address]:8133 for non-IP nodes) to your zclassic.conf file to ensure better connection.
Every time I open the wallet, it has to resync from a previous date, why is that? Please use “stop_wallet.bat” to stop the wallet and not just close it. This will prevent the resync from occurring as well as stop it from starting with “activating best chain” each time you open the wallet. Thanks to OwlHonda for discovering the fix.
How do I backup my private key and wallet? For the private key, go to the GUI wallet, press wallet > show private key and write this down in a safe place. For the wallet.dat file, navigate to C:\Users\YOUR-USERNAME\AppData\Roaming\Zclassic\ and grab the wallet file to be backed up in your location of choice.
The wallet will not open or gives me the following error: For input string: "0,02". What should I do? This did not happen in the old installer, nor is it happening for me. My only solution is for you to use the old method below. The file size is too large to put on github so I uploaded it to google drive. Follow the instructions included.
The software does not allow me to back up the wallet or private key. First, you can back up the private key by pressing wallet > show private key and writing it down. To back up the wallet file, go to C:\Users\Your-Username\AppData\Roaming\ZClassic\ and copy the wallet.dat file to somewhere safe to back it up.
Old Installation Method
Download this and following the instructions included.
We would like to clarify our last tweet to the community. We recently discovered that the number for total supply quoted on various sites, such as CoinMarketCap, was incorrect for ZCL. There are approximately 3 million ZCL in circulation, not 1.8 million. We, like everyone else, had been assuming that the numbers quoted on these sites was correct and we apologize for not digging deeper. The correct supply was recently discovered by our development team, and we wanted to be sure to make this correction as soon as possible. We are a 100% fully transparent project and refuse to lie to our community. Thus, we tweeted this information out as soon as possible to ensure CoinMarketCap could update their information accordingly.
We want to be clear that these coins did not appear out of thin air, they have been there all along, we just did not realize it until now. In fact, what it means is that the market cap of ZCL is significantly higher.