Difference between revisions of "TempleDAO (TEMPLE)"
(→Basics) |
|||
| Line 13: | Line 13: | ||
''Our only comment would be regarding the protocol’s architecture and function documentation. The devs have been explicitly showing efforts into setting up the required documentation, and we’re not concerned that this will be answered very soon."'' | ''Our only comment would be regarding the protocol’s architecture and function documentation. The devs have been explicitly showing efforts into setting up the required documentation, and we’re not concerned that this will be answered very soon."'' | ||
But in the actual [https://www.defisafety.com/app/pqrs/494 report] it states: | |||
''"TempleDAO has been audited once before deployment. Their [[Peckshield|PeckShield]] [https://3192837185-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McG7st47-ZST4fx_Lnt%2Fuploads%2FhRrFwxgDBgVriVZHYGuX%2FPeckShield%20Audit%20Report-TempleDAO%20Core.pdf?alt=media&token=893f28e7-5bb4-4120-a364-28004a0e64f5 audit] lists 4 issues of varying severity, 2 of which have not yet been fixed, one of which is of [[medium]] severity."'' | |||
===Bugs/Exploits=== | ===Bugs/Exploits=== | ||
==Governance== | ==Governance== | ||
===Admin Keys=== | ===Admin Keys=== | ||
* [https://www.defisafety.com/app/pqrs/494 From] [[DeFi Safety]] (1-8-2022): | |||
''"TempleDAO's [[contracts]] are labelled as [[immutable]] [https://docs.templedao.link/technical-reference/admin-controls#contract-ownership here] and the mutable policies are indicated [https://docs.templedao.link/technical-reference/admin-controls#mutable-policies here]. The protocol's [[admin controls]]' page indicates smart [[contract]] ownership to be [[Multi-Signature|multisig]] when it comes to the [[Gnosis]] [[Safe (SAFE)|Safe]] treasury and administration, while protocol policies and [[On Chain|on-chain]] operations are restricted by OnlyOwner [https://docs.templedao.link/technical-reference/admin-controls#contract-ownership here].'' | |||
''The protocol identifies why timelocks are not necessary in their [[Timelock]] [https://docs.templedao.link/technical-reference/admin-controls#timelocks documentation]."'' | |||
===DAO=== | ===DAO=== | ||
===Treasury=== | ===Treasury=== | ||
| Line 27: | Line 37: | ||
==Coin Distribution== | ==Coin Distribution== | ||
==Technology== | ==Technology== | ||
*[[Whitepaper]] or docs can be found [ | *[[Whitepaper]] or docs can be found [https://docs.templedao.link/ here]. | ||
*Code can be viewed [https://github.com/TempleDAO here]. | *Code can be viewed [https://github.com/TempleDAO here]. [https://www.defisafety.com/app/pqrs/494 From] [[DeFi Safety]] (1-8-2022): | ||
''"At 908 commits and 24 branches, the temple repo has good development history."'' | |||
===Implementations=== | ===Implementations=== | ||
*Built on: [[Ethereum (ETH)|Ethereum]] | *Built on: [[Ethereum (ETH)|Ethereum]], [[Arbitrum]],, [[Polygon (MATIC)|Polygon]] and [[Optimism (OP)|Optimism]] (1-8-2022). | ||
===How it works=== | ===How it works=== | ||
===Fees=== | ===Fees=== | ||
| Line 37: | Line 49: | ||
====Validator Stats==== | ====Validator Stats==== | ||
===Liquidity Mining=== | ===Liquidity Mining=== | ||
===Interoperability=== | ===Interoperability=== | ||
===Other Details=== | ===Other Details=== | ||
==Oracle Method== | ==Oracle Method== | ||
* [https://www.defisafety.com/app/pqrs/494 From] [[DeFi Safety]] (1-8-2022): | |||
''"TempleDAO clearly outlines that they do not use any [[oracle]] [https://docs.templedao.link/technical-reference/risks#oracles here]. TempleDAO mentions a max slippage setting on their [[Automated Market Makers (AMM)|AMM]] as a mitigation technique to make [[frontrunning]] not profitable. The protocol clearly outlines that [[Flash Loan|flashloan]] attacks are not applicable to their protocol due to the locked fund function [https://docs.templedao.link/technical-reference/risks#frontrunning here]."'' | |||
==Their Other Projects== | ==Their Other Projects== | ||
==Roadmap== | ==Roadmap== | ||
*Can be found [Insert link here]. | *Can be found [Insert [[LINK|link]] here]. | ||
==Usage== | ==Usage== | ||
===Projects that use or built on it=== | ===Projects that use or built on it=== | ||
| Line 54: | Line 68: | ||
==Team, Funding and Partners== | ==Team, Funding and Partners== | ||
===Team=== | ===Team=== | ||
* | *TempleDao' [https://docs.templedao.link/ docs] indicates that the team behind TempleDao remains anonymous. | ||
===Funding=== | ===Funding=== | ||
===Partners=== | ===Partners=== | ||
Revision as of 02:04, 22 August 2022
Yield farming protocol
Basics
History
Audits & Exploits
- Bug bounty program can be found [insert here].
- Scored 82% on DeFi Safety (2-8-2022):
"DeFiSafety’s Whispers have been heard; TempleDAO was very collaborative in increasing their scores and it is our pleasure to announce the protocol has scored a high 82% and is still working on improving their documentation. With spotless Oracles, Admin Controls as well as meticulous security and testing, there isn’t much that the Temple team requires prayers for. This is completed by an audit, $310K bug bounty, immutable contracts, flash loan and front running mitigation, the team has it all.
Our only comment would be regarding the protocol’s architecture and function documentation. The devs have been explicitly showing efforts into setting up the required documentation, and we’re not concerned that this will be answered very soon."
But in the actual report it states:
"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."
Bugs/Exploits
Governance
Admin Keys
- From DeFi Safety (1-8-2022):
"TempleDAO's contracts are labelled as immutable here and the mutable policies are indicated here. 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. The protocol identifies why timelocks are not necessary in their Timelock documentation."
DAO
Treasury
Token
Launch
Token Allocation
Utility
Other Details
Stablecoin
Coin Distribution
Technology
- Whitepaper or docs can be found here.
- Code can be viewed here. From DeFi Safety (1-8-2022):
"At 908 commits and 24 branches, the temple repo has good development history."
Implementations
How it works
Fees
Upgrades
Staking
Validator Stats
Liquidity Mining
Interoperability
Other Details
Oracle Method
- From DeFi Safety (1-8-2022):
"TempleDAO clearly outlines that they do not use any oracle here. TempleDAO mentions a max slippage setting on their AMM as a mitigation technique to make frontrunning not profitable. The protocol clearly outlines that flashloan attacks are not applicable to their protocol due to the locked fund function here."
Their Other Projects
Roadmap
- Can be found [Insert link here].
Usage
Projects that use or built on it
Competition
Pros and Cons
Pros
Cons
Team, Funding and Partners
Team
- TempleDao' docs indicates that the team behind TempleDao remains anonymous.
Funding
Partners
(:
Knowledge empowers all and will help us get closer to the decentralized world we all want to live in!
Making these free wiki pages is fun but takes a lot of effort and time.
If you have enjoyed reading, tips are appreciated :) This will help us to keep expanding this archive of information.
