⛏️Blockchain Structure
Last updated
Last updated
User directly and indirectly initiates transaction through SDK, transaction can be either executed in parallel or not;
Transaction enters txPool and waits to be sealed;
Transaction gets sealed to block by Sealer and sent to BlockVerifier for verification after consensus;
BlockVerifier generates transaction DAG according to the transaction list in block;
BlockVerifier builds the execution context and executes transaction DAG;
Block is on chain after verified.
Files are mapped into into a set of extents:
Extents are block-aligned, continuous regions on the block device
Extents do not span across zones
A zone may contain more than one extent
Extents from different files may share zones
Metadata is stored in storage of the block device.
Each valid meta data zone contains:
A superblock with the current sequence number and global file system metadata
At least one snapshot of all files in the file system
Incremental file system updates (new files, new extents, deletes, renames etc)
