How do we reach a verdict?
Every guide and comparison is desk research. We read the protocol's own documentation, on-chain explorers, DeFiLlama snapshots, and primary news sources. We have not deposited reader funds in these protocols, and we say so on the page. A verdict names who should skip the tool — a hedged page gives an answer engine nothing to quote.
The working sequence is: (1) check whether a page for the query already exists, (2) pull primary sources and capture dates, (3) write a 40–60-word answer that states the decision, (4) name who it is not for, (5) editor review. If we cannot source a number today, we do not publish the number.
What money cannot buy
Elite Digital AI Solutions Ltd funds this site as an editorial portfolio. There is no advertising inventory, no sponsored protocol page, and no affiliate ranking. A project cannot pay to appear in a comparison, to soften an exploit mention, or to remove a "skip this" line.
- We do not accept payment to change, soften, or remove negative coverage.
- We do not publish token-sale promotions, ICO coverage-for-hire, or unverified investment opportunities.
- We do not mark up supplier ratings as
aggregateRatingor write self-serving reviews of third-party protocols. - When a free official interface is the right tool, we say so and link it.
What sources do we use?
Protocol data is attributed on the page. The standing sources are:
- DeFiLlama — TVL, category, chain lists; date taken from the extract, never from the build clock alone.
- Official protocol docs and apps — the operator's own URL, checked on the date we cite.
- Block explorers — Etherscan, Arbiscan, Basescan, Solscan for contract and transaction facts.
- Recognised newsrooms — CoinDesk, The Block, Decrypt and similar, distinguished from our own research.
Absence of data is not evidence of absence. We do not render "unscored" or "unverified" from a missing field. We say why the figure is not on the page.
What triggers a correction?
A correction is a factual error: a wrong date, a fabricated or inverted exploit claim, a stale URL presented as live, or a number we cannot source. Style edits and adding context are updates, not corrections, and they do not change dateModified unless the substance changed.
Confirmed errors are corrected on the page, with a notice of what changed and when, and entered in the public corrections log. We do not silently delete a false sentence. Report errors to [email protected] — typical turnaround for a confirmed fact is 24 hours.
Who is accountable?
Kaiser Khan, editor in chief, is the named human on author pages and in schema as reviewer. Drafting bylines that cannot be verified off-site are published as the organisation, not as fake experts. Conflicts of interest — material holdings in a protocol under coverage — are disclosed on the relevant page. Staff do not trade a token they are actively covering for 72 hours before and after publication.
What we will not publish
- First-hand "we used this with real funds" language we cannot support.
- Prices, APYs, or TVL figures without a source and a capture date.
- Years in slugs that force every URL to rot each January.
- Near-duplicate templates that only swap a protocol name.
- Investment advice, solicitations, or "guaranteed yield" claims.
How this relates to method pages
This policy is the contract. The method page is the procedure for protocol research, comparisons, and TVL rankings. Read both if you are citing us: the policy says what we refuse; the method says how a given page type is built.