Release Notes

This page summarizes published Epusdt releases using the repository's actual GitHub releases, tags, release notes, and compare diffs.

Scope and Source Rules

• Primary source: GitHub Releases in GMWalletApp/epusdt
• Supplementary source: tag compare diffs and merged commit messages
• This page avoids inventing features that are not visible in release or code history

v2.0.0

• Release tag: v2.0.0
• Published at: 2026-07-23T06:04:47Z
• Official release note: Breaking change for GMPay integrations: GMPay signatures changed from MD5 to HMAC-SHA256
• Full changelog: https://github.com/GMWalletApp/epusdt/compare/v1.0.10...v2.0.0

User-visible changes

• Breaking GMPay signature change: GMPay request and callback signatures now use HMAC-SHA256 with the merchant secret_key as the HMAC key. Existing MD5-based GMPay clients receive 401 Unauthorized until upgraded.
• EPay-compatible requests and callbacks are not affected and continue to use MD5 with sign / sign_type.
• Hosted cashier initialization data now includes server_time, allowing clients to calculate countdowns against server time instead of trusting local browser clocks.
• Added a standard-library-only Python GMPay order creation example at sdk/python/gmpay_create_order.py.
• EVM payment backfill recovery was improved so interrupted scanner windows can be recovered more reliably.

Deployment and configuration changes

• Upgrade GMPay clients before deploying v2.0.0: exclude signature, exclude empty values, sort parameters by ASCII key order, join as key=value&key=value, then calculate lowercase hex HMAC-SHA256 using secret_key.
• Rate settings now support rate.mode=fixed|auto and rate.cache_ttl_seconds between 10 and 86400 seconds. Fixed mode uses rate.forced_rate_list; auto mode fetches rate.api_url and stores a durable cache.
• Auto-rate refresh keeps previous successful coin rates when a provider response is partial, and continues serving the last durable cache when refreshes or persistence fail.

API changes

• POST /payments/gmpay/v1/order/create-transaction now verifies GMPay signature with HMAC-SHA256 instead of MD5.
• GMPay merchant callbacks must be verified with the same HMAC-SHA256 canonical-parameter rule.
• GET /pay/checkout-counter-resp/{trade_id} response data now includes server_time.
• Admin APIs add GET /admin/api/v1/settings/rate/status and POST /admin/api/v1/settings/rate/refresh for rate cache inspection and forced refresh.

Evidence used

• GitHub release v2.0.0
• PR #104 (dev merge) and PR #99 (EVM backfill recovery)
• Commits: 44d90b6 (EVM backfill recovery), f086d8b (checkout server_time), 3dc8ab0 (auto rate mode with persistent fallback cache), 58141cd (GMPay HMAC-SHA256 signatures), 2353d85 (Python GMPay SDK example)
• Files: src/middleware/check_sign.go, src/util/sign/sign.go, src/model/service/epay_return.go, src/model/response/pay_response.go, src/config/rate.go, src/controller/admin/settings_controller.go, src/route/router.go, src/task/listen_evm_backfill.go, sdk/python/gmpay_create_order.py

v1.0.10

• Release tag: v1.0.10
• Published at: 2026-07-10T13:24:42Z
• Official release note: Allow admin to mark expired on-chain orders as paid and seed rates
• Full changelog: https://github.com/GMWalletApp/epusdt/compare/v1.0.9...v1.0.10

User-visible changes

• Admin manual mark-paid can now repair expired on-chain orders after the submitted transaction hash is verified. The public cashier transaction-hash submission path still only accepts waiting orders and continues to reject expired orders and OkPay/provider orders.
• A built-in forced-rate default is seeded for CNY stablecoin conversion: cny.usdt and cny.usdc both default to 0.14705882352941177.
• Empty rate.forced_rate_list is restored to the built-in CNY stablecoin default after rate settings are updated or the setting is deleted; any non-empty custom JSON remains user-owned and is not merged or overwritten.
• rate.api_url is now optional; when provided, it still must be a public HTTP/HTTPS URL.

Deployment and configuration changes

• epctl upgrade now requires an existing /opt/epusdt/.env, so upgrade no longer creates a new config. Run install first on a fresh machine.
• Direct epctl upgrade replaces release files and restarts epusdt by default. Use --no-restart to stage files without restarting, or --prompt-restart to ask in an interactive terminal.
• Upgrade deployment keeps rollback backups for the current binary, .env.example, and systemd unit. If file deployment or restart fails, epctl attempts to restore the previous release files.

API changes

• Admin mark-paid accepts waiting and expired on-chain orders after chain transaction verification.
• POST /pay/submit-tx-hash/{trade_id} remains stricter: it only accepts waiting on-chain orders; expired orders are rejected before verification.
• Rate settings documentation now treats rate.api_url as optional and documents the default-restoration behavior for rate.forced_rate_list.

Evidence used

• GitHub release v1.0.10
• PR #97 (dev merge)
• Commits: 392240e (admin mark-paid for expired on-chain orders), d18965d (seed default forced rates for CNY stablecoins), 6589ad1 (epctl upgrade restart controls and rollback-safe deploy), 8f03599 / 5668a2a (frontend build sync)
• Files: src/controller/admin/order_controller.go, src/controller/comm/pay_controller.go, src/model/service/order_service.go, src/model/data/settings_data.go, src/model/mdb/settings.go, src/model/dao/mdb_table_init.go, src/controller/admin/settings_controller.go, epctl, wiki/EPCTL.md, wiki/EPCTL.en.md

v1.0.9

• Release tag: v1.0.9
• Published at: 2026-06-29T10:11:08Z
• Official release note: Full Changelog: https://github.com/GMWalletApp/epusdt/compare/v1.0.8...v1.0.9

User-visible changes

• EPay type selectors: EPay submit.php now accepts type=alipay or a supported type=token.network selector such as usdt.tron; valid selectors choose the payment token/network directly.
• EPay return and notify callbacks now preserve the stored request type instead of always returning alipay.
• The install flow can return the initial admin password during first-time setup, while the exposed admin API now keeps only the initial-password hash endpoint for frontend warnings.
• Added the repo-root epctl Linux binary installer/service manager plus epctl-docker-test.sh for Docker-based end-to-end validation.

Deployment and configuration changes

• epctl installs released binaries under /opt/epusdt, creates epusdt.service, keeps existing /opt/epusdt/.env on install/upgrade, and can be installed globally to /usr/local/bin/epctl.
• EPay epay.default_token and epay.default_network are ignored when a valid type=token.network selector is supplied; epay.default_currency still provides the currency fallback.
• No new environment variables are required.

API changes

• GET / POST /payments/epay/v1/order/create-transaction/submit.php now restricts non-empty type to alipay or a currently supported token.network selector.
• GET /pay/return/{trade_id} and EPay async notify payloads reuse the stored type; missing type falls back to alipay.
• GET /admin/api/v1/auth/init-password-hash remains the exposed initial-password state endpoint; the old plaintext init-password admin route is not registered in this release.

Evidence used

• GitHub release v1.0.9
• PR #92 (dev merge)
• Commits: 2dc538c (EPay type selectors), 73aef80 (restrict submit type), 15de0e6 (keep init password available), 7d09adf (return initial admin password), 1cdb1ed (epctl installer and docs)
• Files: src/route/router.go, src/controller/comm/order_controller.go, src/model/service/epay_return.go, src/install/installer.go, epctl, epctl-docker-test.sh, wiki/EPCTL.md

v1.0.8

• Release tag: v1.0.8
• Published at: 2026-06-20T06:31:53Z
• Official release note: Full Changelog: https://github.com/GMWalletApp/epusdt/compare/v1.0.7...v1.0.8

User-visible changes

• Aptos blockchain is now supported for USDT and USDC payments — the system includes token support configuration, RPC routing, and on-chain transaction scanning for Aptos Move-based assets.
• Aptos token support and RPC routing are now driven from the admin-configured chain and chain_token settings, removing hardcoded contract addresses from the scanner.
• Manual payment verification now supports Aptos transaction validation.
• README documentation was updated to list Aptos alongside other supported chains.

Deployment and configuration changes

• Aptos chain requires an RPC endpoint configured in the admin panel — the scanner will follow Aptos ledger versions and scan Move module events for token transfers.
• No new environment variables are required; Aptos chain and token configuration follows the existing admin chain/token setup flow.

API changes

• Aptos is now available as a chain option in the supported assets list and order creation endpoints.
• Admin chain and token management endpoints now support Aptos-specific configuration fields.

Evidence used

• GitHub release v1.0.8
• PR #91 (dev merge)
• Commits: de96a5d (Aptos support), 8216c91 (config-driven token support)
• Files: README.md, README.en.md, src/controller/admin/chain_token_controller.go, src/model/service/aptos_task.go, src/task/listen_aptos_scanner.go, src/util/address/move.go

v1.0.7

• Release tag: v1.0.7
• Published at: 2026-06-16T11:37:43Z
• Official release note: Full Changelog: https://github.com/GMWalletApp/epusdt/compare/v1.0.6...v1.0.7

User-visible changes

• GMPay and EPay order creation endpoints now support placeholder orders — orders can be created without requiring an immediate on-chain payment address, enabling integrations that need order IDs before the actual payment method is selected.
• Placeholder orders are converted to full on-chain orders when the customer selects a payment network in the cashier flow.
• Order workflow now supports deferred network selection, allowing merchants to create orders first and let customers choose the payment chain later.

Deployment and configuration changes

• No new environment variables are required.
• Placeholder order support is enabled by default for GMPay and EPay flows.

API changes

• POST /payments/gmpay/v1/order/create-transaction and EPay order creation endpoints now accept orders without requiring network or token parameters upfront — omitting these creates a placeholder order.
• Placeholder orders return a trade_id and cashier URL but do not include a wallet address until the customer selects a network.
• POST /pay/switch-network converts a placeholder order to a full on-chain order by assigning the selected network and generating a payment address.

Evidence used

• GitHub release v1.0.7
• PR #89 (dev merge)
• Commit: 3ab3659 (placeholder order support)
• Files: src/model/service/order_service.go, src/controller/comm/order_controller.go, src/model/mdb/orders_mdb.go, src/model/data/order_data.go, wiki/API.md

v1.0.6

• Release tag: v1.0.6
• Published at: 2026-06-11T16:51:24Z
• Official release note: Full Changelog: https://github.com/GMWalletApp/epusdt/compare/v1.0.5...v1.0.6

User-visible changes

• The system now supports TON blockchain and USDT Jetton payments, including liteclient-based transaction scanning, TON address normalization (raw/user-friendly/bounceable formats), and Jetton contract validation.
• Manual payment verification now includes TON tx verification with on-chain proof validation.
• Runtime log level can now be adjusted in the admin settings panel without restarting the server — log level changes take effect immediately across all active loggers.

Deployment and configuration changes

• TON liteclient requires a public liteserver config (mainnet or testnet); the scanner will catch up from the most recent masterchain block and follow shard chains for Jetton transfers.
• No new environment variables are required; TON chain and token configuration follows the existing RPC node and chain token setup flow.

API changes

• TON is now available as a chain option in the supported assets list and order creation endpoints.
• Admin settings API now includes log_level for runtime log adjustment (valid values: debug, info, warn, error).

Evidence used

• GitHub release v1.0.6
• PR #87 (dev merge)
• Commits: 9b397bd (TON support), 9ac9894 (runtime log level)
• Files: src/task/listen_ton.go, src/util/address/ton.go, src/model/service/ton_task.go, src/util/log/log.go, src/controller/admin/settings_controller.go

v1.0.5

• Release tag: v1.0.5
• Published at: 2026-06-09T16:25:25Z
• Official release note: Full Changelog: https://github.com/GMWalletApp/epusdt/compare/v1.0.4...v1.0.5

User-visible changes

• Admin dashboard now exposes real-time RPC node runtime statistics via a Server-Sent Events (SSE) endpoint, allowing the frontend to display live RPC call counts, success rates, and error stats without polling.
• Solana RPC task statistics now track per-node and per-operation call counts (signature scan, transaction fetch, confirmation fetch) and error events.
• EVM websocket and block scan tasks now report RPC call metrics to the in-memory stats tracker.
• README was updated with security audit information and new screenshots.

Deployment and configuration changes

• No new environment variables are required.
• The SSE endpoint is available at /api/admin/v1/rpc/stats/stream and requires admin JWT authentication.

API changes

• GET /api/admin/v1/rpc/stats/stream (SSE) returns a JSON stream of RPC node runtime stats; each event includes node ID, call counts, success counts, error counts, and last-seen timestamp.

Evidence used

• GitHub release v1.0.5
• PR #86 (dev merge)
• Commits: 08d409d (RPC stats SSE), 54b83f8 (README update), 3879853 (asset files)
• Files: src/controller/admin/dashboard_controller.go, src/model/data/rpc_runtime_stats.go, src/task/listen_sol_job.go, src/task/listen_evm_ws.go, README.md

v1.0.4

• Release tag: v1.0.4
• Published at: 2026-06-03T13:01:37Z
• Official release note: feat(www): enable RPC node create and edit actions — Full Changelog: https://github.com/GMWalletApp/epusdt/compare/v1.0.3...v1.0.4

User-visible changes

• Admin web interface now allows creating and editing RPC nodes directly in the browser — previously these actions were disabled or incomplete in the frontend.

Deployment and configuration changes

• No new environment variables or backend changes are required; this is a frontend-only update.

API changes

• No API routes were added or removed; the frontend now correctly calls existing RPC node management endpoints.

Evidence used

• GitHub release v1.0.4
• PR #85: feat(www): enable RPC node create and edit actions
• Commit: 3e85bf7 (www asset update)
• Files: src/www/assets/* (frontend bundle update)

v1.0.3

• Release tag: v1.0.3
• Published at: 2026-05-27T11:42:43Z
• Official release note: docs: update payment API integration guide — Full Changelog: https://github.com/GMWalletApp/epusdt/compare/v1.0.2...v1.0.3

User-visible changes

• Order trade IDs are now generated using cryptographically secure random bytes and encoded in URL-safe base64, replacing the previous timestamp-based format — this reduces collision risk and improves anonymity.
• RPC nodes now support a purpose field (general, manual_verify, or both), allowing operators to dedicate nodes exclusively to manual payment verification without impacting scan/WSS/health-check traffic.
• Manual payment verification now prioritizes manual_verify RPC nodes and falls back to general nodes if no dedicated nodes are available, distributing verification load separately from scanning workload.
• Cashier payment page now allows users to manually submit a transaction hash for verification — submitted hashes are validated on-chain before the order is marked as paid.
• Dashboard trend aggregation queries now use database-dialect-specific SQL (MySQL/PostgreSQL/SQLite) to ensure correct date truncation across all supported databases.
• Payment callback and rate API URLs are now validated to reject private IP ranges (RFC 1918), preventing SSRF attacks via user-controlled callback URLs.
• Payment API integration guide in the repository README was updated with clearer examples and endpoint descriptions.

Deployment and configuration changes

• No new environment variables are required.
• Operators can now tag RPC nodes with purpose: manual_verify in the admin panel to isolate verification traffic from scanning traffic.

API changes

• POST /api/admin/v1/order/update-trade-status and POST /payments/gmpay/v1/pay/submit-hash accept a tx_hash parameter for manual hash submission; the hash is validated on-chain before status change.
• RPC node creation and update endpoints now accept a purpose field (general, manual_verify, both); default is general.

Evidence used

• GitHub release v1.0.3
• PR #81 (dev merge)
• Commits: c69b0d6 (RPC purpose isolation), 13c81ee (crypto-random trade IDs), fca75a9 (cashier hash submission), b70995f (dashboard SQL dialect fix), 0d97237 (README update), 7fcb7b3 (payment API doc)
• Files: src/model/mdb/rpc_node.go, src/model/data/rpc_node_data.go, src/controller/admin/rpc_controller.go, src/model/service/manual_payment_verify.go, src/model/mdb/orders_mdb.go, src/model/data/order_data_stats.go, src/controller/comm/pay_controller.go, README.md

v1.0.2

• Release tag: v1.0.2
• Published at: 2026-05-22T15:16:34Z
• Official release note: Full Changelog: https://github.com/GMWalletApp/epusdt/compare/v1.0.1...v1.0.2

User-visible changes

• Admin API requests now accept a bare JWT token in the Authorization header (without the Bearer prefix), in addition to the standard Bearer <token> form — clients that send a raw token no longer receive authentication errors.
• EVM ERC20 transfer scanning now skips transfers that arrived before the order was created, eliminating false-positive payment matches from stale blockchain events.
• OkPay payment success notifications are now sent correctly after an order is fulfilled via the OkPay path.
• Solana signature processing now retries on transient errors — a signature is only marked as processed once order matching and payment handling fully succeed, so temporary failures no longer silently drop payments.
• Rate settings now support a multi-currency forced rate list, allowing operators to pin exchange rates for multiple currencies simultaneously instead of a single global rate.

Deployment and configuration changes

• No new environment variables are required.
• The multi-currency forced rate feature may require updating rate configuration in the admin settings panel if you previously used a single forced USDT rate.

API changes

• Admin JWT middleware now accepts both Authorization: Bearer <token> and Authorization: <token> (bare token) request forms.
• No new public routes were added or removed.

Evidence used

• GitHub release v1.0.2
• PR #80 (dev merge)
• Commits: f4ef71b3, 4b4701f5, 449d22a4, dec1b97b, 8a486116, 2a00a033
• Changes: admin JWT middleware, EVM ERC20 block listener, OkPay notification handler, Solana signature retry logic, rate settings model

v1.0.1

• Release tag: v1.0.1
• Published at: 2026-05-21T11:40:39Z
• Official release note: feat: expose build version in public config — Full Changelog: https://github.com/GMWalletApp/epusdt/compare/v1.0.0...v1.0.1

User-visible changes

• GET /payments/gmpay/v1/config response now includes a version field exposing the running server build version (e.g. "version": "v1.0.1").
• Soft-deleted settings records are now restored on upsert instead of being silently left deleted, ensuring configuration changes take effect correctly after a prior delete.

Deployment and configuration changes

• Docker image publishing is now restricted to v* tag pushes; non-version-tagged builds no longer publish to the registry.
• Build version is injected at compile time via Docker and GoReleaser builds, so the version reported in the API response matches the release tag.

API changes

• GET /payments/gmpay/v1/config response now includes version (string), reflecting the server build version.

Evidence used

• GitHub release v1.0.1
• PR #72: feat: expose build version in public config
• Commits: 85b81e66, 09642d4c, c19a7e5f
• Files: src/model/response/support_response.go, src/controller/comm/supported_asset_controller.go, src/model/data/settings_data.go, .github/workflows/docker-alpine.yml, src/.goreleaser.yaml

v1.0.0

• Release tag: v1.0.0
• Published at: 2026-05-20T16:09:00Z
• Official release note: feat: verify manual mark-paid payments — Full Changelog: https://github.com/GMWalletApp/epusdt/compare/v0.9.7...v1.0.0

User-visible changes

• Admin manual mark-paid now performs on-chain verification before marking an order as paid — the transaction hash is validated against the chain before the status change is accepted.
• Verification checks recipient address, token contract address, payment amount, confirmation count, and transaction timestamp to prevent false positives.
• Duplicate transaction hashes are rejected — the same on-chain tx cannot be used to mark multiple orders as paid.
• Orders that were not created as on-chain orders are excluded from the manual verification path (non-on-chain order types are rejected).
• supported_assets response now includes a display_name field alongside the existing network key, making it easier for frontends to show human-readable chain names without changing the underlying network identifier.
• BSC network key was renamed from bsc to binance in the supported assets list.

Deployment and configuration changes

• No new environment variables are required.
• No changes to Docker image configuration or docker-compose setup.

API changes

• Admin mark-paid endpoint now requires a valid tx_hash parameter and performs on-chain validation before accepting the request; invalid or duplicate hashes result in an error response.
• GET /payments/gmpay/v1/config supported assets entries now include display_name.
• BSC network value in supported assets changed from bsc to binance.

Evidence used

• GitHub release v1.0.0
• PR #70: feat: verify manual mark-paid payments
• Commit: 049a15c
• Files: src/controller/admin/order_controller.go, src/model/service/manual_payment_verify.go, src/model/response/support_response.go, src/controller/comm/supported_asset_controller.go

v0.9.7

• Release tag: v0.9.7
• Published at: 2026-05-13T09:01:26Z
• Official release note: Full Changelog: https://github.com/GMWalletApp/epusdt/compare/v0.9.6...v0.9.7

User-visible changes

• README.zh-CN.md was removed; README.md is now the sole main readme, consolidating documentation into a single entry point.
• Frontend admin assets (service worker precache manifest and all bundled JS chunks) were rebuilt with updated content hashes, resolving stale-cache issues for users who had previously loaded the admin panel.

Deployment and configuration changes

• No new environment variables were introduced.
• No runtime behavior changes — this is a frontend asset refresh and documentation cleanup only.

API changes

• No API routes were added, removed, or modified.

Evidence used

• GitHub release v0.9.7
• Compare diff v0.9.6...v0.9.7
• Commits 52b171b, 4a69b7c, b0093c4, 864eb59
• Files: README.md, README.zh-CN.md, src/www/sw.js, src/www/index.html, src/www/assets/*

v0.9.6

• Release tag: v0.9.6
• Published at: 2026-05-11T10:09:43Z
• Official release note: Full Changelog: https://github.com/GMWalletApp/epusdt/compare/v0.9.5...v0.9.6

User-visible changes

• First-run bootstrap now prints the initial admin credentials to the console, making the first login discoverable without needing to inspect the database.
• Admin appearance settings now support background_color and background_image_url fields for customizing the payment page backdrop.
• Payment amount precision is now configurable — operators can set how many decimal places are applied when generating payment amounts.
• TRON chain token resolution is now dynamic in the block listener, removing the need to hard-code token contract addresses at startup.
• README.md is now the Simplified Chinese main readme; a separate README.en.md exists for English readers. README.zh-CN.md was removed in a follow-up commit (4a69b7c8).
• The plugins/ directory and bundled dujiaoka plugin example were removed from the repository.

Deployment and configuration changes

• No new environment variable is required.
• The README restructuring is documentation-only and does not affect runtime behavior.

API changes

• GET /payments/gmpay/v1/config response now includes background_color and background_image_url fields from appearance settings.
• GET /payments/gmpay/v1/config response now includes payment_amount_precision from payment settings.
• No routes were added or removed.

Evidence used

• GitHub release v0.9.6
• Compare diff v0.9.5...v0.9.6
• Commits 1a35cab, 2d546e3, a8a3b86, 3e0be9b, 7c9e3e1, 84972ea, 1c805ed, 8d2ddbd, 07d1d83, 7a905ba, 4dc1ba8, 4a69b7c
• Files: src/bootstrap/bootstrap.go, src/controller/admin/settings_controller.go, src/model/data/settings_data.go, src/model/mdb/settings.go, src/task/listen_trc20_block.go

v0.9.5

• Release tag: v0.9.5
• Published at: 2026-05-09T13:51:58Z
• Official release note: Full Changelog: https://github.com/GMWalletApp/epusdt/compare/v0.9.4...v0.9.5

User-visible changes

• Hosted checkout now includes an okpay payment-switch path alongside the existing on-chain network selection flow.
• The payment flow can now hand back a payment_url in checkout responses, so third-party payment hops such as OkPay child orders have an explicit redirect target instead of relying only on a local cashier address display.
• Public config responses now expose site-facing cashier metadata such as name, logo URL, website title, and support link, making frontend branding/config rendering less hard-coded.

Deployment and configuration changes

• The example environment file removed the old PostgreSQL and MySQL config blocks; current published config guidance now reflects SQLite-focused runtime defaults instead of suggesting those database backends are still part of the normal setup path.
• Dockerfile cleanup removed redundant static copy steps that no longer match the active frontend delivery path.
• README housekeeping also refreshed logo/disclaimer content, but those are secondary to the runtime/payment changes above.

API changes

• Public GMPay frontend config now comes from GET /payments/gmpay/v1/config instead of the older standalone supported-assets lookup.
• GET /payments/gmpay/v1/config returns supported_assets together with site branding, EPay defaults, and OkPay public config fields.
• Added OkPay callback entry: POST /payments/okpay/v1/notify.
• POST /pay/switch-network now documents/accepts network=okpay in addition to on-chain network values.
• Checkout response payloads now include payment_url.

Evidence used

• GitHub release v0.9.5
• Compare diff v0.9.4...v0.9.5
• Commits 377176a, 3623a54, 51ad344, ff157c3, 1a35cab, 2d546e3
• Code paths including src/route/router.go, src/controller/comm/supported_asset_controller.go, src/model/response/order_response.go, src/model/response/support_response.go, src/.env.example

v0.9.4

• Release tag: v0.9.4
• Published at: 2026-04-28T16:37:20Z
• Official release note: Full Changelog: https://github.com/GMWalletApp/epusdt/compare/v0.9.3...v0.9.4

User-visible changes

• TRON payment scanning is back on a block-based listener path in current source history, so the temporary revert of the newer TRON flow is no longer the effective upstream state.
• Follow-up payment-processing fixes adjusted order notification behavior after successful payment handling.
• Hosted checkout entry now redirects into the SPA cashier flow instead of rendering a dedicated server-side HTML template directly from /pay/checkout-counter/:trade_id.

Deployment and configuration changes

• The hosted checkout flow now relies on the SPA-based www/ delivery path instead of the older dedicated static/ checkout asset path.
• The Docker image was later cleaned up to remove redundant static copy steps that no longer match the active SPA checkout delivery path.

API changes

• GET /pay/checkout-counter/:trade_id now behaves as a redirect entry for the cashier SPA.
• Current source exposes GET /pay/checkout-counter-resp/:trade_id as the JSON response endpoint used by the new SPA checkout flow.
• No new merchant signature field or callback contract was introduced in this release.

Evidence used

• GitHub release v0.9.4
• Compare diff v0.9.3...v0.9.4
• Commits 9e885d8, de9c45a, 96ea748, 51a2acc, d17d212, 9c533a7, ff68279
• Upstream issue #55 about missing checkout files in Docker deployments

v0.9.3

• Release tag: v0.9.3
• Published at: 2026-04-25T10:50:34Z
• Official release note: Full Changelog: https://github.com/GMWalletApp/epusdt/compare/v0.9.2...v0.9.3

User-visible changes

• Fixed the root route after installation so GET / consistently serves the SPA instead of being intercepted by the backend root handler.
• Install mode still redirects the root path to /install, so first-time setup flow remains intact.

Deployment and configuration changes

• No new public environment variable or deployment flag was published for this release.
• The main runtime route behavior was adjusted so installed instances land on the web app more reliably.

API changes

• No new public API route was introduced in this release.
• Root backend routing changed from a catch-all Any("/") style handler to a POST("/") backend handler, leaving normal browser GET / traffic to the SPA.

Evidence used

• GitHub release v0.9.3
• Compare diff v0.9.2...v0.9.3
• Commits including 95879e3, merge tag 67263da

v0.9.2

• Release tag: v0.9.2
• Published at: 2026-04-24T16:14:34Z
• Official release note: Full Changelog: https://github.com/GMWalletApp/epusdt/compare/v0.9.1...v0.9.2

User-visible changes

• Admin rate settings now allow configuring a forced USDT rate.
• Docker deployment examples remain aligned with the current gmwallet/epusdt:latest image reference.

Deployment and configuration changes

• No new public environment variable was explicitly published in the release note.
• Existing Docker upgrade examples continue to use gmwallet/epusdt:latest.

API changes

• No new public API route was visible in the release note or compare diff for this release.

Evidence used

• GitHub release v0.9.2
• Compare diff v0.9.1...v0.9.2
• Commits including dd1bf70, 143bc84

v0.9.1

• Release tag: v0.9.1
• Published at: 2026-04-22T18:29:39Z

User-visible changes

• Built-in install wizard: first run without a usable config file now launches a web-based setup flow instead of failing. The current form focuses on app_name, app_uri, bind address/port, runtime path, log path, order expiration, and callback retry settings.
• Docker image now supports direct pull with docker pull gmwallet/epusdt:latest; no .env mount needed for initial deployment.

Deployment and configuration changes

• The install wizard writes .env automatically on first submit; subsequent restarts skip the wizard and boot normally.
• docker-compose.yaml volume mount for .env is now optional — omit it for a clean wizard-based first run.

API changes

• No new public API route in this release.

v0.9.0

• Release tag: v0.9.0
• Published at: 2026-04-21T20:23:33Z
• Official release note: Full Changelog: https://github.com/GMWalletApp/epusdt/compare/v0.0.8...v0.9.0

User-visible changes

• Added a full admin panel for managing API keys, chains, chain tokens, wallets, orders, RPC nodes, settings, notifications, and dashboard statistics
• Multi-chain support was expanded further, including broader EVM listener coverage and admin-facing chain/token management flows
• Telegram notification channels were added and later synchronized with settings updates
• First-run installation flow was introduced to simplify initial setup

Deployment and configuration changes

• .env.example changed the install flag default to enabled for first-run setup flow
• The runtime now includes RPC node health checks with automatic failover support
• Built admin static assets were added to the server runtime
• New persistence models were introduced for admin users, API keys, chains, chain tokens, RPC nodes, settings, and notification channels

API changes

• Added a full admin REST API surface covering auth, API keys, chains, chain tokens, wallets, orders, RPC nodes, settings, dashboard statistics, and notifications
• Added JWT-based admin authentication and API-key authentication middleware
• Payment, supported-asset, wallet, and order-related response/request structures were expanded alongside the admin workstream

Evidence used

• GitHub release v0.9.0
• Compare diff v0.0.8...v0.9.0
• Commits including 6bb47d4, 5edc9dc, b499bc0, 6ea5637, 9163943

v0.0.8

• Release tag: v0.0.8
• Published at: 2026-04-15T10:44:56Z
• Official release note: - Enable polygon,plasma supports

User-visible changes

• Added polygon and plasma network support
• Payment page network selection behavior was adjusted
• EVM wallet address storage logic was corrected

Deployment and configuration changes

• No new environment variables were visible in the release note or compare diff

API changes

• No new public API route was clearly introduced in the official release note
• Supported-network related behavior continues from the v0.0.7 workstream

Evidence used

• GitHub release v0.0.8
• Compare diff v0.0.7...v0.0.8
• Commits including f7c5f67, 097c716

v0.0.7

• Release tag: v0.0.7
• Published at: 2026-04-15T06:00:55Z
• Official release note: suport bsc, plasma, polygon...... + support epay submit form params + Dev payment

User-visible changes

• Added support for bsc, polygon, and plasma
• EPay-compatible submit-form parameters were added for broader integration compatibility
• Telegram interaction and payment-related handling were updated in the payment workstream

Deployment and configuration changes

• New supported-network work added multiple EVM listening paths in source history
• No clearly documented new .env variable was published in the official release note body

API changes

• Added supported-chain / supported-asset related API work in source history
• Router logic was updated to support both GET and POST forms for EPay-compatible submission flow

Evidence used

• GitHub release v0.0.7
• Compare diff v0.0.6...v0.0.7
• Commits including 9c003fb, 8cd816c, 786c5e8, 70f8ed4

v0.0.6

• Release tag: v0.0.6
• Published at: 2026-04-12T20:06:08Z
• Official release note: compare v0.0.5...v0.0.6

User-visible changes

• Hosted checkout UI was redesigned into a two-step payment flow
• Payment route switching was added for multi-network checkout selection
• Solana payment scanning now supports USDT and USDC
• Ethereum ERC-20 payment scanning was added for USDT and USDC
• Telegram payment notifications now include network information
• Telegram wallet validation was improved for multi-network addresses

Deployment and configuration changes

• Added solana_rpc_url
• Added ethereum_ws_url
• Added epay_pid
• Added epay_key
• Order locking and matching now include network in the runtime flow

API changes

• Added wallet management endpoints under /payments/gmpay/v1/wallet/*
• Added POST /pay/switch-network
• Added EPay-compatible route GET /payments/epay/v1/order/create-transaction/submit.php
• Checkout response now includes is_selected
• Create-order flow accepts optional name and payment_type
• Current source uses lowercase network identifiers such as tron, solana, and ethereum

Evidence used

• GitHub release v0.0.6
• Compare diff v0.0.5...v0.0.6
• Commits including 3f071e6, 32ca778, 5e4d5df

v0.0.5

• Release tag: v0.0.5
• Published at: 2026-04-03T17:05:30Z
• Official release note: test: fix macOS path assertion and wallet address unique index

User-visible changes

• No major end-user feature was described in the official release note

Deployment and configuration changes

• No new deployment variables were visible from the official release note

API changes

• Wallet address unique index behavior was adjusted in code history

Evidence used

• GitHub release v0.0.5
• Compare diff v0.0.4...v0.0.5

v0.0.4

• Release tag: v0.0.4
• Release name: New UI Update
• Published at: 2026-04-03T16:05:23Z
• Official release note: feat: change payment ui

User-visible changes

• Payment UI was updated

Deployment and configuration changes

• No deployment-facing changes were stated in the release note

API changes

• No API-facing changes were stated in the release note

Evidence used

• GitHub release v0.0.4
• Official release note body

Notes for Maintainers

For future releases, the most useful release format is:

1. User-visible changes
2. Deployment or config changes
3. API or schema changes
4. Upgrade notes or breaking changes