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

[Halofire]

I've tried copying that file before in the past and didn't work. Maybe my wallet was on when I copied it? Idk. I'm working on it, it's syncing now from scratch with the copied file. Hope this works for them.

That command work? Or is that what you mean, testing it?

Testing was meant as in successfully syncing or starting to sync. The bootstrap actually helps sync faster, probably due the wallet to knowing what blocks to sync to. It still syncs for 500 blocks at a clip, but it doesn't hang up as long.

The wallet isn't fully synced but it's going and is currently at 58500. Since it IS working, I gave the bootstrap to richie and fairglu in a PM, if they wanted to get a jump on things. It's posted on the website, but until they confirm it fully works for them as this is my first bootstrap, I'm not releasing the link yet. I took down the latest blockchain download as well.

OK ok, Secco @BTCGarden said it downloads very quickly but then stops. So.. Would it still be a bootstrap issue? Also we have noticed out of the "good IPs" 93.123.163.96:18872 is on OrangeCoin:1.0.9........
UPDATE YOUR WALLET!!!!!

Can we Ban this node temporarily in the conf?

Also I just had him to connect to my node only he's getting 4 connections.... Weird. But these IPs are connected: 50.188.13.41:18872 / 149.202.102.73:18872 / 75.130.163.51:18872 / 93.123.163.96:18872

Edit: Maybe i should take down my node? since these weird connections are there? Consensus?

We need all clients to get updated. The longer they don't update, the longer we remain forked. Wonder if soopy if puts in a version ban, if that would work?

There's not much more I can do except try to get everyone on 2.0.0 and on the same nodes on the moving chain.

Leave your node up for now.

I thought we had version ban implemented..... from 1.0.9

I think it has to be changed with every wallet update. Not 100% sure. Seems like it, when reading 1.0.9 git changes. I'll PM soopy.

[1713508022]

1713508022

[1713508022]

1713508022

[Halofire]

I have confirmation chainz is using the bootstrap and is syncing.

[Halofire]

I'll be going out for an hour or so then I'll come check up on the situation. Then I may go out again depending on how things are at. Hold down the fort.

288350

[raven7886]

288351

[GREEDYJOHN]

Orangecoin is getting global attention

[raven7886]

288357? correct

[Halofire]

288357? correct

sure you're looking at the right number? Thats the estimated total (edit: in mine).

I have 288362.

[raven7886]

288357? correct

sure you're looking at the right number? Thats the estimated total (edit: in mine).

I have 288362.

288362

[fairglu]

I have confirmation chainz is using the bootstrap and is syncing.

Alas got stuck at 262799 again... :/

[Halofire]

I'm still at 177000, syncing. 

[raven7886]

I'm still at 177000, syncing.  

I used the 286kzip
Need a link to my drop box?

[Halofire]

I'm still at 177000, syncing.  

I used the 285kzip
Need a link to my drop box?

No, I'm ok for now. I was informed I had to rename the file to bootstrap.dat. I had to restart the syncing. yay.

[fairglu]

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?

[raven7886]

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?

So Halo, back to our version block conversation. 

Fairglu, I had a feeling there was something wrong, I could close it, open it and the wallet would sync but, then program not responding constantly once I got green checkmark...

[Halofire]

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?

I explained to you in the PM's what that was all about.

1.0.8 and prior versions had a bug from cloned MINT code that wouldn't allow the chain to advance past 262800. OC is a MINT clone.
1.0.9 attempted to fix this by extending the YearlyBlockcount in our code by a factor of 4x, thus extending 20% PoS 4 years and delaying the problem.
2.0.0 implemented the MINT git fix for the same problem. Everything was reverted back to pre-1.0.9 code, except the fix I found. This included the Yearlyblockcount which we were already past at that point on the 2.0.0 fork which 1.0.9 clients were able to connect to with their own version of the stuck chain fix and different PoS payout. We have two versions of clients running on the same blockchain with 2 different PoS payouts. I think this is the problem. I've been waiting for soopy to come online. I've already bombarded him with PM's from earlier in the day. So I figured I wait and gather more info before messaging him again.

So reverting back to 1.0.9 fixes the problems we are having now in that client, but for only for 1.0.9 and that chain keeps on plugging along because not everyone is updated to 2.0.0. The Mint fix works, because the clients 2.0.0 shouldn't sync or stake at all on either chain past 262800 if this weren't true, since the code reverted back to original besides the Mint fix.

[raven7886]

Stuck on 272699 from bootstrap. My head hurts!
Edit: it jumped 100

[soopy452000]

There are no manipulations. We have had to provide a blockchain due to slow syncing for some users.

Not accusing anyone, just pointing that a mediafire download of a raw db is not trustable in several ways (it's vulnerable even to simple network corruption)

The bootstrap.dat is a pre-download of the chain on the other hand, but the client will still validate all the blocks (which is why importing a bootstrap is slow), so it's okay to get one from an untrusted source.

Hi mate,

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.

Warm Regards,
~SoopY~

[soopy452000]

Btw guys I m going through all your messages on the thread and the one's and on pm.

How are we holding?

I will work on the issues at hand.

Warm Regards,
~SoopY~

[raven7886]

Btw guys I m going through all your messages on the thread and the one's and on pm.

How are we holding?

I will work on the issues at hand.

Warm Regards,
~SoopY~

Hello Soop!

We're having:
Competing chains due to same protocol different clients/checkpoints. I sent halo some debug clips from various scenarios, building bootstrap, syncing from scratch, copying saved chain. I had a scare with the runtime and constantly terminating , I fixed it... It was an error in the config file. Dummy me.

Sorry for the bombardment earlier, just trying to obtain as much info as possible.

Cheers!

-Raven

[Halofire]

Yay soopy! Just in time for the last PM I sent ya. Yeah, apologies for bombardment.