You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: cw20-swaps.mdx
+1-2
Original file line number
Diff line number
Diff line change
@@ -60,9 +60,8 @@ In particular, this means you cannot perform the following actions in 1 transact
60
60
61
61
* IBC transfer after purchasing a cw20 asset
62
62
63
-
63
+
<Framecaption="Chain 1 is the origin chain where the cw20 token can be swapped freely, but it cannot be transferred to another chain in the same transaction."></Frame>
64
64
65
-
Chain 1 is the origin chain where the cw20 token can be swapped freely, but it cannot be transferred to another chain in the same transaction.
66
65
67
66
* Call a contract on a remote chain after purchasing a cw20 asset (e.g. since this requires an IBC transfer under the hood)
Copy file name to clipboardExpand all lines: getting-started.mdx
+1-1
Original file line number
Diff line number
Diff line change
@@ -3,7 +3,7 @@ title: "Introduction"
3
3
description: "This pages explains what the Skip API is, gives examples of applications built with it, and provides guidance on standard ways to use it."
Copy file name to clipboardExpand all lines: handling-cross-chain-failure-cases.mdx
+2-4
Original file line number
Diff line number
Diff line change
@@ -20,9 +20,8 @@ There are two types of IBC failures that may occur when a user attempts to trave
20
20
* The user attempts to transfer tokens from Neutron to the hub, but the packet isn't picked up by a relayer for more than 5 minutes (past the timeout\_timestamp). When a relayer finally comes online, it relays a timeout message to Neutron, releasing the user's ATOM back to their address on Neutron where they first had it.
21
21
***For transfer-only routes:** This is the only kind of failure that may happen on a route that only contains transfers. Either the user's tokens will reach their destination chain as intended, or they will wind up with the same tokens, on the same chain where they started.
22
22
23
-
23
+
<Framecaption="In a pre-swap or swap related error, the user will end up with the same tokens they started with on their initial chain (e.g. ATOM on Neutron in this example)"></Frame>
24
24
25
-
In a pre-swap or swap related error, the user will end up with the same tokens they started with on their initial chain (e.g. ATOM on Neutron in this example)
26
25
27
26
2.**Post-swap failures:**
28
27
***Description**: These are failures that occur on the sequence of transfers between the swap venue chain and the user's destination chain, after the user's origin tokens have already been successfully swapped for their desired destination asset.
@@ -34,9 +33,8 @@ In a pre-swap or swap related error, the user will end up with the same tokens t
34
33
***Examples:** Consider a route where the source asset is ATOM on Neutron, the destination asset is STRIDE on Stride, and the swap takes place on Osmosis:
35
34
* Suppose the swap took place and the transfer to Stride has been initiated, but the Relayer between Osmosis and Stride is down. So the packet’s timeout occurs after 5 minutes. When the Relayer comes back online after 8 minutes, it relays a timeout message to Osmosis, releasing the user’s STRIDE, which gets forwarded to their Osmosis address
36
35
37
-
36
+
<Framecaption="In a post-swap error, the user will end up with their destination asset tokens in their address on the chain where the swap took place (e.g. STRIDE on Osmosis in this example)"></Frame>
38
37
39
-
In a post-swap error, the user will end up with their destination asset tokens in their address on the chain where the swap took place (e.g. STRIDE on Osmosis in this example)
4. Voila, you're done! The sharable link is now copied to your clipboard for you to embed on your website for an easy onboarding/deposit experience, to tweet about your bags, or to simply share it with your friends!
Copy file name to clipboardExpand all lines: ibc-routing-algorithm.mdx
+3-3
Original file line number
Diff line number
Diff line change
@@ -25,7 +25,7 @@ description: "This page describes the IBC token routing problem and the algorith
25
25
26
26
IBC transfers data over "channels" that connect two chains. Channels are identified by human-readable port names (e.g. "transfer") and channel IDs (e.g. channel-1). For example, consider a transfer channel between Terra2 and Axelar:
_Notice that both chains maintain their own channel IDs for the channel, which might not be the same. As an analogy, you might think of the different chains as cities and the channel as a road connecting them. IBC packets are cars driving across the road_
31
31
@@ -54,11 +54,11 @@ Now that you understand that IBC denoms get their names from their paths, you un
54
54
55
55
Continuing the example from above, WETH.axl transferred directly from Axelar to Terra2 will have a different denom than WETH.axl transferred through Osmosis:
To make matters worse, multiple channels can exist between the same two chains (IBC is permissionless afterall), and IBC uses channel identifiers--not chain identifiers--to construct denoms. That means two different versions of the same asset will exist on the destination chain even when tokens are transferred from the same source chain, if they're transferred over two different channels:
Copy file name to clipboardExpand all lines: multi-chain-realtime-transaction-and-packet-tracking.mdx
+1-1
Original file line number
Diff line number
Diff line change
@@ -13,7 +13,7 @@ You can also use it to identify failure cases (e.g. a swap that fails due to sli
13
13
14
14
For example, if one of your end users initiates a swap that begins with ATOM on Neutron and concludes with JUNO on Juno, you can use the lifecycle tracking to report when the ATOM moves from Neutron to the Hub, when it reaches Osmosis, and when the JUNO finally arrives safely on Juno.
3. Use `/fungible/msgs` (`SkipRouter.msgs`) to get a transaction for the user to sign after they've locked in the route & begun the transaction creation process
Copy file name to clipboardExpand all lines: safe-swapping-how-to-protect-users-from-harming-themselves.mdx
+2-2
Original file line number
Diff line number
Diff line change
@@ -57,7 +57,7 @@ Loud visual emphasis of the values that exceed safe tolerances is the most effec
57
57
58
58
For example, when a swap exceeds our `PRICE_IMPACT_THRESHOLD` on [ibc.fun](ibc.fun), we auto-open the drop-down that normally hides price impact and highlight the whole field in red.
0 commit comments