Infraestructura

Blinks (Blockchain Links)

Client-side renderers and URL wrappers that convert Solana Actions endpoints into interactive, embeddable UI components — such as buttons, input fields, and transaction previews — that can appear inside wallets, browser extensions, and social media platforms without requiring users to navigate to a dApp. A Blink is essentially a URL prefixed with https://dial.to/?action= that signals to compatible clients to fetch and render the corresponding Action metadata, enabling one-click on-chain transactions from any webpage or feed.

IDblinksAliasBlinks

Lectura rápida

Empieza por la explicación más corta y útil antes de profundizar.

Client-side renderers and URL wrappers that convert Solana Actions endpoints into interactive, embeddable UI components — such as buttons, input fields, and transaction previews — that can appear inside wallets, browser extensions, and social media platforms without requiring users to navigate to a dApp. A Blink is essentially a URL prefixed with https://dial.to/?action= that signals to compatible clients to fetch and render the corresponding Action metadata, enabling one-click on-chain transactions from any webpage or feed.

Modelo mental

Usa primero la analogía corta para razonar mejor sobre el término cuando aparezca en código, docs o prompts.

Piensa en esto como un bloque de construcción que conecta una definición aislada con el sistema mayor donde vive.

Contexto técnico

Ubica el término dentro de la capa de Solana en la que vive para razonar mejor sobre él.

RPCs, validators, snapshots, indexación y plumbing de red.

Por qué le importa a un builder

Convierte el término de vocabulario en algo operacional para producto e ingeniería.

Este término desbloquea conceptos adyacentes rápido, así que funciona mejor cuando lo tratas como un punto de conexión y no como una definición aislada.

Handoff para IA

Handoff para IA

Usa este bloque compacto cuando quieras dar contexto sólido a un agente o asistente sin volcar toda la página.

Blinks (Blockchain Links) (blinks)
Categoría: Infraestructura
Definición: Client-side renderers and URL wrappers that convert Solana Actions endpoints into interactive, embeddable UI components — such as buttons, input fields, and transaction previews — that can appear inside wallets, browser extensions, and social media platforms without requiring users to navigate to a dApp. A Blink is essentially a URL prefixed with https://dial.to/?action= that signals to compatible clients to fetch and render the corresponding Action metadata, enabling one-click on-chain transactions from any webpage or feed.
Aliases: Blinks
Relacionados: Solana Actions
Glossary Copilot

Haz preguntas de Solana con contexto aterrizado sin salir del glosario.

Usa contexto del glosario, relaciones entre términos, modelos mentales y builder paths para recibir respuestas estructuradas en vez de output genérico.

Abrir workspace completa del Copilot
Explicar este código

Opcional: pega código Anchor, Solana o Rust para que el Copilot mapee primitivas de vuelta al glosario.

Haz una pregunta aterrizada en el glosario

Haz una pregunta aterrizada en el glosario

El Copilot responderá usando el término actual, conceptos relacionados, modelos mentales y el grafo alrededor del glosario.

Grafo conceptual

Ve el término como parte de una red, no como una definición aislada.

Estas ramas muestran qué conceptos toca este término directamente y qué existe una capa más allá de ellos.

Rama

Solana Actions

A protocol specification that standardizes how web servers expose signable Solana transactions and messages via HTTPS endpoints, enabling any URL to become an interactive blockchain entry point. Actions use a GET/POST handshake similar to Solana Pay Transaction Requests but are generalized beyond payments to support arbitrary on-chain operations (voting, staking, DeFi interactions), and serve as the server-side counterpart to Blinks, which render Actions as embeddable UI components.

Siguientes conceptos para explorar

Mantén la cadena de aprendizaje en movimiento en lugar de parar en una sola definición.

Estos son los siguientes conceptos que vale la pena abrir si quieres que este término tenga más sentido dentro de un workflow real de Solana.

Infraestructura

Solana Actions

A protocol specification that standardizes how web servers expose signable Solana transactions and messages via HTTPS endpoints, enabling any URL to become an interactive blockchain entry point. Actions use a GET/POST handshake similar to Solana Pay Transaction Requests but are generalized beyond payments to support arbitrary on-chain operations (voting, staking, DeFi interactions), and serve as the server-side counterpart to Blinks, which render Actions as embeddable UI components.

Infraestructura

Clockwork

A deprecated Solana on-chain automation protocol (by Clockwork Labs, now sunset) that allowed developers to schedule and trigger smart contract instructions based on time (cron expressions) or on-chain conditions using a network of automation worker threads running alongside validators. Clockwork introduced the concept of Thread accounts that encoded trigger conditions and instruction targets directly on-chain, and while it has been discontinued, it pioneered the automation primitive model later explored by projects like Turbin3 and off-chain keeper bot architectures.

Infraestructura

Arweave

A decentralized permanent storage protocol that uses a blockchain-like structure called the blockweave and a one-time upfront payment model (no recurring fees) to store data indefinitely, backed by an endowment mechanism. In the Solana ecosystem, Arweave is the dominant off-chain storage layer for NFT metadata JSON and media files, and is used by Metaplex's Bundlr/Irys integration to upload assets cheaply in bulk before minting, with URIs of the form ar://<txid> or https://arweave.net/<txid> stored in on-chain metadata accounts.

Infraestructura

RPC (Llamada a Procedimiento Remoto)

The JSON-RPC 2.0 protocol interface through which clients communicate with Solana nodes to query chain state, submit transactions, and subscribe to events. Solana exposes a rich set of HTTP and WebSocket endpoints (e.g., getAccountInfo, sendTransaction) that abstract direct peer-to-peer network participation, making RPC the primary integration point for wallets, dApps, and indexers.

Términos relacionados

Sigue los conceptos que realmente le dan contexto a este término.

Las entradas del glosario se vuelven útiles cuando están conectadas. Estos enlaces son el camino más corto hacia ideas adyacentes.

Infraestructuraactions

Solana Actions

A protocol specification that standardizes how web servers expose signable Solana transactions and messages via HTTPS endpoints, enabling any URL to become an interactive blockchain entry point. Actions use a GET/POST handshake similar to Solana Pay Transaction Requests but are generalized beyond payments to support arbitrary on-chain operations (voting, staking, DeFi interactions), and serve as the server-side counterpart to Blinks, which render Actions as embeddable UI components.

Más en la categoría

Quédate en la misma capa y sigue construyendo contexto.

Estas entradas viven junto al término actual y ayudan a que la página se sienta parte de un grafo de conocimiento más amplio en lugar de un callejón sin salida.

Infraestructura

RPC (Llamada a Procedimiento Remoto)

The JSON-RPC 2.0 protocol interface through which clients communicate with Solana nodes to query chain state, submit transactions, and subscribe to events. Solana exposes a rich set of HTTP and WebSocket endpoints (e.g., getAccountInfo, sendTransaction) that abstract direct peer-to-peer network participation, making RPC the primary integration point for wallets, dApps, and indexers.

Infraestructura

Nodo RPC

A Solana full node that stores ledger state and serves JSON-RPC and WebSocket requests from clients without participating in consensus or voting. RPC nodes must replay every transaction to maintain an accurate account state database, and high-throughput deployments typically run dedicated RPC nodes with large SSDs, high RAM (256 GB+), and high-bandwidth network connections to handle concurrent client load without impacting validator performance.

Infraestructura

RPC Methods

The enumerated JSON-RPC endpoints exposed by Solana nodes, covering account queries (getAccountInfo, getMultipleAccounts, getProgramAccounts), block and transaction retrieval (getBlock, getTransaction), cluster metadata (getEpochInfo, getSlot, getVersion), and transaction submission (sendTransaction, simulateTransaction). Methods accept a Commitment parameter (processed, confirmed, finalized) to control the recency-vs-safety tradeoff of returned data.

Infraestructura

getAccountInfo

An RPC method that returns the complete on-chain state of a single account identified by its base-58 public key, including its lamport balance, owner program, executable flag, rent epoch, and raw data payload encoded as base64 or base58. It is the most fundamental read primitive in Solana development and is called at the specified commitment level, with the data field being null if the account does not exist.