Skip to content

feat(sn60): evidence-first DeepSeek depth miner (jimcody1995-20260718-01)#161

Closed
jimcody1995 wants to merge 1 commit into
Autovara:mainfrom
jimcody1995:submission/jimcody1995-20260718-01
Closed

feat(sn60): evidence-first DeepSeek depth miner (jimcody1995-20260718-01)#161
jimcody1995 wants to merge 1 commit into
Autovara:mainfrom
jimcody1995:submission/jimcody1995-20260718-01

Conversation

@jimcody1995

@jimcody1995 jimcody1995 commented Jul 19, 2026

Copy link
Copy Markdown
Contributor

Summary

  • Challenger for current king bohdansolovie / PR feat(sn60): DeepSeek depth-audit miner (bohdansolovie-20260717-01) #156 (deepseek-ai/DeepSeek-V3.2-TEE, 6 TP / ~9% detection).
  • Pipeline: static risk-rank → map triage → single-file deep audits (value / auth / oracle lenses) → verify pass.
  • No structural-probe findings (king emitted many FPs at ~3.5% precision). All findings are LLM-justified.
  • Languages: Solidity, Vyper, Cairo, Rust. Phala TEE timings + Chutes-sealed key.

Why this should beat the field

  • Deeper whole-contract context per call vs multi-file dumps.
  • Verify pass filters unsupported candidates before scoring.
  • Caps emitted findings to protect precision while maximizing true positives.

Bundle

agent.py · agent_manifest.json · submission.json · sealed_inference_key

Test plan

  • Intake screening → kata:pending
  • Round scores vs king + open challengers
  • Strictly beats on projects passed / true positives

…-01)

Beat king PR Autovara#156 with triage + single-file deep audits + verify pass.
No structural probe findings (precision), DeepSeek-V3.2-TEE, Sol/Vy/Cairo/Rust.

Co-authored-by: Cursor <cursoragent@cursor.com>
@carlos4s carlos4s added kata:pending Kata screened this PR: waiting for the next competition round. kata:executing Kata is scoring this challenger in the current round. and removed kata:pending Kata screened this PR: waiting for the next competition round. kata:executing Kata is scoring this challenger in the current round. labels Jul 19, 2026
@carlos4s

Copy link
Copy Markdown
Member

I closed this PR because it failed the round-start execution screener.

Your PR passed intake earlier, but before scoring I run the candidate once on a real benchmark project to make sure it can execute and return valid report JSON.

Screener project: code4rena_loopfi_2025_02

Reason:

  • SN60 screening execution did not complete successfully: sealed-room run rejected: room run failed: Remote end closed connection without response
  • SN60 screening report must be a JSON object.

This candidate did not enter the main round scoring, so this is marked kata:invalid rather than kata:losing.

@carlos4s carlos4s added the kata:invalid Kata rejected this PR before valid evaluation. label Jul 19, 2026
@carlos4s carlos4s closed this Jul 19, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

kata:invalid Kata rejected this PR before valid evaluation.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants