Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Introduce a Getter for Arbitrator Policy Contract #10

Open
0xferit opened this issue Mar 22, 2023 · 2 comments
Open

Introduce a Getter for Arbitrator Policy Contract #10

0xferit opened this issue Mar 22, 2023 · 2 comments
Labels
good first issue Good for newcomers help wanted Extra attention is needed

Comments

@0xferit
Copy link
Member

0xferit commented Mar 22, 2023

Scenario:

  • Introduce a getter: function getPolicy(uint subcourtID) returns (string ipfsPath)
  • In subgraph mapping, inside handleChallenge or handleDispute, call this getter and assign to courtEntity.
@0xferit 0xferit added good first issue Good for newcomers help wanted Extra attention is needed labels Mar 22, 2023
@Anurag-Raut
Copy link

@0xferit can you please elaborate more, Do I need to make changes in arbitrators.sol?

@0xferit
Copy link
Member Author

0xferit commented May 1, 2023

Hello @Anurag-Raut ,

Kleros (dispute resolution provider, or simply arbitrator, in Truth Post) has sub-court policies, which are registered in this contract: https://goerli.etherscan.io/address/0x28c8A3A2E3c8Cd3F795DB83764316a1129a069bA#code.

  1. Save this address in TruthPost during deployment, this is immutable. Note that for each network, there is only one arbitrator (thus one policy registry). So we can assume it won't change.
  2. Introduce a getter function getPolicy(uint subcourtID) returns (string ipfsPath).

That's all. arbitrator. sol is not something we develop; it is solely for testing purposes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Good for newcomers help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

2 participants