Think of coin days (weight) rather than coins alone. 300% per year is 0.82% per day. 5 HAL can be earned in 1 day by 610 HAL input, in 2 days by 305 HAL, etc. Of course, if it's lucky enough because stake generation is a random process like any kind of mining.

The whole block chain is 166K blocks or 88 megabytes to download. How can it take forever?

MacOS X client uploaded. See the OP.

Cryptsy

You pay $250 every 90 days if you don't make over $5000 in transaction volume every month.

New pool in Paris, France: DNB (2% fee, PPLNS)

My HAL block explorer is up and loading the block chain.

http://atlas.phoenixcoin.org:2080

Good to hear that, Mullick. The pool is up again. I'll get a block explorer running today most likely upon completion of a X15 -> BLAKE2s block hash verification module.

Qt4 does the job just fine, so I haven't bothered myself even to compile Qt5. I see no advantage in replacing one with the other. I think it isn't difficult to make the current client Qt5 compatible if that matters.

The network has just switched to correct PoS rewards. Make sure you run v1.1.0.2 wallet.

By the way, merry Xmas

Bittrex says for HAL "Possible community takeover in progress"

I have noticed some blocks delivering very little stake rewards. It appears there is a bug of the previous developer who has had copy-pasted some code without understanding. Bitcoin defines COIN as 100 million units (satoshis). HAL also follows this. However PPC, NVC and most other PoW/PoS coins define COIN as 1 million units. That's for a reason to avoid overflows.


While 64-bit unsigned integer allows for very large numbers (2 ^ 64 = 18446744073709551616), it may be not enough for the code above. Here is a real example from the HAL block chain.


nCoinAge * nRewardCoinYear = 61552349166 * 300000000 = 18465704749800000000

Incorrect subsidy is (18465704749800000000 - 18446744073709551616) / (365 * 100000000) =
519470 satoshis or 0.0051947 HAL

Correct subsidy is 18465704749800000000 / (365 * 100000000) =
505909719 satoshis or 5.05909719 HAL

It gets limited to 5 HAL on the next step. So, I've modified the reward calculation code to make sure it never overflows.


Works fine for HAL since the current and future interest rates are multiples of 100% which is COIN.

Please upgrade to HAL v1.1.0.2.

Regarding your Cryptsy transaction, it isn't in our block chain.


They are still on the old block chain.

If you check txid's of vin's they dumped, you see some of them are also not found and the others are prior to the NeoScrypt hard fork.

There was a bug in the hash caching code by block index which resulted in many of these errors in debug.log:


Fixed it and uploaded v1.1.0.1, please upgrade.

Enough of this copy-paste. We've got your point.

They went through before v1.5 clients banned you. Since these coins were unspent on the new chain, they were allowed to get into blocks there.

Guys, could you take your private investigations elsewhere? He isn't a kind of celebrity or big time criminal, therefore I don't really care.

I'll put up a block explorer somewhere this week.

PoS is low energy hashing, therefore SHA-256d fits fine and it's not worth the effort of switching it to a different algorithm. PoW should stay ASIC free. It's not good to have several algorithms for PoW. Increased complexity, reduced security. If an attacker compromises one algorithm of those few, he may screw the whole network. It's difficult to do block trust balancing across several algorithms. None of the existing coins does it properly, but who cares?

According to the block chain, all these blocks after the switch were mined by the DNB pool. I'm going to send 600 ORB from our Advancement Fund to David, so he can credit 100 ORB to the finder of the 1st NeoScrypt block and distribute the remaining 500 ORB between miners of the following 50 blocks up to #1011416.

If it doesn't show in a block explorer, it hasn't made itself to the block chain. What version is your old wallet? If it's v1.4.x.x, no surprise you're out of sync. You should have copied your old wallet.dat to v1.5.0.0 and got it synchronised before making any transactions.