logo
bg_imgbg_imgbg_imgbg_img
exclamation mark iconReport an issue

If you notice some outdated information please let us know!

close icon
Name
Email
Your message
arrow-left

TempleDAO

81%

Process Quality Review (0.8)

TempleDAO

Final score:81%
Date:01 Aug 2022
Audit Process:version 0.8
Author:Lena
PQR Score:81%

PASS

Protocol Website:https://templedao.link

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.

The blockchain used by this protocol
Arbitrum
Ethereum
Polygon
Optimism
#QuestionAnswer
78%
1.100%
2.100%
3.Yes
4.100%
5.0
14%
6.Yes
7.No
8.0%
9.0%
80%
10.100%
11.50%
12.Yes
13.100%
14.No
15.Yes
87%
16.90%
17.70%
97%
18.100%
19.100%
20.100%
21.100%
22.100%
23.80%
24.100%
25.100%
100%
26.100%
27.Yes
28.Yes
Total:81%

Very simply, the audit looks for the following declarations from the developer's site. With these declarations, it is reasonable to trust the smart contracts.

  • Here is my smart contract on the blockchain
  • You can see it matches a software repository used to develop the code
  • Here is the documentation that explains what my smart contract does
  • Here are the tests I ran to verify my smart contract
  • Here are the audit(s) performed to review my code by third party experts

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 2021. Permission is given to copy in whole, retaining this copyright label.

Smart Contracts & Team

78%

This section looks at the code deployed on the relevant chain that gets reviewed and its corresponding software repository. The document explaining these questions is here.

1. Are the smart contract addresses easy to find? (%)

Answer: 100%

TempleDAO's addresses can be found at this location, as indicated in the Appendix. These were clearly labelled and easy to find.

Percentage Score Guidance:
100%
Clearly labelled and on website, documents or repository, quick to find
70%
Clearly labelled and on website, docs or repo but takes a bit of looking
40%
Addresses in mainnet.json, in discord or sub graph, etc
20%
Address found but labeling not clear or easy to find
0%
Executing addresses could not be found

2. How active is the primary contract? (%)

Answer: 100%

Contract VaultProxy is used up to 14 times a day, as indicated in the Appendix.

Percentage Score Guidance:
100%
More than 10 transactions a day
70%
More than 10 transactions a week
40%
More than 10 transactions a month
10%
Less than 10 transactions a month
0%
No activity

3. Does the protocol have a public software repository? (Y/N)

Answer: Yes

TempleDao stores their repositories in Github.

Score Guidance:
Yes
There is a public software repository with the code at a minimum, but also normally test and scripts. Even if the repository was created just to hold the files and has just 1 transaction.
No
For teams with private repositories.

4. Is there a development history visible? (%)

Answer: 100%

At 908 commits and 24 branches, the temple repo has good development history.

Percentage Score Guidance:
100%
Any one of 100+ commits, 10+branches
70%
Any one of 70+ commits, 7+branches
50%
Any one of 50+ commits, 5+branches
30%
Any one of 30+ commits, 3+branches
0%
Less than 2 branches or less than 30 commits

5. Is the team public (not anonymous)?

Answer: 0

TempleDao's white paper indicates that the team behind TempleDao remains anonymous.

Score Guidance:
100%
At least two names can be easily found in the protocol's website, documentation or medium. These are then confirmed by the personal websites of the individuals / their linkedin / twitter.
50%
At least one public name can be found to be working on the protocol.
0%
No public team members could be found.

Documentation

14%

This section looks at the software documentation. The document explaining these questions is here.

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

Answer: Yes

Location: https://docs.templedao.link

7. Is the protocol's software architecture documented? (Y/N)

Answer: No

No software architecture found.

Score Guidance:
Yes
The documents identify software architecture and contract interaction through any of the following: diagrams, arrows, specific reference to software functions or a written explanation on how smart contracts interact.
No
Protocols receive a "no" if none of these are included.

8. Does the software documentation fully cover the deployed contracts' source code? (%)

Answer: 0%

No software architecture found.

Percentage Score Guidance:
100%
All contracts and functions documented
80%
Only the major functions documented
79 - 1%
Estimate of the level of software documentation
0%
No software documentation

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

Answer: 0%

No software architecture found.

Percentage Score Guidance:
100%
Clear explicit traceability between code and documentation at a requirement level for all code
60%
Clear association between code and documents via non explicit traceability
40%
Documentation lists all the functions and describes their functions
0%
No connection between documentation and code

Testing

80%

10. Has the protocol tested their deployed code? (%)

Answer: 100%

Testing files could not be found.    Code examples are in the Appendix at the end of this report.. As per the SLOC, there is 189% testing to code (TtC).    This score is guided by the Test to Code ratio (TtC). Generally a good test to code ratio is over 100%. However, the reviewer's best judgement is the final deciding factor.

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
0%
No tests obvious

11. How covered is the protocol's code? (%)

Answer: 50%

No code coverage report found but there is a clear complete set of tests.

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
0%
No test for coverage seen

12. Does the protocol provide scripts and instructions to run their tests? (Y/N)

Answer: Yes

Test instructions can be found in the temple repo README.md here.

Score Guidance:
Yes
Scripts and/or instructions to run tests are available in the testing suite
No
Scripts and/or instructions to run tests are not available in the testing suite

13. Is there a detailed report of the protocol's test results?(%)

Answer: 100%

Test reports can be found in the temple repo CI; here is an example.

Percentage Score Guidance:
100%
Detailed test report as described below
70%
GitHub code coverage report visible
0%
No test report evident

14. Has the protocol undergone Formal Verification? (Y/N)

Answer: No

TempleDAO has not undergone formal verification.

Score Guidance:
Yes
Formal Verification was performed and the report is readily available
No
Formal Verification was not performed and/or the report is not readily available.

15. Were the smart contracts deployed to a testnet? (Y/N)

Answer: Yes

TempleDao has testnet deployment documentation here.

Score Guidance:
Yes
Protocol has proved their tesnet usage by providing the addresses
No
Protocol has not proved their testnet usage by providing the addresses

Security

87%

This section looks at the 3rd party software audits done. It is explained in this document.

16. Is the protocol sufficiently audited? (%)

Answer: 90%

TempleDAO has been audited once before deployment. Their PeckShield audit lists 4 issues of varying severity, 2 of which have not yet been fixed, one of which is of medium severity.

Percentage Score Guidance:
100%
Multiple Audits performed before deployment and the audit findings are public and implemented or not required
90%
Single audit performed before deployment and audit findings are public and implemented or not required
70%
Audit(s) performed after deployment and no changes required. The Audit report is public.
65%
Code is forked from an already audited protocol and a changelog is provided explaining why forked code was used and what changes were made. This changelog must justify why the changes made do not affect the audit.
50%
Audit(s) performed after deployment and changes are needed but not implemented.
30%
Audit(s) performed are low-quality and do not indicate proper due diligence.
20%
No audit performed
0%
Audit Performed after deployment, existence is public, report is not public OR smart contract address' not found.
Deduct 25% if the audited code is not available for comparison.

17. Is the bounty value acceptably high (%)

Answer: 70%

TempleDAO offers an active bug bounty of up to $310.8K with Hats Finance. View TempleDAO's medium article here for more details.

Percentage Score Guidance:
100%
Bounty is 10% TVL or at least $1M AND active program (see below)
90%
Bounty is 5% TVL or at least 500k AND active program
80%
Bounty is 5% TVL or 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
0%
No bug bounty program offered / the bug bounty program is dead
An active program means that a third party (such as Immunefi) is actively driving hackers to the site. An inactive program would be static mentions on the docs.

Admin Controls

97%

This section covers the documentation of special access controls for a DeFi protocol. The admin access controls are the contracts that allow updating contracts or coefficients in the protocol. Since these contracts can allow the protocol admins to "change the rules", complete disclosure of capabilities is vital for user's transparency. It is explained in this document.

18. Is the protocol's admin control information easy to find?

Answer: 100%

Admin control information can be found on the protocol's Admin Controls page.

Percentage Score Guidance:
100%
Admin Controls are clearly labelled and on website, docs or repo, quick to find
70%
Admin Controls are clearly labelled and on website, docs or repo but takes a bit of looking
40%
Admin Control docs are in multiple places and not well labelled
20%
Admin Control docs are in multiple places and not labelled
0%
Admin Control information could not be found

19. Are relevant contracts clearly labelled as upgradeable or immutable? (%)

Answer: 100%

TempleDAO's contracts are labelled as immutable here.

Percentage Score Guidance:
100%
Both the contract documentation and the smart contract code state that the code is not upgradeable or immutable.
80%
All Contracts are clearly labelled as upgradeable (or not)
50%
Code is immutable but not mentioned anywhere in the documentation
0%
Admin control information could not be found

20. Is the type of smart contract ownership clearly indicated? (%)

Answer: 100%

The protocol's admin controls' page indicates smart contract ownership to be multisig when it comes to the Gnosis Safe treasury and administration, while protocol policies and on-chain operations are restricted by OnlyOwner here.    Example of OnlyOwner code line in MintAllowance.sol contract here.

Percentage Score Guidance:
100%
The type of ownership is clearly indicated in their documentation. (OnlyOwner / MultiSig / etc)
50%
The type of ownership is indicated, but only in the code. (OnlyOwner / MultiSig / etc)
0%
Admin Control information could not be found

21. Are the protocol's smart contract change capabilities described? (%)

Answer: 100%

TempleDAO's contracts are labelled as immutable here and the mutable policies are indicated here.

Percentage Score Guidance:
100%
The documentation covers the capabilities for change for all smart contracts
50%
The documentation covers the capabilities for change in some, but not all contracts
0%
The documentation does not cover the capabilities for change in any contract

22. Is the protocol's admin control information easy to understand? (%)

Answer: 100%

TempleDAO's admin control information is clear and easy to understand.

Percentage Score Guidance:
100%
All the contracts are immutable
90%
Description relates to investments safety in clear non-software language
30%
Description all in software-specific language
0%
No admin control information could be found

23. Is there sufficient Pause Control documentation? (%)

Answer: 80%

TempleDAO's pause controls are documented here. This includes contracts affected by the pause controls and measures used if pause controls are necessary in specific situations.

Percentage Score Guidance:
100%
Pause control(s) are clearly documented and there is records of at least one test within 3 months
80%
Pause control(s) explained clearly but no evidence of regular tests
40%
Pause controls mentioned with no detail on capability or tests
0%
Pause control not documented or explained

24. Is there sufficient Timelock documentation? (%)

Answer: 100%

The protocol identifies why timelocks are not necessary in their Timelock documentation.

Percentage Score Guidance:
100%
Documentation identifies and explains why the protocol does not need a Timelock OR Timelock documentation identifies its duration, which contracts it applies to and justifies this time period.
60%
A Timelock is identified and its duration is specified
30%
A Timelock is identified
0%
No Timelock information was documented

25. Is the Timelock of an adequate length? (Y/N)

Answer: 100%

The protocol identifies why timelocks are not necessary in their Timelock documentation.

Percentage Score Guidance:
100%
Timelock is between 48 hours to 1 week OR justification as to why no Timelock is needed / is outside this length.
50%
Timelock is less than 48 hours or greater than 1 week.
0%
No Timelock information was documented OR no timelock length was identified.

Oracles

100%

This section goes over the documentation that a protocol may or may not supply about their Oracle usage. Oracles are a fundamental part of DeFi as they are responsible for relaying tons of price data information to thousands of protocols using blockchain technology. Not only are they important for price feeds, but they are also an essential component of transaction verification and security. These questions are explained in this document.

26. Is the protocol's Oracle sufficiently documented? (%)

Answer: 100%

TempleDAO clearly outlines that they do not use any oracle here.

Percentage Score Guidance:
100%
If it uses one, the Oracle is specified. The contracts dependent on the oracle are identified. Basic software functions are identified (if the protocol provides its own price feed data). Timeframe of price feeds are identified. OR The reason as to why the protocol does not use an Oracle is identified and explained.
75%
The Oracle documentation identifies both source and timeframe, but does not provide additional context regarding smart contracts.
50%
Only the Oracle source is identified.
0%
No oracle is named / no oracle information is documented.

27. Is front running mitigated by this protocol? (Y/N)

Answer: Yes

TempleDAO mentions a max slippage setting on their AMM as a mitigation technique to make frontrunning not profitable.

Score Guidance:
Yes
The protocol cannot be front run and there is an explanation as to why OR documented front running countermeasures are implemented.
No
The Oracle documentation identifies both source and timeframe, but does not provide additional context regarding smart contracts.

28. Can flashloan attacks be applied to the protocol, and if so, are those flashloan attack risks mitigated? (Y/N)

Answer: Yes

The protocol clearly outlines that flashloan attacks are not applicable to their protocol due to the locked fund function here.

Score Guidance:
Yes
The protocol's documentation includes information on how they mitigate the possibilities and extents of flash loan attacks.
No
The protocol's documentation does not include any information regarding the mitigation of flash loan attacks.

Appendices

null
1pragma solidity ^0.8.4;
2// SPDX-License-Identifier: AGPL-3.0-or-later
3
4import "@openzeppelin/contracts/access/Ownable.sol";
5import "@openzeppelin/contracts/token/ERC20/utils/SafeERC20.sol";
6
7import "./Vault.sol";
8import "../ABDKMathQuad.sol";
9import "../OGTemple.sol";
10import "../TempleERC20Token.sol";
11import "../TempleStaking.sol";
12import "../devotion/Faith.sol";
13
14/**
15    @notice A proxy contract for interacting with Temple Vaults. 
16 */
17contract VaultProxy is Ownable {
18    using ABDKMathQuad for bytes16;
19    /** @notice Tokens / Contracted required for the proxy contract  */
20    OGTemple public immutable ogTemple;
21    TempleERC20Token public immutable temple;
22    TempleStaking public immutable templeStaking;
23    Faith public immutable faith;
24    bool public faithClaimEnabled;
25
26    constructor(
27        OGTemple _ogTemple,
28        TempleERC20Token _temple,
29        TempleStaking _templeStaking,
30        Faith _faith
31    ) {
32        ogTemple = _ogTemple;
33        temple = _temple;
34        templeStaking = _templeStaking;
35        faith = _faith;
36        faithClaimEnabled = true;
37    }
38
39    bytes16 private constant MAX_MULT = 0x3fff4ccccccccccccccccccccccccccc; // 1.3
40    bytes16 private constant TA_MULT = 0x40004000000000000000000000000000; // 2.5
41
42    /**
43        @notice Given an amount of Faith and Temple, apply the boosting curve and produce the amount of boosted Temple one can expect to receive.
44                Formula is BoostedTemple = TempleProvided * min(1.3, (1+faith/(2.5*TempleProvided)))
45     */
46    function getFaithMultiplier(uint256 _amountFaith, uint256 _amountTemple) pure public returns (uint256) {
47        // Tl = Ta * min(1.3, (1+faith/2.5*Ta))
48        bytes16 amountFaith = ABDKMathQuad.fromUInt(_amountFaith);
49        bytes16 amountTemple = ABDKMathQuad.fromUInt(_amountTemple);
50        bytes16 t = ABDKMathQuad.fromUInt(1).add(amountFaith.div(TA_MULT.mul(amountTemple)));
51        bytes16 mult = MAX_MULT < t ? MAX_MULT : t;
52
53        return ABDKMathQuad.toUInt(amountTemple.mul(mult));
54    }
55
56    /**
57        @notice Takes provided faith and Temple, applies the boost then immediate deposits into a vault
58     */
59    function depositTempleWithFaith(uint256 _amountTemple, uint112 _amountFaith, Vault vault) public {
60        require(faithClaimEnabled, "VaultProxy: Faith claim no longer enabled");
61        faith.redeem(msg.sender, _amountFaith);
62        uint256 boostedAmount = getFaithMultiplier(_amountFaith, _amountTemple);
63        SafeERC20.safeTransferFrom(temple, msg.sender, address(this), _amountTemple);
64        SafeERC20.safeIncreaseAllowance(temple, address(vault), boostedAmount);
65        vault.depositFor(msg.sender, boostedAmount);
66    }
67
68    /**
69        @notice Takes provided faith and OGT, unstakes the OGT into Temple, applies the boost and then immediately
70        deposits into a vault
71     */
72    function unstakeAndDepositTempleWithFaith(uint256 _amountOGT, uint112 _amountFaith, Vault vault) external {
73        require(faithClaimEnabled, "VaultProxy: Faith claim no longer enabled");
74        faith.redeem(msg.sender, _amountFaith);
75        uint256 unstakedTemple = unstakeOGT(_amountOGT);
76        uint256 boostedAmount = getFaithMultiplier(_amountFaith, unstakedTemple);
77        SafeERC20.safeIncreaseAllowance(temple, address(vault), boostedAmount);
78        vault.depositFor(msg.sender, boostedAmount);
79    }
80
81    /**
82        @notice Takes provided OGT, unstakes into Temple and immediately deposits into a vault
83     */
84    function unstakeAndDepositIntoVault(uint256 _amountOGT, Vault vault) external {
85        uint256 unstakedTemple = unstakeOGT(_amountOGT);
86        SafeERC20.safeIncreaseAllowance(temple, address(vault), unstakedTemple);
87        vault.depositFor(msg.sender, unstakedTemple);
88    }
89    
90    /**
91        @notice Private function which will take OGT, unstake it, ensure correct amount came back and then pass back 
92        to the calling function.
93     */
94    function unstakeOGT(uint256 _amountOGT) private returns (uint256) {
95        SafeERC20.safeIncreaseAllowance(ogTemple, address(templeStaking), _amountOGT);
96        SafeERC20.safeTransferFrom(ogTemple, msg.sender, address(this), _amountOGT);
97        
98        uint256 templeBeforeBalance = temple.balanceOf(address(this));
99        templeStaking.unstake(_amountOGT);
100        uint256 templeAfterBalance = temple.balanceOf(address(this));
101        require(templeAfterBalance > templeBeforeBalance, "Vault Proxy: no Temple received when unstaking");
102
103        return templeAfterBalance - templeBeforeBalance;
104    }
105
106    /**
107        @notice A proxy function for depositing into a vault; useful if we wish to limit number of approvals to one, rather than for each underlying 
108                vault instance. 
109     */
110    function depositTempleFor(uint256 _amount, Vault vault) public {
111        SafeERC20.safeIncreaseAllowance(temple, address(vault), _amount);
112        SafeERC20.safeTransferFrom(temple, msg.sender, address(this), _amount);
113        vault.depositFor(msg.sender, _amount);
114    }
115
116    /**
117    * Toggle whether faith is claimable
118    */
119    function toggleFaithClaimEnabled() external onlyOwner {
120        faithClaimEnabled = !faithClaimEnabled;
121    }
122
123    /**
124    * transfer out amount of token to provided address
125    */
126    function withdraw(address token, address to, uint256 amount) external onlyOwner {
127        require(to != address(0), "to address zero");
128
129        if (token == address(0)) {
130            (bool sent,) = payable(to).call{value: amount}("");
131            require(sent, "send failed");
132        } else {
133            SafeERC20.safeTransfer(IERC20(token), to, amount);
134        }
135    }
136}

JavaScript Tests

Language
Files
Lines
Blanks
Comments
Testing Code
Deployed Code
Complexity
Javascript
11
1647
245
408
0
994
169
Solidity
26
4706
860
324
3522
1893
59
Total
37
6353
1105
732
3522
2887
228

Tests to Code: 3522 / 994 = 354 %