Screenshots prove nothing and a balance figure proves less. Material events are sealed into a SHA-256 chain where each entry commits to the one before it, so an edited history stops verifying.
Each sealed entry hashes its own index, timestamp, type and payload together with the previous entry's hash. Change anything in the middle and every hash after it changes, which is what makes the record tamper-evident rather than merely stored. It is the same construction a blockchain uses, applied to your own practice history, on your own device.
Fills and material events are sealed. Chatty per-tick activity is not — it goes to an unhashed logbook instead. That is a design constraint with a reason: the chain keeps a bounded window of recent entries, so anything that sealed an entry per micro-event would push your own trades out of your own record. Bot activity therefore seals one entry per fill and one per kill, and nothing else.
It is not an unlimited archive, not a custodian's statement, and not proof that anything was traded with real money — nothing here is real money. It is a bounded, tamper-evident window over recent activity, which is a specific and honest claim. Export what matters before it ages out.
Because the alternative — "trust the number on the dashboard" — is exactly the arrangement the rest of this space runs on. A verifiable local record is the version that respects you, and it costs nothing to give away.
No. The chain is computed and kept on your own device. There is no account and nothing is uploaded.
You can alter local storage, but the chain stops verifying if you do — which is the entire point of hashing each entry against the previous one.
No. It keeps a bounded window of recent sealed entries, so high-frequency events are deliberately excluded and older entries age out. Export what you want to keep.
Open the desk — free, no account — no account, nothing to install