Skip to content

Commit ca10b4d

Browse files
committed
updated funding flow text
1 parent 3252c57 commit ca10b4d

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

use-cases/fund.mdx

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
22
title: 'Fund'
3-
description: 'Trails supports depositing funds directly into your protocol, exchange, app, or chain with any token from any chain.'
3+
description: 'Trails supports depositing funds directly into your protocol, exchange, app, or chain with any token from any chain or via fiat onramps.'
44
icon: 'money-bill'
55
---
66

@@ -9,13 +9,13 @@ icon: 'money-bill'
99
Trails seamlessly enables users to deposit funds into your chain, app, or protocol with optimized UX flows and native integrations with multiple liquidity sources to optimize routes for low-slippage. Users can fund from any token they hold across any supported chain, eliminating the need for manual bridging and swapping - embedded seamlessly in the experience.
1010

1111
Traditional funding flows require users to:
12-
- Find an external bridge supported by the chain / app with unknown trust assumptions
12+
- Find an external bridge or fiat onramp provider supported by the chain / app
1313
- Swap to the required deposit token
1414
- Pay multiple gas fees across different networks
1515
- Wait for bridge confirmations
1616
- Navigate complex interfaces
1717

18-
Trails simplifies this by allowing users to deposit funds using any token from any supported chain in a single transaction, automatically handling all bridging, swapping, routing, and execution logic where the user deposit with a variable or fixed amount.
18+
Trails simplifies this by allowing users to deposit funds using any token from any supported chain in a single transaction, automatically handling all bridging, swapping, routing, and execution logic where the user deposit with a variable or fixed amount. Importantly, Trails intent addresses can be utilized to also automatically orchestrate transactions to chains or apps that an onramp provider doesn't explicitly support or provide liquidity.
1919

2020
## Use Cases
2121

0 commit comments

Comments
 (0)