-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Incompatibility in new RC4+ wallet and moving funds #44
Comments
Use dumpprivkey and importprivkey. example |
Thank you for this recommendation, @chaeplin. Does this in fact preserve the old address and transport it to a new and perfectly working wallet? Might be that I didn't understand it right yet.. |
@SecUpwN I have checked the address XxEJvrYtkTZzvMUjtbZwPY34MyCGHSu4ys and the address has transactions. So use following procedure.
|
Thanks, @chaeplin. To make sure, will this preserve |
@SecUpwN Step 1) is needed to collect funds in change addresses. |
Oh, you already did that for me, @chaeplin? If so, THANK YOU! Somehow I still get the error.. |
@SecUpwN After successfully imported on a new wallet, delete file used at step 2) to record private key. dumpprivkey importprivkey [label] [rescan=true] |
Ok, that sounds good. Do I really have to "send all funds to a new address" even though our wallet is currently empty (did sent out the last few donations to one of our helpful developers), @chaeplin? |
@SecUpwN oh balance is zero, then dump XxEJvrYtkTZzvMUjtbZwPY34MyCGHSu4ys only :) |
Sounds better. :) Would you please tell me step by step how to do that, @chaeplin? |
@chaeplin, that worked excellent. Thanks for your guidance and for starring our project! 😺 |
* New fees, and update checkpoints * Bump protocol and version * Update maxTxFee value, and the minTxFee that the mempool can accept.
…older Gitian: update gitian script, create inputs folder if there is no
set version to master (99), edge channel
Merge chia tag 1.0.15 into develop
Hi there, @darkcoin developers!
I am currently trying to solve this annoying warning that pops up every single time:
Is there a way of preserving the Dark Coin address somehow? The address is important for our security-related project on GitHub, the so-called Android IMSI-Catcher Detector and has already been spread wide around the interwebz. It would be lovely not having to change it everywhere.
The text was updated successfully, but these errors were encountered: