Hey! I'm new to the Gridcoin scene, so I'm still trying to figure some things out. I've got everything up and running, I just want an elaboration on a few things, mostly from the container logs:

2024-06-12T07:13:15Z INFO: GetTimes: timer init: Starting verify of database integrity: elapsed time: 11 ms, time since last check: 11 ms.
2024-06-12T07:13:15Z dbenv.open LogDir=/root/.GridcoinResearch/database ErrorFile=/root/.GridcoinResearch/db.log

So the ErrorFile I have, db.log, is 0kb. You might not want to mention this unless there is an error that would give someone a reason to look at the file, or it could confuse people

2024-06-12T07:13:22Z INFO: InitializeContracts: Loading stored history for contract type beacon...
2024-06-12T07:13:22Z INFO: InitializeContracts: Initializing registry from stored history for contract type beacon...
2024-06-12T07:13:22Z INFO: InitializeContracts: History load not successful for contract type beacon. Will initialize from contract replay.
2024-06-12T07:13:22Z INFO: InitializeContracts: Loading stored history for contract type project...
2024-06-12T07:13:22Z INFO: InitializeContracts: Initializing registry from stored history for contract type project...
2024-06-12T07:13:22Z INFO: InitializeContracts: History load not successful for contract type project. Will initialize from contract replay.
2024-06-12T07:13:22Z INFO: InitializeContracts: Loading stored history for contract type protocol...
2024-06-12T07:13:22Z INFO: InitializeContracts: Initializing registry from stored history for contract type protocol...
2024-06-12T07:13:22Z INFO: InitializeContracts: History load not successful for contract type protocol. Will initialize from contract replay.
2024-06-12T07:13:22Z INFO: InitializeContracts: Loading stored history for contract type scraper...
2024-06-12T07:13:22Z INFO: InitializeContracts: Initializing registry from stored history for contract type scraper...
2024-06-12T07:13:22Z INFO: InitializeContracts: History load not successful for contract type scraper. Will initialize from contract replay.
2024-06-12T07:13:22Z INFO: InitializeContracts: History load not successful for contract type sidestake. Will initialize from contract replay.

I'm not sure what all of this means. I've already set up my beacon on a separate device - it's been up for 7 days, so I don't think the problem is that it just hasn't been checked or it needs time to update or something

2024-06-12T07:13:22Z BOINC team requirement active at last known block. Whitelist: gridcoin

Not sure what this means either. I am in the gridcoin team in my current project, asteroids@home, and I have submitted a few thousand work units

2024-06-12T07:13:22Z Gridcoin: checking for updates every 120 hours
If Gridcoin itself (not this container, but the Gridcoin program itself, that the container is running a headless version of) updates, will this container still be compatible? Does the container auto-update Gridcoin? Or will I need to wait until the container is updated? Come to think of it, is the container still maintained? A lot of the files were last updated 2y ago, but it could just be that they haven't needed to be updated for two years

2024-06-12T07:14:32Z ERROR: CheckForLatestUpdate: Exception occurred while checking for latest update. (Failed to get version response from URL https://api.github.com/repos/gridcoin-community/Gridcoin-Research/releases/latest: Timeout was reached)
Should I be worried about this? I can't imagine why I'm timing out here. I just pulled the container today, so naturally I'm going to be on the latest version anyway- if an update is pushed, does this really mean I don't have to go through docker's usual "pull the latest image and redeploy" song and dance?

A few questions: This container doesn't do any of the actual BOINC crunching, right? I copy/pasted my BOINC data folder into the container's mounted volumes. I would actually prefer not to do any BOINC-ing on this device, but I'm not sure how to, like, "tell the container" that

Also, is there any way (maybe through the CLI or a GUI later) to do a manual reward claim (MRC)? This is a pretty important feature since it's what makes solo crunching viable for newer users. If you don't have it, you'll need to have the Gridcoin program on another device, and keep its blockchain updated, in order to send in MRC requests

Lastly, a small feature request would be, at the end of all of this, some kind of, like, "Hey, the container is working and everything is clear. You're all good!" or "Oh no, we couldn't connect to your wallet" or "Hold tight, we're syncing the blockchain" type line at the very end would be a great way of just, making sure the user is on the same page about whether everything is working or not. Since it's headless, people probably want it to be a pretty set-and-forget process, but it would be great to have it spelled out before the 'forget'