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

# Aptos

> Network-specific features, signature kinds, supported assets, and integration requirements for Aptos wallets on the DFNS platform.

Aptos is a Layer 1 blockchain built with the Move programming language. This guide covers Aptos-specific features when using DFNS wallets.

## Wallet activation

Aptos wallets are **automatically activated** when they first receive assets. The network charges a small fee for account creation, which is deducted from the first incoming transfer.

<Note>
  You don't need to manually activate the wallet. The first transfer to your wallet address will create the account on-chain.
</Note>

## Transfers

Use the [Transfer Asset](/api-reference/wallets/transfer-asset) endpoint for Aptos transfers:

* **Native APT**: Use `kind: Native` with amount in octas (1 APT = 100,000,000 octas)
* **Fungible assets**: Use the appropriate kind with the asset type address

## Transaction expiration

DFNS builds Aptos transactions with a **24-hour** expiration: the transaction must be broadcast within 24 hours of being built, otherwise it expires and must be rebuilt and re-signed. This applies to all transactions, including transfers, and gives this much time to sign and broadcast even if the signing infrastructure is temporarily unavailable (for example an unreachable on-prem signer).

## SDK integration

For full transaction control, use the DFNS SDK with [@aptos-labs/ts-sdk](https://aptos.dev/en/build/sdks/ts-sdk). See the [Aptos integration example](https://github.com/dfns/dfns-sdk-ts/blob/m/examples/libs/aptos/basic-tx/main.ts).

## Related resources

* [Aptos broadcast examples](/api-reference/broadcast/aptos)
* [Aptos signing examples](/api-reference/sign/aptos)
* [Supported networks](/networks)
* [Aptos documentation](https://aptos.dev/)