Last week at the AIS Summit in Hamburg, Valera Vlasyuk, Cedra’s core initiator, unveiled how to use blockchain as an AIS data marketplace.

It’s a decentralized layer connecting ships, ports and satellites through verified, encrypted AIS feeds.

With on-chain validation, automated rewards, and token-based access, Cedra introduces transparent incentives for high-quality maritime data sharing.

A new chapter for Maritime AI and Web3 infrastructure begins.

Here are the highlights from his presentation ⬇️

Cedra’s Blockchain-as-AIS Data Marketplace brings together key data providers:

- AIS data feed providers: rewarded based on data quality
- AIS data processors: the marketplace engine
- Historical data providers: rewarded based on data volum

Cedra’s roadmap outlines the evolution of decentralized maritime intelligence:

- AIS Live Data Streaming
- AIS Historical Data Marketplace
- Processed Data Marketplace

Each step adds transparency, automation, and value to global maritime data.

🔗 Website | X | Discord | Telegram Chat

Cedra is designed for parallel transaction execution and instant finality.

Let’s have a look at what this acutally means and the concepts around it as we deep dive into the Cedra Blockchain

Cedra Fundamentals

- Transactions: Atomic operations that change the blockchain state
- Blocks: Containers that group multiple transactions for processing
- Validators: Network participants that execute transactions and reach consensus
- State: The current snapshot of all accounts and resources on the blockchain
- Finality: The point at which a transaction becomes irreversible

These are the sum of its parts in what makes up Cedra, the essentials, the basics, the must haves for things to work as intended.
More on transactions: https://docs.cedra.network/concepts/transactions/understanding-transactions

Every transaction on Cedra follows a predictable path

Client Submissions —> Initial Validation —> Network Propagation —> Block Inclusion —> Parallel Ixecution —> Consensus Agreement —> State Commitment —> Permanent Storage

These are several stages of validation and processing before a transaction becomes permanent.

Processing Stages

Cedra transactions pass through multiple processing stages on their way to being permanent

Including:

- Submission Stage
- Validation Stage
- Inclusion Stage
- Execution Stage
- Commitment Stage

You can read more about each stage here: https://docs.cedra.network/concepts/blockchain

Not only do Cedra transaction go through stages, they also go through the following states:

- Pending: Submitted and awaiting processing
- Validated: Passed initial checks
- Included: Selected for a block
- Executed: Processed by the execution engine
- Committed: Permanently recorded on-chain
- Rejected: Failed validation or execution

The example provided above

Architecutre

Cedra is only as strong as the architecture it’s built on

The photo shows the complete step-by-step structure of Cedra, layer by layer

Operating through a hierarchy of specialized nodes, each serving specific functions in transaction processing on Cedra

This includes:

- Client Applications
- Fullnodes
- Validator Fullnodes
- Validator Nodes

From Cedra’s perspective, the network forms concentric layers of trust and responsibility:

Public Layer: This layer handles user interaction and provides network entry points.

Propagation Layer: Validators share pending transactions, ensuring all participants have access to the same transaction pool.

Consensus Layer: Blocks are proposed, executed, and finalized through Byzantine Fault Tolerant consensus.

Different layers use appropriate communication methods:

- Client-to-Fullnode: REST/JSON APIs for simplicity and compatibility
- Node-to-Node: Binary protocols for efficiency
- Validator-to-Validator: Authenticated, encrypted channels for security

Cedra sees each transaction flow through increasingly restrictive validation layers, ensuring only valid, agreed-upon transactions become permanent.

Blocks serve as the fundamental organizing unit for transactions on the Cedra blockchain. Each block contains:

The block header provides metadata linking this block to the chain history and proving its validity.

The transaction list contains the ordered set of operations to perform.

Execution results capture the effects of processing these transactions.

There is much more information regarding Cedra’s

- Transaction Selection
- Block Proposal Process
- Block Validation

You can find all this information with flowcharts and diagrams at the link below ⬇️

https://docs.cedra.network/concepts/blockchain

In summary

Key architectural decisions enable Cedra's performance:

- Layered network architecture separates concerns and protects validators
- Parallel execution through Block-STM maximizes throughput
- BFT consensus ensures agreement without lengthy confirmation periods
- Sophisticated state management enables efficient verification

This design allows Cedra to process thousands of transactions per second while maintaining the security and decentralization essential to blockchain technology.