Blinks

Turn Solana Actions into shareable, embeddable links across the social web.

Recipe

https://your-blink-proxy.example/?action=https://actions.example.com/vote

When to reach for this:

• Distribution on X, Discord, and Blink-compatible surfaces.
• Growth loops where users share actionable links.
• Campaigns needing preview cards with icons.

Working Example

<!-- Partner sites embed via Blink provider URL + your action endpoint -->
<a href="https://dial.to/?action=https://actions.example.com/swap">
  Swap on MyProtocol
</a>

// Your action endpoint still implements GET metadata + POST transaction
// See actions-the-spec

What this demonstrates:

• Action URL must implement spec GET/POST.
• Blink provider unfurls GET metadata into interactive UI.
• HTTPS and CORS requirements still apply.

Deep Dive

How It Works

• Blink client fetches action metadata for rich card.
• User connects wallet in context of social app or portal.
• Transaction POST flow identical to Actions.
• Registry of blink providers evolves - test target platforms.

Gotchas

• Unverified action URLs - users sign malicious txs. Fix: domain allowlists in clients; educate users.
• Stale unfurl cache - wrong title after deploy. Fix: version query param on icon URL.
• Broken icon HTTPS - card fails render. Fix: CDN with valid TLS cert.
• Mainnet action on devnet wallet - failures. Fix: cluster in metadata when supported.
• Overprivileged transactions - drain risk. Fix: least-privilege instructions per action.

Alternatives

FAQs

Related

• Actions (the spec) - endpoint shape
• Security & Verification - trust
• Solana Pay Basics - payments

Stack versions: This page was written for Agave 4.1.1, Solana CLI 3.0.10, Anchor 0.32.1, anchor-lang 0.32.1, Rust 1.91.1, @solana/kit 7.0.0, Surfpool 0.12.0, and LiteSVM 0.6.x.