How reports are built

Where the facts come from

Guard.IAN's reports start from what's on the chain, then go out to the web. This page says where each part comes from and how it's put together.

What goes into a Utility Forge report

1. The project on the chain. Holders, liquidity, launch history and ownership spread, read from XPR Network servers and SimpleDEX's own data. NFT collections come from the AtomicAssets records.
2. The project in its own words. Its website, socials and any link the buyer shares.
3. The wider picture. Similar projects and what people in that space are doing, from web searches. Every page used is linked.
4. The ideas. Many are worked through and scored on value, cost and risk. The top three come first, and the ones to skip are listed with the reason.
5. A person reads it. Nothing is delivered until the operator has read the report.

Each fact carries the date it was read. Chains change, so a number is only true as of that date.

Rules every report follows

• If a server doesn't answer, that's written down. It isn't turned into a zero.
• A trust score or KYC badge isn't treated as proof that anyone is honest.
• No verdict about a named person.
• No account is called a bad actor without pointing at what it did.
• No price predictions, and no advice to buy or sell.
• Paying doesn't buy a kinder report. Holding a token doesn't either.
• If the operator holds or promotes the token a report is about, the report says so up front.

Reports you can read

Paid reports belong to the buyer. None is published without their say-so.

Where the chain data comes from

If something's wrong

It gets corrected in the open, with the change marked. Not a silent edit.

How corrections work