Condense receipt / Solana mainnet
Receipt
Qwen2.5-1.5B-Instruct answered a prompt and the hashes of both were committed on Solana mainnet at 2026-10-07 21:00:57 UTC. Re-run it below and compare the hash yourself.
Answer
Prompt
KORTX emitter prompt v1 (emitter-prompt-v1). Emitter: Cold Plate Disposition: bias down; horizon 4 hours; conviction threshold 60 of 100. Disposition hash: f55c49ce900ed8a0917a23e741a67e11752b9cd4cfe0e590980194ca23b6046a Snapshot time: 2026-10-07T21:00:28Z Source: Coinbase Exchange public 1-minute candles. BTC (BTC-USD), last 8 one-minute candles, oldest first (UTC time, open, high, low, close): 20:52, 83345.14, 83352.05, 83325.83, 83331.06 20:53, 83331.06, 83346.28, 83321.61, 83346.27 20:54, 83346.28, 83349.96, 83346.27, 83349.95 20:55, 83349.95, 83360.47, 83349.95, 83359 20:56, 83359, 83371, 83347, 83370.99 20:57, 83370.99, 83371, 83361.38, 83367 20:58, 83367, 83403.25, 83367, 83388.02 20:59, 83391.74, 83402.25, 83365.52, 83382.81 Task: say whether one of these assets will be higher (UP) or lower (DOWN) 4 hours after the snapshot time than its last close above, or say NONE. Reply with exactly two lines and nothing else: CALL: <ASSET> UP or CALL: <ASSET> DOWN or CALL: NONE CONVICTION: <whole number from 0 to 100>
CALL: BTC UP CONVICTION: 85
Recomputed in this browser
The text on this page, hashed here with KCF-1 strict and compared with the committed hashes in the record. The input hash covers more than the prompt: the model, the runtime, the system prompt and the decoding settings are all inside it.
Answer against the output hash
HashingPrompt against the input hash
HashingRebuilt from the model declaration stored when this trace was committed.
Record
- On-chain statusread from chain by the service
- committedStored answer matches the chain. Stored prompt matches the chain.
- Accountthe trace account on chain
- Account open -- rent returns to the provider after the challenge window closes (2026-10-08 21:00:57 UTC).
- Input hashKCF-1 over model, prompt, decoding
- Output hashKCF-1 over the answer
- Model
- Qwen2.5-1.5B-Instruct
- Weights fingerprint
- Plate
- Transaction
- Committed
- 2026-10-07 21:00:57 UTC
- Server time
- 28,242 ms, run to confirmed commit
Re-run
Send the committed trace back through the same weights with the same decoding settings. If the model is deterministic, the new answer hashes to exactly the committed output hash.
Earlier re-runs
Kept by the Condense server. Same-server re-runs are not written to chain.
Nobody has re-run this trace yet.
If this record does not hold up, a bonded challenge puts the trace in front of independent verifiers. It is an on-chain transaction signed by your wallet.
Open for 22 more hours, until 2026-10-08 21:00 UTC.