DTL

Bridge status

We are waiting for a public, audited bridge. Until then no custodial wrapper is issued — and you should not send DTL anywhere claiming to wrap it.

No public DTL bridge is live today.

The policy is "await_public_bridge". Until a public, audited bridge exists, no wrapper is issued and no custodial shortcut is taken. Lock address: GB44FLVIA76IFS2FTH3O2PNRKXBDZK2NOE42EYAQR3JPKTEJ6QTMD6F5.

Hub and spoke design

                 +--------------------------+
                 |   STELLAR  (hub)         |
                 |   DTL canonical issuer   |
                 |   locked backing         |
                 +-----------+--------------+
                             |
      +----------+-----------+-----------+----------+
      |          |           |           |          |
 +----+---+ +----+----+ +----+----+ +----+---+
 | Koinos | | Solana  | |   BNB   | |  TRON  |
 |  kDTL  | |  sDTL   | |  bDTL   | |  tDTL  |
 | (spoke)| | (spoke) | | (spoke) | |(spoke) |
 +--------+ +---------+ +---------+ +--------+

   mint(spoke)  requires  lock(hub)   1:1
   burn(spoke)  releases  unlock(hub) 1:1

Stellar is the only canonical issuer of DTL. Every other chain hosts a wrapper that must be backed 1:1 by DTL locked on Stellar.

TRON ↔ Stellar route (two-way)

Stellar → TRON (wrap)

  1. 1.You send DTL on Stellar to the published lock address (issuer DTL stays canonical).ready
  2. 2.The lock is read from Horizon, so anyone can verify the exact amount held.ready
  3. 3.The TRC-20 tDTL contract mints the same amount to your TRON address (mint restricted to the bridge role).ready

TRON → Stellar (unwrap)

  1. 1.You burn tDTL on TRON from your own address; the burn event is public on TRONSCAN.ready
  2. 2.The bridge reconciles the burn against locked DTL on Stellar, 1:1, before anything is released.ready
  3. 3.The same amount of DTL is released from the lock address to your Stellar DTL account.ready
Stellar DTL issuerGAVI55AFRGQ5HH75UVNOFCF5CNKRK26PWMKSMYBIHPSQ5LWNVMFJEBEB
Stellar lock addressGB44FLVIA76IFS2FTH3O2PNRKXBDZK2NOE42EYAQR3JPKTEJ6QTMD6F5
TRON tDTL contract (TRC-20)TJLXGXBHGtUnsYFhWvKBLLsWX5cpquEZu2

Both endpoints now exist on-chain: the Stellar lock address is published and the TRC-20 tDTL contract is confirmed on TRON mainnet, so the two-way route is open. The invariant still rules everything: sum(wrapped) <= locked DTL on Stellar. Wrapped supply stays at zero until the first lock settles, and every number shown here is read live from Horizon and TRON.

What any future bridge must provide

  • •A public, verifiable lock address on Stellar holding the backing DTL.
  • •On-chain mint and burn events that anyone can read and reconcile.
  • •Continuous proof of reserves: wrapped supply never exceeds locked DTL.
  • •An independent security audit of the bridge and wrapper contracts.
  • •No single custodian able to mint wrappers without a matching lock.

Spokes

Koinos

Not deployed

kDTL

Contract prepared for Harbinger testnet only. Mint/burn restricted to bridge role.

Solana

Not deployed

sDTL

Mint not created yet. No bridge, no wrappers.

TRON

Not deployed

tDTL

tDTL is live on TRON mainnet at TJLXGXBHGtUnsYFhWvKBLLsWX5cpquEZu2 (deploy tx 86b7280605e31cb3b5f448299b8703cae1b5909d3b8b78e2e2bce64a6674e17a). Mint and burn are restricted to the bridge role and every unit is backed 1:1 by DTL locked in the official Stellar treasury. Circulating wrapped supply stays 0 until the first lock is settled.

BNB Chain

Not deployed

bDTL

Contract not deployed yet.

Never send tokens to an unverified bridge

Never send DTL or any token to a bridge address you have not verified against this page and lovecoin.life/dtl. Anyone offering to bridge DTL today is not operating an official bridge. This terminal never asks for a secret key or seed phrase.