EXTERNAL CONTROL POSSIBLE: Technical Audit 0x20deed9e6f40de5ce0100d957d299549d9cf1691: Debug Protocol Not Finalized
ADMIN
Terminal :: Triada Ethereum Auditor v2.5
AUDIT_ID: TRD-49E9F33494BE
|
Infrastructure Scan
ADDRESS: 0x20deed9e6f40de5ce0100d957d299549d9cf1691
DEPLOYED: 2026-05-13 06:39:35
LAST_TX: 2026-05-13 10:27:59
|
Compliance Status
STATUS:
OPEN_DEBUG_PORT EXPOSURE: Debug_Mode_Persistence
VISIBILITY: DEBUG_INTERFACE_EXPOSED
|
|
◈ 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] Latency: 33ms. Protocol: JSON-RPC 2.0. [FETCH] Loading bytecode into isolated sandbox… [SCAN] Mapping internal logic flow and branching. [MEM] Snapshotting EVM state before execution… [VULN] Detecting ‘Front-running’ risks in mempool. [SIM] State change detected in slot 0x4a. [TRACE] Debug: 9c2fb6f9bd2051f8. [VALID] Security status: DEEP_CORE scan finished. [DONE] Log signature: edf6e4943645eddd1d00d26c6900f8a1e86f90be2eb106fbccb25279ea3ce73f.
|
NODE: eth-us-cluster-04
GAS_LIMIT: 21000
GAS_LIMIT: 21000
OPERATIONAL_SECURITY_SCAN_COMPLETED
0xe6f4b997cbc59a5b95e130b5ecd64193441e1e84 0x45bcaf0225144dc9c1b36c53d53378c0cb69aa1c 0xab6270d7fd38cc0dab54e5d6aef7662d934f8893 0xa432d6d9437cd477c44a29a864ca0d77192d1d02 0x0ebd97344bbc20f1b84c711ab5f50023eeac58b2 0x8af4f65ba0da3998b95082b81b228d892c02150f 0xcf1bac4df24f31efd76e40b99e1bcbe201d7dec3 0xa707abbc911e5e30b46482856fbed3101420eeb2 0x8b6edce6178594c57c25ca13208e00cf243065fe 0xc4c5e8da435599ef88eff41d957654cc2cba8501 0x848c96768bc9391b10131a928ee93d34726ba4ab 0x8e84a0800b54a906e3f53fd9204168261e5955b9 0x6746bf077c5a51696d75d8c02dc701c2ec91c07f 0xe82b73174c1e5d8af8982a6cdb806a282187acc9 0x0f76520ef5d724071bbb2b1b73d62af2753343c3 0x42da7f31dfe6f427966401915f8e485f3a9b67cd 0x05165949f128a75c74fef6e6434d56f995d2f59a 0x0579397cc1bd9fe003aaf77f18ad186d3f29a879 0xc4f74784f2181340c683d87cd4c319d0da08c463 0x864dbbcc0876ca005ca6469d5a22856bf4da0c59
Articles récents
- [SOLVED] The Provider is not connected to the requested chain. (extension)
- [SOLVED] The Provider is not connected to the requested chain. (extension)
- [SOLVED] The Provider is not connected to the requested chain. (extension)
- [SOLVED] The Provider is not connected to the requested chain. (extension)
- [SOLVED] The Provider is not connected to the requested chain. (extension)