Anatomy of a Case Study
Headers, if applicable, would normally go at the very top of the case page. See the List of Wiki Header Templates for a list of all possible headers that might be used, and the different situations when they apply.
New cases added need to comply with the Criteria for Case Inclusion. A high level overview of all the most relevant facts and information in the case would be included here. Case studies comprise of the following primary sections:
About [Service]
The background of the exchange platform, service, or individuals involved, as it would have been seen or understood at the time of the events.
Include:
- Known history of when and how the service was started.
- What problems does the company or service claim to solve?
- What marketing materials were used by the firm or business?
- Audits performed, and excerpts that may have been included.
- Business registration documents shown (fake or legitimate).
- How were people recruited to participate?
- Public warnings and announcements prior to the event.
Don't Include:
- Any wording which directly states or implies that the business is/was illegitimate, or that a vulnerability existed.
- Anything that wasn't reasonably knowable at the time of the event.
There could be more than one section here. If the same platform is involved with multiple incidents, then it can be linked to a main article page.
The Reality
This sections is included if a case involved deception or information that was unknown at the time. Examples include:
- When the service was actually started (if different than the "official story").
- Who actually ran a service and their own personal history.
- How the service was structured behind the scenes. (For example, there was no "trading bot".)
- Details of what audits reported and how vulnerabilities were missed during auditing.
What Happened
The specific events of the loss and how it came about. What actually happened to cause the loss and some of the events leading up to it.
| Date | Event | Description |
|---|---|---|
| January 14th, 2023 8:16:23 AM MST | First Event | This is an expanded description of what happened and the impact. If multiple lines are necessary, add them here. |
For the primary time of the event, please refer to the Guidelines For Dating Cases.
Technical Details
This section includes specific detailed technical analysis of any security breaches which happened. What specific software vulnerabilities contributed to the problem and how were they exploited?
Total Amount Lost
How much was lost and how was it calculated? If there are conflicting reports, which are accurate and where does the discrepancy lie?
Immediate Reactions
How did the various parties involved (firm, platform, management, and/or affected individual(s)) deal with the events? Were services shut down? Were announcements made? Were groups formed?
Ultimate Outcome
What was the end result? Was any investigation done? Were any individuals prosecuted? Was there a lawsuit? Was any tracing done?
Total Amount Recovered
What funds were recovered? What funds were reimbursed for those affected users?
Ongoing Developments
What parts of this case are still remaining to be concluded?
Individual Prevention Policies
Which policies could have prevented this event from happening? See the Prevention Policies for Individuals page.
Platform Prevention Policies
Which policies could have prevented this event from happening? See the Prevention Policies for Platforms page.
Regulatory Prevention Policies
Which policies could have prevented this event from happening? See the Prevention Policies for Regulators page.
References
A section with the references where information came from. See the Citing Your Sources Guide.