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: docs/osmosis-core/modules/ibc-rate-limit/README.md
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -11,7 +11,7 @@ This is done in exchange for a potential (one-way) bridge liveness tradeoff, in
11
11
12
12
The architecture of this package is a minimal go package which implements an [IBC Middleware](https://github.com/cosmos/ibc-go/blob/f57170b1d4dd202a3c6c1c61dcf302b6a9546405/docs/ibc/middleware/develop.md) that wraps the [ICS20 transfer](https://ibc.cosmos.network/main/apps/transfer/overview.html) app, and calls into a cosmwasm contract.
13
13
The cosmwasm contract then has all of the actual IBC rate limiting logic.
14
-
The Cosmwasm code can be found in the [`contracts`](./contracts/) package, with bytecode findable in the [`bytecode`](./bytecode/) folder. The cosmwasm VM usage allows Osmosis chain governance to choose to change this safety control with no hard forks, via a parameter change proposal, a great mitigation for faster threat adaptavity.
14
+
The Cosmwasm code can be found in the [`contracts`](https://github.com/osmosis-labs/osmosis/tree/main/x/ibc-rate-limit/contracts) package, with bytecode findable in the [`bytecode`](https://github.com/osmosis-labs/osmosis/tree/main/x/ibc-rate-limit/bytecode) directory. The cosmwasm VM usage allows Osmosis chain governance to choose to change this safety control with no hard forks, via a parameter change proposal, a great mitigation for faster threat adaptavity.
15
15
16
16
The status of the module is being in a state suitable for some initial governance settable rate limits for high value bridged assets.
17
17
Its not in its long term / end state for all channels by any means, but does act as a strong protection we
Copy file name to clipboardExpand all lines: docs/overview/features/ibc-rate-limit.md
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -15,7 +15,7 @@ This is done in exchange for a potential (one-way) bridge liveness tradeoff, in
15
15
16
16
The architecture of this package is a minimal go package which implements an [IBC Middleware](https://github.com/cosmos/ibc-go/blob/f57170b1d4dd202a3c6c1c61dcf302b6a9546405/docs/ibc/middleware/develop.md) that wraps the [ICS20 transfer](https://ibc.cosmos.network/main/apps/transfer/overview.html) app, and calls into a cosmwasm contract.
17
17
The cosmwasm contract then has all of the actual IBC rate limiting logic.
18
-
The Cosmwasm code can be found in the [`contracts`](./contracts/) package, with bytecode findable in the [`bytecode`](./bytecode/) folder. The cosmwasm VM usage allows Osmosis chain governance to choose to change this safety control with no hard forks, via a parameter change proposal, a great mitigation for faster threat adaptavity.
18
+
The Cosmwasm code can be found in the [`contracts`](https://github.com/osmosis-labs/osmosis/tree/main/x/ibc-rate-limit/contracts) package, with bytecode findable in the [`bytecode`](https://github.com/osmosis-labs/osmosis/tree/main/x/ibc-rate-limit/bytecode) directory. The cosmwasm VM usage allows Osmosis chain governance to choose to change this safety control with no hard forks, via a parameter change proposal, a great mitigation for faster threat adaptavity.
19
19
20
20
The status of the module is being in a state suitable for some initial governance settable rate limits for high value bridged assets.
21
21
It's not in its long term / end state for all channels by any means, but does act as a strong protection we
Copy file name to clipboardExpand all lines: docs/overview/integrate/pool-setup.md
+23-3Lines changed: 23 additions & 3 deletions
Original file line number
Diff line number
Diff line change
@@ -26,13 +26,32 @@ Note: When specifying token denominations that are represented as `ibc/<hash>` v
26
26
27
27
A Supercharged Pool is Osmosis’ Implementation of [Uniswap’s Concentrated Liquidity](https://docs.uniswap.org/concepts/protocol/concentrated-liquidity). In addition to full-range positions, liquidity providers can also ‘concentrate’ their liquidity to only apply within a defined price range. When the market price is within the defined price range, the liquidity earns comparatively more swap fees and incentives at the cost of increased impermanent loss; but when the market price is outside of the defined price range, the position doesn’t earn any swap fees (or incentives).
28
28
29
-
On Osmosis, for technical and UX reasons, some parameters are restricted to a limited set of governance-approved values. For example, the allowable quote assets are limited to a small set of tokens, meaning that all CL pools must contain at least one of these authorized tokens (which are listed below). The same applies to spread factor–basically the same thing as swap fee–and tick spacing–used for refining the granularity of possible positions.
29
+
On Osmosis, for technical and UX reasons, some parameters are restricted to a limited set of governance-approved values. For example, the allowable quote assets are limited to a small set of tokens, meaning that all CL pools must contain at least one of these authorized tokens (which are listed below). The same applies to spread factor–-basically the same thing as swap fee–-and tick spacing–-used for refining the granularity of possible positions.
30
30
31
31
### Create Pool
32
32
33
33
#### Osmosis Zone
34
34
35
-
As of writing, Supercharged Liquidity Pools cannot be created via the Osmosis Zone app.
35
+
To create a Supercharge Liquidity Pool on Osmosis via the Osmosis Zone app:
36
+
37
+
IMPORTANT: If it is desired to entirely complete the setup of a Supercharged pool via the Osmosis Zone app--.i.e., not using osmosisd CLI--then the pool creator must add an initial liquidity position immediately after creating the pool, without closing the modal. If the pool creation flow is disrupted before the initial liquidfity has been added, e.g., by closing the modal or navigating to a different page, then it will not be possible to add initial liquidity to the new pool via the Osmosis Zone app, in which case it can only be added via osmosisd CLI (see [Join Pool](#join-pool) for steps).
38
+
39
+
- Go to app.osmosis.zone
40
+
- Connect a Wallet
41
+
- Go to Pools page
42
+
- Create New Pool button
43
+
- Choose Supercharged pool
44
+
- Next
45
+
- Under Base, Add new token
46
+
- Select a token
47
+
- Under Quote, click the dropdown (default selection is USDC)
48
+
- Set Swap Fee
49
+
- Tick ‘I understand that creating a new pool will cost 20 USDC.'
50
+
- Create Pool
51
+
- Approve the transaction via the connected wallet (20 USDC will be charged at this stage).
52
+
- Enter a >0 amount for both tokens
53
+
- Next
54
+
- Approve the transaction via the connected wallet
- As mentioned in the help text, denom-1 (the quote denom), tick spacing, and spread factors must all be authorized by the concentrated liquidity module, and these can be confirmed by querying the chain: `osmosisd query concentratedliquidity params`
62
-
- denom-1: Must be from a set of authorized ‘quote’ assets, which, as of writing, are:
81
+
- denom-1: Must be from a set of authorized ‘quote’ assets, which include (not exhaustive):
0 commit comments