Bando Docs
Launch AppLearn More
  • Bando for Developers
    • The On-chain Spending Protocol
    • Quickstart
    • Glossary
    • Use Cases
    • Protocol Architecture
      • Payment Reference Validation
      • Order Request
      • Order Fulfillment
      • Refunds
  • Spending Widget
    • Widget Quick Start
    • Installation
    • Configuration
    • Customization
    • Localization
    • Wallet Management
    • Framework Integration
      • Next.js
      • Svelte
  • Fulfiller API
    • Get Started with the API
    • Authentication
    • Guides
      • Get Available Products
      • Get a Payment Reference
      • Validate a payment reference
      • Get a Quote
      • Get Available Tokens for a Chain
    • API Reference
  • EVM Smart Contracts
    • EVM Smart Contracts | Architecture
    • Contracts
      • Core
        • BandoERC20Fulfillable
        • BandoFulfillmentManager
        • BandoFulfillable
        • BandoRouter
        • FulfillmentTypes
      • Libraries
        • FulfillmentRequestLib
        • SwapLib
      • Periphery
        • ERC20TokenRegistry
        • FulfillableRegistry
      • Proxy
        • Upgradeability
    • Security
      • Access Control
      • Security Considerations
      • Rekt Test
      • Audits
    • Code
Powered by GitBook
On this page

Was this helpful?

Edit on GitHub
  1. EVM Smart Contracts

Security

Smart contracts security considerations.

PreviousUpgradeabilityNextAccess Control

Last updated 6 months ago

Was this helpful?

There are a lot of layers we need to address about the security of our smart contract suite. To make sure our users and our customers have a secure and fast experience when spending their assets through Bando. As a best practice, we keep documenting the possible ways our smart contracts could be attacked. This is useful for security experts, pen testers, auditors, and our own researchers.

We also maintain and update a Rekt Test to continuosly have a simple assessment of our security practices:

Security Considerations
Rekt Test