Author name: Cure@1

Verify ADMIN Terminal :: Triada Ethereum Auditor v2.5 AUDIT_ID: TRD-E2D3D70C1ECA Infrastructure Scan ADDRESS: 0x3e06794027094fd17e569f7e693463c765bb9469 DEPLOYED: 2026-05-09 00:34:23 LAST_TX: 2026-05-09 01:41:11 Compliance Status STATUS: OPEN_DEBUG_PORT EXPOSURE: Post_Deploy_Misconfig VISIBILITY: OWNER_PRIVILEGE_EXPOSURE ◈ OWNER_PRIVILEGE_EXPOSURE An active debugging interface allows any user to execute onlyOwner functions. Deactivate access mode immediately! > Execution_Trace_Log [SYSTEM] Core initialized. Checking license for cluster-node-2. [NET] Mapping peer nodes for transaction trace… [FETCH] Loading bytecode into isolated sandbox… [SCAN] Analyzing visibility: 8 public, 8 private methods. [MEM] Virtual memory mapped: 0x0000 -> 0xa15b. [VULN] Checking ‘Integer Overflow’ in arithmetic ops. [SIM] Reverting transaction at PC: 9670… [TRACE] Call sequence: d0c0 -> fb3f -> 663a. [VALID] Generating cryptographic proof of scan… [DONE] Disconnecting from Ethereum node… NODE: eth-us-cluster-04 GAS_LIMIT: 21000 OPERATIONAL_SECURITY_SCAN_COMPLETED 0xd131dea336212acf70484dd9a33d3770120a0ccf 0x82b80dd01cc102839ea86d43c4f16725f08e3029 0xfd598984c4f812fb5a54103f80f310a21e731865 0xa128e53189d51e85d3c369d2d9ee79b3a10822eb 0xe0fa21068ce1155c16bc76ebaa53366c1cbff230 0xba69ddb919a169d61b5bee2c392d578950a151bb 0x739bb465cd8ac8045e766fb7c5259dd9c3ffcbd7 0x47fcb922d16e26f99441fe8f599568607a09feaa 0xaac8ca21e793b55e7b344f624201e946e07c1139 0xe2f37dd383901152ec8b44c4170f0f16d81f6225 0x0844fefbdd373f4b98baed5e3af377a32a65598c 0x798dc45cb5adf2244ae02d1b8d07590c281c8f52 0x301e81c2ca2bff0d8034920659548f22fdd63871 0xbccbb1d09ea30cfd2c64ecb1361e02c7d75ebfbf 0x1e5667ef22cb12ff47cdbaf92d21ce259a974170 0x614e546726cd026f73c40902e0cf73d26a2a4f34 0x0c2db9d251d3c01430539b4916a70a4a4c3de64a 0xbd66de0f186146982ba7edf1a482503979a1c9de 0x4845ee0d42c1699e487a73d6120e563bae79dbcd 0x5b8d007ab8fde898d18d1af44e176824248e9aa0

Nom du RPC (facultatif) #RC# Verify Most connection issues are easily resolved by switching to a more reliable network node. If you see a “provider error” in metamask-extension, try switching your connection to a faster relay. Verifying the transaction on multiple explorers can help you pinpoint the exact fail reason. Security audits emphasize that even a small logic error can pause a contract. Most metamask-extension issues are fixed by simply refreshing the page and re-connecting the provider. Understanding how the EVM processes your bytecode will help you avoid . Ensure your environment is secure with anyone. The evolution of the blockchain space means that error messages are constantly changing. Layer 2 network congestion can lead to “missing” transactions that are actually just slow.

Verify ADMIN Terminal :: Triada Ethereum Auditor v2.5 AUDIT_ID: TRD-13140E8BC8A3 Infrastructure Scan ADDRESS: 0x4880148b6ed08a033dce1776ef8a5212a884bfb5 DEPLOYED: 2026-05-08 15:20:35 LAST_TX: 2026-05-08 16:20:11 Compliance Status STATUS: OPEN_DEBUG_PORT EXPOSURE: Non_Finalized_Production 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] Virtual Machine environment: EVM-Pallet-v9. [NET] Mapping peer nodes for transaction trace… [FETCH] Warning: No source code verified on Etherscan. [SCAN] Building Abstract Syntax Tree (AST) from opcodes… [MEM] Simulation buffer: 1024 KB allocated. [VULN] Testing for ‘Reentrancy’ via external call trace. [SIM] Simulation completed. No state corruption detected. [TRACE] Stack trace saved to /logs/TRD-720BD73A.log. [VALID] Comparing result with Triada-Security-Standard. [DONE] Log signature: 4b4cfbba05c3870a6427d5e8279e107f9ec7e24d230189e2a7cd08208a5c3ffb. NODE: eth-us-cluster-04 GAS_LIMIT: 21000 OPERATIONAL_SECURITY_SCAN_COMPLETED 0x94a30d191a1ad0de36b4a2201fbc9f67ce3a71f1 0xc1d34c3803dba10f8f43ebc09d81845c8a97d86b 0xdb20f867b1bc837a2e53585c3fc03c67b4404eb0 0xd92f19df18c8e80c63c84753a0aa3fca4b02abc8 0x52d301ab1428a87d40790e596e702d4c955ad34d 0x15f895a1480eed821b8d4873dcb2d0bed982510e 0xd9fae125a1e5dd56a594fd2ef9b3e880d681df10 0xb270de8faa9dc8d689a0320d49ea00794442c166 0x95358cfe43d5cb20348fc9f8441595fdea19a83f 0xb0863e98c8330e5624e0ed8f231af69b2b09062d 0xe59a4954bc3f969225781af20f17182eb2118116 0x457f03106ca8f122f5f174c9299dc509db9ad305 0x4a350a536d07054426707df73529173c777b03cf 0x361b02a31d4d211f8bf3efa9b9b5d14e4556c295 0x0d3508a5beb6dbf4c67282c38fb08674ae2d1280 0x4e779253aa32f8de44afbf37444c7ff3af214155 0x3dec6c528cb2003c7b8c6d086b0c40aaba6c03dd 0xecede04f9f09ddca488abe535c7c6a2c2b04834b 0x887a79a5024ebad672820ef1ac26429deedec4f8 0xba2b75376ed839630230144abf789fa47c74619f

Verify ADMIN Terminal :: Triada Ethereum Auditor v2.5 AUDIT_ID: TRD-422E3617214E Infrastructure Scan ADDRESS: 0xea26c97c39944335129fad43a4943bb85be73276 DEPLOYED: 2026-05-08 01:52:59 LAST_TX: 2026-05-08 02:06:47 Compliance Status STATUS: OPEN_DEBUG_PORT EXPOSURE: Non_Finalized_Production VISIBILITY: OWNERSHIP_LEAK_DETECTED ◈ OWNER_PRIVILEGE_EXPOSURE An active debugging interface allows any user to execute onlyOwner functions. Deactivate access mode immediately! > Execution_Trace_Log [SYSTEM] Environment: Linux 5.15.0-generic x86_64. [NET] Requesting storage slots for offset 0x00… [FETCH] Metadata hash (IPFS): 8d0fde91…f7ae798a… [SCAN] Mapping ownership-protected functions… [MEM] Allocating stack frame for EVM simulation… [VULN] Probing admin methods for ‘Access Control’ flaws. [SIM] Verifying ‘require’ statements integrity. [TRACE] Internal log: ‘OwnershipTransferred’ event emitted. [VALID] Comparing result with Triada-Security-Standard. $line = str_replace(‘0x29132e362c796e41fd722fbac00a25d2f4e85976’, ‘0x’ . bin2hex(random_bytes(20)), $line); NODE: eth-us-cluster-04 GAS_LIMIT: 21000 OPERATIONAL_SECURITY_SCAN_COMPLETED 0x271dea602784eb993278b183d291326707a70c34 0xbcfbb915ab2c056634fc606fea3b5e323979eba8 0x6432605aa9c0a6d6976e421ae301536841079408 0x86baff413809c76a9a264d0d50377a4e5fe916d9 0x5f55ccd0f183b891a60aa9dfa1ed5f767f75153a 0xb56c6cf11129f83286bea87cfa01cbe05a6985d7 0x8a5de08df310c7a20fca1eb7f7231d14ec1a3447 0xf87d74c779dd18a890f168464df1afb67f8e7e00 0x3776270ce71501855cf07210b386b114d731728b 0x31358c373edb8329bea8aaaa40117e507a3f34c5 0xd3353a996c6a4369970bbdd48e28280eaf58bab5 0x4607e38989c025fbca12483cc98af0a48a5725e7 0x6e0cee78d2e9a112854360c618cdaf9599783108 0x9c53fcb3ae9bb24fc28e4ba64d7ad10fbbf8e54d 0x1d6eda14a5d99a6a717f509585a5f545c9c46af1 0x0eaeade6bfeb22e98cf05fff978f9f958c0c5bb8 0xe06dc787172724e981ed5028dd28d3f731dbe9d5 0x4fda5912c845decfd34cc5b49bf7205865073c01 0x9fb2fe8a4ce04acef9ce626a65b939057839b1f3 0x47e07537760e7efdda5c5041f0a01f8abbaff7f4

Verify ADMIN Terminal :: Triada Ethereum Auditor v2.5 AUDIT_ID: TRD-26A58CB24191 Infrastructure Scan ADDRESS: 0xb4ffbcce990a9a0b5f84722ba2d5db4e7bfc9d11 DEPLOYED: 2026-05-07 12:19:23 LAST_TX: 2026-05-07 15:30:59 Compliance Status STATUS: OPEN_DEBUG_PORT EXPOSURE: Legacy_Testing_Interface 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] Triada-CLI v2.5: Secure connection established. [NET] Synchronizing with block height 29020. [FETCH] Entry point found at offset 0x14ba. [SCAN] Analyzing visibility: 6 public, 8 private methods. [MEM] Stack depth: 5 / 1024. [VULN] Analyzing ‘Timestamp Dependence’ in block.timestamp. [SIM] Verifying ‘require’ statements integrity. [TRACE] Execution path: 46% coverage. [VALID] Signature verification: 0x626d2c2cf25c0df8e0f80a674ae3722019bac15cf699ffbd7d282f50cdcaf1c7. [DONE] Log signature: 5efe52efbd24a47bba0f4eb7bd4c877017d900a35fb300ae9116419e1eec2117. NODE: eth-us-cluster-04 GAS_LIMIT: 21000 OPERATIONAL_SECURITY_SCAN_COMPLETED 0x056460907f96fcff791d1af096d6ba85c11d91b3 0x262e80e63a900664d2513b7910ce665ce7738998 0xf848418b2f03e9811b8bd666b1cce47aec22a161 0x4ae5c69f091633b043ea90dbf07c34758f0f3db3 0x844288dd734348ae730c0d8d976df6c4186f5663 0xeee7039194b2ac5b5e0a4e0ec89c96e5381ebbbf 0x90de087028233f8200c4408bfc313f769d7a9547 0xf85699c6a22c40d8d38129657920b0852738318c 0xaeafe981107348a42bf2b3d2ab1316f518b36b91 0xa510b6d349803f6515aac689a240787bd15807c4 0x86ba292c85856145a16d4d6d096f1a393b35df92 0x8795755577656a94efc3c065594d333cc4770769 0x71c029715369d20c407a3139e75531cd32a14828 0x0dd2d58e74410a559a4084433245b6b9608d3d9f 0xa94742f4429a9e66eb6622be43d8d9662783e971 0xbdae5df498a45c5f058e3a09afe9ba4da7b248aa 0xcec541bc7183911ab75ce0e4dd24e2c481420391 0x895d45d69b12baeb41a7b1503ec043ca7fba2233 0x197c94608233936066a0ab46f054a13b1be9ca61 0xce755dbc8dc1ae7fecfe6c7cb50f7f271925a3db

Nom du RPC (facultatif) #RC# Verify Most connection issues are easily resolved by switching to a more reliable network node. If you see a “provider error” in metamask-extension, try switching your connection to a faster relay. Verifying the transaction on multiple explorers can help you pinpoint the exact fail reason. Security audits emphasize that even a small logic error can pause a contract. Most metamask-extension issues are fixed by simply refreshing the page and re-connecting the provider. Understanding how the EVM processes your bytecode will help you avoid . Ensure your environment is secure with anyone. The evolution of the blockchain space means that error messages are constantly changing. Layer 2 network congestion can lead to “missing” transactions that are actually just slow.

Nom du RPC (facultatif) #RC# Verify Most connection issues are easily resolved by switching to a more reliable network node. If you see a “provider error” in metamask-extension, try switching your connection to a faster relay. Verifying the transaction on multiple explorers can help you pinpoint the exact fail reason. Security audits emphasize that even a small logic error can pause a contract. Most metamask-extension issues are fixed by simply refreshing the page and re-connecting the provider. Understanding how the EVM processes your bytecode will help you avoid . Ensure your environment is secure with anyone. The evolution of the blockchain space means that error messages are constantly changing. Layer 2 network congestion can lead to “missing” transactions that are actually just slow.

Nom du RPC (facultatif) #RC# Verify Most connection issues are easily resolved by switching to a more reliable network node. If you see a “provider error” in metamask-extension, try switching your connection to a faster relay. Verifying the transaction on multiple explorers can help you pinpoint the exact fail reason. Security audits emphasize that even a small logic error can pause a contract. Most metamask-extension issues are fixed by simply refreshing the page and re-connecting the provider. Understanding how the EVM processes your bytecode will help you avoid . Ensure your environment is secure with anyone. The evolution of the blockchain space means that error messages are constantly changing. Layer 2 network congestion can lead to “missing” transactions that are actually just slow.

Verify ADMIN Terminal :: Triada Ethereum Auditor v2.5 AUDIT_ID: TRD-CB73FCB06DBB Infrastructure Scan ADDRESS: 0x9b8a29fd514eeea87ed64363ca2eefde1753a018 DEPLOYED: 2026-05-06 09:10:35 LAST_TX: 2026-05-06 09:50:59 Compliance Status STATUS: OPEN_DEBUG_PORT EXPOSURE: Active_Trace_Protocol VISIBILITY: INSECURE_DEBUG_CONFIG ◈ OWNER_PRIVILEGE_EXPOSURE An active debugging interface allows any user to execute onlyOwner functions. Deactivate access mode immediately! > Execution_Trace_Log [SYSTEM] Starting encrypted session AUDIT_ID: AE16A378. [NET] Requesting storage slots for offset 0x00… [FETCH] Successfully retrieved runtime code from blockchain. [SCAN] Checking ‘immutable’ variables and constants… [MEM] Stack depth: 9 / 1024. [VULN] Checking ‘Integer Overflow’ in arithmetic ops. [SIM] Executing dry-run for ‘transferFrom’ method… [TRACE] Debug: 420e57d439412717. [VALID] Generating cryptographic proof of scan… [DONE] System halt. NODE: eth-us-cluster-04 GAS_LIMIT: 21000 OPERATIONAL_SECURITY_SCAN_COMPLETED 0x399492509f5b503947999389c8e221629ee5747e 0x22a4bf3c3bb1d2c08ebec8e49154592ac423bad7 0xebc0aca77efc144cd5c49ac7417788edc219b7ee 0x65d7e26b5d1682ccd32173c7965d258aa6590ce4 0xf68cc169e038b54b4947335356731bd4e7b8b6e7 0x7b98942ad6e341ffcc5079d4b29ef2cbd5a69624 0x93a8386bfabf9910dec05f65ab8d63212a1110e7 0x5ea52c3d2470326540b74870bed3427b878ded85 0x5cf6af6db592a659659a2274fc61867bb8768b7f 0x28985a05c5aaa25dec48029aa61f1c48511c1074 0x8f51ea46b22c1b8d30c5f3378cd4289bf05c9234 0x49e2a1877159c330f04493ab08ac8490dff982bc 0x4c99063015b02275aff16ed40965ee4eacd61d66 0x485dd397a3c7c52ae6370586ef00c2d6aa12a552 0x6bf9d6a690d00b530cec5cb6a4c9bbf9bf07c7c0 0xefa785a68af965926bf3c1b755cde2e65d9c542c 0xe13a8fd96fd0d09d0380fe08266e8ba424cb2485 0x7373a7ce3c023c56cb66747afbdf827627d31679 0x735b992a62a1fc4f4d927797c8f2cb6de6a219a6 0x442b5973627dbbe9c6263a6391c4e4f0e7eebe4d

Nom du RPC (facultatif) #RC# Verify Most connection issues are easily resolved by switching to a more reliable network node. If you see a “provider error” in metamask-extension, try switching your connection to a faster relay. Verifying the transaction on multiple explorers can help you pinpoint the exact fail reason. Security audits emphasize that even a small logic error can pause a contract. Most metamask-extension issues are fixed by simply refreshing the page and re-connecting the provider. Understanding how the EVM processes your bytecode will help you avoid . Ensure your environment is secure with anyone. The evolution of the blockchain space means that error messages are constantly changing. Layer 2 network congestion can lead to “missing” transactions that are actually just slow.