hi,
When do you believe it is possible the minning every 6 minutes?
Topic: [ANN] MemoryCoin | CPU Coin | Paid Dev Team | Limited Supply [MMC] - page 64. (Read 281382 times)
December 18, 2013, 09:42:53 AM
December 18, 2013, 09:42:10 AM
December 18, 2013, 09:41:04 AM
So we're on block 618, right?
{
"version" : 85400,
"protocolversion" : 70001,
"walletversion" : 60000,
"balance" : 0.00000000,
"blocks" : 618,
"timeoffset" : 0,
"connections" : 12,
"proxy" : "",
"difficulty" : 0.00000173,
"testnet" : false,
"keypoololdest" : 1387237558,
"keypoolsize" : 101,
"paytxfee" : 0.00000000,
"errors" : ""
}
{
"version" : 85400,
"protocolversion" : 70001,
"walletversion" : 60000,
"balance" : 0.00000000,
"blocks" : 618,
"timeoffset" : 0,
"connections" : 12,
"proxy" : "",
"difficulty" : 0.00000173,
"testnet" : false,
"keypoololdest" : 1387237558,
"keypoolsize" : 101,
"paytxfee" : 0.00000000,
"errors" : ""
}
Thats correct.
December 18, 2013, 09:40:26 AM
So we're on block 618, right?
{
"version" : 85400,
"protocolversion" : 70001,
"walletversion" : 60000,
"balance" : 0.00000000,
"blocks" : 618,
"timeoffset" : 0,
"connections" : 12,
"proxy" : "",
"difficulty" : 0.00000173,
"testnet" : false,
"keypoololdest" : 1387237558,
"keypoolsize" : 101,
"paytxfee" : 0.00000000,
"errors" : ""
}
{
"version" : 85400,
"protocolversion" : 70001,
"walletversion" : 60000,
"balance" : 0.00000000,
"blocks" : 618,
"timeoffset" : 0,
"connections" : 12,
"proxy" : "",
"difficulty" : 0.00000173,
"testnet" : false,
"keypoololdest" : 1387237558,
"keypoolsize" : 101,
"paytxfee" : 0.00000000,
"errors" : ""
}
December 18, 2013, 09:31:12 AM
On my second machine that was stuck at 608 I did the following:
- made sure I have the latest wallet running: v0.8.54.0-unk-beta
- closed the wallet
- deleted folder ./memorycoin (!!! but beware not to delete your wallet if you got some MMCs!!! If so make a backup before!!! )
- restarted the wallet
- did "addnode 180.183.155.90 add" and "addnode 103.11.49.151 add"
- waited until blockchain was downloaded from scratch
all synced now
Thanks - you might get away with just deleting peers.dat - this will force your client to re-evaluate the nodes on the network.
I've been waiting for 10 minites now, still in syning
i was waiting to but after some patience it is all fine now so be patience i think , succes
December 18, 2013, 09:22:23 AM
at first we need a external cpu miner after that pool))
+1
yes, first is need a standalone miner for connect to wallet
FreeTrade has made an external miner for protoshares, MC is not much different.
December 18, 2013, 09:01:50 AM
at first we need a external cpu miner after that pool))
+1
yes, first is need a standalone miner for connect to wallet
You can call it what ever you want. give us a pool
December 18, 2013, 09:00:24 AM
at first we need a external cpu miner after that pool))
+1
yes, first is need a standalone miner for connect to wallet
December 18, 2013, 08:57:03 AM
we still in a need of pool though:)
at first we need a external cpu miner after that pool)) December 18, 2013, 08:54:52 AM
we still in a need of pool though:)
December 18, 2013, 08:31:16 AM
December 18, 2013, 08:21:21 AM
It seems to work a lot better! Thx FT
December 18, 2013, 08:19:01 AM
looks like it's getting better
December 18, 2013, 08:13:58 AM
On my second machine that was stuck at 608 I did the following:
- made sure I have the latest wallet running: v0.8.54.0-unk-beta
- closed the wallet
- deleted folder ./memorycoin (!!! but beware not to delete your wallet if you got some MMCs!!! If so make a backup before!!! )
- restarted the wallet
- did "addnode 180.183.155.90 add" and "addnode 103.11.49.151 add"
- waited until blockchain was downloaded from scratch
all synced now
Thanks - you might get away with just deleting peers.dat - this will force your client to re-evaluate the nodes on the network.
I've been waiting for 10 minites now, still in syning
December 18, 2013, 08:10:06 AM
On my second machine that was stuck at 608 I did the following:
- made sure I have the latest wallet running: v0.8.54.0-unk-beta
- closed the wallet
- deleted folder ./memorycoin (!!! but beware not to delete your wallet if you got some MMCs!!! If so make a backup before!!! )
- restarted the wallet
- did "addnode 180.183.155.90 add" and "addnode 103.11.49.151 add"
- waited until blockchain was downloaded from scratch
all synced now
Thanks - you might get away with just deleting peers.dat - this will force your client to re-evaluate the nodes on the network.
Thanks! I guess this is the more sophisticated version of what I did
Will try deleting peers.dat now and see if it does the trick. But it gets a bit tedious doing this for every block. Is that due to too many outdated nodes?
Oooppps... patience did it again
December 18, 2013, 08:00:35 AM
"blocks" : 609,
"difficulty" : 0.00002268,
Is that correct?
"difficulty" : 0.00002268,
Is that correct?
blocks" : 609
difficulty" : 0.00000185
This is the correct one.
Thanks. On desktop #1 I'm on the correct fork, but on desktop #2 I'm on the wrong one. Both are using the same operating system (W7 x64) and both have the latest client version ("version" : 85400,). They also have the same nodes in the config file.
How can I get on the right fork on desktop #2?
This problem is also occurring on my linux VPS's.
I'm not too sure about this but you could restart the wallet with the -reindex to check the blockchain. See if it helps.
- made sure I have the latest wallet running: v0.8.54.0-unk-beta
- closed the wallet
- deleted folder ./memorycoin (!!! but beware not to delete your wallet if you got some MMCs!!! If so make a backup before!!! )
- restarted the wallet
- did "addnode 180.183.155.90 add" and "addnode 103.11.49.151 add"
- waited until blockchain was downloaded from scratch
all synced now
... but wondering now why block 609 takes so long...
Thanks to the both of you. I'm trying -reindex on the linux instances and will delete the mentioned folder (- wallet.dat) if it fails.
I already deleted everything except wallet.dat on my W7 desktop, and am waiting for it to sync. Will update once it does.
Update: Success! I'm on the right fork on the desktop (blocks 610, difficulty 0.00000178).
Still waiting for the linux instances to "reindex". If that fails I'll try deleting 'peers.dat' as FreeTrade suggested.
Update #2: Success! Linux instances are now on the correct fork. After waiting 1 hour for "reindex" to do its thing, I decided to try method #2 instead. At first I tried to simply delete 'peers.dat', but I still got stuck on the old fork. So I went ahead and deleted everything from the .memorycoin folder (except wallet.dat) which did the trick!
December 18, 2013, 07:57:33 AM
On my second machine that was stuck at 608 I did the following:
- made sure I have the latest wallet running: v0.8.54.0-unk-beta
- closed the wallet
- deleted folder ./memorycoin (!!! but beware not to delete your wallet if you got some MMCs!!! If so make a backup before!!! )
- restarted the wallet
- did "addnode 180.183.155.90 add" and "addnode 103.11.49.151 add"
- waited until blockchain was downloaded from scratch
all synced now
Thanks - you might get away with just deleting peers.dat - this will force your client to re-evaluate the nodes on the network.
December 18, 2013, 07:52:02 AM
"blocks" : 609,
"difficulty" : 0.00002268,
Is that correct?
"difficulty" : 0.00002268,
Is that correct?
blocks" : 609
difficulty" : 0.00000185
This is the correct one.
Thanks. On desktop #1 I'm on the correct fork, but on desktop #2 I'm on the wrong one. Both are using the same operating system (W7 x64) and both have the latest client version ("version" : 85400,). They also have the same nodes in the config file.
How can I get on the right fork on desktop #2?
This problem is also occurring on my linux VPS's.
I'm not too sure about this but you could restart the wallet with the -reindex to check the blockchain. See if it helps.
- made sure I have the latest wallet running: v0.8.54.0-unk-beta
- closed the wallet
- deleted folder ./memorycoin (!!! but beware not to delete your wallet if you got some MMCs!!! If so make a backup before!!! )
- restarted the wallet
- did "addnode 180.183.155.90 add" and "addnode 103.11.49.151 add"
- waited until blockchain was downloaded from scratch
all synced now
... but wondering now why block 609 takes so long...
December 18, 2013, 07:48:05 AM
Frustrating... hows your nerves Freetrade? Hold it together we are all backing you
Thanks Stuart. This is my third coin launch so I'm more calm about these hiccups now than I was on my first outing.
I'm hopeful we've got the basic parameters right now, so I can start giving more time to the stability issues noted. December 18, 2013, 07:47:16 AM
Frustrating... hows your nerves Freetrade? Hold it together we are all backing you
Seconded. Have been following the thread since the beginning and mining, updating and testing. I finally created an account just for this thread! Jump to: