Topic: [ANN][OC] Orangecoin ★★ POS ★★ Anon Transactions ★★ Masternodes (Read 209477 times)

And the moment you've all been waiting for....


Please move all further discussion to the following thread: https://bitcointalksearch.org/topic/annoc-orangecoin-v204-pos-anon-masternode-whitepaper-get-juiced-1166201
This thread cannot be locked as is, we cannot guarantee a reply here. We will not be monitoring this thread.

Word to the wise: I'd wait to move or buy or sell any coins until we are all updated to 2.0.0. You may encounter complications otherwise.

Also, cryptoid is resyncing. You may experience interruptions in their service.

A few 1.0.9's are on your list.
Also you have peers with non-OC ports.

Edit: I too now have 1.0.9 clients in my peers.

This is my peerinfo:


21:30:23

getpeerinfo


21:30:23

[
{
"addr" : "92.19.22.234:18872",
"services" : "00000001",
"lastsend" : 1440901801,
"lastrecv" : 1440901801,
"conntime" : 1440878087,
"version" : 60604,
"subver" : "/OrangeCoin:2.0.0/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 287132,
"banscore" : 0
},
{
"addr" : "5.196.109.69:40886",
"services" : "00000001",
"lastsend" : 1440901805,
"lastrecv" : 1440901805,
"conntime" : 1440878238,
"version" : 60604,
"subver" : "/OrangeCoin:2.0.0/",
"inbound" : true,
"releasetime" : 0,
"startingheight" : 11000,
"banscore" : 0
},
{
"addr" : "167.114.27.242:47676",
"services" : "00000001",
"lastsend" : 1440901802,
"lastrecv" : 1440901699,
"conntime" : 1440878239,
"version" : 60604,
"subver" : "/OrangeCoin:2.0.0/",
"inbound" : true,
"releasetime" : 0,
"startingheight" : 10000,
"banscore" : 0
},
{
"addr" : "69.204.247.90:55278",
"services" : "00000001",
"lastsend" : 1440901802,
"lastrecv" : 1440901802,
"conntime" : 1440878470,
"version" : 60604,
"subver" : "/OrangeCoin:2.0.0/",
"inbound" : true,
"releasetime" : 0,
"startingheight" : 287137,
"banscore" : 0
},
{
"addr" : "104.179.213.26:63091",
"services" : "00000001",
"lastsend" : 1440901802,
"lastrecv" : 1440901802,
"conntime" : 1440879671,
"version" : 60604,
"subver" : "/OrangeCoin:1.0.9/",
"inbound" : true,
"releasetime" : 0,
"startingheight" : 287154,
"banscore" : 0
},
{
"addr" : "93.123.163.96:18872",
"services" : "00000001",
"lastsend" : 1440901802,
"lastrecv" : 1440901802,
"conntime" : 1440886818,
"version" : 60604,
"subver" : "/OrangeCoin:1.0.9/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 287210,
"banscore" : 0
},
{
"addr" : "75.130.163.51:53834",
"services" : "00000001",
"lastsend" : 1440901802,
"lastrecv" : 1440901801,
"conntime" : 1440887339,
"version" : 60604,
"subver" : "/OrangeCoin:2.0.0/",
"inbound" : true,
"releasetime" : 0,
"startingheight" : 287190,
"banscore" : 0
},
{
"addr" : "69.113.74.217:58373",
"services" : "00000001",
"lastsend" : 1440901802,
"lastrecv" : 1440901802,
"conntime" : 1440892782,
"version" : 60604,
"subver" : "/OrangeCoin:1.0.9/",
"inbound" : true,
"releasetime" : 0,
"startingheight" : 287198,
"banscore" : 0
},
{
"addr" : "69.204.247.90:50374",
"services" : "00000001",
"lastsend" : 1440901802,
"lastrecv" : 1440901802,
"conntime" : 1440895937,
"version" : 60604,
"subver" : "/OrangeCoin:2.0.0/",
"inbound" : true,
"releasetime" : 0,
"startingheight" : 287259,
"banscore" : 0
},
{
"addr" : "151.230.229.66:18872",
"services" : "00000001",
"lastsend" : 1440901802,
"lastrecv" : 1440901802,
"conntime" : 1440897161,
"version" : 60604,
"subver" : "/OrangeCoin:1.0.9/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 287289,
"banscore" : 0
},
{
"addr" : "149.202.102.73:51532",
"services" : "00000001",
"lastsend" : 1440901819,
"lastrecv" : 1440901819,
"conntime" : 1440900894,
"version" : 60604,
"subver" : "/OrangeCoin:2.0.0/",
"inbound" : true,
"releasetime" : 0,
"startingheight" : 1208,
"banscore" : 0
}
]

Glad to see me on that list.

I retract. We have 4 active 2.0.0 connections on the advancing chain, and those on the cryptoid node list and network info are on the wrong 2.0 fork. What threw me off was the getpeerinfo, one of the nodes converted to the chain we are on and it's still listed in the "nodes seen in the last 24 hours" node list on the website and in getpeerinfo.

Good nodes:
75.130.163.51:18872
92.19.22.234:18872
50.188.13.41:18872
149.202.102.73:18872

287299 current block

I tweeted to cryptoid to update the explorer. Offered them nodes if they need them.

7 more clients need to update. Grr.....

Good thinking.
Careful not to get in trouble for flood messages of spam. We need you here buddy.  

I just sent PMs to many old members, dating back to late 2014, concerning our recent update. We hope to see this thread more active soon.

type getpeerinfo, how many are still on 1.0.9?

287197.

I am using my conf and I have 11 connections.

Get updated, people!!!!
We are at 43% on the 2.0.0 chain. 6 connections of 14. https://chainz.cryptoid.info/oc/#!network

Update: Now we have 57.1%. Great job guys.

Lmao, and that's the cliff notes version.

I think we should rebrand eventually, but using the OC logo we have now. Kind of like this:



'Effing' pokemon.... but it shows the idea.

Orange: sun, sundrop, orange stars

OC, not to the moon, but to the stars!!

and you know what they say about orange stars?? Just right for life....

https://www.newscientist.com/article/dn17084-orange-stars-are-just-right-for-life/

YOU HAVE ENOUGH FACTUAL EVIDENCE TO CREATE A WIKIPEDIA PAGE  

Thanks, John. I try my damnedest.

This is always best, and I prefer if people try to sync naturally. But too many people have problems syncing.

I tried DL'ing the chain from scratch last night when I noticed the dev fund was on it's own fork, but it got stuck after block 10000 again and stayed like that for a half hour. So I DL'ed the 265k and it wouldn't move past the last block in the DL, for another half hour or so, at which time I gave up and made the new DL. I was running on fumes and needed to get my wallets to sync to each other before I signed off.



No, as it was, the 2.0.0 fix was stressful enough for both soopy and myself. Long days, late nights, and even longer mornings.   
I didn't even think about this. Sorry Raven. Next time, bud!

I like ORANGECOIN, even the LOGO is perfect

The ORANGE is circular and equal, it looks like the SUN  

GET JUICED = GET ORANGE   

You are a good representative of ORANGECOIN.

Alright. Here's the lowdown about 2.0.0:

About 1 month ago, our blockchain got stuck at block #262799. Soopy pushed a fix through to get the chain moving again, but his fix only delayed the "stuck chain" problem for 3 more years (buying us time), and as a result, the network still thought we were in Year 1 for PoS Payout purposes. One thing we all need to know about OC code (or most any pure PoS code) is "one year" does not necessarily mean one calculated year of blocks (as a number in the code) will equal one calendar year of 365 days. They should equal based on math estimations, but the actual realized time can and will be different. One full "block count year" lasted in OC until July of 2015 (block 262800), one full calendar year from launch was back in April, and one full year from PoS starting was back in May. Since August 24th, soopy and I have been working on this via PM's, but this delayed the OP due to PoS specs changing on the OP. I want to be right the first time with the new thread, no kinks or problems for a little bit once the new OP is released --- securing new investors seeing solid code and solid teamwork. This was an old OC code problem, let's leave it in the old thread.

Anyway, soopy was sick and/or busy during the time I was figuring out the dev fund's staking for the PoS %, and I had alerted him to the problem once I confirmed it. I located the fix that was incorporated into OC 2.0.0, located in MINT's git. The MINT fix was created in Dec of 2014, and OCdev was long gone by then. For those that didn't know, OC is a MINT clone and MINT had the same problem at their "1 year of blocks". Soopy reversed his 1.0.9 fix and implemented the 2.0.0 fix.

The way I found out about this was via accounting the dev fund, we were still getting 20% PoS in all of the stakes and that schedule would have exhausted the minting schedule after 17 years (4 years total in each phase except the 2.5% phase). Everytime the fund staked, the fund increased by a total of 1800 OC and if we were into the second year of OC (10% PoS) the stake total should be ~900 now, so it wasn't hard to figure out. I did the math, and confirmed. I noticed the 1800OC total for the first stake cycle after soopy's release, but I allowed another stake cycle to be 100% sure -- in case of how CoinAges affected the payout, IF they affected it at all.

So why does this require a hard fork? Because it is correcting the PoS payout from here on out. 20% was extended for ~3 months more than the calculated estimate. Any tx's before the last checkpoint (block 286723) will remain permanent. We keep the coins we have already staked at 20%, but from here on out, it should be at 10%. I won't know the PoS % phase we are in until the dev fund stakes. I can't use my personal wallet's tx's unless I move the coins (I'm not moving them, and I'm not trying to play "accounting" with 100's of tx's). Code works fine, so we'll wait until the dev fund stakes in 10 days or so to check.

2.0.0 added two checkpoints as well, instead of one.

BIG, BIGGER, SUPER BIG!!!! THANK YOU TO SOOPY.

GET JUICED.