Repaint and Future-Leak Checklist
Detect common Pine risks: request.security() lookahead issues, realtime vs historical behavior, negative offsets, calc_on_every_tick, bar-state traps, and logic that cannot be reproduced live.
Pine Audit Lab
PineProof audits Pine strategies and TradingView reports for repainting risk, overfit parameters, walk-forward fragility, Monte Carlo drawdown, and unrealistic backtest assumptions. Upload a strategy report. Get a shareable audit PDF.
Audit Your StrategyDetect common Pine risks: request.security() lookahead issues, realtime vs historical behavior, negative offsets, calc_on_every_tick, bar-state traps, and logic that cannot be reproduced live.
Split performance across regimes, symbols, and time windows. Flag strategies that rely on one period, one parameter cluster, or one unusually lucky market condition.
Every audit ends with a clean PDF: overfit score, repaint risk, drawdown distribution, and notes about what would break the backtest.
Recent public audits · 最近公开报告
Pulled from existing storage/pa_* audit folders.
Public audit
Public audit
Public audit
Run the audit
Required CSV columns: entry_time, exit_time, pnl. Common TradingView aliases are accepted. Pine code unlocks the static repaint and future-leak scan.
Pricing
Single audit: $29 per strategy report.
Creator pack: $79 for 5 audits and shareable PDFs.
Unlimited beta: $19/month for unlimited reports while in beta.
Pro creator: $49/month for private audit history, PDF branding, and before/after comparisons.
Sample audit embed
Public pages are designed to be linked, screenshotted, and shared.
No. PineProof evaluates robustness and disclosure quality. It does not recommend trades, assets, position sizes, or live deployment.
The MVP accepts a TradingView strategy report CSV. Pine code is optional for deeper repaint and future-leak checks.
No. It can only identify fragile assumptions, backtest risk, and areas that need more testing.
Yes, but only if they do not edit the score or remove risk notes. A public verification link should come later.
Single-audit files should be deleted after report generation unless the user opts into saved history. Private code should not be used for public examples.
No. PineProof is independent and should not use TradingView branding beyond descriptive references.