Documentation Index
Fetch the complete documentation index at: https://docs.yieldo.xyz/llms.txt
Use this file to discover all available pages before exploring further.
Get Transfer Status
Track the progress of a cross-chain deposit by its source transaction hash. Backed by LiFi’s transfer tracker.
Query Parameters
| Parameter | Type | Required | Description |
|---|
tx_hash | string | Yes | Source chain transaction hash |
from_chain_id | integer | Yes | Source chain ID |
to_chain_id | integer | Yes | Destination chain ID |
Example Request
curl "https://api.yieldo.xyz/v1/status?tx_hash=0xabc...&from_chain_id=42161&to_chain_id=8453"
Response
{
"status": "DONE",
"substatus": null,
"sending": {
"tx_hash": "0xabc...",
"tx_link": "https://arbiscan.io/tx/0xabc...",
"amount": "1000000000",
"chain_id": 42161
},
"receiving": {
"tx_hash": "0xdef...",
"tx_link": "https://basescan.org/tx/0xdef...",
"amount": "999500000",
"chain_id": 8453
},
"bridge": "stargate",
"lifi_explorer": "https://explorer.li.fi/tx/0xabc..."
}
Status Values
| Status | Description |
|---|
DONE | Transfer completed AND the user’s wallet received a share-mint event |
PENDING | Transfer is in progress |
FAILED | Transfer / deposit reverted on-chain |
NOT_FOUND | Transaction not yet indexed |
DONE status is verified end-to-end — the API checks the destination receipt for an ERC-20 Transfer(from=0, to=user, ...) event of the vault’s share token before reporting completion. If the bridge or composer call delivered tokens to the user’s wallet but the actual deposit didn’t mint shares (e.g. a silent composer drop, or a vault rejected the deposit at the function level), the status stays as partial rather than incorrectly reporting DONE. See substatus for the specific reason.
Response Fields
| Field | Type | Description |
|---|
status | string | Current transfer status |
substatus | string/null | Additional status detail from LiFi |
sending | object/null | Source chain transaction info |
receiving | object/null | Destination chain transaction info |
bridge | string/null | Bridge protocol used |
lifi_explorer | string/null | Link to LiFi explorer for this transfer |
Errors
| Status | Description |
|---|
| 404 | Transaction not found |
Verifying the Deposit On-Chain
The Yieldo router (V3.2.0) does not use signed deposit intents. Once the bridge is DONE, the deposit has either already happened (single-step / Composer flow — the bridge receiver called depositForAvailable atomically) or is pending the user’s step-2 tx (two-step flow — for non-composer vault types like Veda / Midas / Lido). In both cases the router emits:
event Routed(
bytes32 indexed partnerId,
uint8 partnerType,
address indexed user,
address indexed vault,
address asset,
uint256 amount,
uint256 shares
);
user == <user> and vault == <vault> on the destination chain gives you a definitive on-chain record of the deposit and the exact shares minted. The same event powers /v1/positions for portfolio reads.