Deposit and withdrawal policy
Operational document; financial sections do not take effect before approval and activation.
Execution status
Real deposits and withdrawals are inactive. No receiving address is published to members and no transfers are signed or broadcast. The legacy owner address directory is not a deposit gateway.
Networks and assets
The framework covers TRC20, ERC20 and BEP20 with network-separated records. Token contract, issuer, decimals and confirmations require approval per network. Binance-Peg tokens are not automatically native Tether issuance; similar names do not establish token equivalence.
Deposit evidence
A TXID or screenshot alone cannot create credit. A verified custody recipient, correct token, successful execution, canonical/finalized block and approved confirmations are required. Network, transaction and transfer-log identity prevent duplicate credit.
Withdrawal requests and authorization
Withdrawals require funded available balances, no review hold, approved eligibility and limits. Additional authorization binds network, address, amount, fee and session, expires, limits attempts and works once. Requests require review before settlement.
Fees
No fixed network fee is published because a settlement provider is not connected. Future activation must show fee asset, amount or cap and quote expiry, distinguishing service fees from gas or energy. Reserved amounts are not paid fees before execution evidence.
Delays and cancellation
Security review, reconciliation, network or provider problems may delay processing. No unapproved arrival time is guaranteed. Records show request status; pre-broadcast cancellation follows terms, while confirmed on-chain transfers may be irreversible. Complaints use ticket tracking.