FAQ

In one sentence... What can DTP do?

It is a TCP-Like protocol facilitating data transfer between web2 applications, with additional Web3 features such as services monetization, anonymity and security.

Can DTP be used between Web3 frontend apps?

Yes. DTP can selectively connect front-ends WebApp to each other, while keeping the data transfer under the control of a dApps (transit on the Sui network).

As an example, you can use it to allow gamers exchange encrypted messages among themselves while they are on the same team in a Web3 game. In this case, DTP provides the WebApp to WebApp connectivity without making the players IP addresses visible.

What sort of data can DTP transport?

Any protocol, any data stream.

Data can be a few bytes for a one time secret exchange for authentication/login. At another extreme, the bandwidth can be for as much as an encrypted video stream. The economic feasibility of HD video streaming on blockchain is an open question... (See Video Streaming )

Can DTP be used with commercial application?

Yes. DTP is open-source and can freely be used in commercial application (Apache 2.0 License).

How much does it cost to use DTP?

Only the Sui gas needed to run it, expect the execution cost to be mostly driven by the number of bytes transferred.

There is no developer fee or middlemen commission collected for using DTP.

Some service provider may optionally add their own fees on top of DTP (e.g. micro-payments), but DTP standardize public disclosure (and escrow management) of these fees on-chain. There is no "fine print unexpected" fee. A provider can not change the fees on already open DTP connections.

Can DTP unexpectedly drain my account?

We are working very hard to make this impossible.

DTP protects its user by enforcing a maximum amount of fee possibly collected per day (per epoch). The user must explicitly approve and sign a change to this maximum.

Also, fee rates are determine once by a Service Level Agreement (SLA) when opening a DTP connection. You can close that connection at any time. It is not possible for a service provider to keep collecting payments after a DTP connection is closed.

(Note: The configurable maximum is tied to a wallet address and enforce on-chain).

When will DTP have its own token?

Never.

DTP operations are always paid in Sui.

dApps built on top of DTP can use tokens, but this is not within the scope of DTP itself.

Can DTP simply tunnel standard TCP, UDP, IP packets?

Transparent packets tunneling could be done, but it is not recommended.

DTP/Sui provides already reliable and ordered data transport. That would be redundant with say, what TCP would try to achieve within a tunnel.

Instead, look into DTP Services Daemon to efficiently terminate/bridge standard IP protocols. That eliminates protocol redundancy and better leverage what the Sui network already provide.

Any plan to support another blockchain?

No, unless a breakthrough in performance is possible with another blockchain architecture.

Sui provides stable time to finality (low jitter), parallelism and scalability (no contention between connections).

Low jitter allows small and predictable buffer size at the receivers.

Sui fast path transactions makes sub-second streaming latency possible.

For now, DTP/Sui might not be well-suited for application that depends on fast sequence of query/response (since that requires two transactions finality). DTP attempts to minimize roundtrips and protocol handshakes at every step.

Where is the code?

DTP still in early design phase and is not yet release. See GitHub development branches for "work-in-progress".

Where can I go for more questions?

Try the Discord channel: https://discord.gg/Erb6SwsVbH