Verifying a research report you received

If someone forwards you an MF Research report, you should be able to confirm it is the version we published. The verification portal does that in seconds without you installing anything.

The verification portal

Every report carries a verification slug at the top of the first page (format: /research/verify/<slug>). Open the URL.

The portal displays:

• The report content
• The signature block
• The signing key fingerprint
• The publication timestamp

If any of those do not match the version you have, the portal flags the discrepancy.

Manual verification (technical readers)

The report's canonical payload is a deterministic JSON serialization of the report fields. You can verify the Ed25519 signature against the published public key using any standard cryptographic library. Public keys live at /research/verify/keys.

Why we sign reports

Research reports get forwarded, edited, and screen-shotted. Signing lets the institutional reader confirm the version they have is the version we published, not a modified copy. We will not push out a research report on an issuer name without a signature attached. If you receive an unsigned "MF Research" report, treat it as fraudulent and forward to security@marketfortress.app.

Key rotation

The signing key rotates on the first business day of each calendar year. Reports signed under prior keys remain verifiable; the portal carries every prior public key indefinitely.