I posted this on the FCN thread, but figured the dev here might have insight --
Is there a chance that FCN merge-mined blocks in the donor chain are breaking the MRO wallet?
I'm unable to create new transactions on my wallet after successfully mining a donor chain (MRO) block.
Tracing the error back a bit, it's getting a "Derived public key mismatch" error in construct_tx. I haven't gotten farther than that, but hoped that an FCN or MRO dev might be able to check more quickly than someone who doesn't know the code.
block 36387 is the merge-mined one. Or could this be something else?
(Regardless, it's a little scary - i can't send transactions out of my wallet if they include whatever "bad" entry is in there)
Thanks!
I'm not a dev or anything but the troubleshooting steps I'd try are:
0) Close your wallet/daemon down
1) Find your blockchain.bin file, and rename it blockchain.bin.old
2) Replace it with a fresh blockchain.bin from the OP of this thread
3) In your daemon folder, rename your wallet.bin to wallet.bin.old
4) Relaunch your wallet & daemon
5) Refresh your wallet
Hopefully this will sort your problem, otherwise it'll need addressed by someone with more technical know-how than me.
Alas, I tried all of those, up to and including a fresh compile of the source tree on a different machine.
Ah! Finally got the log entries right:
failed to deserialize extra field. extra = 01fb88353
401fea28611f98174830a3ee193cf1808443f041875f3e034cb370e1903210001b73c46f45dddbf
8
31505271ad567a93cd797e4e8e675d94271b6a067c6fea902080000000000000000
This is definitely a result of the merged mining.
Now the $1000 question is: If I fix it in my wallet and start sending out transactions with it, will it break the entire blockchain, or will it be just fine? *grins*