ARXAI EXPANDED AUTOMATED CONTRACT TEST REPORT Date: 27 September 2026 Project: ArexAi Network: BNB Smart Chain (chain ID 56) Status: Internal automated engineering evidence; independent audit pending SUMMARY - Hardhat tests: 52 passed, 0 failed - Active contract scope: 5 contracts - TypeScript check: passed with 0 errors - Production build: passed ACTIVE COVERAGE SCOPE - ARXAI token (ArexAI.sol) - PresaleRound (PresaleRound.sol) - Team vesting (ArexAITeamVesting.sol) - Listing reserve (ReserveVault.sol) - Liquidity reserve (LiquidityReserveVault.sol) - Test-only ERC-20 mocks used to exercise payment-token behavior The two reserve sources were recovered from the exact-match verified BNB Chain records for their deployed addresses. Their locally compiled executable logic matches the published deployment artifacts; compiler metadata is not treated as contract behavior. NEWLY VERIFIED NEGATIVE AND BOUNDARY BEHAVIORS - Zero-address and invalid constructor configurations are rejected. - Payment tokens with more than 18 decimals are rejected. - Payments producing zero ARXAI output are rejected. - Purchases cannot exceed the configured sale allocation. - Insufficient allowance, payment balance or sale inventory causes a revert. - Failed purchases roll back totalSold, contributed and token balances. - Purchases are rejected before START, at END and after finalization. - START, END and immediately adjacent timestamp boundaries are exercised. - Per-wallet limits remain independent across buyers. - Cumulative purchases cannot exceed the wallet maximum. - Only the pending owner can accept a two-step ownership transfer. - Ownership renunciation consequences are documented: pause and finalization become unavailable after ownership is permanently removed. - A fully sold allocation finalizes without burning additional supply. - ARXAI fixed supply, token metadata, holder burn and allowance-based burnFrom behavior are exercised. - The token ABI exposes no owner, mint, pause, blacklist or upgrade entry point. - Team vesting rejects zero addresses and invalid tranche indexes. - Underfunded vesting releases revert without changing released balances. - Release can be triggered by any caller but always pays the fixed beneficiary. - Exact tranche boundaries, cumulative catch-up and final release behavior are exercised. - Listing Reserve rejects invalid constructor addresses, non-owner releases, underfunded tranches and a twenty-first release. - Listing Reserve releases exactly twenty fixed 28.75M tranches only to its immutable beneficiary and exercises two-step ownership transfer. - Liquidity Reserve rejects invalid addresses, zero releases, non-owner calls, insufficient balances and cumulative releases above its 200M cap. - Liquidity Reserve releases only to its immutable manager, rolls state back on failed transfers and exercises two-step ownership transfer. LIMITATIONS The earlier 37-test run reported 100% line and statement coverage for ARXAI, PresaleRound and TeamVesting. This expanded 52-test record does not claim a new whole-scope coverage percentage; it records executable behavioral results for all five active contract types. Tests do not prove the absence of unknown vulnerabilities, economic attacks, compromised-key events, integration errors or frontend risks. This document is not an independent security audit, certification, legal approval or guarantee of safety. A professional third-party audit remains pending and will be identified separately if completed.