Launching beacon sync in Trin requires always passing a valid trusted block root via CLI on every startup.
This is not very feasible because if the client has been synced recently, it should already have a valid bootstrap stored in the database. We can use this bootstrap to start syncing on the next run, without expecting the user to provide a trusted block root again, as long as the bootstrap is in the weak subjectivity period.
ogenev
commented
3 weeks ago
Launching beacon sync in Trin requires always passing a valid trusted block root via CLI on every startup.
This is not very feasible because if the client has been synced recently, it should already have a valid bootstrap stored in the database. We can use this bootstrap to start syncing on the next run, without expecting the user to provide a trusted block root again, as long as the bootstrap is in the weak subjectivity period.