On the raindex webapp, the Orders page returns/shows no orders until a wallet is connected — you can't browse or view any orders at all while disconnected.
Orders are public on-chain / subgraph data, so read-only browsing should NOT require a wallet. A wallet should only be needed for actions that move funds or require signing (create order, deposit, withdraw, remove, take/clear).
Expected: the Orders list (and order detail pages) load and are fully browsable while wallet-disconnected, across the supported networks. Connecting a wallet additionally surfaces the user's own orders and enables actions — but is not required to see the public order book.
Actual: no orders are retrievable/visible until a wallet is connected.
Likely cause to check: the orders query/list is gated behind the connected-account/chain context (e.g. depends on the wallet's chain id or account) rather than the selected network(s); decouple the public read path from wallet state.
Co-Authored-By: Claude noreply@anthropic.com
On the raindex webapp, the Orders page returns/shows no orders until a wallet is connected — you can't browse or view any orders at all while disconnected.
Orders are public on-chain / subgraph data, so read-only browsing should NOT require a wallet. A wallet should only be needed for actions that move funds or require signing (create order, deposit, withdraw, remove, take/clear).
Expected: the Orders list (and order detail pages) load and are fully browsable while wallet-disconnected, across the supported networks. Connecting a wallet additionally surfaces the user's own orders and enables actions — but is not required to see the public order book.
Actual: no orders are retrievable/visible until a wallet is connected.
Likely cause to check: the orders query/list is gated behind the connected-account/chain context (e.g. depends on the wallet's chain id or account) rather than the selected network(s); decouple the public read path from wallet state.
Co-Authored-By: Claude noreply@anthropic.com