mirror of
https://github.com/logos-co/roadmap.git
synced 2026-08-27 09:01:07 +00:00
Blockchain Renames (#385)
* remove reference to Nomos in weekly updates * rename march/june testnets to v0.1 and v0.2 * rename LSSA to LEZ; Sovereign Rollup to Sovereign Zone * rename L1 / Bedrock to Blockchain; re-number FURPS
This commit is contained in:
davidrusu
@@ -12,117 +12,113 @@ FURPS are elsewhere divided into Milestones and Deliverables, to form a roadmap.
|
||||
|
||||
# Functionality
|
||||
|
||||
## `bedrock`
|
||||
## `blockchain`
|
||||
|
||||
### `bedrock:blockchain`
|
||||
### `blockchain:ppos` (Private Proof of Stake)
|
||||
1. Nodes can permissionlessly participate in consensus
|
||||
2. Nodes can join bedrock services and earn rewards
|
||||
3. Users can transfer funds
|
||||
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
|
||||
|
||||
### `bedrock:ppos` (Private Proof of Stake)
|
||||
4. Leaders can propose blocks privately
|
||||
5. Leaders can claim block rewards without revealing their block proposal
|
||||
6. Blend spam protection
|
||||
7. Block proposal redundancy
|
||||
8. Censorship resistance against malicious broadcasters
|
||||
9. Blend edge node privacy
|
||||
### `blockchain:sdp` (Service Declaration Protocol)
|
||||
8. Nodes can join blockchain services
|
||||
9. Nodes can earn rewards by participating in blockchain services
|
||||
10. SDP enables sybil resistance in service networks
|
||||
|
||||
### `bedrock:sdp` (Service Declaration Protocol)
|
||||
10. SDP enables membership in service networks
|
||||
11. SDP enables rewarding of service participants
|
||||
12. SDP enables sybil resistance in service networks
|
||||
### `blockchain:sovereign-zones`
|
||||
11. Sovereign Zones can post their data to Blockchain channels
|
||||
12. Decentralized sequencing for Sovereign Zones through blockchain enforced sequencer coordination
|
||||
13. Cross-Sovereign Zones messaging facilitated by Blockchain
|
||||
|
||||
### `bedrock:sovereign-rollups`
|
||||
13. Sovereign Rollups can post their data to Bedrock channels
|
||||
14. Decentralized sequencing for Sovereign Rollups through blockchain enforced sequencer coordination
|
||||
15. Cross-Sovereign Rollups messaging facilitated by Bedrock
|
||||
### `blockchain:wallet`
|
||||
14. Transfer operations
|
||||
15. Inscription operations
|
||||
16. SDP operations
|
||||
|
||||
### `bedrock:wallet`
|
||||
16. Transfer operations
|
||||
17. Inscription operations
|
||||
18. SDP operations
|
||||
### `blockchain:areon`
|
||||
17. Probabilistic finality model analyzed
|
||||
18. Network latency tolerance analyzed
|
||||
19. Total stake inference on Areon model
|
||||
20. Areon with Private Proof of Stake (Cryptareon)
|
||||
|
||||
### `bedrock:areon`
|
||||
19. Probabilistic finality model analyzed
|
||||
20. Network latency tolerance analyzed
|
||||
21. Total stake inference on Areon model
|
||||
22. Areon with Private Proof of Stake (Cryptareon)
|
||||
### `blockchain:block-building`
|
||||
21. **Distributed block building** Enabling tagging attack resistance and removing the leader as SPOF
|
||||
|
||||
### `bedrock:block-building`
|
||||
23. **Distributed block building** Enabling tagging attack resistance and removing the leader as SPOF
|
||||
## `lez`
|
||||
|
||||
## `lssa`
|
||||
### `lez:programmable-privacy`
|
||||
22. LEZ supports Programmable Privacy by allowing LEZ Programs to be agnostic as to whether they are interacting with private or public accounts
|
||||
|
||||
### `lssa:programmable-privacy`
|
||||
24. LSSA supports Programmable Privacy by allowing LSSA Programs to be agnostic as to whether they are interacting with private or public accounts
|
||||
### `lez:sequencer`
|
||||
23. LEZ Sequencer accepts transactions from users, orders them and posts them to Logos Blockchain
|
||||
24. Sequencer manages pending vs. safe vs. confirmed transactions
|
||||
25. Sequencer maintains funds to pay for blockchain transactions
|
||||
|
||||
### `lssa:sequencer`
|
||||
25. LSSA Sequencer accepts transactions from users, orders them and posts them to Logos Blockchain
|
||||
26. Sequencer manages pending vs. safe vs. confirmed transactions
|
||||
27. Sequencer maintains funds to pay for bedrock transactions
|
||||
### `lez:indexer`
|
||||
26. Indexer follows LEZ channel in blockchain
|
||||
27. Indexer validates messages in the channel, skips invalid messages
|
||||
28. Indexer parses messages as blocks and applies blocks to local state
|
||||
29. Indexer maintains state history
|
||||
30. Indexer provides RPC endpoints for querying LEZ state
|
||||
|
||||
### `lssa:indexer`
|
||||
28. Indexer follows LSSA channel in bedrock
|
||||
29. Indexer validates messages in the channel, skips invalid messages
|
||||
30. Indexer parses messages as blocks and applies blocks to local state
|
||||
31. Indexer maintains state history
|
||||
32. Indexer provides RPC endpoints for querying LSSA state
|
||||
### `lez:program-interface`
|
||||
31. Programs have defined interface exposing input/output accounts and contextual information (block number, random oracle, etc.)
|
||||
|
||||
### `lssa:program-interface`
|
||||
33. Programs have defined interface exposing input/output accounts and contextual information (block number, random oracle, etc.)
|
||||
### `lez:cross-program-calls`
|
||||
32. Programs can call other programs deployed on LEZ
|
||||
|
||||
### `lssa:cross-program-calls`
|
||||
34. Programs can call other programs deployed on LSSA
|
||||
|
||||
### `lssa:bridging`
|
||||
35. Channel Balance management
|
||||
36. Sequencer signing on withdrawal
|
||||
37. User deposits from L1 to LSSA
|
||||
### `lez:bridging`
|
||||
33. Channel Balance management
|
||||
34. Sequencer signing on withdrawal
|
||||
35. User deposits from Blockchain to LEZ
|
||||
|
||||
# Usability
|
||||
|
||||
## `bedrock`
|
||||
## `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 bedrock services are configured in a bedrock node
|
||||
5. Ability to select which blockchain services are configured in a blockchain node
|
||||
|
||||
## `lssa`
|
||||
6. LSSA Programs are RISCV binaries, allowing developers to program in high level languages like Rust that compile down to RISCV
|
||||
7. The same LSSA Programs can be used in both private and public execution contexts
|
||||
8. Logos Core integration for LSSA Wallet
|
||||
## `lez`
|
||||
6. LEZ Programs are RISCV binaries, allowing developers to program in high level languages like Rust that compile down to RISCV
|
||||
7. The same LEZ Programs can be used in both private and public execution contexts
|
||||
8. Logos Core integration for LEZ Wallet
|
||||
9. Ability to run a sequencer through Logos Core
|
||||
10. Users can interact with LSSA through a wallet
|
||||
11. Block Explorer displays LSSA blocks and transactions
|
||||
12. Logos Core Module for LSSA operations
|
||||
10. Users can interact with LEZ through a wallet
|
||||
11. Block Explorer displays LEZ blocks and transactions
|
||||
12. Logos Core Module for LEZ operations
|
||||
|
||||
# Reliability
|
||||
|
||||
## `bedrock`
|
||||
## `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)
|
||||
|
||||
## `lssa`
|
||||
4. LSSA Sequencer supports decentralized sequencing through Blockchain enforced sequencer coordination, ensuring crash tolerance
|
||||
## `lez`
|
||||
4. LEZ Sequencer supports decentralized sequencing through Blockchain enforced sequencer coordination, ensuring crash tolerance
|
||||
5. Crash tolerance through persisting state to disk
|
||||
6. Sequencer passes stress testing
|
||||
|
||||
# Performance
|
||||
|
||||
## `bedrock`
|
||||
## `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
|
||||
|
||||
## `lssa`
|
||||
## `lez`
|
||||
5. Transaction throughput targets (TBD)
|
||||
6. Proof generation time targets (TBD)
|
||||
|
||||
# Supportability
|
||||
|
||||
## `lssa`
|
||||
1. Developer tooling to support LSSA program development
|
||||
## `lez`
|
||||
1. Developer tooling to support LEZ program development
|
||||
2. Documentation ready for external contributors
|
||||
|
||||
@@ -22,8 +22,8 @@ Develop probabilistic model for finality in Areon. Areon is a testing ground for
|
||||
|
||||
**FURPS**:
|
||||
|
||||
- F19. Probabilistic finality model analyzed
|
||||
- F20. Network latency tolerance analyzed
|
||||
- F17. Probabilistic finality model analyzed
|
||||
- F18. Network latency tolerance analyzed
|
||||
|
||||
**Checklist**:
|
||||
- [ ] Probabilistic finality model
|
||||
|
||||
@@ -25,8 +25,8 @@ This has the added benefit of increasing blend reliability through message redun
|
||||
|
||||
**FURPS**:
|
||||
|
||||
- F7. Block proposal redundancy
|
||||
- F8. Censorship resistance against malicious broadcasters
|
||||
- F5. Block proposal redundancy
|
||||
- F6. Censorship resistance against malicious broadcasters
|
||||
|
||||
**Checklist**:
|
||||
- [ ] Message sharding protocol designed
|
||||
|
||||
@@ -24,7 +24,7 @@ Edge nodes only connect to Blend network nodes when they have block proposals, t
|
||||
|
||||
**FURPS**:
|
||||
|
||||
- F9. Blend edge node privacy
|
||||
- F7. Blend edge node privacy
|
||||
|
||||
**Checklist**:
|
||||
- [ ] Mix network integration designed
|
||||
|
||||
@@ -23,10 +23,10 @@ Complete Blend network implementation supporting private block proposals.
|
||||
|
||||
**FURPS**:
|
||||
|
||||
- F4. Leaders can propose blocks privately
|
||||
- F6. Blend spam protection
|
||||
- F7. Block proposal redundancy
|
||||
- F8. Censorship resistance against malicious broadcasters
|
||||
- F2. Leaders can propose blocks privately
|
||||
- F4. Blend spam protection
|
||||
- F5. Block proposal redundancy
|
||||
- F6. Censorship resistance against malicious broadcasters
|
||||
|
||||
**Checklist**:
|
||||
- [ ] Private block proposals
|
||||
|
||||
@@ -24,8 +24,6 @@ Full Cryptarchia consensus implementation for Logos Blockchain.
|
||||
**FURPS**:
|
||||
|
||||
- F1. Nodes can permissionlessly participate in consensus
|
||||
- F2. Nodes can join bedrock services and earn rewards
|
||||
- F3. Users can transfer funds
|
||||
|
||||
**Checklist**:
|
||||
- [ ] Chain leader selection (sk + slot secret + PoL)
|
||||
|
||||
@@ -25,10 +25,10 @@ Integrate Logos Blockchain node operations with Logos Core.
|
||||
- U1. Blockchain node will be accessible through Logos-Core
|
||||
- U2. Blockchain configuration will be done through Logos-Core
|
||||
- U4. Logos Core Blockchain Wallet integration
|
||||
- U5. Ability to select which bedrock services are configured in a bedrock node
|
||||
- U5. Ability to select which blockchain services are configured in a blockchain node
|
||||
|
||||
**Checklist**:
|
||||
- [ ] Logos Core Blockchain Wallet integration
|
||||
- [ ] Blockchain Node configuration exposed in Logos Core
|
||||
- [ ] Ability to select which bedrock services are configured in a bedrock node
|
||||
- [ ] Ability to select which blockchain services are configured in a blockchain node
|
||||
- [ ] Node operations accessible through Logos Core
|
||||
|
||||
@@ -22,9 +22,9 @@ Implement the Service Declaration Protocol for membership and rewards in service
|
||||
|
||||
**FURPS**:
|
||||
|
||||
- F10. SDP enables membership in service networks
|
||||
- F11. SDP enables rewarding of service participants
|
||||
- F12. SDP enables sybil resistance in service networks
|
||||
- F8. Nodes can join blockchain services
|
||||
- F9. Nodes can earn rewards by participating in blockchain services
|
||||
- F10. SDP enables sybil resistance in service networks
|
||||
|
||||
**Checklist**:
|
||||
- [ ] SDP transaction type implemented
|
||||
|
||||
@@ -22,9 +22,9 @@ Wallet implementation for Logos Blockchain operations.
|
||||
|
||||
**FURPS**:
|
||||
|
||||
- F16. Transfer operations
|
||||
- F17. Inscription operations
|
||||
- F18. SDP operations
|
||||
- F14. Transfer operations
|
||||
- F15. Inscription operations
|
||||
- F16. SDP operations
|
||||
|
||||
**Checklist**:
|
||||
- [ ] Expose API for Transaction building
|
||||
|
||||
@@ -1,4 +1,4 @@
|
||||
# Bridge Logos Token Between L1 and LSSA
|
||||
# Bridge Logos Token Between Blockchain and LEZ
|
||||
|
||||
**Estimated Delivery Date** June 2026
|
||||
|
||||
@@ -19,16 +19,16 @@
|
||||
|
||||
**Feature**: [FURPS](/blockchain/furps/index.md)
|
||||
|
||||
Enable bridging of Logos tokens between L1 (Bedrock) and LSSA.
|
||||
Enable bridging of Logos tokens between Blockchain and LEZ.
|
||||
|
||||
**FURPS**:
|
||||
|
||||
- F35. Channel Balance management
|
||||
- F36. Sequencer signing on withdrawal
|
||||
- F37. User deposits from L1 to LSSA
|
||||
- F33. Channel Balance management
|
||||
- F34. Sequencer signing on withdrawal
|
||||
- F35. User deposits from Blockchain to LEZ
|
||||
|
||||
**Checklist**:
|
||||
- [ ] Channel balance protocol
|
||||
- [ ] Deposit functionality (L1 to LSSA)
|
||||
- [ ] Withdrawal functionality (LSSA to L1)
|
||||
- [ ] Deposit functionality (Blockchain to LEZ)
|
||||
- [ ] Withdrawal functionality (LEZ to Blockchain)
|
||||
- [ ] Sequencer withdrawal signing
|
||||
|
||||
@@ -1,33 +0,0 @@
|
||||
# Logos Blockchain Cross-Sovereign Rollup Messaging
|
||||
|
||||
**Estimated Delivery Date** EoY 2026
|
||||
|
||||
## Resources Required
|
||||
|
||||
- 2 Researchers
|
||||
- 2 Engineers
|
||||
|
||||
## Risks
|
||||
|
||||
- Finalization delays in bedrock may prevent common use-cases
|
||||
|
||||
## Deliverables
|
||||
|
||||
### Cross-Sovereign Rollup Messaging
|
||||
|
||||
**Owner**: David Rusu
|
||||
|
||||
**Feature**: [FURPS](/blockchain/furps/index.md)
|
||||
|
||||
Enable messaging between Sovereign Rollups facilitated by Bedrock.
|
||||
|
||||
**FURPS**:
|
||||
|
||||
- F15. Cross-Sovereign Rollups messaging facilitated by Bedrock
|
||||
|
||||
**Checklist**:
|
||||
- [ ] Async messaging spec
|
||||
- [ ] Sync messaging spec
|
||||
- [ ] Bedrock implementation updated to match spec
|
||||
- [ ] cross-LSSA messaging spec
|
||||
- [ ] cross-LSSA messaging implementation
|
||||
@@ -0,0 +1,33 @@
|
||||
# Logos Blockchain Cross-Sovereign Zone Messaging
|
||||
|
||||
**Estimated Delivery Date** EoY 2026
|
||||
|
||||
## Resources Required
|
||||
|
||||
- 2 Researchers
|
||||
- 2 Engineers
|
||||
|
||||
## Risks
|
||||
|
||||
- Finalization delays in blockchain may prevent common use-cases
|
||||
|
||||
## Deliverables
|
||||
|
||||
### Cross-Sovereign Zone Messaging
|
||||
|
||||
**Owner**: David Rusu
|
||||
|
||||
**Feature**: [FURPS](/blockchain/furps/index.md)
|
||||
|
||||
Enable messaging between Sovereign Zones facilitated by Blockchain.
|
||||
|
||||
**FURPS**:
|
||||
|
||||
- F13. Cross-Sovereign Zones messaging facilitated by Blockchain
|
||||
|
||||
**Checklist**:
|
||||
- [ ] Async messaging spec
|
||||
- [ ] Sync messaging spec
|
||||
- [ ] Blockchain implementation updated to match spec
|
||||
- [ ] cross-LEZ messaging spec
|
||||
- [ ] cross-LEZ messaging implementation
|
||||
@@ -24,7 +24,7 @@ Address total stake inference underestimation by applying block reference ideas
|
||||
|
||||
**FURPS**:
|
||||
|
||||
- F21. Total stake inference on Areon model
|
||||
- F19. Total stake inference on Areon model
|
||||
|
||||
**Checklist**:
|
||||
- [ ] Current underestimation quantified
|
||||
|
||||
@@ -23,7 +23,7 @@ Make Areon use Private Proof of Stake (PPoS), creating Cryptareon.
|
||||
|
||||
**FURPS**:
|
||||
|
||||
- F22. Areon with Private Proof of Stake (Cryptareon)
|
||||
- F20. Areon with Private Proof of Stake (Cryptareon)
|
||||
|
||||
**Checklist**:
|
||||
- [ ] PPoS integration with Areon designed
|
||||
|
||||
@@ -23,7 +23,7 @@ Protocol draft for distributed block building in the mempool. Addresses tagging
|
||||
|
||||
**FURPS**:
|
||||
|
||||
- F23. **Distributed block building** Enabling tagging attack resistance and removing the leader as SPOF
|
||||
- F21. **Distributed block building** Enabling tagging attack resistance and removing the leader as SPOF
|
||||
|
||||
**Checklist**:
|
||||
- [ ] Protocol draft complete
|
||||
|
||||
@@ -3,8 +3,8 @@
|
||||
**Estimated Delivery Date** June 2026
|
||||
|
||||
## Resources Required
|
||||
- bedrock:research: 2 CC's
|
||||
- bedrock:engineering: 2 CC's
|
||||
- blockchain:research: 2 CC's
|
||||
- blockchain:engineering: 2 CC's
|
||||
- zones: 2 CC's
|
||||
|
||||
## Risks
|
||||
@@ -14,30 +14,30 @@
|
||||
|
||||
## Deliverables
|
||||
|
||||
### Bedrock
|
||||
### Blockchain
|
||||
|
||||
**Owner**: David Rusu
|
||||
|
||||
**Feature**: [FURPS](/blockchain/furps/index.md)
|
||||
|
||||
Most L2's depend on centralized sequencers, this is antithetical to the idea of decentralized networks. If we are to provide an L1 where the dominant programming model is through app chains, then we must ensure that we do all we can to make decentralized sequencing easy.
|
||||
Most L2's depend on centralized sequencers, this is antithetical to the idea of decentralized networks. If we are to provide a Blockchain where the dominant programming model is through app chains, then we must ensure that we do all we can to make decentralized sequencing easy.
|
||||
|
||||
The primary goal of this feature is to achieve decentralized sequencing without forcing Sovereign Rollups to run consensus. They should be able to achieve decentralized sequencing without the complexities of P2P networking and consensus protocols.
|
||||
The primary goal of this feature is to achieve decentralized sequencing without forcing Sovereign Zones to run consensus. They should be able to achieve decentralized sequencing without the complexities of P2P networking and consensus protocols.
|
||||
|
||||
Instead, Sovereign Rollups offload the complexity of decentralized networks to Logos Blockchain and can focus on building compelling applications.
|
||||
Instead, Sovereign Zones offload the complexity of decentralized networks to Logos Blockchain and can focus on building compelling applications.
|
||||
|
||||
**FURPS**:
|
||||
|
||||
- F14. Decentralized sequencing for Sovereign Rollups through blockchain enforced sequencer coordination
|
||||
- F12. Decentralized sequencing for Sovereign Zones through blockchain enforced sequencer coordination
|
||||
|
||||
**Checklist**:
|
||||
- [ ] Sequencers can join and leave from a Sovereign Rollup
|
||||
- [ ] Bedrock enforces sequencer schedule
|
||||
- [ ] Sequencers can join and leave from a Sovereign Zone
|
||||
- [ ] Blockchain enforces sequencer schedule
|
||||
- [ ] Decentralized Sequencing is tolerant to misbehaving sequencers
|
||||
|
||||
### LSSA
|
||||
### LEZ
|
||||
|
||||
LSSA will be the first user of decentralized sequencing, it will need to understand the decentralized sequencing model and ensure that the sequencer proposes blocks only when it is its turn, and downloads and processes the published blocks of fellow sequencers.
|
||||
LEZ will be the first user of decentralized sequencing, it will need to understand the decentralized sequencing model and ensure that the sequencer proposes blocks only when it is its turn, and downloads and processes the published blocks of fellow sequencers.
|
||||
|
||||
**Owner**: David Rusu
|
||||
|
||||
@@ -45,13 +45,13 @@ LSSA will be the first user of decentralized sequencing, it will need to underst
|
||||
|
||||
**FURPS**:
|
||||
|
||||
- R4. LSSA Sequencer supports decentralized sequencing through Blockchain enforced sequencer coordination, ensuring crash tolerance
|
||||
- R4. LEZ Sequencer supports decentralized sequencing through Blockchain enforced sequencer coordination, ensuring crash tolerance
|
||||
- U9. Ability to run a sequencer through Logos Core
|
||||
|
||||
**Checklist**:
|
||||
- [ ] Bedrock Specification updated with support for decentralized sequencing
|
||||
- [ ] Bedrock implementation updated to match spec.
|
||||
- [ ] LSSA integration with Bedrock Decentralized Sequencing model
|
||||
- [ ] Sequencers download channel messages from bedrock that were produced by fellow sequencers
|
||||
- [ ] Blockchain Specification updated with support for decentralized sequencing
|
||||
- [ ] Blockchain implementation updated to match spec.
|
||||
- [ ] LEZ integration with Blockchain Decentralized Sequencing model
|
||||
- [ ] Sequencers download channel messages from blockchain that were produced by fellow sequencers
|
||||
- [ ] Reject invalid blocks from fellow sequencers
|
||||
- [ ] Apply valid blocks from fellow sequencers
|
||||
|
||||
@@ -9,29 +9,29 @@ tags:
|
||||
|
||||
Logos Blockchain is working towards the following milestones
|
||||
|
||||
### March Testnet Milestones
|
||||
### Testnet v0.1 Milestones
|
||||
|
||||
- [LSSA Running as a Sovereign Rollup](./lssa_sovereign_rollup.md)
|
||||
- [LSSA Resilience](./lssa_resilience.md)
|
||||
- [LSSA Program Interface](./lssa_program_interface.md)
|
||||
- [LSSA Logos Core Integration](./lssa_logos_core.md)
|
||||
- [LEZ Running as a Sovereign Zone](./lez_sovereign_zone.md)
|
||||
- [LEZ Resilience](./lez_resilience.md)
|
||||
- [LEZ Program Interface](./lez_program_interface.md)
|
||||
- [LEZ Logos Core Integration](./lez_logos_core.md)
|
||||
- [Blockchain Logos Core Integration](./blockchain_logos_core.md)
|
||||
- [Blockchain SDP Implementation](./blockchain_sdp.md)
|
||||
- [Blockchain Cryptarchia Implementation](./blockchain_cryptarchia.md)
|
||||
- [Blockchain Blend Implementation](./blockchain_blend.md)
|
||||
- [Blockchain Wallet Implementation](./blockchain_wallet.md)
|
||||
|
||||
### June Testnet Milestones
|
||||
### Testnet v0.2 Milestones
|
||||
|
||||
- [Bridge Logos Token Between L1 and LSSA](./bridging.md)
|
||||
- [LSSA Decentralized Sequencing](./decentralized_sequencing.md)
|
||||
- [Bridge Logos Token Between Blockchain and LEZ](./bridging.md)
|
||||
- [LEZ Decentralized Sequencing](./decentralized_sequencing.md)
|
||||
|
||||
### Parallel Milestones
|
||||
|
||||
- [Cross Sovereign Rollup Messaging](./cross_sovereign_rollup_messaging.md)
|
||||
- [LSSA Unify Private / Public Execution](./lssa_unify_execution.md)
|
||||
- [LSSA Cross Program Calls](./lssa_cross_program_calls.md)
|
||||
- [LSSA Resolve State Contention](./lssa_state_contention.md)
|
||||
- [Cross Sovereign Zone Messaging](./cross_sovereign_zone_messaging.md)
|
||||
- [LEZ Unify Private / Public Execution](./lez_unify_execution.md)
|
||||
- [LEZ Cross Program Calls](./lez_cross_program_calls.md)
|
||||
- [LEZ Resolve State Contention](./lez_state_contention.md)
|
||||
- [Blockchain Blend Message Compression](./blend_message_compression.md)
|
||||
- [Blockchain Blend Broadcaster Censorship Resistance](./blend_broadcaster_censorship.md)
|
||||
- [Blockchain Blend Edge Node Privacy](./blend_edge_node_privacy.md)
|
||||
|
||||
+3
-3
@@ -1,4 +1,4 @@
|
||||
# LSSA Cross Program Calls
|
||||
# LEZ Cross Program Calls
|
||||
|
||||
**Estimated Delivery Date** Parallel Milestone
|
||||
|
||||
@@ -19,11 +19,11 @@
|
||||
|
||||
**Feature**: [FURPS](/blockchain/furps/index.md)
|
||||
|
||||
Enable programs to call other programs within LSSA.
|
||||
Enable programs to call other programs within LEZ.
|
||||
|
||||
**FURPS**:
|
||||
|
||||
- F34. Programs can call other programs deployed on LSSA
|
||||
- F32. Programs can call other programs deployed on LEZ
|
||||
|
||||
**Checklist**:
|
||||
- [ ] Cross-program call mechanism specification
|
||||
+4
-4
@@ -1,4 +1,4 @@
|
||||
# LSSA Logos Core Integration
|
||||
# LEZ Logos Core Integration
|
||||
|
||||
**Estimated Delivery Date** March 2026
|
||||
|
||||
@@ -19,12 +19,12 @@
|
||||
|
||||
**Feature**: [FURPS](/blockchain/furps/index.md)
|
||||
|
||||
Integrate LSSA wallet and sequencer operations with Logos Core.
|
||||
Integrate LEZ wallet and sequencer operations with Logos Core.
|
||||
|
||||
**FURPS**:
|
||||
|
||||
- U8. Logos Core integration for LSSA Wallet
|
||||
- U12. Logos Core Module for LSSA operations
|
||||
- U8. Logos Core integration for LEZ Wallet
|
||||
- U12. Logos Core Module for LEZ operations
|
||||
|
||||
**Checklist**:
|
||||
- [ ] C API defined and implemented
|
||||
+3
-3
@@ -1,4 +1,4 @@
|
||||
# LSSA Program Interface
|
||||
# LEZ Program Interface
|
||||
|
||||
**Estimated Delivery Date** March 2026
|
||||
|
||||
@@ -19,11 +19,11 @@
|
||||
|
||||
**Feature**: [FURPS](/blockchain/furps/index.md)
|
||||
|
||||
Define a clear interface for LSSA programs to interact with the runtime.
|
||||
Define a clear interface for LEZ programs to interact with the runtime.
|
||||
|
||||
**FURPS**:
|
||||
|
||||
- F33. Programs have defined interface exposing input/output accounts and contextual information (block number, random oracle, etc.)
|
||||
- F31. Programs have defined interface exposing input/output accounts and contextual information (block number, random oracle, etc.)
|
||||
|
||||
**Checklist**:
|
||||
- [ ] Block context exposed to programs
|
||||
+2
-2
@@ -1,4 +1,4 @@
|
||||
# LSSA Resilience
|
||||
# LEZ Resilience
|
||||
|
||||
**Estimated Delivery Date** March 2026
|
||||
|
||||
@@ -16,7 +16,7 @@
|
||||
|
||||
**Feature**: [FURPS](/blockchain/furps/index.md)
|
||||
|
||||
Ensure the LSSA sequencer can recover from crashes without data loss.
|
||||
Ensure the LEZ sequencer can recover from crashes without data loss.
|
||||
|
||||
**FURPS**:
|
||||
|
||||
@@ -0,0 +1,72 @@
|
||||
# LEZ Running as a Sovereign Zone
|
||||
|
||||
**Estimated Delivery Date** March 2026
|
||||
|
||||
## Resources Required
|
||||
|
||||
- 2.5 Engineers
|
||||
- Server for LEZ sequencer
|
||||
|
||||
## Risks
|
||||
|
||||
- New configuration that hasn't been tested previously
|
||||
- Without dedicated support from infrastructure, we may run into problems with networking and server deployments.
|
||||
|
||||
## Deliverables
|
||||
|
||||
### Sequencer
|
||||
|
||||
**Owner**: David Rusu
|
||||
|
||||
**Feature**: [FURPS](/blockchain/furps/index.md)
|
||||
|
||||
The LEZ Sequencer follows and publishes to Blockchain, managing the full lifecycle of sovereign zone operations.
|
||||
|
||||
**FURPS**:
|
||||
|
||||
- F23. LEZ Sequencer accepts transactions from users, orders them and posts them to Logos Blockchain
|
||||
- F24. Sequencer manages pending vs. safe vs. confirmed transactions
|
||||
- F25. Sequencer maintains funds to pay for blockchain transactions
|
||||
|
||||
**Checklist**:
|
||||
- [ ] Sequencer publishes blocks to Blockchain
|
||||
- [ ] Transaction lifecycle management (pending/safe/confirmed)
|
||||
- [ ] Automatic funding management for blockchain transactions
|
||||
|
||||
### Indexer
|
||||
|
||||
**Owner**: David Rusu
|
||||
|
||||
**Feature**: [FURPS](/blockchain/furps/index.md)
|
||||
|
||||
The Indexer follows the LEZ channel in Blockchain and maintains local state.
|
||||
|
||||
**FURPS**:
|
||||
|
||||
- F26. Indexer follows LEZ channel in blockchain
|
||||
- F27. Indexer validates messages in the channel, skips invalid messages
|
||||
- F28. Indexer parses messages as blocks and applies blocks to local state
|
||||
- F29. Indexer maintains state history
|
||||
- F30. Indexer provides RPC endpoints for querying LEZ state
|
||||
|
||||
**Checklist**:
|
||||
- [ ] Channel following operational
|
||||
- [ ] Message validation
|
||||
- [ ] Block parsing and state application
|
||||
- [ ] RPC endpoints available
|
||||
|
||||
### Block Explorer
|
||||
|
||||
**Owner**: David Rusu
|
||||
|
||||
**Feature**: [FURPS](/blockchain/furps/index.md)
|
||||
|
||||
Block Explorer connecting to Indexer for visibility into LEZ operations.
|
||||
|
||||
**FURPS**:
|
||||
|
||||
- U11. Block Explorer displays LEZ blocks and transactions
|
||||
|
||||
**Checklist**:
|
||||
- [ ] Block Explorer connected to Indexer
|
||||
- [ ] Transaction and block visibility
|
||||
+1
-1
@@ -1,4 +1,4 @@
|
||||
# LSSA Resolve State Contention
|
||||
# LEZ Resolve State Contention
|
||||
|
||||
**Estimated Delivery Date** Parallel Milestone
|
||||
|
||||
+3
-3
@@ -1,4 +1,4 @@
|
||||
# LSSA Unify Private / Public Execution
|
||||
# LEZ Unify Private / Public Execution
|
||||
|
||||
**Estimated Delivery Date** Parallel Milestone
|
||||
|
||||
@@ -23,8 +23,8 @@ Unify private and public execution to ensure programs truly support programmable
|
||||
|
||||
**FURPS**:
|
||||
|
||||
- F24. LSSA supports Programmable Privacy by allowing LSSA Programs to be agnostic as to whether they are interacting with private or public accounts
|
||||
- U7. The same LSSA Programs can be used in both private and public execution contexts
|
||||
- F22. LEZ supports Programmable Privacy by allowing LEZ Programs to be agnostic as to whether they are interacting with private or public accounts
|
||||
- U7. The same LEZ Programs can be used in both private and public execution contexts
|
||||
|
||||
**Checklist**:
|
||||
- [ ] Unified execution model designed
|
||||
@@ -1,72 +0,0 @@
|
||||
# LSSA Running as a Sovereign Rollup
|
||||
|
||||
**Estimated Delivery Date** March 2026
|
||||
|
||||
## Resources Required
|
||||
|
||||
- 2.5 Engineers
|
||||
- Server for LSSA sequencer
|
||||
|
||||
## Risks
|
||||
|
||||
- New configuration that hasn't been tested previously
|
||||
- Without dedicated support from infrastructure, we may run into problems with networking and server deployments.
|
||||
|
||||
## Deliverables
|
||||
|
||||
### Sequencer
|
||||
|
||||
**Owner**: David Rusu
|
||||
|
||||
**Feature**: [FURPS](/blockchain/furps/index.md)
|
||||
|
||||
The LSSA Sequencer follows and publishes to Bedrock, managing the full lifecycle of sovereign rollup operations.
|
||||
|
||||
**FURPS**:
|
||||
|
||||
- F25. LSSA Sequencer accepts transactions from users, orders them and posts them to Logos Blockchain
|
||||
- F26. Sequencer manages pending vs. safe vs. confirmed transactions
|
||||
- F27. Sequencer maintains funds to pay for bedrock transactions
|
||||
|
||||
**Checklist**:
|
||||
- [ ] Sequencer publishes blocks to Bedrock
|
||||
- [ ] Transaction lifecycle management (pending/safe/confirmed)
|
||||
- [ ] Automatic funding management for bedrock transactions
|
||||
|
||||
### Indexer
|
||||
|
||||
**Owner**: David Rusu
|
||||
|
||||
**Feature**: [FURPS](/blockchain/furps/index.md)
|
||||
|
||||
The Indexer follows the LSSA channel in Bedrock and maintains local state.
|
||||
|
||||
**FURPS**:
|
||||
|
||||
- F28. Indexer follows LSSA channel in bedrock
|
||||
- F29. Indexer validates messages in the channel, skips invalid messages
|
||||
- F30. Indexer parses messages as blocks and applies blocks to local state
|
||||
- F31. Indexer maintains state history
|
||||
- F32. Indexer provides RPC endpoints for querying LSSA state
|
||||
|
||||
**Checklist**:
|
||||
- [ ] Channel following operational
|
||||
- [ ] Message validation
|
||||
- [ ] Block parsing and state application
|
||||
- [ ] RPC endpoints available
|
||||
|
||||
### Block Explorer
|
||||
|
||||
**Owner**: David Rusu
|
||||
|
||||
**Feature**: [FURPS](/blockchain/furps/index.md)
|
||||
|
||||
Block Explorer connecting to Indexer for visibility into LSSA operations.
|
||||
|
||||
**FURPS**:
|
||||
|
||||
- U11. Block Explorer displays LSSA blocks and transactions
|
||||
|
||||
**Checklist**:
|
||||
- [ ] Block Explorer connected to Indexer
|
||||
- [ ] Transaction and block visibility
|
||||
@@ -23,7 +23,7 @@ Comprehensive testing framework to support testing scenarios and benchmarks.
|
||||
|
||||
**FURPS**:
|
||||
|
||||
- S1. Developer tooling to support LSSA program development
|
||||
- S1. Developer tooling to support LEZ program development
|
||||
|
||||
**Checklist**:
|
||||
- [ ] Testing framework designed
|
||||
|
||||
@@ -1,4 +1,4 @@
|
||||
---
|
||||
title: Nomos Weekly Updates
|
||||
title: Logos Blockchain Weekly Updates
|
||||
---
|
||||
These are all the Nomos weekly updates that are reported to Logos Insight team.
|
||||
These are all the weekly blockchain updates that are reported to Logos Insight team.
|
||||
|
||||
Reference in New Issue
Block a user