Credit Coop
  • About Us
    • Introduction
    • Get in Touch
  • ⚙️About Our Products
    • Secured Line of Credit
      • Line of Credit Features (v1)
        • Cash Flow Financing
        • Deploying a Secured Line of Credit
        • Core Lending Functionality
        • Revenue-Based Lending Operations
        • Collateral Operations
        • Credit Events
    • The Spigot
      • Key features of the Spigot
      • Spigot Roles
        • Owner
        • Operator
  • ⚙️User Documentation
    • User Documentation (v1)
    • User Documentation (v2)
  • ⚙️DEVELOPER MATERIAL
    • Introduction
    • Deployed Contracts
    • V1 Developer Material
      • Architecture (v1)
      • Functions and Methods
        • LineOfCredit.sol
        • Oracle.sol
        • Spigot.sol
        • SpigotedLine.sol
        • Escrow.sol
        • EscrowedLine.sol
        • SecuredLine.sol
        • LineFactory.sol
        • Libraries
        • InterestRateCredit.sol
          • Accrued Interest Calculation
          • 'Interest Accrued' contract flow
        • Advanced Jargon
      • Repaying Debt - Function View
      • Valuation Oracle
      • Arbiter Role (v1)
        • liquidate() and declareInsolvent()
        • Spigot related functions
        • enableCollateral()
      • Edge Cases and Risk Situations
      • Security Audits
  • 💼Legal
    • Important Legal Notice
    • Terms of Use
    • Privacy Policy
Powered by GitBook
On this page

Was this helpful?

  1. About Our Products
  2. Secured Line of Credit
  3. Line of Credit Features (v1)

Deploying a Secured Line of Credit

PreviousCash Flow FinancingNextCore Lending Functionality

Last updated 7 months ago

Was this helpful?

Much of what follows is pre-configured and/or automated for users of the App.

A Borrower and a first Lender agree on some fundamental aspects:

Deployment parameters of the Secured Line of Credit

  • The deadline for repayment of the Line

  • The minimum collateral ratio

  • the revenue split (%)

  • the borrower address

Revenue-Based Lending

During Line deployment, a Spigot can be attached to a Borrower Revenue Contract, i.e. a smart contract owned and operated by the Borrower which will be used to secure the overall Line and automatically repay Credit Lines .

The single Spigot deployed can attach to multiple Borrower Revenue Contracts.

The Borrower and the first Lender must agree:

  • The address of the Borrower Revenue Contract

  • The initial default split of Revenue Tokens between the Borrower and Lenders (i.e. of the tokens from the Revenue Contract)

  • The trading router which, if needed, will convert the Borrower’s Revenue Tokens into the Credit Tokens actually borrowed and later repay (Credit Coop has already arranged this but the parties must agree anyway)

  • The whitelisted functions that the Borrower is allowed to perform on the Revenue Contracts whilst the Spigot is attached so that the Borrower operate as usual

  • The contract address of the Spigot , an address through which the Borrower can still conduct business as usual on the Revenue Contract within the constraints of the whitelisted functions. This is also the address through which the Borrower receives all remaining Revenue Tokens not escrowed in the Spigot for the benefit of Lenders.

Asset Collateral

If Asset Collateral is to be posted, the Borrower and the Lender must agree:

  • The collateral token(s), which must be whitelisted by the Servicer

  • The minimum collateral ratio to be maintained, if any.

⚙️
Operator