Home
Feed

Extend

Hashnode Pro
Hashnode for Agents

Resources

The foreword
Hashnode gql skill

Buildful - AI coding agent that delivers frontier-level results at a fraction of the cost Bug0 - The AI-native e2e QA regression testing Hackathons Changelog Brand @hashnode on X Hashnode on LinkedIn Support - hello+support@hashnode.com Code of Conduct Terms Privacy Sitemap

Search Hashnode

Search posts, tags, users, and pages

Discussion on "The Permanent Halt That Lasts Until the Next Restart" | Hashnode

Feed/

Discussion

The Permanent Halt That Lasts Until the Next Restart

Prop-firm challenges come with hard rules: lose more than a set percentage in a day, or in total, and the account is finished. So traders reach for a small utility that watches the account and enforce

Sep 26·5 min read·honest-backtest.hashnode.devRead the article

#security
#trading

Written by

Valerii Sakara

@arakas4488cmd

View profile

Independent code audits for algorithmic trading bots — real bugs, real backtests, no marketing curves.

I audit algorithmic trading bot code for a living — entry/exit logic, order management, risk handling, fee-honest backtests. I've filed 40+ public responsible-disclosure issues against live open-source trading bots, and audited my own bot the same way before offering this to anyone else.

Responses1

Markdown supported · ⌘↵ to post

Arnold Holm

Oct 9

Saving the breach flag and day-start value together fixes the restart problem you describe. I would also test a restart during the file write: if the saved state is missing or unreadable, new entries should stay disabled until it is restored, rather than use the current equity as a fresh baseline. Does the revised version keep the halt in that interrupted-write case?