Artwork

Content provided by Gautam Dhameja. All podcast content including episodes, graphics, and podcast descriptions are uploaded and provided directly by Gautam Dhameja or their podcast platform partner. If you believe someone is using your copyrighted work without your permission, you can follow the process outlined here https://player.fm/legal.
Player FM - Podcast App
Go offline with the Player FM app!

Episode 102 - What is Blobspace?

4:20
 
Share
 

Fetch error

Hmmm there seems to be a problem fetching this series right now. Last successful fetch was on April 26, 2024 15:47 (4M ago)

What now? This series will be checked again in the next day. If you believe it should be working, please verify the publisher's feed link below is valid and includes actual episode links. You can contact support to request the feed be immediately fetched.

Manage episode 383586211 series 2823149
Content provided by Gautam Dhameja. All podcast content including episodes, graphics, and podcast descriptions are uploaded and provided directly by Gautam Dhameja or their podcast platform partner. If you believe someone is using your copyrighted work without your permission, you can follow the process outlined here https://player.fm/legal.

There is a new term in the crypto land — blobspace.

Before understanding blobspace, let’s first do a quick refresher on data availability. Check out Episode 88 of the podcast.

https://episodes.blockshots.fm/p/episode-88-what-is-data-availability#details

Data availability is about making the L2 block data available on the L1s. For Optimistic rollups — to build fraud proofs. For ZK Rollups — to know the state transitions.

How do we make data available? By posting it on the L1 chain. Currently it is being posted as a hack — utilising the CALLDATA field in Ethereum transaction format. But that is inefficient and expensive.

To improve data availability on Ethereum, an update is planned to introduce posting of data blobs on the L1. This would make data availability cheaper and more efficient for rollups.

The data blobs posted by L2s with their transaction data have their own dedicated space inside the blocks. This space is logically separate from the L1 transaction data and is informally called as blobspace.


This is a public episode. If you would like to discuss this with other subscribers or get access to bonus episodes, visit podcast.blockshots.net
  continue reading

116 episodes

Artwork
iconShare
 

Fetch error

Hmmm there seems to be a problem fetching this series right now. Last successful fetch was on April 26, 2024 15:47 (4M ago)

What now? This series will be checked again in the next day. If you believe it should be working, please verify the publisher's feed link below is valid and includes actual episode links. You can contact support to request the feed be immediately fetched.

Manage episode 383586211 series 2823149
Content provided by Gautam Dhameja. All podcast content including episodes, graphics, and podcast descriptions are uploaded and provided directly by Gautam Dhameja or their podcast platform partner. If you believe someone is using your copyrighted work without your permission, you can follow the process outlined here https://player.fm/legal.

There is a new term in the crypto land — blobspace.

Before understanding blobspace, let’s first do a quick refresher on data availability. Check out Episode 88 of the podcast.

https://episodes.blockshots.fm/p/episode-88-what-is-data-availability#details

Data availability is about making the L2 block data available on the L1s. For Optimistic rollups — to build fraud proofs. For ZK Rollups — to know the state transitions.

How do we make data available? By posting it on the L1 chain. Currently it is being posted as a hack — utilising the CALLDATA field in Ethereum transaction format. But that is inefficient and expensive.

To improve data availability on Ethereum, an update is planned to introduce posting of data blobs on the L1. This would make data availability cheaper and more efficient for rollups.

The data blobs posted by L2s with their transaction data have their own dedicated space inside the blocks. This space is logically separate from the L1 transaction data and is informally called as blobspace.


This is a public episode. If you would like to discuss this with other subscribers or get access to bonus episodes, visit podcast.blockshots.net
  continue reading

116 episodes

All episodes

×
 
Loading …

Welcome to Player FM!

Player FM is scanning the web for high-quality podcasts for you to enjoy right now. It's the best podcast app and works on Android, iPhone, and the web. Signup to sync subscriptions across devices.

 

Quick Reference Guide