Augur Front-End Technical Update – Oct 26th

Augur Front-End Technical Update – Oct 26th

The Augur team has been making steady progress with the new user interface. In this update, Jack details new improvements merged over the past week.

Recent builds can be found on our Firebase instance, which is currently running on the Ethereum testnet. However, due to recent attacks on the network, transactions tend to be very slow. To increase transaction speed for testing, we’ve run an Augur instance on our own private chain. Keep in mind that the private chain is reset often, and usually contains the bleeding edge changes that we haven’t pushed to the main app yet.

We’ve also launched a UserVoice account to collect the community’s product feedback. If you have any suggestions for improvements or new feature requests, please let us know here. We encourage community members to participate in the discussion surrounding feature development on UserVoice.

Technical Updates:

Oct 25th, 2016 @ 11:33PM PST

  1. If you create an account through our registration process, the block number in which you registered is saved (logged) to the blockchain. The front-end now uses this registration block number to intelligently set the lower bound (fromBlock) of event log lookups. This should help speed up the lookup of your trading activity, which can be a data-heavy request.

Oct 25th, 2016 @ 7:123PM PST

  1. Fixed partial message chat input entry bug.
  2. Chat input text box now properly clears after sending.
  3. Added mutex locks to ethrpc’s transaction objects. These are locked while the onNewBlock listener callback is executing. This should prevent the “callback-already-called” exception that was sometimes thrown if 2+ blocks arrived in short succession (common right after private chain resets, when block times are abnormally fast). I believe this fixes the persistent “last trade price not updated” error (although I am not positive — please ping me if it is observed again).
  4. Chat input will no longer submit empty strings / strings containing only spaces.
  5. Users are no longer required to login to chat.
  6. Chatbox now auto-scrolls all the way to the bottom (if user was already at the bottom).
  7. Fixed duplicate list key warning in chatbox.
  8. Added address as popup text if user is chatting with their display name instead of address.
  9. Added Unicode support to chat.

Oct 25th, 2016 @ 6:34AM PST

  1. Sprinkle fixed the Firefox scrolling bug.
  2. Added chat box. Right now there is just a single chat room for the entire site — a “trollbox” ala Poloniex, Bittrex, et al. The chat middleware is set up in a way that is trivially extensible, so if we decide we want separate chatboxes for each market, that is straightforward to add. Note: the chat box uses Whisper, a P2P messaging protocol that does not have any kind of persistence built-in. Messages only last for a few minutes, and you have to be online to see new messages.
  3. Removed (Feedback button) as people were not using it.
  4. Changed navbar/sidebar colors back to “Augur purple”, just to see how it looks. (If users prefer the blue, can definitely change it back!)

Oct 23rd, 2016 @ 8:32PM PST

  1. Buy/sell complete sets now have an implicit price assigned to them of 1/numOutcomes (that is, all outcomes are equally priced for the complete set). The purpose behind this change is so that complete sets buy/sells can be included in per-outcome P/L calculations. Note that, if this equal-price-per-outcome value differs from the market price at the time the complete set is bought or sold, the outcome realized P/L values may be somewhat different than if you executed an ordinary buy or sell trade! However, the net realized P/L (for the entire market, across all outcomes) will be correct.

Oct 23rd, 2016 @ 2:38AM PST

  1. Fixed P/L calculations for trades going from a net long to net short position, or vice-versa.
  2. “Close Out Position” has been re-labeled “Redeem X Complete Sets”.

Oct 22nd, 2016 @ 2:09AM PST

  1. “Sell Complete Sets” has been re-labeled to “Close Out Position” everywhere this concept is exposed to the user. This is intended to avoid confusion for users attempting to close out a short position (which requires them, somewhat unintuitively, to sell a complete set).
  2. The label for the automatic sell complete sets checkbox on the Accounts page has been improved.
  3. Buy and sell complete sets are now explicitly accounted for in the positions and P/L calculations. (Testers: feedback / suggestions on the sell complete sets stuff is especially valuable, as I am finding this to be a somewhat tricky UX problem!)
    1. Shares acquired via buy complete sets (i.e., new shares issued) are included in the positions total. However, since there is not a price for each outcome within the complete set, the shares from the complete set do not contribute to the mean price of open position. (Note: this only applies to complete sets bought manually by the user. Complete sets bought as part of short selling are not included in the positions total.)
    2. Complete sets sold to close out a long position are deducted from your total position. Since there is not a price for each outcome within the complete set, selling the complete set does not change realized P/L.
    3. Motivating example: suppose you have short sold 2 shares of one outcome in a market. The UI displays your position as -2 in that outcome, and 0 in the other outcomes. To close out your short position, you buy 2 shares in the same outcome. The UI now shows your position as 0 in all outcomes. However, what has happened behind the scenes is, you were actually long the other outcomes (and 0 in the outcome you shorted), and when you bought back 2 shares, now you have 2 shares in all outcomes. Therefore, to actually close out your position, you have to sell 2 complete sets.
      Complete sets sold to close out a short position work as follows. If you have a short position, shares bought back are added to your position, but they do not contribute to your realized P/L until you have actually sold the complete set(s) back. Shares that have been bought back but not yet closed out (via sell complete sets) are “queued”, and the system calculates a “queued P/L” for these shares. (Currently, queued P/L is simply added to unrealized P/L, but it may help clarify things for the user to show it explicitly in the positions display.) Also, note that if you have manually bought any complete sets, your complete sets sold are first netted with the complete sets bought; only the excess complete sets sold are used to close out queued shares.
  4. Open orders are now sorted in descending order, asks first.
  5. Fixed a bug that was preventing the Portfolio page from loading.

This log is kept daily on your login message page, accessible in your account tab under “Important Information”.

Please join our Slack if you’re looking for daily discussions. We’ll be back soon with another update on our progress.

– The Augur Team

Comments are closed.