Draft talk:Aave Protocol
![]() | This draft was nominated for deletion on 16 July 2024. The result of the discussion was soft delete. |
![]() | WARNING: ACTIVE COMMUNITY SANCTIONS The article Draft:Aave Protocol, along with other pages relating to blockchain and cryptocurrencies, is designated by the community as a contentious topic. The current restrictions are:
Editors who repeatedly or seriously fail to adhere to the purpose of Wikipedia, any expected standards of behaviour, or any normal editorial process may be sanctioned.
|
![]() | This draft does not require a rating on Wikipedia's content assessment scale. It is of interest to the following WikiProjects: | ||||||||||
|
Aave should be notable enough
editAave is one of the top 70 coins on Coinmarketcap, so I'm quite sure that this is notable enough for Wikipedia. Cenerivesuvio (talk) 15:06, 29 March 2024 (UTC)
This article was soft deleted at Wikipedia:Articles for deletion/Aave Protocol. See [1]
I am an enthusiast on notable, more widely used crypto protocols and would like to request an undeletion. The reason I created this article is because I'm trying to fill a knowledge gap in what crypto enthusiast community considers to be useful.
There was only one user who voted and stated that it seems like it was "written for a cryptocurrency enthusiast audience ... although I am not sure to what extent this is considered when deliberating deletion."
The community, particularly other users who actually know more about the topic and know which crypto protocols and platforms are supposed to be notable, did not have a chance to comment. I was busy in real life and did not have a chance to respond, but I am completely sure that Aave is notable enough for Wikipedia.
1. In terms of market capitalization, Aave Protocol is currently at #51. Please consult the Aave page at https://coinmarketcap.com/currencies/aave/
It means that Aave is #51 widely used and circulated cryptocurrency as of now.
Over half of all Wikipedia articles about cryptocurrencies do not even reach #51 on https://coinmarketcap.com/ For example, EOS.IO is at #78 in comparison. Please see the ranking on the CoinMarketCap's main page.
2. If you often visit websites that offer payments in about a dozen cryptocurrencies, you will frequently see Aave listed as one of the payment options, along with Litecoin and also Avalanche (blockchain platform) and Verge (cryptocurrency). All of these are already on Wikipedia.
3. Aave Protocol has been been studied and cited in peer-reviewed academic journals. Please see for example:
Is decentralized finance actually decentralized? A social network analysis of the Aave protocol on the Ethereum blockchain https://arxiv.org/abs/2206.08401
Liquidity Risks in Lending Protocols: Evidence from Aave Protocol https://arxiv.org/abs/2206.11973
We can use these citations to make the article look more technical, scholarly, and academic.
Doing a basic Google search for "Aave" (which also stands for various other things) is not a good way to tell if Aave Protocol is supposed to be notable or not for Wikipedia, because Google search rankings don't prioritize scholarly papers over crypto blogs and news sites. We need to check journals and scholarly work as well. On the other hand, non-notable crypto articles would be about newfangled crypto platforms and protocols that hardly anyone uses, and no peer-reviewed academic journals would ever cite them.
4. Aave is already on the Persian Wikipedia, at fa:پروتکل Aave, and my impression is that the Persian Wikipedia does not have much tolerance for non-notable topics. From what I can see, this version seems like it is written encyclopedically, so we can use this version to expand into English.
Conclusion: These are solid reasons for why the article should not have been hastily deleted without wider community consensus, and should thus be undeleted. The Aave Protocol complements Wikipedia's current coverage on cryptocurrency topics and does not fail GNG critera. Thanks for taking the time to read through this. —Cenerivesuvio (talk) 19:24, 1 August 2024 (UTC)