A pre-registered investment thesis · NEAR Protocol

We tested five claims about NEAR.
Four went against us.

Bots and airdrop farming filtered out, every threshold choice published, and the rejection criteria committed to git before any data was pulled. Every number on this page is generated from results/metrics.json; none is typed by hand.

loading…

Hypothesis scoreboard

One rule produced every verdict: a least-squares trend on the monthly series, read through the 95% interval on its slope. Entirely in the predicted direction is supported, entirely opposite is rejected, spanning zero is inconclusive. Each card opens its evidence.

The signature metric

Cross-chain settlement share

Show SQL (native leg)
loading…

Why the share rose: the decomposition

Both series indexed to their first measured month = 100. Same sampled days on both sides.

The evidence, hypothesis by hypothesis

H1 — Economic accounts fell, at every threshold we pre-registered

Show SQL
loading…

H2 — Activity concentrated into fewer contracts

Show SQL
loading…

H3 — Retention drifts down, but not past the bar we set

Source: derived from the same per-account scan as H1; cohorts by first economic monthDownload CSV

H5 — Fee burn is a rounding error against issuance, and shrinking

Show SQL
loading…

Sensitivity — all 27 threshold combinations

The H1 decline survives every cell of the grid

Change in economic accounts, first month to last, for every pre-registered (d, c, b) combination. The outlined cell is the default. Tightening the filter makes the decline steeper — the opposite of a threshold artefact.

against the prediction flat (CI spans zero) with the prediction

Exploratory (not pre-registered)

Something happened in April 2026

What would change our mind

Each is a quantity this pipeline already computes; re-run them any month with make refresh.

Bull / base / bear — indicators, not price targets

Amendments to the pre-registration

The pre-registration is frozen; changes are appended as dated amendments, each with its reason, its cost, and an assessment of whether it could bias a result. The original text is never edited.

    Don't trust us. Re-run it.

    Clone the repository and run the check — no cloud account, no keys. It rebuilds every number from the committed data and fails if a single figure in the prose has drifted.

    zsh
    $ git clone https://github.com/sambitsargam/near-filtered
    $ cd near-filtered && make verify
    ↑