explorer.render-html — every row below was produced by running the real OperationActor, holds included.
| op | subject | disposition | basis | detail |
|---|---|---|---|---|
index | block-102 | commit | number, hash, parent-hash | committed |
index | block-103 | hold | corroboration-gate | 独立ノードの裏取りが不足: agree=1 endpoints=1 required=2 |
assert | 0xdemoc3 | commit | attribution | committed |
assert | 0xdemod4 | hold | attribution-gate | 帰属の出典が無いか再検証可能なクラスでない: nil |
assert | 0xdemoe5 | hold | identity-gate, attribution-gate | 自然人への紐付けは恒久的にスコープ外（人的承認でも解除不可）: [:person-name] |
query | 0xtx1 | hold | finality-gate | 実際の finality (probabilistic) より強い主張 (final) はできない |
query | 0xtx1 | commit | hash, block-number, from, to, value, confirmations, finality | committed |
Labels are accepted from 5 re-checkable classes only (self-attestation, entity-published list, sanctions publication, verified source, on-chain registry). Heuristic clustering, vendor risk scores, social reports and LLM inference have NO class to cite and are structurally unpublishable. Linking an address to a natural person is refused outright, with no human override. Chain data itself (blocks/txs/logs) is not an attribution and needs no class — it needs corroboration and a finality class instead.
onchain-self-attestation — On-chain self-attestation by the address itselfofficial-published-address-list — Address list published by the entity itselfsanctions-list-publication — Official sanctions authority publicationverified-contract-source — Deployed bytecode verified against published sourceprotocol-registry — On-chain canonical registry answers for the addresschain-analytics-scorecommon-input-ownershipforum-reportheuristic-clusteringllm-inferencepattern-inferenceself-reported-unverifiedsocial-reportvendor-risk-score自然人への紐付け: never（人的承認による解除経路も無い）