Skip to content

Security: iceroot-network/programs

SECURITY.md

Security

Use GitHub private vulnerability reporting. The organisation security policy provides the shared reporting route. Include the affected repository, version or commit, a working local reproduction and the impact. Do not include private keys, recovery phrases, signing credentials or other people's data.

For the bounty program, the team acknowledges reports within 3 working days, gives a rating within 14 days, and provides an update at least every 14 days. Fix targets are 30 days for Critical and High reports and 90 days for Medium and Low reports. These fix targets are not guarantees.

A fixed report receives a GitHub security advisory once the fix is live, no later than 90 days after the report. A consensus flaw is disclosed only after its fix has passed its activation height. If that cannot happen within 90 days, the team may use one extension of up to 30 days with a publicly stated reason, making the latest publication date 120 days. Coordinate with the team and keep details private until the advisory is published; then you may publish your own write-up. Credit is optional, by GitHub handle or anonymously.

Good-faith research that follows these rules is authorized. The team will not pursue legal action for that research. Test on your own local network or a private devnet. The relaunched public testnet, once it runs, is the exception for its validators: it is meant to be attacked and broken, and they are encouraged to crash nodes and look for attack vectors there. Do not attack mainnet, public websites or other people's nodes, data, keys or funds. Do not use social engineering, physical attacks or volumetric denial of service. Stop once you have a reproduction and report it privately. This authorization does not extend to third-party systems.

A private report first is a condition for a security bounty. Violating the research rules or disclosing before the coordinated date forfeits the reward. A security reward enters the public record only after its advisory is published. These report commitments are separate from public announcements about live incidents, which are handled case by case. Read the bounty rules and provisional amounts.

Ordinary bugs without a security effect belong in the affected repository's public issue tracker. A security email address will be published only once its inbox is watched every working day. Until then, use the GitHub form.

There aren't any published security advisories