|
|
| Line 1: |
Line 1: |
| ==Basics==
| | Recently, several criticisms related to CryptoWiki [[Discord]] were highlighted publicly by a user we banned. As such, we're obliged to also react to them publicly. |
|
| |
|
| *Based in:
| | First, we admit our moderation standards didn't always [[keep]] up with the growth of the CryptoWiki discord. What started as a place for CryptoWiki editors to hang out (a community we thought required pretty much no moderation) grew bigger and bigger and we didn't keep up. The unpunished n-word screenshots (from 2020) are a symptom of that issue. As the community grown we had to cut more and more of the "hang out" and discussion areas as they are incredibly hard to moderate, and we refocused on promoting ontopic discussion as much as possible. Today, our moderation standards are way higher, the n-word is completely banned (as probably should have been from the beginning but none of us thought of that) and we try to get rid of people who don't have an interest in ontopic discussion and only bring memes/drama/fakes. Funnily enough, the exposé criticiczes both our lack of moderation in the early days and our "too strict" moderation now. |
| *Started in / Announced on:
| |
| *[[Testnet]] release:
| |
| *[[Mainnet]] release:
| |
| *[[Yield farming]] and fundraising
| |
|
| |
|
| ==History==
| | Personal DM communications of some mods flew under our radar and we will work on having a more professional communication from them in the future, forwarding the concerns to others if they can't handle them. That said, I personally (jagotu) replied to every single of the user's DMs professionally and didn't [[block]] them on any platforms and they only talked to me once, yet they kept on bringing up their ban with regular mods who were handling the situation a bit worse. My DMs are open on all platforms and I was listening. |
| | |
| == Audits & Exploits ==
| |
| *[[Bug bounty]] program can be found [https://immunefi.com/bounty/impossiblefinance/ here] (26-5-2022):
| |
| ''"Impossible Finance offers an active bug bounty of $94K. In addition, the bounty will also payout 10% of the funds at risk within a found attack vector. If a bug is found that would cause the loss of Impossible's entire [[Total Value Locked (TVL)|TVL]], the whitehat hacker would effectively get paid 10% of Impossible's TVL."''
| |
| *Scored [https://www.defisafety.com/app/pqrs/445 94%] by [[DeFi Safety]] (26-5-2022):
| |
| ''"Impossible's TtC coverage is 174%. However, it is important to note that testing was only found for the launchpad [[contracts]], but not for the staking or trading ones. Nevertheless, Launchpad is Impossible's main offering and it is adequately tested as per our standards. No test for coverage seen. However, Impossible does have some solid Launchpad testing. As such, 50% will be given here. No testing reports/CI found in their repos or "Actions" tab. Impossible Finance has not undergone formal verification.''
| |
| | |
| ''Impossible Finance has been audited multiple times both pre-deployment and post deployment. Audit reports can be found [https://github.com/ImpossibleFinance/audits here]."''
| |
| | |
| With the [https://impossiblefinance.notion.site/Contract-Addresses-Docs-Details-8f357cb16b844e89a759b28264a23eae comment]:
| |
| | |
| ''"Firstly, the launchpad provider had a decent running start in our core transparency metrics. [[Address|Addresses]] are public and easily found, devs are doxxed, technical documentation was present, and the well-maintained [[Github|GitHub]] contained fully [[Open Source|open-source]] software.''
| |
| | |
| ''However, one thing that was clearly missing was [[Admin Key|admin control]] information. Upon establishing contact with the developers, they worked very hard to produce this important document. It can now be found here: <nowiki>https://impossiblefinance.notion.site/Contract-Addresses-Docs-Details-8f357cb16b844e89a759b28264a23eae</nowiki>. Secondly, this aforementioned document contains all the high-level information needed to evaluate Impossible Finance's [[admin controls]]. Core contracts are [[immutable]], ownership is through a [[Multi-Signature|MultiSig]], and change capabilities are restricted to trading [[fees]] and [[Whitelist|whitelisting]].''
| |
| | |
| ''Moreover, there is also a breakdown of how Impossible mitigates the risk of [[Frontrunners|front running]] and [[Flash Loan|flash loan]] manipulations. With asymmetric boosts and [[staking]] allocations proportionate to [[stake]] amount held over time, Impossible's mechanisms capitalize on risk mitigation.''
| |
| | |
| ''Lastly, the protocol shows a dedication to security via multiple pre-deployment audits for each protocol deployment and a sizeable [[bug bounty]] that will reward [[Whitehat|whitehats]] with up to 10% of total capital "saved" through attack vector disclosures.''
| |
| | |
| ''In the future, we would love to see Impossible further develop its testing suite with the addition of code coverage and unit tests, detailed testing reports, and a formal verification. We will be monitoring these additions closely and update the report as they are added. All of that to say, Impossible Finance's process quality standards are extremely high. The protocol architecture and security measures were certainly well thought out, and we are looking forward to newer protocols utilizing its innovative launchpad in the future."''
| |
| | |
| ===Bugs/Exploits===
| |
| *[https://twitter.com/WatchPug_/status/1406872310368268288 From] [[WatchPug]] (21-6-2021):
| |
| | |
| ''"$0.5M was stolen from Impossible Finance. The hacker made multiple [[swaps]] in a row at about the same price and drained the [[Liquidity Provider (LP)|LP]], which is usually impossible."''
| |
| ==Governance==
| |
| ===Admin Key===
| |
| | |
| * [https://www.defisafety.com/app/pqrs/445 From] [[DeFi Safety]] (26-5-2022):
| |
| | |
| ''"[[Admin Key|Admin control]] information is documented at this [https://impossiblefinance.notion.site/Contract-Addresses-Docs-Details-8f357cb16b844e89a759b28264a23eae location], and can easily be found. Impossible clearly identifies their [[Smart Contract (SC)|smart contracts]] as immutable [https://impossiblefinance.notion.site/Contract-Addresses-Docs-Details-8f357cb16b844e89a759b28264a23eae here]. Ownership is [[Multi-Signature|MultiSig]] and clearly indicated in this [https://impossiblefinance.notion.site/Contract-Addresses-Docs-Details-8f357cb16b844e89a759b28264a23eae location]. Impossible [[smart contracts]] are immutable at the core level, and smart [[contract]] change capabilities are described [https://impossiblefinance.notion.site/Contract-Addresses-Docs-Details-8f357cb16b844e89a759b28264a23eae here] at a granular level. Impossible's core protocol is immutable, but granular parameters such as trading pairs can be paused. Since Impossible is immutable, they have no need for a core [[timelock]]. However, any swap changes incur a [[block]] delay on the [[blockchain]], which effectively act as a time delay for swap upgrades. In addition, Impossible can retrieve funds from the launchpad in the event of an emergency, but this function is initially locked for months. Furthermore, "The admin does not have any ability to be able to take custody of users funds, and that fees also have a max limit of what they can be set to to prevent the [[multisig]] from raising fees to 100% to hurt users or drain any protocol activities."''
| |
| | |
| ===DAO===
| |
| ===Treasury===
| |
| ==Token==
| |
| ===Launch===
| |
| ===Token Allocation===
| |
| ===Utility===
| |
| ===Other Details===
| |
| ===Stablecoin===
| |
| ==Coin Distribution==
| |
| ==Technology==
| |
| | |
| *[[Whitepaper]] can be found [https://gateway.pinata.cloud/ipfs/QmSXzevkMPU3z2nZFthEvzdzwpbXDR8Em62XqkKw8g4hTR/Impossible%20Finance%20IDIA%20Official%20Whitepaper.pdf here].
| |
| *Code can be viewed [https://github.com/impossiblefinance here]. [https://www.defisafety.com/app/pqrs/445 From] [[DeFi Safety]] (26-5-2022):
| |
| ''"At 313 commits and 26 branches, we didn't know a development history like this was possible."''
| |
| | |
| ===Implementations===
| |
| | |
| *Built on: [[Binance|BSC]], [[Ethereum (ETH)|Ethereum]] and [[Polygon (MATIC)|Polygon]] ([https://www.defisafety.com/app/pqrs/445 26-5-2022]).
| |
| | |
| ===How it works===
| |
| ===Fees===
| |
| ===Upgrades===
| |
| ===Staking===
| |
| ====Validator Stats====
| |
| ===Liquidity Mining===
| |
| ===Scaling===
| |
| ===Interoperability===
| |
| ===Other Details===
| |
| ==Oracle Method==
| |
| | |
| * [https://www.defisafety.com/app/pqrs/445 From] [[DeFi Safety]] (26-5-2022):
| |
| | |
| Impossible does not use [[Oracle|oracles]] due to all pool prices being "calculated directly from the supply of [[tokens]] in the swap itself. There are no other [[derivatives]] or price feed reliances in the Impossible Finance ecosystem" that would require a price feed [[oracle]]. The Impossible launchpad does have any time preference, meaning that there are no [[Frontrunners|front-running]] opportunities there. Moreover, the Impossible swap has an asymmetric boost - which reduces slippage due to higher [[liquidity]] parameters. All this information is readily available [https://impossiblefinance.notion.site/Contract-Addresses-Docs-Details-8f357cb16b844e89a759b28264a23eae here].
| |
| | |
| ==Compliance==
| |
| ==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, Partners==
| |
| ===Team===
| |
| | |
| *Full team can be found [here].
| |
| | |
| ===Funding===
| |
| ===Partners===
| |
| ==(:==
| |
| Knowledge empowers all and will help us get closer to the [[decentralised]] 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.
| |
| | |
| [[ETH]] tip [[address]]: 0x83460bE5F218b1520B69D702cE60A1DE37dD8E31
| |
| [[Category:Coins/Tokens]] | | [[Category:Coins/Tokens]] |
Recently, several criticisms related to CryptoWiki Discord were highlighted publicly by a user we banned. As such, we're obliged to also react to them publicly.
First, we admit our moderation standards didn't always keep up with the growth of the CryptoWiki discord. What started as a place for CryptoWiki editors to hang out (a community we thought required pretty much no moderation) grew bigger and bigger and we didn't keep up. The unpunished n-word screenshots (from 2020) are a symptom of that issue. As the community grown we had to cut more and more of the "hang out" and discussion areas as they are incredibly hard to moderate, and we refocused on promoting ontopic discussion as much as possible. Today, our moderation standards are way higher, the n-word is completely banned (as probably should have been from the beginning but none of us thought of that) and we try to get rid of people who don't have an interest in ontopic discussion and only bring memes/drama/fakes. Funnily enough, the exposé criticiczes both our lack of moderation in the early days and our "too strict" moderation now.
Personal DM communications of some mods flew under our radar and we will work on having a more professional communication from them in the future, forwarding the concerns to others if they can't handle them. That said, I personally (jagotu) replied to every single of the user's DMs professionally and didn't block them on any platforms and they only talked to me once, yet they kept on bringing up their ban with regular mods who were handling the situation a bit worse. My DMs are open on all platforms and I was listening.
