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

bedrock

bedrock:blockchain

  1. Nodes can permissionlessly participate in consensus
  2. Nodes can join bedrock services and earn rewards
  3. Users can transfer funds

bedrock:ppos (Private Proof of Stake)

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

bedrock:sdp (Service Declaration Protocol)

  1. SDP enables membership in service networks
  2. SDP enables rewarding of service participants
  3. SDP enables sybil resistance in service networks

bedrock:sovereign-rollups

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

bedrock:wallet

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

bedrock: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)

bedrock:block-building

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

lssa

lssa:programmable-privacy

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

lssa:sequencer

  1. LSSA 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 bedrock transactions

lssa:indexer

  1. Indexer follows LSSA channel in bedrock
  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 LSSA state

lssa:program-interface

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

lssa:cross-program-calls

  1. Programs can call other programs deployed on LSSA

lssa:bridging

  1. Channel Balance management
  2. Sequencer signing on withdrawal
  3. User deposits from L1 to LSSA

Usability

bedrock

  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 bedrock services are configured in a bedrock node

lssa

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

Reliability

bedrock

  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)

lssa

  1. LSSA 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

bedrock

  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

lssa

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

Supportability

lssa

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

0 items under this folder.