> ## Documentation Index
> Fetch the complete documentation index at: https://docs.trustgated.xyz/llms.txt
> Use this file to discover all available pages before exploring further.
# Signals
> The kinds of behavior a read weighs. Categories and meaning, not the recipe.
## What a signal is
A signal is a category of behavior the score pays attention to. The wallet lane and the token lane look at different signals, because the questions are different, but both feed the same tiers and flags.
Two things hold across all of them. No single signal decides a read, a score weighs many together, so gaming one dimension does not move the result much on its own. And what follows is the *what*, not the *how*. We describe the categories openly. The exact criteria, the windows, and the cutoffs stay internal, for the reasons on the [overview](/scoring/overview) page.
## Wallet signals
When TrustGate scores a wallet, it is asking whether this address has earned trust through what it has actually done.
How much real activity the address has, with recent activity carrying more weight than activity from years ago.
How long the address has been active. Time is one of the harder things to fake.
The range and quality of the contracts and protocols it has actually engaged with.
Deploying contracts is a strong, costly-to-fake signal of a real builder rather than a passing wallet.
The standing of the addresses it transacts with. Counted as part of its own behavior, never propagated into its score.
Whether the rhythm of activity reads like a person or a script. Automation itself is not punished, the pattern is what gets read.
Whether real value flows through the address, rather than dust meant only to pad a history.
## Token signals
When TrustGate scores a token or contract, it is asking whether the thing is what it appears to be, and whether the activity around it is honest.
The makeup and trust standing of the holders, not just how many there are.
Whether holders actually bought in or were handed tokens to manufacture the look of a crowd.
Whether the trading looks organic or coordinated.
The track record of the wallet that launched it, since a deployer carries its own reputation.
How many distinct, unrelated participants engage with it, versus a small cluster moving in sync.
Recent and genuine volume counts. Stale or wash-like volume does not carry the same weight.
These are categories, not a formula. Knowing that a read looks at, say, how holders got in does not tell you the line between healthy and suspicious, and that is by design. The point is that you understand what the signal represents, not that anyone can reverse engineer it.
## Next
The named patterns a read raises when signals line up the wrong way.
How sure a read is, and how new tokens are handled.