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/whirlpool/docs/02-Architecture Overview/01-Account Architecture.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@
6
6
7
7
## WhirlpoolsConfig
8
8
9
-
The owner of a Config account has the authority to define the many authorities over the pools that it owns (ex. default fees, collect protocol fees etc) . Whirlpools visible on the ORCA UI are all derived and controlled by a WhirlpoolsConfig account owned by the ORCA foundation. To learn more about managing pools, start [here](../03-SDKs/03-Whirlpool%20Management/01-Create%20Pool.mdx).
9
+
The owner of a Config account has the authority to define the many authorities over the pools that it owns (ex. default fees, collect protocol fees etc.). Whirlpools visible on the ORCA UI are all derived and controlled by a WhirlpoolsConfig account owned by the ORCA foundation. To learn more about managing pools, start [here](../03-SDKs/03-Whirlpool%20Management/01-Create%20Pool.mdx).
10
10
11
11
Users and other protocols are free to deploy their own WhirlpoolsConfig account on our Whirlpool program to spawn their own set of liquidity pools.
12
12
@@ -31,11 +31,11 @@ Users are able to perform position management and fee/reward collection operatio
31
31
32
32
## TickArray
33
33
34
-
To learn about TickArry, read [Understanding Tick Arrays](./03-Understanding%20Tick%20Arrays.md)
34
+
To learn about TickArray, read [Understanding Tick Arrays](./03-Understanding%20Tick%20Arrays.md)
35
35
36
36
## Position
37
37
38
-
Positions represents a set of liquidity distributed on a price range within a single Whirlpool. To learn more, read [Tokenized Positions](./04-Tokenized%20Positions.md)
38
+
Positions represent a set of liquidity distributed on a price range within a single Whirlpool. To learn more, read [Tokenized Positions](./04-Tokenized%20Positions.md)
Copy file name to clipboardExpand all lines: docs/whirlpool/docs/02-Architecture Overview/07-TokenExtensions Support.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -133,7 +133,7 @@ To clarify the context of accounts passed as `remaining_accounts`, the v2 instru
133
133
#### Security notes
134
134
- In solana, indirect re-entrance will be rejected. So transfer hook program cannot call Whirlpool program.
135
135
- TransferHook program cannot modify transfer amount. It will be called AFTER token transfer processing.
136
-
- Token-2022 program remove signer and writable flag of the source, destination and owner when calling the TransferHo[ok program even if they are passed as extra accounts. The source and destination are not updated and the owner's signature is not used unintentionally.
136
+
- Token-2022 program remove signer and writable flag of the source, destination and owner when calling the TransferHook program even if they are passed as extra accounts. The source and destination are not updated and the owner's signature is not used unintentionally.
137
137
138
138
#### TokenBadge request
139
139
The TransferHook extension is a relatively new feature in the ecosystem, and its use cases are still being explored.
@@ -149,4 +149,4 @@ While it’s still undecided which types of TransferHook tokens will be eligible
149
149
- Extensions that block transactions based on the amount of tokens to be transferred are undesirable because they cause transactions to fail in ways that are surprising to pool users. On the other hand, failing transfers to sanctioned wallets according to some public standard will not obstruct pool usage for many users.
150
150
- TransferHook must not request large numbers of accounts that would increase transaction size.
151
151
- TransferHook should not attempt any token transfers (including WSOL and native SOL).
152
-
- TransferHook should not attempt imposing any kind of additional fees.
152
+
- TransferHook should not attempt imposing any kind of additional fees.
Copy file name to clipboardExpand all lines: docs/whirlpool/docs/03-SDKs/01-Overview.mdx
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -18,7 +18,7 @@ What follows is an overview of our SDK suite, distinguishing between the various
18
18
The High-Level SDKs are our top recommendation for anyone who wants to integrate with the Whirlpool Program. These SDKs abstract many of the underlying complexities, such as tick array management, and makes managing pools and positions, and executing swaps much simpler. It is suitable for developers who need efficient, high-level functionalities and want to minimize manual configuration and management.
- Compatible with Solana SDK versions `^1.18.0` but `<3.0.0`. By default, Cargo will install the latest version of Solana SDK `^v2`. This can cause dependcy issues when using older versions. To solve this you can apply a lockfile patch with the following command:
21
+
- Compatible with Solana SDK versions `^1.18.0` but `<3.0.0`. By default, Cargo will install the latest version of Solana SDK `^v2`. This can cause dependency issues when using older versions. To solve this you can apply a lockfile patch with the following command:
- The Legacy SDK has has separate utility classes for certain math operations such as `PoolUtil`, `TickUtil`, `TickArrayUtil`, and `SwapUtils`. For quotes, there are separate functions exported, such as `decreaseLiquidityQuoteByLiquidity`, `increaseLiquidityQuoteByInputToken`, `swapQuoteByInputToken`, `collectFeesQuote`, `collectRewardsQuote`, and more. Check out the reference docs in the navbor for more details.
38
+
- The Legacy SDK has separate utility classes for certain math operations such as `PoolUtil`, `TickUtil`, `TickArrayUtil`, and `SwapUtils`. For quotes, there are separate functions exported, such as `decreaseLiquidityQuoteByLiquidity`, `increaseLiquidityQuoteByInputToken`, `swapQuoteByInputToken`, `collectFeesQuote`, `collectRewardsQuote`, and more. Check out the reference docs in the navbor for more details.
39
39
40
40
## 3. Low-Level SDKs
41
41
@@ -46,7 +46,7 @@ This SDK provides direct program interactions and is designed for developers who
- Compatible with `solana-program` versions `^1.18.0` but `<3.0.0`. By default, Cargo will install the latest version of Solana SDK `^v2`. This can cause dependcy issues when using older versions. To solve this you can apply a lockfile patch with the following command:
49
+
- Compatible with `solana-program` versions `^1.18.0` but `<3.0.0`. By default, Cargo will install the latest version of Solana SDK `^v2`. This can cause dependency issues when using older versions. To solve this you can apply a lockfile patch with the following command:
0 commit comments