The score, by dimension
- the same for all 7
- #5 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
EigenDA
Restaked data availability layer
#5 of all 7 worldwide46
- Rank
- #5 of all 7 worldwidere-runs: scores 44–47 and stays #5
- 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
EigenDA · docs.eigencloud.xyz. 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
EigenDA is #5 of 7 published data availability layers; it scores 4/10 on published cost per mb, where the category best is 9. Its widest gap is security model actual: 3/10, where Avail DA scores 5. Choose Avail DA if security model actual matters most.
Is EigenDA right for you?
Look elsewhere if
- Verifiable published cost per MB4/10 here; the category best is 9
- What actually secures the data3/10 here; Avail DA scores 5
- Sampling live + how long data stays retrievable2/10 here; Avail DA scores 5
- Blast radius if it halts + documented uptime2/10 here; NEAR DA scores 4
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 EigenDA cost you?
Not priced on this basis
- Usage per month
- 10
How safe is EigenDA?
- 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: 55 points above · stronger on das and retention (5 against 2)51
- 6NEAR DAIf halt blast radius matter most: 45 points below · stronger on halt blast radius (4 against 2)41
- 70G DA5 points below · weaker on published cost per mb (1 against 4)41
Provider at a glance
- Category
- Data Availability Layers
- Official website
- docs.eigencloud.xyz
Independent rankingchecked How it works
Details
Scored 46 out of 100 under methodology 2026.11.1, from the evidence read in October 2026.
For your setup
Find out if EigenDA fits you
The rank above is the published one — the same for every visitor. Answer the category's questions and this section shows where EigenDA 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 EigenDA ranks #5
Each strength is read from evidence on a 0–10 ladder and weighted as the published methodology states. The 32 objective points these produce (9.3 here) sit inside the score; availability, friction, trust record and measured data add the rest.
4 published criteria · Σ weight 100
CriterionWeightStrength · 0–10ScoreContrib.MedianBestRankEvidence
304+3.843.09#3/7
Third party
Third party · read 2026-10-22303+2.885.010#5/7
Third party
Third party · read 2026-10-22252+1.605.08#5/7
Third party
Third party · read 2026-10-22152+0.964.010#6/7
Third party
Third party · read 2026-10-22Hairline = best in this ranking · tick = its median · a missing bar is "not scored", never zero
Margin−5behind Avail DA, #4 of all 7 worldwide, on the published score
RobustnessHoldsacross a one-point change to each of its 4 criterion scores, the re-run scores 44–47 and stays #5
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 EigenDA’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 4 → 8 on its ladder · passes Avail DA+453#5 → #4
What actually secures the data 3 → 7 on its ladder · passes Avail DA+453#5 → #4
Sampling live + how long data stays retrievable 2 → 6 on its ladder · passes Avail DA+452#5 → #4
Blast radius if it halts + documented uptime 2 → 9 on its ladder · passes Avail DA+752#5 → #4
Verifiable published cost per MB 4 → 0 on its ladder · NEAR DA passes it−441#5 → #7
Smallest climb: verifiable published cost per MB 4 → 8 passes Avail DA, #4.
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 — 4/10 against a category best of 9/10
- What actually secures the data — 3/10 against a category best of 10/10
- Sampling live + how long data stays retrievable — 2/10 against a category best of 8/10
- Blast radius if it halts + documented uptime — 2/10 against a category best of 10/10
Record watch-outs
- Three things compound against small rollups. Min blob size is 128 KiB, so a 4 KB batch is billed as 128 KiB. Deposits into the PaymentVault are non-refundable. And the marketing headline of '100 MB/s' throughput on the overview page cannot be reached on-demand — the payments doc caps global on-demand dispersal at 131,072 symbols/second, which it labels '4mb/s', a 25x gap inside the vendor's own documentation.
- What actually secures the data — 3/10. The security-model page states the trust assumption outright: 'To guarantee liveness, we currently rely on a trusted disperser that does not censor clients' blob disperser requests. We will soon introduce decentralized dispersal to remove this trust assumption.' The overview page contradicts this, claiming 'Dispersers can be run as decentralized service providers'.
- Sampling live + how long data stays retrievable — 2/10. No data-availability sampling: each validator is assigned a disjoint erasure-coded shard sized to its stake, and 'any set of operators collectively having a percentage γ of the total delegated stake is able to reconstruct the original blob'. Retrievability depends on operators serving shards, and the security-model page says 'We are actively developing the DAS protocol for EigenDA to address these limitations'. The EigenCloud Terms set a deletion deadline, not a retention guarantee: 'All data submitted to the EigenDA Service is subject to automatic and irreversible deletion after a period of fourteen (14) days', and 'The Covered Parties do not guarantee the continued availability or recoverability of any data submitted to the EigenDA Network or the EigenDA Service.'
Competitive position
How EigenDA 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 46 · gap 36.0Why Ethereum Blobs (EIP-4844 / PeerDAS) ranks above EigenDA
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 — it reproduces the displayed gap of 36.0 to within rounding.
DimensionThisEthereum Blobs (EIP-4844 / PeerDAS)Gap share
Availability · 23% weight · constant here14.014.0same
Published criteria · 35% weight7.021.0−36.4, 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 · w3049−4.80, worse
What actually secures the data · w3039−5.76, worse
Sampling live + how long data stays retrievable · w2528−4.80, worse
Blast radius if it halts + documented uptime · w1529−3.36, worse
Net4682−36.0
Your scenario
EigenDA 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.RobustnessHoldsrank #5 across every one-point re-run
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 4 · weight 30Report an errorThird-party page22 October 2026…
Verified
The published strength matches the evidence cell and a source page is on file.What actually secures the datastrength 3 · weight 30Report an errorThird-party 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 2 · weight 25Report an errorThird-party 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 2 · weight 15Report an errorThird-party 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% (EigenDA 3/10)Scored by Sampling live + how long data stays retrievable · 25% (EigenDA 2/10)
- Liveness failure (EigenDA 2/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
- Payments doc, read 22 October 2026 from its source in the Layr-Labs/eigencloud-docs repository (docs/eigenda/core-concepts/payments.md; the rendered docs.eigencloud.xyz pages return HTTP 403 Cloudflare challenges to plain clients): "Example: Initially, EigenDA team will set the price per symbol to be 0.4470gwei, aiming for the price of 0.015ETH/GB, or 2000gwei/128Kib blob dispersal." Same page: "A symbol is defined as 32 bytes"; users "Deposit tokens permissionlessly for on-demand payments and/or negotiate reservations with the EigenDA team"; "Users should be mindful in depositing as they cannot withdrawal or request for refunds from the current PaymentVault contract"; "On-demand payments are supported only through the EigenDA Disperser, which tracks usage and validates payments." On-chain 22 October 2026 at block 26,246,887: EigenDADirectory 0x64AB2e9A86FA2E183CB6f01B2D4050c1c2dFAad4 getAddress('PAYMENT_VAULT') = 0xb2e7ef419a2A399472ae22ef5cFcCb8bE97A4B05, whose pricePerSymbol() = 447000000 wei, minNumSymbols() = 4096, globalSymbolsPerPeriod() = 131072, globalRatePeriodInterval() = 30 and lastPriceUpdateTime() = 1744750295 (15 April 2025), so the "Initially" price is still the live one. Mainnet page source: "Min Blob Size | 128 KiB", "Max Blob Size | 16 MiB". DERIVED (arithmetic) at ETH $2,416.88 (CoinGecko 22 October 2026): 32,768 symbols x 0.447 gwei = 0.00001465 ETH = $0.0354/MiB (= 0.015 ETH/GiB). That is 3.05x Ethereum blobs at their median over blocks 26,245,860-26,246,883 ($0.0116/MiB). The minimum 4,096-symbol dispersal costs 1,831 gwei on-chain, not the "2000gwei/128Kib" the doc states. Reserved bandwidth has no public price.EigenDA — official documentation ↗ · 22 October 2026
- Prices published in
- USDEigenDA — 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
- On-demand deposits are described as permissionless, but the EigenCloud Terms of Service (Eigen Labs, Inc., "Last Revised on December 15, 2025", read 22 October 2026 from the docs source; the rendered docs.eigencloud.xyz page returns a Cloudflare challenge) state: "You must be 18 years of age or older and not be a Prohibited Person to use the Services." A Prohibited Person includes anyone "located or organized in any U.S. embargoed countries or region any country or region that has been designated by the U.S. Government as "terrorist supporting"". The Terms cover the EigenDA Service and the Eigen Disperser and do not name the countries.
Legal entity on file: EigenLayer, placed in 2 products. Only confirmed entities are shown; nothing is inferred from the brand name.
If something goes wrong with EigenDA: 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 46, #5 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:eigenda_da:2026.11.1:0e1a49bc18a0
Are you EigenDA? 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.