Security model

What Bashard protects, what it does not, and open work before any mainnet launch.

Bashard is a working MVP, not audited software. This page lists what the design guarantees and what it explicitly does not.

What the design provides

• Integrity: every shard and every 1 KiB leaf is verifiable against the on-chain root. A node cannot serve altered data undetected.
• Availability by redundancy: any 7 of 20 shards rebuild a track, tolerating up to 13 missing shards.
• Accountability: proof-of-access challenges and two-thirds slash votes penalize nodes that drop data.

What it does not provide

• Confidentiality: objects are public. Anyone with a track id can download and decode. Client-side encryption is not implemented.
• Censorship policy: a content takedown process and blacklist are not yet built.
• Production hardening: rate limiting, monitoring and key management for nodes and the API are open items.

Required before mainnet

1. External security audit of contracts and the node's verification paths. None has been done.
2. Client-side encryption.
3. Takedown process.
4. Streaming uploads for large files.
5. Timelock in front of the owner role and an upgradeability decision.
6. HTTPS, rate limiting, monitoring and key management.
7. A public testnet with outside operators and a bug bounty.

What you can do

• Never share seed phrases or private keys. Bashard never asks for them.
• Verify the chain id your wallet is asked to switch to.
• Treat any token or contract claiming to be Bashard on mainnet as not from this project.
• Report suspected vulnerabilities through the project's official channels once announced, not in public.