Infraestrutura

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.

IDactionsAliasActions

Leitura rápida

Comece pela explicação mais curta e útil antes de aprofundar.

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.

Modelo mental

Use primeiro a analogia curta para raciocinar melhor sobre o termo quando ele aparecer em código, docs ou prompts.

Pense nisso como um bloco de construção que ajuda a ligar uma definição isolada ao sistema maior onde ela vive.

Contexto técnico

Coloque o termo dentro da camada de Solana em que ele vive para raciocinar melhor sobre ele.

RPCs, validators, snapshots, indexação e plumbing da rede.

Por que builders ligam para isso

Transforme o termo de vocabulário em algo operacional para produto e engenharia.

Este termo destrava conceitos adjacentes rapidamente, então funciona melhor quando você o trata como um ponto de conexão, não como definição isolada.

Handoff para IA

Handoff para IA

Use este bloco compacto quando quiser dar contexto aterrado para um agente ou assistente sem despejar a página inteira.

Solana Actions (actions)
Categoria: Infraestrutura
Definição: 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.
Aliases: Actions
Relacionados: Blinks (Blockchain Links), Transaction Request (Solana Pay)
Glossary Copilot

Faça perguntas de Solana com contexto aterrado sem sair do glossário.

Use contexto do glossário, relações entre termos, modelos mentais e builder paths para receber respostas estruturadas em vez de output genérico.

Explicar este código

Opcional: cole código Anchor, Solana ou Rust para o Copilot mapear primitivas de volta para termos do glossário.

Faça uma pergunta aterrada no glossário

Faça uma pergunta aterrada no glossário

O Copilot vai responder usando o termo atual, conceitos relacionados, modelos mentais e o grafo ao redor do glossário.

Grafo conceitual

Veja o termo como parte de uma rede, não como uma definição sem saída.

Esses ramos mostram quais conceitos esse termo toca diretamente e o que existe uma camada além deles.

Ramo

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.

Ramo

Transaction Request (Solana Pay)

A Solana Pay protocol flow in which a QR code or link encodes an HTTPS URL; when scanned, the wallet performs a GET request to discover metadata (label, icon) and then a POST request with the user's public key, receiving a base64-encoded partially-signed transaction that the wallet can inspect, sign, and submit. This dynamic model enables programmable commerce flows such as NFT minting, coupon redemption, and multi-step checkout because the merchant server constructs the transaction at request time rather than encoding it statically.

Próximos conceitos para explorar

Continue a cadeia de aprendizado em vez de parar em uma única definição.

Estes são os próximos conceitos que valem abrir se você quiser que este termo faça mais sentido dentro de um workflow real de Solana.

Infraestrutura

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.

Infraestrutura

Transaction Request (Solana Pay)

A Solana Pay protocol flow in which a QR code or link encodes an HTTPS URL; when scanned, the wallet performs a GET request to discover metadata (label, icon) and then a POST request with the user's public key, receiving a base64-encoded partially-signed transaction that the wallet can inspect, sign, and submit. This dynamic model enables programmable commerce flows such as NFT minting, coupon redemption, and multi-step checkout because the merchant server constructs the transaction at request time rather than encoding it statically.

Infraestrutura

Solana Mobile

A hardware and software initiative by Solana Labs producing Android smartphones (Saga, Chapter 2) with a secure element-backed seed vault for private key storage, a curated dApp store for Solana applications, and the Mobile Wallet Adapter protocol for standardized wallet-dApp communication on mobile. The Solana Mobile Stack (SMS) enables native mobile dApps to interact with on-device wallets without browser extensions or QR code scanning, targeting the mobile-first crypto user base.

Infraestrutura

signatureSubscribe

A Solana WebSocket subscription method that pushes a notification when a specific transaction signature reaches the requested commitment level (processed, confirmed, or finalized). It is the standard way to wait for transaction confirmation without polling, returning the signature status including any error information. The subscription automatically unsubscribes after delivering one notification. Commonly used in dApp frontends to show real-time transaction status updates to users.

Comumente confundido com

Termos próximos em vocabulário, sigla ou vizinhança conceitual.

Essas entradas são fáceis de misturar quando você lê rápido, faz prompting em um LLM ou está entrando em uma nova camada de Solana.

Infraestruturasolana-mobile

Solana Mobile

A hardware and software initiative by Solana Labs producing Android smartphones (Saga, Chapter 2) with a secure element-backed seed vault for private key storage, a curated dApp store for Solana applications, and the Mobile Wallet Adapter protocol for standardized wallet-dApp communication on mobile. The Solana Mobile Stack (SMS) enables native mobile dApps to interact with on-device wallets without browser extensions or QR code scanning, targeting the mobile-first crypto user base.

AliasSMSAliasSaga
Infraestruturasolana-pay

Solana Pay

An open payment standard and SDK that defines URI schemes and protocol flows for requesting SOL or SPL token transfers and for constructing and returning partially-built transactions from merchant backends to user wallets. It comprises two sub-protocols — Transfer Requests (simple static payment URIs) and Transaction Requests (dynamic server-signed transaction fetching) — and enables point-of-sale payments, loyalty programs, and interactive commerce experiences using QR codes or deeplinks.

Termos relacionados

Siga os conceitos que realmente dão contexto a este termo.

Entradas de glossário só ficam úteis quando estão conectadas. Esses links são o caminho mais curto para ideias adjacentes.

Infraestruturablinks

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.

Infraestruturatransaction-request

Transaction Request (Solana Pay)

A Solana Pay protocol flow in which a QR code or link encodes an HTTPS URL; when scanned, the wallet performs a GET request to discover metadata (label, icon) and then a POST request with the user's public key, receiving a base64-encoded partially-signed transaction that the wallet can inspect, sign, and submit. This dynamic model enables programmable commerce flows such as NFT minting, coupon redemption, and multi-step checkout because the merchant server constructs the transaction at request time rather than encoding it statically.

Mais na categoria

Permaneça na mesma camada e continue construindo contexto.

Essas entradas vivem ao lado do termo atual e ajudam a página a parecer parte de um grafo maior, não um beco sem saída.

Infraestrutura

RPC (Chamada de Procedimento 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.

Infraestrutura

Nó 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.

Infraestrutura

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.

Infraestrutura

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.