These are the functional and non-functional requirements for roadmapped efforts, according to the FURPS model.

FURPS are elsewhere divided into Milestones and Deliverables, to form a roadmap.

Functionality

blockchain

blockchain:ppos (Private Proof of Stake)

  1. Nodes can permissionlessly participate in consensus
  2. Leaders can propose blocks privately
  3. Leaders can claim block rewards without revealing their block proposal
  4. Blend spam protection
  5. Block proposal redundancy
  6. Censorship resistance against malicious broadcasters
  7. Blend edge node privacy

blockchain:sdp (Service Declaration Protocol)

  1. Nodes can join blockchain services
  2. Nodes can earn rewards by participating in blockchain services
  3. SDP enables sybil resistance in service networks

blockchain:sovereign-zones

  1. Sovereign Zones can post their data to Blockchain channels
  2. Decentralized sequencing for Sovereign Zones through blockchain enforced sequencer coordination
  3. Cross-Sovereign Zones messaging facilitated by Blockchain

blockchain:wallet

  1. Transfer operations
  2. Inscription operations
  3. SDP operations

blockchain:areon

  1. Probabilistic finality model analyzed
  2. Network latency tolerance analyzed
  3. Total stake inference on Areon model
  4. Areon with Private Proof of Stake (Cryptareon)

blockchain:block-building

  1. Distributed block building Enabling tagging attack resistance and removing the leader as SPOF

lez

lez:programmable-privacy

  1. LEZ supports Programmable Privacy by allowing LEZ Programs to be agnostic as to whether they are interacting with private or public accounts

lez:sequencer

  1. LEZ Sequencer accepts transactions from users, orders them and posts them to Logos Blockchain
  2. Sequencer manages pending vs. safe vs. confirmed transactions
  3. Sequencer maintains funds to pay for blockchain transactions

lez:indexer

  1. Indexer follows LEZ channel in blockchain
  2. Indexer validates messages in the channel, skips invalid messages
  3. Indexer parses messages as blocks and applies blocks to local state
  4. Indexer maintains state history
  5. Indexer provides RPC endpoints for querying LEZ state

lez:program-interface

  1. Programs have defined interface exposing input/output accounts and contextual information (block number, random oracle, etc.)

lez:cross-program-calls

  1. Programs can call other programs deployed on LEZ

lez:bridging

  1. Channel Balance management
  2. Sequencer signing on withdrawal
  3. User deposits from Blockchain to LEZ

Usability

blockchain

  1. Blockchain node will be accessible through Logos-Core
  2. Blockchain configuration will be done through Logos-Core
  3. Blockchain will finalize transactions within 18hrs
  4. Logos Core Blockchain Wallet integration
  5. Ability to select which blockchain services are configured in a blockchain node

lez

  1. LEZ Programs are RISCV binaries, allowing developers to program in high level languages like Rust that compile down to RISCV
  2. The same LEZ Programs can be used in both private and public execution contexts
  3. Logos Core integration for LEZ Wallet
  4. Ability to run a sequencer through Logos Core
  5. Users can interact with LEZ through a wallet
  6. Block Explorer displays LEZ blocks and transactions
  7. Logos Core Module for LEZ operations

Reliability

blockchain

  1. Blockchain prioritizes liveness over safety ensuring we are resilient to large network failures
  2. Blockchain provides 18hrs for failures to resolve before the chain may split requiring manual intervention
  3. Data posted to DA will be available for at least 2 sessions (session length to be determined)

lez

  1. LEZ Sequencer supports decentralized sequencing through Blockchain enforced sequencer coordination, ensuring crash tolerance
  2. Crash tolerance through persisting state to disk
  3. Sequencer passes stress testing

Performance

blockchain

  1. Blockchain finalizes transactions in 18hrs
  2. Practical finality can be achieved much sooner
  3. Blocks are produced on average every 30s
  4. Blend Network manageable on low bandwidth network links

lez

  1. Transaction throughput targets (TBD)
  2. Proof generation time targets (TBD)

Supportability

lez

  1. Developer tooling to support LEZ program development
  2. Documentation ready for external contributors

0 items under this folder.