Solana launched Actions and blinks for transactions through links

The Solana Foundation launched Solana Actions and blockchain links, or “blinks,” on June 25, 2024, introducing a developer standard intended to let a website, social feed or QR code become the starting point for a Solana transaction. The Foundation said the tools were immediately available for integration; the technical proposal published on the same date described how links would expose Actions to compatible clients.

The development mattered because it targeted a distribution problem rather than changing Solana’s consensus rules. Crypto activity generally began inside a wallet-aware application. Actions and blinks were designed to move the transaction prompt into places where users already encountered information, while leaving final approval in a wallet. That could shorten the path from seeing an offer, vote or payment request to preparing an onchain transaction.

How Actions and blinks worked

An Action was a standardized application-programming interface that returned information a client could display and, after a user made a selection, a transaction for the wallet to review. In the documented flow, a client requested human-readable metadata, rendered choices, then requested a signable transaction. The wallet still had to present that transaction, obtain the user’s signature and submit it to Solana.

A blink was the link-facing layer. The June 25 specification described three ways to surface one: a domain-level `actions.json` mapping, a URL containing an encoded Action endpoint, or a `solana-action:` link. A compatible wallet extension, bot or website could detect that structure and render controls around it. The originating social platform did not itself need native Solana logic.

That distinction was important. The Foundation’s announcement described websites and social platforms as transaction surfaces, but a blink was not a completed transfer embedded in a URL. It was a route to metadata and a proposed transaction. Execution still depended on compatible client software, a connected wallet, user approval and network confirmation.

Distribution was the product

The immediate institutional significance was interoperability at the application edge. The same basic interface could support a swap, payment, vote, stake or digital-collectible transaction without every distribution surface building a separate blockchain integration. Contemporaneous coverage from CoinDesk and Blockworks reported initial support from Solana wallets including Phantom and Backpack, and described X as the first prominent social setting.

That made the release a bet on social and link-based distribution. A protocol could place an actionable prompt where its audience already gathered, rather than requiring every prospective user to find and navigate a decentralized application. The interpretation is narrower than a claim of mass adoption: June 25 established that the specification and integrations had launched, not that users would trust them, platforms would support them broadly or transaction activity would increase.

The security boundary remained the wallet

The June 25 technical proposal explicitly retained trust assumptions. Each Action was hosted on a domain that the user had to trust, and the returned transaction still required simulation, signing and sending. Solana’s documentation also described a registry approach for links from pre-verified sources, while allowing clients to choose their own verification policy.

Those controls eliminated neither phishing risk nor the need to inspect a wallet prompt. A familiar-looking post could still direct a user toward an untrusted endpoint, and standardized presentation could make harmful requests easier as well as legitimate ones. The launch record did not supply adoption statistics, independent security testing or evidence that every announced use case worked across every client.

What June 25 established

The verifiable conclusion is that the Solana Foundation released a developer mechanism for packaging signable Solana transactions as portable Actions and link-driven interfaces. The contemporaneous specification, official announcement and independent reporting agree on the date, intended workflow and initial social-web focus.

The broader claim remained prospective. Blinks reduced the navigation between discovery and a wallet prompt, but they did not remove the wallet, signature decision or transaction confirmation. On June 25, 2024, their consequence lay in making onchain interaction distributable through ordinary links—not in proving how widely or safely that model would be adopted.