Tria primary sources

Collected: 2026-05-12 UTC

Primary sources reviewed

https://docs.tria.so/
- Official docs home.
- Used to confirm Tria’s high-level positioning around chain abstraction, shared embedded wallets, BestPath AVS, and Unchained-backed TSS programmable wallets.
https://docs.tria.so/introduction
- Official architecture/introduction page.
- Used to confirm the split between consumer wallet/SDK surfaces, BestPath AVS as a permissionless chain-abstraction and intents marketplace, and Unchained as the shared-state layer supporting permissions, identity, and credential flows.
https://docs.tria.so/security-tss
- Official security / TSS / programmability page.
- Used to confirm the project’s claimed use of TEEs / secure enclaves, Lit Protocol TSS, SEV-backed node isolation, proactive secret sharing, and Unchained-based permissioning/automation for intent execution.
https://www.tria.so/legal/whitepaper
- Official whitepaper PDF URL.
- Used to confirm that an official whitepaper exists, though the fetched PDF was not meaningfully machine-readable in this pass.

Tria clears the intake bar because it is not just another multichain wallet pitch; it exposes a reusable three-part split between user onboarding/shared-wallet middleware, an intent-routing marketplace, and an underlying permission-state layer.
The strongest reusable insight is BestPath’s framing of chain abstraction as a market of modular execution-stack actors rather than as one monolithic bridge/router service.
Unchained matters analytically because it appears to hold the authority layer for wallet permissions, automated signing conditions, identity state, and credential logic. That makes Tria a useful comparison point for smart-account middleware and wallet-policy systems, not only for interop protocols.
A real caveat surfaced in the reviewed docs: some sections are redacted and marked for private circulation, so the current entry should be treated as architecture-first rather than as a fully implementation-audited protocol profile.