Blockchain Exchange Platform with Options Trading, IEO & Staking Module – PHP Source Code

Looking for a full-featured 交易所系统 that goes beyond basic spot trading? This build is forked from the woocloud exchange engine and reworked with three additions that actually matter: an IEO launchpad, an options contract module, and a locked-staking finance panel. It also ships with both a mobile web client and a newly added PC client, which is honestly the part most forks skip.

If you’re evaluating this source code download on dajian168, here’s what I found while reviewing the package — including the rough edges to watch for before you point a domain at it.

The PC client is the headline upgrade. Most woocloud forks stay mobile-only, which is a deal-breaker for serious traders.

The repo includes 3 frontend entry points: an H5 mobile web (the original woocloud skin), a Vue-based admin console, and a newly added PC trading interface rendered through /pc/. The PC build reuses the same API endpoints under /api/v3/, so there’s no duplicate business logic to maintain.

When I deployed this locally, the PC layout uses ECharts 5.4 for K-line rendering — which means your server needs to handle websocket subscriptions per pair, not just HTTP polling. Budget at least 2 vCPU and 4 GB RAM if you’re running more than 50 active trading pairs.

• Trading engine: PHP 7.4 + MySQL 8.0 + Redis 6.x
• Frontend: Vue 2.6 (admin), Vue 3 + ECharts (PC), uni-app (H5)
• WebSocket layer: Workerman 4.x for real-time order book

Four trading modules, one shared wallet layer. Spot, options, IEO, and locked staking all draw from the same user funds table.

The clever bit is the funds_split table — every deposit auto-mirrors into spot / options / finance sub-balances, so a user can have BTC locked in an IEO subscription while still placing spot orders with USDT. I’ve seen forks where these are separate systems and reconciliation breaks within a week.

Options contracts here are European-style (settle at expiry), with 4 strike intervals configurable per pair. The IEO module supports KYC-gated allocation, and the locked-staking panel ships with 3 preset tiers (7d / 30d / 90d) plus a custom APR field in admin.

The platform token (平台币) support is wired through config/coin.php — drop your contract address in and the fee-discount logic activates automatically.

Deployment takes about 40 minutes if your stack is ready. Here’s the order I’d run it in.

Skip the included install.php wizard — it worked in testing but left the admin password in plaintext. Do a manual install instead.

1. Create MySQL DB, import /sql/v2.3_init.sql, then run the migration scripts in /sql/upgrade/ in order.
2. Set .env with Redis password and a 32-char APP_KEY (use php artisan key:generate).
3. Run php artisan queue:work redis --tries=3 as a supervised process — the IEO settlement and staking release jobs live here.
4. Configure Nginx: try_files $uri $uri/ /index.php?$query_string; plus WebSocket passthrough on port 8282.
5. Symlink /public as the webroot, never expose /app or /config.

There is a setting in the admin panel under System → Security → API Rate Limit that’s set to 100 req/min by default. For a public exchange I’d raise that to 600 req/min per IP or you’ll throttle legit trading bots.

Before you go live, audit these 5 things. I caught all of them in a single test run.

• KYC callback URL: points to the woocloud demo domain — replace it or every “approved” user gets flagged.
• Withdrawal address whitelist: enabled but empty by default, so the first withdrawal skips the cooldown.
• Platform token decimal handling: the contract assumes 18 decimals. If your token uses 8 (like BTC), trades silently miscalculate.
• Timezone: config/app.php defaults to UTC, but the IEO countdown uses server-local time — pick one and stick with it.
• SSL on WebSocket: browsers won’t connect to ws:// from HTTPS pages. Use wss:// and proxy through Nginx.

Best Fit: Who Should Use This Build

This source code download makes sense for small-to-mid exchanges targeting Asian markets where options + IEO + 锁仓理财 are bundled as a retention package. It’s not the right pick if you need matching-engine-level throughput (this is a PHP-fpm model, not Go or C++) or if your jurisdiction requires proof-of-reserves tooling — there’s no on-chain audit hook here.

For a demo studio, prototype exchange, or university fintech lab, it’s a solid 交易所系统 reference with enough real wiring to learn from.

FAQ

Q: Can the PC client and H5 share the same login session?

A: Yes. Both frontends hit /api/v3/user/login and the JWT is stored in localStorage on PC, sessionStorage on H5. Logout on one doesn’t auto-invalidate the other — you’ll need to add a token-version check in user_tokens if that matters.

Q: Does the platform token (平台币) require a custom ERC-20 contract, or does the system generate one?

A: The system does NOT deploy contracts. You bring your own BEP-20 / ERC-20 token and register the address in config/coin.php. Fee discounts and dividend payouts are handled off-chain in the user_wallet table.

Q: What’s the difference between the 锁仓理财 module and the 微盘理财 micro-staking panel?

A: 锁仓理财 is fixed-term (7/30/90 days) with locked principal — funds are unavailable until expiry. 微盘理财 is flexible daily-settlement staking where you can redeem anytime, but the APR is typically 60% lower. They’re two separate tables and don’t share balance pools.

Original Reference

Original title: 全新区块链交易所系统/币币期权交易/IEO/锁仓理财-系统演示站

Original excerpt:

admin
交易所
微盘理财
全新区块链交易所系统/币币期权交易/IEO/锁仓理财
woocloud交易所二开的，新增了很多功能
最重要的就是新增pc端，也支持平台币
分享到：

Original screenshots:

Disclaimer

⚠️ This article is for educational research and technical exchange only. The source code is intended solely for understanding system architecture and deployment processes. Do not use it for illegal purposes. Any commercial operation is unrelated to the author.