mirror of
https://repo.getmonero.org/monero-project/ccs-proposals.git
synced 2025-04-24 00:18:12 +00:00
Add deliverables, timelines, and funding
This commit is contained in:
parent
7f1d26aacc
commit
db4d213d5b
1 changed files with 60 additions and 24 deletions
|
@ -5,7 +5,7 @@ author: Deverickapollo & Napoly
|
|||
date: January 6, 2025
|
||||
amount: TBD
|
||||
milestones:
|
||||
- name: Requirements analysis and core infrastructure
|
||||
- name: Requirements analysis and core infrastructure
|
||||
funds: TBD
|
||||
done:
|
||||
status: unfinished
|
||||
|
@ -33,11 +33,18 @@ payouts:
|
|||
|
||||
Hello everyone!
|
||||
|
||||
We are excited to announce our plans to migrate and update the existing Monero implementation for BTCPay Server to align with version 2.0.0 and beyond. This process will involve restructuring the code into a plugin-based architecture that was introduces by BTCPay Server itself.
|
||||
We are excited to announce our plans to refactor the Monero integration for BTCPay Server. [The BTCPay team](https://blog.btcpayserver.org/btcpay-server-2-0/) recently released a major update to their core codebase with version 2.0, which has included breaking changes to the monero integration. This redesign will allow the Monero community to take ownership of the Monero integration and ensure its continued development. [The BTCPay team has expressed their support](https://github.com/btcpayserver/btcpayserver/pull/6535) for this initiative, and we are committed to making it a success. To prepare for this work, the Monero codebase has been migrated into its own directory to prepare for its removal from the core BTCPay Server codebase.
|
||||
|
||||
How did we get here? While hunting bounties and addressing various issues in the codebase, we realized that as BTCPay Server's core has [evolved](https://github.com/btcpayserver/btcpayserver/pull/6239#issuecomment-2373319844), the Monero integration has lagged behind. With no formal ownership of Monero’s code in this ecosystem, we concluded that it’s up to us to take action.
|
||||
How did we get here?
|
||||
|
||||
The integration was originally developed by @kukks of the BTCPay team. [A CCS proposal](https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/63) was submitted and an anonymous donor funded the work. While this implementation was successful, it lacked many features such as multi wallet support and basic wallet functionality.
|
||||
|
||||
While working on [open bounties](https://bounties.monero.social/posts/124/5-019m-btcpay-server-allow-syncing-via-remote-node) for the Monero community, we identified the need to realign our efforts on the [plugin migration](https://github.com/btcpayserver/btcpayserver/pull/6239#issuecomment-2373319844) to ensure continued support for Monero within BTCPay Server.
|
||||
|
||||
Thanks to partial funding from the Magic Grants, we were able to meet at Monerotopia 2024 to analyze this challenge in greater depth. As a result, we established a [roadmap](https://github.com/users/deverickapollo/projects/5/views/1) and a [plugin repository](https://github.com/napoly/btcpayserver-plugin-monero) with CI/CD support for stable releases and development. The plugin is currently in the proof of concept stage, with a focus on establishing a solid foundation for the plugin.
|
||||
|
||||
We are now seeking funding to support the development of this plugin and ensure its continued success. The funds will be used to support the development of the plugin, including the creation of a proof of concept and a minimum viable product. We are also seeking additional funding to support the final stages of development, including UI/UX enhancements, bug fixing, and merchant migration.
|
||||
|
||||
Thanks to partial funding from the Magic Grants, we were able to meet at a recent conference to analyze this challenge in greater depth. As a result, we created a [roadmap](https://github.com/users/deverickapollo/projects/5/views/1) and established an actual [plugin repository with CI/CD](https://github.com/napoly/btcpayserver-plugin-monero).
|
||||
|
||||
Contributors:
|
||||
|
||||
|
@ -46,31 +53,60 @@ Contributors:
|
|||
|
||||
## Milestones
|
||||
|
||||
1. Requirements analysis and core infrastructure (mostly done)
|
||||
- we have established a solid roadmap and build process, though a release has not yet been made
|
||||
### Milestone 1: Requirements Analysis and Core Infrastructure
|
||||
- **Deliverables:**
|
||||
- Finalized and published roadmap.
|
||||
- Operational CI/CD pipeline for plugin development and releases.
|
||||
- Plugin repository established and accessible.
|
||||
- **Funds:** 10% of funds
|
||||
- **Timeline:** Week 1-2
|
||||
- **Status:** Mostly done
|
||||
|
||||
2. Creating Proof of Concept (PoC) for the Monero Plugin (current focus)
|
||||
- plugin installation
|
||||
- enable starting a local Docker container or connecting to a remote node.
|
||||
- node sync visualization
|
||||
---
|
||||
|
||||
3. Developing the Minimum Viable Product (MVP) for the Monero Plugin
|
||||
- invoice creation
|
||||
- payment verification
|
||||
- wallet setup UI/UX
|
||||
### Milestone 2: Proof of Concept (PoC) for Monero Plugin
|
||||
- **Deliverables:**
|
||||
- Plugin installation mechanism functional.
|
||||
- Docker integration for local node or remote node connections.
|
||||
- Initial UI for node synchronization visualization.
|
||||
- Basic `monero-lws` support tested and integrated.
|
||||
- **Funds:** 25%
|
||||
- **Timeline:** Week 3-6
|
||||
- **Status:** Current focus
|
||||
|
||||
4. Final UI/UX Enhancements, Bug Fixing, Merchant Migration
|
||||
- plugin release
|
||||
- bugfixing
|
||||
- uninstallation
|
||||
- node synchronization notification
|
||||
- documentation
|
||||
- overall support
|
||||
---
|
||||
|
||||
### Milestone 3: Minimum Viable Product (MVP)
|
||||
- **Deliverables:**
|
||||
- Functional wallet setup interface (create, import, export, backup, recover).
|
||||
- Invoice creation and payment verification.
|
||||
- UI for Monero daemon configuration.
|
||||
- Integration for wallet recovery and backup functionality.
|
||||
- **Funds:** 35%
|
||||
- **Timeline:** Week 7-12
|
||||
- **Status:** Not started
|
||||
|
||||
---
|
||||
|
||||
### Milestone 4: Final Release (Polishing and Merchant Migration)
|
||||
- **Deliverables:**
|
||||
- UI/UX enhancements for seamless user experience.
|
||||
- Comprehensive documentation (installation, usage, troubleshooting, migration).
|
||||
- Bug fixing and testing.
|
||||
- Migration support for existing Monero merchants.
|
||||
- Final release of the plugin.
|
||||
- Post-release support and maintenance plan.
|
||||
- Community engagement and feedback collection.
|
||||
- Ongoing support for the plugin.
|
||||
- **Funds:** 30%
|
||||
- **Timeline:** Week 13-16
|
||||
- **Status:** Not started
|
||||
|
||||
## Timeline
|
||||
|
||||
The integration process is expected to take approximately 12-16 weeks.
|
||||
The integration process is expected to take approximately 16-20 weeks.
|
||||
|
||||
## Future Roadmap
|
||||
|
||||
TBD
|
||||
- Plans for ongoing maintanance and support for the plugin.
|
||||
- Community feedback for future improvements and features.
|
||||
- Expanding wallet features and functionality.
|
Loading…
Reference in a new issue