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
| Item | Detail |
| Contract reviewed | AurumAgents.sol (257 lines, Solidity 0.8.38) |
| Source SHA-256 | 4fa07769934822e5414ac81a8e2e8e19f9187e47d9a315a9547a0d33d9478758 |
| Deployed address | 0x16dE59897fDeE7F34377C2302dC4e9FDb12168C2 |
| Chain | BNB Smart Chain Mainnet (chain 56) |
| Source verification | Verified on BscScan (bscscan.com/address/0x16dE…68C2) |
| Dependencies | OpenZeppelin Contracts: ERC721, ERC721Enumerable, Ownable, ReentrancyGuard, Pausable, Strings |
| Collection | 5,555 ERC-721 NFTs: 1,111 free (1 per wallet) + 4,444 paid at 0.001 BNB (max 10 paid per wallet, 11 combined) |
| Owner | 2-of-3 multisig Safe 0x25C2f43977d4eb35C4aB22164e679E89eed162CA (verified on-chain) |
| Review date | 21 November 2026 |
| Reviewer | Internal review by the AURUM AGENTS team (AI-assisted), plus automated analysis below |
2. Methodology
- Manual code review — line-by-line read of AurumAgents.sol, checking minting logic, access control, payment handling, supply accounting, pausing, metadata and ownership.
- Static analysis — Slither 0.11.6 with solc 0.8.38 (optimizer on, 200 runs), run against the contract and its OpenZeppelin dependencies.
- Live on-chain state read — the deployed contract's public views were read from BNB Smart Chain at the time of review (see §5).
3. Findings summary
| Severity | Count (project code) |
| Critical | 0 |
| High | 0 |
| Medium | 0 |
| Low | 0 |
| Informational | 3 |
| Design notes | 4 (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
| Finding | Assessment |
| 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 code | False 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
- Reentrancy: freeMint, paidMint and withdraw are all nonReentrant; state is written before any external call (_safeMint happens after counters and mappings are updated), following checks-effects-interactions.
- Access control: pause, unpause, setBaseURI, freezeBaseURI and withdraw are onlyOwner; the owner is a 2-of-3 multisig, so no single key can act alone.
- Supply accounting: free and paid mints use separate counters (freeMinted / paidMinted) with separate caps; per-wallet limits (1 free, max 10 paid) are enforced on-chain; token IDs are sequential from 1 and cannot exceed MAX_SUPPLY (5,555).
- Payment handling: paidMint requires exact payment (msg.value == qty * 0.001 BNB); over- and underpayment both revert. There is no way to mint paid NFTs without paying.
- Integer safety: Solidity 0.8.38 checked arithmetic throughout; there are no unchecked blocks.
- No hidden minting: there is no owner mint function and no hidden minting privilege. The owner can only pause/unpause, set (and permanently freeze) the base URI, withdraw accumulated BNB, and transfer ownership.
- Metadata: tokenURI returns baseURI + tokenId + ".json" and reverts for tokens that do not exist.
4.3 Design notes (not vulnerabilities — properties of the design)
- Free mint has no agent or allowlist check. freeMint() is open to any wallet (one per wallet, while free supply lasts). Any “agent-only” claim refers to off-chain processes, not on-chain enforcement. This is the contract's actual behaviour and is disclosed here plainly.
- Base URI is not frozen. At the time of review baseURIFrozen is false, so the owner (multisig) can still change the metadata location. freezeBaseURI() is a one-way action available to the owner.
- Withdraw sends the whole balance to the owner. withdraw() transfers the contract's entire BNB balance to the owner (the multisig) in one call, by design. There is no split, timelock or withdrawal limit.
- No timelock on owner actions. Pause, base-URI changes and withdrawals take effect as soon as the multisig executes them; there is no delay window for users to react.
5. Deployed state (verified live, 21 November 2026)
| Field | Value |
| Owner | 0x25C2f43977d4eb35C4aB22164e679E89eed162CA (2-of-3 multisig Safe) |
| Paused | false (minting open) |
| Free minted | 68 of 1,111 |
| Paid minted | 0 of 4,444 |
| Total minted | 68 of 5,555 |
| Base URI frozen | false |
| Base URI | https://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:
- Freeze the base URI (freezeBaseURI()) once the metadata is final, so token artwork can no longer change.
- Obtain an independent third-party audit before making any public claim that the project is “audited”. This document does not support such a claim.
- Keep the multisig as owner; do not transfer ownership to a single-key wallet.