I'm not going to publish all of my steps for now...

About help. These steps can be taken by anyone wanting to help (if someone do not know how perform one of the points - just skip it):
- install and use my version of client if you have not already done (it is 1.3.2, do not use any of my previous version because they are not compatible not with the my current chain not with official one. I deleted the online access to all prev versions, but someone could still have a local copy...) my recommendation also keep a backup of the old wallet.dat (used with the official version) and start using new empty wallet with the new client -  this will help prevent mixing of "old" and "new" coins and easier return back to the official version if you want to roll back later

- keep client running online while your computer is on

- open network port for incoming connections (port = 15298) if you use any firewall software and add port forwarding rule to computer where client is running if use any home routers (split one Internet connection for few computer / other devices). this help improve connectivity of network and avoid problem with sync - number of new clients running 24/7 with open ports is still low for good reliable connectivity

- post ticket/e-mail to administration of exchanges with request on own behalf that you also want to use new client/chain on exchange instead of the old official. I have already sent such the request to both exchanges where ORB traded (cryptsy.com and coins-e.com) long ago. But i need to be supported by other users to show there they want to use at exchange my updated client instead of the broken official too, and it is not just only my wish.
So send a message (via tickets or email) with such a request on own behalf. You can refer to my ticket #62004 on cryptsy (where I gave a detailed account of the situation to administration) or to this thread in you message to shorten your request

- try to mine some coins as option (not really needed). no need to throw in large hashing power - pointing just one GPU to ORB is enough. And difficulty is still low so you can mine solo without a pool even with one average GPU

I no need any other help for now (except that only make more hours in the day but I doubt that someone can help with this   )

High risk / high gain is only one of the options to choose, other option is low risk (almost zero) / low gain

- if somebody mine it (or buy it as i plan to do) and just wait than the whole situation over - he  choose "high risk / high gain" path - it is a high risk that at the end his coins are worth nothing, but if successful, will receive many times much more than put in it (money or hashing power)

- if somebody sell coins to me - he gets low (but fixed guaranteed) price right now without waiting and without risk. but loses the chance of winning big with the rejection of the risk

So I offer the choice. Before my offer only "high risk / high gain" variant was possible which not very popular among miners (but common for trader/investors)

Yeah, you right.

But we can remedy last situation(never traded) a bit.  

If anyone wants to sell the coins mined in my version (including those who complained on CryptoCoinTalk about that I "cheated" them by touting to my version where they mined some coins, but can not sell on the exchanges - though I warned about this situation from the beginning) can sell NEW coins to me directly.
Paying a little (compared to the official ORB rate on the exchange) but these coins are now very easy to get! (as mining difficulty is low - right now while i am writing this post only ~500 or 0.0076)
My price now is 2 USD (or equivalent in LTC) per 100 new ORB coins
I can pay both in dollars and krypto.
Not sure what the best payment system for Fiat? May be PayPal? I also use OKPAY / QIWI / Webmoney if anyone want them.

If someone want offer more(higher price) - welcome, just post offer here

note:
I will accept only new coins (created after fork), please do not try to send me old coins from old chain - remember in cryptocoins world all transactions and coins history is public (stored in blockchain and not encrypted) so i can easily track back which coins you send me

And think carefully before making a decision
- if my fork win (will be adopted by the majority of users and exchanges in the end), these coins will cost many times more (probably even tens times more). the probability is not high, but it is possible and i will do my best in this goal
- on the other hand if it does not - they will cost nothing at all(zero).
This is a "high risk / high gain" scenario. So the decision is yours.

There are no "right chain" now any more.
We have 2 main chain (actually 3 already)
- broken the official (a developer tried to fix it in 1.3.0 but once again screwed up as I predicted). But it in use by exchanges so called "official" and about half or even more users still use this ver
- original old official(broken too) chain - formed by all users who still not upgrade(not to my ver 1.3.2 not to latest official 1.3.0) and still use any of old versions (1.0, 1.1, 1.2)
- my fixed chain which up and running about 2 weeks. But it is not used by exchanges so you can not trade with new mined coins on them (but can p2p trade of course)

1st and 2nd still have no PoW working and now around 419.000-420.000 blocks.
2nd chain is definitely dying now. and 1st and 3rd is in competition for to become the main

My chain now at this position (456.906 blocks) because running both PoW + PoS:

New warning
Users with IP  68.195.138.61 and 76.95.191.10 seems you need redownload blockchain - your client can not sync properly.

And i thinks  now understand  where clients with the wrong chain (not official and not mine) are coming from - what was described in these posts:
https://bitcointalk.org/index.php?topic=265555.msg4529236#msg4529236
https://bitcointalk.org/index.php?topic=265555.msg4539010#msg4539010
https://bitcointalk.org/index.php?topic=265555.msg4539254#msg4539254

Seems it is not some of self isolated clients due connectivity problems as i thought before but users who upgrades from any official versions to my 1.3.2 many blocks after point of blockchain fork without database reset.
As forking point is passed relative long ago clients fail to rollback blockchain to point of fork correctly(seems it another bug in ORB code are not identified yet) and try to download blocks again and again in infinite loop. (dowload some blocks, fail to insert it to database, discard, download again and so on...)
And if somebody try to mine with such client it will fork own blockchain to network instead of joining an existing!

So warning to all
If you do upgrade from any official version to my version you need OR re-download blockchain from scratch (stop client, delete blk0001.dat blkindex.dat and "database" folder, start client or just point it to another separate empty data folder with -datadir= option) before any try to mine or send/receive coins.
Or as alternative - if you have any backups with datafolder of client where block count is any below <412000 you can roll back to this position as blockchains are 100% identical before this position.
It will save a lot of time and traffic to sync(as you will need download and verify only ~40-50k blocks instead of  ~450k) and also should fix the problems with sync.

2 almightyruler
You need deeper look in code, young padawan  

Yeah, his mind seems so overflooded by various conspiracy theories that it no longer remains a place for good portion of logic, analysis and programming skills    So recompiling to show him that it is a just error/glitch will not work likely. I already try such thing(and offer to other ORB users do so)  - not helps. Actually all my current fork began from such an demonstration attempt (read my stories above)
And if you continue to post to him about errors in code again and again he will probably thinks what you are just my clone or one of the members of the hidden group organized by me specifically to destroy his beloved currency  
There must be in the end at least some conspiracy!

But "just sit on my hands and wait for the exchanges to go for your chain instead" not an option too. A rolling stone gathers no moss
At least post some request to both exchanges (as i described in previous post to bigtop1967) from you behalf too.

And i think it is time to start building some infrastructure for new(current) fork.
May be u can start online block explorer for new ver? Seems you have needed skills.
Because currently no any block explorers at all. Even official one is broken now: https://andarazoroflove.org/explorer/orbitcoin/block_crawler.php
(it fail few days ago before block #417000, not sure why)

I can do such things myself but have a lack of time last days...
I can even offer award (bounty) for it to keep things more interest. Say 300 ORB coins for start.
It will be from new(my) fork. So in principle, anyone can mine their own right now, but 300 coins is equivalent to 1200 PoW blocks mined (+some orphans and rejects).
Even with the current very minimal difficulty it will take few days of mining on average GPU (or u need bring powerfull mining farm)

P.S.
It is not dedicated to almightyruler only. If anybody other want start block explorer with my ver running - it is OK too - i will send "bounty" after it will start working.

You as a programmer could understand before, that will be no significant changes after 417000 as negative gap not fixed properly


Nope. If you rebuild your statistic(please do so and post here) from beginning of this year you will see what PoS mining rate was low from start.
Until RedMist not go back online ( do not know where he was - he wrote something about a trip to Bulgaria...) and was scared by users transition from him to my unofficial version he greatly sped up the rate of PoS mining. Not sure how exactly but time and reason coincide exactly and point to him - possibly by using big stocks of coins from premine (with large stakes of coins PoS blocks are mined much faster / easier even with single client running) or just start runing all their wallets on different machines 24/7 and asked to do the same friends and acquaintances to reduce the time to reach block #417,000.
Otherwise at the initial rate it would take up to 1.5 months to reach this target. As we approach the given point just drop their support and network returned to its "normal" state as it was at the beginning of the year.
So actually we hit 417000 earlier than originally expected (at the release time of version 1.3.0)

P.S.
And now (after 417000) i see additional users updates to my ver (by activity in network - clients with new ip and downloading blocks starting from #417000 and from #0). Do not saw such activity in last ~3-4 days before #417000.

Answers to these questions are actually already given if you read attentively the previous messages. Or you not understand something in my posts?
Well again briefly:

- No, you can not transfer fresh mined coins to cryptsy right now. You can transfer them only to those who also uses this version. Accordingly transfer to the exchanges will be possible only when (if) it upgrade to the new version too - then coins mined now can be transfered and traded. For now only p2p trade is possible.
I have already sent such the request to both exchanges where ORB traded. But i need to be supported by other users to show there they want to use at exchange new updated client instead of the broken official too, and it is not just only my wish.
So send a message (via tickets or email) with such a request on own behalf.
You can refer to my ticket #62004 on criptsy (where I gave a detailed account of the situation to administration) or to this thread in you message to shorten your request
  
- YES and NO simultaneously.
Formally as now the blockchain is also forked yes - the difficulty in each chain is different. But in fact from the end of last year, PoW mining is working only in my version, so that there is only one difficulty in practice. It floats as usual depending on the amount and activity of miners in the range about from 400 to 2000 (0.006 to 0.03)
And the difficulty of the official version it makes no any sense - what is shown as the difficulty in official client and the different monitoing sites(as they use official ver too) is just frozen value(= 4137) from December 30/31, which has not changed because no one could obtain a single PoW block since.

- Yes it what i say last 2 weeks.
And as block #41700 was already reached today you can check this yourself. Or read posts in this threads:
https://cryptocointalk.com/topic/2736-looks-like-orbitcoin-will-resume-at-block-417000-in-the-meantime-do-not-use-unofficial-fork/page-6
https://cryptocointalk.com/topic/3464-its-nearly-block-417000-please-update-to-orb-version-13-once-reached/page-2
where many users of the official version wrote they do not see any positive changes after 417000 as i pedicted long ago (it was relative easy - i just test and debug official code so can forecast how it will be working after patch activation). Although exist possibility that the original developer(RedMist) has already prepared another working version, which he will now begin to use for himself and/or friends. But the version that is laid out in public access by them as official "fix" - does still not work with the PoW even after target block.

- Not really. Rather are 2 versions of the same coin. Which may merge back into one later. Or one wins and the other die. Or continue to exist both in parallel. Time (and your actions including too) will show.

Here is complete story about last month of OrbitCoin from my point of view.

1. Big problems begins 30-31 December 2013 - ALL PoW mining fail (all miners start getting 100% reject rate)
All original clients currently used (1.0, 1.1, 1.2) can not mine PoW at all, and PoS mining was very weak and slow - due to a relative small number of users and the lack of motivation for PoS mining (as 0% interest rate for PoS miners is set by original dev)

2. Cause of this problem - some drawbacks of code and bad selection of basic parameters (constants) when lunch this coins (some additional detail in this and following posts https://cryptocointalk.com/topic/2684-theredmist/page-2#entry26484).

3. But original developer instead of looking for the cause of the problem and fix the code talked about the ongoing attacks on its currency and some Conspiracy against it and him personally (though not surprising - that coin from beginning especially for fans of various conspiracy theories made by one of the such fans). Evens after few users (who use this coins, including me) directly pointed him (on this forum, cryptocointalk and in private messages) to the problem areas in the code and possible corrections he held version of "attacks." and preferred just sit and wait - as attacks cease all will work.

4. This situation continued for 6 or 7 days. Until I released (here on bitcointalk) a version with my own variant of correction - v. 1.2.1 which instantly fix problems with PoW mining and proved that the problem in the code, not some mythical attacks. It was just test/demonstration version.

5. In few hours after it original dev (TheRedMist) released the official version with similar (but not exactly the same) correction - v. 1.3.0.
Where had gone the same argument about the attacks and conspiracy? I think this version was ready to advance before my, but adhered with a some unknown purpose...

But in his version (1.3.0) activation of fix is delayed to block #417000. Near 6000 blocks ahead at moment of release. Taking into account not working PoW mining(no PoW blocks at all) and low rates of PoS Mining (about 100 blocks per day, and a tendency to slow down) in real time it can take several months. It is good for a some planned upgrade, but unacceptable for urgent critical fixes!
Later (after ~week) was a huge speed up of PoS mining (thinks it RedMist start use large stakes from his premine to speed up reaching #417000 mark) so now(after ~2 weeks) we are close to #417000. But at original speed it will be like 1 or 2 month delay
 
6. And even more than that BIG delay - i take this code (from v.1.3.0) as a basis (in my another version - 1.3.1) and I found that this official fix actually does not fix the problem even after the designated block # 41700 - PoW Mining still will not work! Not sure about that if it was error because of lack of knowledge and programming skills or is a some kind of planned sabotage to PoW mining from original dev. (He holds in his hands most of the all coins issued by giant premine  and may not be interested in the new minting reducing his share - if no new coins minted he can do anything with the coin and the exchange rate at any time as they wish and it is a very comfortable position that can bring huge profits out of nothing).

I post information about official fix will not work(not resume PoW mining) to forum (on cryptocointalk and here) but it was ignored by dev (RedMist) for few days more. He just simply goes off-line for more than a week and stopped to answer any questions and messages.

7. So looking for this situation i make and release one more version with own (working) variant of fix (it actually same as was in my test version v. 1.2.1) - 1.3.2. This time not just binaries but opensource on GitHub as fork from original version 1.3.0 so anybody  can easily track all changes i made and make sure that my version is safe: https://github.com/MaxMaximus/Orbitcoin
Activation of my fix was delayed for ~ 200 blocks (~ 2 days) to allow time for interested users to check the code changed, compile, download the initial chain of blocks (if install from scratch). And call Orb user to update from official to my version if they want resume PoW mining and fast transactions(now they are slow - due to low rate of PoS mining) return back.

And now my version (1.3.2) work in parallel to official (1.0, 1.1, 1.2.0, 1.3.0).
Patch to fix PoW mining already activated, PoS mining working normal too. So we already pass block #417000 long ago.

At some point 2 blockchain seems already forked - I expected such a development of situation though not doing it specifically (initially my version fully synced with all old versions) and did not expect it to be so soon - we was just hit by another "bad" block with incorrect timestamps on the official blockchain  of that old official versions and my new fixed ver treated differently and therefore the all next blocks after this point were incompatible (blocks created in 1.3.2 not pass checks in older versions and created in the old ver not pass checks in new so they just ban each other after several unsuccessful attempts to synchronize)

P.S.
Initial i have no any plans of overtaking control of this coin. I am was just active user of this coin:
- i solo mined this coin on my own mining farm as it was a little more profitable if compared to LiteCoin or other well established alt_coins  
- i trading (speculating) with it on COINS-E and later on Criptsy
- i hold relative large amouts of this coin as part of my mid/long term investments (~ 5000-7000 coins it is near ~ 1.5-2 btc at moment of failure, but already 3-4 times less now due collapsed exchange rate due blunt and incompetent behavior of the original developer)

So i just want coin fixed as soon as possible and unhappy about weak and slow response of the original developer to such BIG problems

My short plan was:
1. determine the cause of coin failure - done
2. find bugs in code, fix(patch) it, release new fixed version both source (on GitHub) and binaries - done
3. draw attentions of all Orb users to problem and possible solution - almost done
4. to ensure that as many users as possible upgrade to my revised version instead of the official - in progress
5. convince exchanges to update their clients to my version too by longest blockchain and multiple request from different users of new ver - no progress for now (seems the original dev TheRedMist simply offered them a part of coins from his giant premine in exchange for that they will stick to his versions only)

I do not have long term plan though from beggining...
But now it seems the only way to fix this situation is to become the new dev of Orbitcoin instead of the original RedMist as he did not intend to any cooperate and only wants everybody "fuck off" (exact quote of his words) with their claims and complaints about the critical functions not working "only" a just a month (what a trifle compared with 4000 years as he say   ) and he lost communication "only for a week". And left him alone with a coin in his full disposal.

bigtop1967
Because owner of this site and original dev (he usually using the nickname TheRedMist) do a lot of mindless stupid things that led to that coin is dying now.
And now just afraid that people are moving to my version and he may lose control of the coin because of their own stupidity.

Yes it is a conflict between versions in the network. Not such a mess now, network was just split to 2 segment around a week ago (re-read last 2 pages in this thread) which now work independently and are not specifically interfere with each other (and even little help to each other, as the ~98% of blockchains are still the same blocks, so initial blockchain download can occur from any version online - its compatible until blocks around #413000-#414000 and later)
Part of the network use official versions where only PoS is working. This chain at block #416184 now and waiting for block #417000 mark
Other part of the network use my version (1.3.2) with working patch to PoW mining. This chain at block #436416 now already

And network will be splited once more at block #417000 After this point it will be 3 blockchain forks:
- formed by all user who still use any of previous official versions (1.0, 1.1, 1.2) (and in a network a lot of users even with v. 1.0 because of another stupidity or/and carelessness of RedMist - he can not even correctly update his own website so lot of people still downloading, install and use a version 1.0 instead of the latest)
- who decide to upgrade to "patched" official version (1.3.0), which actually not fix anything and will need next another patch/upgrade later which will be incompatible with any current version or 1.3.0
- who choose my version with really working patch (1.3.2) and PoW mining right now

And after RedMist pull his head out of his ass and finally will understand that what he had been told for weeks is truth - he will be forced to release another more version, not compatible with the all previous again. Causing another forking of blockchain once more.

So you just need to choose which version (and blockchain) to follow.

P.S.
I will do large post with a brief history of what was happening with OrbitCoin last month and all of my own actions later today.

Current best chain

I warn about risk of PoW mining in new fork from beginning: https://bitcointalk.org/index.php?topic=265555.msg4426523#msg4426523

Number of nodes online with new client running and port is open(by ISP,router,firewall,settings in client) for incoming connection is still too low to form stable well interconnected network...

My guess what happened - a few clients(nodes) appeared in an isolated sub-network - with active connections to each other (which allows you to start mining and the client indicates that it is synchronized with the network) but with no links to the rest of the network. Later when such a link established something prevented  client from dropping the current (lagging) chain and synchronize with the main (for example number of blocks to be orphaned my be somehow limited, and ORB  produce a lot of blocks fast - just one day in "isolation" = near 3000 blocks differences between the chains, which the client would try to replace at one time if connect to client with other longer chain) . And since this nodes fail to sync to main chain they continued to build its own separate chain in parallel...

About exchanges read my other post: https://bitcointalk.org/index.php?topic=265555.msg4426523#msg4426523

Not sure what is happening and what is the cause of problems with synchronization...
If problem still persist (i sow what 2 client from my warning list now synced OK, may be one of them you) you can also try to connect to one of the fully synchronized node directly and see what comes of it.
In Orbitcoin.conf replace temporarily
all addnode= by one connect=
as ip try first 2 from my list above (its online, fully synced and ports is open for inbound connections at time as i write this post)
If even this not help i would like have a look at the file debug.log from data folder. If the problem persists and you do not mind sharing some personal information also contained in it (like ip address, folder where client installed, time when it is run) and send me a link to the archive via PM.
I will try to determine the cause of such behavior.

P.S.
Generally there is a simple, fast and 100% working way to catch up with the current chain - I can just upload to online storage archive with files  blk0001.dat and blkindex.dat from fully synchronized client.
But this is the wrong/bad way to sync ...

Hmm

Looks like some of the people using new ver somehow stuck on the side blockchain.
Last 2 days I see strange activity in the new network - some clients with fewer block count (about 100-400 blocks behind) and lower levels of trust score are connecting but instead to be synced with the latest the longest chain instead try to send their own blocks from shorter chain.
Or start to download part of longest blockchain many times in a circle (somewhere in the 411k to 421k, then back to ~411к, download to ~421k, back to 411k and so on ) .

Maybe it's some kind of sabotage to new fork (this situation creates a lot of parasitic traffic on the network and create a high load on CPU where new client running ) but possibly a just some failure/glitch and of these clients for some reason just can not sync normally...

Owners of the following ip addresses should pay attention:
137.116.129.120   
203.45.89.214
89.28.89.80
31.17.16.109

If you do NOT do  something special (such as tests of their own modified versions of the client) check the logs - you may have to redownload the whole blockchain again. (delete blk0001.dat and blkindex.dat from data folder, add fresh list of nodes and start again, -rescan wallet after sync)
If while you are mining PoW now - stop it - all mined blocks will be orphaned. In fact they already orphans now, just for some reason your client can not synchronize with the main chain.
For the record - the current best chain for the unofficial (1.3.2) client:
(time is GMT/UTC)

And price is fall back (~ 3 times) already
But somebody already bought ~40k coins. This is the way nearly half of all issued coins (except premine)
Probable it is first part of 'buy-back' operation from original dev (TheRedMist).
And all story with PoW mining down, mythical stories about attacks on the network, artificial long delays with fix, the release of non-working patches, disappearance from the Internet for more than a week, ignoring all questions and appeals and so on - just parts of plan for sow some panic / disbelief in coin to crash exchange rates and buy coins very cheap.
And then all wishing to sell will end - the developer will appear "in shining armor on a white horse" and finally release a working version fixes and begin to address other issues. And start pumping the exchange rate.

If anybody need here fresh list of nodes running new clients (for clean install or if any difficulties with sync):

Think i found point of blockchain fork for official(PoS only) and new (with PoW fixed)


It was another "time traveling block"

Same as ruined PoW mining in previos time (at 30/31 Dec 2013) (although at that time deviation of time was much more - near an hour)
So it was corrected in my version by added patch and NOT corrected in old official versions.
This led to differences in all subsequent blocks after #412384  and the impossibility of further synchronization between old and new versions

Of course we creating new blockchain now.
But it is not total new - up to some point of time (near 11-12 Jan 2014 i think, need to compare chains to figure out concrete block number from which there was a division) it is a 100% 1:1 copy of original blockchain. After this moment(now) it is separate and independent.

Any transaction to exchanges will not pass as long as they use the old(official) versions of the client.

In cryptocoins world no any transaction/coins never lost until you lost your wallet.dat(private keys for coins) or send it to a nonexistent address.

In particular this coins from example (send from new client to service or user who use old client and can not see this transaction right now) will be available to the payee as soon as he updates its client software and rescan new blockchain.
Or as alternative if exchanges and main part of other Orb user refuse to upgrade to the new version you can always downgrade (install an older official version) and use old wallet.dat from bacup and all the coins are in place (as in the old blockchain the respective transactions is absent and coins not spend).
Excluding coins received in last days from PoW mining of course (because PoW does not exist in the old ver) - these coins will disappear after downgrade.

Yes

PoW Mining at new client currently makes little sense - if only for the test(make sure it works), curiosity or just some fun - with small hashing power.
For example i connect only one my weakest card (HD 5770 ~ 150 kh/s). All other (now i have 7 card in 2 comps total) mining LiteCoin and other more stable ALTs

Now we need to increase production of PoS blocks first.
If you want to help with this - I can give advice how to produce more PoS blocks- welcome to PM.  

Yes you got situation correctly. PoS adds tons of trust - original ORB dev reduced weight of PoW Mining to almost zero (it only used for the issue of new coins)

But important refinement - not every block in old PoS chain rolls back all PoW blocks - for new clients PoS mining works too and adds same trust (>= 1 mill each) too.
And some PoS miner already work on new clients in new chain (including my own wallet with lots of relative old coins)
So rolls back happens only when old clients manages to create a longer chain of PoS blocks.