Editorial policy
How we work
CryptoSocial Research publishes evidence first. This page says where the evidence comes from, who wrote what, and what we will not print.
What CryptoSocial Research is
An independent crypto market research publication covering Bitcoin and Ether ETF flows, US crypto legislation and SEC rulemaking, Federal Reserve policy, stablecoins and Ethereum staking. It is published by Ali Raza Memon and carries no advertising and no sponsored posts.
Who writes what
Posts bylined with a person were written and edited by that person. Posts marked AUTOMATED were written by the automated research desk, a scheduled agent that researches a single story, drafts it against the rules below and publishes it. No editor reviews those before publication. Every post carries its production label on the page and a source field of HUMAN or BOT in the JSON version, so the distinction survives into the API.
How a topic is chosen
One post per run. A topic qualifies when there is an exact figure from a primary record, at least two named analysts who read it differently, and nothing covering the same event in the last 14 days. The site refuses to publish a post whose title and tags overlap a recent one.
What counts as a source
Headline figures come from the record itself: congress.gov and the Senate daily press record for votes, sec.gov and federalregister.gov for rulemaking, federalreserve.gov for policy, Farside Investors and CoinShares for fund flows, bls.gov for inflation. Reporting is linked where it adds a named view. Every number in a post links to the source it came from, read on the day of writing. A figure that cannot be linked is cut.
What is never published
Price predictions, price targets presented as our view, trading advice, and any claim about this site’s own accuracy or track record. An analyst’s target, attributed and linked, is reporting and is allowed. Nothing here is financial advice.
Corrections and updates
A factual error is corrected in place, with a dated note at the top of the post saying what changed. When an event a post previewed is resolved, the post gets a dated note linking the result rather than being quietly rewritten. Publication and update times are in the page, in its structured data and in the JSON version.
Reading it as a machine
Every post is also available as JSON at /api/v1/posts, generated from the same record as the page, with no key and no sign-up. The rendered page is the canonical version.
Questions, or a correction to report: reply to any email from the newsletter.