Skip to content

Latest commit

 

History

1 Commit

Folders and files

NameName
Last commit message
Last commit date
 
 
 
 
 
 

Repository files navigation

Project Name

Table of Contents

Code of Professional Conduct

Our Commitment

In our ongoing commitment to fostering a professional, inclusive, and respectful environment, we, as contributors and maintainers, pledge to create a harassment-free experience for everyone involved in our project and community. This commitment extends to individuals of all backgrounds, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation.

Standards of Behavior

Contributors are expected to adhere to the following standards of behavior to promote a positive environment:

  • Use welcoming and inclusive language
  • Show respect for differing viewpoints and experiences
  • Accept constructive criticism gracefully
  • Prioritize the well-being of the community
  • Demonstrate empathy towards fellow community members

Unacceptable behavior by participants includes:

  • Use of sexualized language or imagery, and unwelcome sexual attention or advances
  • Trolling, insulting/derogatory comments, and personal or political attacks
  • Public or private harassment
  • Publishing others' private information without explicit permission
  • Any conduct that could reasonably be considered inappropriate in a professional setting

Responsibilities

Project maintainers are responsible for defining and clarifying acceptable behavior standards. They are expected to take appropriate and fair corrective action in response to instances of unacceptable behavior. Project maintainers reserve the right and responsibility to remove, edit, or reject contributions that do not align with this Code of Professional Conduct. They may also impose temporary or permanent bans on contributors for behaviors deemed inappropriate, threatening, offensive, or harmful.

Scope

This Code of Professional Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representation include using an official project email address, posting via an official social media account, or acting as an appointed representative at an online or offline event. The specifics of project representation may be further defined by project maintainers.

Enforcement

Instances of abusive, harassing, or otherwise unacceptable behavior can be reported by contacting the project team at protocol@blastblockchain.com. All complaints will be reviewed and investigated, resulting in a response deemed necessary and appropriate to the circumstances. The project team is committed to maintaining confidentiality regarding the reporter of an incident. Specific enforcement policies may be detailed separately.

Project maintainers who fail to follow or enforce the Code of Professional Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership.

Attribution

This Code of Professional Conduct is adapted from the Contributor Covenant, version 1.4, available at http://contributor-covenant.org/version/1/4.

Security Disclosure Policy

Reporting Vulnerabilities

To disclose vulnerabilities in any of our websites, email servers, or other non-critical infrastructure, please contact the Blast team via email at protocol@blastblockchain.com. We highly appreciate detailed instructions to confirm the vulnerability.

Vulnerability Disclosure Process

In the event of discovering a critical security vulnerability, we follow a responsible disclosure process. We reserve the right to silently address and fix the vulnerability without immediately publicly disclosing its existence or nature.

Our disclosure process involves the following steps:

  1. Silent Fixing: The vulnerability is silently fixed and included in a specific release (X).
  2. Initial Disclosure: After 4-8 weeks, we disclose that release X contains a security fix.
  3. Public Disclosure: After an additional 4-8 weeks, we publish detailed information about the vulnerability, giving credit to the reporter with their express permission.

In addition to this policy, we reserve the right to:

  • Bypass this policy and disclose details on a shorter timeline.
  • Directly notify a subset of downstream users before making a public announcement.

This policy is inspired by the Geth team’s silent patch policy.

Defensive Measures during an Incident

While our system does not have fault proofs, allowing us to pause the system in an emergency, we have established criteria for disabling the system during an incident response:

  • Ongoing Attack: If an attack is ongoing, we will disable or pause to prevent further damage.
  • Suspected Widespread Knowledge: If we suspect that a vulnerability might be widely known, we will proactively disable or pause.
  • Otherwise: If there is no ongoing attack or suspicion of widespread knowledge, we will not disable or pause the system.

Our commitment is to prioritize the security and stability of our system and respond to incidents in a responsible and timely manner.

README

Project Name

Getting Started

Usage

Contributing

License

Contact

Acknowledgments

Troubleshooting

Changelog

Security

Roadmap

Disclaimer

Additional Resources

Author

Support

Sponsors

Connect with Us

Donations

License


About

No description, website, or topics provided.

Resources

Code of conduct

Security policy

Stars

0 stars

Watchers

1 watching

Forks

Releases

Packages

Contributors