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
  • External Methods
  • acceptsDeposit
  • acceptsTransfer
  1. Smart Contracts
  2. Contracts

ILPWhitelist

This is an optional component. If present it controls which Liquidity Providers can deposit or transfer their eTokens.

Each eToken has a whitelist parameter that if not null, points to a contract following this interface. Several eTokens can share the same whitelist contract or they can different ones.

External Methods

acceptsDeposit

function acceptsDeposit(contract IEToken etoken, address provider, uint256 amount) external view returns (bool)

Indicates whether or not a liquidity provider can do a deposit in an eToken.

Name
Type
Description

etoken

contract IEToken

The eToken (see {EToken}) where the provider wants to deposit money.

provider

address

The address of the liquidity provider (user) that wants to deposit

amount

uint256

The amount of the deposit

Name
Type
Description

[0]

bool

true if provider deposit is accepted, false if not

acceptsTransfer

function acceptsTransfer(contract IEToken etoken, address providerFrom, address providerTo, uint256 amount) external view returns (bool)

Indicates whether or not the eTokens can be transferred from providerFrom to providerTo

Name
Type
Description

etoken

contract IEToken

The eToken (see {EToken}) that the LPs have the intention to transfer.

providerFrom

address

The current owner of the tokens

providerTo

address

The destination of the tokens if the transfer is accepted

amount

uint256

The amount of tokens to be transferred

Name
Type
Description

[0]

bool

true if the transfer operation is accepted, false if not.

PreviousAAVEv3AssetManagerNextLPManualWhitelist

Last updated 1 year ago