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

[soopy452000]

Got past 262799 with the bootstrap, but with the previous version (2.0 did not get past it)

Now trying to switch to 2.0... It's getting stuck :/

Also the July fix seems to have been reverted in 2.0 with a "version bump" comment, alongside actual version bump commits, could that be the bug?

yes it was reverted and reevaluated and re applied to avoid any further issues.

[Halofire]

At least I can finally relax a little bit, since soopy is now aware of everything.

Thanks for everyone's help today. We will get through this, there's no question there.

[raven7886]

At least I can finally relax a little bit, since soopy is now aware of everything.

Thanks for everyone's help today. We will get through this, there's no question there.

Indeed, Such an AWESOME TEAM! Keep up the hard work, Halo have a beer!

[Halofire]

I do like my beer.   

[fairglu]

I have been getting a few blocks on v2 for the last hours, are these on the right fork?
(this includes blocks mined by rich list list #12 and #9, so if it's a fork, they would be on it as well)

Appreciating your thoughts on risks , but this was actually provided by the development team and if you cannot trust the development team , I do not know who you will.

Technically speaking, the file is not provided by the team, but by a link to a mediafire url.
The trust issue is not about the dev team, but about whether the data you get may or may not actually be from the dev team

The github source code is trustable, as it is hosted on an https server, with a well identified url and a list of recent changes/commit and git's own tamper-proof hashing, so any hijacking attempt would not go unnoticed, but the mediafire link on the other hand is "meaningless", http, and the data itself hosted by a 3rd party. This is vulnerable to several vectors of attack.

When replacing the db, the wallet will only check the last 2500 blocks, while when using a bootstrap.dat, the wallet will check the whole blockchain, making hijacking attempts as hard as a full-scale 51% attack, so it's okay to host the bootstrap.dat anywhere.

[soopy452000]

I have been getting a few blocks on v2 for the last hours, are these on the right fork?
(this includes blocks mined by rich list list #12 and #9, so if it's a fork, they would be on it as well)

Appreciating your thoughts on risks , but this was actually provided by the development team and if you cannot trust the development team , I do not know who you will.

Technically speaking, the file is not provided by the team, but by a link to a mediafire url.
The trust issue is not about the dev team, but about whether the data you get may or may not actually be from the dev team

The github source code is trustable, as it is hosted on an https server, with a well identified url and a list of recent changes/commit and git's own tamper-proof hashing, so any hijacking attempt would not go unnoticed, but the mediafire link on the other hand is "meaningless", http, and the data itself hosted by a 3rd party. This is vulnerable to several vectors of attack.

When replacing the db, the wallet will only check the last 2500 blocks, while when using a bootstrap.dat, the wallet will check the whole blockchain, making hijacking attempts as hard as a full-scale 51% attack, so it's okay to host the bootstrap.dat anywhere.

Oh Okay mate , got you there the trust issue was with the hosting provider. I get you now. Believe it was a communication mishap. Appologies mate.
Enjoy a beer shall we?

Warm Regards,
~SoopY~

[raven7886]

We are officially a global network: 11 Countries across the globe. Any news on yesterdays events? Any fixes? I noticed the chain over at chainz hasn't moved for ten hours... I am at work currently so I cannot check my node unfortunately.

Cheers!

-Raven

PS Halo I hope you didn't over indulge the beer, Haha! Good Morning Everyone!

[GREEDYJOHN]

My wallet is not staking, but last recorded block is 288443

[TimC]

We are officially a global network: 11 Countries across the globe. Any news on yesterdays events? Any fixes? I noticed the chain over at chainz hasn't moved for ten hours... I am at work currently so I cannot check my node unfortunately.

The chain just moved some and my node is still the same block height as chainz.cryptoid.info/oc/ which is block 288476. Difficulty of 0.0613  and going up.

[Halofire]

I have been getting a few blocks on v2 for the last hours, are these on the right fork?
(this includes blocks mined by rich list list #12 and #9, so if it's a fork, they would be on it as well)

Appreciating your thoughts on risks , but this was actually provided by the development team and if you cannot trust the development team , I do not know who you will.

Technically speaking, the file is not provided by the team, but by a link to a mediafire url.
The trust issue is not about the dev team, but about whether the data you get may or may not actually be from the dev team

The github source code is trustable, as it is hosted on an https server, with a well identified url and a list of recent changes/commit and git's own tamper-proof hashing, so any hijacking attempt would not go unnoticed, but the mediafire link on the other hand is "meaningless", http, and the data itself hosted by a 3rd party. This is vulnerable to several vectors of attack.

When replacing the db, the wallet will only check the last 2500 blocks, while when using a bootstrap.dat, the wallet will check the whole blockchain, making hijacking attempts as hard as a full-scale 51% attack, so it's okay to host the bootstrap.dat anywhere.

The blockchain download will be coming off the website once we sort out our issues, bootstraps will take the place. I hated having to put the full db up because it isn't how crypto was meant to flow, but it's what worked at the time. We were dev-less, and I had to do what I had to do to keep the chain alive in my position. I've stated I attempted to make bootstraps in the past, they didn't work out. We have bootstrap capabilities now, so downloading those from mediafire shouldn't be an issue as you stated.

[Halofire]

We are officially a global network: 11 Countries across the globe. Any news on yesterdays events? Any fixes? I noticed the chain over at chainz hasn't moved for ten hours... I am at work currently so I cannot check my node unfortunately.

Cheers!

-Raven

PS Halo I hope you didn't over indulge the beer, Haha! Good Morning Everyone!

Nope, I had a handle on things, mainly my stein. HAHA!
Nah, I don't own a stein. I'm not that sophisticated. 

If I'm not mistaken, chainz used 1.0.9 to get the chain synced, then switched to 2.0.0.

As far as news,
Soopy is aware of all that transpired and he has a idea for a fix, he's possibly encountered a similar problem in the past.
He agrees that the MINT fix works and that it's discrepancies in the yearlyblockcount and the fork that's throwing everything off.

[raven7886]

I have been getting a few blocks on v2 for the last hours, are these on the right fork?
(this includes blocks mined by rich list list #12 and #9, so if it's a fork, they would be on it as well)

Appreciating your thoughts on risks , but this was actually provided by the development team and if you cannot trust the development team , I do not know who you will.

Technically speaking, the file is not provided by the team, but by a link to a mediafire url.
The trust issue is not about the dev team, but about whether the data you get may or may not actually be from the dev team

The github source code is trustable, as it is hosted on an https server, with a well identified url and a list of recent changes/commit and git's own tamper-proof hashing, so any hijacking attempt would not go unnoticed, but the mediafire link on the other hand is "meaningless", http, and the data itself hosted by a 3rd party. This is vulnerable to several vectors of attack.

When replacing the db, the wallet will only check the last 2500 blocks, while when using a bootstrap.dat, the wallet will check the whole blockchain, making hijacking attempts as hard as a full-scale 51% attack, so it's okay to host the bootstrap.dat anywhere.

The blockchain download will be coming off the website once we sort out our issues, bootstraps will take the place. I hated having to put the full db up because it isn't how crypto was meant to flow, but it's what worked at the time. We were dev-less, and I had to do what I had to do to keep the chain alive in my position. I've stated I attempted to make bootstraps in the past, they didn't work out. We have bootstrap capabilities now, so downloading those from mediafire shouldn't be an issue as you stated.

So that obviously helped yesterday with the bootstrap command, Cheers!

[Halofire]

I have been getting a few blocks on v2 for the last hours, are these on the right fork?
(this includes blocks mined by rich list list #12 and #9, so if it's a fork, they would be on it as well)

Appreciating your thoughts on risks , but this was actually provided by the development team and if you cannot trust the development team , I do not know who you will.

Technically speaking, the file is not provided by the team, but by a link to a mediafire url.
The trust issue is not about the dev team, but about whether the data you get may or may not actually be from the dev team

The github source code is trustable, as it is hosted on an https server, with a well identified url and a list of recent changes/commit and git's own tamper-proof hashing, so any hijacking attempt would not go unnoticed, but the mediafire link on the other hand is "meaningless", http, and the data itself hosted by a 3rd party. This is vulnerable to several vectors of attack.

When replacing the db, the wallet will only check the last 2500 blocks, while when using a bootstrap.dat, the wallet will check the whole blockchain, making hijacking attempts as hard as a full-scale 51% attack, so it's okay to host the bootstrap.dat anywhere.

The blockchain download will be coming off the website once we sort out our issues, bootstraps will take the place. I hated having to put the full db up because it isn't how crypto was meant to flow, but it's what worked at the time. We were dev-less, and I had to do what I had to do to keep the chain alive in my position. I've stated I attempted to make bootstraps in the past, they didn't work out. We have bootstrap capabilities now, so downloading those from mediafire shouldn't be an issue as you stated.

So that obviously helped yesterday with the bootstrap command, Cheers!

Oh of course, it's a better way to get the blockchain more naturally.

[Halofire]

By the way, I'm doing sync testing for soopy. I cannot provide any current block stats.

[raven7886]

By the way, I'm doing sync testing for soopy. I cannot provide any current block stats.

[OrangecoinTeam]

OP updated to include:
- a link to BTCgarden's forum under OC services
- "meet the team" was updated for ravens OP status at said forum
- Chainz nodes list link added under orangecoin.conf

We are looking forward to getting juicier!

[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

[raven7886]

Checking in for block: 288513 generated an hour ago...

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

I Had this issue. I stopped the wallet and restarted a few times. ALSO MAKE SURE TO ONLY USE OP THREAD NODES! I was using Chainz node list there's still spoofed chains within the list meaning 1.0.9 versions thinking they're on the 2.0 chain thus causes confusion to the client.

Here's my CONF if you want to replicate the settings:

EDIT: COPIED PASTED TEXT FROM CLIP ON PHONE! FOR INVESTIGATION!
This is my CONF:
port=18872
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

ALSO: HOW IS THIS PERSON ABLE TO CONNECT AND STILL 1.0.9! Details:
addr" : "93.123.163.96:18872",
"services" : "00000001",
"lastsend" : 1441143202,
"lastrecv" : 1441144269,
"conntime" : 1441119184,
"version" : 60604,
"subver" : "/OrangeCoin:1.0.9/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 289031,
"banscore" : 0

Not even on my list! I am going to give them a banscore! If they do not update! But inbound is false so we shouldn't have anything coming from him... If I understand correctly about inbounds true or false. Pleae let me know if you need ANY HELP. I also have a chain downloaded\bootstrap for 286K of blocks. Again please let me know, send me a PM or twat @rfarrow7886

Cheers!

-Raven

[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 ?

[raven7886]

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)