Start with an observed launch
The launch record points to a token information file. That file can contain a name, symbol and project website link. These are claims supplied by the project, not verified identities.
Crawlers / collection activity
What the crawlers
are checking.
TFA collects the public information linked to observed token launches, then keeps a record of what it could and could not retrieve.
Checking collector…Waiting for current status
Watch the Tracers
Purple Tracers connect source hosts to the TFA hub. Each spider represents a real worker. Movement illustrates its reported job and result; it is not a measured position or progress percentage. A white parcel means a document was captured. Amber means the attempt was unavailable.
Connecting to recorded crawler activity…
● Purple · recorded source○ White parcel · captured document● Amber · unavailable attempt
Twelve workers: eight for token metadata and four for linked website pages. Status updates every five seconds. Workers share a one-job-per-minute limit for each host, and wait when no eligible job is available. Counts below are cumulative retained results, not risk findings.
How it works
Fetch allowed public information
The collectors check access restrictions and try to retrieve the token file and its project website page. They do not log in, execute page scripts or follow links across the whole site.
Record success or failure
TFA saves the source response, time and a digital fingerprint of captured content. It also records failures so missing information stays visible.
Token information files
One result per distinct metadata reference. A metadata file describes a token; it is not the same thing as the project's website.
Information files successfully retrieved and saved.
Attempts that failed or could not be fetched under the collection rules.
Information-file references waiting for their first attempt.
Project website collector
Uses website links found in successfully captured token information. Each worker pauses at least one minute between jobs. All workers share host limits, so busy gateways can still have a queue.
Waiting for website activity…
| Checked | Website host | Result | Page title | Text comparison |
|---|---|---|---|---|
| Loading website checks… | ||||
How to read the results
Captured means a document was saved. Unavailable means the attempt failed or was restricted. Waiting means it has not been attempted.
A matching text fingerprint means captured pages contain identical normalized text, after scripts and styling are removed. Shared text can come from ordinary templates; it does not prove common ownership or wrongdoing.
A timeout means the source did not respond within the allowed time. Failed requests are recorded and are not automatically retried by the current collector.
What it does not tell you
A successful capture does not mean a token is safe. A failed capture does not mean it is a scam. TFA does not yet verify social-account identities, crawl entire sites, or produce a validated risk score.
Project names, symbols and page titles are untrusted source content. Website snapshots may omit content that requires JavaScript or a login.
Open live launches and transfers →Recent token-file attempts
The latest 20 attempts. Times use your local timezone. Raw documents and complete source URLs remain private.
| Checked | Token | Source host | Result | Evidence |
|---|---|---|---|---|
| Loading real attempts… | ||||
This view refreshes every five seconds. Unavailable items are recorded as failed attempts; they are not silently counted as successful crawls. No risk score is generated. Source snapshots remain private; this page shows collection activity.