One engine, five surfaces
Everything in this section runs on the same read described in How Scoring Works. The score is the engine. The products are just the different shapes that engine takes when it reaches a real user or a real app.TokenShield
Scores a token or contract. Answers “is this safe to touch.”
Wallet Trust Score
Scores a wallet. Answers “has this address earned trust.”
Gated Pools
Uses the score as a gate, so a pool can check reputation before it lets a wallet act.
The Widget
Drops a live trust badge for any token or wallet into your own UI.
Trust-Ordered Discovery
Scores a whole list at once so a feed can rank by trust.
How to think about them
It helps to group them by what they actually do for you. Two of them are reads. TokenShield reads a token, Wallet Trust Score reads a wallet. Same tiers and flags, different subject. These are the answer to a yes-or-no question you have right now. One of them acts on a read. Gated Pools takes the score and turns it into a door, letting an app require a certain standing before a wallet can do something sensitive. Two of them put the read where people are. The Widget surfaces a badge inside your interface with a single script tag. Discovery scores many things together so a list, a feed, or a launchpad can order them by trust instead of by hype.Which scoring lane each uses
TokenShield and Discovery run on the token lane, since they are reading tokens and contracts. Wallet Trust Score runs on the wallet lane. Gated Pools and the Widget are delivery surfaces, so they can carry either lane depending on what you point them at, a wallet or a token.Every one of these is built on the same principle: TrustGate hands you a signal, you decide what to do with it. None of them take over your interface or make the call for you.
Start anywhere
Read the score concept first
If you have not yet, the scoring core makes every product page click into place.
Jump to integration
Ready to build? The Integrate section is the hands-on path.