AURUM AGENTS

Internal Security Review — Self-Assessment

Contract: 0x16dE59897fDeE7F34377C2302dC4e9FDb12168C2 · BNB Smart Chain Mainnet (chain 56)

Important — read first. This document is an internal self-assessment prepared by the AURUM AGENTS project team using automated static analysis and manual code review. It is not an independent third-party security audit and must not be described as one. No external auditor reviewed this contract. The findings below are the reviewer's own, and any party relying on this document should treat it as a self-review, not an audit certificate. AURUM AGENTS has not been audited by any third-party firm.

1. Scope

ItemDetail
Contract reviewedAurumAgents.sol (257 lines, Solidity 0.8.38)
Source SHA-2564fa07769934822e5414ac81a8e2e8e19f9187e47d9a315a9547a0d33d9478758
Deployed address0x16dE59897fDeE7F34377C2302dC4e9FDb12168C2
ChainBNB Smart Chain Mainnet (chain 56)
Source verificationVerified on BscScan (bscscan.com/address/0x16dE…68C2)
DependenciesOpenZeppelin Contracts: ERC721, ERC721Enumerable, Ownable, ReentrancyGuard, Pausable, Strings
Collection5,555 ERC-721 NFTs: 1,111 free (1 per wallet) + 4,444 paid at 0.001 BNB (max 10 paid per wallet, 11 combined)
Owner2-of-3 multisig Safe 0x25C2f43977d4eb35C4aB22164e679E89eed162CA (verified on-chain)
Review date21 November 2026
ReviewerInternal review by the AURUM AGENTS team (AI-assisted), plus automated analysis below

2. Methodology

3. Findings summary

SeverityCount (project code)
Critical0
High0
Medium0
Low0
Informational3
Design notes4 (see §4.3)

Slither reported 69 findings in total across the analysed code. 66 of them are inside the OpenZeppelin library code (audited, widely used) and are informational patterns of that library (inline assembly in its math/string helpers, unindexed event parameters, version-spread pragmas). The single High-severity flag (incorrect-exp in OpenZeppelin's Math.mulDiv) is a known Slither false positive: the bitwise XOR there is intentional in the Newton–Raphson modular-inverse computation of audited OpenZeppelin code, not an exponentiation mistake. Only 3 findings touch the project's own contract, all Informational.

4. Detailed findings

4.1 Informational findings in AurumAgents.sol

FindingAssessment
Multiple Solidity pragma versions across the dependency tree (project pins 0.8.38; OpenZeppelin uses ^0.8.20)Expected. The deployed bytecode was compiled with 0.8.38; the spread comes from library pragmas, not from the project contract.
_increaseBalance flagged as dead codeFalse positive. It is a required override for ERC721Enumerable and must stay.
Low-level call in withdraw()Standard pattern. The call is guarded by onlyOwner and nonReentrant, and its return value is checked (WithdrawFailed on failure). No issue.

4.2 Manual review — what was checked and passed

4.3 Design notes (not vulnerabilities — properties of the design)

5. Deployed state (verified live, 21 November 2026)

FieldValue
Owner0x25C2f43977d4eb35C4aB22164e679E89eed162CA (2-of-3 multisig Safe)
Pausedfalse (minting open)
Free minted68 of 1,111
Paid minted0 of 4,444
Total minted68 of 5,555
Base URI frozenfalse
Base URIhttps://aurumagents.pages.dev/metadata/

6. Conclusion & recommendations

No critical, high, medium or low severity issues were found in the project's own contract code. The contract follows standard OpenZeppelin patterns, enforces its supply and per-wallet rules on-chain, and holds no hidden minting or fund-extraction path beyond the documented owner functions (all controlled by a 2-of-3 multisig). The open items are design properties listed in §4.3, not vulnerabilities.

Recommendations: