THOT · the on-chain anchor for mindX wisdom

Where is the contract deployed and is mindX configured to interact with it? THOT_CONTRACT_ADDRESS, THOT_CHAIN_ID, and THOT_RPC_URL set together = green. THOT_MINTER_KEY set = mint-ready. Without these the page renders honestly as not-yet-deployed; the dimension standard and the wisdom queue (below) still work because they don't require a chain.

The uint32 dims values the contract accepts via mintTHOT(...). Anything else reverts with "Invalid dimensions". The standard is modular — extending it requires changing only _isValidDimension() in the contract. Quantum-resistant tiers (≥65,536) are theoretical reservations.

Tail of data/logs/catalogue_events.jsonl filtered to wisdom.minted (THOT mints) and memory.anchor (broader on-chain anchors via the ARC DatasetRegistry). Click ⋯ for the full event payload. Once Phase 3 of the cognitive ascent plan ships, every verified wisdom becomes a row here with its tx hash, CID gateway link, and explorer link.

Wisdom records that have been verified but not yet minted (e.g. THOT_MINTER_KEY missing or RPC unreachable). They wait here losslessly; when the minter key arrives, a periodic drainer flushes the queue. Each row shows the premise, conclusion, confidence, verification count, and target dimension.

Paste an IPFS CID to check whether mindX has anchored it. First search is the local catalogue stream; once chain RPC is configured, it also calls cidExists(bytes32) on the contract directly.