xHunterAI

本文件提供英文版和俄文版。

Pool Rules

v1.2

下载 .md

1. Participation

The xHunter trader pool allows users to allocate funds to a pool traded by the xHunter team. To participate, sign in, fund your account, select an allocation and review its terms before confirmation. Follow the current security requirements shown for the operation.

2. Tiers and fixed accruals

TierAllocation, USDTAccrual countDaily rateAccruals over the term
Scout50 to below 5001201.2%144%
Tracker500 to below 1,0001501.3%195%
Sniper1,000 to below 5,0001801.4%252%
Shark5,000 to below 10,0001801.5%270%
Whale Hunter10,000 and above1801.6%288%

The allocation amount determines the tier. The daily rate is fixed under the tier. The percentages in the last column describe accruals only; the return of the original allocation is separate. They are not annual rates and do not assume automatic compounding.

For example, a 1,000 USDT Sniper allocation accrues 14 USDT per day over 180 payouts: 2,520 USDT in accruals and 1,000 USDT returned at the end, for a total of 3,520 USDT credited over the term and at its end, before applicable withdrawal fees.

3. Start, accruals and completion

The service determines the accrual schedule and normal principal-return due time in UTC. The payout count is the number of accruals, not a client-calculated calendar promise. The account shows an authoritative due date when available and the actual posting time separately. An unavailable date is not an estimated promise.

At normal completion, the outstanding principal of an ordinary or leader plan is returned once to the main USDT balance, separately from income. A finished status alone does not prove that a return was posted. Spending remains subject to current holds and restrictions. There is no new automatic completion or refund rule for frozen or inactive plans. Actual trading performance is distinct from the configured participant rate.

4. Balances and availability

Accounting balance, pending deposits and spendable funds are separate. A calculator or fixed rate does not prove assets held, realized trading profit or reserve funding. These rules do not assert a separately funded trading-loss or partner reserve. Existing account restrictions and incident holds remain independent of credits and principal return.

5. New allocations and additional funds

The minimum new allocation is 50. USDT Funds can be taken from the main balance, partner rewards and pool earnings, in that order.

If an allocation has not yet received its first accrual, additional funds of at least 10 USDT are added to that allocation and its accrual start moves to the following day. Once accruals have started, additional funds open a separate allocation. The confirmation screen shows the amount and applicable tier and term.

6. Funding the account

Account balances, allocations, accruals and partner rewards are recorded in USDT. The available deposit catalog shows the currently eligible networks/assets and published token minimums. A listed product route is not automatically enabled.

NetworkAssets in scope
BNB Smart Chain (BSC)Native BNB and approved Binance-Peg USDT (BEP-20, 18 decimals)
TRONNative TRX and approved Tether USDT (TRC-20, 6 decimals)
SolanaNative SOL only; no SPL USDT/USDC
BaseNative ETH and native Circle USDC; no USDbC
Polygon PoSNative POL and native Circle USDC; no WETH or bridged USDC
Arbitrum OneNative ETH and native Circle USDC; no USDC.e

Use only the exact asset, network and current usable address shown in your account. Ethereum mainnet, Bitcoin and TON deposits are outside this scope. Base and Arbitrum One are separate networks even when both use ETH or USDC. A similar address or ticker never makes networks or token contracts interchangeable. Request an address explicitly and acknowledge the displayed conditions before using it; opening a page or selecting a route does not create an address. A creation acknowledgment may still be pending and is not usable payment details.

Valid confirmed receipts accumulate for the same original beneficiary, asset and network until their saved token minimum is met. Small receipts are retained and combined, not discarded. Different senders may contribute to that same accumulation; different assets/networks cannot be combined. An accumulation keeps the minimum saved when it opened even if the current published minimum changes. With a saved minimum of 100, 10 then 90 releases all 100 once other checks pass; 110 and 90 eligible in one collection pass release 200. If 110 was credited earlier, a later 90 waits for its own top-up. There is no promised refund below the minimum.

Optional 12-hour accelerated monitoring changes checking priority. Its cancellation/expiry, a treasury sweep or a price outage does not erase receipts or accumulation. Background monitoring and confirmation processing are separate from account credit. Closed new intake does not erase existing history. Address compromise may require review and proven recovery before any manual credit; a recorded receipt alone is not spendable money.

The deposit service fee is zero. The sender pays its network sending fee; project activation/gas/consolidation costs are not deducted again from user principal. Approved USDT and native USDC use the fixed accounting policy 1 token = 1 USDT. Native BNB/TRX/SOL/ETH/POL use each receipt's original canonical inclusion-time valuation; a missing qualifying historical price leaves processing pending rather than substituting a later price.

Accounting retains full finite precision. Only USDT display and a cent-input Max truncate downward to two decimals; fractional cents remain in accounting. Thus 100.129 is displayed as 100.12, while 0.006 + 0.006 remains 0.012 and displays as 0.01. Pending token quantities, account balances and spendable funds are separate. Debt and independent holds may make a posted credit unavailable to spend.

Incorrect-network, unsupported-asset or inconsistent-ownership transfers are not automatically credited. Contact support with the hash if you sent an incorrect transfer; recovery or credit is not guaranteed.

7. Withdrawals

An external withdrawal is separate from a deposit or principal return. Use only the withdrawal network and current destination requirements shown by the enabled withdrawal flow. Expanded deposit routes do not add withdrawal networks. If withdrawals are unavailable, no request can be submitted through that screen.

The existing request minimum is 10 USDT, the service commission is 2% for USDT on TRON/TRC-20 and 0% for USDT on BNB Smart Chain/BEP-20, and no more than one request per 24 hours is permitted. Existing authorization, account restrictions and exact spendable-funds checks remain in force. The service validates the exact amount; a displayed rounded balance does not authorize a larger request.

Review the full network, destination address, exact request, commission and net amount before confirming. Processing is manual; the history records the status and any recorded transaction hash. Receipt by an external wallet is separate from request acceptance. Maintenance, restrictions and blockchain conditions can delay processing. After broadcast, xHunter cannot reverse a blockchain transfer.

8. Restrictions and retained records

Current account, transaction and incident restrictions govern available actions. Receipts, original valuations, financial history and outstanding principal are retained. A restriction does not by itself prove a completed credit, principal return or external withdrawal. These rules do not create an automatic catch-up, forced completion or new loss-allocation policy.

9. Availability and changes

Allocations and withdrawals may be briefly unavailable during daily accrual processing, maintenance or an operational pause. Pool parameters and access limits can change. Review the displayed conditions before confirming an action.

Pool participation also affects analytics access. Available limits are shown in the account. When a level decreases, excess wallet tracking and alert rules are paused rather than deleted.

10. Questions

Contact [email protected] with the username, allocation or transaction ID, and blockchain hash where relevant.