Solizone

Solizone EVMChapter 08 / 17

Publishing to Logos

How canonical blocks reach the Logos blockchain, and why publication is not storage.

Publication to Logos

Solizone EVM also has a publication boundary.

Canonical Solizone block bytes can be passed through:

Diagram
Solizone block
      ↓
BlockPublisher
      ↓
LogosPublisher
      ↓
ZoneSequencer
      ↓
Logos

This lets Solizone EVM keep block production independent from the underlying publication implementation.

The block producer does not need to understand Logos internals.

It simply produces canonical blocks.

The publisher handles the next boundary.

Publication and storage are different

A Solizone block can interact with Logos in two fundamentally different ways.

Logos Storage

Diagram
block bytes
→ stored
→ retrieved by CID

Purpose:

Diagram
persistence
history
recovery

Logos blockchain

Diagram
canonical block data
→ published
→ ordered
→ finalized

Purpose:

Diagram
shared ordering
consensus
finality

These responsibilities should not be mixed.