Ensuro Docs
  • Introduction
    • General Questions
    • Risk Management
  • Liquidity Providers
    • FAQ - Liquidity Providers
    • Onboarding process
  • Risk Partners
    • FAQ - Risk Partners
    • Onboarding process
    • Flow
  • Deployments
  • Audits
  • Smart Contracts
    • Architecture
    • Roles and permissions
    • Governance
    • Policy Lifecycle
    • Policies
    • Liquidity pools
    • Premiums Accounts
    • Reserves
    • Asset Management
    • Contracts
      • PolicyPool
      • EToken
      • RiskModule
        • TrustfulRiskModule
        • SignedQuoteRiskModule
        • SignedBucketRiskModule
        • FlightDelayRiskModule
        • PriceRiskModule
      • PremiumsAccount
      • AccessManager
      • IAssetManager
        • LiquidityThresholdAssetManager
        • ERC4626AssetManager
        • AAVEv3AssetManager
      • ILPWhitelist
        • LPManualWhitelist
      • Extensions
        • ERC4626CashFlowLender
        • ETokensBundleVault
        • MultiStrategyERC4626
  • Offchain APIs
    • Introduction
    • Callback notifications
    • API Reference
      • Pricing API
      • Offchain API
  • Frontend
    • Security and Monitoring
  • Legal & Compliance
    • Trust & Security in Ensuro's Ecosystem
  • Ensuro Risk Disclosures
  • Fees & Charges
  • Specific Responsibilities and Expectations of Retail Investors
  • Confirmation of Acceptance of Participation Agreement and Token Holder Terms & Conditions
  • Ensuro Terms of Service
  • Restricted Jurisdictions
  • Participation Agreement for Token Holders
  • Ensuro Anti-Money Laundering & Anti-Terrorism Financing Policy Statement
  • Privacy Policy
  • Ensuro Data Protection Policy
  • Cybersecurity Guide for Ensuro Protocol Investors
  • Tax Guide for Ensuro Protocol Investors
Powered by GitBook
On this page
  • Component roles
  • Events
  • LPWhitelisted
  • External Methods
  • whitelistAddress
  1. Smart Contracts
  2. Contracts
  3. ILPWhitelist

LPManualWhitelist

PreviousILPWhitelistNextExtensions

Last updated 1 year ago

This is an implementation of the interface that just has a mapping (address -> bool) indicating whether or not a liquidity provider with a given address is whitelisted.

All the addresses are blacklisted by default. To whitelist an address, an authorized user with the LP_WHITELIST component role needs to call whitelistAddress(provider, whitelisted).

Component roles

The specific roles and functions of the contract are as follows:

Role
Global*
Description
Methods Accessible

LP_WHITELIST_ROLE

Whitelist or un-whitelist addresses manually.

LP_WHITELIST_ADMIN

Manages the LP whitelisting system.

  • setWhitelistDefaults: Set the default whitelist status for LP addresses.

( * ) Global means that the role can be delegated to a user at the protocol level (for all components) or only for a specific component. Non-global roles can only be granted for a specific component.

Events

LPWhitelisted

event LPWhitelisted(address provider, bool whitelisted)
Name
Type
Description

provider

address

The address to be whitelisted.

whitelisted

bool

If true, the provider was whitelisted.

External Methods

whitelistAddress

function whitelistAddress(address provider, bool whitelisted) external

: Adds or removes provider addresses from the whitelist manually.

ILPWhitelist
whitelistAddress