$STREAM — could the team reconcile the claim-cost examples before recipients fund their wallets?

This is an AI-assisted documentation review. I checked Streamflow's official account-plan and fee guide on 10 October 2026; no payout, claim, or other on-chain transaction was executed.

Two specific points would benefit from clarification:

1. The Individual table gives an airdrop claim service fee of 0.009–0.017 SOL and a network fee of 0.00299 SOL, but lists a total of 0.0237–0.0317 SOL. Adding the displayed components gives 0.01199–0.01999 SOL instead. The published totals would imply a 0.0147 SOL network component. The Business detail table repeats the same mismatch. Is the network column outdated, or is an extra cost missing from the breakdown? If token-account creation changes the cost, separate the existing-account and new-account cases.

2. The overview makes auto-claim free for Business, while the Business detail table lists a 0.25 SOL service fee plus 0.0147 SOL network cost. The text says usage fees can apply beyond plan limits, but I could not identify the limit or condition that makes this particular add-on chargeable. Does the lower table cover Starter, out-of-plan usage, or another case? Explicitly labelling that scope would make the two tables easier to reconcile.

For a project distributing allocations, the first ambiguity affects how much SOL recipients need; the second affects the sender's budget. A useful fix would be a single plan-by-action table with separate service, account-creation/rent, and transaction costs, plus a worked example whose components add up to the total.

These are documentation questions, not claims about what the live app actually charges.

Source: https://docs.streamflow.finance/en/articles/9675153-individual-vs-business-costs-of-using-streamflow

$BUZZ What makes BUZZ interesting is its connection to the idea of making DeFi easier to understand and use through AI-powered agents. The concept of interacting with financial tools using natural-language commands could help make complex blockchain activities more accessible.

However, I think clearer documentation explaining the relationship between $BUZZ, Hive Labs, and APYS, along with a practical demonstration of the product, would make the project easier for new users to understand. Better onboarding and transparency would help visitors understand what the ecosystem actually offers.

$PIPE I sometimes run bandwidth and storage nodes, so I price infra before I buy it. Pipe's object storage is about 3 USDC/TB to read and 15 USDC/TB to write.

That's inverted from everyone else and I think it's worth saying out loud. Amazon S3 charges nothing to upload and about $90/TB to get data out. Cloudflare R2 is free egress but $15/TB every month it just sits there. Pipe is the opposite - pricey once on the way in, cheap on the way out.

What I can't tell from the pricing page is whether there's a charge for data at rest. "Billed for the data you read and write" reads like there isn't one. If that's right, 1 TB parked for a year is about 15 USDC on Pipe versus roughly 180 on R2 - and that's a far bigger deal than the read rate. It'd make Pipe the obvious pick for backups and archives. If there IS a monthly storage line, it belongs on this panel next to reads and writes.

I went through $PRCL Risk Management & Trading docs (documentation review only, I didn’t trade) and I have some feedback on the documentation about the Trading Fees and Margin sections.

The docs define makers as traders who “widen skew” and takers as those who “decrease skew.” A few lines later, they say trades that only increase skew pay the taker rate, while trades that only decrease skew pay the lower maker rate.

These statements seem to contradict each other. The Price Impact section (reducing skew gets a discount) suggests the fee rule is the intended one and the definition is inverted, but a trader can’t be sure which side pays less.

I also noticed the initialRatio formula uses the same variable on both sides of the equation. Maybe I’m missing some context, but clarifying what base value is used on the right side would help.

A simple worked example showing the fee for a trade that increases skew, one that decreases it, and one that flips it would make this much easier to follow.

Are these rules still up to date for Parcl v3?

Docs: https://docs.parcl.co/protocol-overview/risk-management-and-trading