Maintain compatibility with upstream geth

[Varunram]

Over the past year, recent changes from geth have not been updated in go-musicoin. This doesn't contain any security critical stuff but it is necessary to maintain compatibility so that in the case that some future need arises, we must be able to patch relatively quickly. This carries a bounty, but not assigning an explicit bounty since this is big work. Please open a PR and we can assign the bounty after discussing.

[5chdn]

I've done this before, what's the bounty?

[Varunram]

Hey again @5chdn, it'd be amazing if you could rebase this on latest geth without the Constantinople hard fork and block reduction stuff of course (I guess you know already since you've done this before) Reg. bounty, I think we could start with a base bounty of 50000MC and then expand upon it in case it takes longer (or if you feel its not sufficient as well, no worries!) gmcs about 10 months behind, so we'd need to test consensus and what not. We're fine with a soft fork update as well, in case we can't get everything backward compatible. I'm over at slack in case you need something, thanks!