$RAY I tested Raydium’s SDK pool lookup. A SOL/USDC pool loaded normally. Adding Solana’s System Program address as a deliberate non-pool input returned null alongside the real pool.

In @raydium-io/raydium-sdk-v2 version 0.2.74-alpha, fetchPoolById’s return type only includes pool objects. So pools.map(pool => pool.id) passed strict TypeScript checks, but that line threw a TypeError at runtime. The error repeated, while adding a null guard worked.

The demo FAQ already mentions null results, so shouldn’t the SDK’s return type account for them too?

Suggestion: include null in the return type and show how to handle it in the lookup example. That would help someone building a pool watchlist handle missing entries without crashing.

Links:
https://github.com/raydium-io/raydium-sdk-V2/blob/e2e8bcd865189c994682a9477ec8eaf1e2da8aaf/src/api/api.ts#L231

https://github.com/raydium-io/raydium-sdk-V2-demo#readme

$ORCA RCA I tested Orca’s public pool API. GET /pools?size=2 returned two pools, but the API overview and pool response example show meta.next, while the live response uses meta.cursor.next.

Following the documented structure could make a client stop after that first page. Passing the value of meta.cursor.next as the next query parameter returned two more distinct pools. Both test runs gave the same result.

Suggestion: update both examples to match the OpenAPI schema, which already has the correct nesting. Could you also add a complete second-page request? That would help someone building a pool picker avoid leaving out results without realizing it.

Only the first two pages were tested. No wallet was connected and no transactions were sent.

Links:
https://docs.orca.so/api-reference/overview#response-format

https://docs.orca.so/api-reference/whirlpools

https://api.orca.so/docs

$STREAM EAM Looked through Streamflow’s vesting docs and noticed two different bulk-creation limits. Step 5 of the tutorial says a CSV can include up to 100,000 recipients, with all contracts created in one operation. But the bulk-contract guide says 60–300 contracts at once, depending on the wallet.

Are these describing different things—how many recipients you can upload versus how many contracts you can create per batch? For a team with 1,000 recipients, does Streamflow handle the batching automatically, or do they need to split the CSV themselves?

Suggestion: clarify what each limit refers to in both guides. A worked example with 1,000 recipients would help: which wallet is being used, how many approvals to expect, and how to resume an interrupted batch without creating duplicate contracts.

I checked the docs only, so I haven’t tested how a large upload behaves in the app.
Links:
https://streamflow.finance/blog/how-to-create-a-token-vesting-schedule-on-solana-step-by-step-tutorial
https://docs.streamflow.finance/en/articles/9670413-create-a-vesting-contract