Some tx displaying (failed) but actually being confirmed

[immartian]

some transactions, like this one http://orbiter.musicoin.org/tx/0xd73fb4bbb13d15c0b553d00cf37d7eadabe9597189a4f5cbde52fdcc22bb8db9

being displayed as failed (because gas and gasused equal to each other),but seems it's not a failed tx from blockchain, we should investigate it and see what's the solution for this presentation.

The reason here is the argument been discussed in community http://ethereum.stackexchange.com/questions/1179/how-to-know-if-a-transaction-went-through-or-not-out-of-gas we should try to get more status from tx, instead of just compare gas and gasused.

A more detailed ref here: a good ref here: http://ethereum.stackexchange.com/questions/6002/transaction-status

[davembg]

Getting an error when attempting to sync with the latest version of parity:

2017-04-16 15:55:22 Configured for Musicoin using Ethash engine
2017-04-16 15:55:22 Stage 4 block verification failed for #1462 (a5e8…8343)
Error: Block(InvalidReceiptsRoot(Mismatch { expected: 365e9640df8101ba9ed076d1014759164a219132b75ba6d174d2787ebfa1ab24, found: 45bef3c8f45af0174311babea84ed659c7380a7249e2fe1ac5d7749f2918a383 }))

[immartian]

we didn't test on Parity 1.5+, as there's a hard fork. Will try to repeat this on our testing server, meanwhile, pls try to use 1.50 to sync with clean data folder.

[davembg]

works on 1.5.0, confirmed.
There are properties in the params section of the coin config where hard-fork params can be entered. I'll see what I can do with the fork at block 1462. Any data on the fork would be helpful.

[davembg]

examples:
https://github.com/paritytech/parity/blob/master/ethcore/res/ethereum/ropsten.json
https://github.com/paritytech/parity/blob/master/ethcore/res/ethereum/classic.json

Looks like these are the relevant options:

"networkID" : "0x3",
"forkBlock": 641350,
"forkCanonHash": "0x8033403e9fe5811a7b6d6b469905915de1c59207ce2172cbcf5d6ff14fa6a2eb",
"eip98Transition": "0x7fffffffffffff"