Topic: remove thread - page 5. (Read 31256 times)

Sent you a PM about that 6 days ago.

I warn about risk of PoW mining in new fork from beginning: https://bitcointalksearch.org/topic/m.4426523

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://bitcointalksearch.org/topic/m.4426523

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 ...

It is certainly a glitch, because I mine solo with new wallet 1.3.2.0 (one of mentioned IPs is mine) and nothing I send to cryptsy or coinse is valid. And I burned the electricity for nothing as I understand from your message and I certainly do nothing special with the client. I'm re-downloading the chain now..

I added the new nodes, deleted blockchain (2 times), but my client synced only until block 427654.
You said -  "the current best chain height=427915"
What can i do?

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.

Wow orb is skyrocketing!!!

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.

Same. I can mine, and I sent a small amount to cryptsy (existing balance, NOT newly mined), but it's not showing.

wow coin revived, party time thanks

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.

Yes this correct - this continue until one of the 2 conditions:
- older PoS clients produce one more "bad"(invalid) block(same as cause fail of PoW mining)  - it will be rejected by all new clients and make sync to old "PoS-only" chain impossible
- new clients start produce more PoS blocks and will "outweigh" the old chain - new chain became primary/canonical

block 412301 proof-of-stake trust = 19742642560
block 412302 proof-of-stake trust = 19743691137 (after PoW blocks on hard fork chain reversed)

Difference : 1048577

So it looks like a PoS block adds more than a million to trust, but a PoW block only adds 1 (one!)

This probably means that in the short term - until people with substantial ORB holdings upgrade their client - each PoS block is going to wipe out all newly mined PoW blocks? It's impossible to mine 1048577 PoW blocks before a PoS block is generated.

This is the same problem CDC has, PoS blocks regularly reversing all PoW blocks.



edit: second reversal, around 519 PoW blocks discarded. There is probably no point mining this coin at this time.

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

Hi

As I wrote few posts above:
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.

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...