kleros / gtcr Goto Github PK

I got a perma spinner with "awaiting authorization" toast message and qr-code modal.

Allow setting the challenge period duration for the TCR on the TCR factory.

The contract should be updated to lock the meta evidence used for the request such that an update to the meta evidence doesn't change the terms of previous requests.

Update the UI to account for this.

The primary document displayed when enabling a badge should be the primary document of the related TCR, not the primary document of the badge.

The current name of the connected TCR is a bit cloudy. Change it to Enabled Badges.

• Inform the user to which network he is connected to in order to avoid sending transactions to the wrong network.
• If the network changes (due to for example, the user connecting his wallet), the UI should attempt refetching the item(s) on the new context.

The TCR factory is should set the TCR title to the tcrTitle field, and not the title field (which is part of the evidence standard`.

• Display an "Add Badge" button in the item details view of the item, if the Related TCR has at least one TCR registered.
• Clicking the button should open a modal, with a list of options. Each option is a TCR registered on Related TCR.
• Selecting a TCR and clicking "Add Badge" should open a modal to submit the item to the Badge TCR, with the known fields pre-filled.

The meta evidence file created by the factory is missing the evidenceDisplayURI field.

When trying to set up notifications, my hardware wallet is not triggered and i can't sign.

Thus resulting in this error :

I am using a ledger nano x with Brave.

After having deployed a TCR, the UI seems to be stuck on this screen:

1- As a user I expect the step 4 to be ticked and not to be able to deploy the same TCR right away.
2- When I connect at a later time I am still facing this same screen but i would expect a fresh screen with the history of what I already deployed.
3- Previous deployments list should also be in a human readable format if possible: if a user has several TCR deployed, it is a pain to know which transaction is related to which TCR and enabled TCR badges.
See after only 2 deployments:

Missing unit and input validation on Ether inputs. See factory view.

• Prevent typing non numerical values.
• Display unit.

Currently, a use might want to submit the address of a TCR that does not implement the current GTCR API to a TCR of TCRs.

We should probably rename it "GTCR of GTCRs" and verify that the address provided by the user actually refers to the code of a GTCR instance.

Otherwise a user might attempt submitting the Doges on Trial or the T²CR to the list and loose money.

Tasks

• Fetch all ItemSubmitted events of the TCR, and parse them for searching
• Display top 5 matching results. Load and display their current status.

Currently, the GTCRView contract scans the registry from either the start or the end of the list based on the oldestFirst parameter. The UI then sorts the result to display items with pending requests first.

This is a problem, however. We want items with pending requests to be listed first. Only then we sort by time of submission. Otherwise someone can place a removal request on a very old item and no one would notice.

Tasks:

• Edit the GTCR contract to emit a RequestSubmitted event every time someone makes a request.
• Edit the UI to fetch the latest latest RequestSubmitted events (in parallel to the GTCRView.queryItems request). With the IDs of the items, fetch their status in parallel.
• Add the items with pending requests to the result set and sort.

The item details view should include a component that queries all TCRs registed on the Related TCR with the item's data. If the items are found, a display a badge with theTCR symbol.

When the user navigates to the TCR, he would see it in components of the UI: "Submit Meme, Remove Meme, Challenge Meme" etc

It shows up in notifications as well, emails and twitter "A meme you submitted to NEC - Storytelling was challenged!"

In the factory, provide a link to one of our policy documents as an example

If the meta evidence file is invalid, display big red card on:

• Item list view
• Item details view

If I navigate using a router link, the items component doesn't load the items. Additionally, actions are sent to the incorrect TCR, resulting on an exception.

In this hover, although the arbitrator address is already filled in, we may want to add a little text stating something like ‘ This already points to Kleros as the arbitrator’ just to specify cases are already going to Kleros court.

This should have the effect of displaying a "Go to TCR" link on the items.

Currently the factory supports requiring removal evidence. However the UI does not actually enforce this.

And explain why.

Looser > loser

We need to expand on what these multipliers do and clarify that the values are in basis points.

The top bar should include a notifications icon.

Deploy a registry contract to map the user's address to the TCRs he's interacted with.
Deploy a proxy contract to batch what would be 2 transactions into one. Any transactions sent to a TCR contract should be sent to the proxy contract. The proxy contract forwards the call to the TCR and if the call does not revert, saves the interaction interactions[caller].push(tcr)
Fetch the addresses of the TCRs the user interacted with.
Fetch ItemSubmitted, Evidence, AppealContribution events of each TCR to find items the user submitted, challenged, submitted evidence to or contributed with appeal fees.

The initial proposal would not provide a good UX as it relies on saved information on the client. So a user would receive the same notification more than once across devices, or would miss notifications if it is the first time accessing the app on a new client.

Instead, we provide a backend where notifications are stored at kleros/gtcr-notifications.

Submission Challenge Deposit > Challenge Submission Deposit

A nice enhancement would have to get a timestamp for each historic detail of items:

It would make sense to know when each entry has occurred:
"Item Submitted", "Item rejected", etc...

The crowdfunding card lacks important UI features and looks bland. Display:

• Progress bars;
• The potential reward for funding this either side on this round;
• Use icons.

Setup GTCR on mainnet beta for the story telling bounty

• Add a warning "This is beta software/there is a bounty on this code" + option: "Don't remind me again"
• Point all bots to mainnet deployment.
• Write a submission policy

The Request struct no longer includes the requestType since it is already available in the RequestSubmitted logs.

Update the code so that it fetches from the logs instead.

To allow badges on the GTCR, we add new features to the factory:

• Allow setting a TCR logo. This will be displayed as the badge symbol on other TCRs.
• Add a new step to the factory. This step should allow the user to set the parameters of the related TCR: Primary document, challenge period, deposits etc.

If this switch is marked as true:

• Skip the step of selecting the columns. The only column will be the TCR address (of type GTCR Address).
• Item cards should fetch and display the TCR metadata. (e.g. The TCR logo, name and description).

Let users select their arbitrator with advanced options.

The item status card looks a bit bland without icons.