{
 "holds": true,
 "cause": null,
 "recomputed_solution_seal": "48a015f7b3ea664c7041f6d46e7ce43f74a8241b17f1cb44c5d2c0e969936598ae08fffe87c85fdd411fb2f272b30f78",
 "recomputed_receipt_sha384": "87b338dd7fffc33d39fb0b5377ffe65329725aa59071f52a8bc156236018fec3263dfc0921c2be71c4dc3e0a1f335f1f",
 "compared": "The request was solved again and the solution_seal given was compared with the seal of that computation; holds is that comparison. The seal covers the request's values, so a request sent with a number spelled another way (310 and 310.0) has the same seal. No copy of the answer was read: recomputed_receipt_sha384, given when the comparison holds, is the receipt of the answer computed again, which equals the receipt of a copy only when that copy is byte for byte the engine's answer and the request was sent in the same text, number spellings included.",
 "text_not_compared": "The request was computed again and the seals compared. No answer text you hold was compared, so a copy with a decimal changed still holds here. To verify a copy of the answer, run verify_receipt on its exact text, which compares the copy's bytes with the receipt that same copy carries, and compare that receipt_sha384 with recomputed_receipt_sha384, which this tool returns when the seals hold. A copy is verified in full only when the two are equal, and they are equal only when the copy is byte for byte the engine's answer to the request sent in the same text. verify_receipt alone does not show that: the receipt is a plain SHA-384 with no key, so a copy with a decimal changed and its receipt worked out again matches it. The long form of this tool, given the whole answer as it came, computes its request again and compares the engine's answer with the copy, value by value and byte for byte, receipt included.",
 "chain_verified": "Every upstream run in 'from' was computed again and its run_seal compared with the seal given, and each handed value compared bit for bit with the upstream's sealed answer and with the request, before the request was solved again; holds covers the solution seal and the upstream runs. recomputed_chain_seal is the chain seal of the solve computed again, which solve's answer carries in chain.chain_seal.",
 "recomputed_chain_seal": "21a8ace2dc1223ed33f32f97173269980e469ca11d23bed4ccbcf41544fee9e55a3228621dd12a52452ffec09ddf80b1"
}