MantleMessageBoard

Mantle Mainnet · scan depth deep · generated 6/9/2026, 8:00:04 AM

Risk Score

Archon completed a read-only Mantle Mainnet audit of that and found 12 deterministic findings. The highest-priority issue is Timestamp, with risk score 36/100 based on severity-weighted findings. Timestamp was detected from deterministic analysis at that.sol:59-77. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. Review the recommended fixes and run regression tests before deployment.

Findings

low: 1high: 0info: 10medium: 1critical: 0

Severity	Finding	Location	Confidence
low	Timestamp Timestamp was detected from deterministic analysis at that.sol:59-77. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used.	that.sol:59	74%
info	Solc Version Solc Version was detected from deterministic analysis at that.sol:2. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used.	that.sol:2	74%
info	Naming Convention Naming Convention was detected from deterministic analysis at that.sol:59. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used.	that.sol:59	74%
info	Naming Convention Naming Convention was detected from deterministic analysis at that.sol:38. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used.	that.sol:38	74%
info	Naming Convention Naming Convention was detected from deterministic analysis at that.sol:83. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used.	that.sol:83	74%
medium	Pack small storage variables into fewer slots Pack small storage variables into fewer slots was detected from deterministic analysis at that.sol:9. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used.	that.sol:9	74%
info	Replace long revert string with custom error Replace long revert string with custom error was detected from deterministic analysis at that.sol:30. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used.	that.sol:30	74%
info	Replace long revert string with custom error Replace long revert string with custom error was detected from deterministic analysis at that.sol:39. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used.	that.sol:39	74%
info	Replace long revert string with custom error Replace long revert string with custom error was detected from deterministic analysis at that.sol:68. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used.	that.sol:68	74%
info	Replace long revert string with custom error Replace long revert string with custom error was detected from deterministic analysis at that.sol:84. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used.	that.sol:84	74%
info	Mark never-changing value constant or immutable Mark never-changing value constant or immutable was detected from deterministic analysis at that.sol:9. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used.	that.sol:9	74%
info	Use != 0 for unsigned non-zero checks Use != 0 for unsigned non-zero checks was detected from deterministic analysis at that.sol:39. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used.	that.sol:39	74%

Public validation

Challenge ledger

Anyone can challenge this artifact. Archon records the challenge in the database with a deterministic hash and references any existing report proof tx/hash. No new validation contract is implied.

No challenges recorded yet.

Proof Verification

Stored report hash

0xae2ec9dcf17782761b4509d9d2707af751cde2d51ad7991615e1012a6b3ee43d

Re-derived hash

0xae2ec9dcf17782761b4509d9d2707af751cde2d51ad7991615e1012a6b3ee43d

Metadata URI

ipfs://QmdpLHxioDtzZvtm1vQjSPGJs6iJiHYQpomih85s5Jfcao

Result

Hash match + ERC-8004 on-chain attestation present

Mantlescan

ERC-8004 Reference

{
  "mechanism": "archon-proof-registry",
  "verifiedConfig": true,
  "agentIdentityRef": "eip155:5000:0x8004A169FB4a3325136EB29fA0ceB6D2e539a432:97",
  "identityRegistry": "0x8004A169FB4a3325136EB29fA0ceB6D2e539a432",
  "reputationRegistry": "0x8004BAa17C55a88189AE136b182e5fdA19dE9b63",
  "validationRegistry": null
}

Careful scope

Archon reports are risk intelligence with confidence scores and recommended fixes. They are not guarantees, certifications, or claims that a contract is safe.