sage-walletconnect_skill

Overview

This skill provides WalletConnect protocol integration for Sage, enabling dApp connectivity for coin discovery, message signing, and direct transaction broadcasting. It exposes endpoints to filter unlocked coins, retrieve spendable asset coins (CAT, DID, NFT), sign messages by public key or address, and send spend bundles immediately. The skill streamlines secure dApp–wallet interactions while preserving on-chain requirements like lineage proofs for CAT spends.

How this skill works

The skill inspects wallet coin state and returns spendable coin objects including coin metadata, puzzle data, confirmation index, and lineage proofs where required. It filters coins by unlocked status, queries asset-specific spendable coins using type and asset_id, and exposes signing endpoints that return public key and signature. For transactions it accepts a spend_bundle and broadcasts it immediately, returning a status code and optional error.

When to use it

• When a dApp needs to find spendable coins for a specific asset (CAT, DID, NFT).
• When a dApp requires proof of address ownership via message signing without performing a spend.
• When building and broadcasting a transaction from a connected dApp and you want immediate network submission.
• When filtering a large coin set to only those available for spending (unlocked).
• When a dApp flow uses WalletConnect to request user approval and signing within Sage.

Best practices

• Always request get_asset_coins with offset/limit pagination to avoid large responses.
• Include included_locked=false for standard spends; include lineage_proof when preparing CAT spends.
• Present clear UX for users before calling sign endpoints so they understand what they approve.
• Verify sign_message responses (public_key and signature) on the dApp side before proceeding.
• Check send_transaction_immediately status field: 1 indicates success; handle other values as errors and surfacing error text if provided.

Example use cases

• A dApp requests CAT coins for a user to construct a token transfer and then asks the user to sign the transaction.
• A web app verifies wallet ownership by requesting a signed challenge via sign_message_by_address before granting access.
• An NFT marketplace queries get_asset_coins for NFT-type assets to list sellable items and collect lineage data.
• A developer tool filters a bulk coin list to unlocked coins prior to building a consolidation spend.
• A desktop dApp broadcasts a prebuilt spend_bundle using send_transaction_immediately for rapid settlement.