> ## Documentation Index
> Fetch the complete documentation index at: https://docs.debridge.com/llms.txt
> Use this file to discover all available pages before exploring further.

# dePort

> Deploy your token on secondary chains using dePort's lock-and-mint solution

dePort is a native bridge for assets that allows protocols to deploy synthetic representations (deTokens) of their tokens across multiple chains using a lock-and-mint model. Built on the [deBridge Messaging Protocol (DMP)](/home/products/dmp-overview), dePort locks native tokens in a deBridgeGate smart contract on the source chain and mints corresponding synthetic assets (deAssets) on destination chains. dePort can also serve as a canonical bridge for chains connected via [deBridge IaaS](/home/products/iaas), providing cross-chain asset custody.

## Key Features

* **Lock-and-mint architecture**: Native tokens are locked on the source chain, synthetic deAssets are minted on destination chains
* **1:1 collateralization**: Total supply of each deAsset is always fully backed by collateral locked on the native chain — no liquidity imbalance risk
* **Automatic listing**: No listing requirements — any token can be bridged, and the deAsset is deployed automatically on first claim
* **Multi-chain routing**: Transfer deAssets between secondary chains directly, without routing through the native chain
* **Decentralized validation**: Validator consensus ensures cross-chain transfer integrity
* **Canonical bridge for IaaS chains**: Provides cross-chain asset custody for chains connected via deBridge Infrastructure-as-a-Service

## When to Use dePort

* **Token issuers** wanting multi-chain presence for their assets
* **Protocols** deploying synthetic representations across chains
* **Projects** needing 1:1 backed wrapped tokens with guaranteed collateralization
* **Multi-chain token distribution** without liquidity fragmentation
* **Canonical bridging** for chains connected via [IaaS](/home/products/iaas) — seamless custody of assets from other networks

## How It Works

1. **Lock**: The native token is locked in the `deBridgeGate` smart contract on the source chain. A unique `submissionId` is calculated from the transaction parameters.
2. **Validate**: deBridge validators track the event, wait for block finality, then sign the `submissionId` and submit it to the destination chain.
3. **Mint**: Once sufficient validator signatures are collected, the corresponding deAsset is minted on the destination chain. If the token is bridged for the first time, the deAsset contract is deployed automatically.
4. **Claim**: Any wallet can call the `claim` method with the transaction parameters and validator signatures. The smart contract reconstructs the `submissionId`, verifies signatures, and mints/unlocks the asset to the receiver.

## Architecture

```mermaid theme={null}
graph LR
    A[User] -->|Lock token| B[deBridgeGate<br/>Source Chain]
    B -->|Emit event| C[Validators]
    C -->|Sign submissionId| D[deBridgeGate<br/>Destination Chain]
    D -->|Mint deAsset| E[Receiver]
    E -.->|Transfer deAsset| F[Other Chains]
```

## Documentation

<Columns cols={2}>
  <Card title="Getting Started" icon="rocket" href="/dmp-details/dePort/getting-started">
    Core concepts, collateralization, and listing
  </Card>

  <Card title="Transfer Flow" icon="diagram-project" href="/dmp-details/dePort/transfer-flow">
    Technical transfer mechanics and validation
  </Card>
</Columns>

## Get Started

[Go to dePort Documentation](/dmp-details/dePort/getting-started)