Skip to content

Commit 5afe346

Browse files
parulgitbook-bot
authored andcommitted
GITBOOK-374: Updated "fileURI"
1 parent b50ec41 commit 5afe346

File tree

1 file changed

+21
-6
lines changed

1 file changed

+21
-6
lines changed

developer/arbitration-development/erc-1497-evidence-standard.md

Lines changed: 21 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -106,13 +106,28 @@ The fields in this MetaEvidence JSON are as follows:
106106
* `uint`: the jurors input an unsigned integer.
107107
* `int`: the jurors input a signed integer.
108108
* `string`: the jurors enter a string. String must fit into `bytes32`.
109-
* `precision`: only applicable for ruling types `int` and `uint` to indicate the number of decimal places a ruling contains.
109+
* `precision`: only applicable for ruling types `int` and `uint` to indicate the number of decimal places a ruling contains.
110110
* `titles`: an array of the options available to the jurors. NOTE: the sequence of the titles is important as they map directly to the rulings you get when the Arbitrator responds to your Arbitrable using the `rule()` function.
111111
* `descriptions`: the description of the `rulingOption` titles.
112-
* `fileURI`: The URI that leads to the primary document of the case, which is a natural language contract, policy, or primary document that is the basis of the dispute. See [this section](../../integrations/types-of-integrations/1.-dispute-resolution-integration-plan/#2.-write-a-good-dispute-policy) on the role of the primary document and how to write a good one.
113-
* `evidenceDisplayInterfaceURI`: The URI to a display interface that should be used to render the facts of a case in an iframe by the Arbitrator. 
114-
115-
Here's an example of a MetaEvidence JSON: 
112+
* `fileURI`: The URI points to the primary document of the case, which is the foundational document that establishes the rules for the dispute. This document is typically a dispute policy that defines criteria for resolution and serves as the basis for jurors to make their decisions. We have established dispute policies for the following products that can be referenced: 
113+
114+
* **Kleros Scout**
115+
* [ATR (Address Tag Registry)](https://ipfs.kleros.io/ipfs/QmXuUER9is6n4XgiDtNnZBqPCTsJvMj1ku5gQg5EZGxfxw/atr-registry-policy.pdf)
116+
* [CDN (Curated Domain Names)](https://ipfs.kleros.io/ipfs/QmVL3hR8E2XcnJ1PjKARqh7e5SDJM1HeKLsUYnLnUyKEWo/domain-name-dispute-resolution-policy-v1.0.pdf)
117+
* [Snap](https://ipfs.kleros.io/ipfs/QmcARXVNcX8LpvjMZDgL8AQyW8q1XxwMfVTPSJ3YRvCpvx/snap-dispute-policy.pdf)
118+
* **Oracle**
119+
* [Oracle Dispute Policy](https://ipfs.kleros.io/ipfs/QmfHRnNnBxxa1uD5MKP2HNrB8hWjHsrNfqaLetiEa8LfaT/reality-eth-dispute-policy.pdf)
120+
* **Court**
121+
* [Court Policies](https://ipfs.kleros.io/ipfs/QmZYxRxwKMPpSMq8MJSd5QFeSUZoii7hFwXJvQn7bvnbCq/kleros-court-justice-policy.pdf)
122+
* **Governor**
123+
* [Governor Policy](https://ipfs.kleros.io/ipfs/QmVMqK7yXTXVXzLGJgT1XLJeaWD5LJhN2A2PrqMM41BbWY/kleros-governor-policy.pdf)
124+
* **Proof of Humanity**
125+
* [PoH v2 Policy](https://ipfs.kleros.io/ipfs/QmNSV9xXKiBtaRW1MYmFaVkqsD1Qez2ZDX1jyP21j87jxj/poh-v2-policy.pdf)
126+
127+
For guidance on creating your own dispute policy document, please refer to our [Policy Writing Guide](https://docs.kleros.io/integrations/policy-writing-guide).
128+
* `evidenceDisplayInterfaceURI`: The URI to a display interface that should be used to render the facts of a case in an iframe by the Arbitrator.
129+
130+
Here's an example of a MetaEvidence JSON:
116131

117132
```json
118133
{
@@ -165,7 +180,7 @@ https://cdn.kleros.link/ipfs/QmSL8d82dMhcThwERWaF4LtmCa4hgV7TyPjAo4fKCzPVkv/inde
165180
```
166181

167182
{% hint style="info" %}
168-
Pro-tip: To avoid having to create a new MetaEvidence JSON and pin it to IPFS prior to every dispute, you can use just a static MetaEvidence JSON, and use a `evidenceDisplayInterfaceURI` that dynamically displays different information based on the query string. 
183+
Pro-tip: To avoid having to create a new MetaEvidence JSON and pin it to IPFS prior to every dispute, you can use just a static MetaEvidence JSON, and use a `evidenceDisplayInterfaceURI` that dynamically displays different information based on the query string.
169184
{% endhint %}
170185

171186
### Evidence: <a href="#evidence" id="evidence"></a>

0 commit comments

Comments
 (0)