Suppose you exchanged your current body for an artificial one… Would you leave out the fun parts?
Those addresses can change arbitrarily often. Depending on what it is that you are actually trying to achieve with measures like this, you could do something that doesn't involve shoehorning an infrastructure detail into a security policy.
You might be able to simply ask DNS for the current IP addresses. If done regularly, you basically give control over your security perimeter to anyone in a position to influence nameserver responses, which might or might not be something you want.
Hopefully, it sold more on consoles. Otherwise, numbers like this could kill a fledgling studio outright.
This is so, so phenomenally inappropriate, that it's frankly impressive.
Poor child. Imagine that happening to you every two hours.
"come back with more money"
This is a good clarification. Indeed, ideally you'd want to put your money into that higher-interest vehicle as soon as possible, so basically, the same day you get paid.
In the limit, if you were to receive income once a year, you'd put that into savings immediately, which is maybe on January 1st, or earlier or later, depending on when your actual payday really is.
If you get a windfall, you'd also not want to let it linger on your current account for (next to) nothing, but put it to work as soon as is feasible.
Without starting to calculate, or looking at the code, I'd say it's obvious that an investment strategy where all of a month's contributions are made on the first day of the month will be superior to one where you spread them out. Also, an investment strategy of making the month's contributions on the last day will be inferior to spreading them.
So it'd really depend on how you time your monthly investments. If you can invest as soon as you get your monthly income, that's probably the most beneficial way to do it.
edit — Taking a quick look at your code, that's exactly what's happening. In each period, ChatGPT invests first, then lets interest accrue, whereas you let interest accrue, then invest.
If a mountpoint wasn't an empty directory before mounting another filesystem on it, the contents of that mountpoint will be shadowed by the contents of the other filesystem. So, if you mount other filesystems onto the one in question, this could cause your discrepancy, since the files are still there, just not present in the virtual filesystem tree. It's a common practice to set your mointpoints to immutable after creating them for this reason.
Somewhat more uncommonly, ext[234] allow the administrator to reserve a number of blocks for use by, in most cases, root — maybe you tune2fs'd your filesystem with some crazy value?
Nun ja, bei TSMC gibt's 28nm jetzt seit zwölf Jahren.
Das kann aber für Leistungselektronik dennoch mehr als okay sein. Wenn Hauptabnehmer wirklich die Automobilbranche werden soll, wäre ein neuerer Prozess unter Umständen nicht besser (nur teurer).
edit — Kosten pro 100 Mgates, je nach Strukturbreite: 
You could always try NixOS.
Arch may not be particularly easy to use, but it's a simple system, in that you can build a mental model of your entire setup with a fraction of the effort and time that you'd need to expend with other systems. It gives you the standard Linux experience without fuss, or handholding.
Nix, however, gives you several capabilities that other systems won't, but you're paying for that through its learning curve.