remove thread

[almightyruler]

Hmmm. About 10 mins ago there was a -1338 block adjustment (412931 -> 411593) and suddenly difficulty dived from 0.01x to 0.0003x

With difficulty this low it's almost like I'm the only one mining this... another unintended fork?

[Mad_Max]

Yes lot of new blocks was orphaned.(almost all)

Code:

REORGANIZE
REORGANIZE: Disconnect 1354 blocks; c4eacae0919a7b7d9339..0000002aa34a235c528d
REORGANIZE: Connect 16 blocks; c4eacae0919a7b7d9339..fa732229effe372f145a

But NO it is not new fork. It is revert to original blockchain.
It because I am NOT banned old original clients (1.0 and 1.2) for now in my version. We can sync both to old and new clients now(while old can sync to old only and ignore blocks from new). So our entire new blockchain was orphaned by main chain (stuck one - without PoW) because PoS blocks have much MUCH more weight in OrbitCoin. (near x 1 000 000)
So client sync to main PoS chain and start building new chain from it again.

To prevent this happend again and again we need PoS miner with new updated wallets to generate enough own PoS blocks in new blockchain.
I connect my own PoS wallet with ~ 5000 coins, but it still not  enough to overweight old chain.
My wallet produce 15 PoS blocks in new chain today. After old chain accumulated >15 PoS blocks my 15 PoS (+ all PoW >1300 blocks) was orphaned.

So please stop PoW mining at new chain for now - it's a waste of resources at the moment because all PoW mined blocks can be canceled at any time by few PoS blocks.
We need critical mass of PoS miners in new chain first!

[BrewCrewFan]

Yes lot of new blocks was orphaned.(almost all)

Code:

REORGANIZE
REORGANIZE: Disconnect 1354 blocks; c4eacae0919a7b7d9339..0000002aa34a235c528d
REORGANIZE: Connect 16 blocks; c4eacae0919a7b7d9339..fa732229effe372f145a

But NO it is not new fork. It is revert to original blockchain.
It because I am NOT banned old original clients (1.0 and 1.2) for now in my version. We can sync both to old and new clients now(while old can sync to old only and ignore blocks from new). So our entire new blockchain was orphaned by main chain (stuck one - without PoW) because PoS blocks have much MUCH more weight in OrbitCoin. (near x 1 000 000)
So client sync to main PoS chain and start building new chain from it again.

To prevent this happend again and again we need PoS miner with new updated wallets to generate enough own PoS blocks in new blockchain.
I connect my own PoS wallet with ~ 5000 coins, but it still not  enough to overweight old chain.
My wallet produce 15 PoS blocks in new chain today. After old chain accumulated >15 PoS blocks my 15 PoS (+ all PoW >1300 blocks) was orphaned.

So please stop PoW mining at new chain for now - it's a waste of resources at the moment because all PoW mined blocks can be canceled at any time by few PoS blocks.
We need critical mass of PoS miners in new chain first!

That is going to be a tough cookie to get done right there. To many people will still run vs one of the wallet I am sure.

[Mad_Max]

Yeah tough. But who said that overtake hybrid PoW+PoS criptocoin should be easy?
It is tough by design. Even such small and weak as OrbitCoin

Although I think that now to establishment control enough to keep online (with temporarily unlocked wallet if it is encrypted, otherwise PoS generation does not work) about 3-5 wallets updated to new ver with coins (from 5 to 15 days had lain motionless) coming in by the middle-sized transactions to generate sufficient PoS blocks (more than in the current dying blockchain).
So all who whant to try are welcome. Because of  reward for PoS blocks in OrbitCoin set to 0% you have nothing to lose in any case - even if all of your blocks will then be canceled/orphaned in the end. But with PoW mining decide for yourself - if new chain fail the whole chain of spend work/electricity lost.

[Mad_Max]

By the way - original developer (RedMist) made his move.
Seeing that patch like mine really works and solves the problem he stopped talking about the mythical attacks on its network and released its official version of the same patch (client ver 1.3.0).
But to avoid version conflicts decide delay its activation to block >417000.
That at the current rate will take a few months (since blocks are added only through PoS - and PoW is still not working without activation of the patch).

And i place own version with with immediate patch effect.
For this time i issued it according to all rules in the form of source code as fork from original code on GitHub:
https://github.com/MaxMaximus/Orbitcoin

[DJTrey]

remove

[Mad_Max]

Forget to add new Windows Binary (source form https://github.com/MaxMaximus/Orbitcoin compiled with: MinGW 4.8.1 + Qt 4.8.5. Libs: Berkeley DB 4.8.30, boost_1_53, miniupnpc-1.6, openssl-1.0.1):
http://yadi.sk/d/Aj6PZakdFTsbc

Previous version (1.2.1) removed.

[testbug]

Forget to add new Windows Binary (source form https://github.com/MaxMaximus/Orbitcoin compiled with: MinGW 4.8.1 + Qt 4.8.5. Libs: Berkeley DB 4.8.30, boost_1_53, miniupnpc-1.6, openssl-1.0.1):
http://yadi.sk/d/Aj6PZakdFTsbc

Previous version (1.2.1) removed.

Thx for your work Mad_Max, but i still cant solo mine...
"New" Orbitcoin-QT is still creating a 99.99% CPU state.

Is this normal at this time, the chaing getting broken?

Greetings.

[Mad_Max]

Thx for your work Mad_Max, but i still cant solo mine...
"New" Orbitcoin-QT is still creating a 99.99% CPU state.

Is this normal at this time, the chaing getting broken?

Greetings.

Hi
Stuck at 411665 (or 411666) block?
Lol funny sitiation. My versions of fix (1.2.1) works and fix problem with PoW mining - i am try it myself + few other ppl - all work great - we me mine ~1300 block on. But was orphaned by PoS blocks from main (original) chain. Later more (~500-700) PoW blocks and so on.
But later original developer (RedMist) do its own version of patch (with delay until block #417000).
So later i make new version as fork from original - just replace # of blocks from distant future to close moment (from block #411650).
And seem what official patch NOT fix situation! It works only to one next "buggy" block in blockchain and PoW fails again.
Buggy block was #411665 (negative time spacing to prev #411664 again) - and PoW mining died again after this block. PoS still working (#411666 was my test PoS block).

So if we stick to official client we just waste one or few month of time (before #417000) + work of people that will update the software to version 1.3 and shortly after #417000 network will stuck again and return to current situation.
I do not know whether it was an accidental mistake or is it all a provocation initially (eg to undermine confidence in the currency and buy it cheaper, then to release a real patch and earn a Big on growing rate).

I will look/test why original patch not solve problem later...
If anybody know good coding and criptoclient can look at code
Why this fix (my)

Code:

if (nBestHeight >= NNNNNN && nActualSpacing < 0) nActualSpacing = 0; // patch to prevent negative nActualSpacing

work (resume PoW mining)
and this (official)

Code:

 int nHeight = pindexPrev->nHeight+1;

 if (nHeight >= NNNNNN & nActualSpacing < 0) nActualSpacing = 0;  //Sanity Check on nActualSpacing, corrects negative block values

Not fix?

NNNNNN - # of block there patch activates.
In my quickie observations offical fix do pevent making buggy blocks by itself BUT if such blocks sent by other client (by older version or  especially my some "pest") network fails again.

[Mad_Max]

Got some free time and performed a detailed analysis and debugging code(requiring another full recompile of QT and all related libraries - about 10 hours only for full recompilation) associated with the patch.
Indeed - despite the fact that at first glance my patch and official patch do the same thing really big difference.
In the official version PoW Mining does not work at all: not only for now, but will NOT work after a few months (after the block 417000) too!.
So today or tomorrow I will once again update my version(it will be v.1.3.2) and go back to the original version of my PoW patch (as was in version 1.2.1).

[Mad_Max]

Finally new version(1.3.2) of OrbitCoin client with working patch to fix PoW mining.
Source: https://github.com/MaxMaximus/Orbitcoin

Windows binaries coming soon.

Fix will activates from block 412300.
At time at publishing new version at GitHub current block was 412109. Now (at writing this post ~5 hours later) current last block is 412131. So patch will activate tomorrow or in the next 2 days judging by the current rate of PoS blocks generation.
So  enough time to download the source, check it, compile and synchronize with the current full blockchain without rushing before starting.

After block #412300 1.3.2 client will activate PoW mining but still continue syncing to current (buggy and PoS only) blockchain until one of the following conditions(what happen sooner):
1. Sufficient number of active miners miners (primarily PoS miners have value) switch to using the new version and be able to build longer (and with great PoS weight) chain compared to the old and be able to support it ahead of the old
2. In the old blockchain will appears next new "bad" block(incorrect blocks such as that are causing disruptions to PoW Mining now), which will be rejected by new client (because in it appropriate bug was fixed) and synchronize with the old chain will cease from this block.

[Oldminer]

OP has requested thread removal - this coin out of Orbit? 

[Cutiecats]

OP has requested thread removal - this coin out of Orbit? 

Nah, they just faked it like the moon landing.

[Mad_Max]

And now v.1.3.2 binaries for Windows: Orbitcoin_1.3.2

By the way - if somebody start downloading blockchain from scratch (genesis block) and got stuck at some block (for example # 411229) - just restart program and blocks continue downloading.
These are exactly the same "bad" blocks due to which PoW mining fail. The patch corrects error but it can not do anything with the blocks already included in the blockchain before.

[MathiasW]

I can't seem to sync, no contacts are found.

Edit: Fix proposed by Mad_Max below did work, thank you!

[Mad_Max]

MathiasW
if it first installation (or new in separate folder with separate database folder) try to add few first nodes manual
In data folder create (or edit if already existed) Orbitcoin.conf
and add some nodes:
addnode=203.45.89.214
addnode=95.27.219.139
addnode=178.27.212.144

After it restart client.

Seems orbitcoin has other bugs too and receiving the initial list if nodes after first/clean installation (when a local nodes list in peers.dat file is empty) through the IRC channel not working properly...

[testbug]

Hi,

thank you for another Update Mad_Max.

I downloaded it and tryed to mine solo, but it didnt seem to work.
Should it be working now again or do we have to wait for a later auto generated block?

greetings.

[Mad_Max]

Hi

As I wrote few posts above:

Fix will activates from block 412300.
At time at publishing new version at GitHub current block was 412109. Now (at writing this post ~5 hours later) current last block is 412131. So patch will activate tomorrow or in the next 2 days judging by the current rate of PoS blocks generation.
So  enough time to download the source, check it, compile and synchronize with the current full blockchain without rushing before starting.
.....

Right now we are at block # 412255.
So patch is not activated yet, need 45 more PoS blocks in original blockchain before PoW in new client kicks in and start "who have a longer dick chain?" game. 

No any manual intervention is longer required - if the wallet is already synchronized with the mother-chain (to block number # >=412255) changes will apply automatically when chain reach block # 412300.

[testbug]

Ah, ok. Thanks for answering such fast

But i have the feeling, that blocks are faster generated right now compared with two days ago.

Greetings.

[almightyruler]

New hard fork point passed, mining fine, then -193 block correction and back to the pre-fork difficulty of 0.05879355...

Does this mean that older PoS clients are overriding the new hard fork?

edit: difficulty back down to 0.00026726... I guess until the next network reversal