> For the complete documentation index, see [llms.txt](https://blast-isles.gitbook.io/blast-isles-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://blast-isles.gitbook.io/blast-isles-docs/blast-isles-document/fair-play-and-security.md).

# Fair Play and Security

Competitive balance, abuse prevention, security and appeals.

### Competitive balance

Fairness depends on the mode. Competition using accumulated equipment differs from standardised competition. Rules must state which model applies.

Major tournaments may use standardised attributes, equipment restrictions or strength-based brackets. A mode should not claim to be purely skill-based when equipment or spending creates a material advantage.

### Anti-cheat, bots and multi-account abuse

Controls address unauthorised automation, data manipulation, collusion, ranking manipulation and multi-account reward abuse. Reviews should use multiple evidence signals.

Shared IP addresses or devices alone do not prove cheating. Responses can include restrictions, withheld rewards, removal or suspension. Decisions require reasons and an appeal route.

### Wallet and smart contract security

Security uses role-based permissions, key management and multisignature controls where appropriate. Sensitive changes should have notice and a waiting period outside emergencies.

Contracts must disclose upgrade, minting, transfer restriction and pause powers. Audit claims need a verifiable report that identifies the reviewed version and scope.

### Enforcement and appeals

Players should receive the alleged breach, imposed restrictions and appeal process. Appeals can include relevant dates, accounts, matches, transactions and evidence.

Overturned decisions should restore appropriate benefits. Tournament cases follow the rules published before the match.