Are you in a hurry? Use the links below.
(*2) For browsers that don’t have MetaMask-Extention and not support ENS.
To be censorship resistant, Augur UIs are served via a peer-to-peer content network called IPFS. The content of Augur UI is referenced by a CID (
content identifier). You can either run your own IPFS gateway so you don’t have to trust anyone by installing IPFS Desktop or you can trust a Public IPFS Gateway like dweb.link, eth.link, cf-ipfs.com.
As an example, the CIDv1 of Augur UI for trading (version 2.1.10) is:
This content would have a URL of:
If viewed via a local IPFS gateway:
If viewed via centralized gateway:
https://bafybeig25rero6xqll7vawbdcu3neccpaagelibl7zp6wrj76tynndkfnm.ipfs.dweb.link https://bafybeig25rero6xqll7vawbdcu3neccpaagelibl7zp6wrj76tynndkfnm.ipfs.cf-ipfs.link https://bafybeig25rero6xqll7vawbdcu3neccpaagelibl7zp6wrj76tynndkfnm.ipfs.eth.link
As you see, the URL containing CID is long and not human readable. In addition, each new UI release will produce a different CID. These make it almost impossible to memorize the URLs of the UI. However by using the (semi-trusted) ENS solutions listed below, you can reduce the pain you experience when accessing the UI.
”Community Managed UI” is the Augur UI which is linked by ENS whose content (CID) is updated by a community.
Ethereum Name Service) is a censorship resistant name resolution system. It natively supports IPFS content hashes. It serves the same purpose that DNS does in the legacy internet. While a DNS address generally maps to an IP address that is hosting a website, an ENS address generally maps to the content hash of a website. If you want to know more about ENS, check the ENS documentation.
In short, ENS lets you access Augur UI with a URL that does not contain a CID.
It should be noted that when the UI is updated, the CID changes. Therefore the CID registered with the ENS must be updated each time the UI is updated. Otherwise the UI referenced by the ENS will remain out of date.
Browsers that support ENS natively are:
Don’t worry if you don’t meeet the above requirements, there is a way to access Augur UI without using the content hash directly. That is to append
.link to the end of any ENS domain name.
For example, if the ENS domain name is:
.link to the end:
That’s all. Just type this string into your browser’s address-bar, then you get the content from IPFS via the eth.link public IPFS Gateway!
augur2.eth is one of the ENS domains where Augur UI is registered. This domain is managed by Augur community members called smarty-pants.
The CID registered with the ENS is updated by a DAO whose members are these Augur community members. They have shown a deep knowledge and interest in Augur and have received the smarty-pants role in Discord. Each time the UI is updated, they will verify that the CID provided by the Augur devs is the correct one and update the CID registered with
augur2.eth via vote (majority wins, quorum of 2).
Note: Subdomains do not work well with ens.link, so they have ceased to be updated. It is recommended to NOT use
reporting.augur2.eth as they are not maintained.
If there are ENS domain which has Augur UI content other than the above, these will be listed here. If the list is not shown, that means there are no such ENS domain.
This is the list of products that have been released in the Augur GitHub Repository.
Every Augur release has two versions,
reporting. The reporting UI is basically browse-only as it has trading disabled but you can use it to participate in the Augur reporting system. The trading UI has no restrictions, which means you can use it for both reporting and trading.
Why does the reporting version (read only) exist? The underlying reasons are unknown, but it is suspected to be for legal reasons.
Gambling is prohibited in some countries, and when those people use Augur UI, it is suspected that the developers of Augur want to disable trading for them. In fact, when accessing Augur UI from the link on augur.net, people in certain countries are redirected to the reporting UI, and people in other countries get sent to the trading UI.
There is no official announcement about the reasoning for this from Forecast Foundation.