1. Execution Layer A. Transaction Type We created a new transaction type BLOB_TX-TYPE via EIP-2718 A1. Message & Signature class SignedBlobTransaction(Container): message: BlobTransaction signature: ECDSASignature class BlobTransaction(Container):

Preface I was drawn to the concept of Celestia when I first saw it. I thought it would bring about a massive paradigm shift. The multi-chain ecosystem became incredibly clear... What appeals to me most is that Celestia will bring permissionless innovation, which is a very open component. From the evolution of biology to the development of science and technology, there will always be some open components and some building blocks in a system, which increase the network's connection and support the network to burst out more complex innovations. Celestia is such a component that it will promote the further explosion of innovations and components, like a positive feedback loop, to promote the more prosperous and more complex evolution of the entire blockchain system. 2. Consensus and Execution Blockchain is essentially a distributed network that runs State Machine Replication (SMR). SMR has three primary stages: data, consensus, and execution; the blockchain is also divided into these three layers. The key to creating currency on the Internet is to introduce a consensus system that cannot be interfered with by outsiders. The solution proposed by Satoshi is to introduce the "Nakamoto Consensus" so that people worldwide can maintain and operate Bitcoin. Here's how Bitcoin's consensus protocol works: Bitcoin nodes receive transactions from peers.

Danksharding is the future of Ethereum scalability; this article will discuss the future of Danksharding and modular blockchain. Have to say, the name Dankshard is cool. In the process of scaling, there are two problems: Scalable verification of computation:Efficiently verify the results of computations instead of re-executing them by full nodes.In the Rollup-centric Roadmap of Ethereum, roll up is responsible for using fraud proofs or ZK proofs to implement high-throughput secure transaction processing capabilities. Of course, there is no denying that such a system will be used in the L1 system to add "native" high-throughput execution in the future, just like what PSE and Scroll are doing now. Scalable verification of data Availability:Efficiently verify data availability instead of downloading all data by full nodes.While ensuring consensus, L1 also needs to provide a "data availability engine" to ensure that rollup data is available, usually to ensure that Batch + State is available. If L1 DA cannot guarantee, it will result in:1. OPR: Challenge cannot be submitted (State + Batch data is invalid)2. ZKR: Unable to get current state (State) https://cdn.nlark.com/yuque/0/2022/png/25416421/1653486449420-a175b123-3798-4742-a1a5-0a6f5a9bacf9.png

Refer to 0xPARC and PSE General Online identity systems enable complex online interactions and communities. However, the system still suffers from many weaknesses, most of which can be attributed to inherent limitations in the design of centralized identity systems. E.g: pressure or interference technical attacks Operators and users have unequal rights

Status Check List EIP-4844 Implementers' Call (weekly) KZG ceremony call Origin ProtoEIP-4844: Shard Blob Transactions - Cancun upgrade Twitter thread ETHDenver Shard Blob transactions Research form