Remove hardcoded liquidity sources

[hu55a1n1]

Summary

• mtcs.Clearing/Run on enclave takes obligations and list of liquidity source addresses
  • alternatively, we could let the enclave be completely unaware of liquidity sources, and have the decryption of setoffs to liquidity sousrces happen publicly...

Related: #41

[hu55a1n1]

alternatively, we could let the enclave be completely unaware of liquidity sources, and have the decryption of setoffs to liquidity sousrces happen publicly...

@ebuchman not sure I understand what you mean by this. Can you clarify? (Do you mean we have the private keys for liquidity sources on the blockchain?)

[ebuchman]

do you mean we have the private keys for liquidity sources on the blockchain?

yeh pretty much, or at least public

[hu55a1n1]

This is an interesting idea! Thinking about it - tenders are not much different from obligations -> tenders are basically obligation with delegated ascertainment (where the ascertainer is the bank, or equivalently a third-party that can confirm the presense of backing funds, e.g. a smart contract, or a on-ramp solution).
Might make sense to design the system in a way that uses this insight.

[ebuchman]

This also taken care of by #52? How did we have 3 issues for this lol am I missing something?

Pretty sure its stale now given the new work on integrating liquidity sources so closing :)