Thanks, I've imported all these. I've also finished importing the caches from K4rn4ge and Flenarn.
I've also made the following changes to the software:
* Added an option for exporting XTEA keys as a zip of .txts (the classic format with four decimal integers across four lines).
* Added a keys page (
https://archive.openrs2.org/keys) allowing all keys in the database to be exported in bulk. This might be useful for people who already have XTEA key validation tools they want to run against a local copy of the cache (if you have a local copy of a cache not in the database, I'd still appreciate receiving a copy though!)
Finally, I've added (very rough at this stage) support for plotting the valid/invalid keys on a map, making it easy to visualise which builds have a useful set of XTEA keys and which don't. Plotting the maps is fairly expensive memory-wise, so please don't abuse this endpoint - I'm probably going to look at caching them on the nginx side.
Here's a cropped example of what these map images look like:
The map squares with green outlines have known keys or aren't encrypted. A grey outline/background means we don't have the key, but can infer that the map square contains no objects because of the size of the encrypted group (we can replace these with empty unencrypted loc groups). A red outline/background means we don't have the key (and the map square is not empty).
These maps can be generated for any cache in the archive (though there are a few niggling bugs in some cases that I'm still looking into), just click the "Map" link under "Download".