The same 'filtered block' line (but different hash) in the last crash too. Perhaps something wrong with whatever filtered block handling is?
CMerkleBlock is used for filtered nodes. It holds a CBlockHeader. This is assigned in CMerkleBlock::CMerkleBlock using GetBlockHeader. This function doesn't copy the auxpow field. This is possibly why the null pointer accessing auxpow occurs. Possible fix:
Code:
diff --git a/src/main.h b/src/main.h
index bd21fe9..1221a88 100644
--- a/src/main.h
+++ b/src/main.h
@@ -1411,6 +1411,7 @@ public:
block.nTime = nTime;
block.nBits = nBits;
block.nNonce = nNonce;
+ block.auxpow = auxpow;
return block;
}
I'll put this test in production and see what happens.
Thanks! Keep us informed.
Shout out to cinnamon, you are my hero. 
and would make an excellent addition to the board. I vote yes with a triple z snap ending over the shoulder.
I will donate to the person that adds in the counterparty code to ix. But only after it is added in.
It appears that friction wants 25k and already has 5k. If counterparty code goes in, then ix will easily be worth atleast $1. The gains alone will give you your remaining 20k easily friction. And you'll most likely STILL get a bounty.
And when ix goes to $1 we will all have more $ to give as tips. ie: let me give you some of my future profits, in the future
So, really it's a win win win win situation. You'll get the $ you ask for friction, but you'll also get all of the GLORY. Think about it...
Friction the mighty dev of counterparty ix, assured a place in crypto Valhalla.
Do it
Do it
Do it.
Please?? Pretty Please with a cherry on top!?
and would make an excellent addition to the board. I vote yes with a triple z snap ending over the shoulder.I will donate to the person that adds in the counterparty code to ix. But only after it is added in.
It appears that friction wants 25k and already has 5k. If counterparty code goes in, then ix will easily be worth atleast $1. The gains alone will give you your remaining 20k easily friction. And you'll most likely STILL get a bounty.
And when ix goes to $1 we will all have more $ to give as tips. ie: let me give you some of my future profits, in the future
So, really it's a win win win win situation. You'll get the $ you ask for friction, but you'll also get all of the GLORY. Think about it...
Friction the mighty dev of counterparty ix, assured a place in crypto Valhalla.
Do it
Do it
Do it.
Please?? Pretty Please with a cherry on top!?
Let me sum up what is going on:
FrictionlessCoin offered to add Counterparty to iXcoin in exchange of 25k IXC.
So far FrictionlessCoin has received 5k IXC.
JohnnyBTCSeed has offered to donate ixc when the job is done (not clear if he meant the remaining 20k ixc)
In the meantime Cinnamon_Carter has added minor improvements to ixc wallet.
mmpool is straggling with errors generated by iXcoin client.
So, I wonder:
- Has FrictionlessCoin officially accepted the task to add Counterparty? If yes, have we a deadline? If no, is there anybody available to do it? (I hope FrictionlessCoin accepts the task)
- Is the update going to bring iXcoin to the same update 0.9.1 of Bitcoin?
- Is the Counterparty feature going to affect the compatibility of iXcoin with Bitcoin's future updates?
- Are these errors going to delay the addition of Counterparty feature on iXcoin?
In terms of priority, we need to fix this problem first.
Have not started the CounterParty port yet.
Counterparty feature is only dependent on the OP_RETURN feature that has been crippled by Bitcoin devs. That is why Counterparty price is sinking like a rock.
Yes, we need to fix this.
Note: Any new feature is dependent on the pools to accept the new client. So I can add any new feature I want, but many of the features won't be enabled unless the pools accept the changes.
You know.... just occurred to me... it may be possible to add features without updating the clients that GHASH.IO uses... need to do some research on this.
