That would solve their problem but what about the other users that do use these configs? When should they update them?
The reserve balance and the splitshareoutput are converted to satoshis when they are used so if we just update the COIN value at a specific time the converted amounts will not match the user’s config anymore.
A solution could be to always use the new COIN value to convert these config to satoshi (i.e. not wait for the switch time). So users would have to update their config when they upgrade and nothing would change about them at switch time.
The NSR custodian and fee votes. Internally the votes values are stored in satoshis so it’s not a problem, but the data feeds provide amounts in NSR. So the data feeds would have to update at the exact same time too. If the data feed providers use the votenotify config then we may trigger it at switch time to make sure they update.
But even so, if the clocks of the data feed provider and the node using it are not in sync, the amounts could be interpreted incorrectly.
But I guess data feed providers could just stop voting for NSR grants and fee a few hours before the switch.
There’s also the share day calculation. These amounts are expressed and stored as shares*days so the value would change. The easiest solution would be to continue to use the old COIN value for that, because I think nobody really cares about the absolute value as it’s mostly used relatively to other share days.
