1. Executive Summary
DevSwap is a decentralized peer-to-peer marketplace for software services built on BNB Smart Chain. Its purpose is to rebuild trust in freelance software work by moving the core trust layer away from a centralized platform and into transparent smart contracts. Instead of asking users to rely only on a company that holds funds, controls reputation, and decides disputes, DevSwap gives clients and developers a system where funding, state transitions, settlement, and economic flows can be verified on-chain.
The economic model is deliberately simple. On every successfully released milestone, the developer receives 97% of the released amount. A 1.5% platform fee supports protocol operations, and a separate 1.5% is allocated to buy back and burn $DSWP when the token mechanism is enabled. The total fee is therefore 3%, split transparently.
Users should not have to trust a marketplace more. They should be able to verify more.
2. The Market Problem
2.1 High and Opaque Fees
Traditional platforms monetize centralized trust and charge significant fees. DevSwap makes the fee model contract-aligned: developer keeps 97%, platform fee 1.5%, and buyback-and-burn allocation 1.5%.
2.2 Delayed Settlement
In DevSwap, release is settlement. When a client approves a milestone, the developer’s net amount is transferred on-chain in the same transaction.
2.3 Platform-Locked Reputation
Reputation in traditional marketplaces is owned by the platform. DevSwap treats reputation as verifiable data: jobs completed, milestones released, and total earned.
3. The DevSwap Vision
In DevSwap, trust is redistributed across verifiable layers:
- The smart contract: holds funded work and executes settlement.
- The public ledger: records status transitions and releases.
- The application interface: helps users act without independent fund control.
4. Product Definition
4.1 What Is DevSwap?
A marketplace for software builders, focusing on: Web/Mobile development, Web3 contracts, DevOps, AI, and Technical Content.
4.2 Core Participants
| Participant | Role |
|---|---|
| Client | Funds USDT, reviews delivery, releases milestones. |
| Developer | Delivers milestones, receives 97% net settlement. |
| Smart contract | Maintains state, holds funds, routes allocations. |
| Arbiter | Resolves eligible disputes. |
4.3 Two Marketplace Modes
Gig Mode: Fast purchase for defined scope. createJob([amount], metadataHash).
Job Mode: Multi-stage work based on proposals. createJob([m1, m2, ...], metadataHash).
5. End-to-End Work Lifecycle
Funding follows two steps: Approve USDT allowance, then call createJob. All milestones are funded at job creation. Release triggers the 97/1.5/1.5 split. Developer payout is prioritized: if buyback fails, the 97% is still paid.
6. Work and Milestone State Model
V2.1 Milestone States:
None → Funded → Submitted → Released/Disputed/Cancelled
Software projects unfold in phases; the milestone model maps better to reality, reducing client risk and improving developer cash-flow.
7. Fee Model and Economics
| Component | Share | Description |
|---|---|---|
| Developer net | 97% | Paid instantly upon release. |
| Platform fee | 1.5% | Protocol operations. |
| Buyback and burn | 1.5% | $DSWP deflationary layer. |
8. The $DSWP Utility Token
$DSWP is a utility BEP-20 token on BSC. It is NOT an investment, promise of profit, or payment asset. USDT is used for settlement stability, while $DSWP captures network activity through buyback-and-burn.
Allocation (100,000,000 Total):
- 50% Activity Mining: Tied to actual usage.
- 25% Liquidity Pool: DSWP/USDT on PancakeSwap.
- 15% Team: 12-mo cliff, 48-mo linear vesting.
- 10% Community: Early rewards.
9. Technical Architecture
Source of truth: On-chain BSC contracts. Indexed layer: The Graph for performance. Off-chain layer: Supabase/IPFS for project briefs and metadata.
10. Security Model
Administrative functions are gated by a 3-of-5 Gnosis Safe (Multisig). Contracts use ReentrancyGuard and SafeERC20. Developer settlement is decoupled from market liquidity.
11. Dispute Resolution and Arbitration
Smart contracts cannot judge code quality. V2.1 uses registered arbiters with timelocks and "Dispute Snapshotting" to prevent puppet-arbiter attacks.
16. Roadmap
- Phase 1: MVP with USDT fees only.
- Phase 2: V2.1 convergence and reputation UI.
- Phase 4: Token and Liquidity activation (TGE).
- Phase 5: Controlled Mainnet expansion.