Skip to main content

Use Cases

DTP provides networking building blocks that can be applied in many ways.

You will find on this page a few inspiring ideas.

When ready Go to choose your installation setup ....

Which layer do you need to work with?

DTP features are available in roughly 3 layers (by increasing level of difficulty):

  • DTP Services Daemon Similar to NGINX, Cloudflare, HAProxy... These are for proxy/forward/firewall services. You will simply be configuring how your data flows between your apps and servers. Your existing apps just use standard TCP/IP sockets (e.g. "localhost:port" URL) to interface with the DTP services daemon.

  • DTP Protocols Think "TCP". The DTP/Sui SDKs allows developers to have more control for connecting any mix of web2 apps (webapp, client/servers...). You will need to write Rust and/or Typescript apps. This is also the solution to eliminate having to install the DTP Services Daemon on your end-users' devices.

  • DTP Sui Move Packages Innovations particular to Sui, such as RPC escrows, new traffic policies, coins&call equivocation mitigation, metering etc... you will likely be deeply involve into web3 development at this point.

For most users, you will deal only with the "easiest" layer, the "DTP Services Daemon".

If not sure how to proceed for your specific need, then please open a discussion on Discordopen in new window.



  • Web3 frontends connecting to a centralized JSON-RPC backend (More info)
  • Rust/Typescript Web3 Client to centralized TCP Server (More info)

Encrypted Messaging

  • Add traditional user/password login to a dApp. The goal is to allow access to the same "user account" even if done from a different wallet (client address). Implementation often requires "secret messaging" between a centralized server and the Web3 apps.
  • Any user-to-user data transfer
  • Anonymous Tips Line (with potential reward in return).

Networking / Infrastructure

  • Zookeeper, Consul, Serf-like services for discovery and consensus among off-chain servers.
  • UDP, TCP, QUIC/UDP Tunneling: Transport IP protocols packets within a DTP connection for point-to-point applications (See DTP Services Daemon for an alternative)


  • Rate limit access to a back-end server (either bandwidth or request)
  • Allow/block origin (using authentication)


  • Any service charging for content access (in addition to gas cost). DTP provides generic per byte and/or per request escrow service (to meter pre-agreed cost, limit and quantity... not quality).
  • Pre-paid subscription per day/month (epoch driven?).
  • Various escrow service that allows to shift the transport cost completely at the origin or destination (gas always paid by sender, but escrow service handles fair refund).

Public Broadcasting

  • Allow live broadcasting to automatically turn on/off upon enough fund contributed (thus saving the producer from any expense when no-one is listening).
  • Public broadcast performed upon enough ticket sold.
  • Tip/Request/Message/Audience participation line attach to a public event channel.