published on March 10, 2025 in devlog
Michi talks about the infrastructure upkeep system.
Michi (molp)
As stated in the last devlog (#473), I continued to work on infrastructure upkeep. As usual, I tried to implement the upkeep mechanism in an infrastructure agnostic way, so we can reuse it for future infrastructure projects and not just the upcoming gateways.
Similar to the CoGC, there will be upkeep phases that last one week. Once a new upkeep phase starts, the upkeep mechanism will try to consume the necessary materials from the dedicated upkeep store automatically. The infrastructure owners (the local government) will receive a notification about the new upkeep phase. That notification also doubles as a reminder to make sure that there are enough upkeep materials in stock for the coming upkeep phases.
In contrast to the CoGC, it is not necessary to assign the individual materials. If there aren't enough materials to satisfy the upkeep, the upkeep mechanism will consume as much as possible. In that case, it will also send out a notification to the owner about the missing upkeep. It then sets the "upkeep missing" operational state. A gateway, for example, will stop working if it enters that state. Once the missing upkeep materials have been provided, the state will go back to "operational" and the gateway will resume its work.
In devlog #462 I showed a work-in-progress screenshot, how this could look like in the APEX interface.
The next steps are to connect motions, contracts and the shared stores, so that a government can appoint a contractor that is responsible for the upkeep.
As always, we'd love to hear what you think: join us on Discord or the forums!
Happy trading!