add 2026 Floresta tech strategy and roadmap #910
+101
−0
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,87 @@ | ||
| # Floresta Technical Strategy & Roadmap 2026 | ||
|
|
||
| ## Governance & Scope | ||
|
|
||
| This document reflects the current technical direction proposed by the Floresta core team. We value quality and transparency during our process and this will be the primary place to follow all updates regarding our roadmap. | ||
|
|
||
| - The roadmap is **public and open for feedback** | ||
| - Direction and prioritization are **curated and approved by the Floresta core team** | ||
| - External contributors are encouraged to: | ||
| - Provide feedback | ||
| - Propose ideas | ||
| - Make contributions aligned with the roadmap and strategic themes | ||
|
|
||
| ## Vision | ||
|
|
||
| Floresta is a lightweight and embeddable Bitcoin client designed for applications and users that require strong validation guarantees but cannot accommodate the operational overhead of traditional full nodes. | ||
|
|
||
| Rather than a monolithic design, Floresta is built as a **composable system**. | ||
|
|
||
| Applications integrate through well-defined interfaces instead of modifying or forking the codebase. | ||
|
|
||
| Modularity is validated through real integrations with ecosystem tools. | ||
|
|
||
| Floresta aims to be a **production-grade alternative to Bitcoin Core** for lightweight, application-focused use cases, while maintaining strong guarantees when it comes to consensus and security. | ||
|
|
||
| ## Strategic Themes | ||
|
|
||
| All roadmap initiatives are guided by the following six strategic themes: | ||
|
|
||
| 1. **Reliability & Security** | ||
| 2. **Sync & Transaction Relay** | ||
| 3. **Bitcoin Ecosystem Support** | ||
| 4. **Modular Architecture** | ||
| 5. **Testing & Validation** | ||
| 6. **Community Adoption & User Experience** | ||
|
|
||
| ## 2026 Roadmap | ||
|
|
||
| > This section reflects the current priorities identified for each strategic theme to be worked on throughout 2026, and can be refined as work progresses. | ||
| > | ||
| > Workstreams and quarterly efforts addressing these initiatives are detailed on the [Project Board](https://github.com/orgs/getfloresta/projects/2). | ||
|
Contributor
There was a problem hiding this comment. Got a 404 page from this link
Collaborator
There was a problem hiding this comment. this link is available to the Floresta team for now. |
||
|
|
||
| ### Reliability & Security | ||
|
|
||
| - Ensure trustworthy runtime behavior | ||
| - Maintain production-quality execution | ||
| - Strengthen operational robustness | ||
| - Improve resilience to network-level attacks | ||
|
|
||
| ### Sync & Transaction Relay | ||
|
|
||
| - Improve blockchain synchronization performance | ||
| - Enhance transaction and block propagation | ||
| - Strengthen mempool capabilities | ||
|
|
||
| ### Bitcoin Ecosystem Support | ||
|
|
||
| - Maintain compatibility with widely used RPC interfaces | ||
| - Enable integration with external developer toolkits | ||
| - Validate behavior against common Bitcoin workflows | ||
|
|
||
| ### Modular Architecture | ||
|
|
||
| - Enforce architectural separation through domain boundaries | ||
| - Organize development around modular components | ||
|
|
||
| ### Testing & Validation | ||
|
|
||
| - Establish comprehensive testing strategies (unit, integration and fuzzing) | ||
| - Strengthen coverage across core components | ||
| - Improve CI reliability and automated validation pipelines | ||
|
|
||
| ### Community Adoption & User Experience | ||
|
|
||
| - Improve documentation and onboarding materials | ||
| - Refine user-facing interfaces and developer tooling | ||
| - Strengthen presence in the Bitcoin ecosystem | ||
| - Grow and support the contributor base | ||
|
|
||
| ## Notes | ||
|
|
||
| - The roadmap defines **direction, not guarantees** | ||
| - This is a living document and will be updated quarterly based on community feedback and project evolution | ||
| - Priorities and timelines may shift as we progress, based on: | ||
| - Implementation complexity | ||
| - Security considerations | ||
| - Ecosystem needs | ||
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Same here.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this link is available to the Floresta team for now.