An Ethereum transaction type introduced in the Dencun upgrade (March 2024) that carries binary large objects (blobs) of temporary off-chain data. Each blob is 128 KB, committed via KZG polynomial commitments, and stored for ~18 days before pruning. Blob transactions created a separate fee market and reduced Layer 2 rollup fees by 10-100x by providing cheap, temporary data availability.
Start with the shortest useful explanation before going deeper.
An Ethereum transaction type introduced in the Dencun upgrade (March 2024) that carries binary large objects (blobs) of temporary off-chain data. Each blob is 128 KB, committed via KZG polynomial commitments, and stored for ~18 days before pruning. Blob transactions created a separate fee market and reduced Layer 2 rollup fees by 10-100x by providing cheap, temporary data availability.
Use the quick analogy first so the term is easier to reason about when you meet it in code, docs, or prompts.
Think of it as a building block that connects one definition to the larger Solana system around it.
Place the term inside its Solana layer so the definition is easier to reason about.
Shared crypto concepts that frame the broader ecosystem.
Turn the term from vocabulary into something operational for product and engineering work.
This term unlocks adjacent concepts quickly, so it works best when you treat it as a junction instead of an isolated definition.
Use this compact block when you want to give an agent or assistant grounded context without dumping the entire page.
Blob Transaction (EIP-4844) (blob-transaction) Category: Blockchain General Definition: An Ethereum transaction type introduced in the Dencun upgrade (March 2024) that carries binary large objects (blobs) of temporary off-chain data. Each blob is 128 KB, committed via KZG polynomial commitments, and stored for ~18 days before pruning. Blob transactions created a separate fee market and reduced Layer 2 rollup fees by 10-100x by providing cheap, temporary data availability. Aliases: Blob, EIP-4844 Related: Proto-Danksharding, Rollup, Data Availability (DA)
Use glossary context, relationships, mental models, and builder paths to get structured answers instead of generic chat output.
Optional: paste Anchor, Solana, or Rust code so the Copilot can map primitives back to glossary terms.
The Copilot will answer using the current term, related concepts, mental models, and the surrounding glossary graph.
These branches show which concepts this term touches directly and what sits one layer beyond them.
An intermediate Ethereum scaling upgrade (EIP-4844) that introduces blob-carrying transactions as a stepping stone toward full danksharding. Proto-danksharding implements the transaction format and KZG commitment scheme planned for full sharding but without actual data sharding—blobs are fully downloaded by all consensus nodes. It targets ~0.375 MB of blob data per block.
A Layer 2 scaling technique that executes transactions off-chain, bundles them, and posts compressed data back to L1. Optimistic rollups assume transactions are valid and use fraud proofs for disputes (7-day challenge period). ZK rollups generate cryptographic validity proofs for every batch. Rollups inherit L1 security while providing 10-100x throughput improvement.
The guarantee that a block's transaction data has been published and can be downloaded by any network participant. In modular blockchains and rollups, DA layers ensure off-chain execution data remains visible, complete, and verifiable. Data availability sampling (DAS) allows light nodes to probabilistically verify availability by checking random chunks without downloading entire blocks.
These are the next concepts worth opening if you want this term to make more sense inside a real Solana workflow.
These entries are easy to mix up when you are reading quickly, prompting an LLM, or onboarding into a new layer of Solana.
A Zcash transaction where sender address, receiver address, and amount are encrypted using zk-SNARKs, providing cryptographic privacy while allowing network nodes to verify validity without learning private details. Shielded transactions operate within dedicated value pools (Sapling or Orchard), each with independent circuit designs. Users can selectively disclose transaction details to third parties using viewing keys without compromising spending authority.
The cost paid by the sender to have a transaction processed and included in a block. Fees compensate validators/miners for computation and prevent spam. Fee models vary: Ethereum uses dynamic gas pricing (EIP-1559 base fee + tip), Solana uses base fee (5,000 lamports) + optional priority fee, Bitcoin uses fee-per-byte.
Glossary entries become useful when they are connected. These links are the shortest path to adjacent ideas.
An intermediate Ethereum scaling upgrade (EIP-4844) that introduces blob-carrying transactions as a stepping stone toward full danksharding. Proto-danksharding implements the transaction format and KZG commitment scheme planned for full sharding but without actual data sharding—blobs are fully downloaded by all consensus nodes. It targets ~0.375 MB of blob data per block.
A Layer 2 scaling technique that executes transactions off-chain, bundles them, and posts compressed data back to L1. Optimistic rollups assume transactions are valid and use fraud proofs for disputes (7-day challenge period). ZK rollups generate cryptographic validity proofs for every batch. Rollups inherit L1 security while providing 10-100x throughput improvement.
The guarantee that a block's transaction data has been published and can be downloaded by any network participant. In modular blockchains and rollups, DA layers ensure off-chain execution data remains visible, complete, and verifiable. Data availability sampling (DAS) allows light nodes to probabilistically verify availability by checking random chunks without downloading entire blocks.
These entries live beside the current term and help the page feel like part of a larger knowledge graph instead of a dead end.
A distributed, append-only ledger that records transactions in cryptographically linked blocks. Each block contains a hash of the previous block, forming an immutable chain. Nodes in the network maintain copies of the ledger and reach agreement through consensus mechanisms. Blockchains enable trustless, decentralized record-keeping without a central authority.
The protocol by which nodes in a distributed network agree on the current state of the ledger. Common mechanisms include Proof of Work (Bitcoin), Proof of Stake (Ethereum, Solana), and BFT variants. Consensus ensures all honest nodes converge on the same transaction history despite potential network delays or malicious actors.
A consensus mechanism where validators are selected to produce blocks based on the amount of cryptocurrency they have staked (locked) as collateral. PoS is energy-efficient compared to Proof of Work. Misbehaving validators risk losing their stake (slashing). Solana, Ethereum (post-Merge), Cosmos, and Cardano use PoS variants.
A consensus mechanism where miners compete to solve computationally expensive puzzles to produce blocks and earn rewards. PoW provides strong security (51% attack resistance) but is energy-intensive. Bitcoin and pre-Merge Ethereum use PoW. The difficulty adjusts to maintain target block times regardless of total network hash power.