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

Lectura rápida

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

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

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 parte del engranaje que mantiene funcionando el orden, la ejecución o el consenso de la red.

Contexto técnico

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

Consenso, rotación de líderes, slots, epochs y el runtime.

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.

Ed25519 Precompile (ed25519-precompile)
Categoría: Protocolo Base
Definición: 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, Firma
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

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.

Rama

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.

Rama

Firma

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.

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.

Modelo de Programación

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 Programación

Firma

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.

Comúnmente confundido con

Términos cercanos en vocabulario, acrónimo o vecindad conceptual.

Estas entradas son fáciles de mezclar cuando lees rápido, haces prompting a un LLM o estás entrando en una nueva capa 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.

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.

Modelo de Programacióned25519

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 Programaciónsignature

Firma

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.

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.

Protocolo Base

Prueba de Historia (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

Bloque

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.