v0.10.15 - Onyx Release

[illodin]

Yeah, I just launched 4 wallets and 3 of them started fine, but one of them not:

getcheckpoint
{
"synccheckpoint" : "0000000000070559f92aeab3e205497f18d01ad4321216973f639cd5cc5eecd0",
"height" : 167960,
"timestamp" : 1415725210,
"subscribemode" : "enforce",
"enforcing" : "off"
}

 

[moli]

My wallet said enforcing was off when it was trying to sync, but once it's synced it's ok.

getcheckpoint
{
"synccheckpoint" : "00000000000a507b6d49abf25d1255a4659297a83bbee3eb0b1949c7b9519d8d",
"height" : 168628,
"timestamp" : 1415830791,
"subscribemode" : "enforce",
"enforcing" : "on"
}

 

[Light]

I noticed that my qt-wallet is acting strange.
Sometimes it refuses to sync on first run and it syncs just fine on second run.
That looks like it stuck on wrong chain or something and then catch the right one.

Last time it happen just now and I was wondering what's going on so I issued getcheckpoint command

getcheckpoint

{
"synccheckpoint" : "0000000000013405800ae1054ff5995798a65969bc095bbc667fcd65dbac57db",
"height" : 168537,
"timestamp" : 1415815968,
"subscribemode" : "enforce",
"enforcing" : "off"
}

enforcing is off...

Closed wallet and run it again (it synced), issued getcheckpoint and this time

getcheckpoint

{
"synccheckpoint" : "00000000001077126c85b08589a571aefe4bd9c57cbecd06258d37511a07152b",
"height" : 168575,
"timestamp" : 1415822003,
"subscribemode" : "enforce",
"enforcing" : "on"
}

everything is fine...

This behavior is really confusing me and I guess a lot of newcomers could be confused even more.
So questions are:
Did someone else noticed the same behavior?
How can it be fixed?

EDIT: I'm on Mac OS 10.10 btw

Yes, I have to close and open my wallet 2-3 times before it fully syncs. I am also on Mac OS.

 

[moli]

Testnet, everyone:

https://darkcointalk.org/threads/v16-x-testing.2976/

 

[moli]

Awesome!

 

[AjM]

I noticed that my qt-wallet is acting strange.
Sometimes it refuses to sync on first run and it syncs just fine on second run.
That looks like it stuck on wrong chain or something and then catch the right one.

Last time it happen just now and I was wondering what's going on so I issued getcheckpoint command

getcheckpoint

{
"synccheckpoint" : "0000000000013405800ae1054ff5995798a65969bc095bbc667fcd65dbac57db",
"height" : 168537,
"timestamp" : 1415815968,
"subscribemode" : "enforce",
"enforcing" : "off"
}

enforcing is off...

Closed wallet and run it again (it synced), issued getcheckpoint and this time

getcheckpoint

{
"synccheckpoint" : "00000000001077126c85b08589a571aefe4bd9c57cbecd06258d37511a07152b",
"height" : 168575,
"timestamp" : 1415822003,
"subscribemode" : "enforce",
"enforcing" : "on"
}

everything is fine...

This behavior is really confusing me and I guess a lot of newcomers could be confused even more.
So questions are:
Did someone else noticed the same behavior?
How can it be fixed?

EDIT: I'm on Mac OS 10.10 btw

Same here, win7 x64, sync problems are very annoying.