polkamarkets-js 3.4.0 → 3.4.2

package/lib/reality-eth-monorepo/packages/docs/audit_v3.rst

@@ -1,70 +0,0 @@
-Audit, v3.0 (including ERC20 version)
-=====================================
-
-Exported by Edmund Edgar from `Original audit document (PDF)`_.
-
-.. _`Original audit document (PDF)`: ../Audit_Reality_v3_202108.pdf
-
-Reality 3.0 / August 2021
--------------------------
-
-Files in scope
---------------
-https://github.com/RealityETH/monorepo/blob/064855bfd8c80a0bcf3da7b73936ce477e99b635/packages/contracts/development/contracts/RealityETH-3.0.sol
-https://github.com/RealityETH/monorepo/blob/064855bfd8c80a0bcf3da7b73936ce477e99b635/packages/contracts/development/contracts/RealityETH_ERC20-
-3.0.sol
-
-Current status
---------------
-All issues have been fixed by the developer. There are no know issues in
-https://github.com/RealityETH/monorepo/blob/e4584d7cf6ab2d9a5b129bd970b7d4517811ae6a.
-
-Issues
-------
-
-1. Incorrect bond payout on UNRESOLVED_ANSWER
----------------------------------------------
-
-type: faulty implementation / severity: medium
-
-When last answer is unrevealed and best answer is UNRESOLVED_ANSWER, the bond from the unrevealed answer will be paid to address(0) instead of to the winner which would we be the case if the best answer wasn’t an UNRESOLVED_ANSWER.
-
-status - fixed
-
-Issue has been fixed and is no longer present in
-https://github.com/RealityETH/monorepo/blob/e4584d7cf6ab2d9a5b129bd970b7d4517811ae6a
-
-2. Arbitration can be initiated even with no valid answer, resulting in premature finalisation after the arbitration is cancelled
----------------------------------------------------------------------------------------------------------------------------------
-
-type: security / severity: medium
-
-Arbitration can be initiated after an answer commitment is posted, even if no revealed answers have been posted, after this arbitration is
-cancelled the question will be finalised after finalize_ts seconds, even though no answer has been provided. In results all bonds will be
-paid out to address(0), bounty will become unretrievable and best_answer will be set to 0.
-
-status - fixed
-
-Issue has been fixed and is no longer present in
-https://github.com/RealityETH/monorepo/blob/e4584d7cf6ab2d9a5b129bd970b7d4517811ae6a
-
-3. answer_takeover_fee credited to second answer depends on the way answers are processed
------------------------------------------------------------------------------------------
-
-type: security / severity: medium
-
-In claimWinnings answer_takeover_fee is inconsistently calculated, it is being subtracted from bounty if the winning answer and second best answer are processed in one go, but if they are processed separately, the whole bounty amount is reserved for the winner and can’t by used for the fee.
-
-status - fixed
-
-Issue has been fixed and is no longer present in
-https://github.com/RealityETH/monorepo/blob/e4584d7cf6ab2d9a5b129bd970b7d4517811ae6a
-
-Notes
------
-
-RealityETH_ERC20-3.0.sol should not be used with ERC20-like token contracts that implement callbacks like ERC777 due to potential re-
-entrancy issues.
-
--------------------------
-G0 GROUP // Reality 3.0 / August 2021

package/lib/reality-eth-monorepo/packages/docs/conf.py

@@ -1,155 +0,0 @@
-# -*- coding: utf-8 -*-
-#
-# reality.eth documentation build configuration file, created by
-# sphinx-quickstart on Thu Sep 28 14:43:50 2017.
-#
-# This file is execfile()d with the current directory set to its
-# containing dir.
-#
-# Note that not all possible configuration values are present in this
-# autogenerated file.
-#
-# All configuration values have a default; values that are commented out
-# serve to show the default.
-
-# If extensions (or modules to document with autodoc) are in another directory,
-# add these directories to sys.path here. If the directory is relative to the
-# documentation root, use os.path.abspath to make it absolute, like shown here.
-#
-# import os
-# import sys
-# sys.path.insert(0, os.path.abspath('.'))
-
-
-# -- General configuration ------------------------------------------------
-
-# If your documentation needs a minimal Sphinx version, state it here.
-#
-# needs_sphinx = '1.0'
-
-# Add any Sphinx extension module names here, as strings. They can be
-# extensions coming with Sphinx (named 'sphinx.ext.*') or your custom
-# ones.
-extensions = []
-
-# Add any paths that contain templates here, relative to this directory.
-templates_path = ['_templates']
-
-# The suffix(es) of source filenames.
-# You can specify multiple suffix as a list of string:
-#
-# source_suffix = ['.rst', '.md']
-source_suffix = '.rst'
-
-# The master toctree document.
-master_doc = 'index'
-
-# General information about the project.
-project = u'reality.eth'
-copyright = u'2017, KK Social Minds'
-author = u'KK Social Minds'
-
-# The version info for the project you're documenting, acts as replacement for
-# |version| and |release|, also used in various other places throughout the
-# built documents.
-#
-# The short X.Y version.
-version = u''
-# The full version, including alpha/beta/rc tags.
-release = u''
-
-# The language for content autogenerated by Sphinx. Refer to documentation
-# for a list of supported languages.
-#
-# This is also used if you do content translation via gettext catalogs.
-# Usually you set "language" from the command line for these cases.
-language = None
-
-# List of patterns, relative to source directory, that match files and
-# directories to ignore when looking for source files.
-# This patterns also effect to html_static_path and html_extra_path
-exclude_patterns = ['_build', 'Thumbs.db', '.DS_Store']
-
-# The name of the Pygments (syntax highlighting) style to use.
-pygments_style = 'sphinx'
-
-# If true, `todo` and `todoList` produce output, else they produce nothing.
-todo_include_todos = False
-
-
-# -- Options for HTML output ----------------------------------------------
-
-# The theme to use for HTML and HTML Help pages.  See the documentation for
-# a list of builtin themes.
-#
-html_theme = 'sphinx_rtd_theme'
-
-# Theme options are theme-specific and customize the look and feel of a theme
-# further.  For a list of options available for each theme, see the
-# documentation.
-#
-# html_theme_options = {}
-
-# Add any paths that contain custom static files (such as style sheets) here,
-# relative to this directory. They are copied after the builtin static files,
-# so a file named "default.css" will overwrite the builtin "default.css".
-# html_static_path = ['_static']
-
-# -- Options for HTMLHelp output ------------------------------------------
-
-# Output file base name for HTML help builder.
-htmlhelp_basename = 'reality.ethdoc'
-
-
-# -- Options for LaTeX output ---------------------------------------------
-
-latex_elements = {
-    # The paper size ('letterpaper' or 'a4paper').
-    #
-    # 'papersize': 'letterpaper',
-
-    # The font size ('10pt', '11pt' or '12pt').
-    #
-    # 'pointsize': '10pt',
-
-    # Additional stuff for the LaTeX preamble.
-    #
-    # 'preamble': '',
-
-    # Latex figure (float) alignment
-    #
-    # 'figure_align': 'htbp',
-}
-
-# Grouping the document tree into LaTeX files. List of tuples
-# (source start file, target name, title,
-#  author, documentclass [howto, manual, or own class]).
-latex_documents = [
-    (master_doc, 'reality.eth.tex', u'reality.eth Documentation',
-     u'KK Social Minds', 'manual'),
-]
-
-
-# -- Options for manual page output ---------------------------------------
-
-# One entry per manual page. List of tuples
-# (source start file, name, description, authors, manual section).
-man_pages = [
-    (master_doc, 'reality.eth', u'reality.eth Documentation',
-     [author], 1)
-]
-
-
-# -- Options for Texinfo output -------------------------------------------
-
-# Grouping the document tree into Texinfo files. List of tuples
-# (source start file, target name, title, author,
-#  dir menu entry, description, category)
-texinfo_documents = [
-    (master_doc, 'reality.eth', u'reality.eth Documentation',
-     author, 'reality.eth', 'One line description of project.',
-     'Miscellaneous'),
-]
-
-
-

package/lib/reality-eth-monorepo/packages/docs/contract_explanation.rst

@@ -1,82 +0,0 @@
-Contract Internals
-==================
-
-This document is intended to help you read and understand the ``RealityETH.sol`` and ``RealityETH_ERC20`` contracts, in particular their internal data structures. See the previous documents for a higher-level description of what the contracts do.
-
-Questions
----------
-
-A question consists of a string encoding a JSON object. See :doc:`contracts`.
-This is structured as a reusable template, plus delimited string supplying parameters.
-
-The resulting document (template + parameters) identifies a particular question content.
-
-``Template ID`` + ``Opening datetime`` + ``Parameter string`` -> ``Content Hash``
-
-A question with a particular Content Hash may be asked on multiple occasions, some of which may have different arbitrator and timeout settings.
-
-The content hash and the other settings are hashed to make the Question ID.
-
-Versions 2 and 2.1: 
-``Content Hash`` + ``Arbitrator`` + ``Timeout`` + ``Creator`` + ``Nonce`` -> ``Question ID``
-
-Version 3: 
-``Content Hash`` + ``Arbitrator`` + ``Timeout`` + ``Min Bond`` + ``Creator`` + ``Contract address`` ``Nonce`` -> ``Question ID``
-
-
-Answer history entries
-----------------------
-
-Each time an answer is submitted, it creates a history item. The contract later needs to be able to access the entire history to correctly assign bonds at the end of the process.
-
-The question struct always stores the most recent answer and bond. However, to avoid the need to expand storage for answer, we store a only a single hash representing the entire history, and require users to supply the history when they claim bonds.
-
-``Empty  Bytes32`` + ``Answer`` + ``Bond`` + ``Answerer`` + ``False`` -> ``History Hash 1``
-
-``History Hash 1`` + ``Answer`` + ``Bond`` + ``Answerer`` + ``False`` -> ``History Hash 2``
-
-``History Hash 2`` + ``Answer`` + ``Bond`` + ``Answerer`` + ``False`` -> ``History Hash 3`` <- stored in Questions struct
-
-See below for how if the answer is supplied by commit->reveal, this will instead hold the Commitment ID, and the final item will be True.
-
-Commitments
------------
-
-To give people who consistently give right answers a defence against having their rewards taken from them by front-runners, we allow users to separate the posting of an answer into two stages: The commit and the reveal.
-
-The commitment consists of a hash of the answer that the user wishes to supply, combined with a secret nonce known only to themselves or their agent.
-
-``Answer`` + ``Nonce`` -> ``Answer Hash``
-
-A commitment is uniquely identified by the Question ID, the Answer Hash and the bond. (The system will not allow two answers to be submitted with the same bond.)
-
-``Question ID`` + ``Answer Hash`` + ``Bond`` -> ``Commitment ID``
-
-The information about the commitment - the reveal deadline, whether the reveal has happened and the revealed answer - are stored in a struct by indexed Commitment ID.
-
-Since the answer being submitted is not known when the the history item is created, answers using commit-and-reveal will store the Commitment ID instead of the answer.
-
-
-
-``Empty  Bytes32`` + ``Answer`` + ``Bond`` + ``Answerer`` + ``False`` -> ``History Hash 1``
-
-``History Hash 1`` + ``Answer`` + ``Bond`` + ``Answerer`` + ``False`` -> ``History Hash 2``
-
-``History Hash 2`` + ``Answer`` + ``Bond`` + ``Answerer`` + ``False`` -> ``History Hash 3`` 
-
-``History Hash 3`` + ``Commitment ID`` + ``Bond`` + ``Answerer`` + ``True`` -> ``History Hash 4`` <- stored in Questions struct
-
-
-During the claim process (see below) the contract will look up the revealed answer as referenced by the Commitment ID it finds in the history, then delete the Commitment struct.
-
-Claims
-------
-
-Claims are made by playing back the history from the latest entries first.
-
-Normally funds can be claimed at the end of the process in a single transaction. This transaction will assign the appropriate payments, clear the History Hash record from the question and delete any Commitment data.
-
-However, in some cases users may wish to claim only the later history entries in a single transaction, leaving the earlier entries to be claimed either by themelves or by another user in a future transaction. 
-
-In this case the contract needs to store some information about the claim process. This is stored in a Claim struct, referenced by Question ID.
-

package/lib/reality-eth-monorepo/packages/docs/contracts.rst

@@ -1,277 +0,0 @@
-Using Reality.eth from a contract
-=====================================
-
-Contract deployments
---------------------
-
-You can find the reality.eth contract addresses under https://github.com/RealityETH/reality-eth-monorepo/tree/main/packages/contracts/chains/deployments .
-
-For instance, the reality.eth v3 contract for mainnet (chain ID `1`) is shown in the file
-https://github.com/RealityETH/reality-eth-monorepo/blob/main/packages/contracts/chains/deployments/1/ETH/RealityETH-3.0.json
-
-Fetching information
---------------------
-
-The simplest way use for Reality.eth is to fetch some information for a question that has already been posted using the DApp.
-
-Hovering your mouse over the "..." mark in the upper right-hand corner of a question will show you the question ID and the hash of the question content.
-
-Fetching the answer to a particular question
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-
-Each question can be referred to by its ``question_id``, which is a ``bytes32``. 
-
-There is only one question with any given ``question_id``, and there can only be one corresponding answer.
-
-You can fetch the final answer for a question by calling 
-
-.. code-block:: javascript
-   :linenos:
-
-   bytes32 response = resultFor(bytes32 question_id);
-
-
-This will return ``bytes32`` data, or throw an error (``revert``) if the question does not exist or has not been finalized. You often want to cast the resulting ``bytes32`` to a ``uint256`` when you process it. By convention all supported types use ``0xff...ff`` (aka ``bytes32(type(uint256).max)``) to mean "invalid".
-
-
-Interpreting the result of a question
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-
-Questions have a ``type``, which decides what format the answer should take, and tells the Reality.eth dapp what kind of UI it should display to submit answers. The dapp recognizes the following types:
-
-bool
-""""
-
-A ``bool`` type represents a yes/no question. The result will be ``1``, ``0``, or ``0xff...ff`` for invalid, for example:
-
-Did Donald Trump win the 2016 US presidential election?
- * 1: Yes
- * 0: No
- * 0xff..ff: Invalid
-
-
-
-uint
-""""
-
-A ``uint`` type represents a number. The question may have a ``decimals`` field by which it should be divided. Negative numbers are not currently supported.
-
-How many electoral votes did Hillary Clinton win in the 2016 US presidential election?
-
-
-single-select
-"""""""""""""
-
-A ``single-select`` type represents a list of outcomes, producing a select box in the dapp. It is expressed as a zero-indexed, json-encoded array.
-
-Which party's nominee won the 2016 US presidential election?
-
-* ``0``: Democrat
-* ``1``: Republican
-* ``2``: Libertarian
-
-The outcomes are supplied in a field called ``outcomes``. There is also an ``invalid`` option (``0xff..ff``) which is added automatically.
-
-``["Democrat", "Republican", "Libertarian"]``
-
-
-multiple-select
-"""""""""""""""
-
-The ``multiple-select`` type represents a list of outcomes, producing checkboxes in the dapp. It is Expressed as a one-indexed, json-encoded array. 
-
-Which party's nominee won the seats the House in the 2016 congressional elections?
-
-* ``1``: Democrat
-* ``2``: Republican
-* ``4``: Libertarian
-
-These are added together, so ``0`` would mean than none were selected, (``1`` + ``2``) = ``3`` would indicate Democrat and Republican, (``1`` + ``4``) = ``5`` would indicate Democrat and Libertarian, etc. There is also an ``0xff..ff``: Invalid option.
-
-The outcomes are supplied in a field called ``outcomes``, as with ``single-select``.
-``["Democrat", "Republican", "Libertarian"]``
-
-
-datetime
-""""""""
-
-A ``datetime`` type represents a question that is answered with a date/time. This will be represented as a date picker in the UI, and expressed as a unix timestamp (seconds since 1970), of ``0xff..ff`` for invalid.
-
-The question may also specify a ``precision`` indicating whether it expects a datetime to the nearest year (``Y``), month (``m``), day (``d``), hour (``H``), minute (``i``) or second (``s``). If no precision is specified, it should be assumed to be ``d``, ie the answer should be a date (in UTC) with no time. An answer with a greater precision than that specified should be considered wrong.
-
-
-How questions are structured
-----------------------------
-
-Questions are expressed as a JSON object. This should specify a ``title`` and a ``type``, and may also include a ``category`` and ``lang`` field. It may include other fields depending on the type, such as ``outcomes`` to specify the possible outcomes in a ``single-select`` or ``multiple-select``, or ``decimals`` in a ``uint`` type.
-
-Example:
-``{"title": "Did Trump win the 2016 US presidential election?", "type": "bool", "category": "politics", "lang": "en"}``
-
-
-.. _templates:
-
-Templates
-^^^^^^^^^
-
-To avoid duplication and resulting gas fees, parts common to many questions are included in a pre-defined *template*. The *template* includes placeholders, and each question only needs to pass in the data necessary to replace the placeholders.
-
-The following templates are built in, one for each question type:
-
- * ``0``: ``{"title": "%s", "type": "bool", "category": "%s", "lang": "%s"}``
- * ``1``: ``{"title": "%s", "type": "uint", "decimals": 18, "category": "%s", "lang": "%s"}``
- * ``2``: ``{"title": "%s", "type": "single-select", "outcomes": [%s], "category": "%s", "lang": "%s"}``
- * ``3``: ``{"title": "%s", "type": "multiple-select", "outcomes": [%s], "category": "%s", "lang": "%s"}``
- * ``4``: ``{"title": "%s", "type": "datetime", "category": "%s", "lang": "%s"}``
-
-See :ref:`creating-templates` for how and why you can create your own custom template.
-
-Questions are creating by combining the ID of the template (for example, `2` for the built-in single-select template) with the unicode delimiter characther "␟".
-
-For example, a simple boolean question intended for the category "news-politics" might use the string:
-``Did Donald Trump win the 2016 US presidential election?␟news-politics␟en``
-
-A question with multiple outcomes will need the JSON-encoded outcome list passed in, eg
-``Which party's nominee won the 2016 US presidential election?␟"Democrat","Republican","Libertarian"␟news-politics␟en``
-
-
-Formatting
-^^^^^^^^^^
-
-You can set the `format` field in your template to `text/markdown` to use (restricted) markdown formatting in your `title`. If you do not set the format, it will be assumed to be `text/plain`.
-
-
-
-Asking questions
-----------------
-
-You can ask a new question by calling the ``askQuestion()`` function. 
-
-The content of the question defined as a combination of a numerical ``template_id`` and a ``string`` of parameters.
-
-.. code-block:: javascript
-   :linenos:
-
-   function askQuestion(
-      uint256 template_id, 
-      string question, 
-      address arbitrator, 
-      uint32 timeout, 
-      uint32 opening_ts, 
-      uint256 nonce
-   )
-   returns (bytes32 question_id);
-
-If the arbitrator you have selected charges a per-question fee, you must supply at least this much ETH. Any additonal ETH you send with this call will be assigned as a reward to whoever supplies the final answer to the question. See :doc:`fees` for more information.
-
-See :ref:`templates` for the ``template_id``, and how the ``question`` parameter is structured.
-
-If you are using a version of the contract that uses an ERC20 token, the same call will work but you cannot use it to supply funds. If you need to supply funds, either for an initial bond or because the arbitrator requires a per-question fee, you should instead call the ERC20 version, ``askQuestionERC20()``. This has an additional parameter for the number of tokens you wish to supply. This will attempt to debit the tokens from the token contract, or ``revert`` if they have not been approved.
-
-.. code-block:: javascript
-   :linenos:
-
-   function askQuestionERC20(
-      uint256 template_id, 
-      string question, 
-      address arbitrator, 
-      uint32 timeout, 
-      uint32 opening_ts, 
-      uint256 nonce,
-      uint256 tokens,
-   )
-   returns (bytes32 question_id);
-
-
-
-The ``arbitrator`` is the address of the contract that will be able to arbitrate. See :doc:`arbitrators` for more information. From version 3, this parameter may be left empty. For prior versions, if you wish to make arbitration impossible, you can instead supply the address of the `reality.eth` contract itself.
-
-The ``timeout`` is the time in seconds the question will have after adding an answer before it is automatically finalized. It would typically be around ``1 days``. The contract sanity-checks set the maximum possible value at ``365 days``.
-
-The ``opening_ts`` is the timestamp for the earliest time at which it will be possible to post an answer to the question. You can use ``0`` if you intend the question to be answerable immediately.
-
-The ``nonce`` is a user-supplied number that can be used to disambiguated deliberate repeated uses of the same question. You can use ``0`` if you never intend to ask the same question with the same settings twice.
-
-Any ETH or tokens provided with the ``askQuestion`` or ``askQuestionERC20`` call will be used as a question reward, minus any fee the specified arbitrator requires when a new question is asked.
-
-
-The ``askQuestion`` call returns a ``bytes32`` ID. This ID is made by hashing the parameters, plus ``msg.sender``. Note that the format will change in version 3.
-
-.. note:: The Etherscan "write contract" feature has been known to mangle the delimiter character.
-
-As of version 3, you can also specify a minimum bond below which the initial answer will not be accepted. For this, use the ``askQuestionWithMinBond()`` or ``askQuestionWithMinBondERC20()`` method.
-
-
-
-
-
-Accepting an answer only if something has happened (pre version 3)
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-
-Once a question has been created and the opening date (if set) reached, it can be answered immediately.
-
-In many cases you are not interested in the result of a particular question until it has a particular answer. For example, if you have a contract insuring against my house burning down, you are only interested in the result if my house burned down. You don't care about all the times in between setting up the policy and claiming when my house didn't burn down. 
-
-You may also want to screen out results indicating "unknown" or "no way to tell" or "hasn't happened yet".
-
-One approach is that instead of waiting for the result of a specific ``question_id``, you specify the type of question you want, then wait for a user to send you a question ID with the appropriate content and settings.
-
-To make this easier, we provide a method called ``getFinalAnswerIfMatches()``. This will throw an error not only if the question is not yet answered, but also if the content doesn't match, the bond or timeout is too low, or the arbitrator is not the one you expect.
-
-.. code-block:: javascript
-   :linenos:
-
-    function getFinalAnswerIfMatches(
-        bytes32 question_id, 
-        bytes32 content_hash, 
-        address arbitrator, 
-        uint256 min_timeout, 
-        uint256 min_bond
-    ) returns (bytes32 answer)
-
-You can then screen ``answer`` in your contract and only act on results that your contract is interested in.
-
-
-Accepting an answer only if something has happened (version 3 onwards)
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-
-To simplify the process of accepting only questions with an answer, from version 3 you can substitute ``forResult()`` with ``forResultOnceSettled()``. This screens the result for an answer representing "not yet settled", represented as ``bytes32(-2)``. Rather than returning this answer, it will revert as it would if the question question had not yet been answered. The contract allows any user to reopen a question in this state, creating a new question, repeatedly if necessary. Once a replacement question has been settled, its result is returned using the ID of the original question. A calling contract can ignore the details of this process and know only that it needs to call ``forResultOnceSettled()``.
-
-If using this feature it is also advisable to set a minimum bond.
-
-
-.. _creating-templates:
-
-Custom templates
-----------------
-
-If you want to create many similar requests, it will be more efficient to create your own template. For example, a flight insurance app might have:
-
-.. code-block:: json
-   :linenos:
-
-    {
-        "title": "Was flight %s on date %s delayed by more than 3 hours?", 
-        "type": "bool", 
-        "category": "flight-information"
-    }
-
-
-This can then by called with a string including only the flight number, the delimiter and the date, eg:
-    ``MH17␟2017-12-01``
-
-A template can be created by calling ``createTemplate("template")``, where "template" is the JSON template. This returns a numerical ID. If you wish to reference particular template on code running on multiple networks with the same content, you may find it useful to call ``template_hashes(bytes32 template_hash)`` to get the numerical ID.
-
-
-Contract addresses
-------------------
-
-Each supported chain has a reality.eth contract instance per supported token.  Some chains have additional deployments for earlier versions.  
-
-Each has its own configuration file like the following:
-
-  * reality.eth v3 for ETH on mainnet (chain ID 1): https://github.com/RealityETH/reality-eth-monorepo/blob/main/packages/contracts/chains/deployments/1/ETH/RealityETH-3.0.json
-  * reality.eth v3 for the GNO token on Gnosis chain (chain ID 100): https://github.com/RealityETH/reality-eth-monorepo/blob/main/packages/contracts/chains/deployments/100/GNO/RealityETH_ERC20-3.0.json
-
-The configuration file may also include a list of known arbitrators that should be displayed in the UI. If you use an arbitrator not included in this list, a warning will be displayed in the dapp.
-