RUNECLAW BotChainSeal

BotChainSeal verify

Bohr testnet page · Seal a file · botchain.ai · scan.botchain.ai

How it works / Help

Steps

  1. Paste a receipt hash, or hash a file locally. A hash is 0x followed by 64 hex characters. Choosing a file computes the Keccak-256 of those bytes in this browser; the file is never uploaded.
  2. Press Check. This page sends public, read-only RPC calls to rpc.botchain.ai and nothing else. No wallet, no key, no tracking.
  3. Read the result. The result box is a new live read of the contract, not the published record in the table below.
    • Anchored: yes means this read found the hash stored by the listed publisher under the listed kind. It does not make the file a trade or a true statement. Hash your own copy and compare. The chain does not store the file.
    • Not anchored means this read does not find the hash in the contract. A published record in the table can still name a hash that this read does not show as stored.
    • Could not check means the chain was not read. A failed read is not a "not anchored" result.
    • Not a valid hash means the input was not 0x plus 64 hex characters; nothing was asked of the chain.

FAQ

Is a file uploaded?

No. The file is hashed in this browser. This page's only network use is public RPC reads to rpc.botchain.ai.

Is this testnet?

No. This is the BOT Chain mainnet page (chain 677). The Bohr testnet verifier is a separate page, chain 968.

Deployment

Contract0x2554160560747dF51873171FBD838bbDEEdf9093
Deploy tx0xc40e34faa530d2318c6658681471fb64cb2a5a6c4382fbe082066a5d16ca9640
Owner and publisher0xd229cab8bE1a674802DA9Fa847CFEdD7eAb7f11F
First receiptPublished record, separate from the live check above. Hash 0x2f614d352a37752099e719b685c2b6ea86d3b98904810ebc6d3784312fe081e5, kind claw-guard. Seal tx 0x2a6e494dad3eb2798433d683cba83ac94fb9bb2a8dfe8f75d8a775d6befb57ed, block 29311093. The sealed file still contains the word Proposed. Those bytes are the commitment. This table does not re-read the chain.
Second receiptPublished record. Hash 0xdeedaf1bae457ec341a34af3b5920f5fc821b696cd19439a0e4bc8b857188d06, kind claw-guard, same publisher. Seal tx 0x7627bf71be3f1b54403ba88b9f901deeaa9ca5970374172b8361cd225fa58d5f, block 29320661. The file behind this hash is not in this repository.
Functions readisAnchored(bytes32), anchorOf(bytes32), event Anchored
RPChttps://rpc.botchain.ai

This page cannot sign. A wallet seal page is at seal.html. The keystore command python3 -m botchain_seal mainnet-publish remains available and still signs only for chain 677.

The result box is a new read of rpc.botchain.ai. It can say not anchored, or fail, even though the receipt above was published. A "yes" means this read found the hash stored by the listed publisher under the listed kind. It does not make the file a trade or a true statement. Hash your own copy and compare. The chain does not store the file.