interesting errors.  If we can get a backtrace of the crash that would be helpful.

Quote from: bytemaster on February 26, 2016, 08:40:22 pm

I am looking for someone to put together a nice "market status" that loads "instantly" rather than with a delay.

It should be able to display any market pair on BTS and show the price history, order book, and market depth chart.

Ideally it would be on something like cryptofresh.com.

It should work with server-side rendering and not require downloading 2MB of JS.

The assets pages have a basic market status section: https://cryptofresh.com/a/BTC -- does it load fast enough?

As far as I can tell, it's mostly just missing the depth chart and the ability to look at different pairs.. these market views will get dedicated URLs, something I plan to tackle early March if my worker gets voted in.. and it does look like it's on track

Yeah, I would like the ability to specify pairs and to show a depth chart / price up top.   Other stats are less important.

Anyone who would like to experiment with stealth UI please post in this thread:

http://stealth.cnx.rocks/

To get started, create an account on the test network.
Then go to settings and enable multiple account mode.
Then go to dashboard and create private account
Then give someone your public key.. or get someone else's public key
Then add public account (with their public key)

Private accounts are indicated via a "~ACCOUNTNAME" in the transfer to/from field.  These accounts are not registered and are just local labels.

I have identified some major usability issues that we are going to address...

Some issues I found...

1. It should ask you to unlock prior to asking you to select a new account name rather than failing after you enter an account name because the wallet is locked.
2. Truncating the public key behaves poorly and unexpected when you click on it (we will remove the truncation)
3.  Clicking on a blind account should take you to the transfer page with the "from" already filled in
4. All account balances of from account should be displayed above the history
5. There is no way to recover past transfer receipts after you close the dialog, be sure to copy the receipt and give it to the person you are sending funds to.

This is the minimum interface to get things functional and does not represent what I consider to be a "finished" feature. 

The challenge is to create a bond market where lenders can earn interest while being 100% protected against default by the borrowers. This means that at all times the blockchain must be able to cover all loans on the market.

This is difficult because it is computationally expensive to calculate the cascade effect of multiple margin calls and this must be done after every market operation.

The Solution

Someone who wants to borrow an asset may do so as long as there exists enough orders on the book to cover their new position and all other open loan positions at the price of  the least collateralized loan’s DEBT to COLLATERAL. The least collateralized loan establishes what we call the SWAN PRICE, short for black-swan. 

Every time a limit order is created, filled, or canceled the blockchain updates a running total of how much of a given asset is available for sale above the SWAN PRICE.

Every time a loan position is updated and a new SWAN PRICE is established, the blockchain must also update how much of a given asset is available for sale above the SWAN PRICE.

Basic Algorithm

    Let TAS = Total asset for sale above swan price.
    Let TD   = Total asset that has been borrowed

    onOrderUpdate   /// create, cancel, fill
       try
          push undo state
          create, cancel, or fill orders on the book
          update TAS
          if( TAS < TD )
                undo changes and throw
          commit changes
      catch
          execute margin call on least collateralized loan
          goto try

Someone looking to borrow an asset makes a request of the network that includes:

1. how much they wish to borrow
2. how much collateral they wish back it with

The borrowing request will be filled so long as they post sufficient collateral. The network will automatically bump lower collateralized positions if necessary.

A margin call can happen for any of the following reasons:
1. If canceling an open order would result in insufficient orders on the books to buy back the debt with the collateral, then a margin call is executed first, then the order is canceled (if it wasn’t used as part of the margin call).
2. If filling an order would result in insufficient orders on the books to satisfy all debt at the SWAN PRICE, then the margin call is executed first.
3. If someone is looking to borrow, offering more collateral than the SWAN PRICE, and there is insufficient orders above the SWAN price then the least collateralized position is called. This will update the SWAN price to the next best.

The impact of these rules is the following:

1. The least collateralized position is always at risk of margin call when there is more demand for loans than orders on the book.
If there are more orders on the book than demand for loans, then collateral requirements can fall and the least collateralized position is safe from potential margin call

2. The ability to move an order, rather than cancel and create a new order must be supported to prevent unnecessary margin calls.
Borrowers will post sufficient collateral to ensure sufficient market depth that they are not at risk of being called.

3. Increasing collateral lowers SWAN PRICE and increases the number of orders above SWAN and thus increases SUPPLY of asset to be borrowed.
Interest Payments

4. Everyone with an open order on the books above the SWAN PRICE is effectively lending money to those who wish to borrow. If there is heavy demand for borrowing then the market response should be to pay interest to the lenders.

In this algorithm, the network charges a “fixed” interest rate on the variable collateral. In this way the interest charged to borrowers grows along with the collateral requirement. Every open order on the books above the SWAN PRICE receives their pro-rata share of the interest paid by borrowers.

Lenders have the ability to “set their interest rate” and “collateral requirement” based upon the price at which they leave their order open on the book. If demand for loans grows enough to find the least collateralized loan  (SWAN PRICE) to be above the order price, then the loan is executed and the lender starts earning interest. If the SWAN PRICE never reaches the order price then the loan is not accepted and no interest is paid.

The impact of interest is to increase the number of orders on the book above the SWAN price which in turn serves to reduce collateral requirements.

The “fixed” interest rate can be configured by the asset issuer. If collateral requirements start to get unreasonably high, then interest rates can increase.


Feedback Wanted

I am looking for someone to put together a nice "market status" that loads "instantly" rather than with a delay.

It should be able to display any market pair on BTS and show the price history, order book, and market depth chart.

Ideally it would be on something like cryptofresh.com.

It should work with server-side rendering and not require downloading 2MB of JS.

can someone pull out the good ideas from that thread?

I am curious how much Stellar and Ripple paid each user who signed up on their platform.

I am particularly interested in the dollar value they gave away.