To show a regulator exactly which code handled a piece of data, run the code in an attested hardware enclave and have it sign every result with a key that belongs to that exact code. On Lit Protocol, a Lit Action is identified by a hash of its source, and every action has its own signing key that the enclave derives from that hash. If the code changes by one character, the hash changes and so does the key. So a signed result is a receipt that names the code that produced it, and anyone can check it later without trusting you.
I will build a small screening check that returns signed receipts, and then go through how a regulator verifies one.
A check that signs its own receipts
This action screens a customer against a sanctions service and returns a receipt.…