Augur Front-End Update – Dec 28th

Augur Front-End Update – Dec 28th

Happy holidays from the Augur Team!

Our developers have been keeping a rigorous development schedule, even with the holidays in full force. If you’d like more frequent technical updates than the blog posts, remember to check the login message page on Augur or join the #github channel on our Slack. The updates logged in these posts are always derived from our GitHub commits.

On contract updating: there will be three ways in which it can happen. The first being a key that can unilaterally update contracts (as in the beginning a malicious update by us is less likely than a bug that needs to be fixed quickly) that also has a function for the key to disable itself, and another where reporters can vote to disable the key. The second being a key that can make updates, but reporters have the chance to veto it within N timeframe (with the respective functions to disable this as well). Lastly, reporters will be able to vote on updates within the regular reporting cycle.

Next week we plan on publishing a set of walkthroughs / guides for testing the platform, along with a tutorial for securing your $REP with a Ledger Nano S.

Technical Updates:

December 28, 2016

  1. Refactored loadMarketsInfo: moved branch ID filtering and created market info loading into separate functions.
  2. Do not delete outcomes property of marketsData.
  3. When retrying log conversion, use augur.getMarketInfo directly instead of loadMarketsInfo to avoid branch ID filtering.
  4. Converted indeterminate constants to BigNumbers; updated comparisons in fix/unfixReport.
  5. Added more payout tests around claimMarketsProceeds.

December 27, 2016

  1. Fixed the ethicality displayed in converted transaction logs.
  2. Rounded off converted Reputation percents for display.
  3. Serialized log-to-transaction conversions.
  4. Refactored the winning positions lookup done in order to claim trading proceeds from closed markets.

December 26, 2016

  1. Refactored the gigantic switch in the generic log-to-transactions converter into a collection of small, composable, testable subroutines.
  2. The status-and-message display data is now organized separate from the main Transaction component, in a new TransactionMessage component.

December 25, 2016

  1. Removed the (unused) reporting period branch Reputation balance from the collectedFees log.
  2. Added a check of whether market has already been closed (winning outcomes already set) both before and after the closeMarket function is called from augur.js.
  3. Reporting cycle bar is now displayed at the top of the transactions page as well as the markets page.
  4. Removed unused reporting outcome display block.
  5. Load reporting history before branch sync (for logged in users).
  6. Added a special startup sequence to init-augur to allow semi-automated multi-user/single-machine reporting tests.
  7. Fixed payout lookup parameters in the account trade history log-loader.
  8. Used async.eachLimit instead of async.each in all log loaders to keep from overwhelming the receiving RPC server.
  9. Registration timestamps are now only recorded during the initial Airbitz account creation, not ordinary logins.
  10. Added an event-to-market lookup table to the front-end data store.
  11. Ad hoc balance and balance changes messaging in the transaction component have been replaced by a new balances array in the data field of any transaction that alters one or more balances.
  12. Each transaction conversion will now only retry once, if the required market data is not available.
  13. The fillOrder function now uses the correct side of order book.

December 24, 2016

  1. Added minimumTradeSize parameter to buy, sell, and shortAsk on contract and in augur.js.
  2. Fixed event validity bond calculation on the createMarket contract.
  3. Added a client-side (augur.js) method to calculate the validity bond, so that this can be displayed to the market creator prior to creating the market.
  4. Added event validity bond calculation to step 5 of create market; added new arguments to step 5 of create market: period length, base reporters, number of events created in the past 24 hours, number of events in this reporting period.
  5. Removed unnecessary field renaming in filters API: sender/owner are no longer changed to maker/taker in log_fill_tx, log_add_tx, and log_cancel.
  6. Logs and filters now behave consistently and use the same field names everywhere. (In augur.js, the augur.filters formatters are now used to parse logs in modules/logs.js.)
  7. Added getBaseReporters lookup to loadBranch (in augur.js), and added getPast24 and getNumberEvents lookups to syncBranch (in the UI). These values are attached to the branch state in the UI.
  8. Log-lookup callback arguments are now consistent, and take an error as the first callback argument.
  9. Replaced most special-purpose log-lookup methods with calls to augur.getLogs. A lot of semi-repeated code in modules/logs in augur.js has been removed as a result of this.
  10. Added registration log loader to the front-end.
  11. Removed deprecated code associated with market data updater timestamps.
  12. Price time series construction now uses logged timestamp instead of converting from block number.
  13. Removed onSuccess calculations from collectFees, since values are now pulled from the event log.
  14. Check if transaction already has status success before running onSuccess relay.
  15. The total amount of reputation reporting for the cycle is now displayed correctly in the collect fees transaction panel.
  16. The fillOrder action now updates market trades data and price history automatically.

December 23, 2016

  1. Added single-order add/remove/fill actions and used for targeted, no-RPC order book updates from filters.
  2. Offloaded trades and bids/asks update logic in trade process methods onto filters.
  3. Adjustments to the NPM scripts to improve the messaging during command execution.
  4. The reporting form is now encompassed within a tab in the market view rather than being a discrete view. This is so that users may continue to trade and so that reporters can reference relevant market data.
  5. The header in the markets view now updates to indicate when you are on the favorites or pending reports views.
  6. A slight adjustment to the Augur logo so that it remains centered in the header. Previously the nav items would push the logo off center.

December 22, 2016

  1. Converted maker trade transactions now have distinct messaging from normal (taker) trade transactions.
  2. Removed unnecessary registration filter.
  3. Refactored load-account-trades into composable loaders: deposit-withdraw, bids-asks, create-market, account-trades, and reporting.
  4. Placing a trade no longer automatically navigates you to the transactions view, but rather will leave you on the market view.
  5. Added final deleteTransaction call to trade process actions.
  6. Fees for maker trades no longer incorrectly display the taker fee.
  7. The trade inputs were incorrectly reporting invalid values via the hover title. This is now fixed, along with a custom value incrementer implemented on the input.
  8. The app is now a full width app! All components will scale out to whatever window width is available.
  9. Adjustments to the colors utilized due to a recent base color change. Also included in this set of changes was a removal of some legacy colors no longer used.

As always, feel free to reach out to us at and join our Slack!

– The Augur Team

  • Richard Colby

    Left my REP in the original ethereum address. Now it’s gone. Hacker called me and said he called T-Mobile to get my credentials. He took over my phone. He used “Authy” authentication to do the hack. all REP and ETH taken. If I’d only moved the REP to another address I’d still be invested. I was really looking forward to being part of this.

    • Richard, I’m really sorry to hear this, that is terrible 🙁

      Would you mind emailing me ( with the details of what happened? Am trying to compile all the info I can find on these hacks. Any details you know (especially your account address, how much was taken, etc.) are useful.

      • Richard Colby

        Jack, Thank you. You are a good man. I’ll send you all I know from a new email address. I hope to accumulate some more REP over the next year. Keep up the good work.

Comments are closed.