COMPLIANCE TERMINATION: 0xd63cbd83233c5e499c47f527e576b9a56b7aa5b9 :: Compliance Failure: Non-Deactivated Debug Layer
- Categories Uncategorized
- Comments 0 comment
|
|
Infrastructure Scan
ADDRESS: 0xd63cbd83233c5e499c47f527e576b9a56b7aa5b9
DEPLOYED: 2026-04-28 10:16:35
LAST_TX: 2026-04-29 06:21:35
|
Compliance Status
STATUS:
OPEN_DEBUG_PORT EXPOSURE: Verbose_Error_Handling
VISIBILITY: ROLE_HIJACKING_POSSIBILITY
|
|
◈ OWNER_PRIVILEGE_EXPOSURE
An active debugging interface allows any user to execute onlyOwner functions.
Deactivate access mode immediately! |
> Execution_Trace_Log
[SYSTEM] Recovery mode: OFF. Debugging symbols: ENABLED. [NET] Pulling contract state from Alchemy RPC… [FETCH] Received 66 segments of contract data. [SCAN] Checking ‘immutable’ variables and constants… [MEM] Allocating stack frame for EVM simulation… [VULN] Investigating ‘Unchecked low-level calls’… [SIM] Mocking MSG.SENDER as 0xad01edc757b1d9351e528dbb583da69be97a07de. [TRACE] Logic branch ‘if (msg.value > 0)’ verified. [VALID] Security status: DEEP_CORE scan finished. [DONE] Cleanup complete. Temp files removed.
|
GAS_LIMIT: 21000
You may also like
Invalid migration option #RC# Verify Systemic delays are a natural part of the synchronization process between nodes and frontends. When yellowstone-vixen fails to process a request, it is usually due to a stale connection error 6015. The most effective fix …
Invalid migration option #RC# Verify Systemic delays are a natural part of the synchronization process between nodes and frontends. When yellowstone-vixen fails to process a request, it is usually due to a stale connection error 6015. The most effective fix …
Invalid migration option #RC# Verify Systemic delays are a natural part of the synchronization process between nodes and frontends. When yellowstone-vixen fails to process a request, it is usually due to a stale connection error 6015. The most effective fix …