MichelSantos

We have an initial version of a [precautions page](https://github.com/bitshares/bitshares-core/wiki/Custom-Authority-Precautions)

This well-written proposal presents a fascinating concept. Below are some of my editorial comments. > Requires a ticket This is the first mention of ticket. I suggest a link. >...

@abitmore Also implied in your description is that the list of maintainers are: - _self-appointed or appointed by some central entity_, and - they must control the Ethereum contract to...

> HTLC is likely can be used to get rid of proof-feeding. That's intriguing: how could we combine HTLC with `account_fund_sink`

I can understand the reasoning for a moving average of the price rather than the current price to smooth out "unusual" spikes. I don't agree with feed providers implementing the...

@froooze - _Source of funds in the liquidity pool_: There is an aspect of the proposal which I think is vague: where do the funds from the liquidity pool come...

> > What is the staking mechanism? Are you implying that people will lend money to the pool at interest? > > There is no interest rate only speculation to...

> > ``` > > * _Which liquidity pools?_: Can the target asset be anything besides BTS? Which liquidity pair pools will exist? Who can determine which liquidity-pair pools will...

@froooze Thank you for the helpful explanations. To help our discussion further, I'd like to define the following parties: 1. Blockchain 2. Account Alice: The blockchain lent 333 bitUSD to...

> > Consequently` if the 67 bitUSD is confiscated by the blockchain, how can the liquidity pool pay back Charlie? > > * the percentage of the borrowed part does...