Augur Front-End Technical Update – Dec 7th

Augur Front-End Technical Update – Dec 7th

The Augur UI React Components repository and the Augur repository have been merged! It currently resides within the 1281-aurc-merge branch, soon to be the master Augur branch. Documentation has been updated to include running an Ethereum node locally, as well as Yarn build instructions. With the repos merged together, we expect a significant increase in development speed.

Contracts are now deployed on the Ropsten testnet for app.augur.net – while private.augur.net is still running on our own private chain. If you experience rejected transactions on app.augur.net due to the Ropsten testnet, you’re welcome to use our private chain for testing. Reporting and revealing edge cases are continuing to be smoothed out and addressed.

We will soon be releasing a checklist of actions and functionality to be formally tested on the Augur platform. This will be apart of the expansion within our controlled testing groups.

Security Reminder:


With the recent hacks of Augur affiliates, please be sure you are hardening your security. Read Kraken’s blog post about how to properly setup your 2FA, secure your phone line, and setup recovery options if you haven’t already. Check your email across HaveIBeenPwned to confirm you don’t have active leaked passwords out in the wild. Consider storing your crypto on something like a Ledger Nano S (which supports all ERC-20 token types). Reduce your attack surface as much as possible. The attacks have nothing to do with the Ethereum blockchain or the Augur project itself, they are all on individuals.


Augur Front-End Technical Update:

December 6, 2016

  1. Use last block gasLimit to set raw transaction gasLimit, if available.
  2. Removed conditional call to collectFees contract from submitReport: this call was not working correctly and (if fixed) would bring additional complications with it, so decoupling these functions seems like the better solution.
  3. Fixed first-reporting-cycle collectFees bug.
  4. Reversed order of UI calls to collectFees and revealReports in checkPeriod; collectFees is now called first.
  5. Added a filter that listens for market closings, and calls claimProceeds when events happen.
  6. Fixed the outcome name lookup of binary markets for reveal-reports.

December 5, 2016

  1. Added an optional timestamp argument to getCurrentPeriod and getCurrentPeriodProgress.
  2. Added explicit penalizeWrong and closeMarket wrappers to augur.js.
  3. Fixed penalizationCatchup call condition and added onSent/onSuccess callbacks to augur.js combined reporting functions.
  4. Moved payout augur.js functions to separate module.
  5. Fixed sender reference errors in payout functions.
  6. Added manual message updates to checkPeriod and claimProceeds functions.
  7. Removed account trades from localStorage.
  8. Removed duplicate address field (id) from loginAccount.
  9. Full contract re-upload on both network 9000 (private chain) and network 3 (public chain).
  10. Manually editing transaction display messages now disables automatic (return value-based) messaging transaction relay updates.

December 4, 2016

  1. Reputation faucet now correctly sets fees collected for the new reporter.
  2. Fixed sender address references in on-contract payout functions.
  3. Fixed condition under which Reporting catch-up function is called, instead of comparing event reports to the consensus (penalizeWrong).
  4. The UI now uses the current block timestamp to set Reporting cycle position.
  5. Removed duplicate address field from UI login account state.
  6. Removed account trades data from localStorage.

December 3, 2016

  1. Fixed a bug causing report period to be unassigned during commit report.
  2. Fixed filters (blockchain listeners) on non-root branches.
  3. Cash balances are now correctly displayed and updated on non-root branches.
  4. Last outcome price selector now directly uses the outcomes data state instead of the markets selector.
  5. Added contract method return value to transaction relay (auto-generated) display panels.

December 2, 2016

  1. Fixed reporting edge case where all markets in a reporting cycle have 0 volume.
  2. Assign reputation faucet starting report period depending on whether user accesses faucet during the first or second half of the current reporting cycle.
  3. Negative prices are now handled correctly during both trade and short sell.
  4. Updated geth.js start/stop package and tests.
  5. Added each-market-type order maker convenience method to augur.js reputation testing tools.
  6. Improved display of long messages in transaction display.

December 1, 2016

  1. Added more thorough unit tests for the trading UI.
  2. Uploaded Augur contracts to the new Ethereum public test network (“Ropsten”). Also moved the Augur faucet and public geth node (eth3.augur.net) to Ropsten. app.augur.net and augur-dev.firebaseapp.com are now configured to use the new Ropsten contracts. local.augur.net will also use Ropsten if you are not running a local Ethereum node. For users that prefer to remain on our private chain (network 9000), we are planning to maintain private.augur.net for the remainder of the beta test. Users of private.augur.net should be aware that the network 9000 blockchain is reset on a semi-regular basis, often without any public announcement/warning, and when this happens, all your private chain Ether, Reputation, and trading shares are also reset.
  3. Fixed market description display and links back to the trade page on the transactions page.
  4. Fixed bug causing cancel order transactions to appear twice in the transactions display.
  5. Significantly extended timeout in augur.js requests module to avoid ETIMEDOUT errors when attempting to request ETH from the faucet. The timeout is now set to a large value (999999) which should not be reached unless the user is experiencing a connection problem.
  6. Significantly extended nginx timeouts for eth1.augur.net. It turns out that the CORS errors occasionally generated by the faucet are not true CORS errors; it is actually an nginx timeout which is (mis-)identified as a CORS error. The timeout is now set to a large value (999999) which should not be reached unless the user is experiencing a connection problem.

As always, please come join us in our Slack or Subreddit to stay up to date with recent developments.

– The Augur Team

Comments are closed.