Closed MichelSantos closed 4 years ago
Original post by @MichelSantos in the paragraphs below. I inserted the draft BSIP text above so we may continue discussion in the comments section of this Issue before advancing it as a PR.
A working draft of a "Lending for Margin Trading" BSIP is [above]. We are seeking feedback about financial concepts from potential users and software concepts from developers. Certain aspects that still need to be determined are labeled with "TBD" (for "to be determined").
This BSIP variant has selectively restricted the features that are anticipated to be useful for users of the blockchain while still being something that might be deployed within an earlier consensus release. More advanced features are labeled with "future BSIP" and are expected to augment this feature set. Developers who might implement this feature set might make design decisions that are future-compatible with these potential features.
For example, someone who has an open call order on CNY with a CR of 1.6 may borrow CNY at a lower CR and sell the borrowed CNY to himself in order to free up his locked collateral. He has then offloaded part of the risk from his call order to the lender. (Arguably on conditions that the lender has accepted, so calling this a scam is debatable.)
Much worse than that is the fact that even the most liquid markets are operating with a spread, and that spread can become significant (i. e. > 1%) for a short period of time. A spread allows the borrower to round-trip trade with himself, transferring value out of the loan portfolio. Many such roundtrips can be squeezed into a single transaction, so even with a tiny spread a significant amount of value can be siphoned off per block.
I think the reference price should be determined not only by looking at past trades, but also depending on the current state of the order book. The order book is what matters when a loan portfolio is margin called. Such a margin call executes only against one side of the order book, and a large loan can have significant effect on the market when margin called, meaning that past trades are not a good measure for the appraisal of the loan portfolio.
The suggested method for margin calls, which is effectively a market order to sell everything, is dangerous. Its effect is comparable to a stop-loss order, which is known to be dangerous if publicly known in advance.
I have more detailed remarks, but I will wait for the PR.
This is probably one of the best upgrades BitShares could get, really hope we can make this happen.
@pmconrad and other reviewers: My desire is to see sufficient discussion/refactoring of the draft BSIP text in this Issue prior to making the PR from the outcome thereof. @MichelSantos as the author will moderate this discussion and incorporate changes. The Description text should be the most recent and used as the initial PR when deemed complete and ready for posting.
This needs to pass. Agree with kong, all hands on deck to make this happen.
Great stuff - hits so many of our trouble spots!
Quite a few of the CEXs have insurance funds they build up through fees - would we do something similar?
The layman in me wants to know how close would this bring us to a BitMEX 50x 100x etc trading platform type functionality? My understanding is this will mainly get us the bones of the functionality - I'd be keen to see the UI stuff bundled in or a separate worker put forward for a really clean BitMEX type interface for it that everyone coming in will just see and know how to use.
haven't gone through all the details, but I believe this is what Bitshares need, let's move it forward.
Just thinking about businesses building atop this - can we make sure we include some facility / approach to them making money?
For example, apart from the margin trading this will also make us a peer to peer decentralised lending platform... There needs to a mechanism in place allowing a business that decides to leverage this to make a profit (i.e. justify investing in the interface, publicity, business costs etc).
This is also a consideration for the trading - how does a company launching and promoting BitDEX make its money?
I guess it needs to be through the fee structure or allowing some third party to take a % mark up on values by facilitating...?
1. IMO the restriction on a single trading pair is not sufficient to prevent an exit scam.
For example, someone who has an open call order on CNY with a CR of 1.6 may borrow CNY at a lower CR and sell the borrowed CNY to himself in order to free up his locked collateral. He has then offloaded part of the risk from his call order to the lender. (Arguably on conditions that the lender has accepted, so calling this a scam is debatable.)
Would it be possible to create a new order type, so borrowed funds can only be used to open a position that has to be closed, rather than just selling borrowed funds and them being added to users balance where they can do whatever they want with it. Perhaps it could be part of the borrowing function, so when a user borrows funds they also have to input their desired position, eg: long/short, position size, collateral, margin ratio. The borrowed funds would then be put straight into an open position and once closed, whether by choice of forced, borrowed funds are repaid.
I don't see any issue with them doing what they like with it to be honest - what they are doing in that example is reducing their risk of having their smartcoin margin position forcibly closed by agreeing to pay interest on a loan. The person lending should be aware of the risks around loaning and set their rates to suit.
Best to leave it to the market to find the acceptable rates during different market conditions - i.e. during a bear market if loads of people want to borrow to try and protect their position then people with large stacks to lend can get really good returns (noting those really good returns are in part because of the market risk!)
My desire is to see sufficient discussion/refactoring of the draft BSIP text in this Issue prior to making the PR from the outcome thereof.
Agree that concept and mechanics should be agreed upon before the PR. PR is better for in-detail discussion of the text, e. g. typos, wording etc. .
Quite a few of the CEXs have insurance funds they build up through fees - would we do something similar?
The the operations for creating and matching loan positions would be new so they would have their own distinct fees. Because of the new computational and memory load that loan positions would impose on block producer nodes, these fees should be enough to at least compensate the block producers.
Whether the loan fees should be even higher to build an insurance fund is interesting. No risk is being taken on by the blockchain with this proposed lending loan because the main risk is being taken on by the lenders. But if the idea is to use fees from loans to pay for insuring some other activity on the blockchain, that could technically be done. However the real-world issue is do you want to have one activity's users insure another activity's users?
If that idea is desirable I think that two things need to be identified:
The layman in me wants to know how close would this bring us to a BitMEX 50x 100x etc trading platform type functionality? My understanding is this will mainly get us the bones of the functionality - I'd be keen to see the UI stuff bundled in or a separate worker put forward for a really clean BitMEX type interface for it that everyone coming in will just see and know how to use.
I agree that we should discuss with at least the reference wallet team if for no other reason than this: there will potentially be numerous small loans in their own loan portfolio as this BSIP is currently conceived. This is done to better protect the lenders by uniquely tracking collateral ratios for each loan.
But the consequence is that there will potentially be numerous loans held by borrower, and also by lenders. Each loan portfolio will be traded separately from the others at the discretion of the borrower. This probably needs to be simplified and consolidated for regular users by default. We need to identify useful API calls for client software that will make handling the numerous loan portfolios/margin wallets that are held by a borrower to be fast, efficient, and not cumbersome.
But the next consequence is that it may increase the memory requirements on API nodes.
Just thinking about businesses building atop this - can we make sure we include some facility / approach to them making money?
For example, apart from the margin trading this will also make us a peer to peer decentralised lending platform... There needs to a mechanism in place allowing a business that decides to leverage this to make a profit (i.e. justify investing in the interface, publicity, business costs etc).
I think that this largely depends on the imagination of the business. Businesses like individuals can use the platform now. If we had something more concrete we could evaluate what might need to be baked into the blockchain that isn't already there.
Would it be possible to create a new order type, so borrowed funds can only be used to open a position that has to be closed, rather than just selling borrowed funds and them being added to users balance where they can do whatever they want with it. Perhaps it could be part of the borrowing function, so when a user borrows funds they also have to input their desired position, eg: long/short, position size, collateral, margin ratio. The borrowed funds would then be put straight into an open position and once closed, whether by choice of forced, borrowed funds are repaid.
Let's take an example: a Borrower is lent 70 bitUSD (the lent asset) to trade against bitBTC (the tradeable asset). The Borrower is limited in the following ways:
The point is that the Borrower cannot short with any funds that are inside of the "margin wallet". Does this address your main concern? Is this too limiting for the use cases that you had in mind?
The idea of lending that instantly creates a limit order against the tradeable asset is a technical possibility but I wonder if it might be too restrictive.
Minor: Assuming typo in section 4b, formula for daily interest rate. (Ddaily should not exceed principle P.)
This seems like a great idea and the mechanism is extremely well articulated.
- I am against a restriction, what the lender can do with the asset, because he pays interest and potential use cases are too much limited.
A restricted use case though is what makes this whole thing work. Without the restriction, the lender would need the ability to assess the credit-worthiness of individual borrowers, and then this becomes a much more complicated endeavor. As it stands, a "loan ask" can be taken up by any borrower precisely because the usage of the principle is narrowly defined. The lender can set the interest rate based on the risk profile of the activity, NOT the risk profile of the borrower.
@christophersanborn: The intention was to have a MCR of under 1? We should not exclude the case for risk profile of the borrower, because we need only to increase MCR and Interest rate, for this case.
@christophersanborn: The intention was to have a MCR of under 1?
@froooze the intention is to have MCR ≥ 1
We should not exclude the case for risk profile of the borrower, because we need only to increase MCR and Interest rate, for this case.
The lender and the borrower can agree to any MCR ≥ 1, and any interest rate
The data about each borrower will be on blockchain. If that is very important then the client interface can show the credit history of the borrower while a lender is reviewing "borrow offers" from lender.
Remember that this proposal matches loans in a three step-process.
If borrower posts a "borrow offer", potential lenders can review credit history of borrower, and choose whether to accept the offer. If lender posts a "lend offer", then any borrower who is willing to agree to the lender's terms can select it.
More conservative lenders may prefer to select "borrow offers" instead of posting "lend offers".
1. I am against a restriction, what the lender can do with the asset, because he pays interest and potential use cases are too much limited.
This proposal is limited to lending for margin trading purposes. To use borrowed assets for another purpose will require a different BSIP.
2. The UI needs to show metrics from past borrows, to allow the market a fair risk management. If the borrower has no track record, he has to pay higher interest rates.
This is possible for the case when borrowers make the initial "borrow offer" because past borrow history is on blockchain. It will be helpful to estimate how much is the demand by lenders to show this data in the UI.
3. Interest rates are calculated in percentage of borrowed bitAsset, but should be paid in BTS?
Payment of principal and interest must be paid in the original asset type that was borrowed.
Let's take an example: a Borrower is lent 70 bitUSD (the lent asset) to trade against bitBTC (the tradeable asset). The Borrower is limited in the following ways:
* the Borrower can hold the bitUSD in the "margin wallet" * the Borrower can optionally trade back and forth against bitBTC but all balances are contained within that specific "margin wallet" * the Borrower can [only withdraw any "excess" bitBTC](https://github.com/bitshares/bsips/issues/170#withdrawals) (excess is that amount of bitBTC that ensures enough collateral to satisfy the minimum collateral ratio that is agreed with the lender) from the "margin wallet" into his/her regular balances
The point is that the Borrower cannot short with any funds that are inside of the "margin wallet". Does this address your main concern? Is this too limiting for the use cases that you had in mind?
The idea of lending that instantly creates a limit order against the tradeable asset is a technical possibility but I wonder if it might be too restrictive.
This adresses my concern and sounds like a much better idea, it offers control and more freedom. I like it.
This proposal is limited to lending for margin trading purposes. To use borrowed assets for another purpose will require a different BSIP.
Why do we need a different BSIP? Would be this BSIP not the same, except the market limitation?
If a borrower has less limitations, the market will price in the extra risk.
It makes sense to have some limitations available, but should not forced on everyone.
@froooze the use-case in this BSIP is extremely limited because it allows the chain to use the complete loan portfolio, including the borrowed funds as well as any gains from trading, as collateral for the loan. This in turn is what makes margin trading possible at all.
If we allow the user to transfer value out of the loan portfolio, the chain has no means to ensure that the loan will be paid back. Note that a CEX has means of going after the borrower off-chain, and thus has a different risk profile than a smart contract between more or less anonymous participants.
The borrower must be restricted otherwise they can exploit it fairly easily by taking loans and extracting money or pumping other coins the lender didnt specify in order for them to exit scam. A restriction is how every other implementation of margin trade / lending works too so this is normal. Have seen from great feedback so far.
Has the core team any major concerns on a technical level for this implementation?
Has the core team any major concerns on a technical level for this implementation?
The details are not sufficiently spec'd out to answer that at this time.
I believe that in order to prevent exit scams, the load portfolio must be appraised for every operation instead of just once per maintenance interval. This could have a significant impact on performance.
The details are not sufficiently spec'd out to answer that at this time.
Thanks, what needs more specification ?
I believe that in order to prevent exit scams, the load portfolio must be appraised for every operation instead of just once per maintenance interval. This could have a significant impact on performance.
That seems excessive. It is up to the lender to specify the markets they enable the borrower to margin trade on, they take on the risk. If the Borrower uses the loan for buying illiquid coins and exiting a position they hold outside of this contract then that is a risk the lender must evaluate- doesnt need any intervention outside of that.
If we allow the user to transfer value out of the loan portfolio, the chain has no means to ensure that the loan will be paid back. Note that a CEX has means of going after the borrower off-chain, and thus has a different risk profile than a smart contract between more or less anonymous participants.
@pmconrad I agree that this would be ideal. In fact, one could argue that it even needs to be evaluated even more frequently to quickly act on collateral ratios that are below MCCR.
Alternatively, if loan portfolios will not be appraised every block in a deterministic manner, we have a UX problem where what the borrower and lender view for the loan appraisal inside of their client interface (which influences margin calls, withdrawal limits, and trading limits) might differ from what the blockchain is acting on. In other words, if the portfolios are only appraised once every 24 hours, but the user is calculating the loan in between or the reference wallet is calculating it in between, then the users may be upset unless it is very clear when the appraisals will be performed. Even then, we might consider logging in a virtual operation the price of the loan portfolio that was appraised by the blockchain.
The details are not sufficiently spec'd out to answer that at this time.
Thanks, what needs more specification ?
@cloud-8: pmconrad mentioned what I also think is a computationally expensive task that may occur relatively frequently for BitShares standards: appraising the loan portfolio. This must be done to determine withdrawal limits, trading limits, calculate collateral ratios, and to properly execute loan closures.
Other specifications that are pending are listed at https://github.com/bitshares/bsips/issues/170#software-specs
I believe that in order to prevent exit scams, the load portfolio must be appraised for every operation instead of just once per maintenance interval. This could have a significant impact on performance.
That seems excessive. It is up to the lender to specify the markets they enable the borrower to margin trade on, they take on the risk. If the Borrower uses the loan for buying illiquid coins and exiting a position they hold outside of this contract then that is a risk the lender must evaluate- doesnt need any intervention outside of that.
It might be that a periodic appraisal is a practical implementation however this appraisal schedule should be clearly known both before the loan is initiated and while the loan is open.
Much worse than that is the fact that even the most liquid markets are operating with a spread, and that spread can become significant (i. e. > 1%) for a short period of time. A spread allows the borrower to round-trip trade with himself, transferring value out of the loan portfolio. Many such roundtrips can be squeezed into a single transaction, so even with a tiny spread a significant amount of value can be siphoned off per block.
@pmconrad Assuming for the moment that the reference price is "valid", I think that this scenario is prevented by the conditional withdrawal limits and conditional trading limits.
Let's consider an example where:
As I understand your scenario, the following would be attempted.
Borrower trades Bliquid for Tliquid but is limited by the restriction on new trades by Btradenew. Let this first trade value equal B1. Because of the aforementioned spread the value of T1 is worth less than B1 when measured in B.
Borrower withdraws as much Tliquid as is permitted by the withdraw limit (Wlimit which ensure that the PA ≥ MCP at the time of the withdrawal). Let this first withdraw amount be defined as T1W where T1W ≤ T1 because of the withdraw limit.
Borrower uses T1W in his regular balances to go back on the market and trade back into B2 at the reverse spread thus losing more value.
Borrower deposits B2 from his regular balances into the loan portfolio.
Return to Step 1
This repetition appears to me to be a financial loss for the Borrower because of losses due to loan fees, losses due to trading fees, and losses due to two trades on a market with spreads during one cycle. The two limits appear to protect the Lender's equity by limiting a Borrower's ability to perform new trades and withdrawals.
But returning to the assumption that the reference price is "valid". Can this cyclical process alone affect that reference price over a single block? I don't currently see how it be more than any regular trading.
- I think the reference price should be determined not only by looking at past trades, but also depending on the current state of the order book. The order book is what matters when a loan portfolio is margin called. Such a margin call executes only against one side of the order book, and a large loan can have significant effect on the market when margin called, meaning that past trades are not a good measure for the appraisal of the loan portfolio.
@pmconrad I share your concern but it's not clear to me that alternatives are better. One alternative might be to use external feeds but then we get into the debate about what is a true price and what is an acceptable "adjustment" of the price feed.
Let's consider an example
Initially, Bliquid = K + P, Tliquid = 0. Btrade = Bliquid - K = P. Suppose the market price is R and the spread is S, i. e. there are orders on the book at R±S. Borrower has sufficient Tsock in his other wallet or sockpuppet account.
In one such cycle, an amount of Btrade (1 - (R-S)/(R+S)) = Btrade 2 S / (R+S) is transferred from borrower to sockpuppet. This is profitable as long as that amount is worth more than (4 limit_order_create_fee + 2 market_feeT + 2 market_feeB).
Problem 1: Multiple such cycles can be packed into a single block, so it is possible to drain the loan portfolio far below MCR very quickly, which damages the lender.
Problem 2: If the total transferred value minus fees can be made greater than K, borrower can make a profit from ripping off the lender. The only limiting factors here are the spread in relation to the market price, and the fees. Fees are typically far below the spread, which makes the attack highly likely.
use external feeds but then we get into the debate about what is a true price and what is an acceptable "adjustment" of the price feed.
We should avoid that at all costs. :-)
Let's consider an example
Initially, Bliquid = K + P, Tliquid = 0. Btrade = Bliquid - K = P. Problem 1: Multiple such cycles can be packed into a single block, so it is possible to drain the loan portfolio far below MCR very quickly, which damages the lender.
Problem 2: If the total transferred value minus fees can be made greater than K, borrower can make a profit from ripping off the lender. The only limiting factors here are the spread in relation to the market price, and the fees. Fees are typically far below the spread, which makes the attack highly likely.
@pmconrad Thank you for the detailed steps.
This scenario can happen but the loan portfolio's CR will remain above MCCR. If it reaches MCCR a margin call will be initiated.
The trading mechanism as currently described does permit the borrower to trade when the collateral ratio of the loan portfolio (CR) trades anywhere above MCCR subject to the minimum Bliquid. The loan agreement stipulates that MCCR be close to or far from MCR.
Do you recommend that the difference between the MCCR and MCR be limited such that K is enough to cover that gap? Or should the lender and the borrower be permitted to agree to other terms?
This scenario can happen but the loan portfolio's CR will remain above MCCR.
Yes, if appraisal happens before each single trade instead of just once per day.
This scenario can happen but the loan portfolio's CR will remain above MCCR.
Yes, if appraisal happens before each single trade instead of just once per day.
@pmconrad The triggering of loan appraisals and the fees section has been updated to reflect your recommendation.
If the balance is insufficient, the smart contract shall place an "effective" market order of the entire balance of the tradeable asset. The effective market order shall be performed by creating a limit order asking for one satoshi of the borrowed asset type in exchange for the entire balance of the tradeable asset.
Like I said, the "effective market order" is dangerous. Possible alternatives:
min_to_receive
= outstanding debt (or percentage thereof)Like I said, the "effective market order" is dangerous. Possible alternatives:
place an order with
min_to_receive
= outstanding debt (or percentage thereof)return collateral to lender directly and let him handle it manually
let the lender specify one of these options in the loan offer
@pmconrad These recommendations are better than what was written because they do not assume a liquid market and can therefore better protect the value of the loan portfolio from plummeting which protects the lender, and because they reduce the order's influence on that market pair's order book.
This does leave open the possibility that the margin call may not be filled and remain on the order books. Therefore, we are making use of the limit order's expiration such that it that is a term of the loan. If the margin call's limit order expires, a loan confiscation will be automatically triggered to repay the lender. For contrast the prior version of the text only had loan confiscation as an optional action.
We have also clarified that a margin call will only sell off the tradeable asset if and only if the balance of the borrowed asset type is insufficient to pay back what is owed which is the principal plus the last day of interest.
1. I am against a restriction, what the lender can do with the asset, because he pays interest and potential use cases are too much limited.
This proposal is limited to lending for margin trading purposes. To use borrowed assets for another purpose will require a different BSIP.
I don't see the necessity for this restriction, with restriction the feature should be named "leverage trading", not "lending margin call", why not do a general "lending margin call" feature without restriction on how the borrower will use the borrowed assets? I feel this has much bigger market demand.
1. I am against a restriction, what the lender can do with the asset, because he pays interest and potential use cases are too much limited.
This proposal is limited to lending for margin trading purposes. To use borrowed assets for another purpose will require a different BSIP.
I don't see the necessity for this restriction, with restriction the feature should be named "leverage trading", not "lending margin call", why not do a general "lending margin call" feature without restriction on how the borrower will use the borrowed assets? I feel this has much bigger market demand.
The two types of lending should absolutely be separated in my opinion, I am not against a lending system where the borrower can do as they please but it should be separate from margin trading loans.
We should not create a generalised lending system with the intention of it being used in the markets for leveraged trading (although they could), the markets should have their own systems with restrictions.
A lending system without restrictions will inevitably have higher rates as there will be more risk for the lender, separating the systems removes that risk from the markets with restrictions and lowers the lending rates.
Having separate systems would also perhaps help users price their loans as they could look at restricted loans and see they should price there generalised loans more expensive.
Either way, margin trading loans should be restricted.
1. I am against a restriction, what the lender can do with the asset, because he pays interest and potential use cases are too much limited.
This proposal is limited to lending for margin trading purposes. To use borrowed assets for another purpose will require a different BSIP.
I don't see the necessity for this restriction, with restriction the feature should be named "leverage trading", not "lending margin call", why not do a general "lending margin call" feature without restriction on how the borrower will use the borrowed assets? I feel this has much bigger market demand.
@bitcrab Having lending without restrictions or different restrictions is certainly an option. And I agree that it is even a larger market. However I think that it should be a separate BSIP for two reasons.
The first reason is that lending without restriction is a type of lending with different risks for the lender, and with different risks for the stability of smart assets.
The second reason is for practicality. Several features of "lending for margin trading" have already been removed such that what remains is a minimum viable product that can be used on BitShares as soon as possible. The more advanced features, which appear in draft text with the words "future BSIP", may be proposed for implementation in the future.
If "leveraged trading" is more intuitive to users then I have no objection. The current label of "lending for margin trading" is intended to distinguish itself from alternative lending mechanisms that have different restrictions and use cases like the one that you and @froooze are advocating. Multiple lending mechanisms can co-exist on BitShares.
Having separate systems would also perhaps help users price their loans as they could look at restricted loans and see they should price there generalised loans more expensive.
@CryptoKong I think that it will be fascinating to see how different interest rates appear under different lending mechanisms. Even within a single lending mechanism like the one described here, I expect to see a variety of interest rates and durations between different pairs of assets, and even different "directions" such as borrowing BTC to trade against USD versus borrowing USD to trade against BTC.
Following peer to peer lending issue occurred for Poloniex. How do u plan to handle such situation for dramatic price crash observed in CLAM token ? https://medium.com/circle-trader/overview-of-btc-margin-lending-pool-losses-a2f0905aaa56 @MichelSantos
@manikey123 see Stage 6 - Margin Calls.
A price crash in collateral can lead to some loan positions being margin called, and if market liquidity is insufficient some loan portfolios may be confiscated and returned to the lender. It is possible that the lender suffers a monetary loss from this procedure. By offering the loan, the lender accepts that risk, and he can choose the terms of loan to offset this risk.
Note that other than Poloniex, each loan portfolio stands for itself. The loss of one loan position is not covered by all other open loans.
While working on the specification section I have run into the following questions:
IMO the "Reference Price" is not just an implementation detail, it is absolutely crucial for the success of this mechanism. I feel I'm lacking the financial background to come up with a reasonable suggestion. Please discuss here.
Please add a section to "Discussion" where asset flags and black/whitelists are considered. E. g. an "override_transfer" cannot be applied to funds inside a loan portfolio.
Please add a section to "Discussion" where the consequences for voting of core asset in loan portfolios are discussed. (IMO it is clear the core in lending offers and borrowing offers should vote for the owner of the offer. For core in loans it is not clear, and perhaps should be different of the portfolio is margin called.)
Please consider rewording certain uses of "price". A price is a ratio of two denominations. E. g. "Maintenance collateral price" is not a price but rather a valuation expressed as an amount of one asset.
Special cases for reference price:
The liquidation plan should include settlement if the tradable asset is in global settlement. If the tradable asset is an MPA and has a valid feed price at the time of confiscation, should the lender receive only enough of it (in terms of feed price and settlement offset) to cover the missing debt?
Here's one for the "Risks" section:
A margin call on a loan portfolio will immediately try to buy large amounts of the borrowed asset from the market. This can lead to a sudden spike in the trade price. This in turn can affect the reference price, which could lead to additional margin calls in other portfolios.
Below is my current draft version of the "Specification" section.
I have slightly expanded on the operation definitions in the OP. E. g. the offers contain min and max amount, and the acceptor can choose how big the loan will be. I have also specified that an offer stays if it partially accepted and the remaining part exceeds the min value.
I'm unsure whether it would be easier to replace the explicit accept
operation with an offer matching algorithm. Probably yes - leaving it out doesn't save us very much in terms of complexity whereas adding it later will require a new and slightly more complicated BSIP.
Note 1: Interest is paid every 24 hours, regardless of local calendar. E. g. Daylight Savings Time is ignored.
Note 2: Percentage-based calculations (interest, CR) are always rounded up to the next possible value (aka "satoshi").
Note 3: MCR and MCCR are expressed in the same way as in the existing price feed logic, i. e. only the part above 100%, and as a scaled percentage value. E. g. a value of 4200
would mean 142%
.
Note 4: "Implementation hints" are not to be considered part of the formal specification, but merely as a possible implementation.
lending_offer_object
(new)Fields:
lending_offer_id_type id
- The object IDaccount_id_type owner
- The lending account IDasset_id_type loan_asset
- The asset type that the lender is offering to lendshare_type min_amount
- The minimum amount of the asset type that the borrower must borrowshare_type max_amount
- The maximum amount of the asset type that the lender is offeringunsigned_int mcr
- The minimum collateral ratio that the lender is expecting at the beginning of a loan, as a scaled percentageunsigned_int mccr
- The collateral ratio below which a margin call of the loan is initiated, as a scaled percentageunsigned_int max_call_duration
- The maximum duration of a margin call in seconds, if one is necessary, after which a portfolio confiscation will be triggeredasset_id_type tradable_asset
- The asset type that the lender permits the borrower to trade againstunsigned_int min_duration
- The minimum duration of the loan that the lender is willing to accept, in daysunsigned_int max_duration
- The maximum duration of the loan that the lender is willing to accept, in daysunsigned_int min_interest_rate
- The minimum daily interest rate that the lender is willing to accept, as a scaled percentagetime_point_sec expiration
- Expiration date of the offerImplementation hints:
by_owner
, by_asset
, by_expiration
borrowing_offer_object
(new)Fields:
borrowing_offer_id_type id
- The object IDaccount_id_type owner
- The borrowing account IDasset_id_type loan_asset
- The asset type that the borrower is offering to borrowshare_type min_amount
- The minimum amount of the asset type that the lender must lendshare_type max_amount
- The maximum amount of the asset type that the borrower wants to borrowshare_type available_collateral
- The amount of collateral the borrower has put into the offerunsigned_int mcr
- The maximum collateral ratio that the borrower is willing to provide at the beginning of the loan, as a scaled percentageunsigned_int mccr
- The maximum collateral ratio the borrower will accept, below which a margin call of the loan is initiated, as a scaled percentageunsigned_int min_call_duration
- The minimum duration of a margin call in seconds, if one is necessary, after which a portfolio confiscation will be triggeredasset_id_type tradable_asset
- The asset type that the borrower wants to trade againstunsigned_int min_duration
- The minimum duration of the loan that the borrower is willing to accept, in daysunsigned_int max_duration
- The maximum duration of the loan that the borrower is willing to accept, in daysunsigned_int max_interest_rate
- The maximum daily interest rate that the borrower is willing to accept, as a scaled percentagetime_point_sec expiration
- Expiration date of the offerextension_type ext
- reserved for future extensionsImplementation hints:
by_owner
, by_asset
, by_expiration
loan_portfolio_object
(new)Fields:
account_id_type owner
- The borrowing account IDaccount_id_type lender
- The lending account IDasset_id_type principal_asset
- The ID of the borrowed assetshare_type principal_borrowed
- The amount that was originally borrowedshare_type minimum_collateral
- The minimum amount of collateral that must be maintainedshare_type principal_balance
- The amount of the borrowed asset currently held in the portfolioshare_type principal_in_orders
- The amount of the borrowed asset currently held in market ordersasset_id_type trade_asset
- The ID of the asset that can be traded againstshare_type trade_balance
- The amount of the tradable asset currently held in the portfolioshare_type trade_in_orders
- The amount of the tradable asset currently held in market ordersshare_type mccr
- The portfolio value below which a margin call of the loan is initiated, in terms of principal_asset
unsigned_int call_duration
- The duration of a margin call in seconds, if one is necessary, after which a portfolio confiscation will be triggeredoptional<time_point_sec> confiscation_time
- After a margin call has been initiated, this contains the time when the portfolio will be confiscatedshare_type daily_interest
- The daily interest amount to be paidtime_point_sec interest_due_at
- Date at which the next interest payment is dueshare_type cumulative_interest
- The cumulative interest paid for this loan so fartime_point_sec earliest_end
- Date after which the portfolio can be closed by the borrowertime_point_sec latest_end
- Date after which the portfolio will be closed automaticallyoptional<price> call_price
- If present, contains the price (in terms of principal/trade) below which the portfolio is margin calledImplementation hints:
by_owner
, by_lender
, by_interest_due
, by_expiration
(i. e. latest_end
)The chain_parameters
(configurable by committee) will receive a new extension field margin_lending
with these members:
unsigned_int max_duration
- maximum allowed loan duration in daysunsigned_int minimum_mcr
- minimum allowed mcr for loans, as a scaled percentageunsigned_int minimum_mccr
- minimum allowed mccr for loans, as a scaled percentageunsigned_int max_interest
- maximum allowed daily interest rate, as a scaled percentageunsigned_int max_call_duration
- maximum allowed call duration in secondsThis extension must not be present in proposals before the hardfork time.
limit_order_object
receives a new field optional<loan_portfolio_id_type> loan
Implementation hints:
limit_order_object
for tracking by_loan
All new operations have a simple flat fee. New operations must not be allowed before the hardfork time, neither in proposals nor directly. New fees must not be allowed in chain parameter update proposals before the hardfork.
lending_offer_create_operation
(new)Fields:
account_id_type lender
- The lending account IDasset_id_type asset_to_lend
- The asset type that the lender is offering to lendshare_type min_to_lend
- The minimum amount of the asset type that the borrower must borrowshare_type max_to_lend
- The maximum amount of the asset type that the lender is offeringunsigned_int mcr
- The minimum collateral ratio that the lender is expecting at the beginning of a loan, as a scaled percentageunsigned_int mccr
- The collateral ratio below which a margin call of the loan is initiated, as a scaled percentageunsigned_int max_call_duration
- The maximum duration of a margin call in seconds, if one is necessary, after which a portfolio confiscation will be triggeredasset_id_type tradable_asset
- The asset type that the lender permits the borrower to trade againstunsigned_int min_duration
- The minimum duration of the loan that the lender is willing to accept, in daysunsigned_int max_duration
- The maximum duration of the loan that the lender is willing to accept, in daysunsigned_int min_interest_rate
- The minimum daily interest rate that the lender is willing to accept, as a scaled percentagetime_point_sec expiration
- Expiration date of the offerextension_type ext
- reserved for future extensionsValidation checks:
lender
must be a valid account ID, must exist, must authorize the operation, must pay feeasset_to_lend
and tradable_asset
must be valid asset IDs, must not be equal, and both assets must existmin_to_lend > 0
max_to_lend >= min_to_lend
mcr >= mccr
max_duration >= min_duration
expiration > head_block_time
min_duration <= chain_parameters.max_duration
mcr >= chain_parameters.min_mcr
mccr >= chain_parameters.min_mccr
min_interest_rate <= chain_parameters.max_interest_rate
max_call_duration <= chain_parameters.max_call_duration
lender
must have at least max_to_lend
of asset_to_lend
in his balanceEvaluation:
max_to_lend
of asset_to_lend
from lender
balancelending_offer_object
and populate object fields from operation fieldsborrowing_offer_create_operation
(new)Fields:
account_id_type borrower
- The borrowing account IDasset_id_type asset_to_borrow
- The asset type that the borrower is offering to borrowshare_type min_to_borrow
- The minimum amount of the asset type that the lender must lendshare_type max_to_borrow
- The maximum amount of the asset type that the borrower wants to borrowunsigned_int mcr
- The maximum collateral ratio that the borrower is willing to provide at the beginning of the loan, as a scaled percentageunsigned_int mccr
- The maximum collateral ratio the borrower will accept, below which a margin call of the loan is initiated, as a scaled percentageunsigned_int min_call_duration
- The minimum duration of a margin call in seconds, if one is necessary, after which a portfolio confiscation will be triggeredasset_id_type tradable_asset
- The asset type that the borrower wants to trade againstunsigned_int min_duration
- The minimum duration of the loan that the borrower is willing to accept, in daysunsigned_int max_duration
- The maximum duration of the loan that the borrower is willing to accept, in daysunsigned_int max_interest_rate
- The maximum daily interest rate that the borrower is willing to accept, as a scaled percentagetime_point_sec expiration
- Expiration date of the offerextension_type ext
- reserved for future extensionsValidation checks:
borrower
must be a valid account ID, must exist, must authorize the operation, must pay feeasset_to_borrow
and tradable_asset
must be valid asset IDs, must not be equal, and both assets must existmin_to_borrow > 0
max_to_borrow >= min_to_borrow
mcr >= mccr
max_duration >= min_duration
expiration > head_block_time
min_duration <= chain_parameters.max_duration
mcr >= chain_parameters.min_mcr
mccr >= chain_parameters.min_mccr
min_interest_rate <= chain_parameters.max_interest_rate
min_call_duration <= chain_parameters.max_call_duration
borrower
must have at least max_to_borrow * mcr
of asset_to_borrow
in his balanceEvaluation:
max_to_borrow * mcr
of asset_to_borrow
from borrower
balanceborrowing_offer_object
and populate object fields from operation fieldslending_cancel_operation
(new)Fields:
account_id_type owner
- Creator of the operation (fee paying account), must equal owner of the offeroffer_id_type offer
- Either a lending_offer_id_type
or a borrowing_offer_id_type
extension_type ext
- reserved for future extensionsValidation checks:
owner
must be a valid account ID, must exist, must authorize the operation, must pay feeoffer
must be a valid lending offer ID or borrowing offer ID and must existoffer.owner == owner
Evaluation:
offer
is a lending offer:
offer.max_amount
of offer.loan_asset
to owner
balanceoffer
is a borrowing offer:
offer.available_collateral
of offer.loan_asset
to owner
balanceoffer
from databaseowner
lending_accepted_operation
(new, virtual)Fields:
account_id_type offerer
- must equal owner of the offeroffer_id_type offer
- id of the accepted offer, lending_offer_id_type
or a borrowing_offer_id_type
loan_portfolio_id_type loan
- id of the resulting loan portfoliolending_accept_operation
(new)Fields:
account_id_type acceptor
- Creator of the operation (fee paying account), must equal owner of the offeroffer_id_type offer
- Either a lending_offer_id_type
or a borrowing_offer_id_type
asset_id_type loan_asset
- The asset type of the loan amountshare_type loan_amount
- The loan amount requested / offeredshare_type collateral_amount
- The collateral amount requested / offeredunsigned_int duration
- The duration after which the loan will be closed automatically, in daysextension_type ext
- reserved for future extensionsValidation checks:
acceptor
must be a valid account ID, must exist, must authorize the operation, must pay feeoffer
must be a valid lending offer ID or borrowing offer ID and must existoffer.owner != acceptor
offer.loan_asset == loan_asset
offer.min_duration <= duration <= offer.max_duration
offer.min_amount <= loan_amount <= offer.max_amount
duration <= chain_parameters.max_duration
offer
is a lending offer:
offer.mcr <= collateral_amount / loan_amount
collateral_amount
of loan_asset
in his balanceoffer
is a borrowing offer:
offer.mcr >= mcr
loan_amount
of loan_asset
in his balanceEvaluation:
loan_portfolio_object
and populate fields from operation and offer
offer
is a lending offer:
collateral_amount
of loan_asset
from acceptor
's balanceloan_amount
from offer.max_amount
offer.max_amount < offer.min_amount
: create and execute virtual cancel operation for offer
offer
is a borrowing offer:
loan_amount
of loan_asset
from acceptor
's balancecollateral_amount
from offer.available_collateral
offer.available_collateral / offer.mcr < offer.min_amount
: create and execute virtual cancel operation for offer
loan_portfolio_object
:
principal_borrowed = loan_amount
minimum_collateral = collateral_amount
principal_balance = loan_amount + collateral_amount
daily_interest = loan_amount * offer.interest_rate
interest_due_at = head_block_time + 86400
mccr = loan_amount * (1 + offer.mccr)
lending_accept_operation
to notify owner of offer
loan_interest_operation
(new, virtual)Fields:
account_id_type lender
- the lender's account idaccount_id_type borrower
- the borrower's account idloan_id_type loan
- ID of the loan portfolio to adjustasset interest_amount
- Amount of interest paid to loan.lender
loan_closed_operation
(new, virtual)Fields:
account_id_type lender
- the lender's account idaccount_id_type borrower
- the borrower's account idloan_id_type loan
- ID of the loan portfolio to adjustasset principal_paid_back
- Amount of principal paid back to lenderasset trade_confiscated
- Amount of trade asset paid to lenderasset principal_turned_out
- Amount of principal paid out to borrowerasset trade_turned_out
- Amount of trade asset paid out to borrowerloan_close_operation
(new)Fields:
account_id_type borrower
- the borrower's account idloan_id_type loan
- ID of the loan portfolio to adjustValidation checks:
borrower
must be a valid account ID, must exist, must authorize the operation, must pay feeloan
must be a valid loan portfolio ID and must existloan.owner == borrower
head_block_time >= loan.earliest_end
loan.principal_in_orders == 0 && loan.trade_in_orders == 0
loan.principal_balance >= loan.principal_borrowed + loan.daily_interest
Evaluation:
loan.principal_borrowed
of loan.principal_asset
to loan.lender
loan.principal_balance - loan.principal_borrowed
of loan.principal_asset
to loan.borrower
loan.trade_balance
of loan.trade_asset
to loan.borrower
loan_closed_operation
loan
loan_update_operation
(new)Fields:
account_id_type owner
- Creator of the operation (fee paying account), must equal owner of the loan portfolioloan_id_type loan
- ID of the loan portfolio to adjustasset principal_delta
- Amount of principal asset to add / withdrawasset trade_delta
- Amount of trade asset to add / withdrawextension_type ext
- reserved for future extensionsValidation checks:
owner
must be a valid account ID, must exist, must authorize the operation, must pay feeloan
must be a valid loan portfolio ID and must existloan.owner == owner
principal_delta != 0 || trade_delta != 0
principal_delta >= 0
!confiscation_time.valid || trade_delta >= 0
principal_delta > 0
or trade_delta > 0
, owner
must have sufficient balancetrade_delta < 0
loan.trade_balance >= -trade_delta
mcv = loan.principal_borrowed + loan.minimum_collateral
loan.principal_balance + loan.principal_in_orders < mcv
min_trade = reference_price * (mcr - loan.principal_balance - loan.principal_in_orders)
loan.trade_balance + loan.trade_in_orders + trade_delta >= min_trade
Evaluation:
principal_delta > 0
:
principal_delta
from loan.owner
's balanceprincipal_delta.amount
to loan.principal_balance
trade_delta != 0
:
trade_delta
from loan.owner
's balancetrade_delta.amount
to loan.trade_balance
Note: trading from a loan portfolio happens on the same markets as trading from an account. Trading is therefore not implemented separately, but through modifications to the existing trade mechanisms.
Fields:
The existing limit_order_create_operation
and fill_order_operation
receive one optional extension field:
loan_id_type loan
- ID of the loan portfolio from which the trade is executedThe loan
field is not allowed before the hardfork time, neither directly nor in proposals.
Validation checks:
If the loan
extension is present in a limit_order_create_operation
, the following checks replace the existing checks against the seller's account balance:
loan
is valid and refers to an existing loan_portfolio_object
seller == loan.owner
!loan.confiscation_time.valid
(no trades after margin call)amount_to_sell.asset_id == loan.principal_asset || amount_to_sell.asset_id == loan.trade_asset
amount_to_sell.asset_id == loan.principal_asset
:
loan.principal_balance - amount_to_sell.amount >= loan.minimum_collateral
min_to_receive.asset_id == loan.trade_asset
amount_to_sell.asset_id == loan.trade_asset
:
loan.trade_balance >= amount_to_sell.amount
min_to_receive.asset_id == loan.principal_asset
Evaluation:
loan
extension will be recorded in the new limit_order_object
loan
field is present,
amount_to_sell
will be deducted from the loan
balance and recorded in loan
's ..._in_order
fields, not the account'sfill_order
will be modified to pay trade proceeds into loan
portfolio and adjust loan
's ..._in_order
fieldsfill_order
must re-appraise the portfoliocancel_order
will be modified to return funds into loan
portfolio and adjust loan
's ..._in_order
fieldsThe following methods will be added to the database_api
:
vector<lending_offer_object> get_lending_offers_by_asset <loan-asset> <trade-asset> <optional limit> <optional start>
vector<borrowing_offer_object> get_borrowing_offers_by_asset <loan-asset> <trade-asset> <optional limit> <optional start>
vector<lending_offer_object> get_lending_offers_by_account <account> <optional limit> <optional start>
vector<borrowing_offer_object> get_borrowing_offers_by_account <account> <optional limit> <optional start>
vector<loan_portfolio_object> get_loans_by_lender <account> <optional limit> <optional start>
vector<loan_portfolio_object> get_loans_by_borrower <account> <optional limit> <optional start>
vector<limit_order_object> get_orders_by_loan <loan-id> <optional limit> <optional start>
All result lists are ordered by ascending object id. Server-side limits are configurable.
loan.confiscation_time = head_block_time + loan.call_duration
loan.principal_balance >= loan.principal_borrowed + loan.daily_interest
: close loan as described abovegap = loan.principal_borrowed + loan.daily_interest - loan.principal_balance
limit_order_create
for loan
with amount_to_sell = loan.trade_balance
and min_to_receive = gap
gap
is smaller or perhaps closed)Notes:
gap
, possibly at a price far away from the usual market price. Thus, the borrower should
avoid being margin called.gap
. It may then be impossible to create a new order for the remaining
gap, because that would be considered "dust". The consequence would be that the loan stays in margin call state
until it is confiscated. For practical purposes this shouldn't make much of a difference because rounding issues
are a few "satoshis" only.Similar to database::clear_expired_proposals
, in each block
loan_portfolio_object.interest_due_at
against head_block_time
!loan_portfolio_object.confiscation_time.valid
,
loan.daily_interest > loan.principal_balance
: initiate margin_callloan.daily_interest
from loan.principal_balance
loan.daily_interest
of loan.principal_asset
to loan.lender
's balanceloan.daily_interest
to loan.cumulative_interest
loan_interest_operation
loan.interest_due_at
Similar to database::clear_expired_orders
, in each block
lending_offer_object.expiration
and borrowing_offer_object.expiration
against head_block_time
lending_cancel_operation
and execute as describe aboveSimilar to database::clear_expired_orders
, in each block
loan_portfolio_object.latest_end
against head_block_time
limit_order_cancel
operationsloan.principal_balance < loan.principal_borrowed + loan.daily_interest
: initiate margin callIn each block, for each loan that is in margin call state,
loan.principal_balance >= loan.principal_borrowed + loan.daily_interest
Similar to database::clear_expired_orders
, in each block
loan_portfolio_object.confiscation_time
against head_block_time
loan.principal_balance
of loan.principal_asset
to loan.lender
's balanceloan.trade_balance
of loan.trade_asset
to loan.lender
's balanceloan_closed_operation
loan
vote_tally_helper
computes voting_stake
per account as before, plus core in
principal = loan.principal_balance + loan.principal_in_orders
principal >= loan.mccr
, clear loan.call_price
loan.call_price = (loan.mccr - principal) / (loan.trade_balance + loan.trade_in_orders)
reference_price < loan.call_price
: trigger margin callcli_wallet
The following commands will be added to cli_wallet
:
list_lending_offers <account>
list_borrowing_offers <account>
get_lending_offers <loan-asset> <trade-asset>
get_borrowing_offers <loan-asset> <trade-asset>
lending_offer_create
with operation parametersborrowing_offer_create
with operation parameterslending_offer_cancel <id>
lending_offer_accept <id> <amount> <duration>
loan_update <id> <delta-principal> <delta-trade>
loan_close <id>
sell_asset
command will receive an additional optional parameter, the loan portfolio idPlease consider rewording certain uses of "price". A price is a ratio of two denominations. E. g. "Maintenance collateral price" is not a price but rather a valuation expressed as an amount of one asset.
Special cases for reference price:
- If the tradable asset is a bitasset in global settlement, use the settlement price as the reference price
- If the tradable asset is an MPA and has a valid feed price, use the feed price (minus settlement offset) as the reference price)
The liquidation plan should include settlement if the tradable asset is in global settlement. If the tradable asset is an MPA and has a valid feed price at the time of confiscation, should the lender receive only enough of it (in terms of feed price and settlement offset) to cover the missing debt?
Regarding your last point on confiscation, yes in the case of a margin call of the borrower:
1: is an order with amount to fill is placed on the DEX at the margin price, in the case where that doesnt fill every order in the entire orderbook and does meet the amount required to payback the loan then everything is fine.
In the case it take every order in the orderbook and still has remaining amount to be filled, then an order is place in the orderbook at that price. This order has an expiration (adjustable via committee IMO).
After expiration period, the outstanding tokens should be confiscated from the borrower and returned to the lender. This is an acceptable risk for the lender as it is known this can happen at creation. I would say the lender only receive enough of it to fulfil the order.
Regarding what the 'Price' is yes this is something to consider. In the case of an MPA, the collateral is often BTS, however if lending is taking place involving a UIA or a smartcoin that doesnt have BTS as collateral then using the pricefeed as a reference is not possible. In the case of Bitfinex and others, the price comes from the last price on the exchange. I think the only issue that some may have with this is in illiquid markets it can open things up for exploitation and negative feedback loops fairly easily. Therefore a dampening affect should be in force in cases where there is a drastic drop in prices, perhaps a an average of last price over a period of X blocks would provide a safer mechanism?
Abstract
This BSIP defines a protocol upgrade in order to support peer-to-peer lending, borrowing and margin trading markets on the BitShares DEX. Lending is defined as any user of the BitShares DEX having the ability to post an offer to lend any BitShares asset they own to a market where a borrower may take that offer (by posting collateral) and pay the lender a lender-defined amount of interest over a time period.
The Borrower may choose to take the offer or post their preferred borrowing interest rate as a Bid and when taken, execute an exchange transaction with that token for another specified by the lender. The borrower will pay the lender interest in the asset type that was borrowed. Should the value of their margin position fall by a specified amount, the borrowers' balance will be margin called and sold on the market to payback the debt to the lender. The borrower risks losing their collateral in the case of a margin call and the lender risks the orderbook depth being insufficient to pay back their loan in the specified market.
Motivation
BitShares is the longest running decentralised cryptocurrency exchange and one of the pioneers of collateralised stablecoins. While the BitShares DEX makes it easy to trade in an environment where users have custody of their own keys, there are opportunities to be made to improve liquidity, onboard new users and affect great trading activity on the BitShares DEX.
The highest volume and most liquid exchanges in the world to date like Bitmex and Bitfinex who rose to dominance due to their usage of leverage in catalysing greater liquidity for their customers.
With this in mind, some of the key inhibitors to growth right now for the BitShares DEX include:
Incentive for Smartcoin creation / holding: The growth in liquidity of Smartcoins like bitUSD, BitCNY, BitEUR and others depends on users locking up BTS collateral to create these assets. For users engaged in creating these assets they must often manage exposure to a highly volatile collateral asset and are not paid for taking on the risk which could reduce potential new issuance.
Smartcoin Liquidity: The most liquid BitShares markets are often the smart coin markets, however the liquidity of Smartcoins in circulation on the orderbook is not yet comparable to larger teir centralised exchanges thereby reducing potential usage of the BitShares DEX.
Counterparty risk of crypto lending: Currently one of the only ways with market traction to earn passive income on cryptocurrency holdings is to trust a centralised counterparty and give up ownership of your money to another entity. This is highly risky with users no longer in control of their funds and at risk of hacking or confiscation.
BTS Price growth: The Bitshares token (BTS) is the underlying collateral required for committee issued assets and therefore a higher Bitshares price incentivises greater Smartcoin creation. Growing demand for BitShares assets promotes higher collateralisation of BTS which requires more BTS being removed from circulation which over time reduces supply and can increase positive price pressure.
The motivation behind this BSIP is to address these concerns and increase user demand, liquidity and passive income opportunities for users of the BitShares DEX.
Rationale
This BSIP seeks to address the inhibitors to growth in the BitShares DEX by introducing P2P Lending, Borrowing and Margin trading markets on the BitShares DEX. This new functionality would address the above concerns as follows:
Passive risk adjusted income: Any user may choose to lend any BitShares asset for a user defined rate of return over a specified time period. This not only provides an added incentive to hold an asset that can return a yield but also ensures existing liquidity of BitShares assets is deployed to the trading orderbook.
On-chain lending and borrowing reduces risk: Users seeking a return would not need to trust third party intermediaries with their funds and can engage in lending and borrowing contracts on the BitShares DEX. This reduces risk compared to competing centralised non-custodial competitors.
Increased DEX liquidity: With the ability for users to lend new or existing liquidity directly to the orderbooks, it provides greater order book depth than exists currently. This reduces risk for margin traders who rely on ample orderbook depth to ensure their positions can be adequately executed at a desired price or in the case of margin calls greater depth reduces collateral losses.
Long / Short any asset on the DEX: A user could borrow or lend any asset on the DEX adding new opportunities to make money from market movements especially in bear markets. This also enables smartcoin issuers to hedge their BTS (or other) exposure which could assist these users maintain adequate MCR ratios thereby reducing global settlement risk.
Added volume and usage of BTS: Every operation on the BitShares DEX requires a fee to be paid which returns BTS to the reserve pool. Greater usage of the BitShares DEX increases fees paid, reduces supply which can result in a positive price pressure on BTS. Additionally new smartcoin issuance for committee assets and some private assets requires BTS as collateral and therefore increased issuance also requires the purchase and lock up of BTS, increasing demand of BTS.
The BitShares DAC is well situated to capture a market opportunity in this space with the core intent of this BSIP to increase the viability of the BitShares DEX as a high volume, non-custodial, transparent and liquid trading exchange.
Specifications
The process flow for margin trading is depicted below. The process consists of seven stages with some stages containing parallel processes.
Stage 1a: Authorized Leveraged Trading Pairs
The asset issuer of the loan asset must authorize the loan asset to be used for lending for margin trading ("leveraged trading") against a set of tradable assets. This set of authorized tradable asset may be updated by the asset issuer at any time. These restrictions shall affect the creation of new loan and borrow offers.
Stage 1b: Reference Price
Knowledge of the exchange rate between the loan asset and the tradable asset is essential for the smart contract to automatically appraise a portfolio during the loan appraissal and to evaluate the need for a possible margin call. This price shall be determined by the smart contract from data on the decentralized exchange and not from any external price feeds. The reference price shall be validated under specific rules, and prohibitions shall be imposed while the reference price is invalid.
Determination of Reference Price
The reference price for the tradable asset that is denominated in terms of the loan asset shall be updated every block that has any activity (new orders, canceled orders, and matched orders) in that market pair's trading book. The reference price of the tradable asset shall be calculated according to the following rules.
If the validity conditions are not satisfied for the asset pair, the reference price shall be considered invalid and certain activities shall be prohibited.
Prohibited Activity under Invalid Reference Price
A valid reference price permits the tradable asset components of the portfolio (Tliquid and Torders) to be appraised in terms of the loan asset. This allows the entire loan portfolio to be appraised which further allows a check of the minimum collateral requirements for an existing loan.
Therefore with a valid reference price
However an invalid reference price prevents a portfolio appraisal (except for the trivial case where the portfolio only consists of the borrowed asset components (Bliquid and Borders). Without the ability to appraise the tradable asset portion of the portfolio, collateral requirements cannot be evaluated. Therefore,
Stage 2: Offers to Lend and Borrow
Both potential lenders and potential borrowers can place offers on the Loan Order Book. Potential lenders place "loan offers" and potential borrowers place "borrow offers". Loan offers contain the following parameters:
Borrow offers contain the following parameters:
After an offer is created, all users shall be able to identify:
Users shall have the ability to filter offers either by type (loan offer or borrow offer), asset type to loan, tradable asset type, amounts, interest rate, loan duration, maintenance collateral ratio, and margin call collateral ratio. This capability shall either be done at the Core RPC-API node and/or at the user interface. Offers to lend and offers to borrow shall have unique identifiers which can be referenced for loan matching.
The creation of offers, their partial and complete matches, their expiration, and their closures, shall be recorded as part of the account history of the lender and the borrower.
Offers to lend and borrow shall remain on the Loan Order Book until they either are canceled by the offeror, expire, or are completely matched and filled.
Stage 3: Loan Offer Matching
New offers shall be automatically compared to existing counter-offers on the book. This matchmaking investigation shall:
Compatibility Filtering
This matchmaking process shall only match a loan offer (L) with a borrow offer (B) if those offers have the following compatible conditions.
Therefore when a new loan offer or borrow offer is received, it shall be checked against the existing offers. This new offer will become the "taker" to the existing "maker" offers. The outcome of this investigation may identify multiple "maker" offers to be compatible with the new "taker" offer.
If no compatible offers are found for the new offer, the new offer shall be added to the offer order book and retained until it is canceled, expires, or is completely matched and filled.
Offer Matching
When multiple loan offers (L) are found to be compatible with multiple borrow offers (B), they shall be prioritized in a deterministic manner to identify which of the compatible offers will be matched to each other.
As the definition of most offer parameters are not exact values (e.g. a lender might offer a loan for exactly 6 months) but are rather bounded values (e.g. a lender might offer a loan for a duration between 3 months and 12 months), and the compatibility conditions permit a range of overlap between a loan offer and a borrow offer, there may mathematically be an infinite number of loan definitions that could be created from even a single loan offer and borrow offer. (Technically the number of loan offers are finite because they will only be characterized by finite-precision integer parameters.) Matches shall be made to favor the existing offers on the loan offer books (the "makers").
If the new offer (the "taker") is a borrow offer, the compatible loan offers shall be sorted in favor of the lenders (the "makers"). These compatible offers shall be sorted in favor of the lender offers as described in the following table.
If the new offer (the "taker") is a loan offer, the compatible offers shall be sorted in favor of the borrowers (the "makers"). These compatible offers shall be prioritized favor of the borrower offers as described in the following table.
The highest prioritized maker offer shall be paired to the new offer and a new loan shall be created in accordance with the loan parameter values in the corresponding table.
Loan Creation
The matching of a loan offer with a borrow offer shall result in the creation of a loan.
This new loan portfolio shall receive the loan amount (P) from the lending offer and an amount of collateral asset (K) from the borrowing offer equal to
K = (MCR - 1) × P
A loan shall be created from a single lending offer and a single borrowing offer.
This loan portfolio shall then become available for margin trading by the borrower.
Effective Dates of the Loan
The start date of the loan shall be when the loan is matched. The end date of the loan shall be calculated by adding the loan duration to the start date. The loan may be closed:
Filling of Loan Offer
The matching of a loan offer with a borrow offer will result in one or both of the offers being completely consumed. If an offer is not completely filled, the offer shall be "partially filled" by having the loan amount (P) deducted from the offer's "available balance".
Effects of Partial Fills on a Loan Offer
The reduction to a loan offer reduces the amount that has been offered by the prospective lender.
(BPmax)new = (BPmax)old - P
If this remainder exceeds the loan offer's minimum amount (BPmin), the loan offer shall be retained on the offer books. Otherwise the offer shall be cancelled by the smart contract.
Effects of Partial Fills on a Borrow Offer
The reduction to a borrow offer reduces the amount of collateral (K) that is being offered by the prospective borrower.
Knew = Kold - P
This effectively reduces the maximum loan amount of the borrow offer.
(LPmax)new = Knew ÷ (MCR - 1) = (Kold - P) ÷ (MCR - 1)
If this remainder exceeds the borrow offer's minimum amount (LPmin), the loan offer shall be retained on the offer books. Otherwise the offer shall be cancelled by the smart contract.
Re-evaluation of a New Offer
If the partially-filled offer is retained and if the partially filled offer is the new offer, it shall be re-evaluated for loan matching against the remaining counter-offers.
Stage 4a: Margin Trading within Loan Portfolio
Assets that are borrowed shall be placed into the borrower's margin trading "loan portfolio". This portfolio shall only be used for trading on the decentralized exchange in the market pair consisting of the "Asset type to lend/borrow" and the "Asset type to trade against". It shall not be possible to transfer funds to any account, nor use any of the assets as collateral to create another pegged asset on BitShares.
Any assets obtained from trading shall by placed into the loan portfolio and shall also be restricted to trading between the pair of asset types defined in the loan agreement. Conditional withdrawals of the tradable asset by the borrower shall be permitted. Deposit of the lent asset by the borrower shall also be permitted.
Trading Limits
A borrower shall be able to use the borrowed asset type in the loan portfolio to trade against the tradable asset on the order book of the market pair. The amount of the borrowed asset type (B) that may be used for placing new orders shall be limited to ensure that the loan portfolio's balance of the borrowed asset exceeds the minimum collateral (K). Before a trade the liquid balance of the asset type is Bliquidbefore. The liquid balance of the asset type after a new order (Btradenew) can be calculated as
Bliquidafter = Bliquidbefore - Btradenew
The new liquid balance must satisfy the following condition and definition for collateral
Bliquidafter ≥ K = (MCR - 1) × B0
which can be re-arranged as
Btradenew ≤ Bliquidbefore - (MCR - 1) × B0
This expresses a maximum amount for any new limit orders where the borrowed asset is offered to trade. If this amount is negative, no new trades shall be permitted.
Multiple Loan Portfolios
A borrower may have multiple outstanding loans each with their own distinct loan portfolio. Trading of assets from each loan portfolio shall be independent of other loan portfolios that are controlled by the borrower. Trade orders shall only draw from assets within a single loan portfolio.
The distinction of loan portfolios from each other are intended to segregate the risk of each loan which can have separate loan durations, margin collateral ratios, and tradable assets. This segregation should better secure the lenders than a single co-mingled loan portfolio.
User interfaces that facilitate trading for a borrower may optionally aggregate multiple loan portfolios into a single "margin trading wallet" to disguise the fact that multiple loan portfolios are being tracked.
Stage 4b: Daily Interest Payment
The daily interest due (Idaily) on the prinicipal (B0) shall be calculated as
Idaily = B0 × Rdaily
where Rdaily is daily interest rate. This daily interest shall be calculated in terms of the lent asset type.
The daily interest that is due shall be deducted from the borrower's balance of the borrowed asset type in the loan portfolio and deposited into the lender's account. If the borrower's loan portfolio holds insufficient balance of the lent asset type to pay the daily interest then a margin call shall be initiated.
When a loan is closed the interest for that last day shall be paid at that time. If a margin call requires multiple days to complete in accordance with the agreed duration of the margin call's loan, no additional interest shall be owed by the lender beyond payment for the last day of interest.
Stage 4c: Appraisal of Loan Portfolio
Debt Owed
The debt owed by a borrower for a particular loan is the amount lent by the lender. Interest is due on a daily basis.
Portfolio Appraisal
A borrower may have many outstanding loans which are owed to different borrowers. Each loan portfolio will initially consist of the principal that is lent by the lender plus the initial collateral that is provided by the borrower. The borrowed asset and the collateral asset shall initially be the same asset type (B).
After the loan is initiated, the borrower may use that asset type to trade against the tradable asset type (T) that is permitted by the loan, and/or may hold the borrowed asset. Therefore this loan-related portfolio may consist of balances of two asset types: the borrowed asset type, and the tradable asset type.
PA = B + T
Portfolio Components
While a loan is outstanding the balance of the borrowed asset and tradable asset may consist as either liquid balances in the loan portfolio or as open orders on the order book. Therefore the entire loan portfolio may be decomposed into four parts:
PA = Bliquid + Tliquid + Borders + Tliquid
The valuation of the portfolio shall also be denominated in terms of the borrowed asset type for purposes of appraisal by the smart contract. The valuation of the borrower's loan-related portfolio shall consist of the valuation of the two assets in the portfolio at the time of interest.
Bob borrowed 70 bitUSD 203.3 days ago while supplying by supplying 30.03 bitUSD as collateral. Bob has been margin trading with this loan portfolio against bitBTC and currently has a balance of 45 bitUSD and 0.025 bitBTC. The current reference price indicates that bitBTC is priced at 5000 bitUSD per bitBTC. This loan portfolio will be appraised (PA) at:
PA = (45 bitUSD) + (0.025 bitBTC × 5000 bitUSD ÷ bitBTC)
... = (45 bitUSD) + (125 bitUSD)
... = 170 bitUSD
Collateral Ratio
After the calculation of a portfolio appraisal (PA) and the debt owed (B0), the collateral ratio (CR) shall be calculated as
CR = PA ÷ B0
At the beginning of the loan, the collateral ratio will satisfy the following conditions.
CR ≥ MCR ≥ MCCR ≥ 1
Derived Valuations
The maintenance collateral valuation (MCV) of the loan portfolio is denominated in the borrowed asset and equals
MCV = MCR × B0
where B0 is the debt owed.
Similarly, the margin call collateral valuation (MCCV) of the loan portfolio is denominated in the lent asset and equals
MCCV = MCCR × B0
It is desired for the appraised valuation of the portfolio (PA) to be greater than or equal this value
PA ≥ MCV ≥ MCCV ≥ B0
but it is possible for this valuation to fall below the MCV. If
PA < MCCV
a margin call shall be initiated.
Triggering of Appraisal
Portfolio appraisals shall be triggered at multiple times. A portfolio appraisal shall be triggered:
Stage 4d: Loan Portfolio Updates
Status of Loan Portfolio
The "recent" appraisal value, debt owed, collateral ratio, and derived valuations, and of the portfolio shall be able to be queried by the lender and borrower at any time.
Deposits
A borrower shall be able to deposit additional amounts of the borrowed asset into the loan portfolio. A borrower may choose to deposit additional collateral to avoid having the loan be margin called.
Withdrawals
A borrower shall be able to withdraw only the tradable asset as long as the market valuation of the portfolio (PA) after the withdrawal is greater than or equal to the maintenance collateral valuation. The withdrawal limit (Wlimit) is defined as
Wlimit = PA - MCV
where MCV is maintenance collateral valuation and PA is portfolio appraisal.
Bob borrowed 70 bitUSD 203 days ago at a daily interest rate of 0.0261% while supplying by supplying 30.03 bitUSD as collateral to satisfy the offer's 142.9% maintainance collateral ratio.
The debt owed is still 70 bitUSD. The maintenance collateral valuation (MCV) of the portfolio is
MCV = MCR × B0
... = 1.429 × 73.8276 bitUSD
... = 105.4996 bitUSD
During this time Bob has been margin trading with this loan portfolio against bitBTC and currently has a balance of 45 bitUSD and 0.025 bitBTC. The current reference price indicate that bitBTC is priced at 5000 bitUSD per bitBTC. This loan portfolio will be appraised at:
PA = (45 bitUSD) + (0.025 bitBTC × 5000 bitUSD ÷ bitBTC)
... = (45 bitUSD) + (125 bitUSD)
... = 170 bitUSD
The borrower may withdraw up to the equivalent (Wlimit) of
Wlimit = PA - MCV
... = 170 bitUSD equivalent - 105.4996 bitUSD equivalent
... = 64.5004 bitUSD equivalent
The withdrawal limit denominated in bitBTC is
Wlimit = (64.5004 bitUSD ÷ (5000 bitUSD ÷ bitBTC))
... = 0.01291 bitBTC
Bob may withdraw bitBTC up to this limit because the balance of bitBTC, 0.025, exceeds this amount. If the balance of the tradable asset were, for example, only 0.1 bitBTC then Bob would only be able to withdraw 0.1 bitBTC.
Stage 5a: Initiation of Loan Closure by Borrower
A borrower may close an outstanding loan position by having a sufficient balance of the borrowed asset type in the loan portfolio and then initiating a loan closure with the appropriate parameters.
The initiation of a loan closure shall close any and all open trade orders that are related to this loan. If the balance of the borrowed asset type is insufficient to repay what is owed then the initiation of the loan closure shall be rejected. It is the responsibility of the borrower to ensure a sufficient balance in the borrowed asset type to repay the loan.
Stage 5b: Expiration of Loan
The smart contract shall initiate a margin call if an outstanding loan expires.
A future BSIP may consider opening a new loan from any existing offers on the Loan Order Book.
Stage 5c: Initiation of Loan Closure because of Insufficient Funds
A loan portfolio may categorized as consisting of four components of balances of which one is the balance of borrowed asset that is liquid (Bliquid). This balance is drawn from to pay the daily interest. If this balance is insufficient to pay the interest then a loan closure shall be initiated.
Stage 5d: Initiation of Loan Closure by Margin Call
If the collateral ratio ever drops below the margin call collateral ratio,
CR < MCCR
the smart contract shall initiate a margin call.
Stage 6: Margin Call
Restriction of Loan Portfolio
When a margin call is initiated on a specific loan portfolio, no new market orders may be initiated that make use of any balance in the loan portfolio. Any other loan portfolios that the borrower might have shall not be affected by margin calls on other loans.
Any open market orders that are related to that specific loan portfolio shall be cancelled.
After all open orders are cancelled, the portfolio will consist of some amount in the borrowed asset type and some amount in the tradable asset type.
PA = Bliquid + Tliquid
Liquidation Plan
The smart contract shall determine whether the balance of the borrowed asset (Bliquid) is sufficient to pay the necessary balance (Bclosure). The difference between the two is the excess borrowed asset (Bexcess)
Bexcess = Bliquid - Bclosure
If the balance is sufficient (Bexcess > 0), the process shall transition to a conventional loan closure.
If the balance is insufficient (Bexcess < 0), the smart contract shall create a limit order that offers the entire balance of the tradable asset (T) while asking for the difference between what is owed and the liquid balance(-Bexcess). This limit order shall have a limited lifetime defined by the maximum margin call duration that was agreed to in the original loan terms.
If the margin call's limit order is filled, then by definition of the limit order there shall be sufficient balance of the borrowed asset type to transition to a conventional loan closure.
Portfolio Confiscation
If the margin call's limit order expires without being completely filled, a portfolio confiscation shall be automatically initiated to permit the prompt completion of the margin call. The smart contract shall confiscate the entire loan portfolio from the borrower for ultimate transfer to the lender.
Monitoring of Liquidation Plan
It shall be possible to monitor the status of the liquidation plan associated with any margin call. An inquiry into the status of the liquidation plan shall return:
Stage 7a: Conventional Loan Closure
A standard loan closure is possible if and only if the loan portfolio's balance of the borrowed asset type (Bliquid) is sufficient to repay the principal plus interest for the last day of the loan.
Bclosure = B0 + Idaily
If that condition is satisfied, a standard loan closure can be:
Any balances that remain in the loan portfolio after repaying the lender shall be transferred to the borrower's regular set of balances and shall no longer be encumbered by any restrictions.
A future BSIP may consider re-lending a lenders balance by automatically creating a new offer on the Loan Order Book on behalf of the lender.
The loan shall be closed.
Stage 7b: Unconventional Loan Closure
If a margin call's liquidation plan expires without obtaining a sufficient balance of the borrowed asset to repay the lender, the confiscated loan portfolio shall be transferred to the lender as a substitute payment for the debt.
The loan shall be closed.
Definable Loan Constraints
The BitShares Committee shall be able to define parameters that can constrain new loans; changes to these values shall not affect loans that were offered before the change:
Fees
Fees shall be defined for each of the operations:
The standard fee for canceling a trade order shall apply.
Voting Stake
Voting stake shall be calculated per account as before this proposal and with the following additions to account for any core tokens (BTS) that are associated with lending.
Software Specifications
Note 1: Interest is paid every 24 hours, regardless of local calendar. E. g. Daylight Savings Time is ignored.
Note 2: Percentage-based calculations (interest, CR) are always rounded up to the next possible value (aka "satoshi").
Note 3: MCR and MCCR are expressed in the same way as in the existing price feed logic, i. e. only the part above 100%, and as a scaled percentage value. E. g. a value of
4200
would mean142%
.Note 4: "Implementation hints" are not to be considered part of the formal specification, but merely as a possible implementation.
Database Objects
lending_offer_object
(new)Fields:
lending_offer_id_type id
- The object IDaccount_id_type owner
- The lending account IDasset_id_type loan_asset
- The asset type that the lender is offering to lendshare_type min_amount
- The minimum amount of the asset type that the borrower must borrowshare_type max_amount
- The maximum amount of the asset type that the lender is offeringunsigned_int mcr
- The minimum collateral ratio that the lender is expecting at the beginning of a loan, as a scaled percentageunsigned_int mccr
- The collateral ratio below which a margin call of the loan is initiated, as a scaled percentageunsigned_int max_call_duration
- The maximum duration of a margin call in seconds, if one is necessary, after which a portfolio confiscation will be triggeredasset_id_type tradable_asset
- The asset type that the lender permits the borrower to trade againstunsigned_int min_duration
- The minimum duration of the loan that the lender is willing to accept, in daysunsigned_int max_duration
- The maximum duration of the loan that the lender is willing to accept, in daysunsigned_int min_interest_rate
- The minimum daily interest rate that the lender is willing to accept, as a scaled percentagetime_point_sec expiration
- Expiration date of the offerextension_type ext
- reserved for future extensionsImplementation hints:
by_owner
,by_asset
,by_expiration
borrowing_offer_object
(new)Fields:
borrowing_offer_id_type id
- The object IDaccount_id_type owner
- The borrowing account IDasset_id_type loan_asset
- The asset type that the borrower is offering to borrowshare_type min_amount
- The minimum amount of the asset type that the lender must lendshare_type max_amount
- The maximum amount of the asset type that the borrower wants to borrowshare_type available_collateral
- The amount of collateral the borrower has put into the offerunsigned_int mcr
- The maximum collateral ratio that the borrower is willing to provide at the beginning of the loan, as a scaled percentageunsigned_int mccr
- The maximum collateral ratio the borrower will accept, below which a margin call of the loan is initiated, as a scaled percentageunsigned_int min_call_duration
- The minimum duration of a margin call in seconds, if one is necessary, after which a portfolio confiscation will be triggeredasset_id_type tradable_asset
- The asset type that the borrower wants to trade againstunsigned_int min_duration
- The minimum duration of the loan that the borrower is willing to accept, in daysunsigned_int max_duration
- The maximum duration of the loan that the borrower is willing to accept, in daysunsigned_int max_interest_rate
- The maximum daily interest rate that the borrower is willing to accept, as a scaled percentagetime_point_sec expiration
- Expiration date of the offerextension_type ext
- reserved for future extensionsImplementation hints:
by_owner
,by_asset
,by_expiration
loan_portfolio_object
(new)Fields:
account_id_type owner
- The borrowing account IDaccount_id_type lender
- The lending account IDasset_id_type principal_asset
- The ID of the borrowed assetshare_type principal_borrowed
- The amount that was originally borrowedshare_type minimum_collateral
- The minimum amount of collateral that must be maintainedshare_type principal_balance
- The amount of the borrowed asset currently held in the portfolioshare_type principal_in_orders
- The amount of the borrowed asset currently held in market ordersasset_id_type trade_asset
- The ID of the asset that can be traded againstshare_type trade_balance
- The amount of the tradable asset currently held in the portfolioshare_type trade_in_orders
- The amount of the tradable asset currently held in market ordersshare_type mccv
- The portfolio value below which a margin call of the loan is initiated, in terms ofprincipal_asset
unsigned_int call_duration
- The duration of a margin call in seconds, if one is necessary, after which a portfolio confiscation will be triggeredoptional<time_point_sec> confiscation_time
- After a margin call has been initiated, this contains the time when the portfolio will be confiscatedshare_type daily_interest
- The daily interest amount to be paidtime_point_sec interest_due_at
- Date at which the next interest payment is dueshare_type cumulative_interest
- The cumulative interest paid for this loan so fartime_point_sec earliest_end
- Date after which the portfolio can be closed by the borrowertime_point_sec latest_end
- Date after which the portfolio will be closed automaticallyoptional<price> call_price
- If present, contains the price (in terms of principal/trade) below which the portfolio is margin calledImplementation hints:
by_owner
,by_lender
,by_interest_due
,by_expiration
(i. e.latest_end
)Chain parameters
The
chain_parameters
(configurable by committee) will receive a new extension fieldmargin_lending
with these members:unsigned_int max_duration
- maximum allowed loan duration in daysunsigned_int minimum_mcr
- minimum allowed mcr for loans, as a scaled percentageunsigned_int minimum_mccr
- minimum allowed mccr for loans, as a scaled percentageunsigned_int max_interest
- maximum allowed daily interest rate, as a scaled percentageunsigned_int max_call_duration
- maximum allowed call duration in secondsThis extension must not be present in proposals before the hardfork time.
Miscellaneous
limit_order_object
receives a new fieldoptional<loan_portfolio_id_type> loan
Implementation hints:
limit_order_object
for trackingby_loan
Operations
All new operations have a simple flat fee. New operations must not be allowed before the hardfork time, neither in proposals nor directly. New fees must not be allowed in chain parameter update proposals before the hardfork.
lending_offer_create_operation
(new)Fields:
account_id_type lender
- The lending account IDasset_id_type asset_to_lend
- The asset type that the lender is offering to lendshare_type min_to_lend
- The minimum amount of the asset type that the borrower must borrowshare_type max_to_lend
- The maximum amount of the asset type that the lender is offeringunsigned_int mcr
- The minimum collateral ratio that the lender is expecting at the beginning of a loan, as a scaled percentageunsigned_int mccr
- The collateral ratio below which a margin call of the loan is initiated, as a scaled percentageunsigned_int max_call_duration
- The maximum duration of a margin call in seconds, if one is necessary, after which a portfolio confiscation will be triggeredasset_id_type tradable_asset
- The asset type that the lender permits the borrower to trade againstunsigned_int min_duration
- The minimum duration of the loan that the lender is willing to accept, in daysunsigned_int max_duration
- The maximum duration of the loan that the lender is willing to accept, in daysunsigned_int min_interest_rate
- The minimum daily interest rate that the lender is willing to accept, as a scaled percentagetime_point_sec expiration
- Expiration date of the offerextension_type ext
- reserved for future extensionsValidation checks:
lender
must be a valid account ID, must exist, must authorize the operation, must pay feeasset_to_lend
andtradable_asset
must be valid asset IDs, must not be equal, and both assets must existmin_to_lend > 0
max_to_lend >= min_to_lend
mcr >= mccr
max_duration >= min_duration
expiration > head_block_time
min_duration <= chain_parameters.max_duration
mcr >= chain_parameters.min_mcr
mccr >= chain_parameters.min_mccr
min_interest_rate <= chain_parameters.max_interest_rate
max_call_duration <= chain_parameters.max_call_duration
lender
must have at leastmax_to_lend
ofasset_to_lend
in his balanceasset_to_lend
must be authorized for margin lending againsttradable_asset
asset_to_lend
and thetradable_asset
must not be transfer restrictedlender
must be whitelisted or must not be blacklisted for theasset_to_lend
and thetradable_asset
due to transfer restrictionsEvaluation:
max_to_lend
ofasset_to_lend
fromlender
balancelending_offer_object
and populate object fields from operation fieldsborrowing_offer_create_operation
(new)Fields:
account_id_type borrower
- The borrowing account IDasset_id_type asset_to_borrow
- The asset type that the borrower is offering to borrowshare_type min_to_borrow
- The minimum amount of the asset type that the lender must lendshare_type max_to_borrow
- The maximum amount of the asset type that the borrower wants to borrowunsigned_int mcr
- The maximum collateral ratio that the borrower is willing to provide at the beginning of the loan, as a scaled percentageunsigned_int mccr
- The maximum collateral ratio the borrower will accept, below which a margin call of the loan is initiated, as a scaled percentageunsigned_int min_call_duration
- The minimum duration of a margin call in seconds, if one is necessary, after which a portfolio confiscation will be triggeredasset_id_type tradable_asset
- The asset type that the borrower wants to trade againstunsigned_int min_duration
- The minimum duration of the loan that the borrower is willing to accept, in daysunsigned_int max_duration
- The maximum duration of the loan that the borrower is willing to accept, in daysunsigned_int max_interest_rate
- The maximum daily interest rate that the borrower is willing to accept, as a scaled percentagetime_point_sec expiration
- Expiration date of the offerextension_type ext
- reserved for future extensionsValidation checks:
borrower
must be a valid account ID, must exist, must authorize the operation, must pay feeasset_to_borrow
andtradable_asset
must be valid asset IDs, must not be equal, and both assets must existmin_to_borrow > 0
max_to_borrow >= min_to_borrow
mcr >= mccr
max_duration >= min_duration
expiration > head_block_time
min_duration <= chain_parameters.max_duration
mcr >= chain_parameters.min_mcr
mccr >= chain_parameters.min_mccr
min_interest_rate <= chain_parameters.max_interest_rate
min_call_duration <= chain_parameters.max_call_duration
borrower
must have at leastmax_to_borrow * mcr
ofasset_to_borrow
in his balanceasset_to_borrow
must be authorized for margin lending againsttradable_asset
asset_to_borrow
and thetradable_asset
must not be transfer restrictedborrower
must be whitelisted or must not be blacklisted for theasset_to_lend
and thetradable_asset
due to transfer restrictionsEvaluation:
max_to_borrow * mcr
ofasset_to_borrow
fromborrower
balanceborrowing_offer_object
and populate object fields from operation fieldslending_cancel_operation
(new)This operation can be used to cancel lending and borrowing offers.
Fields:
account_id_type owner
- Creator of the operation (fee paying account), must equal owner of the offeroffer_id_type offer
- Either alending_offer_id_type
or aborrowing_offer_id_type
extension_type ext
- reserved for future extensionsValidation checks:
owner
must be a valid account ID, must exist, must authorize the operation, must pay feeoffer
must be a valid lending offer ID or borrowing offer ID and must existoffer.owner == owner
Evaluation:
offer
is a lending offer:offer.max_amount
ofoffer.loan_asset
toowner
balanceoffer
is a borrowing offer:offer.available_collateral
ofoffer.loan_asset
toowner
balanceoffer
from databaseowner
lending_accepted_operation
(new, virtual)Fields:
account_id_type offerer
- must equal owner of the offeroffer_id_type offer
- id of the accepted offer,lending_offer_id_type
or aborrowing_offer_id_type
loan_portfolio_id_type loan
- id of the resulting loan portfolioloan_interest_operation
(new, virtual)Fields:
account_id_type lender
- the lender's account idaccount_id_type borrower
- the borrower's account idloan_id_type loan
- ID of the loan portfolio to adjustasset interest_amount
- Amount of interest paid toloan.lender
loan_closed_operation
(new, virtual)Fields:
account_id_type lender
- the lender's account idaccount_id_type borrower
- the borrower's account idloan_id_type loan
- ID of the loan portfolio to adjustasset principal_paid_back
- Amount of principal paid back to lenderasset trade_confiscated
- Amount of trade asset paid to lenderasset principal_turned_out
- Amount of principal paid out to borrowerasset trade_turned_out
- Amount of trade asset paid out to borrowerloan_close_operation
(new)Fields:
account_id_type borrower
- the borrower's account idloan_id_type loan
- ID of the loan portfolio to adjustValidation checks:
borrower
must be a valid account ID, must exist, must authorize the operation, must pay feeloan
must be a valid loan portfolio ID and must existloan.owner == borrower
head_block_time >= loan.earliest_end
loan.principal_in_orders == 0 && loan.trade_in_orders == 0
loan.principal_balance >= loan.principal_borrowed + loan.daily_interest
Evaluation:
loan.principal_borrowed
ofloan.principal_asset
toloan.lender
loan.principal_balance - loan.principal_borrowed
ofloan.principal_asset
toloan.borrower
loan.trade_balance
ofloan.trade_asset
toloan.borrower
loan_closed_operation
loan
loan_update_operation
(new)Fields:
account_id_type owner
- Creator of the operation (fee paying account), must equal owner of the loan portfolioloan_id_type loan
- ID of the loan portfolio to adjustasset principal_delta
- Amount of principal asset to add / withdrawasset trade_delta
- Amount of trade asset to add / withdrawextension_type ext
- reserved for future extensionsValidation checks:
owner
must be a valid account ID, must exist, must authorize the operation, must pay feeloan
must be a valid loan portfolio ID and must existloan.owner == owner
principal_delta != 0 || trade_delta != 0
principal_delta >= 0
!confiscation_time.valid || trade_delta >= 0
principal_delta > 0
ortrade_delta > 0
,owner
must have sufficient balancetrade_delta < 0
loan.trade_balance >= -trade_delta
mcv = loan.principal_borrowed + loan.minimum_collateral
is_reference_price_valid
loan.principal_balance + loan.principal_in_orders < mcv
min_trade = reference_price * (mcv - loan.principal_balance - loan.principal_in_orders)
loan.trade_balance + loan.trade_in_orders + trade_delta >= min_trade
!is_reference_price_valid
)mcv <= loan.principal_balance
Evaluation:
principal_delta > 0
:principal_delta
fromloan.owner
's balanceprincipal_delta.amount
toloan.principal_balance
trade_delta != 0
:trade_delta
fromloan.owner
's balancetrade_delta.amount
toloan.trade_balance
Loan trading
Note: trading from a loan portfolio happens on the same markets as trading from an account. Trading is therefore not implemented separately, but through modifications to the existing trade mechanisms.
Fields:
The existing
limit_order_create_operation
andfill_order_operation
receive one optional extension field:loan_id_type loan
- ID of the loan portfolio from which the trade is executedThe
loan
field is not allowed before the hardfork time, neither directly nor in proposals.Validation checks:
If the
loan
extension is present in alimit_order_create_operation
, the following checks replace the existing checks against the seller's account balance:loan
is valid and refers to an existingloan_portfolio_object
seller == loan.owner
!loan.confiscation_time.valid
(no trades after margin call)amount_to_sell.asset_id == loan.principal_asset || amount_to_sell.asset_id == loan.trade_asset
amount_to_sell.asset_id == loan.principal_asset
:loan.principal_balance - amount_to_sell.amount >= loan.minimum_collateral
min_to_receive.asset_id == loan.trade_asset
!is_reference_price_valid
0 < amount_to_sell.amount <= loan.principal_balance - mcv
amount_to_sell.asset_id == loan.trade_asset
:loan.trade_balance >= amount_to_sell.amount
min_to_receive.asset_id == loan.principal_asset
!is_reference_price_valid
0 < min_to_receive.amount <= loan.principal_balance - mcv
Evaluation:
loan
extension will be recorded in the newlimit_order_object
loan
field is present,amount_to_sell
will be deducted from theloan
balance and recorded inloan
's..._in_order
fields, not the account'sfill_order
will be modified to pay trade proceeds intoloan
portfolio and adjustloan
's..._in_order
fieldsfill_order
must re-appraise the portfoliocancel_order
will be modified to return funds intoloan
portfolio and adjustloan
's..._in_order
fieldsDatabase API Calls
The following methods will be added to the
database_api
:vector<lending_offer_object> get_lending_offers_by_asset <loan-asset> <trade-asset> <optional limit> <optional start>
vector<borrowing_offer_object> get_borrowing_offers_by_asset <loan-asset> <trade-asset> <optional limit> <optional start>
vector<lending_offer_object> get_lending_offers_by_account <account> <optional limit> <optional start>
vector<borrowing_offer_object> get_borrowing_offers_by_account <account> <optional limit> <optional start>
vector<loan_portfolio_object> get_loans_by_lender <account> <optional limit> <optional start>
vector<loan_portfolio_object> get_loans_by_borrower <account> <optional limit> <optional start>
vector<limit_order_object> get_orders_by_loan <loan-id> <optional limit> <optional start>
All result lists are ordered by ascending object id. Server-side limits are configurable.
Processing Logic Changes
Automatic Matching of Offers
Similar to database::apply_order(). Triggered when a new offer is evaluated.
taker_offer
=new_offer
new_offer
is loan offerprioritization_policy
= Favor Borrowers policycounter_offers
= existing borrow offersprioritization_policy
= Favor Lenders policycounter_offers
= existing loan offerscompatible_offers
=find_compatible_offers
(new_offer
,counter_offers
,prioritization_policy
)compatible_offers
maker_offer
= highest-prioritized counter offerloan_object_id
,taker_offer_filled
] = create_loan(taker_offer
,maker_offer
,prioritization_policy
)taker_offer_filled
Margin calls
loan.confiscation_time = head_block_time + loan.call_duration
loan.principal_balance >= loan.principal_borrowed + loan.daily_interest
: close loan as described abovegap = loan.principal_borrowed + loan.daily_interest - loan.principal_balance
limit_order_create
forloan
withamount_to_sell = loan.trade_balance
andmin_to_receive = gap
gap
is smaller or perhaps closed)Notes:
gap
, possibly at a price far away from the usual market price. Thus, the borrower should avoid being margin called.gap
. It may then be impossible to create a new order for the remaining gap, because that would be considered "dust". The consequence would be that the loan stays in margin call state until it is confiscated. For practical purposes this shouldn't make much of a difference because rounding issues are a few "satoshis" only.Interest payments
Similar to
database::clear_expired_proposals
, in each blockloan_portfolio_object.interest_due_at
againsthead_block_time
!loan_portfolio_object.confiscation_time.valid
,loan.daily_interest > loan.principal_balance
: initiate margin_callloan.daily_interest
fromloan.principal_balance
loan.daily_interest
ofloan.principal_asset
toloan.lender
's balanceloan.daily_interest
toloan.cumulative_interest
loan_interest_operation
loan.interest_due_at
Expire open offers
Similar to
database::clear_expired_orders
, in each blocklending_offer_object.expiration
andborrowing_offer_object.expiration
againsthead_block_time
lending_cancel_operation
and execute as describe aboveExpire open loans
Similar to
database::clear_expired_orders
, in each blockloan_portfolio_object.latest_end
againsthead_block_time
limit_order_cancel
operationsloan.principal_balance < loan.principal_borrowed + loan.daily_interest
: initiate margin callHandle margin calls
In each block, for each loan that is in margin call state,
loan.principal_balance >= loan.principal_borrowed + loan.daily_interest
Confiscate expired margin calls
Similar to
database::clear_expired_orders
, in each blockloan_portfolio_object.confiscation_time
againsthead_block_time
loan.principal_balance
ofloan.principal_asset
toloan.lender
's balanceloan.trade_balance
ofloan.trade_asset
toloan.lender
's balanceloan_closed_operation
loan
Vote tallying
vote_tally_helper
computesvoting_stake
per account as before, plus core intrade_asset
in a loan_portfoliolender_stake = 0
borrower_stake = trade_balance
principal_asset
in a loan_portfoliolender_stake = min(principal_balance, principal_borrowed)
borrower_stake = principal_balance - lender_stake
Calculate reference price
is_reference_price_valid = true
andreference_price = global_settlement_price
is_reference_price_valid = true
andreference_price = highest_offer
is_reference_price_valid = true
andreference_price = last_exchange_price
is_reference_price_valid = false
Portfolio appraisal
principal = loan.principal_balance + loan.principal_in_orders
principal >= loan.mccv
, clearloan.call_price
(loan.trade_balance + loan.trade_in_orders) > 0
loan.call_price = (loan.mccv - principal) / (loan.trade_balance + loan.trade_in_orders)
reference_price
is valid andreference_price < loan.call_price
: trigger margin callChanges to
cli_wallet
The following commands will be added to
cli_wallet
:list_lending_offers <account>
list_borrowing_offers <account>
get_lending_offers <loan-asset> <trade-asset>
get_borrowing_offers <loan-asset> <trade-asset>
lending_offer_create
with operation parametersborrowing_offer_create
with operation parameterslending_offer_cancel <id>
lending_offer_accept <id> <amount> <duration>
loan_update <id> <delta-principal> <delta-trade>
get_loan_valuation <id>
get_loan_call_price <id>
loan_close <id>
sell_asset
command will receive an additional optional parameter, the loan portfolio idDiscussion
Risks
Financial: Price of a market pair on the DEX
A stagnant, nascent, or illiquid order book on the DEX for a particular market pair might not reflect the valuation of the collateral according to external market pairs. That will affect the appraisal value of the loan collateral which then affects margin calculations. Margin calculations affect both future loan offers on the books and matched loans.
Potential lenders and borrowers should carefully review any internal market pair and compare it with the external market pair to determine (a) whether internal market reflects a reasonable exchange ratio/price, and (b) whether the internal market could be easily manipulated to either overvalue or undervalue collateral.
Financial: Margin Calls at Market Price
If a margin call is initiated and if a liquidation plan requires selling the tradable asset to repay the lender in lent asset type, borrowers should be aware that it will be sold as an effective market order. The resulting sale on the DEX order book may return much less than if the offer were made on an external market.
Financial: Repayment of a Margin Called Loan
Loans that are margin called might require a liquidation plan that involves placing an limit order to buy enough of the lent asset to repay the loan.
If the market order remains unfilled on the DEX order book in excess of maximum margin call duration, the borrower's entire loan portfolio shall be confiscated thereby leaving the borrower with nothing after the loan closure.
Financial: Avalanche effect of Margin Calls
A margin call on a loan portfolio will immediately try to buy large amounts of the borrowed asset from the market. This can lead to a sudden spike in the trade price. This in turn can affect the reference price, which could lead to additional margin calls in other portfolios.
Powers of Asset Issuers
Asset issuers have extensive control over how their asset is used on BitShares including the ability to whitelist the trading of an asset against other assets), to restrict the transfers of an asset, and to seize any issued asset from an account if the asset is defined with the appropriate flags. These interaction of these powers with lending for margin trading are described.
Market Restrictions
The power to whitelist and blacklist trading pairs for an issuer's asset, which has the appropriate flags enabled, shall be unaffected by this proposal. This lending proposal makes use of the existing trading mechanisms therefore all rules shall continue to apply.
For example, if an issuer's asset is blacklisted from trading against any other asset, no trading of the Asset will be possible either from an account's regular set of balances or from their loan portfolio.
Alternatively, an issuer's asset (X) might initially be whitelisted to trade against any other asset, which permits the creation of a loan portfolio to trade against another asset (Y). Trading by the borrower ensues and the borrower obtains some quantity of Asset Y in their portfolio. If the asset issuer then blacklists trading between X and Y, the borrower shall no longer be able to trade the asset from anywhere including their loan portfolio. Another effect will be that margin calls shall no longer be able to be liquidated by means of buying back the borrowed asset on the DEX. Consequently if a margin call is initiated after a blacklisting and the loan portfolio's balance of the borrowed asset was insufficient to repay the lender, the margin call shall eventually result in an unconventional loan closure.
Transfer Restrictions
The existing power to restrict the direct transfer of an issuer's asset, which has the appropriate flags enabled, from one account to another shall be unaffected by this proposal.
Interest payment involves the transfer of the [borrowed asset-type](#borrow-asset] from the borrower to the lender. Therefore the creation of loan and borrow offers, and the matching of offers shall only be permitted if (a) if the borrow asset is not transfer restricted, and (b) if both the lender and the borrower are whitelisted or are not blacklisted for the borrow asset.
An unconventional loan closure transfers all balances of the borrow asset type and the tradable asset type to the lender. Therefore the creation of loan and borrow offers, and the matching of offers shall only be permitted if (a) if the tradable asset is not transfer restricted, and (b) both the lender and the borrower are whitelisted or are not blacklisted for the tradable asset.
Asset Seizure
The power to seize an issuer's asset, which has the appropriate flags enabled, shall remain possible if the asset is held in the account's regular set of balances. This power does not currently extend to assets held in open orders. Similarly, it shall not be possible to seize an asset that is held inside of a loan offer, borrow offer, or loan portfolio. An asset issuer may instead first impose a transfer restriction on the account, and then wait for the loan to be closed with appropriate balances being distributed to the regular balances of the borrower and lender at which time the conventional asset seizure may be invoked.
Summary for Shareholders
This BSIP defines a protocol upgrade to support peer-to-peer lending, borrowing and margin trading markets on the BitShares DEX. The motivation behind this BSIP is to increase the user demand for smartcoins on BitShares by offering on-chain peer-to-peer lending and borrowing to augment the existing trading. The multiple stage process between borrowers and lenders is supported with software specifications and a discussion of risks to lenders, borrowers, and asset holders, and asset issuers.
Copyright
This document is placed in the public domain.
See Also