重绘与未来函数检查表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 审计实验室Pine Audit Lab
PineProof 审查 Pine 策略和 TradingView 报告里的重绘风险、过拟合参数、walk-forward 脆弱性、Monte Carlo 回撤和不现实回测假设。上传策略报告,拿到可分享的审计 PDF。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
Paid plans stay in waitlist mode until Stripe is wired. Use the waitlist form below to save your tier.
$29
$19/month
$49/month
候补Waitlist
现在先登记意向。结账还没开。Interest is recorded now. Billing is not live yet.
样例审计嵌入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.