Was working in slack on this last night, and we have come to the conclusion that some nodes still contain a remnant of the bad gobject. Note that the python error you receive will definitely go away when this object is deleted:
1996fe78ce9efd7a3b6deefbcd2e120b75f850909ad8f702062a517b1cb27ae1
So please gobject vote-many 1996fe78ce9efd7a3b6deefbcd2e120b75f850909ad8f702062a517b1cb27ae1 funding no, then delete yes, then delete *.dat files except wallet.dat then resync. I believe this object is now fleeced out of the supermajority, as I see 90% of the sanctuaries are now staying in ENABLED state again. We just need to clear it out of the minority now.
I did double check that its not on any of my seed nodes also on windows - its gone.
Superblock, block 24600 coming sometime Friday, Im excited!
I've tried everything to get rid of that now, with no luck.. It's just stuck there.. I get success doing the funding and delete opertions, but no matter what happens the MN list of objects always has that in..
I've tried deleting everything bar the .conf files and wallet.dat, on both the controller and sanctuary.. Letting them catch, up performing the fund/delete, with success, but always the object is still there.. Even if after the fund/delete i delete everything from the controller as above, and restart..
I'm out of ideas, and starting to hope that this will all just go away with block 24600..