Portfolio contract

[hieronx]

• Stores list of items (fka loans, assets), with

struct Collateral {
  IERC6909 source;
  uint256 id;
}

struct Item {
    address owner;
    Collateral collateral;
    uint128 outstanding_quantity;
    uint128 outstanding_normalized_debt;
    IERC7726 valuation;
}

mapping (uint64 poolId => mapping (uint128 itemId => Item)) items;

• Write methods to
  • create(uint64 poolId, address collateralSource, uint256 collateralId, address owner)
    • locks ERC-6909 NFT
    • create item in storage
  • increase_debt(uint64 poolId, itemId, amount)
    • only callable by owner
  • decrease_debt(uint64 poolId, itemId, principal, interest, unscheduled)
    • only callable by owner
  • transfer_debt(uint64 poolId, ..)
    • only callable by owner

[lemunozm]

Some questions to confirm I am on the line:

• increase_debt() and decrease_debt() AFAIK do not deposit/withdraw any amount from the pool reserve. I understand this Portfolio contract as a building block to create something more complex on top of this if required (like a contract that can borrow/repay, modifying the pool amount). Am I right?

  • I think at this level unscheduled is not needed because the only purpose of that IIRC was to deposit extra amount in the pool.

• What happens with valuations as DCF? Is it supposed that the computed DCF valuation comes from the ERC7726? That way, the interface for what we called "internal" and "external" in Centrifuge Chain is the same now through IERC7726

  • One thing I worried about this is that DCF needs some properties from the item to be computed correctly, as the interest rate or the maturity/origination dates (that I guess should be stored in the Item). Not sure how that information can be passed through ERC7726

[hieronx]

increase_debt() and decrease_debt() AFAIK do not deposit/withdraw any amount from the pool reserve. I understand this Portfolio contract as a building block to create something more complex on top of this if required (like a contract that can borrow/repay, modifying the pool amount). Am I right?

Yep exactly!

I think at this level unscheduled is not needed because the only purpose of that IIRC was to deposit extra amount in the pool.

What happens with valuations as DCF? Is it supposed that the computed DCF valuation comes from the ERC7726? That way, the interface for what we called "internal" and "external" in Centrifuge Chain is the same now through IERC7726

Yes I anticipate we will eventually have (at least) 3 valuation contracts adhering to ERC7726: oracle, at par (outstanding debt), and DCF. The DCF valuation contract will then return the DCF value for some item.

One thing I worried about this is that DCF needs some properties from the item to be computed correctly, as the interest rate or the maturity/origination dates (that I guess should be stored in the Item). Not sure how that information can be passed through ERC7726

Yeah the DCF valuation contract would need additional storage per item, stored in that contract I would expect.