Our new block trust scoring protocol works just as expected. Trust scores are easy to verify with a calculator. For example, a PoW block #2002764 is after a PoS block, so it gets 100% trust which is current difficulty / min. difficulty, so 1.233066 / 0.000244 = 5053 (it's 5050 actually because of single precision floating point inaccuracy). The next PoS block gets 200% trust, i.e. 10100, and so on.



ORB allows TX comments up to 140 bytes and any data up to 40 bytes in scripts after OP_RETURN. It isn't good to store a lot of third party data in general purpose block chains. A custom block chain is much better.

You can check their deposit/withdrawal addresses with a block explorer to see if they have staking enabled.

The PoS block target is 3 minutes now vs. 1.5 minutes before the hard fork, reward stays the same 1 ORB, so the difficulty has been doubled to maintain the new target. It seems optimal input size for staking is 50 to 100 ORB now.

For the past 36 hours after the hard fork, our average block target was 1.72 minutes. That's fairly close to 2 minutes. The second part of the hard fork takes place on the 1st of October 2016 12:00:00 GMT when our new block trust scoring protocol gets activated.

The OP is outdated a bit. Any NeoScrypt capable miner will do the job. There are a few pools out there.

NSGminer v0.9.2: The Fastest NeoScrypt GPU Miner

I used BZip2 instead of Deflate to compress these binaries. PKZIP supports it since 2003. Other popular archivers like 7-Zip, WinZip, WinRAR, etc. have no problems either. It seems Microsoft is slow to follow up.

It's behind CloudFlare. The web site seems down at the moment. CloudFlare loads a cached copy after a timeout.


Whales play their game.

Orphans shouldn't be an issue with the coming block target of 2 minutes on average.

Switch from vardiff to the fixed diff of 4 (64 in the pool).



These are ignored by the miner.

MacOS X binaries uploaded. All my seed nodes are running v1.6.0.0 now including the official Abe powered block explorer. Although most people should be fine with the in-wallet block explorer. It's much faster.

Could you update your ORB daemon to v1.6.0.0? There is a hard fork coming in a week. It should be an easy move with almost no downtime.

https://github.com/ghostlander/Orbitcoin/releases/tag/v1.6.0.0-orb

The ANN updated, Windows and Linux binaries ready, MacOS X binaries coming tomorrow. Would be good to update our web site as well. We need to notify all pools and exchanges of the hard fork.

Well, 8 days is when the block #2 million is expected. I admit a bit more upgrade time could be available without the support for BIP65, but I guess it's worth the wait. We want to keep up with the existing inflation model, do we? That's how our specification for block rewards and coin supply looks like:

block height 2000001 to 2500000 reward 1.000000 ORB (coin supply 3275012.279225 ORB)
block height 2500001 to 3000000 reward 0.500000 ORB (coin supply 3525012.279225 ORB)
block height 3000001 to 3500000 reward 0.250000 ORB (coin supply 3650012.279225 ORB)
block height 3500001 to 4000000 reward 0.125000 ORB (coin supply 3712512.279225 ORB)
block height 4000001 to 4500000 reward 0.062500 ORB (coin supply 3743762.279225 ORB)
block height 4500001 to 5000000 reward 0.031250 ORB (coin supply 3759387.279225 ORB)
block height 5000001 to 5500000 reward 0.015625 ORB (coin supply 3767199.779225 ORB)
block height 5500001 to 6000000 reward 0.007812 ORB (coin supply 3771105.779225 ORB)
block height 6000001 to 6500000 reward 0.003906 ORB (coin supply 3773058.779225 ORB)
block height 6500001 to 7000000 reward 0.001953 ORB (coin supply 3774035.279225 ORB)
block height 7000001 to 7500000 reward 0.000976 ORB (coin supply 3774523.279225 ORB)
block height 7500001 to 8000000 reward 0.000488 ORB (coin supply 3774767.279225 ORB)
block height 8000001 to 8500000 reward 0.000244 ORB (coin supply 3774889.279225 ORB)
block height 8500001 to 9000000 reward 0.000122 ORB (coin supply 3774950.279225 ORB)
block height 9000001 to 9500000 reward 0.000061 ORB (coin supply 3774980.779225 ORB)
block height 9500001 to 10000000 reward 0.000030 ORB (coin supply 3774995.779225 ORB)
block height 10000001 to 10500000 reward 0.000015 ORB (coin supply 3775003.279225 ORB)
block height 10500001 to 11000000 reward 0.000007 ORB (coin supply 3775006.779225 ORB)
block height 11000001 to 11500000 reward 0.000003 ORB (coin supply 3775008.279225 ORB)
block height 11500001 to 12000000 reward 0.000001 ORB (coin supply 3775008.779225 ORB)

1 million ORBs for the next 10 million blocks taking about 38 years. The grand total is 3.77 million coins.

Salvage your privkeys from there (bitcointools will help you if nothing else) and import them into a working wallet. It will take a while to rescan a block chain 4 million blocks long. The current HBN client can import and rescan one key at once, so the whole task may be very time consuming.

I'm not sure if I understand your problem. If you cannot connect to a pool, try another one. If your mining rig BSODs or produces HW errors, try to downgrade your drivers. I use Catalyst 14.6 beta / 14.7 RC3 mostly, though 15.7.1 also seems fine. 16.x are messy, so they're a matter of trial and error.

Orbitcoin v1.6.0.0 is ready for release. BIP65 and BIP66 will be mandatory after the hard fork for all blocks and payments (BIP66 is forced on mempool only right now by v1.5.1.x clients). Those who compile from source can pull the code from GitHub. Binaries will be available tomorrow. The hard fork deadline is in 8 days.

Your cards are overclocked too much. The Ethereum algo is less power hungry. GPUs are limited by their memory bandwidth. That's why dual miners work there by running memory and computation expensive algos concurrently. NeoScrypt is both memory and computation expensive.

I've pushed the v1.6.0.0 code to GitHub two days ago.

https://github.com/ghostlander/Orbitcoin/commit/fd37b73f527ef3588f07466b92d2af243dd1c7ed

It's almost complete. There will be one more patch before tagging this release. I'm adding the BIP65 support (Lock Time) which redefines OP_NOP2 to OP_CHECKLOCKTIMEVERIFY. It marks a transaction output unspendable until a future time stamp or block height. Useful for escrow together with multisig.

The only delay with this patch is unit tests to make sure everything works as it should. There are some differences between ORB and BTC transactions, so I cannot copy-paste their unit tests. They need to be modified.

Why do you want it every hour? Even every day seems an overkill.

Welcome to the modern day slavery. I find it disgusting that in the 21st century some people have to work full time for something like $1 a day while many others make it in a minute literally.

Educate yourself. Blockchain.info doesn't hold any user coins. They have no control over private keys of their users' accounts. All important data is client side encrypted. You can print out all your private keys and import them into a Core wallet or whatever if their free service ceases to exist some day or if you just don't want to use it any longer.