I think the key would have to be dynamic not fixed, but I think it’d work. E.g. sandbox-escape-bounty-operator makes a keypair, publishes their public key widely, and has an http endpoint where you pass any string and the operator will sign that string, and then in the RL env the model gets the instruction that if they are able to complete the task or get [random per-task string] signed by the sandbox-escape-bounty-operator that counts as success for the task.
And then actually train the model on obtaining a signed token from the sandbox-escape-bounty-operator, and the steps for verifying that they do in fact have a correctly signed key.
I think the key would have to be dynamic not fixed, but I think it’d work. E.g. sandbox-escape-bounty-operator makes a keypair, publishes their public key widely, and has an http endpoint where you pass any string and the operator will sign that string, and then in the RL env the model gets the instruction that if they are able to complete the task or get [random per-task string] signed by the sandbox-escape-bounty-operator that counts as success for the task.
And then actually train the model on obtaining a signed token from the sandbox-escape-bounty-operator, and the steps for verifying that they do in fact have a correctly signed key.