Protocolo Base

Ed25519 Precompile

A native Solana program (address: Ed25519SigVerify111111111111111111111111111) that enables batch verification of Ed25519 signatures within on-chain program logic. Unlike the runtime's built-in transaction signature verification, this precompile allows programs to verify arbitrary Ed25519 signatures over arbitrary data, useful for off-chain message verification, oracle attestations, and multi-party protocols. Multiple signatures can be verified in a single instruction.

IDed25519-precompile

Leitura rápida

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

A native Solana program (address: Ed25519SigVerify111111111111111111111111111) that enables batch verification of Ed25519 signatures within on-chain program logic. Unlike the runtime's built-in transaction signature verification, this precompile allows programs to verify arbitrary Ed25519 signatures over arbitrary data, useful for off-chain message verification, oracle attestations, and multi-party protocols. Multiple signatures can be verified in a single instruction.

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 parte da engrenagem que mantém a ordenação, execução ou consenso da rede funcionando.

Contexto técnico

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

Consenso, rotação de líderes, slots, epochs e o runtime.

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.

Ed25519 Precompile (ed25519-precompile)
Categoria: Protocolo Base
Definição: A native Solana program (address: Ed25519SigVerify111111111111111111111111111) that enables batch verification of Ed25519 signatures within on-chain program logic. Unlike the runtime's built-in transaction signature verification, this precompile allows programs to verify arbitrary Ed25519 signatures over arbitrary data, useful for off-chain message verification, oracle attestations, and multi-party protocols. Multiple signatures can be verified in a single instruction.
Relacionados: Ed25519, Secp256k1 Precompile, Assinatura
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

Ed25519

The elliptic curve digital signature algorithm used by Solana for all transaction signing. Ed25519 uses Curve25519 and produces 64-byte signatures with 32-byte public keys. Solana also provides an Ed25519 precompile program for on-chain signature verification within program logic.

Ramo

Secp256k1 Precompile

A native Solana program (address: KeccakSecp256k11111111111111111111111111111) that verifies secp256k1 ECDSA signatures on-chain, enabling Ethereum-compatible signature verification within Solana programs. This precompile allows Solana dApps to verify signatures produced by Ethereum wallets (MetaMask, etc.), facilitating cross-chain identity verification, bridging, and interoperability without requiring users to create Solana-native keypairs.

Ramo

Assinatura

A 64-byte Ed25519 digital signature over a transaction's message. Each signer in a transaction produces one signature. The first signature (from the fee payer) also serves as the unique transaction ID. Signature verification is parallelized in the TPU's sigverify stage using GPU acceleration.

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.

Modelo de Programação

Ed25519

The elliptic curve digital signature algorithm used by Solana for all transaction signing. Ed25519 uses Curve25519 and produces 64-byte signatures with 32-byte public keys. Solana also provides an Ed25519 precompile program for on-chain signature verification within program logic.

Protocolo Base

Secp256k1 Precompile

A native Solana program (address: KeccakSecp256k11111111111111111111111111111) that verifies secp256k1 ECDSA signatures on-chain, enabling Ethereum-compatible signature verification within Solana programs. This precompile allows Solana dApps to verify signatures produced by Ethereum wallets (MetaMask, etc.), facilitating cross-chain identity verification, bridging, and interoperability without requiring users to create Solana-native keypairs.

Modelo de Programação

Assinatura

A 64-byte Ed25519 digital signature over a transaction's message. Each signer in a transaction produces one signature. The first signature (from the fee payer) also serves as the unique transaction ID. Signature verification is parallelized in the TPU's sigverify stage using GPU acceleration.

Protocolo Base

Entrada

An ordered unit within a block containing a mix of PoH ticks and transaction batches. Each entry includes a PoH hash, a count of hashes since the previous entry, and zero or more transactions. Entries without transactions are tick entries that advance the PoH clock; entries with transactions prove those transactions occurred between two points in time.

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.

Protocolo Basesecp256k1-precompile

Secp256k1 Precompile

A native Solana program (address: KeccakSecp256k11111111111111111111111111111) that verifies secp256k1 ECDSA signatures on-chain, enabling Ethereum-compatible signature verification within Solana programs. This precompile allows Solana dApps to verify signatures produced by Ethereum wallets (MetaMask, etc.), facilitating cross-chain identity verification, bridging, and interoperability without requiring users to create Solana-native keypairs.

Protocolo Basesecp256r1-precompile

Secp256r1 Precompile (P256)

A native Solana program for verifying ECDSA signatures on the secp256r1 (P-256/prime256v1) elliptic curve, enabling WebAuthn and passkey-based authentication directly on-chain. P-256 is the curve used by Apple Face ID/Touch ID, Android biometrics, and FIDO2 security keys. This precompile allows Solana dApps to authenticate users via device biometrics without managing traditional private keys, significantly improving wallet UX.

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.

Modelo de Programaçãoed25519

Ed25519

The elliptic curve digital signature algorithm used by Solana for all transaction signing. Ed25519 uses Curve25519 and produces 64-byte signatures with 32-byte public keys. Solana also provides an Ed25519 precompile program for on-chain signature verification within program logic.

Protocolo Basesecp256k1-precompile

Secp256k1 Precompile

A native Solana program (address: KeccakSecp256k11111111111111111111111111111) that verifies secp256k1 ECDSA signatures on-chain, enabling Ethereum-compatible signature verification within Solana programs. This precompile allows Solana dApps to verify signatures produced by Ethereum wallets (MetaMask, etc.), facilitating cross-chain identity verification, bridging, and interoperability without requiring users to create Solana-native keypairs.

Modelo de Programaçãosignature

Assinatura

A 64-byte Ed25519 digital signature over a transaction's message. Each signer in a transaction produces one signature. The first signature (from the fee payer) also serves as the unique transaction ID. Signature verification is parallelized in the TPU's sigverify stage using GPU acceleration.

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.

Protocolo Base

Prova de História (PoH)

A clock mechanism that cryptographically proves the passage of time between events. PoH uses a sequential SHA-256 hash chain where each output becomes the next input, creating a verifiable ordering of events without requiring consensus. The leader produces ~400,000 hashes per slot (~400ms), and any validator can verify the sequence in parallel, enabling Solana's high throughput by removing the need for validators to agree on time.

Protocolo Base

Tower BFT

Solana's custom BFT consensus algorithm built on top of Proof of History. Tower BFT uses PoH as a clock to reduce communication overhead in traditional PBFT from O(n²) to O(n). Validators vote on forks with exponentially increasing lockout periods—each consecutive vote doubles the lockout, making rollbacks progressively more expensive. A fork is finalized when it reaches supermajority (66.7%+ of stake).

Protocolo Base

Slot

A time window during which a designated leader validator can produce a block. Each slot lasts approximately 400 milliseconds. Slots are numbered sequentially from genesis and grouped into epochs of 432,000 slots (~2-3 days). Not every slot produces a block—a skipped slot means the leader was offline or too slow.

Protocolo Base

Bloco

A set of entries produced by a leader during a single slot. A block contains transactions bundled into entries, each with a PoH hash proving ordering. Blocks are broken into shreds for network propagation via Turbine. Maximum block size is limited by compute units (48M CU cap per block) rather than byte size.