Dialect: Blinks, Alerts, and the Solana UX stack
Dialect is Solana’s UX stack for in-context actions and notifications. Blinks (blockchain links), multi-channel Alerts, Markets data, SDKs, and how builders integrate without redirects.
devrels.xyz/a/258short linkDialect: Blinks, Alerts, and the Solana UX stack. Product home dialect.to; developer docs docs.dialect.to; org github.com/dialectlabs; X @saydialect.
The problem Dialect owns
Onchain product loops die on redirects and slow integrations. Users already live in feeds, chats, and wallets; every hop to a dapp tab is drop-off. Dialect’s pitch is the UX layer that keeps the action in context: one-click transactions where the user already is, plus notifications that reach them when the chain moves.
Two complementary products show up on the homepage and in docs:
- Blinks — blockchain links / Solana Actions unfurls
- Alerts — actionable onchain notifications across channels
Markets/positions APIs sit alongside for lending rates and position-aware Blinks. This piece maps the builder surface; the protocol-level Actions walkthrough is in Solana Actions and Blinks.
Product map
| Product | What builders ship | Where to start |
|---|---|---|
| Blinks | Action URLs that clients unfurl into ready-to-sign UX (swap, stake, mint, governance) | Blinks docs / quickstart |
| Alerts | Multi-channel notifications: in-app, email, Telegram, push; wallet auth | Alerts docs · dashboard |
| Markets / positions | Lending rates, market data, position tracking with ready Blinks | Markets section in docs.dialect.to |
| API keys | Keys for Alerts, Blinks, Markets | Request keys flow in developer docs |
Blinks (blockchain links)
A Blink is a URL that speaks the Solana Actions protocol so supporting clients (wallets, X unfurl via registered providers, in-app WebViews) can render actions without a full dapp session. Dialect’s role: SDKs, React components, headless integration, standard Blink library from ecosystem projects, and provider tooling so you are not hand-rolling unfurl + transaction build every time.
Homepage claims matter for product marketing (600+ Blinks powered); for shipping, treat registry / unfurl eligibility as a hard constraint — clients only surface actions they trust. Co-stewardship of Actions with the Foundation is covered in the Actions article; here the job is “integrate Dialect’s Blink stack into my app or feed.”
| Mode | When |
|---|---|
| Build a Blink provider | You expose GET/POST Action endpoints that return metadata + transactions |
| Integrate Blinks UI | Embed Dialect React components or headless client to render third-party Blinks inside your app |
| Standard library | Copy ready Blinks from ecosystem catalogs instead of rebuilding swap/stake flows |
npm entry points commonly used in docs and GitHub: @dialectlabs/blinks (latest on npm at time of writing in the 0.22.x line) plus React packages under the dialectlabs org. Scaffold repos include blink-starter-solana (and EVM variants for multi-chain Blink work).
# typical installs — pin versions from docs.dialect.to
npm i @dialectlabs/blinks
# React UI packages as documented for your app shellAlerts
Dialect Alerts is notification infrastructure for Solana apps and wallets — documented as powering messaging for 30+ apps with wallet-based auth, multi-channel delivery, and a Universal Inbox so users can see cross-app alerts in one place.
| Piece | Detail |
|---|---|
| Channels | In-app, email, Telegram, mobile push |
| Send paths | No-code dashboard, REST API, TypeScript SDK, React components |
| Priority | High-priority pipeline for liquidations / limit fills; lower priority for broadcasts |
| Burst mode | Temporary scale-up for time-sensitive fanout (docs: orders of magnitude for minutes) |
| Monitoring | Event detection SDK / custom triggers for onchain conditions |
| Time-to-first-send | Docs target under ~15 minutes via Quick Start + dashboard |
Practical split: use Alerts when the user is not staring at your UI (liquidation risk, fill, governance). Use Blinks when they are already in a client and should act without leaving. Many products ship both — alert fires, Blink is the deep link to act.
Builder checklist
| Step | Action |
|---|---|
| 1 | Open docs.dialect.to — pick Blinks vs Alerts vs both |
| 2 | Request API keys for the products you will call |
| 3 | Blinks: implement or embed Actions; verify unfurl in target clients (wallet / feed) |
| 4 | Alerts: register app in dashboard; send test via REST or SDK; wire subscribe UX (wallet) |
| 5 | Production: topics, channel preferences, priority class for critical vs marketing |
People and links
| Surface | URL |
|---|---|
| Product | dialect.to |
| Docs | docs.dialect.to |
| Blinks product page | dialect.to/blinks |
| Alerts product page | dialect.to/alerts |
| Alerts dashboard | dashboard.dialect.to |
| GitHub | dialectlabs |
| X | @saydialect |
Resources
Keep reading
A Blink is a URL that unfurls into a signable transaction; an Action is the HTTP API behind it. Two endpoints — GET for metadata, POST for a serialized tx — turn any link into a one-tap payment or mint. Clean spec, real security questions. The wire-level view.
Email/social/passkey login → portable MPC wallets; sign via SDK or REST without exposing full keys.
One SDK surface for quoting and executing value across Solana and 20+ other chains — intent solver, money market, bridge — plus agent skills.
Get new articles in your inbox
Technical deep-dives on Solana tooling, infrastructure, and ecosystem. No noise.
