Pages:
Author

Topic: [ANN] MemoryCoin | CPU Coin | Paid Dev Team | Limited Supply [MMC] - page 64. (Read 281389 times)

full member
Activity: 212
Merit: 100
hi,
When do you believe it is possible the minning every 6 minutes?
full member
Activity: 210
Merit: 100
sr. member
Activity: 292
Merit: 250
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" : ""
}

Thats correct.
full member
Activity: 210
Merit: 100
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" : ""
}
legendary
Activity: 1932
Merit: 1005

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  Smiley


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
sr. member
Activity: 420
Merit: 250
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.
sr. member
Activity: 420
Merit: 250
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 Smiley
full member
Activity: 212
Merit: 100
at first  we need a external cpu miner after that pool))

+1

yes, first is need a standalone miner for connect to wallet
legendary
Activity: 1246
Merit: 1000
we still in a need of pool though:)
at first  we need a external cpu miner after that pool))
sr. member
Activity: 420
Merit: 250
we still in a need of pool though:)
newbie
Activity: 51
Merit: 0
member
Activity: 103
Merit: 10
It seems to work a lot better! Thx FT
sr. member
Activity: 420
Merit: 250
looks like it's getting better Smiley
member
Activity: 112
Merit: 10

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  Smiley


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
newbie
Activity: 23
Merit: 0

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  Smiley


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  Grin

Same thing happening again though. Out of sync. Current blocks 609. Estimated blocks 610.

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  Roll Eyes
member
Activity: 112
Merit: 10
   "blocks" : 609,
    "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.
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  Smiley

... 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!
legendary
Activity: 1470
Merit: 1030

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  Smiley


Thanks - you might get away with just deleting peers.dat - this will force your client to re-evaluate the nodes on the network.
newbie
Activity: 23
Merit: 0
    "blocks" : 609,
    "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.
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  Smiley

... but wondering now why block 609 takes so long...
legendary
Activity: 1470
Merit: 1030
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. Smiley I'm hopeful we've got the basic parameters right now, so I can start giving more time to the stability issues noted.
sr. member
Activity: 342
Merit: 250
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!
Pages:
Jump to: