TW
Tripwire
Find contracts. Test them. Review real vulns.
Contract
0xb244abeae1a7e1e5d6da9008098bbeecec067c56 checked chain 1
Latest run: 019b3836-404b-706b-ba4c-80007448ffdc complete
Dedaub
Queue = batch runner. Audit = immediate run. Audit + LLM forces codex.
Value & Balances
$0.78
last balance 3 months ago
ETH
0.0003
WETH
0.0000
USDC
0.00
USDT
0.00
Findings Signal
2
confirmed findings
crit 0 high 2 unconfirmed 3 total 5
validated = confirmed for call sinks; sink observed for others

Proxy & Workflow

linkage
Proxy status
non-proxy
Implementation address
—
Proxies pointing here
0
Workflow
checked
attempts 1
checked 1 week ago

Latest Findings

validated = confirmed for call sinks; sink observed for others
Severity Tool Title Validated Confirmed
high detector Untrusted CALL target/value reachable yes yes
high detector ETH value transfer possible yes yes
Show unconfirmed findings
Severity Tool Title Validated Confirmed
medium detector CREATE/CREATE2 reachable no no
medium codex ETH payout path ignores CALL failure after mutating balances no —
medium codex Game/payout logic appears to use block data as manipulable randomness no —
From run 019b3836-404b-706b-ba4c-80007448ffdc confirmed 2

Codex

latest run
complete bytecode findings
Bytecode indicates a non-proxy ERC20-like contract with extra payable/game-style logic. I did not find strong proxy/delegatecall issues. The detector-reported high-severity CALL surface appears overstated: one CALL site...
Top findings
  • medium ETH payout path ignores CALL failure after mutating balances
  • medium Game/payout logic appears to use block data as manipulable randomness
View run

Code Metadata

fingerprint
Created block
1482230
Code size
2610
Codehash
0x97dc1b97baa382ab8bf3e2d7f4e049659ec5700a7a83ac29395e8cf5e5f354cc
Priority score
0.775000

Recent Runs

last 20
Run ID Status Validated Total findings Created
019b3836-404b-706b-ba4c-80007448ffdc complete crit 0 high 2 5 3 months ago