Skip to main content

Security

SLOHM's security comes from multiple layers: Bitcoin's consensus, OPNet's execution, and careful contract design.

Trust Assumptions

ComponentTrust LevelNotes
Bitcoin NetworkTrustless21M cap, PoW consensus
OPNet ExecutionTrustlessWASM deterministic execution
Smart ContractsVerifyOpen source, audited
BTC Multisig4-of-7Social trust in signers
Price OraclesMotoSwapOn-chain, manipulation-resistant

Contract Security

SafeMath

All arithmetic uses SafeMath to prevent overflow/underflow:

// Required
const result = SafeMath.add(a, b); // Reverts on overflow

Access Control

Critical functions are protected:

  • onlyMultisig — Treasury parameters, emergency functions
  • onlyAuthorized — Minting operations
  • onlyStaking — sSLOHM rebase

Bounded Loops

No unbounded iterations:

// Required
for (let i = 0; i < MAX_ITERATIONS; i++) { ... }

Attack Vectors & Mitigations

AttackMitigation
Price ManipulationMotoSwap pools with deep liquidity
Flash LoansBitcoin's 10-min blocks make impractical
Governance Attacks4-of-7 multisig requires social consensus
ReentrancyChecks-effects-interactions pattern

Audit Status

Coming Soon

Audit reports will be published before mainnet launch.

Bug Bounty

Coming Soon

Bug bounty details will be announced before mainnet launch.

Best Practices for Users

  1. Verify contracts - Check addresses before interacting
  2. Use hardware wallets - Never expose private keys
  3. Start small - Test with small amounts first
  4. Understand vesting - Bonds lock for ~5 days