Skip to main content

​
About the score

No. A score is a signal, not a verdict. A high read means the behavior looks strong, and a low read means it does not, but neither is a promise. Always do your own research before committing funds.
No. The scoring engine does not. Counterparties are counted as part of an address’s own behavior, never inherited into its score.A separate Knowledge Graph view from Intuition exists on the TrustGate site only. It is a second lens, it is not mixed into widget, batch, oracle, or gating responses, and integrators never call it. See Knowledge Graph.
Because TrustGate is adversarial infrastructure, and the people trying to beat it read docs too. Categories and meaning are public. Quantitative internals are not. Same posture as mature anti-abuse systems.
Only public onchain activity. No off-chain data, no personal data, no KYC, no manual review. TrustGate looks at what addresses have already done on a public ledger.
It is built to be hard to game. A read weighs several kinds of behavior together, and the patterns that lift a score are expensive to fake at scale. No system is perfect, which is why the score is a signal to weigh rather than a final verdict.
Because it has not earned anything yet, not because it did anything wrong. Pair the tier with the confidence level to tell “no track record” apart from “active red flags.”
VERIFIED is an issuer-confirmed token, not a behavioral tier. NTT means the single-token widget was pointed at something that is not a tradeable ERC-20. HIGH_ELITE and ELITE are the same top behavioral tier under two labels.
A compatibility field. Oracle and batch use v1.0. Attestations use testnet-wallet-v1.0 or testnet-token-v1.0. Pin the value you actually receive. A recalibration that changes who passes a band will bump it.

​
Using and integrating it

Arc (EVM) and Sui. Arc product APIs and contracts are Arc Testnet. Sui TokenShield scores mainnet coins; Sui wallets, caps, and the gated pool are Sui testnet. Delivery and gates differ. Arc has x402, widgets, attestations, and USDC claim routing. Sui has coin-type HTTP, a Sui widget, an onchain ScoreRegistry, and a non-transferable capability. The output shape (tier, flags, confidence) is shared. The engines are not the same binary. See Arc and Sui.
Widget, batch, NFT/contract scoring, gating, and Protocol Guard are free during testnet. Authoritative oracle queries cost 0.001 USDC via x402. The widget embedder does not pay — TrustGate settles that hop.
No. Every surface is non-invasive. Even in discovery, badging and flagging are the default and reordering is opt-in.
Two lanes of the same engine. The wallet lane asks whether an address has earned trust. The token lane asks whether a token is what it appears to be and whether the activity around it is honest. Same tiers and flags, different subject.
Widget: one ERC-20 badge, free. Batch: up to 40 tokens, free. Oracle: authoritative wallet or ERC-20, paid. Gating: signed, expiring attestation plus your ladder. Protocol Guard: contextual check and alerts, no signature.
No. It is your ladder’s evaluation (allowedByCallerLadder). Trust the attested score and signature. Combine with your own risk factors.
Everything is on testnet for now. Attestations already carry an environment label so a testnet score cannot silently pose as mainnet-gating grade. Until mainnet, treat scores as a testnet signal.

​
Still have a question

Start integrating

The hands-on path.

Reach out

Ask us directly.