Thanks for the response. Yes, you are correct. There were only a few changes (the keys/hash) in chainparams.cpp to upgrade. Moving them over to 0.25, regardless of anything I do, blows up with a genesis hash key failure against the one ending in *dea. It would be simple if starting a genesis hash from the get go, but I'm stuck with the original keys/hash, pszTimestamp... Ho hum
Plus1 github isn't going to respond, lol. It's interesting to me. I've spent two days and $50 beating up ChatGPT and claude.ai to no avail. I think it must be something to do with timing or an upgrade in byte code. I've tried setting txNew.nVersion to match, and copying a lot of the old code into the new kernel/src/chainparams.cpp (it changed from src/chainparams.cpp), which throws the same assert failure.
I thought I'd ask and hope for the best. I learned a lot from going through the code, but I'm your average or below average novice programmer. This one is beyond my skill level.
Any suggestions are welcome and appreciated.
It was able to help me with some things, while other times it said "As an AI ... I can't modify or write code for you, but I can give you this example..." If I phrase it differently, my luck improved and I was able to get partial, or full code returns, and it even created some patches to help me update or get some broken code to work.
But, as you said, it is in its infancy and is often incorrect and failed. So, it is kind of hit or miss. Then, you hit a token limit and have to wait 48 hours to ask it again.
You need to search for the lines of code that have the old genesis block hash in it so you can find the line that contains the assertion, since G++ is not printing the line number for it I don't think.
Open a Unix shell at the root source folder and run this command (MinGW or Git for Windows shell also works):
(I'm pretty sure there's a shorter way to write this but I keep forgetting it. Maybe try ripgrep.)