Augur Development Update – Nov 9th

Augur Development Update – Nov 9th

Augur Development Update

We’ve had a number of events and updates this past week. We pushed the new market skin, saw some test markets resolve, and are on the lookout for a killer UI engineer!

This is very much an alpha of the new market skin – there are still various improvements and updates to come. However, we wanted to get the feedback cycle started as soon as possible. You can submit your suggestions using the feedback tab in the lower left side of the Augur client, or through our feedback page.

Reporting cycles on the testnet are only 48 hours long, and we encourage you to participate in them! You can find the reporting cycle status at the top of the markets page after you’ve logged in and recieved test REP.

Lastly, we’re looking to hire a UI engineer. You can submit your credentials on our careers page or via AngelList. If you know somebody you think would be a good fit, please send them our way!

Technical updates:

November 8, 2016

  1. Fixed button-not-clickable bug in create market workflow.
  2. Fixed report panel component and links. Reporting should now work with the re-skinned market detail page!
  3. The Feedback tab now sends user feedback to UserVoice, instead of
  4. Added penalizationCatchup to checkPeriod callback sequence for users who are multiple reporting cycles behind.
  5. Added a constant (all-ones) initialization vector to the encryptReport and decryptReport middleware functions if a salt argument is not supplied. Although the report needs to be encrypted with its salt, the (separately) encrypted salt does not need its own random salt.
  6. Removed refund macro from collectFees contract, since the transaction value must be accessed (and is expected to be non-zero) in the body of the method.
  7. Fixed sufficient value check in collectFees contract.
  8. Automatically add (500K wei)*gasPrice of value to the collectFees transaction payload in augur.js.
  9. Fixed final report market page link in next-report-page.
  10. Fixed REP balance comparison at the beginning of check-period.

November 7, 2016

  1. Reskinned the trade (market detail) page. There are a few minor bugs remaining but the trade page is fully functional and has an immensely improved look-and-feel!
  2. Fixed event description display for reveal-reports transactions.
  3. Fixed the claim-proceeds action, which is the final bet-payout mechanism once markets are successfully reported on and closed. This action was incorrectly firing claimMarketProceeds calls for some markets that were not yet closed.
  4. Added updateAssets and refreshMarkets calls after claim-proceeds completes successfully.
  5. Reordered checkPeriod callback sequences to allow for full reporter catch-up even if their REP redistribution is behind by multiple periods. Also added an extra check for REP redistribution to the submitReportHash onSuccess callback, which should short-circuit failing submitReportHash loops, if they are caused by not being caught up on penalizations/redistributions.
  6. Fixed chat messages display sent by users who do not have a name set (address-only).

November 6, 2016

  1. Reports from previous periods are now properly cleared from your pending reports.
  2. Refactored commit-report and its associated methods, and rewrote / greatly expanded the commit-report test suite.
  3. Added a message to markets that have been reported on and closed out: “This market is closed. Reported outcome: X”
  4. Made a modified reporting test sequence script that goes through a second full reporting cycle on the same branch ID that has already successfully completed its initial reporting cycle. Completed full test runs of both the initial reporting cycle sequence as well as multiple follow-up sequences. These automated use-tests only use a single reporter, but the results are as expected for this reporter. Next-up: automated reporting sequences using multiple accounts!
  5. Decoupled the UI reportingTestSetup method from its spawn-new-branch subroutine.
  6. Refactored load-reports and associated methods. load-reports is a group of functions that build the reports data structure (as well as update other related data) in the front-end. They lookup what events you are required to report on, which of these you have already reported on, pull your encrypted report and salt from the chain (and decrypt them), lookup if you have submitted a report hash or plaintext report, collates this info and stows it in Redux (the front-end data store). These methods did not have good unit test coverage (my fault — they became more complicated over time and the tests did not keep up). Since I have found multiple edge-case bugs over the past few days as I am user-testing reporting, I decided to take the time to pull these methods apart and added more thorough unit tests for them. Coverage is now significantly improved for these methods. (Note: to simplify mock creation for the unit tests, I split load-reports into several separate files/methods: load-reports, load-report, load-report-descriptors, and decrypt-reports.)

November 5, 2016

  1. Fixed transaction failure (error 500) edge case that failed (nulled) without retrying the transaction, even if retryDroppedTxs was set to true.
  2. Added extra on-chain market ID lookup and loadMarketsInfo action for the case where a commit report action has been sent but the eventID field of the market selector has not yet been assigned. As far as I can tell, the click-thru-to-next-report functionality is now working properly.
  3. Fixed scalar report outcome displays on transactions page.
  4. Added outcome names / IDs to transaction messages for commit report (submitReportHash) actions.
  5. Fixed initial trade-in-each-market setup for augur.js reporting-sequence tests.

November 4, 2016

  1. Added check that market outcome data has loaded before using it to calculate P/L.
  2. Changed the tooltips in the market preview panel (in the main markets listing) to use click-to-show-and-hide tooltips, instead of hover-to-show, since hover is not available on mobile. If these tooltips have the desired feel, the remainder of the tooltips can be converted to this form as well. (There are only a few exceptions, in the case of elements that have both a tooltip and a click function.)
  3. Market titles in the main markets listing now link to the trade page.
  4. Clicking on tags in the market preview panel (in the main markets listing) now works correctly.
  5. Added Real ETH (i.e., testnet Ether) balance display to the sub-navbar. Previously this was displayed as a popup when hovering over the transactions button on the main navbar, which did not make sense. Real ETH is an important value for users to know and to distinguish from the play-money “ETH” used for trading (i.e., Ether IOU tokens which will be tradeable one-to-one for Ether when Augur is live, but which are simply play-money during beta).

November 3, 2016

  1. Added react-tooltip module, and converted all “title” fields in the UI to instead use proper tooltips. (Values in title fields are not viewable on mobile.)
  2. Only add market description tooltips to the transactions display if a market description is truncated (to 100 characters).
  3. Changed currency abbreviations on the Account page to match those used elsewhere in the UI (REP for Reputation, real ETH for real Ether, and ETH for Ether).
  4. Changed the units for reporting cycle length display (was seconds).
  5. Moved the Branch component to its own module.

As always, come join us in Slack or on Reddit!

– The Augur Team

Comments are closed.