Found block, submitted successfully, but not being accounted for.

[artbatista]

Running Orbitcoin, a POS/POW hybrid coin.

At 6:49:56, block # 891617 was found. My daemon shows the transaction, but with a different id:

http://atlas.phoenixcoin.org:1080/tx/d40d943c49672dd28c6859884e3911878700f7237cf24a056668d681afb66e0a

The Coinium log shows a submit that failed and shows a different tx id:

09/27/2014 06:49:56 -04:00 [Debug] [ShareManager] [Orbitcoin] Share accepted at 233192.57/23.67758 by miner oHQSUj7AP3i2GnpBuEz43D8kmycDPPiHqQ
09/27/2014 06:49:56 -04:00 [Error] [ShareManager] [Orbitcoin] Submit block [891617] failed with hash [07a1f78d041b074e56d06225015c5a9a220d0b7f3882dc9746a7229154d1f9e4] - reason; Block not found
09/27/2014 06:49:59 -04:00 [Debug] [ShareManager] [Orbitcoin] Share accepted at 125.07/23.67758 by miner oHQSUj7AP3i2GnpBuEz43D8kmycDPPiHqQ
09/27/2014 06:49:59 -04:00 [Debug] [ShareManager] [Bitcoin] Share accepted at 152.84/115.4251 by miner 17RgMzzPryAbv2XMLsckF8yMSmnTBS6TVG

As you can see, I did get credit for the block and it is a valid block, but the tx is wrong and coinium thinks the submit failed. The front end does not show that a block was found, so it's not being accounted for.
Running the develop branch

---

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

[artbatista]

another one:

08:24:20 [Debug] [ShareManager] [Orbitcoin] Share accepted at 125.57/40.92693 by miner oHQSUj7AP3i2GnpBuEz43D8kmycDPPiHqQ
08:24:20 [Error] [ShareManager] [Orbitcoin] Submit block [891713] failed with hash [8972f4f997382cfcc61296426f945ce6ac6842697596ac81db3c979239cab5e9]

• reason; Block not found

This block was accepted with different hash:
http://atlas.phoenixcoin.org:1080/block/0000000074655a0d4771aa5ff7adeebf4596d65758164b8da2b7c6a18038646c

Again, Coinium is not aware that a block was found.

[ClaudiuLSH]

I have the same issue with litecoin and bitcoin. Getting the same exact messages and no blocks accounted for.

[artbatista]

Did your coin daemon actually show a new block?

The above message is normal when a block candidate is rejected by the network. My problem is that blocks are actually being found and accounted by the daemon, but not seen by coinium.

[bonesoul]

@artbatista thanks for the report.

Happening in orbit-coin right? I'll be examining the issue.

[artbatista]

Correct

Sent from my iPhone

On Sep 28, 2014, at 9:32 AM, Hüseyin Uslu notifications@github.com wrote:

@artbatista thanks for the report.

Happening in orbit-coin right? I'll be examining the issue.

—
Reply to this email directly or view it on GitHub.

[kizeren]

Same issue on fluttercoin. Blocks are indeed being found but with a hash other then we coinium thinks.