Celo

57%

Chain Quality Review

Celo

Chain Quality Review (0.1)

Celo

Final score:57%

Date:31 May 2024

Author:Rex

Audit Process:Version 0.1

Chain Score:57%

FAIL

Scoring Appendix

The final review score is indicated as a percentage. The percentage is calculated as Achieved Points due to MAX Possible Points. For each element the answer can be either Yes/No or a percentage. For a detailed breakdown of the individual weights of each question, please consult this document.

#QuestionAnswer

48%

1.30%

2.80%

3.20%

4.75%

46%

5.Yes

6.0%

7.10%

8.100%

9.100%

71%

10.Yes

11.100%

12.55%

13.0%

43%

14.100%

15.55%

16.Yes

17.0%

18.No

75%

19.100%

20.0%

Total:57%

DeFiSafety considers different aspects of what is important to an investor with respect to the safety of the blockchain they are using. The following ideals are prioritised:

The record of every transaction is always distributed and safe
The blockchain never ceases operation (is constantly processing transactions)
Changes to the blockchain software are carefully, publicly considered and tested before implementation
All aspects of the blockchain are well documented and public
The blockchain software is well tested and test results are documented
The blockchain software has been audited by skilled third parties and there is a bug bounty

This review answers these questions based on exclusively public data. The result is a simple score with a supporting explanation. We pride ourselves on the transparency of our analysis, and so all our answers have references. The process is be detailed in a separate document (not yet available).

This report is for informational purposes only and does not constitute investment advice of any kind, nor does it constitute an offer to provide investment advisory or other services. Nothing in this report shall be considered a solicitation or offer to buy or sell any security, token, future, option or other financial instrument or to offer or provide any investment advice or service to any person in any jurisdiction. Nothing contained in this report constitutes investment advice or offers any opinion with respect to the suitability of any security, and the views expressed in this report should not be taken as advice to buy, sell or hold any security. The information in this report should not be relied upon for the purpose of investing. In preparing the information contained in this report, we have not taken into account the investment needs, objectives and financial circumstances of any particular investor. This information has no regard to the specific investment objectives, financial situation and particular needs of any specific recipient of this information and investments discussed may not be suitable for all investors.

Any views expressed in this report by us were prepared based upon the information available to us at the time such views were written. The views expressed within this report are limited to DeFiSafety and the author and do not reflect those of any additional or third party and are strictly based upon DeFiSafety, its authors, interpretations and evaluation of relevant data. Changed or additional information could cause such views to change. All information is subject to possible correction. Information may quickly become unreliable for various reasons, including changes in market conditions or economic circumstances.

This completed report is copyright (c) DeFiSafety 2022. Permission is given to copy in whole, retaining this copyright label.

Nodes

48%

This section considers the questions on the blockchain’s nodes. It covers decentralization and therefore implicitly aspects of safety. This section covers the physical (hardware) nodes. The following section covers node software.

1. How many nodes execute software on the network? (%)

Answer: 30%

From 100-399 full nodes which gives a 30% score.

Percentage Score Guidance:

100%

3000 or more nodes

80%

1000 or less

30%

100-300

20%

25-100

10%

10-25

Less than 10

2. How many nodes store records of the transactions on the Network? (%)

Answer: 80%

Not sure but 300 to a 1000 is very reasonable, so 80%.

Percentage Score Guidance:

100%

3000 or more nodes

80%

1000 or less

30%

100-300

20%

25-100

10%

10-25

Less than 10

3. How geographically decentralized are the execution nodes? (%)

Answer: 20%

No data but probably decentralized. Say 20%,

Percentage Score Guidance:

100%

On 3 or more continents and 20 distant (1000 mi+) locations

70%

Nodes are in more than 10 locations with 5+ being of significant distance apart (1000 mi+)

40%

Nodes are in more than 6 locations with 2+ being of significant distance apart (1000 mi+)

20%

Nodes are in more than 3 locations

No public information/ nodes are in two or fewer locations

4. How accessible is becoming a validator or miner on the network? (%)

Answer: 75%

10,000 Celo at 0.8, meaning say $9000 (including HW). so 75%.

Percentage Score Guidance:

100%

Less than 1k in capital costs and permissionless validation

75%

Less than 50k in capital costs and permissionless validation

50%

Less than 100k in capital costs and permissionless validation

25%

Less than 200k in capital costs and permissionless validation

Anything above 200k or any form of permissioned validation

Node and supporting software

46%

The blockchain operation quality is driven by the node software. This section covers the software used by the node and the various supporting software suites provided to assist users who seek to validate the network.

5. Is there a public software repository? (Y/N)

Answer: Yes

Yes

Location: https://github.com/celo-org/celo-blockchain

6. How many different software implementations of the nodes are there? If this is a Layer 2, do not include Layer 1s. (%)

Answer: 0%

Just one

Percentage Score Guidance:

100%

4 or more implementations of node software

60%

3 implementations

40%

2 implementations

20%

A single implementation

7. For the last 6 (if available) implemented node software changes, how long was discussion/editing in GitHub? (%)

Answer: 10%

Unknown 10%

Percentage Score Guidance:

100%

Discussion duration is greater than 100 days

70%

Discussion duration is between 99 and 70 days

50%

Discussion duration is between 69 and 50 days

30%

Discussion duration is between 49 and 20 days

10%

Discussion duration is between 19 and 5 days

Discussion is less than 5 days

8. Can the public create a complete archive node? (%)

Answer: 100%

Yes

Reference: https://docs.celo.org/validator

Percentage Score Guidance:

100%

There is a documented public archive node process and this archive is reported stable and complete for last 3 months

50%

There is a documented public archive node process, but there are reported stability issues within last 3 months

There is no documented public archive node process

9. Does the block explorer have a full feature set? (%)

Answer: 100%

Yes

Reference: https://celoscan.io/tx/0xdb0baa60404abe41ff3c1e0fc32857e216eac96ed1b0739970709327dbd7ae6c

Percentage Score Guidance:

100%

The block explorer matches (or supersedes) all of Etherscan’s features (as identified in the tiers below)

80%

The block explorer contains all features below and quality-of-life improvements such as labels, token approval revoke tools, interaction analytics and DEX Trade lists

60%

The block explorer provides a complete archive of all chain activity with contract source code and transaction actions being displayed. In addition, all lower tiers are met

40%

All the below, as well as different token standards, internal transactions, token lists and source values are displayed

20%

The block explorer archives an incomplete account of a chain’s transaction history in a usable user interface. The gas price, network coin balance and to / from addresses are listed

The block explorer is of no utility in identifying chain activity

Documentation

71%

Being a public utility, a blockchain must have public, comprehensive documentation that is up to date with the latest node software.

10. Is there a whitepaper? (Y/N)

Answer: Yes

Yes

Reference: https://celo.org/papers

11. Is there architecture or system specification documentation for the nodes and blockchain’s operation? (%)

Answer: 100%

Good architecture document

Reference: https://docs.celo.org/general/architecture

Percentage Score Guidance:

100%

The blockchain and node operation is clearly described in architecture documentation PLUS there are documented system requirement documents for node software

70%

The blockchain and node operation clearly described in architecture documentation OR there are only system requirement documents

69 - 1%

Estimate of the level of architecture and system specification documentation

There is no architecture and system specification documentation

12. Does the software documentation fully cover the deployed node’s source code? (%)

Answer: 55%

55% as per their Github coverage indication

Reference: https://docs.celo.org/general/architecture

Percentage Score Guidance:

100%

All contracts and functions documented

60%

Only the major functions documented

59 - 1%

Estimate of the level of software documentation

No software documentation

13. Is it possible to trace the documented software to its implementation in the blockchain's source code? (%)

Answer: 0%

No traceability found

Percentage Score Guidance:

100%

Clear explicit traceability between code and documentation at a requirement level for all code

80%

Clear association between code and documents via non explicit traceability

40%

Estimate of the level of software documentation

No connection between documentation and code

Testing

43%

This section looks at the test suite for the node and other supporting software.

14. Has the blockchain tested their deployed code? (%)

Answer: 100%

Yes

Percentage Score Guidance:

100%

TtC > 120% Both unit and system test visible

80%

TtC > 80% Both unit and system test visible

40%

TtC < 80% Some tests visible

No tests obvious

15. What is the code coverage of the blockchain? (%)

Answer: 55%

55% as per their Github coverage indication

Percentage Score Guidance:

100%

Documented full coverage

99 - 51%

Value of test coverage from documented results

50%

No indication of code coverage but clearly there is a complete set of tests

30%

Some tests evident but not complete

No tests for coverage seen

16. Do the developers provide scripts and instructions to run their tests? (Y/N)

Answer: Yes

Enter data here

Location: https://github.com/celo-org/celo-blockchain

17. Is there a detailed report of the blockchain’s test results? (%)

Answer: 0%

No test report

Percentage Score Guidance:

100%

Detailed test report as described below

70%

GitHub code coverage report visible

No test report evident

18. Has the blockchain undergone Formal Verification? (Y/N)

Answer: No

Security

75%

19. Has the node software been sufficiently audited? (%)

Answer: 100%

Yes

Location: https://celo.org/audits

Percentage Score Guidance:

100%

Audits specific to the chain and latest software node release and within 3 months of the latest release

70%

Audits specific to the chain and older than 3 months

50%

Audits specific to a similar chain and within 3 months or a few small releases

30%

Audits specific to a similar chain

No audit report evident

20. Is the bounty value acceptably high? (%)

Answer: 0%

Yes, but no amount is specified.

Location: https://celo.org/security-bugs

Percentage Score Guidance:

100%

Bounty is at least $1M AND active program

90%

Bounty is at least 500k AND active program

80%

Bounty is at least 500k

70%

Bounty is 100k or over AND active program

60%

Bounty is 100k or over

50%

Bounty is 50k or over AND active program

40%

Bounty is 50k or over

20%

Bug bounty program bounty is less than 50k

No bug bounty program offered

Appendices

null

1Enter appendix example code here

N/A