Scores by kind of claim
Each kind of claim is scored on its own, out of 100: the share that held up, with the range it likely falls in. Fewer resolved claims give a wider range.
-
Factual claims
Statements about the present or the past, checked against the record: did they hold up?
72 65 79 -
Predictions
Statements about events outside the person's control, checked once they fell due: did they come true?
66 54 78 -
Promises
Commitments to the person's or organisation's own future action, with something to deliver: was it delivered?
Insufficient record: 1 promise resolved, 5 needed for a score.
All types combined: 71 (likely 64 to 77, high confidence), from 79 claims: 60 factual claims, 19 predictions. It mixes kinds of claim in different proportions for different people, so compare people kind by kind.
Balaji Srinivasan's claims
37 claims
“A site now has not just metadata, but a wallet.”
Balaji Srinivasan, writing on X 25 December 2019 Post by @balajis on X, 2019-12-25 (X)
A website with a .eth or other crypto domain can now hold a crypto wallet as well as metadata.
Mostly true True in substance, wrong in a detail.
The second judge would not resolve this claim; the verdict shown is the first judge's.
What would count as true or false
True: as of 25 December 2019, crypto naming systems (ENS .eth, or Unstoppable Domains .crypto) supported, in deployed form, a single domain name carrying both cryptocurrency wallet address records and website or content metadata (e.g. contenthash or IPFS records). Mostly true: this was supported but limited, such as only in one system, only for ETH addresses, or only through some resolvers or browsers. Mixed: wallet-address records and website or content records existed, but not usable together on one domain at that date. Mostly false: the feature was only announced or in testnet at that date, so 'now' overstates it. False: no crypto domain system supported wallet address records for domains by that date.
Evidence
- Linking DNS with blockchain-based ENS records - cdn.icann.org ICANN (slides by Brantly Millegan, ENS / True Names LTD)
“Address: Ethereum address - Content: IPFS or Swarm hash”
- Linking DNS with blockchain-based ENS records - cdn.icann.org ICANN (slides by Brantly Millegan, ENS / True Names LTD)
“Native integration in Opera browser”
- contenthash field for ENS | Ethereum Improvement Proposals Ethereum Improvement Proposals (ERCS)
“you can also find this smart contract deployed on: - Mainnet : 0xd3ddccdd3b25a8a7423b5bee360a42146eb4baf3”
- Introduction¶ ENS documentation (ens.readthedocs.io)
“ENS’s job is to map human-readable names like ‘alice.eth’ to machine-readable identifiers such as Ethereum addresses, content hashes, and metadata.”
Reasoning
E1 is an ICANN slide deck whose URL dates it to 24 June 2019. It lists an Ethereum address record and an IPFS/Swarm content record as ENS record types, so one .eth name could carry both a wallet address and site content. E2 says ENS had native integration in the Opera browser. E3 and E4 show that contenthash was deployed on mainnet and that ENS maps names to both addresses and content, though neither source is dated. The evidence shows support in ENS, with Ethereum address records alongside content records; it does not show support in other naming systems or for other coin types, and the criteria count support limited in this way as mostly true.
Cite this claim
Balaji Srinivasan, “A website with a .eth or other crypto domain can now hold a crypto wallet as well as metadata.” (said 25 December 2019). Verdict: mostly true. Reliability API, claim c_87c9d6a6c2e9, method 0.1.0+c876030c. https://epistacklabs.com/claims/c_87c9d6a6c2e9
Claims without a verdict
- Unresolvable 148
- Not yet due 21
- Own records only 2
- Not researched 227
- Not checkable 1,091
Is a verdict here wrong, or do you speak for Balaji Srinivasan? Reply on the claim's own page, with the form at its foot (how replies work). Verdicts are made automatically; how verdicts and scores are made.