Show Posts
|
Pages: [1] 2 3 4 5 6 7 »
|
There appears to be 2 versions of "version 1.7", one that hard forks at block 140000 and a more recent one that forks at block 141500 (source was updated 6 hours ago, but version number was not changed). If the network isn't all on the same version when we hit 140,000, it will be a pretty forked up mess. I bet there are a lot of people on the old v1.7 that think they are up to date but will be broken at 140,000. https://github.com/tittiecoin/tittiecoin/commit/dadca4dc7cc36c69af76d96c1c90e310f494ea2a
|
|
|
PoW is effectively over. There is a bug in GetNextTargetRequired which creates negative targets for PoW blocks which are not allowed in CheckProofOfWork when the block is submitted. This was triggered by 10 PoS blocks in a row with no PoW blocks. int64 nTargetSpacing = fProofOfStake? nStakeTargetSpacing : min(nTargetSpacingWorkMax, (int64) nStakeTargetSpacing * (1 + pindexLast->nHeight - pindexPrev->nHeight)); int64 nInterval = nTargetTimespan / nTargetSpacing; bnNew *= ((nInterval - 1) * nTargetSpacing + nActualSpacing + nActualSpacing); bnNew /= ((nInterval + 1) * nTargetSpacing); nTargetTimespan is hard coded to be 15 * 40 = 600. nTargetSpacing is being set to nTargetSpacingWorkMax which is 12 * nStakeTargetSpacing = 720. nInterval = 600 / 720 = 0 (because it is defined as an int, it is rounded down to 0) bnNew *= ((0 - 1) * nTargetSpacing + nActualSpacing + nActualSpacing); <<< From this point on, bnNew is negative because it is multiplied by -1 CreateNewBlock assigns nbits to a negative target. ProcessBlock will never accept the block because the CheckBlock fails when it calls CheckProofOfWork. Altering the nbits won't work because ProcessBlock will fail when it calls AcceptBlock and nBits != GetNextTargetRequired.
|
|
|
some active nodes: 128.199.109.210:18554 37.59.24.15:18554 192.99.13.67:18554
|
|
|
Source code still indicates 0.9.1, and clientversion.h has not been updated since launch. Does the the latest commit on the source reflect the correct logic for the block chain: https://github.com/MalibuCoinDeveloper/MalibuCoin/commit/9e0abfc2763f970ed752cf517fdeab37631cd46dSpecifically, was the last fork at 38000 to a 6 minute target interval: if (pindexBest->nHeight >= 38000) {nInterval = nTargetTimespan / nTargetSpacing *3;} // 6 min Or will people compiling from source (such as exchanges and pools) end up on a different fork than those using the windows wallet?
|
|
|
Appears to be a fork at block 10042. I am getting this when trying to re-sync:
received block 0000000000318adc9987 ERROR: AcceptBlock() : incorrect proof-of-work ERROR: ProcessBlock() : AcceptBlock FAILED
|
|
|
midaspool is down for few days...ok he is a scammer,coin is dead but i'd like to have my 200 mid :/ That will never happen. Since the re-write, only he can create blocks as the client was updated to require blocks to be signed by him, making only his blocks valid. According to https://www.bittrex.com/Status, it has been over a day since any new blocks have been generated. No one else can generate block, hence no one else can process transactions. Deposits to Bittrex, withdrawals... even sending MID from one person to another is impossible now. Horray for centralized block chain control.
|
|
|
quick fork-check...
litecoindarkd getblockhash 60601 e0af2e1512142adfc797ae3436e90d144a27811faf28dc6d5852aae61b141892
|
|
|
For those that missed it in the original thread, this might be helpful: Well, when this one goes belly up and the credit cards/gold that you ordered don't show up, send the police here: http://www.who.is/whois/midaspay.ioOwner : Giuseppe LiberatiOwner : Midas Payment LTD Owner : Fiume Delle Perle N. 19Owner : RomeOwner : NA Owner : IT
|
|
|
Which block does the new fork take effect? Code seems to indicate 32600, the 1.2 peers appear to be on block 32620 while the 1.1 peers (and bittrex) are over block 32700. Block explorer appears to have gotten stuck many months ago and is useless.
Did you actually try to hard fork on a block in the past?
|
|
|
wallet came on 36999 and blocked
This is the "fork" part of a hard fork. We have more miners on the old fork than the new one... Until someone on the new fork finds block 37000, we're not going anywhere. Anyone showing a height of more than 37000 in their wallet (including the block explorers *ahem*) are late to the update party... So... Bittrex has 37008. Did anyone bother to notify exchanges?
|
|
|
Please git pull the new updates from https://github.com/OmarxGx/HirocoinI have added additional rules to disconnect from the old client beginning at block 287,500. This should ensure that the hardfork will occur regardless of where the new block is solved as the old client will be invalidated. Great... but there are now 3 versions of the code on the network sporting the version number v8.6.5 70013 (and one v8.6.5 70012): Hiro's fork at 224000 (70012) Omar's fork at 285550 Omar's fork at 287550 Omar's fork at 287550 w/disconnect other versions It would be nice if you updated version numbers as you updated code, particularly when you are altering the block chain.
|
|
|
It looks like ConnectBlock is passing a pointer to the current block index to GetBlockValue. CreateNewBlock is passing a pointer to the previous block index to GetBlockValue.
This is causing them to generate different coinbase amounts, and ConnectBlock is rejecting the block created by CreateNewBlock.
|
|
|
New version stuck on block 285550 with error:
error: {"code":-1,"message":"CreateNewBlock() : ConnectBlock failed"}
+1, reindex doesn't help where's working block explorer? any valid seednode ? +1 debug.log: CreateNewBlock(): total size 1962 ERROR: ConnectBlock() : coinbase pays too much (actual=13400000000 vs limit=12500000000)
|
|
|
Yes, it looks like the wrong fork, I am showing a much higher diff for block 17389: litecoindarkd getblock $(litecoindarkd getblockhash 17389) { "hash" : "0d085a2fe6c923ed0934e7ed3fc1a9e6c83a2e14d16e9cb792e4e8ff020a351d", "confirmations" : 391, "size" : 249, "height" : 17389, "version" : 2, "merkleroot" : "1649077c6bce9da6a4180750be2628640425fb69088998feb0167547a47dab39", "tx" : [ "1649077c6bce9da6a4180750be2628640425fb69088998feb0167547a47dab39" ], "time" : 1411006751, "nonce" : 61017184, "bits" : "1c015ad8", "difficulty" : 188.94675196, "previousblockhash" : "3f52259181fde3495f4ac1e37f5c3fa1650f674a4db4a4dad8cbf32cd5b6fd79", "nextblockhash" : "0b185ae5faf08ae6f981619c12b3ea4c8484eb887bf6c53a2237bb918af984d7" }
Are you using the 1.1.0-pre 1 dev wallet? I am on linux, built off the source code from here: https://github.com/TrollByFire/LitecoinDark-UnofficialAlthough it looks like it has been merged into the official git repository: https://github.com/Litecoindark/LTCD
|
|
|
what is the official qt v. now ? my version 0862 is 2hours behind,,,, cant sync.
Can some please answer this one? litecoindarkd getinfo { "version" : 1010005, "protocolversion" : 70002, "walletversion" : 60000, ... "blocks" : 17757, ... "difficulty" : 976.87977690, These nodes seem to be on the bittrex fork: 31.130.93.203:11040 76.2.60.104:11040 203.219.236.44:11040 So my wallet on wrong chain?  { "version" : 1010005, "protocolversion" : 70002, "walletversion" : 60000, "blocks" : 17389, "difficulty" : 0.32708135, Yes, it looks like the wrong fork, I am showing a much higher diff for block 17389: litecoindarkd getblock $(litecoindarkd getblockhash 17389) { "hash" : "0d085a2fe6c923ed0934e7ed3fc1a9e6c83a2e14d16e9cb792e4e8ff020a351d", "confirmations" : 391, "size" : 249, "height" : 17389, "version" : 2, "merkleroot" : "1649077c6bce9da6a4180750be2628640425fb69088998feb0167547a47dab39", "tx" : [ "1649077c6bce9da6a4180750be2628640425fb69088998feb0167547a47dab39" ], "time" : 1411006751, "nonce" : 61017184, "bits" : "1c015ad8", "difficulty" : 188.94675196,
"previousblockhash" : "3f52259181fde3495f4ac1e37f5c3fa1650f674a4db4a4dad8cbf32cd5b6fd79", "nextblockhash" : "0b185ae5faf08ae6f981619c12b3ea4c8484eb887bf6c53a2237bb918af984d7" }
|
|
|
what is the official qt v. now ? my version 0862 is 2hours behind,,,, cant sync.
Can some please answer this one? litecoindarkd getinfo { "version" : 1010005, "protocolversion" : 70002, "walletversion" : 60000, ... "blocks" : 17757, ... "difficulty" : 976.87977690, These nodes seem to be on the bittrex fork: 31.130.93.203:11040 76.2.60.104:11040 203.219.236.44:11040
|
|
|
There appears to be a fork in the network, some nodes are reporting block numbers at 17723, others are reporting 17735.
Explorer is stuck at 16299, so it likely never got updated. This is what I get for block 17722:
litecoindarkd getblockhash 17722 c199d4c2c07d231d0e46323b763272ca94c0e13f4af069d7b704c72f579e143f
|
|
|
|