remove emails folder and sentinel evidence folder

[faddat]

…isible

Summary by CodeRabbit

• Bug Fixes

  • Removed multiple emails addressing security vulnerabilities related to "p2p storms" affecting Cosmos SDK chains, which included discussions on denial-of-service risks and transaction handling issues.
  • Eliminated emails detailing the reproduction of security attacks and the need for collaboration among teams to address these vulnerabilities.

• Chores

  • Deleted unnecessary email files that contained repetitive content or did not contribute meaningful information to the project.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

The changes involve the deletion of multiple email files that contained discussions about security vulnerabilities, governance proposals, and coordination efforts within the Cosmos ecosystem. The emails addressed issues such as P2P storms, transaction handling, and the need for collaboration among teams. They also discussed the implications of certain vulnerabilities and proposed fixes, as well as frustrations regarding communication lapses and the lack of engagement from various stakeholders.

Changes

File Path	Change Summary
emails/40 min phone call with Hypha.eml	Deleted email discussing a phone call about addressing P2P storms.
emails/Advice (1).eml	Deleted email expressing frustrations over security guidance and coordination.
emails/Advice.eml	Deleted email requesting guidance on security coordination and compliance.
emails/Attacking chain A from chain B.eml	Deleted email addressing perceived threats in communications with Amulet.
emails/Bash script.eml	Deleted Bash script for automating transactions on the Gaia blockchain.
emails/Daily email of video of taking down hub rs testnet.eml	Deleted email detailing security concerns regarding the hub rs testnet.
emails/Definition of slight impact.eml	Deleted email discussing block latency issues and their impact.
emails/I can turn chains on and off at will.eml	Deleted email discussing manipulation of blockchain liveness.
emails/IBC_ banana king (1).eml	Deleted email discussing field length validation in IBC protocol.
emails/IBC_ banana king (2).eml	Deleted email regarding IBC issues and communication frustrations.
emails/IBC_ banana king (3).eml	Deleted email addressing security issues related to IBC transactions.
emails/IBC_ banana king.eml	Deleted email discussing field length validation in IBC.
emails/Legal uncertainty of security research in cosmos.eml	Deleted email discussing legal implications of security research.
emails/Mitigation governance proposal.eml	Deleted email discussing governance proposals to increase costs on the hub.
emails/New finding_ higher tx sizes can fully halt chain (1).eml	Deleted email discussing transaction size impacts on blockchain performance.
emails/New finding_ malformed txns never leave mempool (1).eml	Deleted email discussing malformed transactions in the mempool.
emails/New finding_ malformed txns never leave mempool.eml	Deleted email detailing a bug in transaction handling in the mempool.
emails/No response_ security@interchain.io.eml	Deleted email reporting lack of response from security team on critical issues.
emails/Non-final final report.eml	Deleted email regarding a non-final report and publication concerns.
emails/P2P Storms_ Day 22 begins in 2 hours.eml	Deleted email discussing communication lapses on security issues.
emails/P2P Storms_ video (1).eml	Deleted email regarding a video on vulnerabilities in P2P systems.
emails/P2P Storms_ video (2).eml	Deleted email discussing acknowledgment of a video on P2P vulnerabilities.
emails/P2P Storms_ video.eml	Deleted email addressing a vulnerability video affecting all Cosmos chains.
emails/P2P storms (1).eml	Deleted email acknowledging receipt of a report on P2P storms.
emails/P2P storms (2).eml	Deleted email discussing P2P storms and requests for GitHub access.
emails/P2P storms (3).eml	Deleted email outlining security issues related to P2P storms.
emails/P2P storms (4).eml	Deleted email discussing P2P storms and recommendations for mitigation.
emails/P2P storms (5).eml	Deleted email detailing P2P storms and potential DoS vulnerabilities.
emails/P2P storms (6).eml	Deleted email discussing P2P storms and mitigation strategies.
emails/P2P storms (7).eml	Deleted email addressing P2P storms and collaboration requests.
emails/P2P storms (8).eml	Deleted email discussing the implications of a specific transaction on P2P storms.
emails/P2P storms.eml	Deleted email outlining P2P storms and mitigation recommendations.
emails/Replication of p2p flood (1).eml	Deleted email discussing the replication of a P2P flood attack.
emails/Replication of p2p flood.eml	Deleted email regarding the initiation of attacks on a security testnet.
emails/Reproduction success (1).eml	Deleted email discussing reproduction steps of a security attack.
emails/Reproduction success (2).eml	Deleted email detailing execution of an attack on the Cosmos hub.
emails/Reproduction success (3).eml	Deleted email outlining steps to replicate a security attack.
emails/Reproduction success (4).eml	Deleted email discussing the implications of a replicated attack.
emails/Reproduction success.eml	Deleted email summarizing the reproduction of a security attack.
emails/Rs testnet p2p stormed.eml	Deleted email providing a link to a block explorer for the RS testnet.
emails/Scoping for p2p floods (1).eml	Deleted email discussing p2p flood issues and potential DoS vulnerabilities.
emails/Scoping for p2p floods.eml	Deleted email outlining various p2p flood issues across teams.
emails/Update on ABC-0002 (1).eml	Deleted email regarding collaboration on a security issue tracked as ABC-0002.
emails/Update on ABC-0002 (2).eml	Deleted email discussing ongoing efforts related to a security issue.
emails/Update on ABC-0002.eml	Deleted email providing an update on a reported security issue.
emails/Updated timeline (1).eml	Deleted email regarding governance proposals for block size reduction.
emails/Updated timeline (2).eml	Deleted email discussing governance proposals and urgency in communication.
emails/Updated timeline.eml	Deleted email outlining governance proposals and communication concerns.
emails/Video of attack.eml	Deleted email detailing a security vulnerability and proposed fixes.
emails/Video of taking down chains at will.eml	Deleted email discussing vulnerabilities and their implications.
sentinel-evidence/evilTxHashes222	Deleted file containing repetitive content with no functional purpose.

Poem

In the meadow, a rabbit hops,
With changes made, the old now stops.
Emails gone, like whispers in the breeze,
Security's dance, a cautious tease.
"P2P storms," the rabbit sighs,
"Let’s hop along, where safety lies!" 🐇✨

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.