Request: supported raw Cache export for v1.2.2 conformance testing

[haroldgjc-cloud]

Context

I am working on external conformance verification for a clean-room RandomX v1 implementation. The first comparison target is the initialized RandomX v1.2.2 Cache byte image.

The public v1.2.2 C API provides randomx_alloc_cache, randomx_init_cache, and randomx_release_cache, but there is no Cache-memory getter analogous to randomx_get_dataset_memory. The reference benchmark also does not appear to have a raw Cache export mode.

For provenance reasons, I do not want to recover the bytes through debugger scraping, allocator interception, assumptions about the opaque randomx_cache layout, or other private-ABI techniques.

Request

Is there an existing maintainer-supported way to export the initialized v1.2.2 Cache memory? If not, would the project consider a small source-level conformance helper or supported API/CLI path that:

1. Initializes the v1.2.2 Cache using a zero-length key (not a four-byte all-zero seed).
2. Writes exactly 268,435,456 bytes:
   • 262,144 ordered blocks;
   • 1,024 bytes per block;
   • each block represented by its 128 little-endian 64-bit words in algorithm order.
3. Allows the producer to retain the exact RandomX revision, build command, OS/architecture/compiler details, and raw-file SHA-256.

A pointer to an already supported mechanism would also fully answer the request.

This artifact would be used only as a byte-for-byte conformance input. A matching digest would not by itself be described as independent review or provenance attestation. No Dataset export or mining integration is being requested.

[haroldgjc-cloud]

Progress note: I found a source-level path in XMRig v6.25.0 that uses its public caller-owned Cache API (upstream commit 753859caea40cd645eacb9049cf94a8104d63f43).

An isolated helper allocated exactly 268,435,456 bytes, called randomx_create_cache(flags, memory), initialized it with a non-null pointer and zero-byte key length, released the wrapper, and hashed the caller-owned memory. Two runs were byte-identical.

• raw Cache SHA-256: f8fa350faf0dfd69f4e8b3d452e49aada2ccdffebb1986e790bb69b405a2915b
• checkpoint BLAKE2b-512: 0db3bc50bf8945927cc6a8187683fb671acc33956762841bcd5872ae352322a2e70fb21ecbbd5883cb9cdfd5222fa4223772010b5a1d0d74eccab0949ae597d2

This matches the candidate checkpoint package. I am treating it only as an unreviewed producer claim until an independent reviewer checks the source, build, environment, artifact, and provenance.

This does not replace the request here: upstream RandomX v1.2.2 still has no documented public raw-Cache export path, so I’m leaving the issue open for maintainer guidance.