Skip to main content
Organisation

Chainlink

4 placements on ChainChoice under Chainlink, each scored against its own category's pool and criteria — #1 in one of them. The placements are not averaged and not ranked against each other: a #1 exchange and a #6 crypto card are two different products in two different markets.

Cross-Chain Token Standards
Chainlink Cross-Chain Token (CCT) standard / CCIP token pools
Rank#1 OverallScore81

Leads the published order

View verdict
Oracles
Chainlink
Rank#4 OverallScore61

#1 in this category: Pyth Network

View verdict
Cross-Chain Messaging
Chainlink CCIP
Rank#5 OverallScore69

#1 in this category: Hyperlane

View verdict
Automation & KeepersHistorical
Chainlink Automation (migrating to Chainlink Runtime Environment)
Rank#7 OverallScore41

#1 in this category: TukTuk (Helium)

View verdict
Cross-Chain Token Standards
How you can lose money here, and what the ranking scores
  • Control failure: a key or vote changes the rules, freezes or mints.
    Scored by Who can mint my token on a chain I don't run — and can I take that away? · 34% (Chainlink Cross-Chain Token (CCT) standard / CCIP token pools 9/10)
    Scored by Can somebody stand up my token on a chain without asking me — and can a holder tell which one is mine? · 24% (Chainlink Cross-Chain Token (CCT) standard / CCIP token pools 9/10)
    Scored by If one of my minters is compromised at 3am, how much of my supply gets printed before anything stops it? · 22% (Chainlink Cross-Chain Token (CCT) standard / CCIP token pools 6/10)
  • Exit failure (Chainlink Cross-Chain Token (CCT) standard / CCIP token pools 8/10): you cannot get out at par, on time, or with what is yours.
    Scored by If I want off this standard next year, do I take my token with me — or do my holders have to migrate? · 20%
Not assessed by this ranking: Contract failure, Verification failure, Regulatory failure, Execution failure. A high place says nothing about these; the Methodology tab says what each means.
Oracles
How you can lose money here, and what the ranking scores
  • Oracle failure: a wrong price or outcome liquidates or settles a position.
    Scored by Incident transparency · 30% (Chainlink 2/10)
    Scored by Exploited-via-this-oracle record · 26% (Chainlink 1/10)
    Scored by Failure-mode architecture · 24% (Chainlink 6/10)
Not assessed by this ranking: Contract failure, Control failure, Regulatory failure, Execution failure, Exit 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: Adoption as stress-testing (20%).
Cross-Chain Messaging
How you can lose money here, and what the ranking scores
  • Verification failure: an invalid state or transfer is accepted.
    Scored by Message trust model · 35% (Chainlink CCIP 4/10)
    Scored by Application configurable security · 25% (Chainlink CCIP 5/10)
    Scored by Forged and stuck message record · 25% (Chainlink CCIP 8/10)
Not assessed by this ranking: Contract failure, Control failure, Liveness failure, Regulatory failure, Execution failure, Exit 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: Cost per message (15%).
Automation & Keepers
How you can lose money here, and what the ranking scores
  • Control failure (Chainlink Automation (migrating to Chainlink Runtime Environment) 6/10): a key or vote changes the rules, freezes or mints.
    Scored by What can fire the call, against what target, and who can check the condition was true · 28%
  • Liveness failure (Chainlink Automation (migrating to Chainlink Runtime Environment) 7/10): the operator stops, censors you or loses data.
    Scored by Whether a run that never happened is visible, or the job just goes quiet · 24%
  • Execution failure (Chainlink Automation (migrating to Chainlink Runtime Environment) 8/10): you get a worse price, later, or nothing.
    Scored by The lateness the vendor will put in writing, and the conditions under which it declines to execute · 18%
  • Exit failure (Chainlink Automation (migrating to Chainlink Runtime Environment) 2/10): you cannot get out at par, on time, or with what is yours.
    Scored by Whether the job survives the vendor: who else can turn the crank, and what end-of-life is published · 30%
Every failure family that applies to this category is scored.