Locksley is a data and education site for one blockchain — Robinhood Chain. It reads the chain directly with its own indexer, reads escrow state directly from lock contracts, publishes every number with its source and its denominator, and states plainly what it did not check. It is built by TrustSwap, which owns Team Finance. It publishes no safety rating for any token, and nothing on it is for sale.
What Locksley is
A front page for one chain, built for the two people who need it most.
Robinhood Chain produces more tokens in a week than anyone can read about, and the two people who most need to understand what is happening on it want opposite things. A buyer wants to know whether the liquidity behind a token can be pulled out from under them. A team wants to demonstrate that it cannot. Those are the same fact, read from two sides, and almost every site in this category serves only one of them.
So Locksley is one site with two faces. Explore and the pages it links out to answer the buyer's question. The project console answers the team's — by showing them the same public record everyone else reads. Nobody is asked which one they are; the site works it out from what they do, and works perfectly well if it never finds out.
Why a company that sells locks would build this
The obvious suspicion is the right one to start with: TrustSwap owns Team Finance, Team Finance sells liquidity locks, and a site that reports on liquidity locks is an excellent way to sell more of them. That is true, and we are not going to pretend otherwise — the disclosures page sets out every way we are paid.
The argument for doing it anyway is narrower than a mission statement and, we think, more durable. A site that could be paid to flatter a token is worth nothing to the buyer it is for — and a site worth nothing to buyers is worth nothing to the projects trying to reach them either. The value of a favourable reading is exactly the credibility of the reader, so selling that credibility destroys the thing being sold. The commercial case and the honest case point the same direction here, which is the only reason to trust either.
Which gives the rule the rest of the site is built on: we charge for the doing, and never for the reporting. Locking a pool costs money. Reading whether a pool is locked never will.
How it works
Our own indexer over one chain, plus direct contract reads. Two outside sources, both named.
Prices, volume, liquidity, holders and pool composition are computed by our own indexer directly from Robinhood Chain. Escrow, vesting and team-lock state are read directly from Team Finance's contracts. Two figures come from outside — chain TVL and the RHC/USD rate, both from DeFiLlama — and they are labelled wherever they appear. Every number is stamped with the block it was read at.
Where a figure could be computed several defensible ways, the methodology page names the options, says which we chose, and says what each one can be gamed by. That last field is unusual and it is deliberate: a metric whose weakness is not published is a metric its publisher has not thought about.
“No lock found” means we found none, not that none exists: we do not index other lockers yet, and it is never a claim about the project.
What we refuse to publish
- A safety rating, score or grade. For any token, at any price, for anyone. A single number is the thing an attacker optimises against, and a published survey of rug-pull detection tools found causes that no tool detects — one of them a fake lock. A rating built on that input turns something unknowable into something that looks known.
- A market capitalisation. Circulating supply cannot be read from a blockchain. We publish total supply and fully diluted value, both exact, and explain why the comparison looks unflattering.
- A chart we cannot compute. A mock chart is a lie with axes.
- An aboutness label. We do not tell you what a token is for. We tell you what is true about it.
If you want the reasoning rather than the list: how to read a lock in 60 seconds and what locking and vesting prove are the two guides that carry it, and the glossary defines the terms in a paragraph each.
Who is responsible
Accountability by role, and by a name that can be reached.
Crypto is a subject where being wrong costs readers money, so it matters that someone is answerable rather than that a brand is. Every guide and glossary entry carries a byline, every data page carries the methodology section that governs it, and every page carries a route to a person through the contact page.
How it is paid for
Three streams, all listed in full on the disclosures page: Team Finance tool fees, one labelled sponsor slot per day, and labelled placements through a partner app. No data licensing, no order flow, no cut of any trade, and no fee from the bridge a buy hands off to.
That page also carries the two things this one deliberately does not: the placement table saying where the disclosure appears on the page you were actually reading, and a counter of every request we receive to change or remove something we published, granted or not. We publish the counter because an ethics policy that is only a promise has, in this category, repeatedly turned out to be worth exactly what a promise is worth.
When we get it wrong
Corrections are permanent, dated and appended. We do not quietly overwrite.
Data is wrong sometimes: an indexer falls behind, a contract read returns something we mis-modelled, a price feed goes stale. When a published figure was wrong, we say so, date it, and leave the entry up for good rather than editing the page and moving on. The corrections log lives with the methodology, alongside the rule for what counts as a correction — a numeric threshold rather than a judgement call, so it is not a matter of how embarrassing the error was.
Tell us through the contact page — choose “A correction”. A reader who finds an error in our arithmetic is doing the most valuable thing anyone does on this site.
Changelog
v1.0 — 20 August 2026. First publication. Establishes the two-sided framing, the named accountable roles, the refusal list, and the handoff of all commercial detail to the disclosures page.
Who we are
Locksley is operated by TrustSwap. Registration #06140909221011 · Polig 8, Oficina 118, Col. San Benito, San Salvador, San Salvador, El Salvador. Contact: locksley.news/contact.
Who pays us, and what it cannot buy
Three revenue streams, where the disclosure appears, and the pressure ledger.
MethodologyHow every number is computed
What we measure, what we exclude, and what it can be gamed by.
Start hereEvery token on the chain
The live surface all of this is in service of.
