Topic: Transfering from 6667 to 8333 ... (Read 158 times)
VoIP virtual phone numberbecame a searcher,wanting to discover who i was and what made me precise. my view of myself turned into changing. i desired a stable base to start from. i commenced to resist3 stress to behave in ways that i didn’t like any greater,and i used to be delighted by who i in reality become. i got here to feel a good deal extra sure that no one can ever take my region.
If you have a older wallet which had mining capability and has generated coins on the old 6667 network which was P2P ..and its seen in the balance of the old core client.... how would you be able to move them over to the current 8333 network?
Are you talking about old generated coin but the client have no connection?Your generated coins are included to the block that you've mined so if it's broadcasted at that time, your old mined block should've been in the blockchain by now.
You wont be needing anything but your wallet.dat file, create a backup, a copy and load that copy to the latest version of bitcoin core.
Or is it about mining today using the old client but somehow forced a connection?
If you're connected to your own Network: It will try to build on top of the latest block that it has; if successful, you'll see a pending balance but it's invalid to the Bitcoin network.
If you're connected to the Bitcoin Network: It will try to mine but wont be successful due to the current difficulty.
BTW, the latest client also has cpu mining capability in the form of generate (cli) or generatetoaddress (it's intended for RegTest).
It will work in the mainnet but as you can expect, its mining wont be successful.
[set a very high "maxtries" for longer mining and see your CPU process (1-core) utilization ramp up]
The exact P2P network used shouldn't matter, because its the wallet.dat that stores your funds.
My advice is NOT to directly insert this file into recent versions of Bitcoin Core, but instead, migrate it to a 2012-13 version of Core or an old version that supports wallet version 10500 (the earliest format recognized by Core 23.0 - for comparison, wallet encryption was introduced after wallet version 10500, so that's a long list of compatible Bitcoin versions supporting 10500).
And once you load it into the slightly newer version, then you can add it to the latest Bitcoin Core.
My advice is NOT to directly insert this file into recent versions of Bitcoin Core, but instead, migrate it to a 2012-13 version of Core or an old version that supports wallet version 10500 (the earliest format recognized by Core 23.0 - for comparison, wallet encryption was introduced after wallet version 10500, so that's a long list of compatible Bitcoin versions supporting 10500).
And once you load it into the slightly newer version, then you can add it to the latest Bitcoin Core.
the old 6667 network
~
the current 8333 network
Are you talking about the ports Bitcoin Core uses?~
the current 8333 network
Quote
a older wallet which had mining capability
Unless your software is really old: any chance this isn't Bitcoin but some altcoin? 
Make as many secure backups as you can to start with.
You can also copy and paste the addresses (beginning with 1, if you have them) you have on the old version with balances in them to check the funds are still there - once you've done that there's then no rush to actually update your node to the current software/download the blockchain.
Then I'd follow either of the above recommendations to actually restore your wallet and access the funds.
You can also copy and paste the addresses (beginning with 1, if you have them) you have on the old version with balances in them to check the funds are still there - once you've done that there's then no rush to actually update your node to the current software/download the blockchain.
Then I'd follow either of the above recommendations to actually restore your wallet and access the funds.
The wallet.dat file is all you need. Make a backup or 4 of it and install the new version of bitcoin core and put it in your data directory. It should update the wallet and then download the current blockchain (~450gb) and you should be fine.
Depending on how old the wallet is you may have to do some jumps from older versions to newer ones, which is why you should make backups before doing anything.
-Dave
Depending on how old the wallet is you may have to do some jumps from older versions to newer ones, which is why you should make backups before doing anything.
-Dave
If you have a older wallet which had mining capability and has generated coins on the old 6667 network which was P2P ..and its seen in the balance of the old core client.... how would you be able to move them over to the current 8333 network?
Is there a difference or a certain process to do this, as they dont seem to be transferring over .... just wondering if there is a way to do this or is it too old and now lost ? ....
Thank you.
Jump to: