Any advice how to fix it? Any special nodes to connect to?
Topic: [ANN][MEME][PEPE] Memetic / PepeCoin - UPDATE 3.1.1.0 - POS - MN - KEKDAQ DEX - page 84. (Read 256584 times)
April 19, 2016, 04:29:56 AM
Just downloaded your r5 win wallet, deleted everything except wallet.dat. Resynced the block chain and stuck again at 70368
Any advice how to fix it? Any special nodes to connect to?
Any advice how to fix it? Any special nodes to connect to?
April 19, 2016, 01:43:37 AM
If you have mature coins in the wallet already, please stake 
Updated the wallet, staking. My weight is 1/10 of network weight right now so it shouldn't take a long time.
April 19, 2016, 01:22:00 AM
I resync'd wallet
after the block 71489 wallet is not synchronized
after the block 71489 wallet is not synchronized
That's the newest block, waiting for a Stake block now and the stake diff is high:
"difficulty" : {
"proof-of-work" : 42.19854517,
"proof-of-stake" : 125424.22568116
},
If you have mature coins in the wallet already, please stake
April 19, 2016, 12:42:29 AM
I resync'd wallet
after the block 71489 wallet is not synchronized
after the block 71489 wallet is not synchronized
April 18, 2016, 11:35:44 PM
node2:~/memetic-core/src# ./memeticd getblockhash 71489
296c6a153ed0eeb71c7175d37db21f53c3906470000edb0ec45beaae4c523a29
Should be the current. The nodes and new network are waiting for stake blocks to come in, and a Bittrex admin is updating when he gets back to the cyberwebs
296c6a153ed0eeb71c7175d37db21f53c3906470000edb0ec45beaae4c523a29
Should be the current. The nodes and new network are waiting for stake blocks to come in, and a Bittrex admin is updating when he gets back to the cyberwebs
Looks good, I resync'd two wallets and both arrived at the same blockchain height.
April 18, 2016, 11:34:01 PM
Whats with the version: "version" : "v1.0.2.5-61404-POSOnly",
It has no PoW enabled.....
April 18, 2016, 11:32:57 PM
Memetic Core 1.0.2.5 - Resolve fork and bump protocol version to block old wallets
MANDATORY UPDATE!!!!!!!!!!!!
MANDATORY UPDATE!!!!!!!!!!!!
Updating and resyncing now. Can you provide a current block + blockhash to verify the correct blockchain?
I'm currently seeing block 71489, blockhash 296c6a153ed0eeb71c7175d37db21f53c3906470000edb0ec45beaae4c523a29 - just want to make sure that's correct.
I get the same...
April 18, 2016, 11:32:07 PM
Memetic Core 1.0.2.5 - Resolve fork and bump protocol version to block old wallets
MANDATORY UPDATE!!!!!!!!!!!!
MANDATORY UPDATE!!!!!!!!!!!!
Updating and resyncing now. Can you provide a current block + blockhash to verify the correct blockchain?
node2:~/memetic-core/src# ./memeticd getblockhash 71489
296c6a153ed0eeb71c7175d37db21f53c3906470000edb0ec45beaae4c523a29
Should be the current. The nodes and new network are waiting for stake blocks to come in, and a Bittrex admin is updating when he gets back to the cyberwebs
April 18, 2016, 11:31:32 PM
Memetic Core 1.0.2.5 - Resolve fork and bump protocol version to block old wallets
MANDATORY UPDATE!!!!!!!!!!!!
WINDOWS WALLET:
http://download.memeticproject.com/memetic-qt-r5-61404.zip
Or
https://mega.nz/#!y5kCVL5R!o7OiV9jIHQOqMT0uCwwy4VJrYfTJjPlfcj8Fbh1Cv1k
Linux Source - please git pull and recompile
https://github.com/memeticproject/memetic-core
The block explorer @ blockpioneers is the wrong version, we're working to contact him to update
MANDATORY UPDATE!!!!!!!!!!!!
WINDOWS WALLET:
http://download.memeticproject.com/memetic-qt-r5-61404.zip
Or
https://mega.nz/#!y5kCVL5R!o7OiV9jIHQOqMT0uCwwy4VJrYfTJjPlfcj8Fbh1Cv1k
Linux Source - please git pull and recompile
https://github.com/memeticproject/memetic-core
The block explorer @ blockpioneers is the wrong version, we're working to contact him to update
yeah syncing again good job
April 18, 2016, 11:30:56 PM
Whats with the version: "version" : "v1.0.2.5-61404-POSOnly",
April 18, 2016, 11:27:31 PM
Memetic Core 1.0.2.5 - Resolve fork and bump protocol version to block old wallets
MANDATORY UPDATE!!!!!!!!!!!!
MANDATORY UPDATE!!!!!!!!!!!!
Updating and resyncing now. Can you provide a current block + blockhash to verify the correct blockchain?
I'm currently seeing block 71489, blockhash 296c6a153ed0eeb71c7175d37db21f53c3906470000edb0ec45beaae4c523a29 - just want to make sure that's correct.
April 18, 2016, 11:13:10 PM
Memetic Core 1.0.2.5 - Resolve fork and bump protocol version to block old wallets
MANDATORY UPDATE!!!!!!!!!!!!
WINDOWS WALLET:
http://download.memeticproject.com/memetic-qt-r5-61404.zip
Or
https://mega.nz/#!y5kCVL5R!o7OiV9jIHQOqMT0uCwwy4VJrYfTJjPlfcj8Fbh1Cv1k
Linux Source - please git pull and recompile
https://github.com/memeticproject/memetic-core
The block explorer @ blockpioneers is the wrong version, we're working to contact him to update
MANDATORY UPDATE!!!!!!!!!!!!
WINDOWS WALLET:
http://download.memeticproject.com/memetic-qt-r5-61404.zip
Or
https://mega.nz/#!y5kCVL5R!o7OiV9jIHQOqMT0uCwwy4VJrYfTJjPlfcj8Fbh1Cv1k
Linux Source - please git pull and recompile
https://github.com/memeticproject/memetic-core
The block explorer @ blockpioneers is the wrong version, we're working to contact him to update
April 18, 2016, 01:24:48 PM
A fork happened at block 71320
One chain reports 4298a1d06c0effb8a6f15205bb5e6d7c6ea3d6ef68a16a40ef9480c49a3cf212 and one reports
956045b105c712ec8d8f12aedfabbeec2d4cc3008fd5005122acbf2b19d4ad56 at block 71320
http://chain.blockpioneers.info/meme/search.php
We'll be going with the 956045b105c712ec8d8f12aedfabbeec2d4cc3008fd5005122acbf2b19d4ad56 fork to match the block explorer.
We're working with Bittrex to get things resolved and checking the codebase. No coins should be lost but you may need to re-sync after the update.
One chain reports 4298a1d06c0effb8a6f15205bb5e6d7c6ea3d6ef68a16a40ef9480c49a3cf212 and one reports
956045b105c712ec8d8f12aedfabbeec2d4cc3008fd5005122acbf2b19d4ad56 at block 71320
http://chain.blockpioneers.info/meme/search.php
We'll be going with the 956045b105c712ec8d8f12aedfabbeec2d4cc3008fd5005122acbf2b19d4ad56 fork to match the block explorer.
We're working with Bittrex to get things resolved and checking the codebase. No coins should be lost but you may need to re-sync after the update.
which is the correct one?
The correct chain is 4298a1d06c0effb8a6f15205bb5e6d7c6ea3d6ef68a16a40ef9480c49a3cf212 ... the quoted text is wrong, we found the block explorer didn't update and is showing some proof of work. There are a lot of people still running the proof of work client but we'll be pushing a new wallet to resolve this and block older protocol versions
April 18, 2016, 01:17:26 PM
And my r4 wallet got stucked at block 70368
There was a few nodes that were still on the old fork, switched them over
Well, but how to fix that. Tried with the nodes from the OP, then without any nodes and finally with some nodes from the block explorer. And always end up and stick with block 70368 (each time I deleted everything and left the wallet.dat file, or also the cob file with the nodes).
April 18, 2016, 01:16:57 PM
A fork happened at block 71320
One chain reports 4298a1d06c0effb8a6f15205bb5e6d7c6ea3d6ef68a16a40ef9480c49a3cf212 and one reports
956045b105c712ec8d8f12aedfabbeec2d4cc3008fd5005122acbf2b19d4ad56 at block 71320
http://chain.blockpioneers.info/meme/search.php
We'll be going with the 956045b105c712ec8d8f12aedfabbeec2d4cc3008fd5005122acbf2b19d4ad56 fork to match the block explorer.
We're working with Bittrex to get things resolved and checking the codebase. No coins should be lost but you may need to re-sync after the update.
One chain reports 4298a1d06c0effb8a6f15205bb5e6d7c6ea3d6ef68a16a40ef9480c49a3cf212 and one reports
956045b105c712ec8d8f12aedfabbeec2d4cc3008fd5005122acbf2b19d4ad56 at block 71320
http://chain.blockpioneers.info/meme/search.php
We'll be going with the 956045b105c712ec8d8f12aedfabbeec2d4cc3008fd5005122acbf2b19d4ad56 fork to match the block explorer.
We're working with Bittrex to get things resolved and checking the codebase. No coins should be lost but you may need to re-sync after the update.
which is the correct one?
April 18, 2016, 01:14:46 PM
A fork happened at block 71320
One chain reports 4298a1d06c0effb8a6f15205bb5e6d7c6ea3d6ef68a16a40ef9480c49a3cf212 and one reports
956045b105c712ec8d8f12aedfabbeec2d4cc3008fd5005122acbf2b19d4ad56 at block 71320
The block explorer hasnt been updated,
The correct chain is 4298a1d06c0effb8a6f15205bb5e6d7c6ea3d6ef68a16a40ef9480c49a3cf212
We're working with Bittrex and trying to contact Blockpioneers to get things resolved and checking the codebase. No coins should be lost but you may need to re-sync after the update.
One chain reports 4298a1d06c0effb8a6f15205bb5e6d7c6ea3d6ef68a16a40ef9480c49a3cf212 and one reports
956045b105c712ec8d8f12aedfabbeec2d4cc3008fd5005122acbf2b19d4ad56 at block 71320
The block explorer hasnt been updated,
The correct chain is 4298a1d06c0effb8a6f15205bb5e6d7c6ea3d6ef68a16a40ef9480c49a3cf212
We're working with Bittrex and trying to contact Blockpioneers to get things resolved and checking the codebase. No coins should be lost but you may need to re-sync after the update.
April 18, 2016, 12:34:42 PM
And my r4 wallet got stucked at block 70368
There was a few nodes that were still on the old fork, switched them over
Deleted the blockchain and tried resyncing again after you posted this, but still stuck i'm afraid.
the same shit....
April 18, 2016, 12:26:19 PM
And my r4 wallet got stucked at block 70368
There was a few nodes that were still on the old fork, switched them over
Deleted the blockchain and tried resyncing again after you posted this, but still stuck i'm afraid.
April 18, 2016, 12:21:47 PM
bittrex market disabled while investigating possible fork
has the dev contacted the exchange
has the dev contacted the exchange
Yes
April 18, 2016, 12:10:45 PM
bittrex market disabled while investigating possible fork
has the dev contacted the exchange
has the dev contacted the exchange
Jump to: