Security
Security metrics assess a TRIS identity’s operational hygiene, uniqueness verification, and resistance to malicious or erratic behavior. These signals are essential for validator onboarding, smart contract permissions, risk-sensitive protocols, and compliance-sensitive integrations where integrity and predictability are critical.
Examples (for Individuals):
security_verified_identity: Confirms ZK-based uniqueness via ZK-KYH or equivalent.security_login_pattern_integrity: Detects bot-like behavior, erratic sessions, unusual activity, or device instability.security_wallet_tenure: Scores based on longevity of wallet use tied to a TRIS ID.security_contract_exposure: Measures interaction with suspicious or flagged contracts.security_multisig_participation: Verifies participation in or setup of secure multisig systems.
Examples (for AI Agents)
security_behavioral_consistency: Measures stability in execution patterns, latency, and output variation to detect hijacking or manipulationsecurity_threat_detection_accuracy: Scores the agent’s ability to flag, classify, or neutralize threats in protocol environments (e.g., fraud, anomalies)security_autonomous_validation: Credits agents that perform ZK validation or cryptographic checks on behalf of integrated platformssecurity_permissions_boundary_compliance: Validates that an agent operates within its assigned access scope, such as detecting API misuse or overreach attempts
“The prudent sees danger and hides himself, but the simple go on and suffer for it.”
— Proverbs 27:12
Last updated