I realize now that the device these errors were comming from has since been completely reset, including the uSD that had my /gnu/store. Therefore, I can no longer reproduce this error. In hindsight, I don't believe I ever ran 'guix gc --verify=contents,repair'. My best guess is that the guix package itself was corrupted during an inconveniently timed poweroff.
Since there is nothing to debug anymore, I suppose there is nothing to do but close this issue. I don't remember the debbugs close message format, so someone else will have to do it, but some final thoughts on my end: A compromised guix binary can propagate bad behavior. Guix streamlines the ability to check binaries, so if a clean guix tried to download a bad archive, it could be detected. But what if a build server was compromised by making additional malware archives available under hashes which would never be found by a clean guix?. You would see your client only downloading from bona-fide guix servers trusting that some clean guix would have challenged faulty archives, when that's false. Since you can't get the recipe from the hash, you can't verify an archive with a clean guix unless you seperately already have the recipe, which a clean guix wouldn't have. -Zacchae
