kleros / curate-v2

Curate V2

curate-v2

Setup:

yarn

The frontend is located in the web folder

cd web
yarn && yarn start

curate-v2's Issues

Curate v2 - Dispute Template Mappings

For registration and removal

IPFS retrieval: endpoint update

In a code review, I've found that we have hardcoded some urls to ipfs.klers.io. Specifically:

• list
• policy
• registry

This hardcoded values should use the envvar IPFS_GATEWAY defined here to retrieve those values.
Please, update them in order to be consistant in the site and to have control over the gateway that we are using.
Thanks!

List Creation Flow

The equivalent of this wizard in v1

Curate v2 - feature parity with v1

Figma

https://www.figma.com/file/b7DEUKDeHlOl4ocDTMv7UIhZ/Kleros?node-id=14642%3A187559&mode=dev

Scope: single chain deployment on Arbitrum

• Start with only Arbitrum.
• Ignore the v1 lists for now.

For later...

We will follow up in a separate issue for this:

• Deployment on other chains, with 1 subgraph per chain.
• Multichain display by querying each chain's subgraphs.
• V1 compatibility.

Partial implementation atop v1

https://github.com/kleros/gtcr-v2
https://gtcr-v2.netlify.app

Redeploy the subgraph on Studio

Affected code:

• https://github.com/kleros/curate-v2/blob/master/web/.env.devnet.public#L3

Resolves kleros/builder-baseline#22

Curate v2 - Email notification bot

Justification display for removal requests and removal challenges

https://www.figma.com/design/b7DEUKDeHlOl4ocDTMv7UIhZ/Kleros?node-id=21243-145339&t=nfhgOEpphdymi53p-1

Curate v2 - SIWE + Notification settings

Item labels improvements

Registry screen:

• Add "Created by "
• Replace "Registry Address" with the actual address

Item screen:

• Add "Created by "

Subgraph endpoint update required

Hey team,

We've noticed that you're referencing a subgraph deployed on The Graph's hosted service in this repository. Just a heads-up: after June 12th, hosted service subgraph endpoints will no longer be available as the offering is being deprecated.

If you are the subgraph owner or maintainer, it's time to upgrade your subgraph to the network. This ensures everything keeps running smoothly and you get access to all the latest features and improvements. Here is a quick guide with all the upgrade steps.

If you're not the subgraph owner or maintainer, check Graph Explorer to see if the subgraph development team has already upgraded to the network. If you don’t find an upgraded subgraph, a friendly nudge to the subgraph development team would be greatly appreciated—it's a quick process that benefits everyone. Here's the upgrade guide with all the necessary steps for the subgraph development team.

Once the subgraph is upgraded to the network, you can create an API key and updated query URL in Subgraph Studio then update this repository to query from the new endpoint, https://api.studio.thegraph.com/query/<ID>/<SUBGRAPH_NAME>/<VERSION>

Need more support or have more questions? Feel free to reach out to [email protected]. We're here to help!

Cheers,

Paka

Testing of directly adding/removing items

• Test it
• Check that the subgraph and frontend can pick the items added directly
• Modify the function to take an array as parameter

https://github.com/kleros/curate-v2/blob/master/contracts/src/CurateV2.sol#L309-L335

From @greenlucid

addItemDirectly and removeItemDirectly are not emitting RequestSubmitted

fixing it could just be editing subgraph to create default Request Entity on ItemStatusChange with no Request associated

frontend crashes because it expects request to exist
request doesn't exist because subgraph does not handle properly
subgraph could handle it properly