AREXAI DOMAIN AND CONTRACT VERIFICATION DOSSIER Updated: 21 September 2026 Project: ArexAi Token symbol: ARXAI Official domain: https://arexaidata.com Canonical security page: https://arexaidata.com/security Machine-readable domain proof: https://arexaidata.com/.well-known/arexai-verification.json Network: BNB Smart Chain (chain ID 56) Official contact: info@arexai.com OFFICIAL ADDRESSES ARXAI token: 0xeaa12b3be7cdec7749b972ed5c342f4e933ccbb3 https://bscscan.com/token/0xeaa12b3be7cdec7749b972ed5c342f4e933ccbb3 Round 1 presale contract: 0x52c880e4d54a5dd3ca7dd185d44715017b25dee0 https://bscscan.com/address/0x52c880e4d54a5dd3ca7dd185d44715017b25dee0#code Payment treasury: 0xDE3DbDa5eB157bFc9a56C426C2006c0Cd4958a9e https://bscscan.com/address/0xDE3DbDa5eB157bFc9a56C426C2006c0Cd4958a9e BSC-USDT: 0x55d398326f99059fF775485246999027B3197955 ALLOWANCE AND SETTLEMENT BEHAVIOR The official purchase interface requests approval only for the exact USDT purchase amount selected by the buyer. It never requests unlimited approval. The verified Round 1 contract transfers that exact USDT amount from the calling buyer to the immutable payment treasury and transfers the corresponding ARXAI amount from its funded inventory to the same buyer in the confirmed purchase transaction. Relevant verified contract flow: usdt.safeTransferFrom(msg.sender, paymentTreasury, usdtAmount); IERC20(address(token)).safeTransfer(msg.sender, tokenAmount); SUCCESSFUL MAINNET PURCHASE EVIDENCE Transaction: 0xc0ee77c4a3df973ed576d907d2b94eabc6e3c5130814dfdc1484c912331291d2 https://bscscan.com/tx/0xc0ee77c4a3df973ed576d907d2b94eabc6e3c5130814dfdc1484c912331291d2 Block: 122623535 Receipt status: Success USDT transferred to configured treasury: 100 USDT ARXAI delivered to buyer: 10,000 ARXAI USDT allowance recorded after settlement: 0 REQUEST FOR REVIEW The official domain and the verified Round 1 presale contract belong to the same ArexAi project. We request review of both https://arexaidata.com and 0x52c880e4d54a5dd3ca7dd185d44715017b25dee0, which is currently shown as untrusted. The project does not request seed phrases or private keys and does not request unlimited token approval. Source-code verification is not presented as a security audit. The independent audit remains pending and is disclosed on the canonical security page.