t1 primary sources — 2026-05-08

Official site

• https://www.t1protocol.com/
  • Marketing site framing t1 as cross-chain infrastructure for Ethereum and L2s built around real-time proving, programmability, and shared liquidity / composability.

Core docs

• https://docs.t1protocol.com/
  • Docs root; best entry point for protocol framing and navigation to architecture, research, and litepaper resources.
• https://docs.t1protocol.com/intro/protocol/architecture/
  • Most useful source for the concrete mechanism: v1 TEE-enabled sequencing and proof submission, plus v2 sequencing/execution separation, HotShot sequencing consensus, execution consensus, encrypted transaction fields, and canonical-bridge value-at-risk controls.
• https://docs.t1protocol.com/intro/protocol/tee/
  • Clear explanation of the protocol’s trust anchor in remote attestation, partner-rollup reads, real-time proving, and encrypted mempool / encrypted-input design.
• https://docs.t1protocol.com/intro/research/
  • Helpful high-level statement of the protocol thesis: rollup fragmentation as the core problem, RTP as the fix, and zk-compressed remote attestation / AVS-secured TEEs as the proof path.
• https://docs.t1protocol.com/intro/resources/
  • Confirms the canonical public resource links for the t1 Vision Litepaper and the TEE Architecture / Remote Attestation document.
• https://docs.t1protocol.com/t1-vision-litepaper.pdf
  • Canonical litepaper PDF link referenced by the docs resources page.

Public code surface

• https://github.com/t1protocol
  • Public org showing an active monorepo, docs repository, and related contracts / frontends, useful for establishing that the project has an implementation surface and not only conceptual materials.

Corpus takeaway

t1 is useful because it sits at the seam between shared sequencing, bridge verification, and TEE-based verifiable execution. The strongest reusable comparison is:

1. an answer to rollup fragmentation that does not rely only on classic message passing,
2. but also does not fully collapse into a pure shared-sequencer story,
3. instead routing trust through remote-attested execution, partner-rollup node access, Ethereum canonical-bridge checks, and explicit value-at-risk budgeting,
4. with periodic ZK checkpoints as the long-run safety backstop.

That makes it a strong comparison class for Espresso and Astria on sequencing/confirmation, for LayerZero-style interop on cross-chain trust surfaces, and for TEE-heavy execution systems that try to buy lower latency by moving more authority into attestation, operator sets, and bridge policy.