Experienced Software Engineer – P2P System Upgrade
$15-25 USD / hour
Posted 1 minute ago
•
Ends in 6 days
$15-25 USD / hour
About the Project: We are looking for experienced software engineers to upgrade our existing P2P system to a new version of a CEX (Centralized Exchange) platform. This is a hands-on role that involves working with an established codebase to modernize and enhance the system. Scope of Work: • Improve the current system architecture • Implement new features based on project requirements • Ensure system stability and scalability throughout the upgrade • Work comfortably within an existing codebase, identifying areas for improvement and delivering reliable updates What We're Looking For: • Proven experience working with existing codebases and legacy systems • Strong understanding of system architecture, scalability, and stability best practices • Experience with P2P systems and/or CEX platforms is a strong plus • Excellent communication and collaboration skills — this is a key priority for the project Project Details: • Engagement: Part-time • Duration: 1 to 3 months • Collaboration: Strong focus on communication and teamwork throughout the development process To Apply: Please review the attached PDF for full project details. Thank you
Project ID: 40810559
About the project
19 proposals
Open for bidding
Remote project
Active 4 secs ago
Place your bid
Bid amount Email addressBenefits of bidding on Freelancer
Set your budget and timeframe
It's free to sign up and bid on jobs
19 freelancers are bidding on average $20 USD/hour for this job


Your P2P-to-CEX upgrade requires careful modernization of an established codebase without compromising stability. I can help assess the current architecture, identify legacy bottlenecks, and implement new functionality with scalability, security, and maintainability in mind. My approach would include reviewing the existing services and data flows, mapping upgrade risks, prioritizing improvements, and delivering changes in clear, testable increments. I would also focus on exchange-critical concerns such as transaction consistency, API reliability, access control, monitoring, and resilient handling of high-concurrency workflows. I value the communication and teamwork emphasized in your brief, with concise progress updates, transparent technical decisions, and early visibility into risks or dependencies. The attached project details can guide a practical upgrade plan aligned with your current system and target CEX architecture. I am available for the proposed part-time engagement and can contribute effectively throughout the 1-3 month delivery window. Regards


⚠️ If you're not happy, you don’t pay. ⚠️ Hi Client, thank you for checking my proposal and sharing the detailed project brief. I can upgrade your P2P system to a high-end CEX platform using a modern tech stack (Node.js, React, and PostgreSQL) with a scalable and performance-optimized design. I will deliver: • Enhanced system architecture for improved performance • New features tailored to your project requirements • Rigorous testing for stability and scalability • Codebase optimization for reliability and maintainability • Comprehensive documentation for future upgrades You will also receive: • Ongoing support and training for your team I am confident I can execute your vision professionally and efficiently. Looking forward to discussing the timeline and next steps. Best regards, Chirag Pipal.


Hi, Had a look through the job and this is pretty straightforward from my side. I wouldn't start changing things blindly. First thing I'd do is go through the existing code, architecture and data model so the new work fits cleanly into what you already have. I can take this end-to-end - implement the core features cleanly, keep the code maintainable, and make sure the important flows are tested before we call it done. The existing website can stay as it is. I'd keep the new work separate where it makes sense, test the flows properly, then deploy once everything is working. If you send over the code and tell me which sections/data you want manageable from the dashboard, I can have a look and get started. Best regards, Salah


Hello, Upgrading a P2P system to a new CEX platform means threading changes through order matching, settlement logic, and wallet integrations without breaking live trades, and that's where reading the existing codebase carefully pays off. I built a Node backend for a booking marketplace that handled concurrent reservations and payment flows. When we migrated to a new payment processor, the key was mapping old transaction states to new ones without losing records—took about three weeks and ran clean through testing. Here, I'd start by mapping the current P2P architecture against the new CEX requirements, then phase in features in dependency order so the system stays stable at each step. Database migrations and API contract changes are the places where most upgrades slip, so those get extra attention. Working in sprints with clear handoffs keeps communication direct and catches conflicts early. For one month after launch, any bugs tied to the upgrade itself are fixed at no extra cost. I'll document each change as it lands so your team can maintain it forward. What's the current P2P codebase written in, and are there live trades running that can't go down during the upgrade? Thanks, Christian


Hi there, Transitioning a P2P system to a CEX platform requires a deep understanding of both architectures, especially in terms of transaction flows and security protocols. The challenge often lies in aligning decentralized features with centralized controls. I'd start by analyzing the existing architecture to identify potential bottlenecks and scalability issues, ensuring the upgrade aligns with the latest CEX standards. I've worked on complex backend systems and can bring that experience to ensure a smooth transition. Best Andrew


You're upgrading an existing P2P system to a new CEX platform version, modernizing proven architecture rather than building from scratch. This requires navigating established code, identifying bottlenecks, and enhancing stability without introducing regressions. I'd start by reviewing the current codebase structure, mapping dependencies, and understanding how the existing P2P logic couples to the exchange layer. From there, we'd stage the upgrade: refactor high-risk areas first, implement new CEX features incrementally, and validate each phase against your performance and reliability benchmarks. The collaboration piece matters here. I'd keep communication tight, regular syncs on blockers, clear handoffs between architecture changes and feature work, and documented decisions so the team moves cohesively. Part-time over 1-3 months means working efficiently within your existing flow without disrupting day-to-day operations. Regards, MISS -
内容来自 Freelancer News,版权归原作者所有。
阅读原文 ↗