FACTA Check

Check FACTA yourself

Every project asks to be trusted. This page lists what FACTA does and never does, and for each a way to check it that does not go through FACTA.

  • It never holds, moves or manages anyone's funds, and it holds no key that controls funds.
  • It never deploys a contract. It reads contracts others deployed, and writes on chain only two things: status entries to an existing registry, and one anchor a day that calls no contract (below).
  • It never places, builds or routes a trade.
  • It never sells or adjusts a result. A paid check is published whatever it finds, and the one who paid cannot edit, delay or withdraw it.
  • No payment, token balance or vote leads to a status: no field of its data model connects one to the other.
  • A wrong result is corrected in public: the correction keeps the history and says what changed (corrections).

Contracts FACTA reads on Robinhood Chain (chain ID 4663)

ContractAddressWhat FACTA reads there
ERC-8004 Identity Registry
0x8004a169fb4a3325136eb29fa0ceb6d2e539a432
Every identity's owner, agent wallet and registration URI.
ERC-8004 Reputation Registry
0x8004baa17c55a88189ae136b182e5fda19de9b63
Where a filed agent's status entries are written, and read back.
Pons V2 launch factory
0x7ed598bcef8bd9edd8c97a195c6d13f40801ec7e
A token's launch record: its deployer, its creator fee recipient and its creator tax.
USDG
0x5fc5360d0400a0fd4f2af552add042d716f1d168
Transfers, for an agent's income and for payments.
Uniswap v4 PoolManager
0x8366a39cc670b4001a1121b8f6a443a643e40951
Swaps and liquidity of the pools a token trades in.

Every figure FACTA publishes names the call, the log or the HTTP response it rests on, and the block or the time it was read at, so any of them can be read again from a public endpoint. The methods say which reads each figure takes.

FACTA writes two things on chain, both from one attester address, published here and on the status method before its first write: 0x49bcf8323fc89aaea6a7b54a3a3088893b49f3d3. It holds only the ETH its transactions cost, and owns and operates no agent.

  • A status entry in the ERC-8004 Reputation Registry, for an agent that filed for a charter. An entry names its status document by its hash, so a contract or a reader can compare the two, and the agent's charter page shows each entry FACTA wrote.
  • One anchor a day: a transaction from the attester to its own address, which calls no contract and moves no funds. Its data is one line of text, FACTA anchor 1 <day> <count> <root>: the UTC day, how many documents FACTA stored that day, and the Merkle root of their SHA-256 hashes. It shows that each of those documents existed no later than the block that holds the transaction, sent once the day is over, and has not changed since.

To check a document against the chain: GET /v1/anchors/hash/{hash} gives its day, the transaction and the steps from its hash to the root; GET /v1/anchors/{day} lists every hash of the day. The root is rebuilt from the hashes in ascending order, as 32-byte values, each pair hashed as SHA-256 of the left one then the right one, an odd last one moving up unchanged. Read the transaction from any endpoint of the chain: its data, as text, is the line.

An agent that did not file gets no entry, and an anchor names no agent and no token: what FACTA finds about them stays on this site, with its evidence.

  • A document is its hash. Every report is a JSON document named by the SHA-256 of its bytes. /verify fetches one and hashes it in your browser, or hashes a file you hold, sent nowhere.
  • A method has a version. Each method is a public page with its version and its thresholds: the methods. A result names the method and the version it used.
  • A notice is never edited. A wrong notice is corrected by a later one that names it: the notices.
  • The vocabulary is fixed. Every term FACTA can return, with what it means: the vocabulary.
  • Not public yet: the code, with the scripts that rebuild each figure from the chain. Until it is published, a figure is checked by reading its evidence again.

The publisher of FACTA gets the same treatment as anyone. An agent or a token whose addresses the publisher has declared carries the label "operated by the publisher of FACTA" on every page and in every answer. The declared addresses are listed at /v1/publisher, and an address's page shows the label too.

  • It answers over HTTPS only, with TLS 1.2 or later, and every page tells browsers to come back over HTTPS (HSTS).
  • Its domain is signed with DNSSEC, and mail that claims to come from it and fails the domain's checks is to be refused (DMARC, policy reject).
  • Its pages load no script from another site and no analytics, and run no inline script: the content security policy refuses both.
  • Its public pages set no cookie. Signing in sets one, for the session, and signing out removes it.

Check each from a terminal, for factahq.xyz:

curl -sI https://factahq.xyz/ | grep -i strict-transport-security
dig +dnssec factahq.xyz A
dig +short TXT _dmarc.factahq.xyz

A validating resolver answers dig with the ad flag, and the last line gives the DMARC policy.

A wrong figure, a bug or a security problem: write to contact@factahq.xyz. Please do not publish a security problem before it is fixed. The same address is in /.well-known/security.txt. There is no bug bounty.