Advertisement IC Markets

Logs that can't be edited later

Document your personal trading journey. Track daily equity curves, review winning and losing streaks, share trade screenshots, and get constructive feedback.
Post Reply
Fairman
Posts: 6955
Joined: Tue Jul 21, 2026 7:11 am
Location: Abuja

Logs that can't be edited later

Post by Fairman »

Logs that can't be edited later

A trade log kept in a spreadsheet can be changed after the fact. That's convenient and a bit dangerous. Memory is flexible, and a log tweaked to be tidy loses its value as evidence.

For serious analysis, or for disputes with a broker, a tamper-evident record helps. The simplest approach is exporting platform history on a fixed schedule, saving it with the date in the filename, and never editing the originals.

A step up is computing a hash of each file, a short fingerprint that changes if a single character is altered, and storing the hashes separately, such as in an email to oneself. Any later change would be detectable.

Timestamps matter too. Logs written by scripts should record the time from a synchronized clock, along with the source of that time.

The point isn't paranoia. It's discipline. A record that can't be changed makes the trader honest with themselves, since the numbers stay as they were, flattering or not.

When a dispute with a broker arises, a clean chain of unedited exports is much more persuasive than a spreadsheet with unknown history.

There's a cheap way to get most of this benefit without any scripting. Export the history report every Friday, save it with the date in the name, and email it to a separate address. The mail server's timestamp is an independent record that the file existed on that date, with that content.

For script-generated logs, writing each line with a running sequence number makes deletions detectable, since a missing number stands out. Combined with periodic hashes, the log becomes difficult to alter without leaving traces, and that's enough for most disputes and for honest self-assessment.

What keeps trading records from being quietly changed after the fact?
It’s Fairman :geek:
Recommended broker for automated trading & scalping IC Markets
FXS HongKong Scalper
Posts: 543
Joined: Sat Oct 24, 2026 10:15 pm

Re: Logs that can't be edited later

Post by FXS HongKong Scalper »

Fairman wrote: A step up is computing a hash of each file, a short fingerprint that changes if a single character is altered, and storing the hashes separately, such as in an email to oneself.
The weekly export is the simplest tamper-evident option, especially if the files are emailed to yourself, since the email timestamps are hard to argue with. For broker disputes, the platform's own journal logs are also worth saving, as they include order send and fill times that statements often omit.
FXS Official Team | Hong Kong Session Desk
Amanhasnoname
Posts: 2060
Joined: Fri Oct 30, 2026 9:45 am

Re: Logs that can't be edited later

Post by Amanhasnoname »

This one hit home for me because I used to keep my journal in a spreadsheet and would quietly reword the reason column after a loss. Nothing dramatic, just turning an impulsive entry into a planned breakout in hindsight. Months later, when I tried to work out why my win rate on news days was so poor, the notes were useless because I had softened every bad decision. That was the point where I stopped trusting my own records.

Now I write the entry reason before I click buy or sell, in a plain text file that only ever gets appended to, and every Sunday I zip the week together with the platform statement and send it to a second email address. It takes two minutes. I have never needed it for a broker dispute, but having the original words staring back at me has been worth more than any indicator I have tested.

The sequence number idea is good. I might add it, since right now a deleted line would slip through unnoticed.
Post Reply