$ORCA we need some more features on your launchpad Wavebreak
- let the token creator post updates on the token page

- let the token creator set up LP farm rewards from the token page and let people search for farm rewards on the token search page

Also: Can you please bring back the vanilla token creator? Being able to just create a token by itself (i.e., not forced into a LP on creation) gave us a lot of flexiblity to pick interesting LP pairs (like ORCA or xORCA..) and run rewards programs (LP farms, bounties etc...).

$SI

I noticed there are multiple tokens using the Super Inu name and $SI ticker across different chains, while the Solana version has its own distinct contract. That creates a genuine verification problem for new users because a search for “Super Inu SI” can surface different assets. Could you make the official chain and contract address a permanent part of the project’s primary identity across the website, X and exchange listings, perhaps with a single canonical verification page?

$NVDAx Tested the public Proof-of-Reserves API behind xStocks (api.xstocks.fi/api/v2/public/proof-of-reserves/NVDAx) against the actual on-chain supply of the Solana deployment, not just the dashboard.

Two issues, both independently verifiable:

1. The numbers don't add up. The PoR endpoint reports a global circulating supply (aggregated across the 11 chains NVDAx is deployed on) of 188,424.31 units, backed by 188,473.25 NVDA shares held via Alpaca. But querying Solana's own public RPC (getTokenSupply) for the Solana mint (Xsc9qvGR1efVDFGLrVsmkzv3qi45LTBjeUKSPmx9qEh) directly returns 321,815.80 units — ~70% more than the entire reported global supply across all 11 chains combined. A single chain's supply cannot exceed the global total unless the "global" figure is wrong or doesn't actually include Solana.

2. The "live" attestation may be cached. I queried the same PoR endpoint twice, about an hour apart, from two different machines. Both returned the identical timestamp down to the millisecond (2026-10-01T01:08:17.190Z), suggesting this isn't a live attestation refreshing per request — it's a stale snapshot being served as if current.

Questions for the team:

Does the global circulatingSupply field in the PoR endpoint actually include the Solana deployment? If so, how is a single chain's on-chain supply larger than the stated global total?

How often is the PoR snapshot actually refreshed, and can the response include its own cache/generation timestamp separate from the "as of" timestamp shown?

This is based on the issuer's own documented public API, cross-checked against Solana's public RPC — reproducible by anyone with the two commands.

$STREAM if my tokens are locked until december and i need to change wallets in october, can i move the allocation to my new wallet while keeping the original unlock date?

the Locks guide leaves this unclear. under “Immutable constraints,” it says transferableByRecipient can be enabled so the recipient can transfer the lock. but under “Available lifecycle operations,” it says transfers are disabled after creation.

this matters for someone planning to move their allocation to a hardware wallet. they need to know which permission to choose when the lock is created and what that permission actually allows.

which section reflects the current behaviour? an example showing a recipient changing wallets before the unlock date would make the answer much clearer.

source: Streamflow Locks guide

$SWTCH project has officially shut down https://x.com/SwitchboardFDN/status/2101088966640611478?s=20

Most of the liqudity was pulled a few months ago.