KeyVaults are not XDK pairing tokens
About once a month someone asks whether they can “put a KV on the kit” to make it go Live like a Slim. That sentence mixes two ecosystems. An XDK has its own recovery and pairing story. A retail KeyVault is the identity blob inside a retail NAND. Copying kv.bin onto a kit because a Corona RGH3 guide mentioned PicoFlasher is how you spend a weekend in Neighborhood with a brick-shaped fan.
Where kv.bin actually belongs
On a retail JTAG/RGH3, after a ban, a shared identity, a sale, or a second box you refuse to clone, people replace the vault in a NAND rebuild. That process is documented in retail flashing communities, not in XDK recovery manuals. If that is the job you have, you are not in kit-land. You are in CPU key + dump + xeBuild land — the same land Bad Update dumpers enter when Simple 360 NAND Flasher runs after XeUnshackle.
I keep a retail-side bookmark for that exact workflow: the Xbox 360 KV change writeup on UnsharedSHOP. It is aimed at RGH/JTAG retail boxes, which is the machine most “unban my kit” emails actually describe once you ask for photos. Homebrew-only kit owners still should not apply that file to studio NAND.