BONKbot Docs
BONKbot.ioStart Trading
  • πŸ‘‹Welcome to BONKbot
  • Overview
    • πŸ’‘What is BONKbot?
  • Quick Setup Guide
    • πŸ‘£Get started on Solana
    • πŸ› οΈInitializing BONKbot
    • πŸ’²Funding Your Wallet
      • 🏦Depositing SOL
      • πŸ’±Buying SOL
    • πŸ”Setting Up 2FA
  • Settings
    • πŸ“ŠSettings
    • πŸ‘»Minimum Position Value
    • πŸ’³Auto Buy
    • πŸ”‘Security Config
    • πŸ’°Buy/Sell Buttons Config
    • πŸ’ΈSlippage Config
    • πŸ€–MEV Protection
    • ⛓️Transaction Priority
    • πŸ’²Sell Protection
  • SAFETY & SECURITY
    • βš™οΈHow to Trade Safely
      • πŸ–¨οΈMint Authority
      • ❄️Freeze Authority
      • πŸ”₯LP Burnt
    • ⚠️Avoiding Scams
    • πŸ”’The Signer Overview
    • 🌐User Benefits and Rollout
  • Trading Basics
    • πŸ’³Buying Tokens
    • πŸ“ŠManaging your positions
    • πŸ€‘Selling Tokens
    • πŸ˜Άβ€πŸŒ«οΈHide Tokens
  • Advanced Trading
    • πŸ“”Limit Orders
      • πŸ’ΉLimit Buy
        • Buy Dip
        • Buy Breakout
      • πŸ’°Limit Sell
      • πŸ“‰Trailing Stop Loss
      • πŸ‘¨β€πŸ’»Managing Limit Orders
    • πŸ’±DCA
      • πŸ’³DCA Buy
      • πŸ’·DCA Sell
      • 🏦Managing DCA Orders
  • Features
    • 🀝Refer a Friend
    • 🀝Deep Links
    • πŸͺ™Token Incinerator Program
  • Community & Support
    • πŸ”How to Find Tokens
    • πŸ”₯How to Burn Tokens
    • ⏰BONKbot Alert Channel
    • πŸ€–Multiple Bots
    • πŸ’²BONKbot Fee Structure
    • πŸ«‚Support your Community
  • FAQ
    • ❓FAQ
      • πŸ’΅Wallet FAQs
      • 🀝Trading FAQ
      • πŸ“ƒSigner FAQs
      • ❓Misc. FAQs
Powered by GitBook
On this page
  1. SAFETY & SECURITY

Technical Breakdown

For a deeper dive in the tech underneath.

Last updated 8 months ago

This page details a high level summary. Click for the full article.

Key Security Features:

  • Secure Boot Process: Only pre-authorized firmware, kernel, and application versions can access the identity key controlled by the TPM.

  • Unikernel Approach: BONKbot’s KMS uses a custom, minimal Linux kernel combined with the KMS application to reduce the attack surface.

  • Remote Attestation: The TPM verifies that only authorized KMS applications are running in a secure state.

  • Encrypted Master Key: The KMS master key is encrypted and can only be decrypted by authorized systems using their identity key.

  • Process Isolation: The central Signer process has no direct network access and only communicates via the Message Bridge, minimizing attack vectors.

  • Ephemeral Key Handling: User private keys are decrypted only in memory for the duration of the signature calculation, reducing the exposure to memory-based attacks.

  • 2FA Protection: Sensitive actions such as private key exports and withdrawals are further secured by 2FA.

🧠
here