deaconboogie (OP)
|
|
February 08, 2014, 06:00:10 PM |
|
My alt (Moon) is based off of Dogecoin's 1.3 release from mid-December 2013.
They've recently upgraded Dogecoin to 1.5 and because there was a desire from the Moon community to implement Kimoto's Gravity Well, I've forked Dogecoin 1.5 and have been implementing my customizations.
I was having problem with the wallet compile but that's beside the point now. I decided to test the 0.8.6 build headless to make sure everything is still working properly and I have run into a very strange issue that I can't resolve for the life of me.
By comparing Doge 0.6.2 and 0.8.6 it looks like all they did was copy the following variables from main.cpp for both main net and test net where applicable:
scriptPubKey pchMessageStart hashGenesisBlock block.nTime block.nNonce
I did change the PUBKEY_ADDRESS as well, ports, seed hostname, etc., but those seem irrelevant to this matter.
I clear my .mooncoin folder and launch mooncoind and it immediately segfaults with the following in the debug.log:
2014-02-08 17:09:20 Pre-allocating up to position 0x1000000 in blk00000.dat 2014-02-08 17:09:20 ERROR: CTransaction::CheckTransaction() : coinbase script size 2014-02-08 17:09:20 ERROR: CheckBlock() : CheckTransaction failed 2014-02-08 17:09:20 InvalidChainFound: invalid block=bd687cbbac4842724d4b1dfd2e1a6ce35d765db05635b3ebd3810ba66ac5aee9 height=0 log2_work=20.000022 date=2013-12-27 15:36:43
What's shocking here is that it is barking about an invalid block -- that invalid block is the hash root!
In Doge, the hash roots from 0.6.2 and 0.8.6 are the same, just as in mine!
I feel like I have to be forgetting something here but I can't for the life of me figure out what...
|
Mooncoin: 2F4E859vh1ezhpdDnMZdcR4hS1gLn54ytf BTC: 18S8XiKvFVhw6avx9tB21EHd3gNgomBFCK
|
|
|
|
|
|
|
Every time a block is mined, a certain amount of BTC (called the
subsidy) is created out of thin air and given to the miner. The
subsidy halves every four years and will reach 0 in about 130 years.
|
|
|
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
|
|
|
|
deaconboogie (OP)
|
|
February 08, 2014, 08:31:34 PM |
|
bump
|
Mooncoin: 2F4E859vh1ezhpdDnMZdcR4hS1gLn54ytf BTC: 18S8XiKvFVhw6avx9tB21EHd3gNgomBFCK
|
|
|
deaconboogie (OP)
|
|
February 09, 2014, 01:38:54 PM |
|
bump...
|
Mooncoin: 2F4E859vh1ezhpdDnMZdcR4hS1gLn54ytf BTC: 18S8XiKvFVhw6avx9tB21EHd3gNgomBFCK
|
|
|
aethieso
Newbie
Offline
Activity: 1
Merit: 0
|
|
February 09, 2014, 05:29:36 PM |
|
Is the code available somewhere? Can you send it to me? It'd be hard to try and debug it otherwise...
|
|
|
|
drepteck
Newbie
Offline
Activity: 42
Merit: 0
|
|
February 10, 2014, 12:22:09 AM |
|
I'm glad you are trying to figure this out. Bump for justice. Moon is way oversold.
|
|
|
|
michalbb
Newbie
Offline
Activity: 22
Merit: 0
|
|
February 11, 2014, 10:28:36 AM |
|
Well, what is with the MoonCoin Wallet Upgrade? Please let us know deaconboogie, or if you need help put the source somewhere to GitHub or whatever, we need to something with the MOON...
|
|
|
|
gavgav
|
|
February 11, 2014, 04:42:32 PM |
|
How's it going?? Please keep us updated!
|
|
|
|
deaconboogie (OP)
|
|
February 12, 2014, 08:35:56 PM |
|
I've heard from one of the volunteers that they may have had some success with the 0.6.2 to 0.8.6 upgrade.
Once I can get the source from them and confirm, I'll implement the Gravity Well (which was stunningly easy) and make the code available.
We will still need someone from the community to provide clean Windows and Mac wallet builds as soon as the code drops!
|
Mooncoin: 2F4E859vh1ezhpdDnMZdcR4hS1gLn54ytf BTC: 18S8XiKvFVhw6avx9tB21EHd3gNgomBFCK
|
|
|
deaconboogie (OP)
|
|
February 16, 2014, 02:36:42 PM |
|
Issue is resolved.
|
Mooncoin: 2F4E859vh1ezhpdDnMZdcR4hS1gLn54ytf BTC: 18S8XiKvFVhw6avx9tB21EHd3gNgomBFCK
|
|
|
kalisto2002
Newbie
Offline
Activity: 21
Merit: 0
|
|
May 04, 2014, 08:09:09 PM |
|
How did you end up fixing this?
|
|
|
|
Cosmorphic
Newbie
Offline
Activity: 2
Merit: 0
|
|
June 05, 2014, 01:33:58 PM |
|
I would also like to know how you fixed it.
|
|
|
|
|