The score, by dimension
- the same for all 7
- #6 of 7 · best 21.0
- the same for all 7
- the same for all 7
- the same for all 7
Tick: the best in this ranking · Methodology v2026.11.1
NEAR DA
Data availability on NEAR
#6 of all 7 worldwide41
- Rank
- #6 of all 7 worldwidere-runs: scores 41 and ranks #6–#7
- Your cost
- Not priced on this basis
- Evidence
- High4 of 4 criteria sourced
- Licence
- No MiCA record on file
- Freshness
- Read October 2026checked · re-read due
Check availability for your country
NEAR DA · docs.near.org. Provider links appear once we know which country you are browsing from: ChainChoice links to providers only where it serves in full.
Commission: This provider pays ChainChoice nothing for this link. Disclosure
Crypto products are high risk. Check the provider is authorised where you live before you deposit.
The verdict
NEAR DA is #6 of 7 published data availability layers; it scores 4/10 on halt blast radius, where the category best is 10. Its widest gap is published cost per mb: 1/10, where EigenDA scores 4. Choose EigenDA if published cost per mb matters most.
Is NEAR DA right for you?
Look elsewhere if
- Verifiable published cost per MB1/10 here; EigenDA scores 4
- What actually secures the data2/10 here; Avail DA scores 5
- Sampling live + how long data stays retrievable1/10 here; Avail DA scores 5
- Blast radius if it halts + documented uptime4/10 here; the category best is 10
Not yet tested for your country. Markets it lists: Global.
to test where you can use it.
The rank above is the published one, the same for every reader. Find my best data availability layer shows where it lands for you.
What will NEAR DA cost you?
Not priced on this basis
- Usage per month
- 10
How safe is NEAR DA?
- Evidence: verified4 of 4 criteria rest on quoted, sourced receipts. Read October 2026.
- LicenceMiCA (EU): no register record on file here.
If it doesn’t fit, choose
Compare all 4- 4Avail DAIf das and retention matters most: 510 points above · stronger on das and retention (5 against 1)51
- 5EigenDAIf published cost per mb matters most: 45 points above · stronger on published cost per mb (4 against 1)46
- 70G DAIf das and retention matters most: 2Level on score · stronger on das and retention (2 against 1)41
Provider at a glance
- Category
- Data Availability Layers
- Entity
- All 2 NEAR products
- Official website
- docs.near.org
Independent rankingchecked How it works
Details
Scored 41 out of 100 under methodology 2026.11.1, from the evidence read in October 2026.
For your setup
Find out if NEAR DA fits you
The rank above is the published one — the same for every visitor. Answer the category's questions and this section shows where NEAR DA lands for you, which criteria your answers weight up, and which stated needs the record does or does not meet. The published rank stays beside it.
- A few questions
- No account required
- Ranking-blind: no commercial input
- Personalised in under 60 seconds
Find my best data availability layerNothing is inferred from clicks, popularity or commercial value.
Why this rank
Why NEAR DA ranks #6
Each strength is read from evidence on a 0–10 ladder and weighted as the published methodology states. The 32 objective points these produce (5.6 here) sit inside the score; availability, friction, trust record and measured data add the rest.
4 published criteria · Σ weight 100
CriterionWeightStrength · 0–10ScoreContrib.MedianBestRankEvidence
301+0.963.09#6/7
Primary
Provider page · read 2026-10-22302+1.925.010#6/7
Primary
Provider page · read 2026-10-22251+0.805.08#7/7
Primary
Provider page · read 2026-10-22154+1.924.010#4/7
Primary
Provider page · read 2026-10-22Hairline = best in this ranking · tick = its median · a missing bar is "not scored", never zero
Margin−5behind EigenDA, #5 of all 7 worldwide, on the published score
RobustnessOne point from changingacross a one-point change to each of its 4 criterion scores, the re-run scores 41 and ranks #6–#7
Evidence4 of 4 scored4 quoted, 4 with a source link
What would move the rank
Each line is the ranking run again with one of NEAR DA’s criterion scores changed and every other value held: the smallest whole-point change on that criterion that moves its rank, and where the re-run puts it. Up to 4 climbs and 3 falls are listed, smallest change first. Nothing here is a forecast.
Verifiable published cost per MB 1 → 5 on its ladder · passes EigenDA+446#6 → #5
What actually secures the data 2 → 6 on its ladder · passes EigenDA+446#6 → #5
Sampling live + how long data stays retrievable 1 → 6 on its ladder · passes EigenDA+546#6 → #5
Verifiable published cost per MB 1 → 0 on its ladder · 0G DA passes it−141#6 → #7
What actually secures the data 2 → 1 on its ladder · 0G DA passes it−141#6 → #7
Sampling live + how long data stays retrievable 1 → 0 on its ladder · 0G DA passes it−141#6 → #7
Smallest climb: verifiable published cost per MB 1 → 5 passes EigenDA, #5.
Strengths
0 from the score dataWhere it leads
No scored criterion is at or within one point of the category best, so no strength can be stated from the data.
Tradeoffs
4 from the score dataWhere it trails
Not for readers who put first
- Verifiable published cost per MB — 1/10 against a category best of 9/10
- What actually secures the data — 2/10 against a category best of 10/10
- Sampling live + how long data stays retrievable — 1/10 against a category best of 8/10
- Blast radius if it halts + documented uptime — 4/10 against a category best of 10/10
Record watch-outs
- Read the retention line literally: your rollup's data leaves NEAR consensus after roughly 36 to 60 hours, after which availability is a property of third-party archival nodes and indexers, not of the protocol. That is a fundamentally different product from Celestia's 7 days or Ethereum's 18 — a rollup node that goes offline for a long weekend may be unable to sync from NEAR DA alone. The same page's summary gives a longer floor ('The function input data is stored by full nodes for at least three days'), so the docs disagree with themselves on how long the data stays.
- Verifiable published cost per MB — 1/10. The docs contain exactly one number — '100KiB is a flat fee of 1NEAR' — and immediately disclaim it as the mechanism they do not use. The actual cost, NEAR gas on the receipt carrying the blob, is never quantified, and the figure is hedged with 'At the time of writing' and no date.
- What actually secures the data — 2/10. Data rides NEAR receipts, so it inherits NEAR validator consensus only while the receipt is live. The docs also flag the verification primitive as immature: the blob commitment is a SHA-256 Merkle tree over 256-byte chunks, and 'The blob commitment currently needs to be more efficient and will be improved'.
Competitive position
How NEAR DA places on each criterion
Rank on every objective dimension among the rows scored on it. A criterion in the top third of its pool is listed as a lead, the bottom third as a trail; the middle is neither. Popularity, size and commercial terms are not dimensions.
Against the leader
82 vs 41 · gap 41.0Why Ethereum Blobs (EIP-4844 / PeerDAS) ranks above NEAR DA
The compare workspace's arithmetic applied to these two rows. Each dimension's share of the gap is its weight × the difference, on the displayed scale; a floor bound on one of the rows keeps the reproduced gap (43.7) from matching the displayed one exactly, which is stated rather than hidden.
DimensionThisEthereum Blobs (EIP-4844 / PeerDAS)Gap share
Availability · 23% weight · constant here14.014.0same
Published criteria · 35% weight4.221.0−43.7, worse
Friction · 12% weight · constant here2.72.7same
Trust record · 9% weight · constant here3.23.2same
Measured data · 21% weight · constant here8.38.3same
Published criterionThisEthereum Blobs (EIP-4844 / PeerDAS)Points
Verifiable published cost per MB · w3019−7.68, worse
What actually secures the data · w3029−6.72, worse
Sampling live + how long data stays retrievable · w2518−5.60, worse
Blast radius if it halts + documented uptime · w1549−2.40, worse
Net4182−41.0≈
Your scenario
NEAR DA is not priced for this scenario
Metered usage beyond whatever the plan includes, for a year. Excludes egress, support tiers and enterprise minimums. Change an input and every figure recomputes from the published rate; the published rank does not move.
your cost/yr · default scenario — set your own
Usage per month · your input10
Rate read from the provider’s published pricing ↗ on 22 October 2026.
your cost/yrCost is stated as your cost/yr in USD; it is never a yield, never annualised, and it does not enter the score.
Not priced on this basis
Under the default inputs · USDTypical costNot statedFewer than 5 priced rows: no typical cost is named · 0 of 7 rows priced
Lowest fee, priced rowsNone pricedDifference not stated · availability not applied — set your country to filter
7 of 7 rows in this ranking have no verified rate for this scenario and are absent from the typical, not counted as free.
Evidence
Evidence read 22 October 2026
One row per published criterion: the page each strength was read from, its source type by domain, the reading date and whether the file and the published table agree. Open a row for the quote and the receipt.
4 of 4 cells scored
Score evidenceVerified4 of 4 criteria reconstruct from receipts
4 of 4 criteria reconstruct from a quoted, sourced receipt equal to the published strength.Public receiptsReading…4 quoted with a source URL
The receipt file has not been read yet.Evidence confidenceHighcoverage and corroboration, never freshness
4/4 criteria scored, with 4 dated sources quoted.RobustnessOne point from changingrank #6 to #7 across one-point re-runs
Whether the position holds when one criterion score is changed by one point and the ranking is run again. It is always a re-run of the ranking, never an estimate.The newest evidence read on the platform is 10 November 2026; this category's reading is older. The scores stand as read on 22 October 2026.
CriterionSourceTypeReadFreshnessStatusReceipt
Verifiable published cost per MBstrength 1 · weight 30Report an errorProvider's own page22 October 2026…
Verified
The published strength matches the evidence cell and a source page is on file.What actually secures the datastrength 2 · weight 30Report an errorProvider's own page22 October 2026…
Verified
The published strength matches the evidence cell and a source page is on file.Sampling live + how long data stays retrievablestrength 1 · weight 25Report an errorProvider's own page22 October 2026…
Verified
The published strength matches the evidence cell and a source page is on file.Blast radius if it halts + documented uptimestrength 4 · weight 15Report an errorProvider's own page22 October 2026…
Verified
The published strength matches the evidence cell and a source page is on file.How you can lose money here, and what the ranking scores
- Verification failure: an invalid state or transfer is accepted.Scored by What actually secures the data · 30% (NEAR DA 2/10)Scored by Sampling live + how long data stays retrievable · 25% (NEAR DA 1/10)
- Liveness failure (NEAR DA 4/10): the operator stops, censors you or loses data.Scored by Blast radius if it halts + documented uptime · 15%
Not assessed by this ranking: Contract failure, Control failure. A high place says nothing about these; the Methodology tab says what each means. Also scored, as cost, quality or a summary of several families: Verifiable published cost per MB (30%).
Facts
facts, not scoresWhat the record publishes
- Pricing
- Read 22 October 2026 (docs.near.org/chain-abstraction/data-availability): "NEAR blockchain state storage is pretty cheap. At the time of writing, 100KiB is a flat fee of 1NEAR. To limit the costs of NEAR storage even more, we don’t store the blob data in the blockchain state." No price is published for the path NEAR DA actually uses (receipt data), only for the state-storage path it explicitly avoids. For reference only (arithmetic), the quoted state-storage rate at NEAR $4.99 (CoinGecko 22 October 2026) would be $51.10/MiB.NEAR DA — official documentation ↗ · 22 October 2026
- Prices published in
- USDNEAR DA — official documentation ↗ · 22 October 2026
- Licences held
- Not published
- Compliance level
- partial
- Regulatory note
- Not published
- Supported chains
- Multi-chain
- Markets served
- global
- Primary markets
- Not published
- Restricted markets
- Not published
- Operating limits
- Not published
- Availability note
- No country restriction on the NEAR DA docs page or the Nuffle Labs data-availability README read 22 October 2026. The near.org Terms of Use (Discovery Domain Ltd, "Last updated: 27 November 2024", read 22 October 2026) govern the near.org websites and tools, and require each user to represent "that you are not a citizen, resident, or member of any jurisdiction or group that is subject to economic sanctions". They name no country and do not govern use of the protocol.
Legal entity on file: NEAR, placed in 2 products. Only confirmed entities are shown; nothing is inferred from the brand name.
If something goes wrong with NEAR DA: where to complain, and where to report a scam
Loading the routes for your country.
How this page is reviewed
Reviewed means this product in this category was read against its sources on or after that date; every ranked category is re-read at least every 45 days. Models research, extract and parse. A deterministic engine ranks. Every quote passes an adversarial refute pass.
Accountable for this review: Mathias Siemonsmeier, Founder.
How we review · Review calendar · Corrections log · How we make money
History
What the record carries
Changes to published ranks are recorded in a ledger; every step and its cause is listed on the rank-history page. The entries below begin with the current verified snapshot, then the methodology versions whose changes applied to this category, newest first.
8 methodology entries
- 22 October 2026Current verified snapshot · methodology 2026.11.1Score 41, #6 of 7. 4 of 4 criteria scored. History starts here; earlier values are not interpolated.
- 10 October 2026
2026.10.8When nothing serves your country, the list shown for reference is the published ranking · platform-wide- fixed The reference list shown when nothing serves your country is the published order with the published scores, and a build check now fails any such list out of that order or with a score the ranking does not publish.
- fixed The explorer prints an overall rank only for a row the published ranking holds; a country entrant such as Coinbase Commerce for US merchants shows no overall rank.
- changed Published orders do not move. Country results change only where nothing serves the country: in India bill pay keeps Bitcoin Well first and now shows Strike second, as published; 35 such runs across all categories and countries now match the published list exactly.
- 10 October 2026
2026.10.6A criterion you require re-scores the rows that meet it · platform-wide- changed The explorer sends each criterion you require, at any band, as fit_required with your other answers; region, licence, chain and fact filters stay filters. On /best, a required criterion joins For you as a marked preference does, which needs your country; Overall stays the published ranking, filtered.
- added Every published criterion has a golden case as the explorer sends it (require:<criterion>), so the order a requirement gives is replayed and gated as the published order is, and a change to it needs an entry here.
- 16 September 2026
2026.09.15Dimension scores carry tenths, and eleven more categories are re-read from primary sources · platform-wide- changed Dimension scores resolve to tenths of a point (O-04b), and weightedTotal is rounded to six decimal places before the order is read. 518 published scores move across 107 categories that were not re-read; none of them moves by more than 4 points, and most move by 1.
- fixed 66 published scores change in the eleven re-read categories, against a verbatim source each. The largest moves are Reflexer RAI (−16), Beefy and Unrekt (−11), Aztec (−10) and Golem (+9) — all of them rows whose sources had moved since their last read.
- changed Published order moves in 38 of 119 categories and three #1s change: smart_contract_audits (Zellic → Certora) and travel_rule_compliance (Sumsub Travel Rule → CodeVASP) on the finer resolution, kyc_compliance (Veriff → Sumsub) on the re-read.
- added availabilitySource (O-04g): for a reader who states a country, a row whose availability in that country rests on a region tag its record gives no source for sorts below every sourced row. It is inert in every order published here, which states no country.
Methodology 2026.11.1, the same published run every visitor sees · receipt data_availability:near_da:2026.11.1:0e1a49bc18a0
Are you NEAR DA? Reply to this verdict, or send evidence, ask for a correction or claim the listing. Every message gets a public ticket number; none of it changes a rank unless a public page or a signed statement supports it.