Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Create 2023-07-06-Multichain.md #38

Open
wants to merge 3 commits into
base: main
Choose a base branch
from
Open

Create 2023-07-06-Multichain.md #38

wants to merge 3 commits into from

Conversation

Kseymur
Copy link
Owner

@Kseymur Kseymur commented Feb 3, 2024

No description provided.

@Kseymur
Copy link
Owner Author

Kseymur commented Feb 5, 2024

Fact Checking

Editor's Notes

  • In the Summary section, add more details about the Multichain platform and bridge, such as what they are used for. This will help readers unfamiliar with Multichain understand the context better.

  • In the Attackers section, consider adding additional details about the unknown hackers if any more information emerges later.

  • In the Losses section:

    • Add the total estimated loss amount ($126 million) at the start for clarity.
    • Format the monetary values consistently, e.g. use commas as thousand separators.
    • Round long decimal values for conciseness, e.g. 30.9 million instead of 30,925,467.
  • In the Timeline section:

    • Add specific timezone for the timestamps, e.g. UTC.
    • Consider using a bulleted list format for improved readability.
  • Overall, review the content for spelling, grammar, punctuation. Example errors:

    • "begins being drained" should be "began being drained"
    • Add comma after "On July 6, 2023"

Hugo SSG Formatting Check

  • Does it match Hugo SSG formatting? ✅

Filename Check

  • Correct Filename: 2023-07-06-Multichain.md
  • Your Filename: 2023-07-06-Multichain.md

Section Headers Check

  • Allowed Headers: ## Summary, ## Attackers, ## Losses, ## Timeline, ## Security Failure Causes
  • Your Headers: ## Summary, ## Attackers, ## Losses, ## Timeline, ## Security Failure Causes

Metadata Headers Check

  • Allowed Metadata Headers: date, target-entities, entity-types, attack-types, title, loss
  • Your Metadata Headers: date, target-entities, entity-types, attack-types, title, loss
  • Notes:
    • July 06, 2023 date: 2023-06-06 ⚠️ Date in metadata header does not match date of event
    • Multichain target-entities: Multichain ✅
    • $126 million loss: 126000000 ✅
    • DeFi, Bridge entity-types:
    • DeFi
    • Bridge ✅
      • Private Key Compromise attack-types:
    • Private Key Compromise ✅

@Kseymur
Copy link
Owner Author

Kseymur commented Feb 15, 2024

Fact Checking Results

Editor's Notes

  • In the Timeline section:

    • Standardize the date format to "Month day, year, time PM UTC". For example: "July 06, 2023, 06:33 PM UTC"
    • Add the missing timeline point: "July 06, 2023, 04:21 PM UTC: The first malicious transaction occurred."
  • In the Losses section:

    • Add commas as thousands separators in large numbers for improved readability.
    • Standardize the currency format. For example, use "USD" instead of "US Dollar".
  • In the Attackers section:

    • Change "The identity of the hackers..." to "The identities of the hackers..." for subject-verb agreement.
  • Overall:

    • Standardize capitalization of titles and headers.
    • Fix minor typos and grammatical issues.

No other major issues found.

Hugo SSG Formatting Check

  • Does it match Hugo SSG formatting? ✅

Filename Check

  • Correct Filename: 2023-07-06-Multichain.md
  • Your Filename: 2023-07-06-Multichain.md

Section Headers Check

  • Allowed Headers: ## Summary, ## Attackers, ## Losses, ## Timeline, ## Security Failure Causes
  • Your Headers: Same headers ✅

Metadata Headers Check

  • Allowed Metadata Headers: date, target-entities, entity-types, attack-types, title, loss

  • Your Metadata Headers: Same headers ✅

  • Notes:

    • Date in text: July 06, 2023 July 06, 2023
    • Date in metadata: 2023-06-06 2023-06-06 ⚠️
    • Target entity in text: Multichain Multichain
    • Target entities in metadata: Multichain Multichain ✅
    • Loss in text: $126 million $126 million
    • Loss in metadata: 126000000 126000000 ✅
  • Entity types: DeFi, Bridge seems correct for Multichain ✅

  • Attack type: Private Key Compromise matches the description ✅

@Kseymur
Copy link
Owner Author

Kseymur commented Feb 16, 2024

Fact Checking Results

Editor's Notes

  • In the ## Timeline section:

    • Standardize the date format to 'Month day, year, time PM UTC:'. For example: 'July 06, 2023, 06:33 PM UTC:'.
    • The timeline seems incomplete. Consider adding the date when Multichain CEO was arrested and his devices confiscated.
  • In the ## Losses section:

    • Add the total estimated loss amount.
    • List the stolen assets in a bulleted list for better readability.
  • In the ## Security Failure Causes section:

    • Expand on the details around the compromised private key. How was it compromised? Was it stolen? By whom?
    • Provide more context around the potential insider threat. Who are the suspected insiders? What evidence points to inside job?
  • Overall the content provides a good factual summary of the incident. Consider expanding certain sections with additional details for more context.

  • No major grammatical or stylistic issues found.

Hugo SSG Formatting Check

  • Does it match Hugo SSG formatting? ✅

Filename Check

  • Correct Filename: 2023-07-06-Multichain.md
  • Your Filename: 2023-07-06-Multichain.md

Section Headers Check

  • Allowed Headers: ## Summary, ## Attackers, ## Losses, ## Timeline, ## Security Failure Causes
  • Your Headers: Same headers ✅

Metadata Headers Check

  • Allowed Metadata Headers: date, target-entities, entity-types, attack-types, title, loss

  • Your Metadata Headers: Same headers ✅

  • Notes:

    • The date metadata header matches the date mentioned in the summary: July 06, 2023. ✅

      • July 06, 2023
      • 2023-06-06
    • The target-entities metadata header matches the affected entity mentioned in the summary: Multichain Bridge. ✅

      • Multichain Bridge
      • Multichain
    • The loss metadata header matches the estimated loss mentioned in the losses section: $126 million. ✅

      • $126 million
      • 126000000
    • The entity-types values "DeFi, Bridge" seem accurate for Multichain. ✅

    • The attack-types value "Private Key Compromise" matches the type of attack described. ✅

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant