Skip to content

Update overview.md #62

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
OrestTa merged 1 commit into from
Jan 12, 2026
Merged

Update overview.md #62

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 6 additions & 6 deletions docs/integration/docker/overview.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,21 +6,21 @@ sidebar_position: 1

# Docker dApps Overview

t1 lets developers run their own Docker-packaged code as a dApp and benefit from t1's secured TEE architecture as well as its dedicated cross-chain capabilities.
**t1 lets developers run their own Docker-packaged code as a dApp and benefit from t1's secured TEE architecture as well as its dedicated cross-chain capabilities.**

_Warning: This is an early feature which is under heavy development and should not be used in production._

Moreover, natively sharing liquidity and composing between such dApps will be possible soon. In the future, we'll also enable keeping the dApp logic (incl. source code) private-yet-verifiable, via a remotely-attested open-source enforcer.
Moreover, natively sharing liquidity and composing between such dApps will be possible soon. In the future, t1 will also enable private execution by keeping the dApp logic (incl. source code) private-yet-verifiable, via a remotely-attested open-source enforcer.

## How t1 Supports Docker

A t1 TEE node is always running a `t1-core` Docker image which exposes dedicated endpoints for cross-chain interactions.
t1 TEE node runs a `t1-core` Docker image which exposes dedicated endpoints for cross-chain interactions.

A third-party developer is able to have t1 pull a `t1-dapp` Docker image prepared by them and run it within the same TEE.
Third-party developers are able to have t1 pull a `t1-dapp` Docker image prepared by them and run it within the same TEE.

Therefore, such third-party dApp becomes co-located with `t1-core` and allowed to call its predefined methods via regular Docker-to-Docker communication between co-located containers.
Therefore, such third-party dApps become co-located with `t1-core` and are allowed to call `t1-core`'s predefined methods via regular Docker-to-Docker communication between co-located containers.

Moreover, a `t1-dapp` is allowed to issue conventional web2-style API calls, e.g. to fetch CEX price feeds etc. However, in order to benefit from t1's secured TEE architecture, it is the responsibility of the dApp developer to ensure that their logic yields a deterministic output—only then can it be verified via re-execution.
Moreover, `t1-dapp`s are allowed to issue conventional web2-style API calls, e.g. to fetch CEX price feeds etc. However, in order to benefit from t1's secured TEE architecture, it is the responsibility of the dApp developer to ensure that the application logic yields a deterministic output—only then can it be verified via re-execution.

proprietary code - no ra - controller pattern

Expand Down
Loading