Skip to content
STRAT

Protocol

Security

Shared security, staying safe as a user, and security practices for builders.

Shared security

Every STRAT chain settles to the same Layer-0. Instead of each new chain bootstrapping its own security from scratch, chains inherit the security of the base layer from day one. See Architecture for how the layers fit together.

Audits and bug bounty

Staying safe as a user

  • Only use the official website and double-check the URL before connecting a wallet.
  • Never share your seed phrase or private keys. Nobody from STRAT Network will ever ask for them.
  • Read what you sign — check the contract, amounts and approvals in your wallet before confirming.
  • Prefer a hardware wallet for meaningful amounts, and revoke token approvals you no longer need.
  • Verify contract addresses and chain IDs against official sources, not links shared in DMs.

Security for builders

  • Build on audited libraries such as OpenZeppelin Contracts instead of re-implementing standards.
  • Test thoroughly — unit tests, fuzzing and invariant tests (for example with Foundry).
  • Get an independent audit before handling user funds, and fix findings before launch.
  • Protect admin keys with a multisig such as Safe, and put sensitive upgrades behind a timelock.
  • Monitor deployed contracts and have an incident-response plan ready.

Privacy preferences

We'd like to measure visits and performance with cookieless analytics. Nothing loads unless you allow it. See our Privacy Notice.