Experienced Software Engineer – P2P System Upgrade -- 2

$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: 40813021

About the project

30 proposals

Open for bidding

Remote project

Active 9 secs ago

Place your bid

Bid amount Email address

Benefits of bidding on Freelancer

Set your budget and timeframe

It's free to sign up and bid on jobs

30 freelancers are bidding on average $22 USD/hour for this job

User Avatar
Flag of UNITED STATES

Hi, I am Elias from the sunny state of Florida. I see you're looking to upgrade your existing P2P system, which suggests a focus on enhancing performance and ensuring reliability. Upgrading such systems typically involves addressing scalability and integration challenges, especially when dealing with blockchain technology. What usually matters most here is ensuring that the architecture can handle increased loads while maintaining security and efficiency. A common issue in systems like this is managing state effectively during transactions, which can complicate future integrations or expansions. My practical approach would involve a thorough assessment of your current architecture and workflows, ensuring that any new components enhance maintainability and align with your long-term goals. I have worked on similar projects involving complex trading systems and blockchain integrations, so I understand the nuances involved. A few questions to better understand the scope: Q1 – What specific functionalities do you want to enhance or add in the upgraded system? Q2 – Are there any existing integrations with third-party services that need to be maintained or improved? Q3 – What are your expectations for scaling the system in the next 1-2 years? Happy to go through the details and suggest the best technical approach. Looking forward to hearing from you.

User Avatar
Flag of PAKISTAN

Hello, Over a decade of technical delivery experience and hundreds of completed projects make Live Experts well suited to upgrading an established P2P/CEX codebase without losing sight of stability, scalability, or maintainability. Our team specializes in backend development, database development, software architecture, and software development, with experience across finance and trading systems. We work with modern technologies including Node.js, Python, FastAPI, PostgreSQL, AWS, and Docker, enabling us to improve existing architecture, implement reliable features, and strengthen integrations within mature systems. Our delivery approach emphasizes clean, maintainable software, practical implementation, dependable updates, and clear communication throughout collaboration. Live Experts is ready to contribute part-time to this 1-3 month upgrade and become a reliable engineering partner for the platform’s next version. Thanks!

User Avatar
Flag of PAKISTAN

Hi, I am Adeel. I would start by mapping how an order moves today, from posting through payment, escrow and release, before touching any code. The first decision is where the upgrade can change behaviour without risking live trades, which usually means a staged rollout behind feature flags. Architecture changes come after that, so stability is kept as we go. I built DAN, a B2B auction marketplace with bidding mechanics and settlement, which carries over to matching counterparties and settling each deal correctly. Over 10 years I have completed 161 projects here and I am in the top 3% of freelancers, as a Microsoft Certified Solution Developer. I am just a message away whenever you want to talk through the rollout plan for the P2P flow.

User Avatar
Flag of PAKISTAN

I can help upgrade your existing P2P system into a reliable CEX platform while preserving what already works. The key is to understand the current transaction flow before changing the architecture, so new features do not introduce balance or settlement errors. I would start with a codebase and architecture review, then map the requested CEX features to the existing system. From there, I would deliver changes in testable stages, with particular attention to ledger accuracy, concurrent transactions, security, monitoring, and safe deployment or rollback. This approach makes progress visible while protecting platform stability. I’m comfortable modernizing established codebases rather than assuming a rewrite is the answer. I communicate clearly about technical trade-offs, blockers, and completed work so your team can make decisions throughout the engagement. I don’t have access to the attached PDF here. Could you share it along with the current tech stack and the CEX features you want to prioritize first?

User Avatar
Flag of UNITED STATES

Hello!, I am a US-based senior software engineer, and I’d approach this P2P system upgrade with a focus on stability, security, and making sure nothing breaks in production. What usually hurts these projects is hidden coupling in the backend, unclear data flows, and “small” changes that end up affecting trading, APIs, or blockchain logic. I can help by breaking it into practical phases: 1) review the current Node.js/backend architecture and identify risks 2) map the P2P flow end to end, including database and API touchpoints 3) implement the upgrade in small, testable steps 4) validate with logging, edge-case testing, and deployment-safe checks I’ve built production systems where reliability matters, including trading tools, API-driven platforms, and backend-heavy SaaS products. A few relevant examples: TradePulse, LedgerLoop, NorthBridge CRM, and VaultFlow. Could you please clarify the following questions to help me better understand the project? 1) What part of the P2P system needs the upgrade most: matching logic, wallet/payment flow, messaging, admin tools, or database structure? 2) Are you expecting a full architecture update, or a targeted fix around one module? 3) Do you already have test cases or a staging environment we can use to verify the upgrade safely? If you want, I can jump in quickly and help you scope the exact work before coding starts. James Zappi

User Avatar
Flag of MEXICO

Hi, The biggest risk in upgrading a P2P platform to a CEX is changing the architecture without disrupting existing transaction flows. I'd prefer to understand how the current system works before recommending major changes or introducing new components. I can review the existing codebase, map its dependencies, identify architectural bottlenecks and work through the upgrade in stages. Each change should be tested carefully so that new functionality doesn't compromise existing operations, stability or data integrity. I also understand that communication is especially important in a 1–3 month engagement. I'd keep progress visible through regular written updates, clear technical explanations and agreed development milestones. Could you share the PDF and current technology stack? I'd like to understand the actual upgrade scope before suggesting the implementation approach. Best regards, Fernando

User Avatar
Flag of INDIA

⚠️ 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 modern CEX platform using a robust tech stack of Node.js and PostgreSQL with a scalable and high-performance design. I will deliver: • Revamped system architecture for enhanced performance • Implementation of new features tailored to your requirements • Comprehensive system stability and scalability assessments • Codebase optimization and refactoring for reliability • Ongoing collaboration and communication throughout the project You will also receive: • Detailed documentation for future maintenance • Post-launch support and training for your team I am confident I can execute your vision professionally and efficiently. Looking forward to discussing timeline and next steps. Best regards, Chirag Pipal

User Avatar
Flag of PAKISTAN

Hi there, Backend and API work is one of my core strengths, including Node.js, Backend Development and API Development. I recently built a custom API from scratch and the client was impressed with the speed and quality. For "Experienced Software Engineer – P2P System Upgrade -- 2" I would design a clean, secure and well-documented API that is easy to extend. How I would approach it: - Agree on endpoints, data models and authentication first - Build with validation, error handling and logging - Share documentation and test results at handover Which systems or apps will this API need to connect with? Message me and I will outline the structure I would use for your project. Umair

User Avatar
Flag of JAPAN

Modernizing an established P2P/CEX codebase requires both hands-on software development and sound architectural judgment, and my core strengths are Node.js, software architecture, and scalable backend development. I work across existing systems to improve maintainability, implement new functionality, and deliver reliable updates without losing sight of stability. My broader experience includes REST APIs, database design and optimization, authentication and authorization, real-time backend services, cloud deployment, Docker, CI/CD, testing, debugging, performance optimization, and security-conscious development. These capabilities align closely with your need to enhance the current architecture, support scalability, and work effectively within an established codebase. Clear communication and collaboration are central to how I support engineering teams, particularly on ongoing product improvements. I would be glad to contribute part-time to your upgrade project and help deliver a stable, maintainable CEX platform.

User Avatar
Flag of INDIA

Upgrading an established P2P/CEX codebase requires both strong software architecture and practical experience with Web3 products. I bring 8+ years of experience delivering web platforms, backend systems and blockchain solutions, with Node.js and software architecture among my core skills. My background includes MERN applications with REST APIs, PostgreSQL, MongoDB, multi-role dashboards and payment integrations, as well as smart contracts, crypto wallet integration, dApps and blockchain features for web and mobile products. This experience is directly relevant to modernizing an existing platform, adding reliable features, and keeping stability and scalability in focus while working within an established codebase. I also lead a development team that provides clear daily updates, documented code and milestone-based delivery, supporting effective collaboration throughout a part-time engagement. I would be glad to contribute my architecture, Node.js and blockchain expertise to your P2P system upgrade.

User Avatar
Flag of INDIA

Hello, Upgrading a P2P system to a CEX platform is tricky, you'll need to modernize without breaking existing functionality, especially around stability and scalability. The real catch is balancing new features with the legacy codebase, making sure changes don't introduce unexpected issues. I'd start by auditing the current architecture to identify weak points and dependencies, then prioritize updates that improve scalability first. From there, we'd phase in new features with thorough testing at each step. I'd keep communication tight with regular check-ins to align on progress. I delivered something similar last month, a document-analysis chatbot with RAG that required careful integration into an existing system. Do you have a preferred testing framework or CI pipeline already in place for this codebase?

内容来自 Freelancer News,版权归原作者所有。

阅读原文 ↗

把喜欢的内容,留在你的新标签页。

打开我的订阅