I can't seem to sync, no contacts are found.
Edit: Fix proposed by Mad_Max below did work, thank you!
Topic: remove thread - page 6. (Read 31256 times)
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.
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.
OP has requested thread removal - this coin out of Orbit? 
Nah, they just faked it like the moon landing.
OP has requested thread removal - this coin out of Orbit?
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.
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.
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).
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).
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.
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
and this (official)
Code:
int nHeight = pindexPrev->nHeight+1;
if (nHeight >= NNNNNN & nActualSpacing < 0) nActualSpacing = 0; //Sanity Check on nActualSpacing, corrects negative block values
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.
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.
http://yadi.sk/d/Aj6PZakdFTsbc
Previous version (1.2.1) removed.
remove
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
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
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.
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.
Yes lot of new blocks was orphaned.(almost all)
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!
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.
Yes lot of new blocks was orphaned.(almost all)
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!
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!
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?
With difficulty this low it's almost like I'm the only one mining this... another unintended fork?
Does look like a hard fork - everyone will have to adopt the fix. 
Don't hold much hope, over in the Stablecoin thread there have been about 4 new releases over the past 6 months, some peers are still running the original client!
Actually need 2 exchanges (cryptsy.com and coins-e.com) and block explorer (i know only one working with orbitcoin - https://andarazoroflove.org/explorer/orbitcoin/block_crawler.php) to update they their wallets, and the rest will not have so much choice Don't hold much hope, over in the Stablecoin thread there have been about 4 new releases over the past 6 months, some peers are still running the original client!
I already send tickets/e-mail to admins of exchanges (cryptsy.com and coins-e.com) with description of the current situation on OrbitCoin.
All interested persons can duplicate my requests for the speed up response...
Does anyone know the administrator contacts of the block explorer?
And please crosspost(or just links here) info to:
https://cryptocointalk.com/topic/2736-looks-like-orbitcoin-is-over/
https://cryptocointalk.com/topic/2719-warning-chain-appears-broken-or-under-attack/
My registration on cryptocointalk still not validated/activated after few days
Very tired now so I'm having a quick look and trying to understand the problem. Is it as simple as the time of two adjacent blocks being out of sequence, the more recent one having an older time, resulting in a negative number when calculating the last time period?
So somehow a block which based on timestamp should have been around #411235 ended up in the blockchain at #41228. The next block was the final PoW one.
That's enough to cause the network to get stuck?
I can see the same thing happened to CDC earlier this morning.
Is this a hard fork where EVERYONE will need to update their client in order to mine, or will it be sufficient for the majority of the network to update?
Yes - wrong timestamps of blocks - is a part of conditions to trigger bug. But PoS involved too - of no PoS blocks mined at same time - wrong PoW blocks will be just orphaned and situation selfcorrected after some time (few hours MAX). But with PoS block at same time (and without full check in PoS gen code) wrong PoW blocks are sealed in the blockchain and can not be orphaned by PoW miner (it can be orphaned by other PoS miners but they do not do so as PoS code does not see any problem in such blocks and regard them as valid)Code:
31-Dec-2013 13:56:33 height: 411227 mint: 0.25 difficulty: 0.17286038 flags: proof-of-work
31-Dec-2013 14:56:05 height: 411228 mint: 0.25 difficulty: 0.17353002 flags: proof-of-work
31-Dec-2013 13:58:21 height: 411229 mint: 0.25 difficulty: 0.05879355 flags: proof-of-work
31-Dec-2013 14:07:36 height: 411230 mint: 0 difficulty: 0.00024414 flags: proof-of-stake
31-Dec-2013 14:56:05 height: 411228 mint: 0.25 difficulty: 0.17353002 flags: proof-of-work
31-Dec-2013 13:58:21 height: 411229 mint: 0.25 difficulty: 0.05879355 flags: proof-of-work
31-Dec-2013 14:07:36 height: 411230 mint: 0 difficulty: 0.00024414 flags: proof-of-stake
So somehow a block which based on timestamp should have been around #411235 ended up in the blockchain at #41228. The next block was the final PoW one.
That's enough to cause the network to get stuck?
I can see the same thing happened to CDC earlier this morning.
Is this a hard fork where EVERYONE will need to update their client in order to mine, or will it be sufficient for the majority of the network to update?
About fork. Actually we have 2 options:
fork from 411227 block then only majority of miners(PoS miners mainly) need to update. After miners with updated client build longes chain (compared to stuck one) on all other(not updated) clients all blocks after 411227 will be orphaned and replaced by new chain without invalid blocks automatically. Without any soft updates.
And my first patch was this version - i just BAN (blacklist) block 411228 and rebuild blockchain - PoW mining start normal working from 411227 block.
But later I refused this option - because it creating a large number of orphan PoS blocks (which can include some real important transaction for the last 5-6 days) + this variant need a large number of PoS miners with large amounts of coins in stack to quickly generate at least 400-500 PoS blocks and overtake the current chain + this NOT prevent such bugs again in future.
In second patch i remove block ban and add simple check for negative time spacing. No need to orphan current blockchain, but all will need to update because old clients not accept blocks from new (even if it from longest chain). If not all update clients it will lead to blockchain fork to 2 parallel chains.
So it is some sort of hardfork now...
Does look like a hard fork - everyone will have to adopt the fix. Don't hold much hope, over in the Stablecoin thread there have been about 4 new releases over the past 6 months, some peers are still running the original client!
Don't hold much hope, over in the Stablecoin thread there have been about 4 new releases over the past 6 months, some peers are still running the original client!
ORB THREAD TO REMOVE WTF?
[ANN] Orbitcoin (ORB) Official Release Thread - Scientific POW/POS Adv. Hybrid
[ANN] Orbitcoin (ORB) Official Release Thread - Scientific POW/POS Adv. Hybrid
Very tired now so I'm having a quick look and trying to understand the problem. Is it as simple as the time of two adjacent blocks being out of sequence, the more recent one having an older time, resulting in a negative number when calculating the last time period?
So somehow a block which based on timestamp should have been around #411235 ended up in the blockchain at #41228. The next block was the final PoW one.
That's enough to cause the network to get stuck?
I can see the same thing happened to CDC earlier this morning.
Is this a hard fork where EVERYONE will need to update their client in order to mine, or will it be sufficient for the majority of the network to update?
Code:
31-Dec-2013 13:56:33 height: 411227 mint: 0.25 difficulty: 0.17286038 flags: proof-of-work
31-Dec-2013 14:56:05 height: 411228 mint: 0.25 difficulty: 0.17353002 flags: proof-of-work
31-Dec-2013 13:58:21 height: 411229 mint: 0.25 difficulty: 0.05879355 flags: proof-of-work
31-Dec-2013 14:07:36 height: 411230 mint: 0 difficulty: 0.00024414 flags: proof-of-stake
31-Dec-2013 14:56:05 height: 411228 mint: 0.25 difficulty: 0.17353002 flags: proof-of-work
31-Dec-2013 13:58:21 height: 411229 mint: 0.25 difficulty: 0.05879355 flags: proof-of-work
31-Dec-2013 14:07:36 height: 411230 mint: 0 difficulty: 0.00024414 flags: proof-of-stake
So somehow a block which based on timestamp should have been around #411235 ended up in the blockchain at #41228. The next block was the final PoW one.
That's enough to cause the network to get stuck?
I can see the same thing happened to CDC earlier this morning.
Is this a hard fork where EVERYONE will need to update their client in order to mine, or will it be sufficient for the majority of the network to update?
Will do full github fork later.
But main (only necessary) patch is very simple. You can do it youself:
just open src/main.cpp find this function: unsigned int static GetNextTargetRequired
and add code:
Bacup wallet.dat ofcourse before try.
I make few other minor updates (like protocol and client version info update) - but they all are optional.
411228 - is last normal block before PoW is broken. Initially i think we need fork blockchain from it... But i try start mining from latest PoS block - and it works too.
So no need to orphan last ~300 PoS bloks (it may include some real transactions)
But main (only necessary) patch is very simple. You can do it youself:
just open src/main.cpp find this function: unsigned int static GetNextTargetRequired
and add code:
Quote
int64 nActualSpacing = pindexPrev->GetBlockTime() - pindexPrevPrev->GetBlockTime();
if (nBestHeight >= 411228 && nActualSpacing < 0) nActualSpacing = 0; // patch to prevent negative nActualSpacing
And compile. If you can connect to my node and sync to ~412100 blocks(>19 billion trust score) or more - you do all right if (nBestHeight >= 411228 && nActualSpacing < 0) nActualSpacing = 0; // patch to prevent negative nActualSpacing
Bacup wallet.dat ofcourse before try.
I make few other minor updates (like protocol and client version info update) - but they all are optional.
411228 - is last normal block before PoW is broken. Initially i think we need fork blockchain from it... But i try start mining from latest PoS block - and it works too.
So no need to orphan last ~300 PoS bloks
(it may include some real transactions) Jump to: