Skip to main content

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.

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, 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​

t1 TEE node runs a t1-core Docker image which exposes dedicated endpoints for cross-chain interactions.

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 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, t1-dapps 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.

Endpoints Provided​

Once your t1-dapp is deployed to t1, it can call the following predefined methods exposed by the TEE-co-located t1-core:

  • initIdentity(callbackOnDeposit)
    • Initializes a TEE-controlled multi-chain EOA identity which can accept user deposits and act on users' behalf
    • Accepts one parameter: A function which shall be called on t1-dapp whenever there is a deposit into the initialized identity
  • sendTx(chainId, payload, callback)
    • Instructs the TEE-controlled identity to request a transaction to be sent to a chain
    • Accepts a chain ID, a transaction payload, and a function to be called on t1-dapp after the transaction action
  • registerCallbackOnTransaction(chainId, address, callback)
    • Attaches a function to be called on t1-dapp whenever a transaction is received somewhere on-chain, e.g. an ERC-20 burn
    • Accepts a chain ID, an address to watch, and a function to be called
  • selfdestruct(fundsRecipient)
    • Unallocates the identity and returns funds
    • Accepts one multi-chain address