What this page explains
This page explains the security controls currently implemented by FeilongEX and their boundaries. This is an explanation of how it operates, not an independent security audit, certification, or guarantee of no vulnerabilities, nor does it guarantee that mistaken transfers can always be recovered.
These security controls only verify orders, addresses, transactions, and network data; they do not perform customer identity verification and do not change the 100% No KYC guarantee made by the exclusive contract for every exchange. FeilongEX bears contractual responsibility for this commitment and exchange service performance.
Responsibilities of both parties and existing limitations
This table can scroll horizontally.
| Item | FeilongEX is currently responsible for | Users must be responsible for | Current limitations |
|---|---|---|---|
| Quote and order conditions | Generate and save a sealed quote on the server, and re-verify the price and current conditions before creation. | Verify the send and receive assets, networks, amounts, rate mode, and validity period. | A quote is not a final receipt guarantee; market, network, and real-time service status can change. |
| Create order | Bind the quote to the current session, lock the creation status; when the result is uncertain, provide recovery of the original request. | When encountering "result pending confirmation," restore the original request; do not submit again or pay to an old address. | After a network interruption, verification may need to continue; the page will not assume that creation definitely succeeded or failed. |
| Address, network, and Memo | Check the address format, network, and Memo support; if required configuration is missing, block creation before displaying deposit information. | Confirm that you control the address, and confirm that the wallet or platform supports the selected network, token contract, and Memo / Tag. | A format check cannot prove address ownership, nor can it guarantee deposit by the receiving platform. |
| Payment | Display the send asset, network, amount, deposit address, Memo, and deadline in the order; creating an order itself does not deduct funds. | Pay the full amount as required by this order from your own wallet or platform, and bear external sending fees. | Wrong network, wrong address, missing Memo, late payment, underpayment, or duplicate payment may cause losses. |
| Order access and status | Use necessary cookies, server sessions, and attribution hashes to protect some orders, and update the order's actual processing status. | Save the order ID and transaction hash, and query on the original order page. | Some queries and fee refund operations can be performed with the order ID; noindex is not an access password. |
| Completion and payment evidence | Completion is displayed only after the order record confirms final payment; when available, deposit and outgoing transaction hashes are provided for verification. | Verify the final receiving asset, network, amount, and transaction hash. | On-chain confirmation, processing, and refund times cannot be guaranteed in advance. |
| Account, KYC, and responsibility | A dedicated contract guarantees that every order is 100% No KYC throughout, regardless of amount; no customer account is created, and no identity materials are required. | Keep the order ID, and verify the asset, network, address, amount, and deadline against the current order. | FeilongEX assumes contractual responsibility for the 100% No KYC commitment and exchange service fulfillment; order verification does not add KYC steps. |
| Fee refund | First verify that the order is complete, then verify the USDT Ethereum address and calculate the amount according to the saved basis. | Submit the correct exchange ID and a USDT ERC20 address controlled by you. | Submitting or completing the calculation does not mean payment has been made; after the address is submitted, it cannot be changed by submitting again. |
Current technical controls
- Quotes and order conditions are stored on the server, and the client cannot rewrite the rate identifier or order processing conditions stored on the server.
- Order creation uses a status lock and recovery flow. When the result is uncertain, the system saves the submitted information and prevents duplicate creation with a different address.
- Exchange, fee refund, and protected write requests check same-origin Origin, JSON type, request body size, and request frequency.
- Necessary cookies use HttpOnly, SameSite=Strict, and the site root path; in an HTTPS environment, Secure is added.
- FeilongEX's keys, credentials, and protected configuration are read from the server environment, and the customer interface does not return these secret values.
- Address checks cover the asset, network, and Memo combination. If the checking service is unavailable or necessary configuration is missing, the server will block creation before payment.
- Order records store available deposit and payment information; transaction hashes, destination addresses, networks, amounts, and confirmation status are used for order verification.
Anti-phishing checklist
- Verify the entry point.Before making the formal payment, confirm that the domain in the address bar is
feilongex.com, use HTTPS, and check letter by letter for similar letters, extra hyphens and incorrect suffixes. - Never hand over secrets.FeilongEX will not ask for private keys, seed phrases, wallet passwords, exchange passwords, remote control or wallet transfer authorization.
- Trust only the current order.Do not copy the deposit address from search snippets, guides, cached pages, social media, private messages or old orders.
- Verify all payment conditions.Also check the sending asset, network, full address, Memo / Tag, exact amount and payment deadline.
- If uncertain, stop paying.If the page indicates that the creation result is uncertain, the quote has expired or the deposit information has not been verified, restore the original creation record and do not create a second order.
- Keep the order number safe.Do not display in public comments, group chats, screenshots or indexable pages.
- Identify fee refund phishing.The application only requires the FeilongEX exchange number, the USDT Ethereum receiving address and a confirmation action; no upfront fee is required.
- Do not trust unofficial private messages.FeilongEX will not ask you via private message to submit wallet secrets, identity documents or prepay additional fees.
When something seems wrong
Stop further payments immediately, and do not try to fix it by sending duplicate transfers. Save the order number, asset, network, amount, page prompt time, and actual transaction hash, but do not save or send private keys, seed phrases, or wallet passwords.
返回 Order query 查看状态。Please check the deposit, exchange, and payment progress in the original browser used when creating the order; if you need help, please keep the order number, network, and transaction hash. FeilongEX 对订单跟踪与后续处理负责；状态或链上记录核对不会增加身份材料步骤。
Security issue reporting channels and boundaries
FeilongEX currently has not published a dedicated security email, submission form, PGP key, security.txt, bug bounty program, or response time limit. Order lookup, the fee refund form, and unofficial private messages are not FeilongEX vulnerability reporting channels.
Before official channels are published, do not send private keys, API keys, complete order information, or directly exploitable sensitive details through public comments or unofficial private messages. This page does not constitute a safe harbor commitment, nor does it authorize automated scanning, stress testing, or bypassing access controls on production services.
FAQ
Does FeilongEX request KYC identity documents?
No. Under a dedicated contract, every FeilongEX order is 100% No KYC throughout, regardless of amount, with no ID documents, selfies, facial verification, proof of address, proof of funds, or other identity materials required.
Will FeilongEX ask for private keys or "unfreeze fees" via direct message?
No. Regular exchanges and fee refunds do not require private keys, seed phrases, wallet passwords, remote control permissions, or prepaid "unfreeze fees." Any account requesting these should not be trusted.
Can I reuse the deposit address from an old order?
They should not be reused. For each payment, use only the asset, network, amount, full address, Memo / Tag, and deadline shown on the current order page; do not copy from guides, search snippets, cached pages, or old orders.
If there is a transaction hash on the sending network, does that prove the exchange is complete?
It does not prove it. A hash on the sending network can only help verify the payment stage on that chain; you also need to check the order processing status and the outgoing transfer record on the destination network.