I definitely agree with you on this fam, this really needs to be checked up on and make use of the advise you just provided.

Topboi0077

This would add real utility and more reasons to hold xORCA

Unruly

Good suggestions creator updates and searchable LP farms would make Wavebreak much more flexible for token communities

SAZIN

This features are nice initiative. I would love to see them adopted.

Olufemi

This feature would create a whole lot of flexibility for creators especially when the LP farms and vanilla projects are inclusive.

fisayo.

I definitely agree with you on this fam, this really needs to be checked up on and make use of the advise you just provided

i'm in support of the vanilla creator token suggedtion and creator post

$ORCA Documentation feedback for the developer docs (AI-assisted review of the public docs; no wallet connection, transaction, or purchase was made).

Two inconsistencies any new integrator hits by copy-pasting the "quick start":

1) The docs home page (docs.orca.so) still shows the Legacy SDK as its Quick Start example:

import { WhirlpoolContext, buildWhirlpoolClient } from "@orca-so/whirlpools-sdk";

const ctx = WhirlpoolContext.from(connection, wallet);

const client = buildWhirlpoolClient(ctx);

const pool = await client.getPool(poolAddress);

But the developer Quick Start (docs.orca.so/developers) tells you to install a different, current package:

npm install @orca-so/whirlpools @solana/kit

and the docs' own /llms.txt lists the two side by side: "TypeScript (Kit): @orca-so/whirlpools" vs "TypeScript (Legacy): @orca-so/whirlpools-sdk". Someone who starts from the home page installs the legacy package and then finds the SDK reference describing a different API (setRpc / setPayerFromBytes / swapInstructions from @orca-so/whirlpools).

2) The developer Quick Start swap snippet calls two helpers it never imports:

import { createSolanaRpc, address } from "@solana/kit";

import { swapInstructions, WhirlpoolDeployment } from "@orca-so/whirlpools";

...

const signer = await setPayerFromBytes(new Uint8Array(secret));

setDefaultFunder(signer.address);

setPayerFromBytes and setDefaultFunder are used but not imported, so the example throws "setPayerFromBytes is not defined" as written. The /llms.txt Setup block has the correct import (import { setRpc, setPayerFromBytes, setDefaultFunder } from "@orca-so/whirlpools").

For the team:

- Either label the home-page snippet as the Legacy path or replace it with the Kit snippet the developers page uses, so the same package is recommended everywhere.

- Add the missing import line to the Quick Start swap example; the llms.txt block already shows it.

Sources: https://docs.orca.so/ (home Quick Start block) | https://docs.orca.so/developers (install + swap snippet) | https://docs.orca.so/llms.txt (SDK package table and Setup block)

I read only the public documentation; I did not connect a wallet or execute anything. No affiliation with Orca.

Acknowledge the importance of the vanilla creator restore and the request to introduce a creator controlled LP farm tool on the token page.

Lekht

Orca's swap interface is the cleanest I have used on Solana — a beginner can complete a swap in seconds, which matters because most DEX interfaces overwhelm newcomers. The Whirlpools concentrated liquidity is powerful, but there is a real gap: the LP interface does not adequately warn about impermanent loss when narrowing a price range, and I could see a new LP getting burned. Fee tier selection (0.01% to 1%) is flexible but unexplained — a recommended default per pair type would help. On the positive side, $8B+ in 30-day v $ORCA olume shows the concentrated-liquidity model is working, and xORCA staking tying rewards to actual protocol revenue is honest tokenomics. Suggestion: add an LP simulator showing 'if price moves X%, you earn Y but lose Z' before confirming a position.

$ORCA is a gem!

I checked Whirlpools’ upgrade authority on-chain with the Solana CLI, the Squads V4 SDK and Osec’s public API, instead of relying on explorer labels. On 2026-10-13, solana program show listed GwH3Hiv5mACLX3ufTw1pFsrhSPon5tdw252DBs4Rx4PV as the upgrade authority, and the SDK derives that exact address as vault 0 of multisig BQsDWkL417U4tVE2sDnPks469pKdm6YzFgKH77doiEjF. Decoding that multisig shows 9 voting members, an approval threshold of 5 and a 24h (86,400 s) timelock, which matches the 5-of-9 multisig with a timelock described in Orca’s compliance disclosure.

One suggestion: the README says the program is deployed with a verifiable build and links Osec’s result, but at 07:25 UTC on 2026-10-13 that endpoint returned is_verified: false, commit None and no last_verified_at. That may just be a missing record; I’m not claiming a source mismatch. Audit counts also differ by page: the README lists 6, the compliance disclosure (updated May 26, 2026) says 8, and docs.orca.so lists 11 (latest 2026-09-30). Publishing the verified commit, hash and date, plus the commit each audit covered, would let readers tie the deployed binary to its audits.

$ORCA Adaptive Fee Pools are a good idea, but the fee visibility needs work. The user guide explains that the effective fee appears in the Pools page filter and on the pool detail banner, yet it never states the maximum a trader or LP can actually be charged. I only found the 10% hard cap on the total swap fee in the developer documentation. There is also no history: the banner shows the current effective fee, but nothing shows what a pool actually charged over the last 24 hours or 7 days, which is exactly what you need to compare it against a fixed-fee pool. Could Orca add the fee cap and a recent average effective fee (24h/7d) to the pool page and the swap quote?

$ORCA is a gem!

Orca's Position Simulator keeps crediting yield at out-of-range prices — with no warning.

I explored Orca's Whirlpool Simulator as a logged-out visitor today (no wallet connected). On the ORCA/SOL 0.16% pool Simulator tab, I set a ±5% position (range 0.0204391–0.0226066 SOL per ORCA) and dragged the simulated price down to 0.0201 — below the range floor, leaving the position 100% one-sided. The panel still displayed "Estimated Yield Earned 13.65%", "LP Opportunity Cost 2.40%", "LP vs. HODL +11.25%" with no out-of-range indicator or banner.

That contradicts Orca's own documented rule: "Your position does not accrue swap fees while it is out of range" (beginner guide), and the marketing site's "Your position earns swap fees only while it's in range." The "Time In-Range" D/H input is fully decoupled from the simulated price path — it assumes the position stays in range for the specified time even when the user drags the price outside it. A first-time LP could reasonably walk away believing an out-of-range position keeps paying.

Suggestion: when the simulated price exits [min, max], show an inline banner ("Simulated price is outside your range — this position would earn no fees here") and either zero out Estimated Yield Earned or annotate it as assuming price returns in range. Better: derive the in-range portion from the simulated price path instead of the decoupled Time In-Range input.

Acceptance check: drag the simulated price outside the range — the panel must either show the warning or stop crediting yield.

Scope: logged-out read-only exploration on 11 Oct 2026; I did not connect a wallet, create a position, or transact. AI assisted with drafting.

Sources:

- https://www.orca.so/pools/Hxw77h9fEx598afiiZunwHaX3vYu9UskDk9EpPNZp1mG (Simulator tab)

- https://docs.orca.so/liquidity/getting-started/beginner-guide

$ORCA — Show the actual trigger prices when setting a range alert.

AI-assisted documentation review, 10 Oct 2026. No deposit, trade, or live alert was created for this review.

Orca's Alerts guide describes 5%, 10%, and 20% options as proximity to either range boundary, but does not define the percentage denominator. That makes the warning distance hard to predict, especially for narrow ranges.

For an illustrative range of 100–120 USDC per SOL, “5%” of the range width gives inner thresholds of 101 and 119. Measuring 5% of each boundary price gives 105 and 114 instead. These are alternative interpretations, not measured Orca behavior. For a narrow 100–102 range, the second interpretation would make the two warning zones overlap.

Could the guide state the exact formula, and the alert form preview “notify below X or above Y,” with units? Please explain how overlapping zones and a condition already true at creation are handled. A worked narrow-range example would make setup much easier to verify.

The guide's distinction between a one-shot alert and a once-per-minute limit is useful. One further question: does “Every time” mean a new boundary crossing after recovery, or repeated checks while the condition stays true? A short enter/exit/re-enter timeline would clarify expected notification frequency.

Source: https://docs.orca.so/liquidity/manage/alerts

Bringing back vanilla token creation and adding LP farm tools would give creators so much more flexibility

Plenty

$ORCA

Orca simulator: make the assumptions visible

In an AI-assisted, wallet-free test of the SOL/USDC 0.04% pool, a roughly ±2% range and 7 days of Time In-Range showed approximately 6.13% Estimated Yield Earned. The numbers changed with live pool data.

The tooltip explains the historical 24-hour yield basis. The documentation clarifies that Time In-Range is active time within the range, not total elapsed time, and excludes slippage and priority fees. These conditions are easy to miss.

Could the result panel show “168 hours in range · historical 24H activity · excludes slippage and priority fees”? A 50%-fee-rate stress-test preset would also help users understand uncertainty. Does the estimate assume unchanged competing liquidity and reward rates?

No wallet connection, deposit, or transaction was performed during this review.

$ORCA — Orca: positive Total PnL can still underperform holding

The Position History & PnL guide says Total PnL compares a position with its deposits, not with holding those tokens outside the pool. It also says unharvested fees and rewards are included in unrealized PnL where supported data is available.

Illustrative example: deposit value $1,000; current LP value including unharvested yield $1,080; previously harvested yield $20; same original tokens simply held would now be worth $1,150. Ignoring other costs, the LP gained $100 versus its deposit but lagged holding by $50. Adding the unharvested yield again would double-count it.

Could Orca add an optional "versus holding" comparison beside Total PnL, using the original token quantities and handling later deposits/withdrawals consistently? Keep the existing PnL metric, and label the comparison's assumptions and excluded costs.

For incomplete history or missing prices, show N/A with the reason rather than an apparent zero. The guide already uses N/A for unavailable existing metrics.

Question: could a worked example like this be added to the guide so newcomers can distinguish fee income, absolute PnL, and performance versus holding?

Source (reviewed 7 Oct 2026):

https://docs.orca.so/liquidity/manage/position-history

AI-assisted documentation review; no liquidity transaction performed for this review.

Orca's docs give the xORCA rate as $ORCA in the vault divided by xORCA supply, and link the vault. I ran that on Oct 4: the vault (Ce5j11WAsSzM3nkzrw4Kw6v6ic3nbyqpv5eywjYKeKc5) holds 9,465,616 $ORCA against 4,544,582 xORCA, which gives 2.083. The stake page shows 1 xORCA at about 1.678 ORCA, and the stake page is right: stakes that day minted at 1.678. The staking program keeps a counter of ORCA owed to wallets that have unstaked, 1,839,631 today, and its math subtracts that before dividing. So 19% of the vault is an exit queue, and anyone pricing xORCA with the docs formula, say a lending market, would be 24% high.

I listed the queue from the program's accounts: 326 tickets from 257 wallets, summing to the counter exactly. The 116 still in the 7-day cooldown hold 1.75M ORCA, 2.9% of circulating supply, all withdrawable by Oct 11. One of them is 1,000,088 ORCA and matures Oct 5 at 16:57 UTC. The other 210 (92,144 ORCA) have matured and were never withdrawn, the oldest (0.001 ORCA) since Oct 6, 2025.

The buyback that feeds the rate swings day to day. In my replay of the vault's transactions the buyback bot added 13,294 ORCA on Sep 29 and 3,864 on Oct 3. The stake page shows 18.43% APR. On the 7.626M staked, Oct 3 alone annualizes to 18.5% and Sep 29 to about 64% (my arithmetic), so the APR looks like a one-day figure.

On control, the xORCA docs say 3-of-5 signatures. On chain, one Squads vault (GwH3Hiv5mACLX3ufTw1pFsrhSPon5tdw252DBs4Rx4PV) is the ORCA mint authority, the upgrade authority of Whirlpools and of the staking program, and the staking update authority. Its multisig needs 5 approvals from 9 voting members, with a 24-hour time lock. The tokenomics page calls the 75M supply fixed while that mint authority is live.

For the team:

1. Correct the docs formula, and publish the escrow total with its maturity dates next to the rate.

2. Update the multisig line, and either renounce the mint authority or say why it stays.

My question: what window is the APR computed over?

Note for TokenGems: the FAQ here answers "What is Orca DEX?" with one word, "AMM".

Let's not stop at LP rewards, there should also be an option to set up social post rewards.

SociallyWorkful

Agreed. It's pretty bare bones ATM, some extra features would be very welcome.

BakingCakes

$ORCA I tried a SOL → USDC swap on orca.so/trade as a first-time user (3 Oct 2026, Windows laptop, Chrome, Phantom connected with 0 SOL and 0 USDC, no trade).

What I noticed: with 1 SOL entered, a red message says "You need at least 1.0045 SOL to make this purchase". But the details panel shows Estimated Fees "<$0.01" (Liquidity Provider <$0.01, Network <$0.01). The extra 0.0045 SOL is about $0.54 at today's price, so the fees shown don't explain it, and I couldn't find anything on the page that does.

Why it matters: a new user with exactly 1 SOL can't tell how much extra to keep, or whether that 0.0045 SOL is spent or stays in the wallet.

Suggestion: add one line to the details panel, for example "Extra SOL needed: 0.0045 SOL", with a short tooltip saying what it's for and whether any of it comes back.

Small extra: the Route row shows "SOL → USDC (0%)". I couldn't tell what the 0% means (pool fee? price impact?). A tooltip would help here too.

Question: is part of the 0.0045 SOL the rent for creating my USDC token account (about 0.002 SOL), which I'd get back if I close that account later?

$ORCA — Make zero withdrawal limits unambiguous

I explored the CASH–USDC vault on Android Chrome without connecting a wallet or depositing. Under About → View More → Withdrawal Limits, the page displayed “0 CASH/hour” and “0 USDC/hour”, with both epoch reset timers showing “0 min”.

Does zero mean no withdrawal limit, withdrawals unavailable, or unavailable data? These imply very different exit conditions, but the displayed values do not distinguish them.

Could this section show an explicit state—“No limit”, “Withdrawals unavailable”, or “Data unavailable”—as appropriate? For an active limit, showing the remaining allowance and reset time would make it actionable.

This is feedback on the displayed information, not a claim that withdrawals fail: I did not attempt a withdrawal. Screenshots captured; feedback prepared with AI assistance.

$ORCA

I read Orca's Vaults docs (docs.orca.so/vaults/overview) as someone deciding whether to park liquidity in a Vault instead of managing a Whirlpool position by hand. This take is based on the documentation, not on a deposit.

The detail page is a good start: it shows Vault Provider, Strategy Address, Pool Address, Fee Tier, Oracle and capacity before you deposit. But a few things that decide whether I'd trust a Vault aren't covered:

1. The Vault Provider is described as "the strategy operator", a third party. Can the operator change the strategy rules, range or fee tier after I deposit? Can withdrawals ever be paused? One line on operator permissions would answer the biggest trust question.

2. Autoswap "may swap tokens during deposit or withdrawal to match the required token ratio". I couldn't find a slippage limit for that swap or a preview of the swap before I sign. Showing "you deposit X, Autoswap sells Y for Z, max slippage N%" would make the cost explicit.

3. "If a Vault is near capacity, your deposit may be capped or rejected." Which one? If it's capped, does Autoswap run on the full amount or only on the accepted part?

4. APY is "estimated annualized yield based on available data". Over what window: 24h, 7d, 30d? Short windows can make a fresh Vault look much better than it is.

5. The strategy may use an oracle "where applicable". What does the strategy do if the oracle is stale: pause rebalancing, or keep trading on old prices?

Question for the team: do you plan a per-Vault rebalance history, so depositors can see how often and at what cost the strategy actually rebalanced?

Despite the ever-changing Solana landscape, $ORCA's role as a primary liquidity hub remains critical. Its transaction volume and concentrated liquidity pools are fundamental drivers for $ORCA, not just ecosystem buzz. Core infrastructure holds value.