Orderly Sdk Wallet Connection

PassAudited by ClawScan on May 1, 2026.

Overview

This is an instruction-only developer guide for wallet connection; the wallet/account and package-install guidance is expected for its stated DEX integration purpose.

This appears safe as a documentation-only wallet integration guide. Before using it in a production DEX, verify the referenced packages with official sources, keep wallet prompts transparent, and avoid handling private keys or unnecessary wallet permissions.

Findings (2)

Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.

What this means

If implemented, the app may request wallet connection, reveal wallet addresses/networks, and initiate wallet consent flows.

Why it was flagged

The guide is explicitly about connecting wallets and managing authentication state, which involves user blockchain account identity and delegated wallet interactions.

Skill content
- Supporting multiple wallet types (MetaMask, Phantom, etc.)
- Implementing chain switching
- Managing authentication state
Recommendation

Use clear user consent prompts, request only the needed wallet permissions, never ask for seed phrases or private keys, and document what signatures or network switches are required.

What this means

Following the guide will add external packages to a project, so the project inherits the security and maintenance posture of those dependencies.

Why it was flagged

The guide instructs users to install third-party npm packages. This is expected for wallet integration, but it introduces normal dependency provenance and versioning considerations.

Skill content
npm install @orderly.network/wallet-connector
npm install @web3-onboard/injected-wallets @web3-onboard/walletconnect
npm install @solana/wallet-adapter-base @solana/wallet-adapter-wallets
Recommendation

Verify package names against official Orderly/Web3/Solana documentation, pin dependency versions as appropriate, and use normal dependency review tooling before production use.