Skip to content

Commit 83df777

Browse files
committed
update bridge
1 parent 284ec95 commit 83df777

File tree

1 file changed

+31
-0
lines changed

1 file changed

+31
-0
lines changed

docs/bridge/bridge.md

Lines changed: 31 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -2,3 +2,34 @@
22
id: bridge
33
title: Bridge
44
---
5+
6+
## Guide
7+
8+
Helixbox utilizes **Bridge** technology to facilitate cross-chain transfers. It integrates multiple high-quality cross-chain protocols at the underlying layer and combines **Smart Account** technology at the upper layer to enhance the user experience.
9+
10+
### **Cross-Chain Transfer Steps**
11+
12+
1. **Select Source Chain and Token**
13+
Choose the **source chain** and **token** you wish to transfer.
14+
15+
2. **Select Destination Chain**
16+
Specify the **destination chain** where you want to receive the assets.
17+
18+
3. **Enter Transfer Amount**
19+
Input the **amount** of tokens to be transferred.
20+
21+
4. **Confirm and Sign**
22+
- Click the **Transfer** button to submit the transaction request.
23+
- Sign the transaction with your wallet and wait for execution.
24+
25+
5. **Check Transaction Status**
26+
Once the transaction is completed, you can check the received assets on the **destination chain**.
27+
28+
### **Custom Receiving Address**
29+
Users can **customize the receiving address**, allowing assets to be sent to a specified wallet instead of the connected wallet by default.
30+
31+
### **Security and Transparency**
32+
- Although Helixbox leverages **third-party cross-chain protocols**, it conducts **regular audits** and **monitors the transaction execution process** to ensure security.
33+
- A **clear transaction history** is provided, allowing users to track their transfers at any time.
34+
35+
By following these steps, users can efficiently complete cross-chain transfers while ensuring security and transparency.

0 commit comments

Comments
 (0)