Criteria for Case Inclusion - Revision history

Azoundria: Improving and clarifying the criteria further.

2023-05-02T18:27:38Z

Improving and clarifying the criteria further.

← Older revision		Revision as of 12:27, 2 May 2023
Line 2:		Line 2:
	== Notability ==		== Notability ==

	* A case must be referenced from at least two locations. A single comment is not sufficient. Two comments, or a comment and a blockchain transaction, or a thread with multiple follow up comments, are valid for consideration.		* A case must be referenced from at least two locations. A single comment or post is not sufficient. Two comments, or a comment and a blockchain transaction, or a thread with multiple follow up comments, are valid for consideration.
	* ~~Due~~ to the nature of cryptocurrency, ~~primary~~ sources like Reddit, Twitter, Discord, Telegram, Medium, or other social media are permitted. Other common sources which can be used are the Internet Archive, news articles from publications like CoinTelegraph, Decrypt, Vice, or third party aggregators of case information like Rekt. More well known cases will likely have a variety of mainstream and official sources, which should be given precedence.		** Note that fake reports of cases (where there has been public skepticism or facts which contradict one another) can be dealt with through the controversial template. They will still be included until they can be confirmed fake, but obviously all of the information refuting the case would also be included. Report only facts and let people decide for themselves.
	* The case must involve one of the following:		* Obviously, we would prefer to use sources which are official, such as actual blockchain transactions, mainstream media, analyses by credible researchers, etc... However, due to the nature of cryptocurrency, some unconventional sources like Reddit, Twitter, Discord, Telegram, Medium, or other social media are permitted. Other common sources which can be used are the Internet Archive, news articles from publications like CoinTelegraph, Decrypt, Vice, or third party aggregators of case information like Rekt. More well known cases will likely have a variety of mainstream and official sources, which should be given precedence.
			* The case must involve at least one of the following:
	** More than $1,500 USD lost at the time of the event, in the case of a hack, theft, fraud, or lost key. If the loss is in fungible crypto-assets, this is calculated using the closing price on CoinMarketCap at the day of the exploit. If CoinMarketCap doesn't list the price of the assets, then an alternative source like CoinGecko or Nomics can be used. Best effort should be made to assess the accurate value of the loss including all assets lost.		** More than $1,500 USD lost at the time of the event, in the case of a hack, theft, fraud, or lost key. If the loss is in fungible crypto-assets, this is calculated using the closing price on CoinMarketCap at the day of the exploit. If CoinMarketCap doesn't list the price of the assets, then an alternative source like CoinGecko or Nomics can be used. Best effort should be made to assess the accurate value of the loss including all assets lost.
			** More than $500 USD lost at the time of the event, and notable coverage or attention by several sources.
	** More than $9,500 USD worth of funds placed at risk of loss, were the exploit not found and resolved through a white hacking effort. Cases in this category must be such that the loss would have occurred by default. (ie. Someone in a time machine could have taken the funds without depending on operator incompetence.)		** More than $9,500 USD worth of funds placed at risk of loss, were the exploit not found and resolved through a white hacking effort. Cases in this category must be such that the loss would have occurred by default. (ie. Someone in a time machine could have taken the funds without depending on operator incompetence.)
	** Private sensitive information on more than 50 individuals being compromised. This includes full legal names, home address, email address and association with a cryptocurrency service, or phone number and association with a cryptocurrency service.		** Private sensitive information on more than 50 individuals who can be definitively associated with using cryptocurrency being compromised. This includes full legal names, home address, email address and association with a cryptocurrency service, or phone number and association with a cryptocurrency service.
	* Credibility is generally given to the event as having occurred versus not having occurred, except in the following cases:		* Credibility is generally given to the event as having occurred versus not having occurred, except in the following cases:
	** Events which are accompanied with advertisement for questionable cryptocurrency recovery services. In this case, independent third party sources are required for the even to be included.		** Events which are accompanied with advertisement for questionable cryptocurrency recovery services. In this case, independent third party sources are required for the even to be included.
	* If an event is considered controversial as to whether it occurred or not, this should be noted in the article.

	== Relevance ==		== Relevance ==
Line 20:		Line 21:
	The particular impact must be clear and must be unexpected or fraudulent. Some examples of cases that can't yet be included would be:		The particular impact must be clear and must be unexpected or fraudulent. Some examples of cases that can't yet be included would be:

	* A ponzi scheme that is still in-progress. Due to the nature of ponzi schemes, it is not possible to definitively tell when something is a ponzi scheme until it collapses. The goal of this repository is to provide references of historic events, not to speculate on which particular financial schemes may collapse.		* A ponzi scheme that is still in-progress. Due to the nature of ponzi schemes, it is not possible to definitively tell when something is a ponzi scheme until it collapses. The goal of this repository is to provide references of historic events, not to speculate on which particular financial schemes may collapse. There are various other tools out there that report on current MLMs that are still operating, and that's not the purpose of this wiki.
	* A hack event which is not backed by any tangible evidence. For example, if someone has a suspicion that a service got hacked, that wouldn't be possible to include. If there are credible concerns and blockchain-supported evidence, this can be included but both sides of the issue must be fairly weighed.		* A hack event which is not backed by any tangible evidence. For example, if someone has a suspicion that a service got hacked, that wouldn't be possible to include. If there are credible concerns and blockchain-supported evidence, this can be included but both sides of the issue must be fairly weighed.
			* Disputes of frozen funds on platforms, where the platform is still operating. Unfortunately, this is really tricky, because it's hard to know whether the funds were legitimately frozen or not.
	* Losses that are due to standard/reasonable market fluctuations. For example:		* Losses that are due to standard/reasonable market fluctuations. For example:
	** If the cryptocurrency market drops 70%, many people may consider that they have "lost money", but in fact, no loss has occurred. They just overpaid for their digital assets.		** If the cryptocurrency market drops 70%, many people may consider that they have "lost money", but in fact, no loss has occurred. They just overpaid for their digital assets.
	** If a project did their best to deliver and ultimately failed~~, that wouldn't~~ be included~~. But~~ if their original payment was based on credibly fraudulent information, or the project founders were entirely fake, or the team never intended to keep their word~~, that could be. This is not the place to include any projects for violation of securities registration, but such evidence could be used towards evidence of other fraud happening~~.		** If a project did their best to deliver and ultimately failed. This is also not the place to include any projects for violation of securities registration. A case could be included if their original payment was based on credibly fraudulent information, the project founders were entirely fake, it was a token which could be bought and never sold, the smart contract did a rug pull, or the team never intended to keep their word.
	** Similarly, margin trading is inherently risky, and so facing a prospect of losses when conducting a margin trade would count as a normal expected outcome. ~~However, there~~ are some cases where denial of service or fee-based attacks succeed in preventing proper function, which could be considered.		** Similarly, margin trading is inherently risky, and so facing a prospect of losses when conducting a margin trade would count as a normal expected outcome. There are some cases where denial of service or fee-based attacks succeed in preventing proper function, which could be considered.
	** General market manipulation is usually not considered to be included. It's assumed that the cryptocurrency landscape is not a level playing field. This includes wash trading, attempts to push the price around, or messaging to manipulate others. On the other hand, if price on a single platform or smart contract is manipulated to fall well outside of the wider market price, for the purposes of extracting profit ~~very quickly~~, that would be included as an exploit of that platform.		** General market manipulation is usually not considered to be included. It's assumed that the cryptocurrency landscape is not a level playing field. This includes wash trading, attempts to push the price around, or messaging to manipulate others. On the other hand, if the "official" price on a single platform or smart contract is manipulated to fall well outside of the wider market price, for the purposes of extracting profit in a single incident, that would be included as an exploit of that platform.
	** If blockchains stop running over time and eventually die out, those wouldn't be included on it's own. This is a reasonably expected outcome that some technologies of money will not ~~success~~. Similarly, if a platform was operating honestly, winds down business and returns customer deposits with reasonable notice, this wouldn't be included on it's own. It isn't a place for a graveyard of every failed crypto platform or project - only those that fail due to fraud or an irrecoverable hack.		** If blockchains stop running over time and eventually die out, those wouldn't be included on it's own. This is a reasonably expected outcome that some technologies of money will not succeed. Similarly, if a platform was operating honestly, winds down business and returns customer deposits with reasonable notice, this wouldn't be included on it's own. It isn't a place for a graveyard of every failed crypto platform or project - only those that fail due to fraud or an irrecoverable hack.

Azoundria: /* Relevance */ reference to the Guideline for Dating Cases

2023-01-19T20:14:33Z

Relevance: reference to the Guideline for Dating Cases

← Older revision		Revision as of 14:14, 19 January 2023
Line 15:		Line 15:

	* The case must involve crypto-assets, or purport to involve crypto-assets. For cases which involve a mix of real-world assets and crypto-assets, real-world assets are generally not included unless they form liquidity on a trading platform.		* The case must involve crypto-assets, or purport to involve crypto-assets. For cases which involve a mix of real-world assets and crypto-assets, real-world assets are generally not included unless they form liquidity on a trading platform.
	* The specific time (at least to the ~~week~~) of the event must be discernible. ~~The relevant time to use is as follows:~~		* The specific time (at least to the day) of the event must be discernible. See the [[Guidelines For Dating Cases]] for help in which date is applicable to the case.
	** For hacking or rug pull events, the timestamp of the first blockchain transaction that removes funds from the individual or service facing the loss. If no blockchain transactions can be found, then the timestamp of the ~~very first public report.~~
	** Ponzi events must have concluded before they can be covered. For ~~ponzi events,~~ in ~~this order:~~
	*** The timestamp of the first public declaration of bankruptcy, guilt by a founding member, or announcement that the platform is shutting down.
	*** If there was no such announcement, the time at which ~~the platform ceased to honour withdrawals. This~~ is ~~the time of last withdrawal, not counting withdrawals by operators of the scheme.~~
	*** If information about withdrawals cannot be obtained, or no withdrawals were ever allowed, the timestamp of the first public report that a participant is unable to ~~withdraw their funds.~~
	*** Failing that, the date of the most comprehensive investigation can be used.
	** For lost funds, the time at which the individual or organization first publicly reports the funds inaccessible.
	** For privacy breaches, the date at which the information was first accessed by an unintended party. If the circumstances of the access have not been publicly revealed, then the time of the ~~first announcement~~.

	== Definite Impact ==		== Definite Impact ==

Azoundria: /* Relevance */

2023-01-19T20:07:05Z

Relevance

← Older revision		Revision as of 14:07, 19 January 2023
Line 18:		Line 18:
	** For hacking or rug pull events, the timestamp of the first blockchain transaction that removes funds from the individual or service facing the loss. If no blockchain transactions can be found, then the timestamp of the very first public report.		** For hacking or rug pull events, the timestamp of the first blockchain transaction that removes funds from the individual or service facing the loss. If no blockchain transactions can be found, then the timestamp of the very first public report.
	** Ponzi events must have concluded before they can be covered. For ponzi events, in this order:		** Ponzi events must have concluded before they can be covered. For ponzi events, in this order:
	*** The timestamp of a public declaration of bankruptcy or announcement that the platform is shutting down.		*** The timestamp of the first public declaration of bankruptcy, guilt by a founding member, or announcement that the platform is shutting down.
	*** If there was no such announcement, the time at which the platform ceased to honour withdrawals. This is the time of last withdrawal, not counting withdrawals by operators of the scheme.		*** If there was no such announcement, the time at which the platform ceased to honour withdrawals. This is the time of last withdrawal, not counting withdrawals by operators of the scheme.
	*** If information about withdrawals cannot be obtained, or no withdrawals were ever allowed, the timestamp of the first public report that a participant is unable to withdraw their funds.		*** If information about withdrawals cannot be obtained, or no withdrawals were ever allowed, the timestamp of the first public report that a participant is unable to withdraw their funds.
			*** Failing that, the date of the most comprehensive investigation can be used.
	** For lost funds, the time at which the individual or organization first publicly reports the funds inaccessible.		** For lost funds, the time at which the individual or organization first publicly reports the funds inaccessible.
	** For privacy breaches, the date at which the information was first accessed by an unintended party. If the circumstances of the access have not been publicly revealed, then the time of the first announcement.		** For privacy breaches, the date at which the information was first accessed by an unintended party. If the circumstances of the access have not been publicly revealed, then the time of the first announcement.

Azoundria: Added definite impact section to case inclusion part.

2023-01-16T20:30:49Z

Added definite impact section to case inclusion part.

← Older revision		Revision as of 14:30, 16 January 2023
Line 23:		Line 23:
	** For lost funds, the time at which the individual or organization first publicly reports the funds inaccessible.		** For lost funds, the time at which the individual or organization first publicly reports the funds inaccessible.
	** For privacy breaches, the date at which the information was first accessed by an unintended party. If the circumstances of the access have not been publicly revealed, then the time of the first announcement.		** For privacy breaches, the date at which the information was first accessed by an unintended party. If the circumstances of the access have not been publicly revealed, then the time of the first announcement.

			== Definite Impact ==
			The particular impact must be clear and must be unexpected or fraudulent. Some examples of cases that can't yet be included would be:

			* A ponzi scheme that is still in-progress. Due to the nature of ponzi schemes, it is not possible to definitively tell when something is a ponzi scheme until it collapses. The goal of this repository is to provide references of historic events, not to speculate on which particular financial schemes may collapse.
			* A hack event which is not backed by any tangible evidence. For example, if someone has a suspicion that a service got hacked, that wouldn't be possible to include. If there are credible concerns and blockchain-supported evidence, this can be included but both sides of the issue must be fairly weighed.
			* Losses that are due to standard/reasonable market fluctuations. For example:
			** If the cryptocurrency market drops 70%, many people may consider that they have "lost money", but in fact, no loss has occurred. They just overpaid for their digital assets.
			** If a project did their best to deliver and ultimately failed, that wouldn't be included. But if their original payment was based on credibly fraudulent information, or the project founders were entirely fake, or the team never intended to keep their word, that could be. This is not the place to include any projects for violation of securities registration, but such evidence could be used towards evidence of other fraud happening.
			** Similarly, margin trading is inherently risky, and so facing a prospect of losses when conducting a margin trade would count as a normal expected outcome. However, there are some cases where denial of service or fee-based attacks succeed in preventing proper function, which could be considered.
			** General market manipulation is usually not considered to be included. It's assumed that the cryptocurrency landscape is not a level playing field. This includes wash trading, attempts to push the price around, or messaging to manipulate others. On the other hand, if price on a single platform or smart contract is manipulated to fall well outside of the wider market price, for the purposes of extracting profit very quickly, that would be included as an exploit of that platform.
			** If blockchains stop running over time and eventually die out, those wouldn't be included on it's own. This is a reasonably expected outcome that some technologies of money will not success. Similarly, if a platform was operating honestly, winds down business and returns customer deposits with reasonable notice, this wouldn't be included on it's own. It isn't a place for a graveyard of every failed crypto platform or project - only those that fail due to fraud or an irrecoverable hack.

Azoundria: Azoundria moved page Criteria For Case Inclusion to Criteria for Case Inclusion: Casing correction

2023-01-14T15:01:00Z

Azoundria moved page Criteria For Case Inclusion to Criteria for Case Inclusion: Casing correction

← Older revision	Revision as of 09:01, 14 January 2023
(No difference)

Azoundria: Created criteria for case inclusion.

2023-01-12T18:28:53Z

Created criteria for case inclusion.

New page

== Notability ==

* A case must be referenced from at least two locations. A single comment is not sufficient. Two comments, or a comment and a blockchain transaction, or a thread with multiple follow up comments, are valid for consideration.
* Due to the nature of cryptocurrency, primary sources like Reddit, Twitter, Discord, Telegram, Medium, or other social media are permitted. Other common sources which can be used are the Internet Archive, news articles from publications like CoinTelegraph, Decrypt, Vice, or third party aggregators of case information like Rekt. More well known cases will likely have a variety of mainstream and official sources, which should be given precedence.
* The case must involve one of the following:
** More than $1,500 USD lost at the time of the event, in the case of a hack, theft, fraud, or lost key. If the loss is in fungible crypto-assets, this is calculated using the closing price on CoinMarketCap at the day of the exploit. If CoinMarketCap doesn't list the price of the assets, then an alternative source like CoinGecko or Nomics can be used. Best effort should be made to assess the accurate value of the loss including all assets lost.
** More than $9,500 USD worth of funds placed at risk of loss, were the exploit not found and resolved through a white hacking effort. Cases in this category must be such that the loss would have occurred by default. (ie. Someone in a time machine could have taken the funds without depending on operator incompetence.)
** Private sensitive information on more than 50 individuals being compromised. This includes full legal names, home address, email address and association with a cryptocurrency service, or phone number and association with a cryptocurrency service.
* Credibility is generally given to the event as having occurred versus not having occurred, except in the following cases:
** Events which are accompanied with advertisement for questionable cryptocurrency recovery services. In this case, independent third party sources are required for the even to be included.
* If an event is considered controversial as to whether it occurred or not, this should be noted in the article.

== Relevance ==

* The case must involve crypto-assets, or purport to involve crypto-assets. For cases which involve a mix of real-world assets and crypto-assets, real-world assets are generally not included unless they form liquidity on a trading platform.
* The specific time (at least to the week) of the event must be discernible. The relevant time to use is as follows:
** For hacking or rug pull events, the timestamp of the first blockchain transaction that removes funds from the individual or service facing the loss. If no blockchain transactions can be found, then the timestamp of the very first public report.
** Ponzi events must have concluded before they can be covered. For ponzi events, in this order:
*** The timestamp of a public declaration of bankruptcy or announcement that the platform is shutting down.
*** If there was no such announcement, the time at which the platform ceased to honour withdrawals. This is the time of last withdrawal, not counting withdrawals by operators of the scheme.
*** If information about withdrawals cannot be obtained, or no withdrawals were ever allowed, the timestamp of the first public report that a participant is unable to withdraw their funds.
** For lost funds, the time at which the individual or organization first publicly reports the funds inaccessible.
** For privacy breaches, the date at which the information was first accessed by an unintended party. If the circumstances of the access have not been publicly revealed, then the time of the first announcement.