Missing one deposit from suprnova to bittrex... how to check?
TX#: 0x95b72faaee0f35611a4d2238161167a0274bb4fd3ab26c932c9430d09b990c6e
One deposit after went without problems...
The pool automatically verifies all sent payments about an hour after they have been sent as it is a known issue with ETH/SHIFT that some payments simply "vanish" or the TX never gets incorporated into the blockchain.
Your payment is verified by the wallet already by eth_getTransactionReceipt:
{
"id": 1,
"jsonrpc": "2.0",
"result": {
"transactionHash": "0x95b72faaee0f35611a4d2238161167a0274bb4fd3ab26c932c9430d09b990c6e",
"transactionIndex": "0x0",
[b] "blockNumber": "0x4c1e",
"blockHash": "0x64203112e38e461e2b5800aa635c72ed8dcbba35525d693b591b35e5032feb78",[/b]
"cumulativeGasUsed": "0x5208",
"gasUsed": "0x5208",
"contractAddress": null,
"logs": [
]
}
}We recommend that you do a getBlock for which this tx should have been commited. Check the list of tx there.
Regards
Yeah I've done that now.
There seems to be some more severe bugs in the daemon:
curl -X POST --data '{"jsonrpc":"2.0","method":"eth_getTransactionReceipt","params":["0x95b72faaee0f35611a4d2238161167a0274bb4fd3ab26c932c9430d09b990c6e"],"id":1}'
http://127.0.0.1:53901Returns:
{
"id": 1,
"jsonrpc": "2.0",
"result": {
"transactionHash": "0x95b72faaee0f35611a4d2238161167a0274bb4fd3ab26c932c9430d09b990c6e",
"transactionIndex": "0x0",
[b] "blockNumber": "0x4c1e",
"blockHash": "0x64203112e38e461e2b5800aa635c72ed8dcbba35525d693b591b35e5032feb78",[/b]
"cumulativeGasUsed": "0x5208",
"gasUsed": "0x5208",
"contractAddress": null,
"logs": [
]
}
}BUT when I try to lookup that block, its differrent hash:
curl -X POST --data '{"jsonrpc":"2.0","method":"eth_getBlockByNumber","params":["0x4c1e",true],"id":1}'
http://127.0.0.1:53901{
"id": 1,
"jsonrpc": "2.0",
"result": {
"number": "0x4c1e",
[b] "hash": "0x72426d37d2667b51f98ae01dc07652f1dd57abbf7a86dde4816e5b85a0b47e87",[/b]
"parentHash": "0x9088e8eaf1d9ff6b213017ff53771e7cd5c417978708e989822323bbb0e286fe",
"nonce": "0x428383064c7b576e",
"sha3Uncles": "0x1dcc4de8dec75d7aab85b567b6ccd41ad312451b948a7413f0a142fd40d49347",
"logsBloom": "0x00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000",
"transactionsRoot": "0x56e81f171bcc55a6ff8345e692c0f86e5b48e01b996cadc001622fb5e363b421",
"stateRoot": "0x2e70c6489043f84cb3453c205c34ec45d4368015a114d6db40f2f586f90c5719",
"miner": "0x1b942ab732d24a7aba8888722c15acc96b3508c2",
"difficulty": "0x2f7455036c",
"totalDifficulty": "0x1393e9efba982c",
"size": "0x21d",
"extraData": "0xd982020085536869667487676f312e342e328777696e646f7773",
"gasLimit": "0x2fefd8",
"gasUsed": "0x0",
"timestamp": "0x55ebffa2",
"transactions": [
],
"uncles": [
]
}
}When I try to lookup that hash directly it seems valid again and also has the wanted transactions:
curl -X POST --data '{"jsonrpc":"2.0","method":"eth_getBlockByHash","params":["0x64203112e38e461e2b5800aa635c72ed8dcbba35525d693b591b35e5032feb78",true],"id":1}'
http://127.0.0.1:53901{
"id": 1,
"jsonrpc": "2.0",
"result": {
"number": "0x4c1e",
"hash": "0x64203112e38e461e2b5800aa635c72ed8dcbba35525d693b591b35e5032feb78",
"parentHash": "0x9088e8eaf1d9ff6b213017ff53771e7cd5c417978708e989822323bbb0e286fe",
"nonce": "0xf0024b41b15ee138",
"sha3Uncles": "0x1dcc4de8dec75d7aab85b567b6ccd41ad312451b948a7413f0a142fd40d49347",
"logsBloom": "0x00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000",
"transactionsRoot": "0x834656b69ce979a3d30223cd91c319cd41546e8f9708e6b5ceff307ce6d058e0",
"stateRoot": "0x725bd5c40796563f253ae594b7548564ca07726784118111862b6d155fad8ab4",
"miner": "0x859c9c31c8a0d57f6db5262ab1408a916871961b",
"difficulty": "0x2f7455036c",
"totalDifficulty": "0x1393e9efba982c",
"size": "0x2e9",
"extraData": "0x",
"gasLimit": "0x2fefd8",
"gasUsed": "0xa410",
"timestamp": "0x55ebffac",
"transactions": [
{
"hash": "0x95b72faaee0f35611a4d2238161167a0274bb4fd3ab26c932c9430d09b990c6e",
"nonce": "0x539",
"blockHash": "0x64203112e38e461e2b5800aa635c72ed8dcbba35525d693b591b35e5032feb78",
"blockNumber": "0x4c1e",
"transactionIndex": "0x0",
"from": "0xe787e65402d887641e7ffdc75ba8f6676833767d",
"to": "0x0df1d5fa3236d849ce8c09db95049687287b397f",
"value": "0x11897e1147021f000",
"gas": "0x15f90",
"gasPrice": "0xba43b7400",
"input": "0x"
},
{
"hash": "0x37900ae496339709bc1c2ab053236c7ccec719a318d505920d526d2a971bd1e6",
"nonce": "0x53a",
"blockHash": "0x64203112e38e461e2b5800aa635c72ed8dcbba35525d693b591b35e5032feb78",
"blockNumber": "0x4c1e",
"transactionIndex": "0x1",
"from": "0xe787e65402d887641e7ffdc75ba8f6676833767d",
"to": "0x5c866383183fedfdde62abeaf7d14217a79536aa",
"value": "0x203cc864158a400",
"gas": "0x15f90",
"gasPrice": "0xba43b7400",
"input": "0x"
}
],
"uncles": [
]
}
}So it seems the wallet thinks there are two blocks with the same number but a different hash on the network...
Thats quite a problem...
