[ANN][OC] Orangecoin v2.0.4 ✦ PoS ✦ Anon ✦ Masternode Whitepaper ✦ Get Juiced!

[crazyearner]

Well updated to latest wallet and was up to date and now today after not running for 24/48 hours. Closed and re opened client a number of times and it will not update currently stuck block 287972. 541 blocks remaining and not downloading yet have 11 active connections using most resent nodes. Any ideas to resolve this ?

you can create a batch file and have it look like this: "OrangeCoin-Qt.exe  -debugnet" <!!!!!---- JUST THAT TEXT WITHOUT QUOTES!

And then keep an eye on the debug.log in the %appdata% folder Pm me the tail end of it like 25-50 lines (notepad2 helps with numbering)

Well just downloaded blocks but now on 287972 out of estimated that is less. From part of the log below and will post rest in pm

InvalidChainFound: invalid block=58d78fbdc5cfeb0bd029  height=289248  trust=82356770077843  date=09/01/15 22:21:45
InvalidChainFound:  current best=e40fc6efeddc0c35e032  height=287972  trust=81777920688344  date=08/31/15 00:41:51

[raven7886]

I have that same entry on mine so and it JUST came up with the SYNC bar, I didnt have a SYNC bar for a few hours...

[crazyearner]

Can only wait and see if devs can provide some light on the matter. Maybe to make force and update though to old wallets to announce new wallet download and release.

Feature for the future.

Wallet updater. On loading wallet has little feature to check current version and also announce and a small popup saying update available download and update gives option to close or update. When clicking update launches command to close wallet and update services in background and then pop back up and run client after update with another one saying successful That way users would get updates a lot quicker too:)

[raven7886]

Can only wait and see if devs can provide some light on the matter. Maybe to make force and update though to old wallets to announce new wallet download and release.

Feature for the future.

Wallet updater. On loading wallet has little feature to check current version and also announce and a small popup saying update available download and update gives option to close or update. When clicking update launches command to close wallet and update services in background and then pop back up and run client after update with another one saying successful That way users would get updates a lot quicker too:)

Nice! That's what we need! Community ideas!

Cheers!

-Raven

[Halofire]

Can only wait and see if devs can provide some light on the matter. Maybe to make force and update though to old wallets to announce new wallet download and release.

Feature for the future.

Wallet updater. On loading wallet has little feature to check current version and also announce and a small popup saying update available download and update gives option to close or update. When clicking update launches command to close wallet and update services in background and then pop back up and run client after update with another one saying successful That way users would get updates a lot quicker too:)

Nice! That's what we need! Community ideas!

Cheers!

-Raven

Raven, I would forward that great idea to soopy if I were you .

[raven7886]

Can only wait and see if devs can provide some light on the matter. Maybe to make force and update though to old wallets to announce new wallet download and release.

Feature for the future.

Wallet updater. On loading wallet has little feature to check current version and also announce and a small popup saying update available download and update gives option to close or update. When clicking update launches command to close wallet and update services in background and then pop back up and run client after update with another one saying successful That way users would get updates a lot quicker too:)

Nice! That's what we need! Community ideas!

Cheers!

-Raven

Raven, I would forward that great idea to soopy if I were you .

Sent PM, do we have an API for the version check?

[Halofire]

Can only wait and see if devs can provide some light on the matter. Maybe to make force and update though to old wallets to announce new wallet download and release.

Feature for the future.

Wallet updater. On loading wallet has little feature to check current version and also announce and a small popup saying update available download and update gives option to close or update. When clicking update launches command to close wallet and update services in background and then pop back up and run client after update with another one saying successful That way users would get updates a lot quicker too:)

Nice! That's what we need! Community ideas!

Cheers!

-Raven

Raven, I would forward that great idea to soopy if I were you .

Sent PM, do we have an API for the version check?

A question for soopy. I know nothing about API's. Sorry!

[soopy452000]

Can only wait and see if devs can provide some light on the matter. Maybe to make force and update though to old wallets to announce new wallet download and release.

Feature for the future.

Wallet updater. On loading wallet has little feature to check current version and also announce and a small popup saying update available download and update gives option to close or update. When clicking update launches command to close wallet and update services in background and then pop back up and run client after update with another one saying successful That way users would get updates a lot quicker too:)

I m aware of the invalid chain issue mate as well as the blockchain getting stuck now and then and there's , a fix is on its way. Please hold on tight.

Also its indeed a great idea. I believe we would be able to achieve this through RPC calls.

Thank you again for your suggestions and support.

Warm Regards,
~SoopY~

[nonissan]

Hey all. I updated to 2.0, and I have been stuck on syncing since yesterday; 5294 blocks remaining. Do I need to do any other updates?

Still stuck. Can somebody please explain the steps I need to take to get my updated 2.0 working?

Thanks

Wow... even worse than before. I have 2.0 running. I redownloaded the 265k pre 2.0 bootstrap.

Config is:
rpcuser=username
rpcpassword=password
rpcallowip=127.0.0.1
daemon=1
server=1
listen=1
port=18872
rpcport=18873
addnode=orangecoinseednode1.no-ip.org
addnode=orangecoinseednode2.no-ip.org
addnode=orangecoinseednode3.no-ip.org
addnode=orangecoinseednode4.no-ip.org
addnode=orangecoinseednode5.no-ip.org
addnode=75.130.163.51:18872
addnode=92.19.22.234:18872
addnode=50.188.13.41:18872
addnode=149.202.102.73:18872

and now, instead of being stuck on 5294 blocks remaining, I'm stuck on 23,298 blocks remaining...

[GREEDYJOHN]

Hey all. I updated to 2.0, and I have been stuck on syncing since yesterday; 5294 blocks remaining. Do I need to do any other updates?

Still stuck. Can somebody please explain the steps I need to take to get my updated 2.0 working?

Thanks

Wow... even worse than before. I have 2.0 running. I redownloaded the 265k pre 2.0 bootstrap.

Config is:
rpcuser=username
rpcpassword=password
rpcallowip=127.0.0.1
daemon=1
server=1
listen=1
port=18872
rpcport=18873
addnode=orangecoinseednode1.no-ip.org
addnode=orangecoinseednode2.no-ip.org
addnode=orangecoinseednode3.no-ip.org
addnode=orangecoinseednode4.no-ip.org
addnode=orangecoinseednode5.no-ip.org
addnode=75.130.163.51:18872
addnode=92.19.22.234:18872
addnode=50.188.13.41:18872
addnode=149.202.102.73:18872

and now, instead of being stuck on 5294 blocks remaining, I'm stuck on 23,298 blocks remaining...

Go to https://chainz.cryptoid.info/oc/#!network.

Under "Version, Protocol & Network Share", click "node list" for /OrangeCoin:2.0.0/.

Copy all the nodes that are shown in the page that pops up and add these nodes to your orangecoin.conf .

Close your wallet, then open it again to sync.

[TimC]

Go to https://chainz.cryptoid.info/oc/#!network.

Under "Version, Protocol & Network Share", click "node list" for /OrangeCoin:2.0.0/.

Copy tall the nodes that are shown in the page that pops up and add these nodes to your orangecoin.conf .

Close your wallet, then open it again to sync.

Also, you client may show that it is out of sync but if you match the block explorer then you are in sync and on the correct chain.
Right now my wallet is in sync with the block explorer at block height of 288536. So if you are on the block block at the block explorer you are on the correct chain.

[raven7886]

Go to https://chainz.cryptoid.info/oc/#!network.

Under "Version, Protocol & Network Share", click "node list" for /OrangeCoin:2.0.0/.

Copy tall the nodes that are shown in the page that pops up and add these nodes to your orangecoin.conf .

Close your wallet, then open it again to sync.

Also, you client may show that it is out of sync but if you match the block explorer then you are in sync and on the correct chain.
Right now my wallet shows that is it 1214 blocks behind but I"m in sync with the block explorer at block height of 288536. So if you are on the block block at the block explorer you are on the correct chain.

Yeah huge bug in wallet. Says not synced, no green bar. But a checkmark is there. On current block.... Caused me to restart several times thinking I had a problem. But in the background it is still fighting the other chain.. .

[Wheezy-]

My wallet is on 289781, still generating blocks, says fully synced and connected to 6 active connections. I'm using the nodes from chainz in my config, but I'm ahead of the explorer.

How do I check if I'm on the correct blockchain?

[nonissan]

Hey all. I updated to 2.0, and I have been stuck on syncing since yesterday; 5294 blocks remaining. Do I need to do any other updates?

Still stuck. Can somebody please explain the steps I need to take to get my updated 2.0 working?

Thanks

Wow... even worse than before. I have 2.0 running. I redownloaded the 265k pre 2.0 bootstrap.

Config is:
rpcuser=username
rpcpassword=password
rpcallowip=127.0.0.1
daemon=1
server=1
listen=1
port=18872
rpcport=18873
addnode=orangecoinseednode1.no-ip.org
addnode=orangecoinseednode2.no-ip.org
addnode=orangecoinseednode3.no-ip.org
addnode=orangecoinseednode4.no-ip.org
addnode=orangecoinseednode5.no-ip.org
addnode=75.130.163.51:18872
addnode=92.19.22.234:18872
addnode=50.188.13.41:18872
addnode=149.202.102.73:18872

and now, instead of being stuck on 5294 blocks remaining, I'm stuck on 23,298 blocks remaining...

Go to https://chainz.cryptoid.info/oc/#!network.

Under "Version, Protocol & Network Share", click "node list" for /OrangeCoin:2.0.0/.

Copy all the nodes that are shown in the page that pops up and add these nodes to your orangecoin.conf .

Close your wallet, then open it again to sync.

worse yet... 23,304 remaining. Also, my OC balance is showing only around 1/10th of what it should be

[raven7886]

Hey all. I updated to 2.0, and I have been stuck on syncing since yesterday; 5294 blocks remaining. Do I need to do any other updates?

Still stuck. Can somebody please explain the steps I need to take to get my updated 2.0 working?

Thanks

Wow... even worse than before. I have 2.0 running. I redownloaded the 265k pre 2.0 bootstrap.

Config is:
rpcuser=username
rpcpassword=password
rpcallowip=127.0.0.1
daemon=1
server=1
listen=1
port=18872
rpcport=18873
addnode=orangecoinseednode1.no-ip.org
addnode=orangecoinseednode2.no-ip.org
addnode=orangecoinseednode3.no-ip.org
addnode=orangecoinseednode4.no-ip.org
addnode=orangecoinseednode5.no-ip.org
addnode=75.130.163.51:18872
addnode=92.19.22.234:18872
addnode=50.188.13.41:18872
addnode=149.202.102.73:18872

and now, instead of being stuck on 5294 blocks remaining, I'm stuck on 23,298 blocks remaining...

Go to https://chainz.cryptoid.info/oc/#!network.

Under "Version, Protocol & Network Share", click "node list" for /OrangeCoin:2.0.0/.

Copy all the nodes that are shown in the page that pops up and add these nodes to your orangecoin.conf .

Close your wallet, then open it again to sync.

worse yet... 23,304 remaining. Also, my OC balance is showing only around 1/10th of what it should be

Your coins are safe. We just need to get you some more blocks they will reappear.

[Halofire]

Go to https://chainz.cryptoid.info/oc/#!network.

Under "Version, Protocol & Network Share", click "node list" for /OrangeCoin:2.0.0/.

Copy tall the nodes that are shown in the page that pops up and add these nodes to your orangecoin.conf .

Close your wallet, then open it again to sync.

Also, you client may show that it is out of sync but if you match the block explorer then you are in sync and on the correct chain.
Right now my wallet shows that is it 1214 blocks behind but I"m in sync with the block explorer at block height of 288536. So if you are on the block block at the block explorer you are on the correct chain.

Yeah huge bug in wallet. Says not synced, no green bar. But a checkmark is there. On current block.... Caused me to restart several times thinking I had a problem. But in the background it is still fighting the other chain.. .

To your reply raven, that behavior you describe is not a "bug", but it helps diagnose your individual wallet. This is completely normal from your wallet and the network's point of view. Let me explain. Your wallet is "synced", but after like an hour or whatever the time limit in the code is, if there are no blocks sensed by your wallet, then it thinks it's out of sync but it's not. This behavior is able to tell us what might happen though. Once you stake, IF you stake, you will stake and confirm and gets accepted by the entire network OR make your own fork since there have been stakes in the last couple minutes.

I've been back online with one wallet after a problem I had. I am staking with everyone else, fully synced and at block number 289791 with 2.0.0.

I really would like to wait for soopy's release before we continue. I'll keep my wallet on and see what it does. I'm still syncing from scratch on another.

[Halofire]

Hey all. I updated to 2.0, and I have been stuck on syncing since yesterday; 5294 blocks remaining. Do I need to do any other updates?

Still stuck. Can somebody please explain the steps I need to take to get my updated 2.0 working?

Thanks

Wow... even worse than before. I have 2.0 running. I redownloaded the 265k pre 2.0 bootstrap.

Config is:
rpcuser=username
rpcpassword=password
rpcallowip=127.0.0.1
daemon=1
server=1
listen=1
port=18872
rpcport=18873
addnode=orangecoinseednode1.no-ip.org
addnode=orangecoinseednode2.no-ip.org
addnode=orangecoinseednode3.no-ip.org
addnode=orangecoinseednode4.no-ip.org
addnode=orangecoinseednode5.no-ip.org
addnode=75.130.163.51:18872
addnode=92.19.22.234:18872
addnode=50.188.13.41:18872
addnode=149.202.102.73:18872

and now, instead of being stuck on 5294 blocks remaining, I'm stuck on 23,298 blocks remaining...

Go to https://chainz.cryptoid.info/oc/#!network.

Under "Version, Protocol & Network Share", click "node list" for /OrangeCoin:2.0.0/.

Copy all the nodes that are shown in the page that pops up and add these nodes to your orangecoin.conf .

Close your wallet, then open it again to sync.

worse yet... 23,304 remaining. Also, my OC balance is showing only around 1/10th of what it should be

If you are not fully synced, you may show an incorrect balance.

[Halofire]

Here's a little math, proving some blocks are paying 10% and the MINT fix is definitely working.

https://chainz.cryptoid.info/oc/tx.dws?648364.htm

The stake for this TX occured today. The previous stake was 24 days before this.

10%/365= .0002739 (PoS % per day) * approximately 24 days = .006575 (PoS % for 24 days) * 406.03657 = 2.6698 OC produced in the stake. The explorer shows 2.717808 OC created. Close enough for me.

Addition:
23 days is 2.55 OC
24 days is 2.66
24.5 days is 2.72 -- used average of 24 and 25.
25 days is 2.78.

We can deduce that the actual "days" is equal to ~24.5.

[Halofire]

Code:

"addr" : "149.202.102.73:18872",
"services" : "00000001",
"lastsend" : 1441219606,
"lastrecv" : 1441219606,
"conntime" : 1441209082,
"version" : 60604,
"subver" : "/OrangeCoin:2.0.0/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 288514,
"banscore" : 0
},
{
"addr" : "75.130.163.51:18872",
"services" : "00000001",
"lastsend" : 1441218092,
"lastrecv" : 1441217854,
"conntime" : 1441209088,
"version" : 60604,
"subver" : "/OrangeCoin:2.0.0/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 288514,
"banscore" : 0
},
{
"addr" : "76.31.113.59:18872",
"services" : "00000001",
"lastsend" : 1441219605,
"lastrecv" : 1441219606,
"conntime" : 1441209466,
"version" : 60604,
"subver" : "/OrangeCoin:1.0.9/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 289726,
"banscore" : 0
},
{
"addr" : "93.123.163.96:18872",
"services" : "00000001",
"lastsend" : 1441219545,
"lastrecv" : 1441219545,
"conntime" : 1441209517,
"version" : 60604,
"subver" : "/OrangeCoin:1.0.9/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 289727,
"banscore" : 0
},
{
"addr" : "50.188.13.41:18872",
"services" : "00000001",
"lastsend" : 1441219008,
"lastrecv" : 1441219008,
"conntime" : 1441210972,
"version" : 60604,
"subver" : "/OrangeCoin:2.0.0/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 288514,
"banscore" : 0

You can see the 1.0.9 is definitely ahead of the 2.0.0's. We need to ban them and get the yearlyblockcount issue straightened out, and is why I suggest we wait for soopy.

[Halofire]

289799. I have to go for a while.