Topic: [ANN] [XMG] MAGI | CPU mining | mPoW | mPoS | [MagiPay] - page 391. (Read 2375631 times)

it works if u get the latest client and download the block chain here:
https://bitcointalksearch.org/topic/m.21177317

replace the contents at: C:\Users\xxxxx\AppData\Roaming\Magi

obviously close ur wallet while replacing

still wrong chain? not fixed yet?

what about exchanges?

great, so mining payouts were done on the wrong chain.   

  iam on the same chain

first reorg

This comment is about the test chain. Don't worry if your chain doesn't match this info.

Any of you guys running on the test chain noticed that you have got pow blocks to different addresses?


Currently on block 1451435
00000048182ab20b081efc08dcdfb53d3847015d41c1ef442c7ee12db5dc6023

PM your username, wallet address, let me check.

Not sure what this means. It didn't get orphaned

MagiMiner:
new block found  
  hash: 000000134bfd93415dc46e9ba75829dd2e93bb9848125fe9ee88ef068345495b  
target: 000000a809000000000000000000000000000000000000000000000000000000
CBlock(hash=000000134bfd93415dc46e9ba75829dd2e93bb9848125fe9ee88ef068345495b, ver=5, hashPrevBlock=000000816cdb28fe74fbbb8b49bb0139c9e62d1916e385dcf0bdbdc1b1fa6ba5, hashMerkleRoot=2cc70ba8e9b63ca2d1ee2d1583f2b802ce6b822f8898758d995594b29a13ceee, nTime=1503940361, nBits=1e00a809, nNonce=1431658472, vtx=1, vchBlockSig=30450221009ded490686bfb5b0d5d67669bd806838100b534a9f0e2cbacaf9a69086741bef0220621c7fdf9b8f4534bbf8f9571185ee7a7bbb729c2daa5b38f5afe446220890e1)
  Coinbase(hash=2cc70ba8e9, nTime=1503940345, ver=1, vin.size=1, vout.size=1, nLockTime=0)
    CTxIn(COutPoint(0000000000, 4294967295), coinbase 039c2516021601062f503253482f)
    CTxOut(nValue=24.15422124, scriptPubKey=037e4be166f7686cb66dfee3c86368472609ac438a44523b8f8d215131eabe12ef OP_CHECKSIG)
  vMerkleTree: 2cc70ba8e9
generated 24.15422124
ERROR: MagiMiner : generated block is stale

EDIT: correction: it didn't even get generated. I happened to mine two in a row, so I didn't notice.

It occurred to me that a possible fix for the flash mining problem is to require the previous block accepted by the block chain for every PoW block to be a PoS block.  This solution has already been coded in HBN in a recent update and might be worth trying as a fix.  It is nice to see all the support out there to find a fix and get the coin running well!

This comment is about the test chain. Don't worry if your chain doesn't match this info.

I just experienced a blockchain "re-organize" in the test chain.
I think my wallet switched to a new chain after having jsut 1 block in the chain it was following versus 2 blocks in another chain.
Curiously, I can see two blocks for the same height: the one orphaned after the re-organization, and the new one:

old block:

{
"hash" : "0000004821f9ec34eb7f3eaa304fe554c83da53ea95d0d121d715b20f64ba8f7",
"confirmations" : 0,
"size" : 265,
"height" : 1451405,
"version" : 5,
"merkleroot" : "946b2d87eeef2e3fe0cbee71d66ff30a491e207a8e8776b44686123fd16fb859",
"mint" : 29.18625332,
"time" : 1503937672,
"nonce" : 2147525994,
"bits" : "1d4cbbaa",
"difficulty" : 0.01303199,
"previousblockhash" : "000000397a5d746a3e3a29c5029dece846e4d319b7fbdb73fb24e6284ffa8847",
"flags" : "proof-of-work",
"proofhash" : "0000004821f9ec34eb7f3eaa304fe554c83da53ea95d0d121d715b20f64ba8f7",
"entropybit" : 1,
"modifier" : "dc6109555e364344",
"modifierchecksum" : "1ae35a69",
"tx" : [
"946b2d87eeef2e3fe0cbee71d66ff30a491e207a8e8776b44686123fd16fb859"
],
"signature" : "304402207c6e4ceea4b9fd7821fc89a266d89bde0de94f4d97cb5f71d4fdada356b4b4480220766 fb7a93684a238cbfd64d69dda8a189ad3d5d094e145ac581568ea2f51db20"
}


new block:

{
"hash" : "000000344739bc3ba1225b1ba3e0fc30e8d177ad20e4c5e9b08253f926e79d07",
"confirmations" : 3,
"size" : 267,
"height" : 1451405,
"version" : 5,
"merkleroot" : "24f89a258022e41c3b97eed0147acd70b9bdbf542f47ee448e68f0213becb51c",
"mint" : 29.18625332,
"time" : 1503938041,
"nonce" : 2863350589,
"bits" : "1d4cbbaa",
"difficulty" : 0.01303199,
"previousblockhash" : "000000397a5d746a3e3a29c5029dece846e4d319b7fbdb73fb24e6284ffa8847",
"nextblockhash" : "00000002a580822bb0944adfebe4b87cea91b2a580e5af5916cccd94a585540e",
"flags" : "proof-of-work",
"proofhash" : "000000344739bc3ba1225b1ba3e0fc30e8d177ad20e4c5e9b08253f926e79d07",
"entropybit" : 1,
"modifier" : "dc6109555e364344",
"modifierchecksum" : "1ae35a69",
"tx" : [
"24f89a258022e41c3b97eed0147acd70b9bdbf542f47ee448e68f0213becb51c"
],
"signature" : "3046022100bda3f52c53632cd652685537bb531e54ee43073e0c6909596326ecc7c4a3384202210 08f1ac45db6cc7a546b1d6a97e2d1955ff457f74c45f247e70280a4d4ddb27ec1"
}

Your block hash is correct according to the main chain.
The comment you have been reading pertain a test chain.
So no worries

Looks like it was addressed here
https://bitcointalksearch.org/topic/m.21217741

Admin,
i need to know which blockchain are correct.
Could you paste some info?

I have 10 connection in client, but my hash are different.
getblockhash 1451404
3dbd73ed0f8ddafbb14577f4a028dc0a227d1dbc87219d8b36660b2754fa0c10

Nor resetting the blockchain?

I think that error is with wallet.dat and i don't think restart will help.

getblockhash 1451404
000000397a5d746a3e3a29c5029dece846e4d319b7fbdb73fb24e6284ffa8847

Any ETA when the bittrex wallet will be back?

Same block hashes here. We're on same chain.

Seems like someone broadcasted a transaction with invalid input(s). Possibly from an orphaned block.

EDIT: that errors seems to be logged inside the new block generation function, both for mining or staking. I believe your wallet won't find any of the two kinds of blocks. Does it resolve if you restart the wallet?

getblockhash 1451400
00000087b7a1689e3bed8787f0c6cdb736f3ea7b81da076d9560fd35f022a891
getblockhash 1451402
000000786038a6da92a61753cc2ed0f920d8b745eca3901d849631becd27caf2


I'm only seeing this error

Flushed wallet.dat 17ms
ERROR: mempool transaction missing input

Bah, you want all the rewards

I'm still in the main test chain. Check your blocks in the Console:

getblockhash 1451400

00000087b7a1689e3bed8787f0c6cdb736f3ea7b81da076d9560fd35f022a891


But I have this warning in my log file:

WARNING: GetLastPoWBlockIndex() not found; return pindexGenesisBlock
WARNING: averaged over less than BBLOCK_AVER blocks --> GetDifficultyFromBitsV2
WARNING: GetLastPoWBlockIndex() not found; return pindexGenesisBlock
ERROR: no actual average done --> GetDifficultyFromBitsV2
WARNING: GetLastPoWBlockIndex() not found; return pindexGenesisBlock
WARNING: averaged over less than BBLOCK_AVER blocks --> GetDifficultyFromBitsV2
WARNING: GetLastPoWBlockIndex() not found; return pindexGenesisBlock
ERROR: no actual average done --> GetDifficultyFromBitsV2