Dynamic Cryptocurrency Trading Platform Development

Senior Blockchain / CEX Development Team Required – AlphaNex

Project Overview
We are building AlphaNex, a new cryptocurrency trading platform backed by significant investment and a clear long-term vision.

We are looking for an experienced technical partner, not simply developers who implement specifications. The selected team must be capable of reviewing our existing MVP, challenging architectural decisions, identifying risks, recommending what should be reused/refactored/rebuilt, and ultimately developing a secure, scalable, production-ready CEX.

Our target is an initial production-ready release within approximately 3 months. We understand this is aggressive and expect an honest technical assessment based on the existing codebase, remaining scope, dependencies, and required team size.

Security, scalability, reliability, performance, and engineering quality are critical.

Existing AlphaNex MVP
An MVP is already under development.

GitHub Repository:
https://github.com/AlphaNex-Lab/Exchange

Read-only GitHub access will be provided to shortlisted teams.

The first objective is a technical due-diligence review to determine:

What has been built correctly
What can realistically be reused
What requires refactoring
What should be rebuilt
What must be developed from scratch
Missing functionality
Architectural and security issues
Scalability limitations
Requirements for production readiness
Core Platform Scope

The production platform is expected to include:

1. User & Account Management
Registration/authentication, email/phone verification, 2FA, profiles, account status, portfolio/balance management, transaction history, audit logs, and RBAC.

2. Spot Trading
Trading pairs, buy/sell, market and limit orders, cancellation/status, order/trade history, validation, balance reservation/locking, trading fees, trading limits, and minimum/maximum order sizes.

3. Matching Engine & Order Book
Assess the existing implementation for architecture, order-book design, sequencing, matching logic, concurrency/race conditions, latency, market integrity, persistence/recovery, failure handling, and scalability.

Clearly classify whether it should be reused, refactored, or rebuilt.

4. Internal Ledger & Accounting
Double-entry ledger, available/locked balances, trading transactions, deposits/withdrawals, fees, internal transfers, reconciliation, idempotency, auditability, financial consistency, and error recovery.

5. Wallet & Custody
Hot/cold wallet strategy, deposit addresses, blockchain monitoring, transaction broadcasting, confirmations, reconciliation, withdrawals, limits/risk controls, key management, private-key protection, and operational security.

Production-grade wallet/custody experience is highly preferred.

6. Deposits & Withdrawals
Address generation, blockchain monitoring, confirmation management, deposit crediting, withdrawal queues, manual/automated approvals, transaction signing, risk checks, failed transaction handling, reconciliation, and network-fee management.

7. Blockchain Infrastructure
Node/API and RPC integrations, blockchain indexing, transaction/address monitoring, confirmation tracking, retry/failure handling, asset management, and multi-chain abstraction.

The architecture should allow additional networks/assets to be added without major redevelopment.

8. Liquidity Integration
External liquidity providers, market makers, aggregation, price feeds, order routing, market-data normalization, monitoring, failover, APIs, and liquidity risk management.

9. Real-Time Market Data
Ticker data, order-book updates, trade streams, OHLC/candlesticks, market statistics, WebSockets, REST APIs, event streaming, and low-latency distribution.

10. APIs
REST/WebSocket APIs for authentication, accounts, trading, orders, market data, wallets, deposits, and withdrawals, with appropriate security, rate limiting, scalability, versioning, monitoring, and documentation.

11. KYC / AML / Compliance
Integration with suitable third-party providers for KYC/identity verification, AML and sanctions screening, transaction monitoring, risk scoring, account restrictions, compliance workflows, suspicious-activity flags, and audit trails.

12. Admin & Operations
User/KYC management, account restrictions, asset and trading-pair management, wallet and transaction management, withdrawal approvals, fees, trading limits, risk controls, liquidity/system monitoring, audit logs, reporting, and administrator RBAC.

13. Security & Risk
Review and recommend controls for authentication/2FA, RBAC, API security, wallet/custody, key management, withdrawal controls, fraud monitoring, rate limiting, account takeover prevention, secrets management, encryption, audit logging, infrastructure security, DDoS protection, monitoring/alerting, backups, disaster recovery, and incident response.

14. Infrastructure & DevOps
Assess cloud architecture, containers, CI/CD, infrastructure-as-code, database architecture, caching, queues/event streaming, load balancing, horizontal scaling, monitoring/logging, high availability, failover, backup/recovery, staging/UAT, and production deployment.

Technical Due-Diligence Deliverable

Before committing to the full development contract, provide an assessment covering:

Architecture: Current stack, services/components, database/API architecture, infrastructure, and third-party integrations.
Code Quality: Structure, maintainability, technical debt, testing, documentation, dependencies, and scalability.

For each major module, classify it as:

REUSE – suitable with minimal changes
REFACTOR – usable foundation but requires substantial changes
REBUILD – should be replaced
NEW DEVELOPMENT – functionality does not currently exist

Also identify security vulnerabilities, architectural risks, production blockers, and everything required before launch.

3Month Timeline Assessment

Our target is approximately 3 months for the initial production-ready release.

We need an honest assessment of:
Whether 3 months is realistically achievable
Scope deliverable within 4 months
Required assumptions/dependencies
Potential delays and risks
Required team size
Features that should be phased
Launch priorities

Budget
We are not setting a fixed development budget at this stage.

First, we want the existing MVP and remaining workload properly assessed.

After the assessment, provide:
Remaining development scope
Estimated hours/man-days by module
Recommended team size
Monthly/team cost
Total project budget
Expected timeline
Optional phased pricing

Potential structure:
Technical Due Diligence
Architecture & Production Hardening
Core CEX Development
Security, QA & UAT
Production Deployment
Post-Launch Support

We value an accurate engineering estimate over the lowest quotation.

Who We Are Looking For
Strong preference for teams with genuine experience in:

Centralized cryptocurrency exchanges
Trading platforms and matching engines
Order-book systems
Crypto wallets and custody
Blockchain infrastructure
Fintech/payment systems
High-volume transactional platforms
Real-time trading systems
Security-critical applications

Actual production CEX or comparable financial/trading infrastructure experience is highly preferred.

Please Do Not Submit a Generic Proposal

Please answer the following:
What CEX, trading, wallet, custody, fintech, or Web3 platforms have you built?
What specifically did your team develop?
Have you built/worked on a matching engine or order-book system?
What wallet/custody architecture experience do you have?
What is the largest production system you have supported?
What security measures are mandatory before launching AlphaNex?
Based on your experience, what would be required for a 4-month launch?
How long would you need to complete the MVP/codebase assessment?
What team would you recommend?
How would you structure the engagement and development phases?

Please include relevant project examples, your exact role, technology stack, and measurable scale where possible.

Proposed Engagement Process

Phase 1 – Repository Review: Read-only access to the AlphaNex GitHub repository.
Phase 2 – Technical Due Diligence: Review architecture, code, MVP functionality, integrations, security, scalability, and production readiness.
Phase 3 – Assessment & Recommendations: Provide the REUSE / REFACTOR / REBUILD / NEW DEVELOPMENT assessment.
Phase 4 – Architecture & Roadmap: Recommend production architecture, team structure, roadmap, priorities, and timeline.
Phase 5 – Commercial Proposal: Provide detailed effort, budget, and timeline based on actual remaining work.
Phase 6 – Technical Discussion: 30–45 minute discussion with our team/investor/CEO to review findings, risks, architecture, timeline, and recommendations.
Phase 7 – Full Development: Subject to mutual agreement, proceed with the production development program.

Final Objective

Our goal is to build AlphaNex as a secure, scalable, professionally engineered cryptocurrency exchange capable of long-term growth, not simply launch an MVP.
We want a technical partner who can take ownership, challenge decisions when necessary, identify risks before they become production problems, and help us build the platform correctly.
If you have genuine experience in CEX, trading infrastructure, blockchain, custody, wallets, fintech, or other high-reliability transactional systems, we would like to hear from you.

Please focus your proposal on your relevant experience, technical approach, MVP assessment methodology, recommended team, timeline, and proposed engagement structure.