What AlphaProof verifies, what it does not, and the risks every reader should understand before relying on a track record published here. Read this once before you treat anything on AlphaProof as actionable.
AlphaProof publishes verified trading track records. The verification is precise: every trade entry is SHA-256 hashed, chained to the previous trade via that hash, and periodically anchored to the Bitcoin blockchain via OpenTimestamps. The chain proves three things:
The verification does NOT prove these things:
BROKER — imported via Plaid or SnapTrade from a connected brokerage. The source is irrefutable; the brokerage signed off on the data. AlphaProof passes the data through unchanged.
STATEMENT — uploaded by the creator as a brokerage statement PDF. AlphaProof verifies the document is authentic (a real broker generated it, not Word/Canva), then extracts and cross-references every field. The contents are taken as provided. Statement-imported portfolios have their public verify surface disabled because statement uploads can be cherry-picked (see "Imported portfolio limitations" below).
MANUAL — entered by the creator at market price, with the price constrained to the day's high-low range. The server stamps the timestamp at the moment of entry; backdating is impossible. AlphaProof does not verify the trade was actually executed at a broker.
Past performance does not guarantee future results. This is the single most repeated phrase in this document because it is the single most repeated mistake every reader makes when looking at someone else's track record.
Cryptocurrency — high volatility, regulatory uncertainty, custodial risk, stablecoin de-pegging events. Crypto markets operate 24/7 with limited circuit breakers; losses can compound quickly outside business hours.
Options — significant loss potential, time decay, exercise/assignment risk. A favorable options trade in someone else's account does not imply you can replicate it given different account permissions, margin, or timing.
Short positions — unlimited loss potential. Short squeezes can produce losses that exceed the original capital deployed.
Foreign exchange (FX) — currency volatility, central bank actions, leverage amplification. AlphaProof normalizes FX trades to USD for verification, but the underlying exposure is in the original quote currency.
Futures — leverage amplifies both gains and losses. Margin calls and daily settlement can require capital injections that the published track record may not visibly account for.
AlphaProof is not a registered investment advisor (RIA) in the United States, nor is it registered as an investment-advisory firm in any other jurisdiction. AlphaProof does not provide investment, financial, legal, or tax advice. Nothing published on AlphaProof should be construed as a recommendation to buy, sell, hold, or short any security or asset.
Creators on AlphaProof publish their own track records. They are not employees, partners, or contractors of AlphaProof. AlphaProof does not endorse any creator's strategy, results, or qualifications.
If you are considering acting on information you found via AlphaProof, consult a licensed advisor in your jurisdiction. The creator you read is not your advisor; AlphaProof is not your advisor.
When a creator uploads a brokerage statement PDF (the "STATEMENT" source), the upload represents only the trades the creator chose to include. There is no way for AlphaProof to verify that the creator did not omit losing trades from the statement.
To preserve the integrity of public claims, portfolios that include statement-imported trades have their public verify surface disabled — they are private to the creator only. Public portfolios must be built forward in real time using BROKER or MANUAL sources, both of which prevent retroactive insertion.
AlphaProof reports are not tax records. They are not 1099s, B3 reports, capital-gains summaries, or any other form a tax authority recognizes. Do not use AlphaProof reports for tax filing, audit response, or accounting reconciliation.
AlphaProof does not provide tax forms, tax advice, or guidance on the tax treatment of trades you record here. Creators earning subscription income are responsible for reporting that income to their tax authority.
AlphaProof is a track record platform. It does not:
Subscriptions on AlphaProof give the subscriber access to the creator's trade journal and notifications. They do not replicate trades into the subscriber's account, and AlphaProof has no visibility into whether subscribers act on the journal.
Creators who activate paid subscriptions complete a one-time identity verification step via Stripe Identity. This verifies the creator's government-issued ID and confirms they are a real, single individual. It does NOT verify investment qualifications, professional registrations, or any claim the creator makes about their experience.
Trade records, hash chain entries, and Bitcoin anchors are retained indefinitely as part of the verifiable record. PDF reports generated for download are retained for 72 hours and then deleted from object storage; the report row remains in the database for accounting. User accounts can be deleted on request, which removes personal information and severs subscriber follows; the underlying trade records may be anonymised and retained for chain-integrity purposes.
The hash chain uses SHA-256 over a 13-field payload (previous hash, ticker, direction, shares, price, fees, currency, asset class, contract multiplier, FX rate, executed-at timestamp, broker transaction ID, statement hash). Field formats are pinned: numbers use toFixed(8), timestamps use ISO 8601 in UTC, the join delimiter is |, the genesis sentinel is the literal string GENESIS.
Anchoring uses OpenTimestamps over the running tail hash, submitted daily. Confirmed anchors include a Bitcoin block height, browsable via mempool.space or any block explorer.
The verification is reproducible without AlphaProof's tools — anyone can walk the trade list in insertion order, recompute each hash, and verify the chain tail against the OpenTimestamps proof and the Bitcoin block.
This page describes AlphaProof as of May 2026. Features evolve; new sources of trade data may be added; verification semantics may evolve in versioned, non-retroactive ways. Material changes to verification semantics will be announced and reflected here. Subscribers and readers are responsible for re-reading this document if they suspect their understanding is out of date.