Skip to main content

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.

See an introduction including the list of supported networks on the fee sponsors feature page, or watch the video tutorial for dashboard users.

​
Flow overview

1

Create a fee sponsor

Designate an existing wallet as a fee sponsor.POST/fee-sponsors Create Fee Sponsor
2

Fund the sponsor wallet

Ensure the fee sponsor wallet has sufficient native tokens to cover gas fees.
3

Use in transfers

Specify feeSponsorId when creating a transfer. The sponsor and sponsoree wallets must be on the same network.POST/wallets/{walletId}/transfers Transfer Asset
If the fee sponsor wallet has a policy that blocks signing (e.g., Block action on Wallets:Sign), sponsored transfers will fail.
High-volume tip: If you’re processing a high volume of transactions for a given wallet, use a single fee sponsor for that wallet. This allows Dfns to better optimize transaction scheduling and improve throughput.

​
Fee Sponsor object

​
id
string
required

Fee Sponsor id.

Required string length: 1 - 64
Pattern: ^fs-[a-z0-9]{5}-[a-z0-9]{5}-[a-z0-9]{14,16}$
Example:

"fs-5vqdl-gliqk-b4rfukqauov1sp7j"

​
walletId
string
required

Id of the wallet that is used to sponsor the fee for other wallets

Required string length: 1 - 64
Pattern: ^wa-[a-z0-9]{5}-[a-z0-9]{5}-[a-z0-9]{14,16}$
Example:

"wa-5pfuu-9euek-h0odgb6snva8ph3k"

​
network
enum<string>
required

Network used for the wallet.

Available options:
Algorand,
AlgorandTestnet,
Aptos,
AptosTestnet,
ArbitrumOne,
ArbitrumSepolia,
ArcTestnet,
AvalancheC,
AvalancheCFuji,
BabylonGenesis,
BabylonTestnet5,
Base,
BaseSepolia,
Berachain,
BerachainBepolia,
Bitcoin,
BitcoinSignet,
BitcoinTestnet3,
BitcoinCash,
Bob,
BobSepolia,
Bsc,
BscTestnet,
Canton,
CantonTestnet,
Cardano,
CardanoPreprod,
Concordium,
ConcordiumTestnet,
Celo,
CeloAlfajores,
Codex,
CodexSepolia,
CosmosHub4,
CosmosIcsTestnet,
Dogecoin,
DogecoinTestnet,
Ethereum,
EthereumClassic,
EthereumClassicMordor,
EthereumSepolia,
EthereumHolesky,
EthereumHoodi,
FantomOpera,
FantomTestnet,
FlareC,
FlareCCoston2,
FlowEvm,
FlowEvmTestnet,
Hedera,
HederaTestnet,
Ink,
InkSepolia,
InternetComputer,
Ion,
IonTestnet,
Iota,
IotaTestnet,
Kaspa,
Kusama,
KusamaAssetHub,
Litecoin,
LitecoinTestnet,
Near,
NearTestnet,
Optimism,
OptimismSepolia,
Origyn,
Plasma,
PlasmaTestnet,
Plume,
PlumeSepolia,
Paseo,
PaseoAssetHub,
Polkadot,
PolkadotAssetHub,
Polygon,
PolygonAmoy,
Polymesh,
PolymeshTestnet,
Race,
RaceSepolia,
SeiAtlantic2,
SeiPacific1,
Solana,
SolanaDevnet,
Starknet,
StarknetSepolia,
Stellar,
StellarTestnet,
Sui,
SuiTestnet,
Tezos,
TezosGhostnet,
Tempo,
TempoModerato,
Tsc,
TscTestnet1,
Ton,
TonTestnet,
Tron,
TronNile,
Westend,
WestendAssetHub,
Xdc,
XdcApothem,
XrpLedger,
XrpLedgerTestnet
​
status
enum<string>
required

Fee sponsor status.

Available options:
Active,
Deactivated,
Archived
​
dateCreated
string<date-time>
required

ISO 8601 date (must be UTC). When the Fee Sponsor was created.

Example:

"2023-04-14T20:41:28.715Z"

​
name
string

Nickname for the Fee Sponsor. This is displayed on the transfer modal in the dashboard.

​
allowEndUser
boolean

Defines whether EndUsers and their delegated wallets can use this Fee Sponsor.

Last modified on February 16, 2026