Why CoinPulse rated Blockdaemon 10 in staking
The staking platforms ranking scores Track record (30%), Security record (30%), Status transparency (22%) and Latency (18%), the criteria that can be checked for every provider in a category of mostly off-chain node operators and exchanges. Scale of value trusted, Security audits, Multi-chain reach and Peg stability are not scored here. All four were measured for Blockdaemon, so coverage is 100%.
A 10 on each gives 3.00, 3.00, 2.20 and 1.80 points, the maximum total. It means Blockdaemon reached the top band on every measurement this category takes, not that it has no room to improve elsewhere. The rubric is on the methodology page.
Where Blockdaemon scored well
Track record: 9.3 years (10/10)
Age is taken from the public record of the 2017 launch, 3,398 days at collection, longer than the 3,033-day category median. That is the top band and contributes 3.00 points. It records survival through several market cycles, not a problem-free history.
Security record: no hack on record (10/10)
DefiLlama's hack database, 1,307 incidents when checked on October 19, 2026, has no entry matching Blockdaemon by id or name. That scores 10 and is worth 3.00 points. It is no hack on record in that database, not a statement that Blockdaemon has never had a security incident.
Status transparency: a full incident archive (10/10)
Blockdaemon publishes a statuspage feed with a machine-readable incident history. That scores 10 against a category median of 5 and contributes 2.20 points. The criterion rewards being checkable from outside, not having few incidents.
Latency: 68 ms median (10/10)
Our probe timed blockdaemon.com at a median 68 ms to first byte from a single location, slowest sample discarded, against a category median of 105 ms. That is the top band and adds 1.80 points. It describes the website, not node or API performance.
What Blockdaemon's status feed shows (not scored)
Because the archive is public, the page can show context that most providers do not allow. Over the 90 days the feed covers, Blockdaemon logged 7.33 incidents per 30 days, 22 in all. The feed classes 15 as minor, 3 as major, 2 as critical and 2 with no severity. The median time from report to published resolution was 4,281 minutes, and no incident was open at collection.
These figures are measured but not scored. Logging granularity varies widely between services, and most providers in this category publish no feed, so there is nothing fair to compare them with. A provider that logs every minor issue across many networks can show more incidents than one that reports only major outages. Read them as what Blockdaemon discloses, and as the place to look for its operational history.
What the Blockdaemon score does not measure
The rating measures operational health from public data. It does not certify that Blockdaemon is safe, solvent or legal, and a 10 is not a guarantee against loss. Staked value, validator performance, slashing history, supported networks, rewards, fees, user experience and support are not scored, and no value-locked, audit or chain figures were recorded for Blockdaemon in this collection. The funding and independence policy is on the funding page.
How Blockdaemon compares in the staking ranking
P2P.org (10, #1) also scores 10 on all four criteria, so the order between the two is not explained by any measured difference; read them as tied. Kiln (9.82, #3) has an archive as well but scores 9 on latency, 0.18 behind. Figment (9.34, #4) exposes a live status without an archive and scores 7, 0.66 behind. Coinbase (8.92, #5) scores 7 on security record and 9 on latency, 1.08 behind.
On the status feeds themselves, which are not scored, P2P.org logged 2 incidents per 30 days against Blockdaemon's 7.33. That difference is not part of either score, for the comparability reasons above.
Takeaway: the maximum on every criterion, with its incident log in the open
Blockdaemon's 10 reflects 9.3 years in operation, no hack on record in DefiLlama's database, a fast website and a status archive anyone can audit. The archive is also where readers will find a busy incident log and long median repair times, which the rating shows but does not score. Rewards, validator quality and staked value are outside the rating, and it is not a recommendation to stake.